From 2394cd8dfe39fd30a97eef56feaf227dc0d9b920 Mon Sep 17 00:00:00 2001 From: Marine DECHAMP-GUILLAUME <92780073+MdechampG@users.noreply.github.com> Date: Tue, 2 Apr 2024 10:09:19 +0200 Subject: [PATCH 1/2] feat: update ticker AXONE --- docs/academy/part-2/describe-resource.mdx | 2 +- docs/academy/part-2/describe-zone.mdx | 2 +- docs/academy/part-2/resource-governance.mdx | 2 +- docs/academy/part-2/zone-governance.mdx | 2 +- docs/faq/faq.md | 18 ++++++++--------- docs/tutorials/cli-1.mdx | 4 ++-- docs/tutorials/explorer-sc.md | 8 ++++---- docs/tutorials/keplr-1.mdx | 22 ++++++++++----------- docs/whitepaper/architecture.mdx | 14 ++++++------- docs/whitepaper/roles.md | 10 +++++----- docs/whitepaper/token-model.mdx | 2 +- docs/whitepaper/use-cases.md | 6 +++--- 12 files changed, 46 insertions(+), 46 deletions(-) diff --git a/docs/academy/part-2/describe-resource.mdx b/docs/academy/part-2/describe-resource.mdx index 881c63b1bb6..bf4dd32d00c 100644 --- a/docs/academy/part-2/describe-resource.mdx +++ b/docs/academy/part-2/describe-resource.mdx @@ -256,7 +256,7 @@ The Axone blockchain can only register VCs in N-Quads format. Then, you must con The final step is to register the VCs in the Axone blockchain by submitting them to the Dataverse smart contract. It's the role of the Registrant (who can be the Holder or another entity). :::info -Note that as you interact with the Axone blockchain, you must pay fees in $AXON at each transaction. +Note that as you interact with the Axone blockchain, you must pay fees in $AXONE at each transaction. ::: ```bash diff --git a/docs/academy/part-2/describe-zone.mdx b/docs/academy/part-2/describe-zone.mdx index 09b41a8a59b..9c389b44f57 100644 --- a/docs/academy/part-2/describe-zone.mdx +++ b/docs/academy/part-2/describe-zone.mdx @@ -185,7 +185,7 @@ The Axone blockchain can only register VCs in N-Quads format. Then, you must con The final step is to register the VCs in the Axone blockchain by submitting them to the Dataverse smart contract. It's the role of the Registrant (who can be the Holder or another entity). :::info -Note that as you interact with the Axone blockchain, you must pay fees in $AXON at each transaction. +Note that as you interact with the Axone blockchain, you must pay fees in $AXONE at each transaction. ::: ```bash diff --git a/docs/academy/part-2/resource-governance.mdx b/docs/academy/part-2/resource-governance.mdx index d9f9b807165..13cbae91955 100644 --- a/docs/academy/part-2/resource-governance.mdx +++ b/docs/academy/part-2/resource-governance.mdx @@ -309,7 +309,7 @@ The Axone blockchain can only register VCs in N-Quads format. Then, you must con The final step is to register the VCs in the Axone blockchain by submitting them to the Dataverse smart contract. It's the role of the Registrant (who can be the Holder or another entity). :::info -Note that as you interact with the Axone blockchain, you must pay fees in $AXON at each transaction. +Note that as you interact with the Axone blockchain, you must pay fees in $AXONE at each transaction. ::: ```bash diff --git a/docs/academy/part-2/zone-governance.mdx b/docs/academy/part-2/zone-governance.mdx index 30536e569c0..be46f387ae5 100644 --- a/docs/academy/part-2/zone-governance.mdx +++ b/docs/academy/part-2/zone-governance.mdx @@ -288,7 +288,7 @@ The Axone blockchain can only register VCs in N-Quads format. Then, you must con The final step is to register the VCs in the Axone blockchain by submitting them to the Dataverse smart contract. It's the role of the Registrant (who can be the Holder or another entity). :::info -Note that as you interact with the Axone blockchain, you must pay fees in $AXON at each transaction. +Note that as you interact with the Axone blockchain, you must pay fees in $AXONE at each transaction. ::: ```bash diff --git a/docs/faq/faq.md b/docs/faq/faq.md index 366a3fea56a..8f752d2ce9e 100644 --- a/docs/faq/faq.md +++ b/docs/faq/faq.md @@ -248,25 +248,25 @@ The Logic module is designed to primarily address logical queries based on facts ## Token -### What is the utility of the $AXON token? +### What is the utility of the $AXONE token? -The $AXON is the fee token of the Axone blockchain, it is required to submit transactions to the network of validators. +The $AXONE is the fee token of the Axone blockchain, it is required to submit transactions to the network of validators. -Similar to other Proof-of-stake chains, the $AXON secures the network through staking. +Similar to other Proof-of-stake chains, the $AXONE secures the network through staking. -The $AXON is also a governance token. Anyone can do on-chain proposals, and $AXON holders can vote yes, no, abstain or no with veto to these proposals. +The $AXONE is also a governance token. Anyone can do on-chain proposals, and $AXONE holders can vote yes, no, abstain or no with veto to these proposals. -The $AXON token can also be a governance token for any Zone if implemented that way. +The $AXONE token can also be a governance token for any Zone if implemented that way. -Beyond that, and more related to use cases, the $AXON is used by default for value sharing when a workflow is initiated according to the business model of the Zone and of the resources invoked in the workflow. A 2% tax is applied on workflows to reduce the token supply in order compensate for inflation and another 1% tax is collected for the community to redistribute it and fund any initiative like contributing to public goods. +Beyond that, and more related to use cases, the $AXONE is used by default for value sharing when a workflow is initiated according to the business model of the Zone and of the resources invoked in the workflow. A 2% tax is applied on workflows to reduce the token supply in order compensate for inflation and another 1% tax is collected for the community to redistribute it and fund any initiative like contributing to public goods. -The $AXON token may also be used for security purposes, requiring data or service providers to lock some tokens in order to prove their good faith. The tokens may be used for curation on Datasets and Services, allowing users to lock tokens on specific resources to get a part of their revenue, when relevant. +The $AXONE token may also be used for security purposes, requiring data or service providers to lock some tokens in order to prove their good faith. The tokens may be used for curation on Datasets and Services, allowing users to lock tokens on specific resources to get a part of their revenue, when relevant. More details about Token Model [here](https://docs.okp4.network/whitepaper/token-model) -### Can price volatility of the $AXON token be a problem? +### Can price volatility of the $AXONE token be a problem? -The $AXON price volatility can become a problem when it's used for payment. Imagine a dataset or service providers denominates its price in KNOW. If the $AXON values goes +50%, then it goes the same of providers who may see their resources less used because 50% more expensive. An external service can be used to define another unit of account (like the dollar) and have the $AXON value updated every time their resource is consumed. +The $AXONE price volatility can become a problem when it's used for payment. Imagine a dataset or service providers denominates its price in KNOW. If the $AXONE values goes +50%, then it goes the same of providers who may see their resources less used because 50% more expensive. An external service can be used to define another unit of account (like the dollar) and have the $AXONE value updated every time their resource is consumed. ### Decentralization seems to add complexity. Does that get offset but the open composability? diff --git a/docs/tutorials/cli-1.mdx b/docs/tutorials/cli-1.mdx index b84a4c9045d..6a22c621f68 100644 --- a/docs/tutorials/cli-1.mdx +++ b/docs/tutorials/cli-1.mdx @@ -135,7 +135,7 @@ pagination: :::tip -Provide your Axone address to the [faucet](https://faucet.okp4.network/) to receive 1 $AXON (test tokens). +Provide your Axone address to the [faucet](https://faucet.okp4.network/) to receive 1 $AXONE (test tokens). ::: @@ -148,7 +148,7 @@ okp4d query bank total \ --node https://api.testnet.okp4.network:443/rpc ``` -### Send some $AXON to another wallet +### Send some $AXONE to another wallet Here is the command to send 0.5 AXON (`500000 uAXON`) from the wallet `mywallet` you control to the wallet with the Axone address `okp41r0pf2d78w8w29sm9a6qm8x6yqshezm0k6vwcrg`: diff --git a/docs/tutorials/explorer-sc.md b/docs/tutorials/explorer-sc.md index c331680ea84..de05f6f17e4 100644 --- a/docs/tutorials/explorer-sc.md +++ b/docs/tutorials/explorer-sc.md @@ -31,11 +31,11 @@ A transaction on the blockchain is a record of some blockchain state change, lik The [Axone Explorer](https://explore.okp4.network/OKP4%20Drunemeton%20testnet) allows you to view and analyze these transactions in detail. Several transactions are validated in a block. You can check the last validated blocks via the ["Blocks" menu](https://explore.okp4.network/OKP4%20Drunemeton%20testnet/block) . Click on the "Transactions tab" to get the transactions in recent blocks. -Before moving on to transactions with smart contracts, let's begin with a basic operation: a transfer of $AXON tokens. +Before moving on to transactions with smart contracts, let's begin with a basic operation: a transfer of $AXONE tokens. :::info -You need to [set up a wallet with Keplr and own some $AXON tokens](https://docs.okp4.network/tutorials/keplr-1). +You need to [set up a wallet with Keplr and own some $AXONE tokens](https://docs.okp4.network/tutorials/keplr-1). ::: @@ -46,10 +46,10 @@ You need to [set up a wallet with Keplr and own some $AXON tokens](https://docs. You'll see your Axone wallet address if you click again on the wallet button. Click on it to copy the address. -2. Now,you are ready to send $AXON via the explorer interface : +2. Now,you are ready to send $AXONE via the explorer interface : - Click on the "Send" button from the Dashboard. -- Send a few $AXON tokens to another Axone wallet, `okp41wuxc2mzy0wp27cdcfnde3vz07eurpd7grfmq6n` as the recipient for example. +- Send a few $AXONE tokens to another Axone wallet, `okp41wuxc2mzy0wp27cdcfnde3vz07eurpd7grfmq6n` as the recipient for example. - Click on "Send" and "Approve" to confirm the transfer.
diff --git a/docs/tutorials/keplr-1.mdx b/docs/tutorials/keplr-1.mdx index a828413df6e..eafd1c5b451 100644 --- a/docs/tutorials/keplr-1.mdx +++ b/docs/tutorials/keplr-1.mdx @@ -34,7 +34,7 @@ Optionally, you can **pin Keplr for easy access**: click the ‘Extensions' butt ![New Keplr wallet created](/img/content/tutorials/keplr-4.webp) -## Add Axone network to Keplr and get $AXON test tokens +## Add Axone network to Keplr and get $AXONE test tokens **AXON** is the native token on the Axone blockchain. You need **AXON** tokens to interact with the Axone blockchain (i.e. send a payment or execute a smart contract query). @@ -44,17 +44,17 @@ The official Axone faucet provides a way to obtain test tokens for experimentati 2. Click on the "**Send me AXON**" button. -![Axone Faucet, ask for $AXON tokens](/img/content/tutorials/keplr-5.webp) +![Axone Faucet, ask for $AXONE tokens](/img/content/tutorials/keplr-5.webp) 3. You will have to pass the reCaptcha challenge, and then a Keplr pop-up will appear. **Approve** adding the `okp4-drunemeton-1` chain to Keplr. ![Approve Axone network adding to Keplr](/img/content/tutorials/keplrmaj-6.webp) -4. And you're done! Congrats, you received $AXON tokens 🥳 +4. And you're done! Congrats, you received $AXONE tokens 🥳 -## Check your $AXON balance and get your Axone address +## Check your $AXONE balance and get your Axone address -1. To see your $AXON balance, you have to make the `OKP4-drunemeton-1` network visible within the extension: +1. To see your $AXONE balance, you have to make the `OKP4-drunemeton-1` network visible within the extension: - Click on the Keplr extension. - Click the **≡** button upper on the left, then click "**Manage Chain Visibility**". @@ -72,7 +72,7 @@ Alright, there's **1 AXON** in the wallet.
-3. Your wallet is identified by an address derived from your recovery phrase. To receive $AXON tokens, you should provide your Axone address to the spender. +3. Your wallet is identified by an address derived from your recovery phrase. To receive $AXONE tokens, you should provide your Axone address to the spender. Here's how you can have your Axone address: - Click on the Keplr extension icon and "Copy address". @@ -81,9 +81,9 @@ Here's how you can have your Axone address:
-## Send $AXON tokens to another wallet +## Send $AXONE tokens to another wallet -Now that you have $AXON tokens in your Keplr Wallet, you can send them to other Axone accounts. Follow these steps: +Now that you have $AXONE tokens in your Keplr Wallet, you can send them to other Axone accounts. Follow these steps: 1. Click on the Keplr extension icon and on "Send". @@ -95,7 +95,7 @@ Now that you have $AXON tokens in your Keplr Wallet, you can send them to other ### Check your transaction with the explorer -You can look at the [Axone explorer](https://explore.okp4.network/OKP4%20Drunemeton%20testnet) to check all transactions you executed. Click the "Search" button (up on the right) and provide your Axone address. The $AXON payment you've sent will appear in the Transactions part. +You can look at the [Axone explorer](https://explore.okp4.network/OKP4%20Drunemeton%20testnet) to check all transactions you executed. Click the "Search" button (up on the right) and provide your Axone address. The $AXONE payment you've sent will appear in the Transactions part. ![Look for your transaction in the Axone explorer](/img/content/tutorials/keplr-13.webp) @@ -105,10 +105,10 @@ To get started, you should: - Set up an account with the Keplr Wallet extension - Safely store the recovery phrase, the secret way to use your account -- Add the Axone network and get $AXON tokens via the official faucet +- Add the Axone network and get $AXONE tokens via the official faucet Once you're done, you can interact with the blockchain: -- You can send $AXON tokens to another wallet using the "Send" button in Keplr, for example. +- You can send $AXONE tokens to another wallet using the "Send" button in Keplr, for example. - You can also checkout the explorer to see the transactions status and more. Congratulations! You have successfully learned how to set up an Axone account using Keplr Wallet, obtain test tokens, and send transactions. diff --git a/docs/whitepaper/architecture.mdx b/docs/whitepaper/architecture.mdx index e2085c7b057..434a056c020 100644 --- a/docs/whitepaper/architecture.mdx +++ b/docs/whitepaper/architecture.mdx @@ -32,7 +32,7 @@ Tendermint is a partially synchronous Byzantine fault-tolerant (BFT) consensus p When a user wants to update the blockchain state, he submits a transaction with cryptographic keys authentication. Users interacting with the network pay fees to these validators for every transaction. These fees are paid with the Axone blockchain native coin, $KNOW. -Validators guarantee the reliability of the blockchain. As they all share the same on-chain data and process the same transactions, if a node acts maliciously (e.g., the purpose of updating a state for its benefit without required permissions), the rest of the network will reject it. The economic incentive with $AXON fees makes virtuous behavior more profitable than unwise conduct. +Validators guarantee the reliability of the blockchain. As they all share the same on-chain data and process the same transactions, if a node acts maliciously (e.g., the purpose of updating a state for its benefit without required permissions), the rest of the network will reject it. The economic incentive with $AXONE fees makes virtuous behavior more profitable than unwise conduct. ### Built on Cosmos @@ -56,7 +56,7 @@ The `logic` module is not strongly coupled to the Axone blockchain. It's designe The Axone blockchain uses production-grade modules from the Cosmos SDK. These generic modules facilitate the implementation of protocol governance, token operation management, validator punishment mechanisms, and authentication of accounts and transactions. Two of them have a custom implementation: the mint and the vesting modules. -"Mint", used for creating new $AXON units, applies specific tokenomics parameters. It determines the inflation rate for validators' and stackers' earnings. +"Mint", used for creating new $AXONE units, applies specific tokenomics parameters. It determines the inflation rate for validators' and stackers' earnings. "Vesting" refers to distributing tokens over a specified period rather than all at once. This approach allows for controlled token distribution over time, promoting responsible token management and preventing immediate sell-offs that could negatively impact the Axone ecosystem. ### WASM @@ -210,18 +210,18 @@ The Axone solution orchestrates the training process without exposing raw data, 1. Each on their own, Corp A and Corp B indicate through an administration portal the underlying technology of their respective database. They store access tokens with a Secret Management Service, with authorization for orchestration service. -2. Corp A and Corp B continue on the administration portal and define the rules, with access restrictions and payment conditions (a fixed $AXON fee per request, for example). A raw Prolog file is accepted, but the interface provides an ergonomic form for a better UX. +2. Corp A and Corp B continue on the administration portal and define the rules, with access restrictions and payment conditions (a fixed $AXONE fee per request, for example). A raw Prolog file is accepted, but the interface provides an ergonomic form for a better UX. Corp A and Corp B inform a maximum of metadata, especially to describe the different available datasets, their structures and the nature of their contents. The portal combines the service execution instructions, the governance rules and the descriptive pieces of information in a Turtle file. Then a transaction adds it to the on-chain ontology. 3. Metadata indicate that resources shared by Corp A and Corp B are compatible with a ML job from Corp C. Corp C also uses the administration portal to submit its training model algorithm, governance rules, and service execution instructions. 4. Individual D parameters its cloud environment with the portal, setting up how an orchestration service should store the execution request results. -5. Individual D uses the portal to request service execution with the ML Workflow from Corp C, using data from Corp A and Corp B. He submits a transaction with a Keplr wallet and pays with $AXON tokens. The blockchain validates the execution request (access and execution authorizations). +5. Individual D uses the portal to request service execution with the ML Workflow from Corp C, using data from Corp A and Corp B. He submits a transaction with a Keplr wallet and pays with $AXONE tokens. The blockchain validates the execution request (access and execution authorizations). 6. The orchestration service listens to the event from the blockchain. It recovers access keys, and then executes the workflow training algorithm from Corp C, using Corp A & Corp B data it fetches. -7. The orchestration service tracks the progress and state changes of all jobs within the workflow and reports this information to the blockchain. If all works well, service agreement rules are applied, $AXON tokens from Individual D are unlocked to Corp A, Corp B et Corp C. +7. The orchestration service tracks the progress and state changes of all jobs within the workflow and reports this information to the blockchain. If all works well, service agreement rules are applied, $AXONE tokens from Individual D are unlocked to Corp A, Corp B et Corp C. 8. The orchestration service stores the result in the provided Individual D's storage solution. Optionally, this new knowledge can also be referenced as a data source for other workflows. @@ -256,7 +256,7 @@ Note right of IndD: 4. IndD->> Secret: Cloud storage keys for results Note right of IndD: 5. -IndD->> Axone: Knowledge request(ML Workflow(DbA + Db B)) - $AXON payment +IndD->> Axone: Knowledge request(ML Workflow(DbA + Db B)) - $AXONE payment Axone->>Axone: Valid knowledge request Note right of Axone: 6. @@ -272,7 +272,7 @@ ML Workflow->> Orchestrator: Knowledge result Note right of Orchestrator: 7. Orchestrator->> Axone: Workflow state report -Axone->>Axone: Service agreement exec ($AXON rev share, ...) +Axone->>Axone: Service agreement exec ($AXONE rev share, ...) Note right of Orchestrator: 8. Orchestrator->> Storage: Store result diff --git a/docs/whitepaper/roles.md b/docs/whitepaper/roles.md index 8693773cd83..a608f90bef0 100644 --- a/docs/whitepaper/roles.md +++ b/docs/whitepaper/roles.md @@ -36,7 +36,7 @@ More information about [Tendermint BFT mechanism](https://tendermint.com/core/) ***Purpose*** -Delegators primarily delegate their $AXON tokens and voting power to Validators to accumulate rewards. +Delegators primarily delegate their $AXONE tokens and voting power to Validators to accumulate rewards. ***Responsibilities*** @@ -48,7 +48,7 @@ Delegators engage with the protocol by delegating their tokens to Validators. Ho ***Entity*** -Delegators are typically individuals or entities staking $AXON tokens. +Delegators are typically individuals or entities staking $AXONE tokens. ### DAO Participants @@ -58,15 +58,15 @@ The principal role of DAO Participants is to participate in the on-chain governa ***Responsibilities*** -DAO Participants are responsible for issuing improvement proposals, voting on these proposals, and staking $AXON tokens to participate in governance. As protocol holders, they also have a direct stake in its direction and success. +DAO Participants are responsible for issuing improvement proposals, voting on these proposals, and staking $AXONE tokens to participate in governance. As protocol holders, they also have a direct stake in its direction and success. ***Interaction*** -DAO Participants interact with the protocol by making and voting on proposals, facilitated by staking $AXON. Each $AXON token provides a voting right. +DAO Participants interact with the protocol by making and voting on proposals, facilitated by staking $AXON. Each $AXONE token provides a voting right. ***Entity*** -DAO Participants can only be delegators or Validators for voting. Nevertheless, note that it is necessary to deposit $AXON to make a proposal and therefore not necessarily need to be a Delegator. +DAO Participants can only be delegators or Validators for voting. Nevertheless, note that it is necessary to deposit $AXONE to make a proposal and therefore not necessarily need to be a Delegator. ## Dataverse & Zone Participants diff --git a/docs/whitepaper/token-model.mdx b/docs/whitepaper/token-model.mdx index 3773aa7cf5c..69c66576dc9 100644 --- a/docs/whitepaper/token-model.mdx +++ b/docs/whitepaper/token-model.mdx @@ -28,7 +28,7 @@ The AXON Token Model aims to: One issue we've seen with many other layer-1 chains is that to secure the network, they define a high inflation parameter resulting in token selling pressure and unattractive price action. While this is not bad *per se* for the holders who stake, the reflective nature of crypto assets is further exagerated to the downside when inflation is high during market downturns. -One way to secure the network while limiting inflation is by providing rewards derived from network activity. Unlike Ethereum's [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), which reduces inflation through fee burning, Axone introduces a tax on value-creating network activity: the workflows. As with VAT (value-added tax), a fraction of the workflow's price can be collected to secure the network while reducing selling pressure and even resulting in long-term $AXON supply reduction. +One way to secure the network while limiting inflation is by providing rewards derived from network activity. Unlike Ethereum's [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), which reduces inflation through fee burning, Axone introduces a tax on value-creating network activity: the workflows. As with VAT (value-added tax), a fraction of the workflow's price can be collected to secure the network while reducing selling pressure and even resulting in long-term $AXONE supply reduction. The two opposite forces that influence the AXON token supply are (1) the bonded ratio ($\rho_{\text{bonded}}$) which influences the inflation rate ($r_{\text{inflation}}$), and (2) the workflow tax which burns tokens. diff --git a/docs/whitepaper/use-cases.md b/docs/whitepaper/use-cases.md index 3fde8daab93..0788fc9dc75 100644 --- a/docs/whitepaper/use-cases.md +++ b/docs/whitepaper/use-cases.md @@ -98,12 +98,12 @@ Two companies (Corp A and Corp B) grant access to their databases, while a third The Axone solution orchestrates the training process without exposing raw data, ensuring privacy, sovereignty and security. Moreover, the protocol provides revenue-sharing conditions and immutable records of the ML model's training sources. 1. Each on their own, Corp A and Corp B indicate through an administration portal the underlying technology of their respective database. They store access tokens with a Secret Management Service, with authorization for orchestration service. -2. Corp A and Corp define the rules, with access restrictions and payment conditions (a fixed $AXON fee per request, for example). They inform a maximum of metadata, especially to describe the different available datasets, their structures and the nature of their contents. +2. Corp A and Corp define the rules, with access restrictions and payment conditions (a fixed $AXONE fee per request, for example). They inform a maximum of metadata, especially to describe the different available datasets, their structures and the nature of their contents. 3. Metadata indicates that resources shared by Corp A and Corp B are compatible with an ML job from Corp C. Corp C submitted its training model algorithm, governance rules, and service execution instructions. 4. Individual D parameters its cloud environment, setting up how an orchestration service should store the execution request results. -5. Individual D requests service execution with the ML Workflow from Corp C, using data from Corp A and Corp B. He submits a transaction with a Keplr wallet and pays with $AXON tokens. The blockchain validates the execution request (access and execution authorizations). +5. Individual D requests service execution with the ML Workflow from Corp C, using data from Corp A and Corp B. He submits a transaction with a Keplr wallet and pays with $AXONE tokens. The blockchain validates the execution request (access and execution authorizations). 6. The orchestration service listens to the event from the blockchain. It recovers access keys and then executes the workflow training algorithm from Corp C, using Corp A & Corp B data it fetches. -7. The orchestration service tracks the progress and state changes of all jobs within the workflow and reports this information to the blockchain. If all works well, service agreement rules are applied, and $AXON tokens from Individual D are unlocked to Corp A, Corp B, et Corp C. +7. The orchestration service tracks the progress and state changes of all jobs within the workflow and reports this information to the blockchain. If all works well, service agreement rules are applied, and $AXONE tokens from Individual D are unlocked to Corp A, Corp B, et Corp C. 8. The orchestration service stores the result in the provided Individual D's storage solution. Optionally, this new knowledge can also be referenced as a data source for other workflows. Individual D can have access to the newly generated knowledge. ### And tomorrow? From 64844036c45e40f77c174d7e56aa064cc73618ab Mon Sep 17 00:00:00 2001 From: Marine DECHAMP-GUILLAUME <92780073+MdechampG@users.noreply.github.com> Date: Tue, 2 Apr 2024 10:11:26 +0200 Subject: [PATCH 2/2] feat: update ticker AXONE 2 --- docs/tutorials/cli-1.mdx | 6 +++--- docs/whitepaper/token-model.mdx | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/tutorials/cli-1.mdx b/docs/tutorials/cli-1.mdx index 6a22c621f68..363ecd3f83e 100644 --- a/docs/tutorials/cli-1.mdx +++ b/docs/tutorials/cli-1.mdx @@ -117,7 +117,7 @@ Here the terminal returns `okp41cu9wzlcyyxpek20jaqfwzu3llzjgx34cwnv2v5` as the A A wallet balance refers to the amount of cryptocurrency or digital assets held in a specific wallet address. It represents the total value of funds that are available for spending or transferring from that particular wallet. -The following command indicates that `okp41cu9wzlcyyxpek20jaqfwzu3llzjgx34cwnv2v5` Axone wallet holds 1 AXON (1 AXON = 1,000,000 uAXON). +The following command indicates that `okp41cu9wzlcyyxpek20jaqfwzu3llzjgx34cwnv2v5` Axone wallet holds 1 $AXONE (1 $AXONE = 1,000,000 uAXON). ```bash okp4d query bank balances okp41cu9wzlcyyxpek20jaqfwzu3llzjgx34cwnv2v5 \ @@ -150,11 +150,11 @@ okp4d query bank total \ ### Send some $AXONE to another wallet -Here is the command to send 0.5 AXON (`500000 uAXON`) from the wallet `mywallet` you control to the wallet with the Axone address `okp41r0pf2d78w8w29sm9a6qm8x6yqshezm0k6vwcrg`: +Here is the command to send 0.5 $AXONE (`500000 $uAXONE`) from the wallet `mywallet` you control to the wallet with the Axone address `okp41r0pf2d78w8w29sm9a6qm8x6yqshezm0k6vwcrg`: ```bash okp4d tx bank send mywallet okp41r0pf2d78w8w29sm9a6qm8x6yqshezm0k6vwcrg \ -500000uAXON \ +500000 $uAXONE \ --chain-id okp4-nemeton-1 --node https://api.testnet.okp4.network:443/rpc ``` diff --git a/docs/whitepaper/token-model.mdx b/docs/whitepaper/token-model.mdx index 69c66576dc9..e4ed63c7f7d 100644 --- a/docs/whitepaper/token-model.mdx +++ b/docs/whitepaper/token-model.mdx @@ -19,7 +19,7 @@ export const nPercentFormat = new Intl.NumberFormat('en', { ## Motivation -The AXON Token Model aims to: +The AXONE Token Model aims to: - secure the network by providing sufficient incentives for validators to participate and delegators to stake their tokens; - ensure low-cost participation for Providers and Consumers; @@ -30,7 +30,7 @@ One issue we've seen with many other layer-1 chains is that to secure the networ One way to secure the network while limiting inflation is by providing rewards derived from network activity. Unlike Ethereum's [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), which reduces inflation through fee burning, Axone introduces a tax on value-creating network activity: the workflows. As with VAT (value-added tax), a fraction of the workflow's price can be collected to secure the network while reducing selling pressure and even resulting in long-term $AXONE supply reduction. -The two opposite forces that influence the AXON token supply are (1) the bonded ratio ($\rho_{\text{bonded}}$) which influences the inflation rate ($r_{\text{inflation}}$), and (2) the workflow tax which burns tokens. +The two opposite forces that influence the AXONE token supply are (1) the bonded ratio ($\rho_{\text{bonded}}$) which influences the inflation rate ($r_{\text{inflation}}$), and (2) the workflow tax which burns tokens. ## Mint @@ -64,10 +64,10 @@ The yearly inflation rate described above doesn't take into consideration the bu ### Workflow tax -For each workflow, whatever the application, consumers pay providers according to the business model defined on-chain. A tax is applied to the workflow's price. The tax percentage is a parameter defined by governance. When AXON tokens are used by consumers, the tax is automatically burnt. +For each workflow, whatever the application, consumers pay providers according to the business model defined on-chain. A tax is applied to the workflow's price. The tax percentage is a parameter defined by governance. When AXONE tokens are used by consumers, the tax is automatically burnt. This tax compensates for inflation. The higher the tax collected on workflows, the lower the overall inflation rate. Another indirect effect of that tax is to prevent fake volume on datasets and services, making volume a more robust reputation metric. ### Other payment tokens -Depending on the business model of the zone and of the invoked resources, consumers can pay for workflows using other `cw-20` tokens, such as stablecoins like USDC. While providers will be paid with that payment token, and the same workflow tax will still apply. These payment tokens, instead of being immediately burnt, will be collected into a multisig pool, before getting used to buyback and burn AXON tokens, using the best route for optimal liquidity. This creates additional buying pressure on the token, while also decreasing the overall supply. +Depending on the business model of the zone and of the invoked resources, consumers can pay for workflows using other `cw-20` tokens, such as stablecoins like USDC. While providers will be paid with that payment token, and the same workflow tax will still apply. These payment tokens, instead of being immediately burnt, will be collected into a multisig pool, before getting used to buyback and burn AXONE tokens, using the best route for optimal liquidity. This creates additional buying pressure on the token, while also decreasing the overall supply.