diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 90544830e..ebdb8053e 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -1,65 +1,51 @@ -name: docs +name: Deploy to GitHub Pages on: - pull_request: - branches: [main] push: - branches: [main] + branches: + - main + # Review gh actions docs if you want to further define triggers, paths, etc + # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on jobs: - checks: - if: github.event_name != 'push' + build: + name: Build Docusaurus runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 - - uses: actions/setup-node@v2 + - uses: actions/checkout@v4 with: - node-version: '19.x' - - name: Test Build - run: | - if [ -e yarn.lock ]; then - npm install yarn -g - yarn install --frozen-lockfile - elif [ -e package-lock.json ]; then - npm ci - else - npm i - fi - npm run build - gh-release: - if: github.event_name != 'pull_request' + fetch-depth: 0 + - uses: actions/setup-node@v4 + with: + node-version: 18 + cache: yarn + + - name: Install dependencies + run: yarn install --frozen-lockfile + - name: Build website + run: yarn build + + - name: Upload Build Artifact + uses: actions/upload-pages-artifact@v3 + with: + path: build + + deploy: + name: Deploy to GitHub Pages + needs: build + + # Grant GITHUB_TOKEN the permissions required to make a Pages deployment + permissions: + pages: write # to deploy to Pages + id-token: write # to verify the deployment originates from an appropriate source + + # Deploy to the github-pages environment + environment: + name: github-pages + url: ${{ steps.deployment.outputs.page_url }} + runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 - - uses: actions/setup-node@v2 - with: - node-version: '19.x' - - name: Add key to allow access to repository - env: - SSH_AUTH_SOCK: /tmp/ssh_agent.sock - run: | - mkdir -p ~/.ssh - ssh-keyscan github.com >> ~/.ssh/known_hosts - echo "${{ secrets.GH_PAGES_DEPLOY }}" > ~/.ssh/id_rsa - chmod 600 ~/.ssh/id_rsa - cat <> ~/.ssh/config - Host github.com - HostName github.com - IdentityFile ~/.ssh/id_rsa - EOT - - name: Release to GitHub Pages - env: - USE_SSH: true - GIT_USER: git - run: | - git config --global user.email "actions@gihub.com" - git config --global user.name "gh-actions" - if [ -e yarn.lock ]; then - npm install yarn -g - yarn install --frozen-lockfile - elif [ -e package-lock.json ]; then - npm ci - else - npm i - fi - npx docusaurus deploy + - name: Deploy to GitHub Pages + id: deployment + uses: actions/deploy-pages@v4 diff --git a/README.md b/README.md index b9d18be4d..310c4a157 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# HydraDX-docs +# Hydration-docs ## Installation diff --git a/docs/bonds.md b/docs/bonds.md index 458daf397..aacb35b82 100644 --- a/docs/bonds.md +++ b/docs/bonds.md @@ -5,9 +5,9 @@ title: Bonds import useBaseUrl from '@docusaurus/useBaseUrl'; -The HydraDX Protocol uses **Bonds** as part of its strategy to **grow and diversify its Protocol-owned liquidity (POL)**. For this purpose, the HydraDX Governance can at any time decide to **issue a given amount of bonds** which will be traded against assets that the HydraDX Treasury wishes to accumulate. +The Hydration Protocol uses **Bonds** as part of its strategy to **grow and diversify its Protocol-owned liquidity (POL)**. For this purpose, the Hydration Governance can at any time decide to **issue a given amount of bonds** which will be traded against assets that the Hydration Treasury wishes to accumulate. -All HDX bonds have a **maturity date**, which marks the moment when the bond can be **swapped against the underlying asset (HDX)**. The HydraDX Protocol can decide the manner in which bonds are sold: For example, it can host a **dynamically priced LBP event**, or simply place an **OTC order against a fixed price**. Once acquired, bonds are **transferrable and tradeable on the secondary market** (e.g. OTC), also before they have reached maturity. +All HDX bonds have a **maturity date**, which marks the moment when the bond can be **swapped against the underlying asset (HDX)**. The Hydration Protocol can decide the manner in which bonds are sold: For example, it can host a **dynamically priced LBP event**, or simply place an **OTC order against a fixed price**. Once acquired, bonds are **transferrable and tradeable on the secondary market** (e.g. OTC), also before they have reached maturity. On this page you will find more info about bonds, including the process of a bonds campaign. For step-by-step guidance on how to participate in a bonds LBP, please visit [this guide](/howto_bonds_lbp). @@ -17,9 +17,9 @@ The concept of bonds was first pioneered by OlympusDAO in 2021 as a tool which w ## The Process of a Bonds Campaign -The first step of a Bonds campaign is the issuance of the bonds by the Protocol. Any member of the HydraDX Community can initiate a governance discussion and a referendum to issue a given amount of bonds with a predefined maturity date, in order to obtain a given asset as POL. +The first step of a Bonds campaign is the issuance of the bonds by the Protocol. Any member of the Hydration Community can initiate a governance discussion and a referendum to issue a given amount of bonds with a predefined maturity date, in order to obtain a given asset as POL. -Once bonds are issued, the HydraDX Governance must decide on the method of trade. One option is to host a dedicated LBP event, which limited in time and allows for dynamic pricing thanks to the interplay between time-based weights shifting and demand (more info in our [LBP docs](/lbp)). Another option is for the Protocol to place an OTC order against a predefined price per bond. +Once bonds are issued, the Hydration Governance must decide on the method of trade. One option is to host a dedicated LBP event, which limited in time and allows for dynamic pricing thanks to the interplay between time-based weights shifting and demand (more info in our [LBP docs](/lbp)). Another option is for the Protocol to place an OTC order against a predefined price per bond.
metadata diff --git a/docs/bridge_from_ethereum.md b/docs/bridge_from_ethereum.md index 635882db7..f1871f41c 100644 --- a/docs/bridge_from_ethereum.md +++ b/docs/bridge_from_ethereum.md @@ -7,9 +7,9 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; Bridging assets from the Ethereum ecosystem is easy using the [Wormhole](https://wormhole.com/) bridge which is implemented by the [Moonbeam network](https://moonbeam.network/). -When bridging an asset, Wormhole will lock it on the source network and mint an equivalent amount of Wormhole-wrapped assets on the Moonbeam network. The assets are then transferred to the HydraDX chain where they can be used for trading. In a few clicks and seamlessly. +When bridging an asset, Wormhole will lock it on the source network and mint an equivalent amount of Wormhole-wrapped assets on the Moonbeam network. The assets are then transferred to the Hydration chain where they can be used for trading. In a few clicks and seamlessly. -To bridge assets from Ethereum to HydraDX, follow the steps below. +To bridge assets from Ethereum to Hydration, follow the steps below. ### Prerequisites @@ -19,14 +19,14 @@ To bridge assets from Ethereum to HydraDX, follow the steps below. ### Step-by-step 1. Navigate to the [Carrier UI](https://www.carrier.so/) -2. As Destination, select `HydraDX` +2. As Destination, select `Hydration` 3. Connect your Ethereum wallet -4. Connect your HydraDX wallet +4. Connect your Hydration wallet 5. Select the asset you wish to bridge and the amount 6. Click on `Settings` and turn on `Auto Relay` 7. Confirm and sign the transaction -Once finalized, the assets will appear in your HydraDX wallet. +Once finalized, the assets will appear in your Hydration wallet.
metadata diff --git a/docs/build_dev_chain.md b/docs/build_dev_chain.md index 46539e6ac..a59faedbf 100644 --- a/docs/build_dev_chain.md +++ b/docs/build_dev_chain.md @@ -5,11 +5,11 @@ title: Set up a Development Chain import useBaseUrl from '@docusaurus/useBaseUrl'; -This section runs you through the process of setting up a local HydraDX chain instance for development. +This section runs you through the process of setting up a local Hydration chain instance for development. ## 01 Install dependencies {#01-install-dependencies} -To prepare a local HydraDX chain instance for development, your machine needs to cover all dependencies for running a Substrate chain. You will need to install a Rust developer environment and make sure that it is configured properly for compiling Substrate runtime code to the WebAssembly (Wasm) target. +To prepare a local Hydration chain instance for development, your machine needs to cover all dependencies for running a Substrate chain. You will need to install a Rust developer environment and make sure that it is configured properly for compiling Substrate runtime code to the WebAssembly (Wasm) target. You can install and configure all dependencies manually following the [Substrate guide](https://substrate.dev/docs/en/knowledgebase/getting-started), or you could let this script do all the work for you: @@ -52,7 +52,7 @@ $ RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/hydra-dx -lruntime=debug --de ## 04 Connect to your local chain instance {#04-connect-to-your-local-chain-instance} -You can connect to your HydraDX development node using Polkadot/apps and changing network to `Development`. You can also use this link: +You can connect to your Hydration development node using Polkadot/apps and changing network to `Development`. You can also use this link: https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/explorer connect to node diff --git a/docs/claim.md b/docs/claim.md index 05141ce08..6e47806d5 100644 --- a/docs/claim.md +++ b/docs/claim.md @@ -17,13 +17,13 @@ If your xHDX tokens are stored in Coinbase Wallet or Trust Wallet, you will need ## Claim process {#claim-process} -After making sure that you have fulfilled the prerequisites described above, you can navigate to the [HydraDX Claim app](https://claim.hydradx.io) and proceed with the claim process. +After making sure that you have fulfilled the prerequisites described above, you can navigate to the [Hydration Claim app](https://claim.hydradx.io) and proceed with the claim process. During the claim process, you will use your xHDX tokens (ERC-20) to claim your share of HDX tokens. ### 00 Authorize {#00-authorize} -The HydraDX Claim app will request authorization from the Polkadot.js browser extension. +The Hydration Claim app will request authorization from the Polkadot.js browser extension. :::warning @@ -33,7 +33,7 @@ Make sure that you are not the victim of a phishing attack and pay attention to authorize -After authorizing, you will be prompted to update the metadata for the Polkadot.js browser extension. This will allow Polkadot.js to create HydraDX-specific addresses which are required to complete the claim process. +After authorizing, you will be prompted to update the metadata for the Polkadot.js browser extension. This will allow Polkadot.js to create Hydration-specific addresses which are required to complete the claim process. authorize @@ -55,7 +55,7 @@ You are not eligible for a gas refund if you have obtained your xHDX at some oth In the second step, you will be asked to select your HDX address. -To create a new HDX address, open the Polkadot.js browser extension and click on the + sign to create a new account. In the first step of account creation, you will see the 12-word mnemonic phrase which can be used to recover your account. After saving your seed phrase in a secure place, click on *Next step*. Here, you should change the **Network** by selecting the option **HydraDX Snakenet**. Enter a name and password for your account, and finish the account creation. +To create a new HDX address, open the Polkadot.js browser extension and click on the + sign to create a new account. In the first step of account creation, you will see the 12-word mnemonic phrase which can be used to recover your account. After saving your seed phrase in a secure place, click on *Next step*. Here, you should change the **Network** by selecting the option **Hydration**. Enter a name and password for your account, and finish the account creation. authorize @@ -65,13 +65,13 @@ Make sure that you back up your recovery seed phrase by storing it in a safe pla ::: -After creating your HDX account, you should be able to select it in the HydraDX Claim app. After doing so, the app should provide you with an overview of the ETH and HDX addresses used for the claim process. Click on next to proceed to signing the message. +After creating your HDX account, you should be able to select it in the Claim app. After doing so, the app should provide you with an overview of the ETH and HDX addresses used for the claim process. Click on next to proceed to signing the message. authorize ### 03 Sign {#03-sign} -In the third step of the claim process using the HydraDX Claim app, you will be provided with the option to sign the message for using your xHDX tokens to claim HDX. +In the third step of the claim process using the Claim app, you will be provided with the option to sign the message for using your xHDX tokens to claim HDX. :::note @@ -83,7 +83,7 @@ Depending on the choice you have made in the first step, you have two options to * If you are using **Metamask**, after clicking the *Sign* button you will be prompted by Metamask to sign the message. Follow the instructions in Metamask. -* If you have entered your ETH address manually, you will need to sign the message through the external wallet that holds the private keys of your xHDX tokens. Once you have signed the message, copy the signature (starting with *0x*) to the respective field in the HydraDX Claim app. +* If you have entered your ETH address manually, you will need to sign the message through the external wallet that holds the private keys of your xHDX tokens. Once you have signed the message, copy the signature (starting with *0x*) to the respective field in the Claim app. authorize @@ -95,4 +95,4 @@ After signing the message with the wallet holding your xHDX tokens, the Polkadot You have now completed the claim process, thereby officially becoming an HDX owner! -You can check your balance using Polkadot/apps connected to the HydraDX network: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts +You can check your balance using Polkadot/apps connected to the Hydration network: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts diff --git a/docs/collator_setup.md b/docs/collator_setup.md index a742bc29f..f469ffb93 100644 --- a/docs/collator_setup.md +++ b/docs/collator_setup.md @@ -5,11 +5,11 @@ title: Set up a Collator Node import useBaseUrl from '@docusaurus/useBaseUrl'; -This is a step-by-step how-to so you can get your HydraDX collator up and running. In this guide, we use Ubuntu 20.04 LTS. +This is a step-by-step how-to so you can get your Hydration collator up and running. In this guide, we use Ubuntu 20.04 LTS. ## Required technical specifications {#technical-specifications} -The following technical specifications are required as a minimum for running a HydraDX collator node: +The following technical specifications are required as a minimum for running a Hydration collator node: * OS: Ubuntu 20.04 * CPU: Intel Core i7-7700K @ 4.5Ghz (or equivalent single core performance) @@ -85,7 +85,7 @@ chown hydra:hydra /var/lib/hydradx Make sure you have enough volume for your `base-path` by using `df -h` command. ::: -Note that `--prometheus-external` is optional, but we highly recommend it so you can be able to export prometheus metrics and monitor your node's health through Grafana. For more details about monitoring, please visit [this link](https://docs.hydradx.io/node_monitoring/). +Note that `--prometheus-external` is optional, but we highly recommend it so you can be able to export prometheus metrics and monitor your node's health through Grafana. For more details about monitoring, please visit [this link](https://docs.hydration.net/node_monitoring/). If you need to monitor both the `parachain` and `relaychain` metrics, `--prometheus-external`option should be setup in both parts. You also need to set a separate port for the relaychain part as follows: `--prometheus-port YOUR_CUSTOM_PORT_NUMBER` @@ -122,7 +122,7 @@ Once done, you will have an output similar to: ## Set your session key -To associate the generated session keys with your Controller account, navigate to the following menu item in the [Polkadot/apps](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics) on the Polkadot parachain HydraDX: *Developer* > *Extrinsics*. +To associate the generated session keys with your Controller account, navigate to the following menu item in the [Polkadot/apps](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics) on the Polkadot parachain Hydration: *Developer* > *Extrinsics*. Fill in the fields: diff --git a/docs/create_account.md b/docs/create_account.md index a1b0da2fa..3c272679e 100644 --- a/docs/create_account.md +++ b/docs/create_account.md @@ -23,7 +23,7 @@ To create a new HDX address, open the Polkadot.js browser extension and click on You will be displayed a 12-word mnemonic phrase which can be used to recover your account. Make sure that you backup your seed phrase in a secure location. Click on `Next step` and fill in the following information: -* **Network**: Please select `HydraDX Snakenet` +* **Network**: Please select `Hydration` * **Descriptive name of the account** * **Password** diff --git a/docs/democracy_council.md b/docs/democracy_council.md index 034370285..41eb6e5de 100644 --- a/docs/democracy_council.md +++ b/docs/democracy_council.md @@ -1,30 +1,30 @@ --- id: democracy_council -title: HydraDX Council +title: Hydration Council --- -The HydraDX Council is an on-chain entity which plays a key role in the governance of the protocol. This article provides information on the [composition](#composition) of the Council, its [main tasks](#tasks), and the [election of Council members](#elections). +The Hydration Council is an on-chain entity which plays a key role in the governance of the protocol. This article provides information on the [composition](#composition) of the Council, its [main tasks](#tasks), and the [election of Council members](#elections). For step-by-step guidance on how to participate in Council elections, please refer to [this guide](/participate_in_council_elections). ## Composition {#composition} -The HydraDX Council currently consists of **13 members**. +The Hydration Council currently consists of **13 members**. A minority share of 6 seats is reserved for the founding team and the investors (4 founders + 2 investors). The remaining 7 seats are elected by the wider community of HDX holders. ## Tasks and Responsibilities {#tasks} -The tasks of the HydraDX Council cover a wide range of day-to-day governance activities. To begin with, the Council controls the Treasury and approves or rejects Treasury proposals. +The tasks of the Hydration Council cover a wide range of day-to-day governance activities. To begin with, the Council controls the Treasury and approves or rejects Treasury proposals. -The HydraDX Council also plays a role in the referendum mechanism. The Council can initiate a referendum, provided that at least 60% of the members support this (super-majority) and no member exercises a veto. In the case of a veto, the proposal can be resubmitted after the cool-down period has lapsed. The vetoing member cannot veto the same proposal twice. +The Hydration Council also plays a role in the referendum mechanism. The Council can initiate a referendum, provided that at least 60% of the members support this (super-majority) and no member exercises a veto. In the case of a veto, the proposal can be resubmitted after the cool-down period has lapsed. The vetoing member cannot veto the same proposal twice. Furthermore, any proposed referendum can be cancelled with a 2/3 super-majority of the Council votes. This can be used as a last-resort measure to stop malicious proposals or changes which could introduce bugs in the code. -Finally, the HydraDX Council is responsible for electing the Technical Committee. +Finally, the Hydration Council is responsible for electing the Technical Committee. ## Elections {#elections} -Any holder of HDX tokens can [apply](/participate_in_council_elections) for one of the 7 non-permanent sets of the HydraDX Council as a candidate. +Any holder of HDX tokens can [apply](/participate_in_council_elections) for one of the 7 non-permanent sets of the Hydration Council as a candidate. The Council elections take place every 7 days, at which point an algorithm fills the 7 non-permanent Council seats for the duration of the following 7 days. The democracy module uses the same Phragmen algorithm which is used to elect the active set of validators on the Polkadot Relay Chain. diff --git a/docs/democracy_intro.md b/docs/democracy_intro.md index 7bf2d6487..5e7b68493 100644 --- a/docs/democracy_intro.md +++ b/docs/democracy_intro.md @@ -3,14 +3,14 @@ id: democracy_intro title: Introduction --- -HydraDX is in the process of fully decentralizing its governance. All decisions which affect the protocol are adopted following a democratic process which is supported by the Substrate democracy module. The central mechanism for establishing consensus among the stakeholders is the **referendum**. +Hydration is in the process of fully decentralizing its governance. All decisions which affect the protocol are adopted following a democratic process which is supported by the Substrate democracy module. The central mechanism for establishing consensus among the stakeholders is the **referendum**. -This section contains a series of knowledge articles which should provide you with a better understanding of the mechanisms behind the governance of HydraDX. You will find more information on [how referenda work](/democracy_referenda), as well as on the two central groups of governance actors: the [HydraDX Council](/democracy_council) and the [Technical Committee](/democracy_technical_committee). +This section contains a series of knowledge articles which should provide you with a better understanding of the mechanisms behind the governance of Hydration. You will find more information on [how referenda work](/democracy_referenda), as well as on the two central groups of governance actors: the [Hydration Council](/democracy_council) and the [Technical Committee](/democracy_technical_committee). -If you are looking for practical guidance on how to participate in the governance of HydraDX, please refer to the step-by-step guides on [participating in referenda](/participate_in_referenda) and [participating in Council elections](/participate_in_council_elections). +If you are looking for practical guidance on how to participate in the governance of Hydration, please refer to the step-by-step guides on [participating in referenda](/participate_in_referenda) and [participating in Council elections](/participate_in_council_elections). ## Democracy parameters -The list below contains the most important parameters which influence the governance mechanism on HydraDX. Please note that these may change over time. +The list below contains the most important parameters which influence the governance mechanism on Hydration. Please note that these may change over time. * Minimum HDX deposit for initiating a referendum: **10 000 HDX** diff --git a/docs/democracy_referenda.md b/docs/democracy_referenda.md index 56742e394..1aed1b991 100644 --- a/docs/democracy_referenda.md +++ b/docs/democracy_referenda.md @@ -22,16 +22,16 @@ All HDX tokens which are deposited to propose or second a referendum are locked ::: ### Council Referendum {#referenda-initiate-council} -The HydraDX Council has the powers to propose a referendum for a community vote. If it does so unanimously, the applicable voting mode for the referendum is [Negative Turnout Bias](#referenda-voting-modes). If the referendum is proposed with a simple majority of the Council votes, then the voting mode for accepting the proposals by the community is [Simple Majority](#referenda-voting-modes). +The Hydration Council has the powers to propose a referendum for a community vote. If it does so unanimously, the applicable voting mode for the referendum is [Negative Turnout Bias](#referenda-voting-modes). If the referendum is proposed with a simple majority of the Council votes, then the voting mode for accepting the proposals by the community is [Simple Majority](#referenda-voting-modes). ### Emergency Proposals by the Technical Committee {#referenda-initiate-tech-committee} The Technical Committee can submit emergency proposals which deal with (critical) bug fixes or the quick adoption of battle-tested functionality. Emergency proposals skip the waiting queue and enter the voting round directly. The community can vote on emergency proposals in parallel to any regular proposal which has entered the voting round. Furthermore, emergency proposals have a shorter voting period to ensure that they can be fast-tracked. ### Canceling a Referendum {#cancel} -Once a referendum has been proposed, it cannot be revoked until it has entered the voting round. An exception to this rule is made for proposals which are deemed detrimental to the protocol (e.g. code changes introducing a bug). In this limited case, the referendum proposal can be cancelled by the [HydraDX Council](/democracy_council) (with a 60% super-majority) or the [Technical Committee](/democracy_technical_committee) (unanimously). All tokens wich were locked by supporters seconding the proposal are burned. +Once a referendum has been proposed, it cannot be revoked until it has entered the voting round. An exception to this rule is made for proposals which are deemed detrimental to the protocol (e.g. code changes introducing a bug). In this limited case, the referendum proposal can be cancelled by the [Hydration Council](/democracy_council) (with a 60% super-majority) or the [Technical Committee](/democracy_technical_committee) (unanimously). All tokens wich were locked by supporters seconding the proposal are burned. ## Voting in a Referendum {#referenda-vote} -HydraDX referenda have a launch period of 3 days. At the beginning of every new period, the proposal with the highest amount of seconding is taken from the waiting queue and put into a voting round. Every voting round has a duration of 3 days. During this period, community members can vote on the referendum using a weighted, stake-base mechanism. They do so by locking up a certain amount of HDX tokens for a given timeframe. +Hydration referenda have a launch period of 3 days. At the beginning of every new period, the proposal with the highest amount of seconding is taken from the waiting queue and put into a voting round. Every voting round has a duration of 3 days. During this period, community members can vote on the referendum using a weighted, stake-base mechanism. They do so by locking up a certain amount of HDX tokens for a given timeframe. :::note Locked HDX tokens cannot be transferred for the duration of the chosen lock period. However, they can still be used for voting. diff --git a/docs/democracy_technical_committee.md b/docs/democracy_technical_committee.md index d6fd4a325..f78b1c250 100644 --- a/docs/democracy_technical_committee.md +++ b/docs/democracy_technical_committee.md @@ -3,7 +3,7 @@ id: democracy_technical_committee title: Technical Committee --- -The Technical Committee is a group of experienced core developers which is appointed directly by the HydraDX Council. Its main task is to safeguard the technical stability of the protocol. +The Technical Committee is a group of experienced core developers which is appointed directly by the Hydration Council. Its main task is to safeguard the technical stability of the protocol. The Technical Committee has the right to **produce emergency referenda** which are fast-tracked and voted in parallel with any other active referenda. This allows the Committee to act quickly and deliver critical (code) changes. diff --git a/docs/dev_intro.md b/docs/dev_intro.md index f87a8846f..458427d91 100644 --- a/docs/dev_intro.md +++ b/docs/dev_intro.md @@ -3,9 +3,9 @@ id: dev_intro title: Intro to Development --- -The purpose of the `Build` section of the HydraDX documentation is to share technical knowledge with the community and to empower individual contributions. HydraDX is a community-driven project which invests heavily in incentivizing community involvement, and we especially appreciate technical contributions! +The purpose of the `Build` section of the Hydration documentation is to share technical knowledge with the community and to empower individual contributions. Hydration is a community-driven project which invests heavily in incentivizing community involvement, and we especially appreciate technical contributions! -All technical contributions which are aligned with the goals of HydraDX are eligible for generous rewards which are paid out as Treasury tips in HDX. You can find more information about our reward scheme under the following links: +All technical contributions which are aligned with the goals of Hydration are eligible for generous rewards which are paid out as Treasury tips in HDX. You can find more information about our reward scheme under the following links: * [New Deal reward scheme announcement](https://hydradx.substack.com/p/incentivized-testnet-reward-scheme) * [Example tasks which brings rewards](/spending_fw) @@ -14,7 +14,7 @@ All technical contributions which are aligned with the goals of HydraDX are elig ## How to Start -HydraDX is powered by Substrate which is a cutting-edge blockchain framework built on Rust. Knowledge of Rust is therefore an important prerequisite for chain development. If you want to learn Rust, a good place to start is the ["Rust Book"](https://doc.rust-lang.org/stable/book/). +Hydration is powered by Substrate which is a cutting-edge blockchain framework built on Rust. Knowledge of Rust is therefore an important prerequisite for chain development. If you want to learn Rust, a good place to start is the ["Rust Book"](https://doc.rust-lang.org/stable/book/). A further requirement is basic knowledge of the Substrate framework. If you want to get up to speed quickly, we highly recommend you to subscribe to the [Acala Runtime Developer Academy](https://www.industryconnect.org/substrate-runtime-developer-academy/). diff --git a/docs/fees.md b/docs/fees.md index ceee228bb..ad582394b 100644 --- a/docs/fees.md +++ b/docs/fees.md @@ -5,7 +5,7 @@ title: Fees import useBaseUrl from '@docusaurus/useBaseUrl'; -The HydraDX Protocol charges users fees for its products. Some of these fees go to the HydraDX Treasury, while others are distributed as rewards to Liquidity Providers (LPs), stakers, referrers or trades. In some cases, fees in HDX may be even burned. +The Hydration Protocol charges users fees for its products. Some of these fees go to the Hydration Treasury, while others are distributed as rewards to Liquidity Providers (LPs), stakers, referrers or trades. In some cases, fees in HDX may be even burned. Here is an overview of all fees: @@ -23,16 +23,16 @@ Here is an overview of all fees: | OTC | Trade fee | 0% | Currently there are no fees on OTC trades | | ## Transaction fee -To submit any transaction on the HydraDX network (e.g. trade an asset, transfer tokens, submit a governance vote), users must pay a **transaction fee.** In Ethereum, this is commonly referred to as **gas**. +To submit any transaction on the Hydration network (e.g. trade an asset, transfer tokens, submit a governance vote), users must pay a **transaction fee.** In Ethereum, this is commonly referred to as **gas**. -On HydraDX, users are able to pay these transaction fees in **any Omnipool asset**. In order to reduce user friction, the Protocol will automatically set the first asset sent to HydraDX as the fee payment asset. This can be changed at any time on the wallet page of the app. +On Hydration, users are able to pay these transaction fees in **any Omnipool asset**. In order to reduce user friction, the Protocol will automatically set the first asset sent to Hydration as the fee payment asset. This can be changed at any time on the wallet page of the app. Note: If you are using **a 0x address with MetaMask**, it is currently only possible to pay for transaction fees in **WETH (MRL)**. ## Asset fee Asset fees are are paid by users whenever they make a trade in the Omnipool. These fees are charged in the asset that is “bought” from the Omnipool. Asset fees are dynamic, meaning that they can increase or decrease based on the current volatility of the traded assets. -With the introduction of **Referrals** to HydraDX, asset fees are distributed in the following way: +With the introduction of **Referrals** to Hydration, asset fees are distributed in the following way: - 50% remains in the Omnipool as a reward for LPs - 50% is distributed for referrals to 3 distinctive groups: Referrers, traders & HDX stakers. The proportions vary based on the tier of referral code linked to the trader account (learn more in [Referrals](/referrals)) diff --git a/docs/howto_bonds_lbp.md b/docs/howto_bonds_lbp.md index a726f0877..256f7e372 100644 --- a/docs/howto_bonds_lbp.md +++ b/docs/howto_bonds_lbp.md @@ -5,19 +5,19 @@ title: Acquire Bonds (LBP) import useBaseUrl from '@docusaurus/useBaseUrl'; -The HydraDX Protocol uses **Bonds** as part of its strategy to **grow and diversify its Protocol-owned liquidity (POL)**. For this purpose, the HydraDX Governance can at any time decide to **issue a given amount of bonds** which will be traded against assets that the HydraDX Treasury wishes to accumulate. +The Hydration Protocol uses **Bonds** as part of its strategy to **grow and diversify its Protocol-owned liquidity (POL)**. For this purpose, the Hydration Governance can at any time decide to **issue a given amount of bonds** which will be traded against assets that the Hydration Treasury wishes to accumulate. -This page contains a step-by-step guide on how to acquire Bonds via LBP on HydraDX. Before proceeding, we recommend that you get familiar with Bonds: https://docs.hydradx.io/bonds. +This page contains a step-by-step guide on how to acquire Bonds via LBP on Hydration. Before proceeding, we recommend that you get familiar with Bonds: https://docs.hydration.net/bonds.
metadata
-### Step 0: Navigate to HydraDX Bonds Page +### Step 0: Navigate to Hydration Bonds Page -https://app.hydradx.io/trade/bonds +https://app.hydration.net/trade/bonds -Connect your wallet to HydraDX by clicking **`Connect Account` (1 in image above).** +Connect your wallet to Hydration by clicking **`Connect Account` (1 in image above).** ### Step 1: Pick the Bond you want to support @@ -32,10 +32,10 @@ Connect your wallet to HydraDX by clicking **`Connect Account` (1 in image above :::caution Before participating in a Liquidity Bootstrapping Pool (LBP), you should first get familiar with how an LBP works. -Find more info [in our docs](https://docs.hydradx.io/lbp). +Find more info [in our docs](https://docs.hydration.net/lbp). ::: -The HydraDX Bonds LBP UI allows you to intuitively execute the swap: +The Hydration Bonds LBP UI allows you to intuitively execute the swap: - Select the token you intend to use and enter the amount **(4)**. - A price graph tracking the LBP price history and price trajectory (without any new trades) is provided for users to reference. diff --git a/docs/howto_dca.md b/docs/howto_dca.md index 2d2f81756..499e3787c 100644 --- a/docs/howto_dca.md +++ b/docs/howto_dca.md @@ -5,21 +5,21 @@ title: Place a DCA Order import useBaseUrl from '@docusaurus/useBaseUrl'; -On this page you will find a **step-by-step guide for setting up a DCA order** in the HydraDX Omnipool. +On this page you will find a **step-by-step guide for setting up a DCA order** in the Hydration Omnipool. -Before proceeding, we encourage you to visit our [DCA product page](/omnipool_dca) in order to get yourself familiar with the HydraDX implementation of the dollar-cost averaging strategy. +Before proceeding, we encourage you to visit our [DCA product page](/omnipool_dca) in order to get yourself familiar with the Hydration implementation of the dollar-cost averaging strategy.
-### Step 1: Navigate to HydraDX DCA Page +### Step 1: Navigate to Hydration DCA Page -https://app.hydradx.io/dca +https://app.hydration.net/dca ### Step 2: Connect to Your Account -Connect your wallet to HydraDX by clicking **`Connect Account` (1 in image above).** +Connect your wallet to Hydration by clicking **`Connect Account` (1 in image above).** ### Step 3: Set up DCA Order * Select the asset you will use to pay for the swap; Enter the order amount for each DCA trade, and the total order size **(2)**; diff --git a/docs/howto_hydrated_farms.md b/docs/howto_hydrated_farms.md index a01b13cec..3db64696b 100644 --- a/docs/howto_hydrated_farms.md +++ b/docs/howto_hydrated_farms.md @@ -7,7 +7,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; With Hydrated Farms, providing liquidity to selected assets is incentivized by additional rewards on top of rewards from trading fees. To learn more, please visit the [dedicated product page](/omnipool_hydrated_farms). ## 00 Navigate to Liquidity Page -[https://app.hydradx.io/liquidity](https://app.hydradx.io/liquidity) +[https://app.hydration.net/liquidity](https://app.hydration.net/liquidity) ## 01 Provide Liquidity Incentivized assets can be identified by the `Farm rewards` section which displays all available rewards for a given farm. diff --git a/docs/howto_lp.md b/docs/howto_lp.md index f80e6a865..4010253cc 100644 --- a/docs/howto_lp.md +++ b/docs/howto_lp.md @@ -5,21 +5,21 @@ title: Provide Liquidity import useBaseUrl from '@docusaurus/useBaseUrl'; -On this page you will find a **step-by-step guide for providing liquidity** in the HydraDX Omnipool. Becoming a liquidity provider allows you to **earn rewards** from the fees generated by trades in the pool. +On this page you will find a **step-by-step guide for providing liquidity** in the Hydration Omnipool. Becoming a liquidity provider allows you to **earn rewards** from the fees generated by trades in the pool. -Before deciding to become a liquidity provider, we encourage you to visit our [product page](/) and to **get yourself familiar** with the unique features of the HydraDX Omnipool. +Before deciding to become a liquidity provider, we encourage you to visit our [product page](/) and to **get yourself familiar** with the unique features of the Hydration Omnipool. ## 00 Transport tokens -If you would like to execute a trade using a non-native asset (e.g. DOT or DAI), you first need to get these assets to the HydraDX chain. This step does not apply to HDX. +If you would like to execute a trade using a non-native asset (e.g. DOT or DAI), you first need to get these assets to the Hydration chain. This step does not apply to HDX. There are two different mechanisms to transport non-native assets: -* [Cross-chain transfer](https://app.hydradx.io/#/cross-chain) - use this tool to transfer assets from other Polkadot parachains, or from Polkadot itself. Step-by-step documentation [here](howto_xcm); +* [Cross-chain transfer](https://app.hydration.net/#/cross-chain) - use this tool to transfer assets from other Polkadot parachains, or from Polkadot itself. Step-by-step documentation [here](howto_xcm); * [Ethereum bridge](https://www.portalbridge.com/#/transfer) - for bridging assets from the Ethereum ecosystem. Step-by-step documentation [here](/bridge_from_ethereum). -These solutions can also be used to transport tokens outside of the HydraDX network. +These solutions can also be used to transport tokens outside of the Hydration network. ## 01 Navigate to Omnipool Liquidity -[https://app.hydradx.io/#/liquidity](https://app.hydradx.io/#/liquidity) +[https://app.hydration.net/#/liquidity](https://app.hydration.net/#/liquidity)
metadata @@ -34,7 +34,7 @@ Click on `Connect wallet` **(1 in image above)** and connect to your preferred P To add liquidity for a given asset, click the button `Add liquidity` which is located right next to that asset **(3)**. :::important -In the HydraDX Omnipool, each individual asset has a Total Value Locked (TVL) cap. This means that once the cap has been reached, users can no longer further add liquidity for that specific asset. +In the Hydration Omnipool, each individual asset has a Total Value Locked (TVL) cap. This means that once the cap has been reached, users can no longer further add liquidity for that specific asset. The individual caps for each asset will be reviewed from time to time by the team; any suggested revisions (either from team or the community) will be submitted as proposals via governance and voted on. ::: diff --git a/docs/howto_stake.md b/docs/howto_stake.md index 6a99fb4f1..fc88a8053 100644 --- a/docs/howto_stake.md +++ b/docs/howto_stake.md @@ -7,13 +7,13 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; Staking allows users to stake their HDX tokens and earn rewards which vest over time. This page contains a step-by-step guide on how to stake your HDX. Before proceeding, we recommend that you get familiar with [the basics of HDX staking](/staking). -If you don't have any HDX, you can obtain some on our [trade page](https://app.hydradx.io/#/trade) by swapping against a range of assets supported by the Omnipool. +If you don't have any HDX, you can obtain some on our [trade page](https://app.hydration.net/#/trade) by swapping against a range of assets supported by the Omnipool. -### Step 0: Navigate to HydraDX Staking Page +### Step 0: Navigate to Hydration Staking Page -https://app.hydradx.io/staking +https://app.hydration.net/staking -Connect your wallet to HydraDX by clicking **`Connect Account`**. +Connect your wallet to Hydration by clicking **`Connect Account`**. ### Step 1: Stake Your HDX diff --git a/docs/howto_trade.md b/docs/howto_trade.md index 2fb69f719..5405a7e59 100644 --- a/docs/howto_trade.md +++ b/docs/howto_trade.md @@ -5,31 +5,31 @@ title: Trade in Omnipool import useBaseUrl from '@docusaurus/useBaseUrl'; -This page provides a **step-by-step guide** which will **help you execute your first trades** using the HydraDX Omnipool. +This page provides a **step-by-step guide** which will **help you execute your first trades** using the Hydration Omnipool. -The HydraDX Omnipool is a next-gen AMM which unlocks unparalleled efficiencies, you can find out more in our [product documentation](/). +The Hydration Omnipool is a next-gen AMM which unlocks unparalleled efficiencies, you can find out more in our [product documentation](/).
metadata
## 00 Transport tokens -If you would like to execute a trade using a non-native asset (e.g. DOT or DAI), you first need to get these assets to the HydraDX chain. This step does not apply to HDX. +If you would like to execute a trade using a non-native asset (e.g. DOT or DAI), you first need to get these assets to the Hydration chain. This step does not apply to HDX. There are two different mechanisms to transport non-native assets: -* [Cross-chain transfer](https://app.hydradx.io/cross-chain) - use this tool to transfer assets from other Polkadot parachains, or from Polkadot itself. Step-by-step documentation [here](howto_xcm); +* [Cross-chain transfer](https://app.hydration.net/cross-chain) - use this tool to transfer assets from other Polkadot parachains, or from Polkadot itself. Step-by-step documentation [here](howto_xcm); * [Ethereum bridge](https://www.portalbridge.com/#/transfer) - for bridging assets from the Ethereum ecosystem. Step-by-step documentation [here](/bridge_from_ethereum). -These solutions can also be used to transport tokens outside of the HydraDX network. +These solutions can also be used to transport tokens outside of the Hydration network. ## 01 Enter Omnipool -[https://app.hydradx.io/#/trade](https://app.hydradx.io/trade) +[https://app.hydration.net/#/trade](https://app.hydration.net/trade) ## 02 Connect Your Account Click on `Connect wallet` **(1 in image above)** and connect to your preferred Polkadot wallet. After that, select your account. ## 03 Execute a Trade -The HydraDX Trade UI allows you to intuitively execute a trade: +The Hydration Trade UI allows you to intuitively execute a trade: * Select the pair of tokens you intend to trade **(2)**; * Enter the amount of tokens for the trade **(3)**. diff --git a/docs/howto_wallet_parity_signer.md b/docs/howto_wallet_parity_signer.md index 6b049ab65..c83947358 100644 --- a/docs/howto_wallet_parity_signer.md +++ b/docs/howto_wallet_parity_signer.md @@ -87,11 +87,11 @@ To add your account, open the Polkadot.js browser extension, click on `+` and se * Select your desired account or sub-account; * You will see a QR code which you need to scan with your device camera. -### Add HydraDX Chain +### Add Hydration Chain To use Parity Signer, you first need to add a new chain to Parity Signer. If you want to use Parity only for Polkadot or Kusama, you can skip this step and proceed with updating metadata. To add a new chain, you need to scan a QR code with base information about the chain. #### 01 Get Chain Specs -On your Desktop, navigate to https://nova-wallet.github.io/metadata-portal/ and select HydraDX as the desired chain. After that, click on `Chain Specs`. +On your Desktop, navigate to https://nova-wallet.github.io/metadata-portal/ and select Hydration as the desired chain. After that, click on `Chain Specs`.
metadata diff --git a/docs/howto_xcm.md b/docs/howto_xcm.md index 24a6f398b..aa479815f 100644 --- a/docs/howto_xcm.md +++ b/docs/howto_xcm.md @@ -7,9 +7,9 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; On this page you will find a **step-by-step guide for performing cross-chain transfers**. -Cross-chain transfers allow you to transport non-native assets to the HydraDX chain from other Polkadot parachains, or from Polkadot itself. +Cross-chain transfers allow you to transport non-native assets to the Hydration chain from other Polkadot parachains, or from Polkadot itself. -Currently, the following tokens are supported by HydraDX for cross-chain transfers: +Currently, the following tokens are supported by Hydration for cross-chain transfers: * DOT * DAI (from Acala, bridged via Wormhole) * ETH (from Acala, bridged via Wormhole) @@ -19,7 +19,7 @@ Currently, the following tokens are supported by HydraDX for cross-chain transfe Before you continue, please make sure you have sufficient amount of tokens on the destination chain for fees (ACA or DOT). ## 01 Navigate to Cross-chain Transfers -[https://app.hydradx.io/#/cross-chain](https://app.hydradx.io/#/cross-chain) +[https://app.hydration.net/#/cross-chain](https://app.hydration.net/#/cross-chain)
metadata diff --git a/docs/identity.md b/docs/identity.md index e6965a160..7212faab6 100644 --- a/docs/identity.md +++ b/docs/identity.md @@ -5,15 +5,15 @@ title: Set your Identity import useBaseUrl from '@docusaurus/useBaseUrl'; -Account holders have the possibility to set their identity by prodiving specific information and storing it on-chain. Besides that, the identity information can optionally be submitted to the HydraDX registrars for verification. By setting and verifying their identity, validators and nominators help safeguard the trust in the network. +Account holders have the possibility to set their identity by prodiving specific information and storing it on-chain. Besides that, the identity information can optionally be submitted to the Hydration registrars for verification. By setting and verifying their identity, validators and nominators help safeguard the trust in the network. :::note -If you are participating as a HydraDX validator we **highly recommend** that you both set your identity and undergo the verification process. Verified validators appear more trustworthy and attract more nominations, thereby increasing their chances to be included in the set of active validators. +If you are participating as a Hydration validator we **highly recommend** that you both set your identity and undergo the verification process. Verified validators appear more trustworthy and attract more nominations, thereby increasing their chances to be included in the set of active validators. ::: ## 01 Set identity {#01-set-identity} -To set your identity, open Polkadot/apps (connected to *HydraDX Snakenet* network) and navigate to *My accounts*. Alternatively, you can follow this link: +To set your identity, open Polkadot/apps (connected to *Hydration Snakenet* network) and navigate to *My accounts*. Alternatively, you can follow this link: https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts @@ -45,12 +45,12 @@ After you have set your identity, you can submit it to the network registrars fo https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics -After selecting the relevant HydraDX account from the last step, you need to fill out the following information: +After selecting the relevant Hydration account from the last step, you need to fill out the following information: * **extrinsic**: identity * **action**: requestJudgement * **reg_index**: here you need to enter the ID of the registrar that you choose to carry out the verification. -HydraDX has 2 registrars: Simon Kraus - HydraSik (ID: **0**) and Jimmy Tudeski - stakenode (ID: **1**). +Hydration has 2 registrars: Simon Kraus - HydraSik (ID: **0**) and Jimmy Tudeski - stakenode (ID: **1**). * **max_fee**: here you need to enter the maximum fee in HDX that you are willing to pay to the registrar for the verification. Only registrars with a fee below your max_fee will be eligible to carry out the verification. To submit your verification request, click on *Submit Transaction* and sign the transaction. diff --git a/docs/intro.md b/docs/intro.md index 9b79dd75f..7a512e905 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -4,16 +4,16 @@ title: Meet Omnipool slug: / --- -HydraDX is a next-gen DeFi protocol which is designed to **bring an ocean of liquidity to Polkadot**. Our tool for the job the **HydraDX Omnipool** - an innovative Automated Market Maker (AMM) which **unlocks unparalleled efficiencies** by **combining all assets in a single trading pool**. +Hydration is a next-gen DeFi protocol which is designed to **bring an ocean of liquidity to Polkadot**. Our tool for the job the **Hydration Omnipool** - an innovative Automated Market Maker (AMM) which **unlocks unparalleled efficiencies** by **combining all assets in a single trading pool**. -By putting an **end to liquidity fragmentation**, the HydraDX Omnipool makes trading efficient like no other AMM. Thanks to **lower slippage and less hops**, traders can enjoy capital efficiency gains (which scale further with TVL) as compared to a typical situation where liquidity is fragmented across different trading pools ([learn more](/omnipool_trading)). +By putting an **end to liquidity fragmentation**, the Hydration Omnipool makes trading efficient like no other AMM. Thanks to **lower slippage and less hops**, traders can enjoy capital efficiency gains (which scale further with TVL) as compared to a typical situation where liquidity is fragmented across different trading pools ([learn more](/omnipool_trading)). -The design of the HydraDX Omnipool empowers **single-sided liquidity provisioning** - anyone can provide liquidity only for the asset they want, and the Omnipool will take care of the rest ([learn more](/omnipool_lp)). In the early phases of bootstrapping growth, providing liquidity for selected assets will be incentivized by **Hydrated Farms** - additional rewards on top rewards from trading fees which grow over time ([learn more](/omnipool_hydrated_farms)). +The design of the Hydration Omnipool empowers **single-sided liquidity provisioning** - anyone can provide liquidity only for the asset they want, and the Omnipool will take care of the rest ([learn more](/omnipool_lp)). In the early phases of bootstrapping growth, providing liquidity for selected assets will be incentivized by **Hydrated Farms** - additional rewards on top rewards from trading fees which grow over time ([learn more](/omnipool_hydrated_farms)). Single-sided LPing is an especially powerful concept for **treasuries of DAOs and other projects** who can supply their asset to the Omnipool - **trustlessly via XCM**, and gain **instant exposure to an ocean of assets**. Without hidden fees for market makers, **while building up (diversified) POL from trading fees** ([learn more](/omnipool_treasuries)). -The HydraDX Omnipool enjoys **state of the art security**: The underlying code has underwent **multiple audits**, and there is a **generous bug bounty program** incentivizing the **responsible disclosure of vulnerabilities**. Besides that, a combination of cutting-edge mechanisms such as liquidity caps, protocol fees and circuit breakers work together to keep your liquidity safe ([learn more](/omnipool_security)). +The Hydration Omnipool enjoys **state of the art security**: The underlying code has underwent **multiple audits**, and there is a **generous bug bounty program** incentivizing the **responsible disclosure of vulnerabilities**. Besides that, a combination of cutting-edge mechanisms such as liquidity caps, protocol fees and circuit breakers work together to keep your liquidity safe ([learn more](/omnipool_security)). -Building upon **2+ years of R&D**, HydraDX has found ways to address another pain point of AMMs - **impermanent loss (IL)**. Thanks to a **combination of non-inflationary measures**, liquidity providers will **experience less IL** when providing their liquidity to the Omnipool ([learn more](/omnipool_impermanent_loss)). +Building upon **2+ years of R&D**, Hydration has found ways to address another pain point of AMMs - **impermanent loss (IL)**. Thanks to a **combination of non-inflationary measures**, liquidity providers will **experience less IL** when providing their liquidity to the Omnipool ([learn more](/omnipool_impermanent_loss)). Stay hydrated, not liquidated. diff --git a/docs/lbp.md b/docs/lbp.md index 8675e5f76..be23ce61b 100644 --- a/docs/lbp.md +++ b/docs/lbp.md @@ -85,8 +85,8 @@ Initial price was not sniped and allowed to fall before the significant demand f lbp
-### Exhibit C: HydraDX LBP -Finally, you can take a look at our [analysis of the HydraDX LBP](https://hydradx.substack.com/p/lbp-analysis) back in February 2021 which helped HydraDX raise 22.9M DAI to become one of the most successful LBPs ever conducted. +### Exhibit C: Hydration LBP +Finally, you can take a look at our [analysis of the Hydration LBP](https://hydradx.substack.com/p/lbp-analysis) back in February 2021 which helped Hydration raise 22.9M DAI to become one of the most successful LBPs ever conducted.
lbp diff --git a/docs/learn_amm.md b/docs/learn_amm.md index f80a574ad..f0d257750 100644 --- a/docs/learn_amm.md +++ b/docs/learn_amm.md @@ -7,7 +7,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; This article provides an introduction to Automated Market Makers (AMMs) together with some of their underpinning concepts such as [slippage](#slippage), [liquidity provisioning](#lp) and [impermanent loss](#impermanent-loss). -This introductory information will help you understand better the mechanics behind the HydraDX Omnipool which you can find described in our [product documentation](/). +This introductory information will help you understand better the mechanics behind the Hydration Omnipool which you can find described in our [product documentation](/). ## A Short Intro into AMMs diff --git a/docs/node_monitoring.md b/docs/node_monitoring.md index 8129af621..107cd21e7 100644 --- a/docs/node_monitoring.md +++ b/docs/node_monitoring.md @@ -121,7 +121,7 @@ scrape_configs: - targets: ["localhost:9615"] ``` -The first scrape job exports data of Prometheus itself, the second one exports the HydraDX node metrics. +The first scrape job exports data of Prometheus itself, the second one exports the Hydration node metrics. We adjusted the `scrape_interval` of both jobs to get more detailed statistics. This overrides the global values. The `target` in `static_configs` sets where the exporters run, we stick to the default ports here. @@ -327,7 +327,7 @@ Please click the `Plus`-button in the main navigation and select `import`.
-We will use the [HydraDX Dashboard](https://grafana.com/grafana/dashboards/14158) layout, so simply input the id `14158` and hit the `Load`-button. +We will use the [Hydration Dashboard](https://grafana.com/grafana/dashboards/14158) layout, so simply input the id `14158` and hit the `Load`-button.
diff --git a/docs/omnipool_dca.md b/docs/omnipool_dca.md index 87d6e6813..b90209cce 100644 --- a/docs/omnipool_dca.md +++ b/docs/omnipool_dca.md @@ -5,21 +5,21 @@ title: DCA Trading import useBaseUrl from '@docusaurus/useBaseUrl'; -[HydraDX DCA](https://app.hydradx.io/dca) and [Split Trade](https://app.hydradx.io/trade) (easy DCA) are two user-friendly features which allow traders to implement the dollar-cost-averaging (DCA) strategy when trading in the Omnipool - in a permissionless and non-custodial way. +[Hydration DCA](https://app.hydration.net/dca) and [Split Trade](https://app.hydration.net/trade) (easy DCA) are two user-friendly features which allow traders to implement the dollar-cost-averaging (DCA) strategy when trading in the Omnipool - in a permissionless and non-custodial way. Following the DCA strategy, orders are not placed at once but instead split into smaller trades which are executed at regular intervals of time. By doing so, traders may protect themselves against price volatility and achieve an average price. Additionally, splitting a large order in smaller chunks will result in less slippage. -HydraDX has two DCA implementations - the [full DCA feature](#hydradx-dca), and [Split Trade](#split-trade) (easy DCA) which can be found on the main trading page. Further down, you can learn more about these features. +Hydration has two DCA implementations - the [full DCA feature](#hydration-dca), and [Split Trade](#split-trade) (easy DCA) which can be found on the main trading page. Further down, you can learn more about these features. If you are looking for step-by-step guidance, check out the [how-to place a DCA order guide](/howto_dca). -## HydraDX DCA {#hydradx-dca} +## Hydration DCA {#hydration-dca} -[HydraDX DCA](https://app.hydradx.io/dca) provides an intuitive UI which enables users to fine-tune their DCA orders in the Omnipool. +[Hydration DCA](https://app.hydration.net/dca) provides an intuitive UI which enables users to fine-tune their DCA orders in the Omnipool. When setting up their order, users specify the amount of Asset A they would like to spend in order to obtain Asset B, as well as the frequency of the trades - in hours (approximation) or number of blocks (more granularity). -After placing the order, the HydraDX DCA pallet makes sure that trades are scheduled at the specified intervals until the predetermined amount of Asset A has been spent. Placing multiple DCA orders which are executed in parallel is supported. +After placing the order, the Hydration DCA pallet makes sure that trades are scheduled at the specified intervals until the predetermined amount of Asset A has been spent. Placing multiple DCA orders which are executed in parallel is supported. Users can track the status of their orders on the UI. Open orders can at any time be terminated for the remaining amount. @@ -30,7 +30,7 @@ Users can track the status of their orders on the UI. Open orders can at any tim ## Split Trade (easy DCA) {#split-trade} -[Split Trade](https://app.hydradx.io/trade) is a more simple implementation of DCA directly into the main trade page. It provides users with a one-click solution for splitting larger orders in order to protect themselves from slippage. +[Split Trade](https://app.hydration.net/trade) is a more simple implementation of DCA directly into the main trade page. It provides users with a one-click solution for splitting larger orders in order to protect themselves from slippage. When activated, Split Trade will split the order in smaller chunks until the size of the trades is small enough to achieve less than 0.1% slippage (estimate only - the exact slippage for future trades can never be predicted in advance). diff --git a/docs/omnipool_design.md b/docs/omnipool_design.md index 06ec4c610..d1e1ae89c 100644 --- a/docs/omnipool_design.md +++ b/docs/omnipool_design.md @@ -5,7 +5,7 @@ title: Omnipool Design import useBaseUrl from '@docusaurus/useBaseUrl'; -The HydraDX Omnipool is a novel type of AMM which concentrates all liquidity in a single trading pool, thus unlocking +The Hydration Omnipool is a novel type of AMM which concentrates all liquidity in a single trading pool, thus unlocking an array of efficiencies. This doc contains a mathematical specification of the mechanics which power the Omnipool. ## The Omnipool diff --git a/docs/omnipool_hydrated_farms.md b/docs/omnipool_hydrated_farms.md index bdce300e4..27d7e630d 100644 --- a/docs/omnipool_hydrated_farms.md +++ b/docs/omnipool_hydrated_farms.md @@ -10,7 +10,7 @@ Departing from traditional liquidity mining programs, Hydrated Farms offer sever On this page you will find further details on the features of Hydrated Farms. If you would like to participate, please visit our [step-by-step guide on Hydrated Farms](/howto_hydrated_farms). ## Farm NFTs {#farm-nfts} -Whenever a user provides liquidity to the Omnipool and joins a Hydrated Farm, the HydraDX Protocol will mint an NFT which is owned by the user. This NFT represents the user position in the farm and stores certain details such as time of entry. This enables the Protocol to provide sustainable incentives with rewards which grow over time. +Whenever a user provides liquidity to the Omnipool and joins a Hydrated Farm, the Hydration Protocol will mint an NFT which is owned by the user. This NFT represents the user position in the farm and stores certain details such as time of entry. This enables the Protocol to provide sustainable incentives with rewards which grow over time. The owner of the farm NFT controls the position in the farm as well the underlying liquidity in the Omnipool. In the future, Protocol stakeholders may decide to open up a marketplace for Farm NFTs or enable their usage as collateral. @@ -21,7 +21,7 @@ Due to the unique properties of the Farm NFTs, joining a given farm multiple tim ## Rewards Stacking {#rewards-stacking} Hydrated Farms support the possibility to offer rewards in more than one asset. In other words, rewards are stackable. -Any team can reach out to the HydraDX stakeholders with the request to create a Hydrated Farm incentivized by their own TKN. Following this example, the HydraDX governance can decide to also provide HDX as incentives to that farm. As a result, hydrated farmers would receive both HDX and TKN rewards. +Any team can reach out to the Hydration stakeholders with the request to create a Hydrated Farm incentivized by their own TKN. Following this example, the Hydration governance can decide to also provide HDX as incentives to that farm. As a result, hydrated farmers would receive both HDX and TKN rewards. ## Loyalty Multiplier {#loyalty-multiplier} To encourage more sustainable liquidity provisioning, Hydrated Farms feature a loyalty multiplier - rewards grow over time as liquidity remains in the farm. You can view the exact curve for distributing rewards on the farm detail page. diff --git a/docs/omnipool_impermanent_loss.md b/docs/omnipool_impermanent_loss.md index 0dc6b765a..2ccae0fdc 100644 --- a/docs/omnipool_impermanent_loss.md +++ b/docs/omnipool_impermanent_loss.md @@ -5,7 +5,7 @@ title: Impermanent Loss import useBaseUrl from '@docusaurus/useBaseUrl'; -This page provides guidance which will help you understand how impermanent loss (IL) may affect Liquidity Providers (LPs) in the HydraDX Omnipool. +This page provides guidance which will help you understand how impermanent loss (IL) may affect Liquidity Providers (LPs) in the Hydration Omnipool. It begins with a brief introduction to the concept of impermanent loss, followed by a description of how Omnipool’s design interacts with IL. There are many factors which may influence the IL which any given LP suffers, and this makes it very difficult to make any reliable predictions. Keeping this disclaimer in mind, we have simulated some model scenarios which will help you get a better grasp of IL in the Omnipool. @@ -16,17 +16,17 @@ AMMs consist of multiple tokens (usually two) which are paired together in a liq The risk is referred to as "impermanent" because the loss is only realized when LPs withdraw their tokens from the pool. If the relative prices of tokens in the pool return to their original state when the tokens were deposited, the loss is minimized or eliminated. If, on the other hand, an LP decides to exit their position with IL, the loss becomes “permanent”. -## Design of the HydraDX Omnipool +## Design of the Hydration Omnipool -The HydraDX Omnipool, in its most basic form, can be thought of as a collection of XYK AMM pools in which each of the different TKN assets is paired with the hub token LRNA. This design lies at the core of one of our distinguishing features: Single-sided LPing, or the ability of LPs to provide liquidity for a single asset only. +The Hydration Omnipool, in its most basic form, can be thought of as a collection of XYK AMM pools in which each of the different TKN assets is paired with the hub token LRNA. This design lies at the core of one of our distinguishing features: Single-sided LPing, or the ability of LPs to provide liquidity for a single asset only. To enable single-sided LPing, the Protocol will automatically mint/burn a corresponding amount of LRNA tokens every time liquidity is provided/withdrawn. Since all tokens have a pair with the hub token, LRNA acts as a price proxy providing an efficient way to determine the relative value of any two given assets in the Omnipool. -## IL in the HydraDX Omnipool +## IL in the Hydration Omnipool The impermanent loss experienced by any TKN position in the Omnipool is determined by the divergence in value between TKN and LRNA. A stronger price correlation between TKN and LRNA suggests a smaller IL (and vice versa). -Since LRNA has a liquidity pair with all other tokens in the Omnipool, it can be seen as a weighted price index which reflects the aggregate movement of all different assets within the Omnipool. The [basket of Omnipool assets](https://app.hydradx.io/stats/overview) includes both stablecoins and other cryptocurrencies. +Since LRNA has a liquidity pair with all other tokens in the Omnipool, it can be seen as a weighted price index which reflects the aggregate movement of all different assets within the Omnipool. The [basket of Omnipool assets](https://app.hydration.net/stats/overview) includes both stablecoins and other cryptocurrencies. This design has important implications for IL. If TKN achieves a price movement which is aligned with the rest of the crypto market (e.g. with DOT or BTC), then the expected IL of TKN in the Omnipool shall be lower as compared to an XYK pool between TKN/stablecoin, however that same IL will be higher as compared to an isolated XYK pool between TKN/DOT (or BTC). @@ -97,14 +97,14 @@ In one of the examples above, LRNA is distributed to LPs to balance out IL. This Assuming the LP sells the LRNA obtained back into the Omnipool for an asset, this results in LRNA’s value to decrease which would affect all other liquidity positions within the Omnipool. -To mitigate the negative effects of the value depreciation of LRNA, the HydraDX Protocol has implemented the following mechanisms: +To mitigate the negative effects of the value depreciation of LRNA, the Hydration Protocol has implemented the following mechanisms: ### Fees In the first place, there are three types of fees which act as a safeguard. For more info please refer to our [fees](/fees) page. #### Protocol Fees -HydraDX charges Protocol fees upon every swap which are paid in LRNA. Whenever there is a negative LRNA imbalance, HydraDX will continually burn the Protocol fee until it has reached 2x the amount of any LRNA sold back into the Omnipool. +Hydration charges Protocol fees upon every swap which are paid in LRNA. Whenever there is a negative LRNA imbalance, Hydration will continually burn the Protocol fee until it has reached 2x the amount of any LRNA sold back into the Omnipool. #### Dynamic Fees during Increased Volatility Protocol fees are dynamic and adjusted based on the current market volatility. If prices in the Omnipool are volatile, each swap will incur higher Protocol fees which are potentially translated to a higher amount of LRNA which is burnt. @@ -115,10 +115,10 @@ Withdrawal fees are another type of dynamic fees which are designed to ensure th ### Protocol-Owned Liquidity -In the second place, HydraDX owns a substantial amount of Protocol-owned liquidity (POL). POL is held by the Protocol itself and it acts as the “liquidity of last resort”. It ensures that there is always a base level of liquidity within the Omnipool. As such, POL helps set a floor on how much the price of LRNA could decrease even if all 3rd-party LPs were to withdraw their liquidity from the Omnipool. +In the second place, Hydration owns a substantial amount of Protocol-owned liquidity (POL). POL is held by the Protocol itself and it acts as the “liquidity of last resort”. It ensures that there is always a base level of liquidity within the Omnipool. As such, POL helps set a floor on how much the price of LRNA could decrease even if all 3rd-party LPs were to withdraw their liquidity from the Omnipool. ### Liquidity Restrictions -Finally, the HydraDX Protocol has put some liquidity restrictions in place. One such restriction is to make **LRNA unvailable for purchase** on the market. The only way to obtain LRNA is to receive it as partial compensation for the IL experienced by LPing. This is meant to cap the total amount of LRNA that could leave the Omnipool, and therefore limit how much LRNA could suddenly be sold back to the Omnipool. +Finally, the Hydration Protocol has put some liquidity restrictions in place. One such restriction is to make **LRNA unvailable for purchase** on the market. The only way to obtain LRNA is to receive it as partial compensation for the IL experienced by LPing. This is meant to cap the total amount of LRNA that could leave the Omnipool, and therefore limit how much LRNA could suddenly be sold back to the Omnipool. Asset caps are another type of liquidity restriction. Asset caps are defined per asset and they ensure that any token cannot make up a greater proportion of the Omnipool than initially defined by the cap. diff --git a/docs/omnipool_lp.md b/docs/omnipool_lp.md index 46a9fd570..10a36044e 100644 --- a/docs/omnipool_lp.md +++ b/docs/omnipool_lp.md @@ -5,9 +5,9 @@ title: Single-Sided LPing import useBaseUrl from '@docusaurus/useBaseUrl'; -The cutting-edge design of the HydraDX Omnipool unlocks the possibility of single-sided liquidity provisioning: Anyone can provide liquidity only for the asset they want, and as much as they want (up to the respective TVL cap for the asset). This resolves one of the main drawbacks of standard XYK AMMs which require that liquidity providers (LPs) deposit a pair of assets in equivalent value. +The cutting-edge design of the Hydration Omnipool unlocks the possibility of single-sided liquidity provisioning: Anyone can provide liquidity only for the asset they want, and as much as they want (up to the respective TVL cap for the asset). This resolves one of the main drawbacks of standard XYK AMMs which require that liquidity providers (LPs) deposit a pair of assets in equivalent value. -Liquidity in the HydraDX Omnipool is concentrated, meaning that by providing your asset you gain instant exposure to all other assets in the Omnipool. Forget about liquidity fragmentation and the need to spread your liquidity across several trading pools. +Liquidity in the Hydration Omnipool is concentrated, meaning that by providing your asset you gain instant exposure to all other assets in the Omnipool. Forget about liquidity fragmentation and the need to spread your liquidity across several trading pools. ## The Hub Token LRNA diff --git a/docs/omnipool_security.md b/docs/omnipool_security.md index 85efc18b9..e218ccf48 100644 --- a/docs/omnipool_security.md +++ b/docs/omnipool_security.md @@ -3,43 +3,43 @@ id: omnipool_security title: State of the Art Security --- -The HydraDX Protocol pursues a multi-layered security strategy. On this page you will find a description of the various measures which work together to keep your funds safe. +The Hydration Protocol pursues a multi-layered security strategy. On this page you will find a description of the various measures which work together to keep your funds safe. -The most basic layer of the HydraDX security strategy consists carefully conducted research and development, as well as rigorous peer review processes. On top of that, HydraDX strives to have all mission-critical code undergo rigorous audits. The next layer of the security strategy is a generous bug bounty program which makes it worthwhile to find and disclose vulnerabilities (as opposed to exploiting them). +The most basic layer of the Hydration security strategy consists carefully conducted research and development, as well as rigorous peer review processes. On top of that, Hydration strives to have all mission-critical code undergo rigorous audits. The next layer of the security strategy is a generous bug bounty program which makes it worthwhile to find and disclose vulnerabilities (as opposed to exploiting them). -Finally, the protocol has implemented a combination of state-of-the-art measures which are designed to [protect your liquidity](https://docs.hydradx.io/omnipool_security#protecting-liquidity) against unfortunate events such as toxic assets or (economic) exploits. +Finally, the protocol has implemented a combination of state-of-the-art measures which are designed to [protect your liquidity](https://docs.hydration.net/omnipool_security#protecting-liquidity) against unfortunate events such as toxic assets or (economic) exploits. ## Audits {#audits} -The HydraDX protocol conducts audits of all mission-critical code and [publishes the audit reports](https://github.com/galacticcouncil/HydraDX-audit-reports) on a regular basis. +The Hydration protocol conducts audits of all mission-critical code and [publishes the audit reports](https://github.com/galacticcouncil/Hydration-audit-reports) on a regular basis. -The security audit of the Rust implementation of the HydraDX Omnipool was performed by [Runtime Verification](https://runtimeverification.com/) - an established industry leader with clients such as NASA, Ethereum and Polkadot. The scope of the security audit includes the source code of [HydraDX Omnipool pallet](https://github.com/galacticcouncil/HydraDX-node/blob/master/pallets/omnipool/src/),its [mathematical logic](https://github.com/galacticcouncil/HydraDX-math/tree/main/src/omnipool) and [asset registry](https://github.com/galacticcouncil/warehouse/tree/main/asset-registry), as well as 3rd party libraries which have been included as a (Substrate) dependency. The results of the audit were published in September 2022, you can [consult the full report here](https://github.com/galacticcouncil/HydraDX-audit-reports/blob/main/220907-Runtime-Verification-Security-Audit.pdf). +The security audit of the Rust implementation of the Hydration Omnipool was performed by [Runtime Verification](https://runtimeverification.com/) - an established industry leader with clients such as NASA, Ethereum and Polkadot. The scope of the security audit includes the source code of [Hydration Omnipool pallet](https://github.com/galacticcouncil/HydraDX-node/blob/master/pallets/omnipool/src/),its [mathematical logic](https://github.com/galacticcouncil/HydraDX-math/tree/main/src/omnipool) and [asset registry](https://github.com/galacticcouncil/warehouse/tree/main/asset-registry), as well as 3rd party libraries which have been included as a (Substrate) dependency. The results of the audit were published in September 2022, you can [consult the full report here](https://github.com/galacticcouncil/HydraDX-audit-reports/blob/main/220907-Runtime-Verification-Security-Audit.pdf). -In March 2022, the economic/math audit of the Omnipool was completed by [BlockScience](https://block.science/) - a leading web3 native firm dedicated to analyzing complex systems for the likes of Graph Protocol and Protocol Labs (Filecoin). The scope of this audit was to provide an overview of the AMM specification with a special attention to the mathematical and economic concepts underpinning the Omnipool, together with the implications of those mechanisms for liquidity provisioning and trading activity. You can [consult the full report here](https://github.com/galacticcouncil/HydraDX-audit-reports/blob/main/220322-BlockScience-Omnipool-Report%2Baddendum-by-HydraDX.pdf), including the addendum by HydraDX with post-factum changes. +In March 2022, the economic/math audit of the Omnipool was completed by [BlockScience](https://block.science/) - a leading web3 native firm dedicated to analyzing complex systems for the likes of Graph Protocol and Protocol Labs (Filecoin). The scope of this audit was to provide an overview of the AMM specification with a special attention to the mathematical and economic concepts underpinning the Omnipool, together with the implications of those mechanisms for liquidity provisioning and trading activity. You can [consult the full report here](https://github.com/galacticcouncil/HydraDX-audit-reports/blob/main/220322-BlockScience-Omnipool-Report%2Baddendum-by-HydraDX.pdf), including the addendum by Hydration with post-factum changes. ## Bug Bounty Program {#bug-bounties} -HydraDX has set up a [generous bug bounty program](https://immunefi.com/bounty/hydradx/) which provides strong incentives for the detection and responsible disclosure of bugs and other vulnerabilities. +Hydration has set up a [generous bug bounty program](https://immunefi.com/bounty/hydradx/) which provides strong incentives for the detection and responsible disclosure of bugs and other vulnerabilities. Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. ## Mechanisms for Protecting Omnipool Liquidity {#protecting-liquidity} -The HydraDX protocol is continuously researching and implementing mechanisms that keep the Omnipool liquidity safe. These mechanisms are activated in the unfortunate (but not impossible) scenario that an actor tries to drain liquidity from the Omnipool by abusing a toxic asset situation (LUNA-like scenario) or some malicious exploit. +The Hydration protocol is continuously researching and implementing mechanisms that keep the Omnipool liquidity safe. These mechanisms are activated in the unfortunate (but not impossible) scenario that an actor tries to drain liquidity from the Omnipool by abusing a toxic asset situation (LUNA-like scenario) or some malicious exploit. ### TVL Caps {#tvl-caps} -All assets are subject to a specific TVL cap defining the maximum proportion of liquidity which any given asset can represent in the Omnipool. Riskier assets will have lower caps compared to less risky (high mcap or stable) assets. This allows the HydraDX protocol to significantly limit the damage which may potentially be caused from toxic asset flows: Using a hyper-inflationary asset, attackers cannot drain more liquidity than its TVL cap. +All assets are subject to a specific TVL cap defining the maximum proportion of liquidity which any given asset can represent in the Omnipool. Riskier assets will have lower caps compared to less risky (high mcap or stable) assets. This allows the Hydration protocol to significantly limit the damage which may potentially be caused from toxic asset flows: Using a hyper-inflationary asset, attackers cannot drain more liquidity than its TVL cap. ### Oracles {#oracles} -On-chain oracles provide average price information for a specified Omnipool asset during a given timeframe (e.g. 10 blocks). Oracles are an essential monitoring tool that allow the HydraDX protocol to detect irregularities and potential price manipulation attacks - and to act accordingly. +On-chain oracles provide average price information for a specified Omnipool asset during a given timeframe (e.g. 10 blocks). Oracles are an essential monitoring tool that allow the Hydration protocol to detect irregularities and potential price manipulation attacks - and to act accordingly. ### Dynamic Withdrawal Fees {#dynamic-withdrawal-fees} To protect the Omnipool liquidity, all withdrawals of liquidity positions are subject to a fee. The withdrawal fee is dynamic, ranging between 0.01% and 1% of the total amount. The exact fee amount is determined at the time of withdrawal based on the asset in question. -The withdrawal fee covers the spread between the current spot price of the asset and the its average price over the previous 10 blocks (fetched from the HydraDX oracles). A large discrepancy between spot and average price indicates a potential price manipulation attack, and a higher withdrawal fee is applied to eliminate the economic incentives for carrying out such an attack. +The withdrawal fee covers the spread between the current spot price of the asset and the its average price over the previous 10 blocks (fetched from the Hydration oracles). A large discrepancy between spot and average price indicates a potential price manipulation attack, and a higher withdrawal fee is applied to eliminate the economic incentives for carrying out such an attack. In the scenario that extreme volatility leads to the spread between the spot price and average oracle price of an asset being greater than 1%, liquidity addition or withdrawal for that asset will be temporarily paused. These operations will again resume once this threshold is respected. @@ -49,4 +49,4 @@ To protect the Omnipool against economic exploits, there is a limit in place tha ### Targeted Function Pausing {#tfp} -If some suspicious behaviour is detected on-chain, Targeted Function Pausing allows the HydraDX Technical Committee to take swift action and temporarily pause certain or all actions relating to specific assets. This action of last resort can help mitigate the damage and allow for further investigation. +If some suspicious behaviour is detected on-chain, Targeted Function Pausing allows the Hydration Technical Committee to take swift action and temporarily pause certain or all actions relating to specific assets. This action of last resort can help mitigate the damage and allow for further investigation. diff --git a/docs/omnipool_trading.md b/docs/omnipool_trading.md index 5b046bade..a39fa1857 100644 --- a/docs/omnipool_trading.md +++ b/docs/omnipool_trading.md @@ -5,7 +5,7 @@ title: Efficient Trading import useBaseUrl from '@docusaurus/useBaseUrl'; -The traditional DeFi landscape is characterised by fragmented liquidity which is dispersed across several trading pools. This leads to economic inefficiencies: More hops and shallower liquidity create higher price impact and slippage. By combining all liquidity in a single trading pool, the HydraDX Omnipool enables efficient trading like no other AMM. +The traditional DeFi landscape is characterised by fragmented liquidity which is dispersed across several trading pools. This leads to economic inefficiencies: More hops and shallower liquidity create higher price impact and slippage. By combining all liquidity in a single trading pool, the Hydration Omnipool enables efficient trading like no other AMM. ## Traditional AMMs: Liquidity Fragmentation @@ -19,7 +19,7 @@ One of the flaws of the XYK model is that trading pools are constrained to pairs - 85% direct from ETH to AAVE (incurring 0.3% fee); - 15% ETH traded for UNI first then the UNI is swapped for AAVE (incurring two 0.3% swap fees). -## HydraDX Omnipool: Unified Liquidity +## Hydration Omnipool: Unified Liquidity Thanks to the cutting-edge design, liquidity in the Omnipool truly *acts as* *one*. By having all the liquidity connected through LRNA, the assets within the Omnipool have direct access to the entirety of liquidity for any other asset that is also deposited into the Omnipool. This allows for a **seamless on-chain execution** and enables swaps to be completed in a **single transaction** with no hopping required between various isolated trading pools. @@ -31,4 +31,4 @@ Furthermore, based on internal research, the increase in the number of tokens an To illustrate with an example, imagine the TKN asset is distributed across 4 different liquidity pools with varying levels of liquidity. In the scenario that a trader wants to trade DAI for TKN, they would only have access to the direct liquidity of the $1M TKN-DAI pool. If their trade size is substantial (e.g. $100K+), the majority of the trade will likely be routed through a DAI-ETH pool followed by the TKN-ETH pool in the traditional XYK landscape. -However, with the Omnipool, that same $5mm (50% of the total $10mm TVL) of the TKN asset and $3mm of DAI would be concentrated in one pool. As such, if a trader proceeds to make the same trade in the HydraDX Omnipool, they will get the entire benefit of the $5mm of TKN and $3mm of DAI liquidity in their direct swap, materially reducing the overall price impact. +However, with the Omnipool, that same $5mm (50% of the total $10mm TVL) of the TKN asset and $3mm of DAI would be concentrated in one pool. As such, if a trader proceeds to make the same trade in the Hydration Omnipool, they will get the entire benefit of the $5mm of TKN and $3mm of DAI liquidity in their direct swap, materially reducing the overall price impact. diff --git a/docs/omnipool_treasuries.md b/docs/omnipool_treasuries.md index 2dd13ea10..737ae9877 100644 --- a/docs/omnipool_treasuries.md +++ b/docs/omnipool_treasuries.md @@ -3,12 +3,12 @@ id: omnipool_treasuries title: Hydrate Your Treasury (B2B) --- -The HydraDX Omnipool has an **outspoken value proposition** for the **treasury of any project or DAO**. Forget about centralized market makers and inflationary rewards for liquidity mining; the Omnipool can facilitate the creation of a market for your token in a cost-efficient manner - trustless, without hidden costs and while building up your POL from trading fees. +The Hydration Omnipool has an **outspoken value proposition** for the **treasury of any project or DAO**. Forget about centralized market makers and inflationary rewards for liquidity mining; the Omnipool can facilitate the creation of a market for your token in a cost-efficient manner - trustless, without hidden costs and while building up your POL from trading fees. -Thanks to its cutting-edge design, the HydraDX Omnipool supports [single-sided LPing](/omnipool_lp). Instead of wastefully allocating liquidity mining rewards to incentivize other users to provide liquidity, projects and DAOs can deposit a part of their treasury to the Omnipool and receive **instant exposure to all other assets in an ocean of liquidity:** Diversified and deep (HydraDX has $20M+ worth of POL which is gradually being deployed). +Thanks to its cutting-edge design, the Hydration Omnipool supports [single-sided LPing](/omnipool_lp). Instead of wastefully allocating liquidity mining rewards to incentivize other users to provide liquidity, projects and DAOs can deposit a part of their treasury to the Omnipool and receive **instant exposure to all other assets in an ocean of liquidity:** Diversified and deep (Hydration has $20M+ worth of POL which is gradually being deployed). -LPing in the HydraDX Omnipool is **truly** **trustless**. Leveraging Polkadot’s unique capability of **cross-chain communication (XCM)**, the Omnipool empowers you to always remain in control of your funds: You can both provide your liquidity and manage it without relying on third parties. +LPing in the Hydration Omnipool is **truly** **trustless**. Leveraging Polkadot’s unique capability of **cross-chain communication (XCM)**, the Omnipool empowers you to always remain in control of your funds: You can both provide your liquidity and manage it without relying on third parties. -Providing liquidity to the HydraDX Omnipool is not only cost-efficient - it is also **profitable**. Instead of having your tokens sit idle in your treasury, you can put them to work. You will earn **rewards from trading fees**, allowing you to **build up POL** over time. Soon, our upcoming **TWAMM/DCA** feature will allow you **diversify the accumulated POL in** other assets (e.g. dollar cost averaged stablecoins or DOT which you can use to bid on your next parachain slot). +Providing liquidity to the Hydration Omnipool is not only cost-efficient - it is also **profitable**. Instead of having your tokens sit idle in your treasury, you can put them to work. You will earn **rewards from trading fees**, allowing you to **build up POL** over time. Soon, our upcoming **TWAMM/DCA** feature will allow you **diversify the accumulated POL in** other assets (e.g. dollar cost averaged stablecoins or DOT which you can use to bid on your next parachain slot). -Finally, the HydraDX Omnipool enjoys state of the art security. Besides rigorous audits and a generous bug bounty program, we have set up a combination of measures which work together to keep your liquidity safe. Learn more here. +Finally, the Hydration Omnipool enjoys state of the art security. Besides rigorous audits and a generous bug bounty program, we have set up a combination of measures which work together to keep your liquidity safe. Learn more here. diff --git a/docs/participate_in_referenda.md b/docs/participate_in_referenda.md index 3131ad91f..ff2856da4 100644 --- a/docs/participate_in_referenda.md +++ b/docs/participate_in_referenda.md @@ -25,7 +25,7 @@ To cast your vote, click on `Vote` and provide the following information: - **Vote with account** - select the voting account. - **Value** - this is the amount of HDX tokens you are willing to lock in support of the referendum. -- **Vote lock** - this is the multiplier which co-determines the [weight of your vote](https://docs.hydradx.io/democracy_referenda#referenda-votes-weighing). +- **Vote lock** - this is the multiplier which co-determines the [weight of your vote](https://docs.hydration.net/democracy_referenda#referenda-votes-weighing). After that, bring out your vote by clicking on *Nay* (No) or *Aye* (Yes) and sign the transaction. @@ -87,5 +87,5 @@ After submitting the proposal on-chain and signing the transaction, your proposa :::caution Every voting period, the referendum proposal with the highest backing (*seconding*) enters the voting round. As the amount of referenda grows, there is no guarantee that your proposal will ever gain sufficient seconding to enter voting. There is no option to withdraw a referendum proposal, meaning that your funds might remain locked for a longer period of time. -Malicious referendum proposals are punished. The HydraDX Council and the Technical Committee have the right to cancel any referendum which was proposed in bad faith. As a result, the deposited tokens will be burnt. +Malicious referendum proposals are punished. The Hydration Council and the Technical Committee have the right to cancel any referendum which was proposed in bad faith. As a result, the deposited tokens will be burnt. ::: diff --git a/docs/performance_benchmark.md b/docs/performance_benchmark.md index 93c6c5463..e00f55af3 100644 --- a/docs/performance_benchmark.md +++ b/docs/performance_benchmark.md @@ -38,10 +38,10 @@ transaction_multi_payment| 218.00 vs 198.00 | 20.00 | 9.1 Notes: - in the diff fields you can see the difference between the reference benchmark time and the benchmark time of your machine -- if diff is positive for all three pallets, your machine covers the minimum requirements for running a HydraDX node +- if diff is positive for all three pallets, your machine covers the minimum requirements for running a Hydration node - if diff deviates by -10% or more for some of the pallets, your machine might not be suitable to run a node ``` -You can see the difference in the performance between your machine and the minimum required setup in the column **diff* (%)**. If all three values in this column are positive, your machine should be suitable to run a HydraDX validator node. If any of the values is below *-10 %*, we do not recommend running a HydraDX node. +You can see the difference in the performance between your machine and the minimum required setup in the column **diff* (%)**. If all three values in this column are positive, your machine should be suitable to run a Hydration validator node. If any of the values is below *-10 %*, we do not recommend running a Hydration node. Join us at Discord if you would like to discuss your benchmark results, our community is always happy to help. diff --git a/docs/polkadotjs_apps_local.md b/docs/polkadotjs_apps_local.md index b90af78c7..ba9fce5d9 100644 --- a/docs/polkadotjs_apps_local.md +++ b/docs/polkadotjs_apps_local.md @@ -5,7 +5,7 @@ title: Connect to a Local Node import useBaseUrl from '@docusaurus/useBaseUrl'; -You can use the Polkadot/apps to connect to your local HydraDX node. For this purpose, you need to have access to port `9944` which is used for RPC websocket connections. +You can use the Polkadot/apps to connect to your local Hydration node. For this purpose, you need to have access to port `9944` which is used for RPC websocket connections. :::warning diff --git a/docs/polkadotjs_apps_public.md b/docs/polkadotjs_apps_public.md index c39a40bfe..b838c9709 100644 --- a/docs/polkadotjs_apps_public.md +++ b/docs/polkadotjs_apps_public.md @@ -5,9 +5,9 @@ title: Connect to a Public Node import useBaseUrl from '@docusaurus/useBaseUrl'; -There are two public RPC nodes which are maintained by HydraDX and our partners. You can use these nodes for interacting with Snakenet. You can directly connect to a public node with Polkadot/apps by clicking on the link below: +There are two public RPC nodes which are maintained by Hydration and our partners. You can use these nodes for interacting with Snakenet. You can directly connect to a public node with Polkadot/apps by clicking on the link below: -* [RPC node hosted by HydraDX](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer) +* [RPC node hosted by Hydration](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer) ## Connect manually to an RPC node {#connect-manually-to-an-rpc-node} @@ -18,7 +18,7 @@ To access a public RPC node manually, open the [Polkadot/apps](https://polkadot.
-Click on **LIVE NETWORKS** and select **HydraDX**. +Click on **LIVE NETWORKS** and select **Hydration**.
diff --git a/docs/referrals.md b/docs/referrals.md index 91c29d0f0..d3b95cca2 100644 --- a/docs/referrals.md +++ b/docs/referrals.md @@ -5,9 +5,9 @@ title: Referrals import useBaseUrl from '@docusaurus/useBaseUrl'; -HydraDX is running a Referrals Program which aims to create **sustainable long-term incentives** to help onboard users to HydraDX. Anyone can participate and **start earning referral rewards** by registering their unique referral code: +Hydration is running a Referrals Program which aims to create **sustainable long-term incentives** to help onboard users to Hydration. Anyone can participate and **start earning referral rewards** by registering their unique referral code: -[https://app.hydradx.io/referrals/](https://app.hydradx.io/referrals/) +[https://app.hydration.net/referrals/](https://app.hydration.net/referrals/) ## How do referrals work? Users that are onboarded with a referral code are linked to the account of their referrer. From this point on, the referrer accumulates rewards from the fees generated by all Omnipool trades of these users. diff --git a/docs/spending_fw.md b/docs/spending_fw.md index 4b5f0f678..a24393e78 100644 --- a/docs/spending_fw.md +++ b/docs/spending_fw.md @@ -1,21 +1,21 @@ --- id: spending_fw -title: Contribute to HydraDX +title: Contribute to Hydration --- -# Rewarding Contributions to HydraDX +# Rewarding Contributions to Hydration -HydraDX welcomes various contributions which are in the interest of the Protocol. Such activities are incentivized with the help of rewards from the HydraDX Treasury. +Hydration welcomes various contributions which are in the interest of the Protocol. Such activities are incentivized with the help of rewards from the Hydration Treasury. -The present document sets out the general framework for rewarding community contributions. This framework has been approved by the community of HydraDX in a [general vote](https://hydradx.subsquare.io/democracy/referendum/11). The spending framework empowers payouts in the mentioned categories by the HydraDX Council, within the defined limits. +The present document sets out the general framework for rewarding community contributions. This framework has been approved by the community of Hydration in a [general vote](https://hydradx.subsquare.io/democracy/referendum/11). The spending framework empowers payouts in the mentioned categories by the Hydration Council, within the defined limits. -Please note in advance that the payout of all bounties and tips mentioned in this document is subject to the full discretion of the HydraDX Council. If you are in doubt whether your effort entitles you to a bounty, please reach out in advance. +Please note in advance that the payout of all bounties and tips mentioned in this document is subject to the full discretion of the Hydration Council. If you are in doubt whether your effort entitles you to a bounty, please reach out in advance. -You can ask questions in #bounties on the HydraDX Discord. +You can ask questions in #bounties on the Hydration Discord. ## 1. Bug Bounties {#bug-bounties} -HydraDX runs a Bug Bounty program on Immunefi. Bugs and vulnerabilities are classified into three to four categories of severity which determine the maximum size of the bounty: +Hydration runs a Bug Bounty program on Immunefi. Bugs and vulnerabilities are classified into three to four categories of severity which determine the maximum size of the bounty: ### Blockchain: {#bug-bounties-blockchain} @@ -32,20 +32,20 @@ HydraDX runs a Bug Bounty program on Immunefi. Bugs and vulnerabilities are clas ### Notes: {#bug-bounties-notes} -* In order to be granted a bounty, bug reports must be made in accordance with the procedure for responsible disclosure and any other guideline posted on the HydraDX Immunefi page; +* In order to be granted a bounty, bug reports must be made in accordance with the procedure for responsible disclosure and any other guideline posted on the Hydration Immunefi page; * Bounties for critical Blockchain vulnerabilities are capped at 10% of the potential economic damage; * The actual size of the rewarded bounties is at the discretion of the Council; -* Bounties are paid by the treasury in HDX using the 7d MA USD price from an exchange (CEX or DEX once Oracles are available - if in doubt, please discuss with the HydraDX Council in #bounties). +* Bounties are paid by the treasury in HDX using the 7d MA USD price from an exchange (CEX or DEX once Oracles are available - if in doubt, please discuss with the Hydration Council in #bounties). ## 2. Development Bounties {#dev-bounties} -The HydraDX development team will be launching a dashboard with development bounties in an effort to decentralize technical work on the protocol. The dashboard will present the latest bounties together with a description, technical specification and size of the bounty. +The Hydration development team will be launching a dashboard with development bounties in an effort to decentralize technical work on the protocol. The dashboard will present the latest bounties together with a description, technical specification and size of the bounty. -The present framework authorizes the HydraDX Council to propose development bounties of up to $100,000 which will be paid by the Treasury in HDX using the 7d MA USD price from an exchange. Bounties exceeding this amount still need to undergo the governance process. +The present framework authorizes the Hydration Council to propose development bounties of up to $100,000 which will be paid by the Treasury in HDX using the 7d MA USD price from an exchange. Bounties exceeding this amount still need to undergo the governance process. ## 3. Community Management {#community-mgmt} -Efforts spent on Community Management can be rewarded from the HydraDX treasury in HDX at a rate of $20 per hour (using the 7d MA USD price from an exchange). +Efforts spent on Community Management can be rewarded from the Hydration treasury in HDX at a rate of $20 per hour (using the 7d MA USD price from an exchange). New community managers are subject to prior approval by the team. @@ -60,22 +60,22 @@ Here are some of the expectations attached to these roles: ## 4. Translations {#translations} -Work on translations can be rewarded from the HydraDX treasury in HDX at a rate of $20 per hour (using the 7d MA USD price from an exchange). Currently, HydraDX welcomes translations in the following languages (this list can be extended via a referendum): +Work on translations can be rewarded from the Hydration treasury in HDX at a rate of $20 per hour (using the 7d MA USD price from an exchange). Currently, Hydration welcomes translations in the following languages (this list can be extended via a referendum): * Mandarin * Spanish * Russian * Slovak -New translators are subject to prior approval by the Community Managers and/or HydraDX Council. +New translators are subject to prior approval by the Community Managers and/or Hydration Council. ## 5. Other Community Contributions {#other-contributions} -Are you looking to contribute with an effort which does not fall into one of the categories above? Please feel free to reach out, the HydraDX Council is prepared to consider your case. This spending framework authorizes the HydraDX Council to provide tips up to the value of $100,000 (using the 7d MA USD price from an exchange). +Are you looking to contribute with an effort which does not fall into one of the categories above? Please feel free to reach out, the Hydration Council is prepared to consider your case. This spending framework authorizes the Hydration Council to provide tips up to the value of $100,000 (using the 7d MA USD price from an exchange). Here are some examples of contributions that could be rewarded: -* Creating good educational content such as guides, explanative blogs or videos [content creator should liaise with Community Managers & HydraDX Council ahead of and during production process to ensure information is of the highest quality]; +* Creating good educational content such as guides, explanative blogs or videos [content creator should liaise with Community Managers & Hydration Council ahead of and during production process to ensure information is of the highest quality]; * Provisioning Decentralized infrastructure; * Advancing integrations which contribute to the Protocol or the community; * Memes (!!), emojis, merch and stickers. \ No newline at end of file diff --git a/docs/staking.md b/docs/staking.md index 91b6b04b3..30ef850fa 100644 --- a/docs/staking.md +++ b/docs/staking.md @@ -5,11 +5,11 @@ title: Staking import useBaseUrl from '@docusaurus/useBaseUrl'; -HydraDX has a **long-running HDX staking program** which **incentivizes user activity** in areas that are beneficial to the Protocol. On this page you will find important information regarding the **mechanics behind the HDX Staking program**. You can also check out our [step-by-step guide on staking](/howto_stake). +Hydration has a **long-running HDX staking program** which **incentivizes user activity** in areas that are beneficial to the Protocol. On this page you will find important information regarding the **mechanics behind the HDX Staking program**. You can also check out our [step-by-step guide on staking](/howto_stake). ## Staking Basics {#basics} -HDX holders can **stake their HDX and receive rewards** which become **claimable as time passes**. Staking rewards are distributed from a dedicated pot that is gradually filled up by **different Protocol revenue streams**. Initially, the main revenue stream are the **LP fees** which the HydraDX Protocol accrues from its **HDX LP position in the Omnipool**. Furthermore, the HydraDX community has approved a proposal to support the APR during the first year of the staking program with **an additional subsidy of ~22M HDX** from the HydraDX Treasury which is gradually distributed to the staking rewards pot once per day. +HDX holders can **stake their HDX and receive rewards** which become **claimable as time passes**. Staking rewards are distributed from a dedicated pot that is gradually filled up by **different Protocol revenue streams**. Initially, the main revenue stream are the **LP fees** which the Hydration Protocol accrues from its **HDX LP position in the Omnipool**. Furthermore, the Hydration community has approved a proposal to support the APR during the first year of the staking program with **an additional subsidy of ~22M HDX** from the Hydration Treasury which is gradually distributed to the staking rewards pot once per day. Rewards which enter the staking pot are always distributed directly to all stakers at any given moment. The amount that users are entitled to is proportional to the relative size of their stake in the stake pool. However, stakers do not automatically receive the rewards on their account - instead, they need to claim them. @@ -19,7 +19,7 @@ Users who want to claim as many rewards as possible should keep their HDX staked ## Boosting Your Rewards {#boosting-your-rewards} -Stakers can increase the pace at which they can claim their rewards by **collecting action points** and **boosting their rewards**. Action points can be acquired by performing certain actions that are incentivized by the Protocol. Initially, the only way to collect action points is to **participate in the governance of HydraDX** by [voting on community referenda](https://hydradx.subsquare.io/democracy/referenda) **using the staked HDX**. +Stakers can increase the pace at which they can claim their rewards by **collecting action points** and **boosting their rewards**. Action points can be acquired by performing certain actions that are incentivized by the Protocol. Initially, the only way to collect action points is to **participate in the governance of Hydration** by [voting on community referenda](https://hydradx.subsquare.io/democracy/referenda) **using the staked HDX**.
login diff --git a/docs/testnet_howto.md b/docs/testnet_howto.md index 950656291..7dd923da5 100644 --- a/docs/testnet_howto.md +++ b/docs/testnet_howto.md @@ -1,4 +1,4 @@ -# Design and Automation of our Tesnet Deployment at HydraDX +# Design and Automation of our Tesnet Deployment at Hydration In this article, we are going to show you how we designed and automated our pipeline to be able to deploy a new testnet (Parachain + Relaychain) within minutes using Kubernetes (EKS Fargate), AWS ACM, Route53, Terraform and Github Actions. @@ -75,7 +75,7 @@ spec: - containerPort: 30333 ``` -In this manifest, we choose the name of our node, the ports to expose, the command and its argument (please check HydraDX docs) as well as the number of replicas. This parameter is important as we only want one replica per node, to avoid sync issues. Note that you can have as many nodes as necessary. +In this manifest, we choose the name of our node, the ports to expose, the command and its argument (please check Hydration docs) as well as the number of replicas. This parameter is important as we only want one replica per node, to avoid sync issues. Note that you can have as many nodes as necessary. #### Service Example We use the Service object in Kubernetes for at least two purposes here: diff --git a/docs/tip_request.md b/docs/tip_request.md index 57f3b83fb..c60f1b415 100644 --- a/docs/tip_request.md +++ b/docs/tip_request.md @@ -5,13 +5,13 @@ title: Request a Treasury Tip import useBaseUrl from '@docusaurus/useBaseUrl'; -Community members can request HDX tips from the HydraDX Treasury as a reward for their contributions to the Protocol. This guide walks you through the process of tip requests. You can find more information about the different types of activities that get rewarded in [this post](/spending_fw). +Community members can request HDX tips from the Hydration Treasury as a reward for their contributions to the Protocol. This guide walks you through the process of tip requests. You can find more information about the different types of activities that get rewarded in [this post](/spending_fw). The process of requesting a Treasury tip consists of two steps. As a first step, contributors need to [publish their tip request](#01-publish-tip-request) in Subsquare with a description of the contribution. As a second step, the Treasury tip request must be [submitted on-chain](#02-submit-on-chain) using Polkadot/apps. ## 01 Publish in Subsquare {#01-publish-tip-request} -To safeguard transparency, all Treasury tip requests must be published as a Discussion thread on the [HydraDX Subsquare page](https://hydradx.subsquare.io/discussions). +To safeguard transparency, all Treasury tip requests must be published as a Discussion thread on the [Hydration Subsquare page](https://hydradx.subsquare.io/discussions). :::note Before opening a thread, make sure that Subsquare is linked to your HDX wallet. To do so, click on Sign-Up (first-time use) or Login (repeated use) and select the option `with Web3 address`. After selecting your HDX address in the popup, you will be asked to sign the message using your wallet. @@ -25,7 +25,7 @@ You can use the title of the thread to indicate the subject (tip request) and th * A brief summary of the contribution * The amount of the requested tip (in HDX) * Time spent on the contribution (in hours) -* If appropriate, provide more detailed information such as the relevance of the contribution to HydraDX and a link to the PR (in the case of technical contributions) +* If appropriate, provide more detailed information such as the relevance of the contribution to Hydration and a link to the PR (in the case of technical contributions) Before posting the thread, please make sure that the tab `Treasury` is selected to indicate the nature of the Discussion. diff --git a/docs/tokenomics.md b/docs/tokenomics.md index c5fb1b774..6f233c1a2 100644 --- a/docs/tokenomics.md +++ b/docs/tokenomics.md @@ -7,9 +7,9 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; ## Purpose -The HDX token is a governance token that allows staked token holders to decide the future of the protocol. Our mission with the HydraDX DAO is to distribute all decision-making to create a trustless liquidity protocol built around community-growth and self-sustainability. +The HDX token is a governance token that allows staked token holders to decide the future of the protocol. Our mission with the Hydration DAO is to distribute all decision-making to create a trustless liquidity protocol built around community-growth and self-sustainability. -To have a vote in the HydraDX DAO, and to contribute to the determination of any of the topics raised by community members, one must hold the HDX governance token. For more specifically on the governance process, please read our [Democracy](https://docs.hydradx.io/democracy_intro) documentation. +To have a vote in the Hydration DAO, and to contribute to the determination of any of the topics raised by community members, one must hold the HDX governance token. For more specifically on the governance process, please read our [Democracy](https://docs.hydration.net/democracy_intro) documentation. HDX will initially be used for the following: @@ -19,7 +19,7 @@ HDX will initially be used for the following: ## HDX Token Allocation -Upon the launch of the HydraDX DAO, the defined maximum supply of HDX tokens was 10 billion HDX. However through the [governance-approved supply reduction](https://hydradx.subsquare.io/democracy/referendum/7), this defined maximum supply was reduced to 6.5 billion HDX tokens. +Upon the launch of the Hydration DAO, the defined maximum supply of HDX tokens was 10 billion HDX. However through the [governance-approved supply reduction](https://hydradx.subsquare.io/democracy/referendum/7), this defined maximum supply was reduced to 6.5 billion HDX tokens. The allocation of these tokens is currently as follows: @@ -44,6 +44,6 @@ As of Sept 2023, ~2.6 billion of HDX tokens are in circulation.
-There is currently no concrete emission/release schedule for HDX tokens residing in the Treasury and Growth allocations. HydraDX intends to distribute the supply of HDX in the treasury and growth funds to help fund ecosystem development where opportunities may arise. All of these distributions will be discussed transparently to the community beforehand and voted on by the HydraDX DAO. +There is currently no concrete emission/release schedule for HDX tokens residing in the Treasury and Growth allocations. Hydration intends to distribute the supply of HDX in the treasury and growth funds to help fund ecosystem development where opportunities may arise. All of these distributions will be discussed transparently to the community beforehand and voted on by the Hydration DAO. Token distributions range from a variety of developmental purposes and growth initiatives, (eg. HDX bonds, liquidity provider rewards, integrations/partnerships with other projects, etc). diff --git a/docs/trade_metamask.md b/docs/trade_metamask.md index ac77eec19..a4bea9d48 100644 --- a/docs/trade_metamask.md +++ b/docs/trade_metamask.md @@ -5,19 +5,19 @@ title: Start Trading with MetaMask import useBaseUrl from '@docusaurus/useBaseUrl'; -The HydraDX chain supports the Ethereum Virtual Machine (EVM). You can use your 0x address with MetaMask and/or Ledger to perform any on-chain action such as trading in the Omnipool or placing a trustless over-the-counter order. +The Hydration chain supports the Ethereum Virtual Machine (EVM). You can use your 0x address with MetaMask and/or Ledger to perform any on-chain action such as trading in the Omnipool or placing a trustless over-the-counter order. The accepted currency for gas fees is **WETH (Moonbeam)**. -The easiest way to onboard assets from the Ethereum network into your MetaMask HydraDX account is to [bridge them to the Moonbeam network](https://www.carrier.so/). +The easiest way to onboard assets from the Ethereum network into your MetaMask Hydration account is to [bridge them to the Moonbeam network](https://www.carrier.so/). -Once you have the assets on the Moonbeam network, you can easily transfer them to the HydraDX chain using the guide below. +Once you have the assets on the Moonbeam network, you can easily transfer them to the Hydration chain using the guide below. ## Step-by-step -To onboard assets from Moonbeam to HydraDX: +To onboard assets from Moonbeam to Hydration: -1. Navigate to the [HydraDX cross-chain UI](https://app.hydradx.io/cross-chain) -2. Connect your MetaMask wallet and accept changing network to HydraDX +1. Navigate to the [Hydration cross-chain UI](https://app.hydration.net/cross-chain) +2. Connect your MetaMask wallet and accept changing network to Hydration 3. Select as source chain `Moonbeam` 4. Select the asset you want to transfer and the amount 5. Transfer and sign using your MetaMask wallet diff --git a/docs/yield_dca.md b/docs/yield_dca.md index 74b190a25..13b0d97f2 100644 --- a/docs/yield_dca.md +++ b/docs/yield_dca.md @@ -3,15 +3,15 @@ id: yield_dca title: Yield DCA --- -[Yield DCA](https://app.hydradx.io/trade/yield-dca) enables users to diversify their rewards from DOT staking by setting up a [DCA schedule](/omnipool_dca) which periodically swaps their DOT staking yield into any asset traded on HydraDX. +[Yield DCA](https://app.hydration.net/trade/yield-dca) enables users to diversify their rewards from DOT staking by setting up a [DCA schedule](/omnipool_dca) which periodically swaps their DOT staking yield into any asset traded on Hydration. Yield DCA works with vDOT - the DOT liquid staking token by [Bifrost Finance](https://bifrost.finance/). vDOT is a shadow token of staked DOT, with an underlying DOT reserve and incorporating the yield-bearing feature of DOT staking rewards (more info in the [Bifrost docs](https://docs.bifrost.finance/builders/liquid-staking-slp/vdot)). Holding vDOT acts as an equivalent to having a DOT staking position which is liquid, with staking rewards being accumulated as an appreciation in the price of vDOT. ## How does it work? -Users can [mint vDOT](https://bifrost.app/vstaking/vDOT?r=hydradx) by depositing their DOT into the Bifrost SLP (and vice versa: DOT can be redeemed using vDOT). Once minted, the vDOT can be sent to HydraDX using our [Cross-chain UI](https://app.hydradx.io/cross-chain). Alternatively, vDOT can be obtained directly from the [HydraDX Omnipool](https://app.hydradx.io/trade/swap). +Users can [mint vDOT](https://bifrost.app/vstaking/vDOT?r=hydradx) by depositing their DOT into the Bifrost SLP (and vice versa: DOT can be redeemed using vDOT). Once minted, the vDOT can be sent to Hydration using our [Cross-chain UI](https://app.hydration.net/cross-chain). Alternatively, vDOT can be obtained directly from the [Hydration Omnipool](https://app.hydration.net/trade/swap). -On HydraDX, users can easily [set up a Yield DCA order](https://app.hydradx.io/trade/yield-dca) which swaps the yield from the value appreciation of their vDOT (average APY of 15%) into any asset traded on HydraDX. The swaps will take place at least once every 24h (depending on the order size). +On Hydration, users can easily [set up a Yield DCA order](https://app.hydration.net/trade/yield-dca) which swaps the yield from the value appreciation of their vDOT (average APY of 15%) into any asset traded on Hydration. The swaps will take place at least once every 24h (depending on the order size). This mechanism allows users to diversify their yield from DOT staking into other assets from the Polkadot ecosystem, and the DCA strategy helps users smoothen out the volatility of the markets. -[https://app.hydradx.io/trade/yield-dca](https://app.hydradx.io/trade/yield-dca) +[https://app.hydration.net/trade/yield-dca](https://app.hydration.net/trade/yield-dca) diff --git a/docusaurus.config.js b/docusaurus.config.js index ef5dfa809..b0a540669 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -2,39 +2,29 @@ const math = require('remark-math'); const katex = require('rehype-katex'); module.exports = { - title: "HydraDX Docs", + title: "Hydration Docs", tagline: "Let's learn this", - url: "https://docs.hydradx.io", + url: "https://docs.hydration.net", baseUrl: "/", onBrokenLinks: "throw", onBrokenMarkdownLinks: "throw", favicon: "img/favicon.png", organizationName: "galacticcouncil", // Usually your GitHub org/user name. - projectName: "HydraDX-docs", // Usually your repo name. + projectName: "Hydration-docs", // Usually your repo name. themeConfig: { prism: { additionalLanguages: ['rust'], }, navbar: { - title: "HydraDX Documentation", + title: "Hydration Docs", logo: { - alt: "HydraDX logo", + alt: "Hydration logo", src: "img/logo.svg", }, items: [ { - to: "/", - activeBasePath: "/", - label: "Docs", - position: "left", - }, - { - type: 'localeDropdown', - position: 'right', - }, - { - href: "https://hydradx.io", - label: "HydraDX Homepage", + href: "https://hydration.net", + label: "Hydration Homepage", position: "right", }, ], @@ -68,7 +58,7 @@ module.exports = { routeBasePath: "/", remarkPlugins: [math], rehypePlugins: [katex], - editUrl: "https://github.com/galacticcouncil/HydraDX-docs/edit/main/", + editUrl: "https://github.com/galacticcouncil/Hydration-docs/edit/main/", }, theme: { customCss: require.resolve("./src/css/custom.css"), @@ -84,28 +74,4 @@ module.exports = { crossorigin: 'anonymous', } ], - i18n: { - defaultLocale: 'en', - locales: ['en', 'de', 'ru', 'es', 'fr', 'cn'], - localeConfigs: { - en: { - label: 'English', - }, - de: { - label: 'Deutsch', - }, - ru: { - label: 'русский', - }, - es: { - label: 'español', - }, - fr: { - label: 'français', - }, - cn: { - label: '中文', - } - }, - }, }; diff --git a/i18n/cn/code.json b/i18n/cn/code.json deleted file mode 100644 index 11ea61b9b..000000000 --- a/i18n/cn/code.json +++ /dev/null @@ -1,158 +0,0 @@ -{ - "theme.NotFound.title": { - "message": "哎呀！网页找不到了......", - "description": "The title of the 404 page" - }, - "theme.NotFound.p1": { - "message": "我们找不到您想要的东西！", - "description": "The first paragraph of the 404 page" - }, - "theme.NotFound.p2": { - "message": "请联系将您引导至此的 URL 所有者，并告知其链接已损坏。", - "description": "The 2nd paragraph of the 404 page" - }, - "theme.AnnouncementBar.closeButtonAriaLabel": { - "message": "关闭", - "description": "The ARIA label for close button of announcement bar" - }, - "theme.blog.post.readingTime.plurals": { - "message": "一分钟阅读时间|{readingTime} min read", - "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.tags.tagsListLabel": { - "message": "标签：", - "description": "The label alongside a tag list" - }, - "theme.blog.post.readMore": { - "message": "阅读更多", - "description": "The label used in blog post item excerpts to link to full blog posts" - }, - "theme.blog.paginator.navAriaLabel": { - "message": "博客目录页面导航", - "description": "The ARIA label for the blog pagination" - }, - "theme.blog.paginator.newerEntries": { - "message": "新链接入口", - "description": "The label used to navigate to the newer blog posts page (previous page)" - }, - "theme.blog.paginator.olderEntries": { - "message": "旧链接入口", - "description": "The label used to navigate to the older blog posts page (next page)" - }, - "theme.blog.post.paginator.navAriaLabel": { - "message": "博客帖子页面导航", - "description": "The ARIA label for the blog posts pagination" - }, - "theme.blog.post.paginator.newerPost": { - "message": "新帖子", - "description": "The blog post button label to navigate to the newer/previous post" - }, - "theme.blog.post.paginator.olderPost": { - "message": "旧帖子", - "description": "The blog post button label to navigate to the older/next post" - }, - "theme.tags.tagsPageTitle": { - "message": "标签", - "description": "The title of the tag list page" - }, - "theme.blog.post.plurals": { - "message": "一个帖子|{count} posts", - "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.blog.tagTitle": { - "message": "{nPosts} 标记为 \"{tagName}\"", - "description": "The title of the page for a blog tag" - }, - "theme.tags.tagsPageLink": { - "message": "查看所有标签", - "description": "The label of the link targeting the tag list page" - }, - "theme.CodeBlock.copyButtonAriaLabel": { - "message": "将代码复制到剪贴板", - "description": "The ARIA label for copy code blocks button" - }, - "theme.CodeBlock.copied": { - "message": "已复制", - "description": "The copied button label on code blocks" - }, - "theme.CodeBlock.copy": { - "message": "复制", - "description": "The copy button label on code blocks" - }, - "theme.docs.paginator.navAriaLabel": { - "message": "文档页面导航", - "description": "The ARIA label for the docs pagination" - }, - "theme.docs.paginator.previous": { - "message": "上一页", - "description": "The label used to navigate to the previous doc" - }, - "theme.docs.paginator.next": { - "message": "下一页", - "description": "The label used to navigate to the next doc" - }, - "theme.docs.sidebar.expandButtonTitle": { - "message": "展开侧边栏", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.expandButtonAriaLabel": { - "message": "展开侧边栏", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.responsiveCloseButtonLabel": { - "message": "关闭菜单", - "description": "The ARIA label for close button of mobile doc sidebar" - }, - "theme.docs.sidebar.responsiveOpenButtonLabel": { - "message": "打开菜单", - "description": "The ARIA label for open button of mobile doc sidebar" - }, - "theme.docs.sidebar.collapseButtonTitle": { - "message": "收起侧边栏", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.sidebar.collapseButtonAriaLabel": { - "message": "收起侧边栏", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.versions.unreleasedVersionLabel": { - "message": "这是{siteTitle} {versionLabel}版本的未发布文档。", - "description": "The label used to tell the user that he's browsing an unreleased doc version" - }, - "theme.docs.versions.unmaintainedVersionLabel": { - "message": "这是{siteTitle} {versionLabel}的文档，该文档不再有效维护。", - "description": "The label used to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionSuggestionLabel": { - "message": "有关最新文档，请参见{latestVersionLink}（{versionLabel}）。", - "description": "The label userd to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionLinkLabel": { - "message": "最新版本", - "description": "The label used for the latest version suggestion link label" - }, - "theme.common.headingLinkTitle": { - "message": "直接链接到标题", - "description": "Title for link to heading" - }, - "theme.common.editThisPage": { - "message": "编辑此页", - "description": "The link label to edit the current page" - }, - "theme.lastUpdated.atDate": { - "message": " 在{date}", - "description": "The words used to describe on which date a page has been last updated" - }, - "theme.lastUpdated.byUser": { - "message": " 由{user}", - "description": "The words used to describe by who the page has been last updated" - }, - "theme.lastUpdated.lastUpdatedAtBy": { - "message": "上次更新时间{atDate}{byUser}", - "description": "The sentence used to display when a page has been last updated, and by who" - }, - "theme.common.skipToMainContent": { - "message": "跳转到主要内容", - "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation" - } -} \ No newline at end of file diff --git a/i18n/cn/docusaurus-plugin-content-docs/current.json b/i18n/cn/docusaurus-plugin-content-docs/current.json deleted file mode 100644 index 33c3e5d44..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current.json +++ /dev/null @@ -1,46 +0,0 @@ -{ - "version.label": { - "message": "下一页", - "description": "The label for version current" - }, - "sidebar.sidebar.category.HydraDX": { - "message": "HydraDX", - "description": "The label for category HydraDX in sidebar sidebar" - }, - "sidebar.sidebar.category.How-to": { - "message": "指南", - "description": "The label for category How-to in sidebar sidebar" - }, - "sidebar.sidebar.category.Wallets": { - "message": "钱包", - "description": "The label for category Wallets in sidebar" - }, - "sidebar.sidebar.category.Connect to a Node": { - "message": "连接到节点", - "description": "The label for category Connect to a Node in sidebar" - }, - "sidebar.sidebar.category.Learn": { - "message": "知识", - "description": "The label for category Learn in sidebar sidebar" - }, - "sidebar.sidebar.category.Democracy": { - "message": "民主", - "description": "The label for category Democracy in sidebar" - }, - "sidebar.sidebar.category.Maintain": { - "message": "运行", - "description": "The label for category Maintain in sidebar sidebar" - }, - "sidebar.sidebar.category.Build": { - "message": "构建", - "description": "The label for category Build in sidebar sidebar" - }, - "sidebar.sidebar.category.Contribute": { - "message": "共建", - "description": "The label for category Contribute in sidebar sidebar" - }, - "sidebar.sidebar.category.Archive": { - "message": "存档", - "description": "The label for category Archive in sidebar sidebar" - } -} \ No newline at end of file diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/archive_hydradx_crowdloan.md b/i18n/cn/docusaurus-plugin-content-docs/current/archive_hydradx_crowdloan.md deleted file mode 100644 index f7a47204f..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/archive_hydradx_crowdloan.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -id: archive_hydradx_crowdloan -title: HydraDX 众贷 ---- - -:::warning -此页面已存档，意味着它包含的信息可能已过时或不再适用。 -::: - -Polkadot 平行链拍卖的 HydraDX 众贷现已上线！您可以通过参与我们的众贷活动并贡献锁定一定数量的 DOT 令牌来支持 HydraDX，这些令牌将在平行链插槽期间被锁定。 - -作为回报，您将获得 HDX 奖励，用于支付您的机会成本。 一旦平行链插槽过期，您将收到全额返还的 DOT 令牌。 这同样适用于 HydraDX 未能在下文所述众贷活动截止日期内赢得平行链插槽的情况。 - -## 众贷详情 {#crowdloan-details} -* 访问： **https://loan.hydradx.io/** -* 众贷开始： **2021 年 12 月 28 日** -* 插槽竞标： **#6 - #11** -* 获胜平行链后的接入： **2022 年 3 月 11 日** -* 租赁平行链插槽结束： **2024 年 1 月 12 日** -* 众贷上限： **8,000,000 DOT** -* 奖励： **每个贡献的 DOT 奖励 280 到 12.5 HDX** -* 奖励上限： **不超过 1,000,000,000 HDX** (总供应量的 10%) -* 归属期： HDX 奖励 **线性分配**。分发，将在 HydraDX 作为 Polkadot 平行链接入，并完成从 Snakenet（我们的测试网）迁移后开始。 -* 众贷活动截止日期： **2022 年 3 月 12 日** - -## HDX 奖励 -HydraDX 众贷所有参与者，都将 **获得 HDX**，以奖励他们的贡献。 奖励的多少，取决于您贡献时我们 **在平行链拍卖竞赛中的排名**，以及其他人贡献的 **DOT 总量**。 - -在 **HydraDX 领先 15% 之前** 做出的贡献，将获得最高金额的奖励 - **每个贡献的 DOT 将获得 280 到 125 HDX** 。 - -在我们获得舒适的领先优势后，奖励将开始 **线性下降**。 一旦 HydraDX **领先 25% 或更多**，它们将处于最低水平。 在我们领先超过 25% 的时间内做出的贡献，每个贡献的 DOT 将获得 28 到 12.5 HDX。 - -奖励系统，旨在抵消在平行链租赁期间锁定您的 DOT 的 **机会成本**，而不是抵押它。 在我们获得 15% 的领先优势之前做出的贡献，将获得 **全部机会成本的补偿**。 用于计算的 **HDX** 价格为 **0.026 美元**。 该数字源于 HDX LBP 收盘价 0.08 美元（2021 年 2 月），同时考虑测试网期间实施的所有余额增至三倍这一因素。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/claim.md b/i18n/cn/docusaurus-plugin-content-docs/current/claim.md deleted file mode 100644 index ab6396842..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/claim.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -id: claim -title: 申领您的 HDX ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -您可以使用 **[Balancer LBP](https://hydradxcn.substack.com/p/lbpgg)** 期间获得的 xHDX 令牌（ERC-20）申领您的 HDX。 - -## 前提条件 {#prequisites} - -申领 HDX，有两个前提条件。首先，您需在浏览器上安装 **[Polkadot.js 扩展程序](https://polkadot.js.org/extension/)**，它将用于创建 HDX 钱包。其次，您需要访问您的 xHDX 令牌，该令牌应该存储在支持 ERC-20 令牌消息签署的钱包中（如 Metamask）。 - -如果您的 xHDX 令牌存储在 Coinbase 钱包或 Trust 钱包中，则需使用以下其中一个方法申领 HDX，因它们不支持消息签署： - -* Metamask：您可以使用 Metamask 浏览器扩展程序，并使用恢复种子短语（*助记词* ）导入钱包。 -* MEW (MyEtherWallet)：您可以通过导入恢复种子短语(*助记词* ) 或使用 WalletLink 连接这两个选项来使用 MEW 。这两个选项都可从 **[MEW 钱包页面](https://www.myetherwallet.com/access-my-wallet)** 访问。如果您使用的是 Coinbase 钱包，则可以使用 WalletLink，在那里可以找到 Coinbase 的设置。 - -## 申领过程 {#claim-process} - -满足上述前提条件后，您可以导航到 **[HydraDX 申领程序](https://claim.hydradx.io)**，启动申领过程。 - -在申领过程中，您将使用 xHDX 令牌（ERC-20）申领属于您的 HDX 令牌份额。 - -### 00 授权 {#00-authorize} - -HydraDX 申领程序，需要 Polkadot.js 扩展程序的授权。 - -:::warning - -请确保您不是钓鱼攻击的受害者，注意授权弹出：申领程序应自我标识为 **CLAIM.HYDRADX.IO**，且请求来自于 **https://claim.hydradx.io** 。 - -::: - -authorize - -授权后，会提示您更新 Polkadot.js 扩展程序的元数据。这将允许 Polkadot.js 创建一个申领过程所需的 HydraDX 特定地址。 - -authorize - -### 01 选择 ETH 地址 {#01-select-your-eth-address} - -在这一步，系统将要求选择持有您 xHDX 令牌的帐户。可通过连接到支持 ERC-20 令牌（如 Metamask）的钱包，或在输入框手动输入 ETH 地址完成（在此情况下，稍后需手动签署消息）。 - -确认 ETH 地址后，您应该能看到可申领的 HDX 令牌余额，包括您在 Balancer 上获得 xHDX 所花费的 **[Gas 退款](https://hydradxcn.substack.com/p/sczltp)**。 - -:::note - -如果您在 Balancer 官方池以外的其它地方（如 Uniswap）获得了 xHDX，或已将 xHDX 令牌从原始购买钱包中移出，则无资格获得 Gas 退款。 - -::: - -authorize - -### 02 创建并选择 HDX 地址 {#02-create-and-select-an-hdx-address} - -这一步，将要求您选择 HDX 地址。 - -要创建新的 HDX 地址，请打开 Polkadot.js 扩展程序，单击 `+` 号创建一个新帐户。在帐户创建的第一步，您会看到由 12 个英语单词组成、用于恢复帐户的助记词。将助记词保存在安全的地方后，点击 `Next step`（下一步）。在这里，选择 **HydraDX** 来切换 **NETWORK** （网络）。输入您的帐户名称和密码，完成帐户创建。 - -authorize - -:::warning - -确保通过安全的方式保存备份您的助记词，并且永远不要分享给任何人。助记词，是恢复账户的唯一方法，丢失或泄漏它可能会造成加密资产的损失。请注意，当前所有的 HDX 令牌均被锁定，主网启动前，您需要确保拥有对钱包的访问权限。如无法访问 HDX 钱包，那您也就丢失了所拥有的 HDX 。 - -::: - -创建 HDX 帐户后，您应能在 HydraDX 申领程序中选择它。之后，该应用程序应为您提供用于申领过程的 ETH 和 HDX 地址概况。单击 `Next`（下一步）继续对消息进行签署。 - -authorize - -### 03 签署 {#03-sign} - -在这一步，您将可以选择用 xHDX 令牌申领 HDX 的消息进行签署。 - -:::note - -请注意，在此步骤中，您将看到 HDX 地址的 **公钥** ，而不是上一步和 Polkadot.js 扩展程序中显示的该地址的可读格式形式的地址（更多详细信息，请参阅 **[ss58 文档](https://polkadot.js.org/docs/keyring/start/ss58)** ）。如果您已严格按照上述步骤进行操作，则无需担心，可以安全地对消息进行签署。我们还将验证，您最后一步用于签署申领交易的 HDX 帐户，与接收所申领 HDX 的帐户是否相对应。 - -::: - -根据您第一步的选择，有两个方法可对消息进行签署，以在申领过程中使用 xHDX 令牌： - -* 如果您用的是 **Metamask** , 则在单击 `Sign`（签署）按钮后，将由 Metamask 提示您对信息进行签署。请按 Metamask 中的说明进行操作。 - -* 如果您手动输入了 ETH 地址，则需通过外部钱包签署消息，该外部钱包保留了您 xHDX 令牌的私钥。签署消息后，将签署哈希（以 *0x* 开头）复制粘贴到 HydraDX 申领程序的相应对话框中。 - -authorize - -### 04 申领 {#04-claim} - -使用持有 xHDX 令牌的钱包签署消息后，Polkadot.js 扩展程序应自动打开，并将要求签署交易，以将 HDX 申领到您的帐户中。输入您的 HDX 帐户密码，然后点击 `Sign the transaction`（签署交易）。 - -authorize - -此时您已完成申领过程，从而正式成为 HDX 的所有者。 - -您可以使用连接到 HydraDX 网络检查令牌数额： -**https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts** - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/collator_setup.md b/i18n/cn/docusaurus-plugin-content-docs/current/collator_setup.md deleted file mode 100644 index 17420df4e..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/collator_setup.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -id: collator_setup -title: 搭建整理器节点 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -这是一个启动并运行 HydraDX 整理器的分步操作指南。在本指南中，我们使用 Ubuntu 20.04 LTS。 - -## 所需要的技术条件 {#technical-specifications} - -运行 HydraDX 整理器节点至少需要满足以下技术要求： - -* 操作系统：Ubuntu 20.04 -* CPU: Intel Core i7-7700K @ 4.5Ghz (或同等单核性能) -* 内存: 64GB RAM -* 存储：容量至少为 200GB 的 NVMe SSD（数据占用空间会随着时间增长） - -:::note - -这些是经团队验证过的最低技术要求。想要确保您的机器有足够的资源来运行节点？请运行 **[基本性能测试](/performance_benchmark)** 以找出答案。 - -::: - -## 创建技术 `hydra` 用户并将其添加到 Sudoers - -```bash -sudo adduser hydra -sudo usermod -aG sudo hydra -su - hydra -``` - -## 下载并配置 `hydradx` 二进制文件 - -选择一个 12.x 版本，我们使用我们资产存储库中的 `v12.1.0` ： - -```bash -wget https://github.com/galacticcouncil/HydraDX-node/releases/download/v12.1.0/hydradx -sudo mv hydradx /usr/local/bin -sudo chmod +x /usr/local/bin/hydradx -sudo chown hydra:hydra /usr/local/bin/hydradx - -``` - -## 命令您的整理器运行 - -最好是使用 `systemctl` 将您的整理器作为 `service`。 为此，在 `/etc/systemd/system/hydradx-collator.service` 中创建一个名为 `hydradx-collator.service` 的文件。 - -```bash -sudo vim /etc/systemd/system/hydradx-collator.service -``` - -然后粘贴以下内容： - -```bash -[Unit] -Description=hydradx validator -[Service] -Type=exec -User=hydra -ExecStart=/usr/local/bin/hydradx \ - --name YOUR_COLLATOR_NAME \ - --prometheus-external \ - --base-path /var/lib/hydradx \ - --collator \ - -- \ - --execution wasm \ - --telemetry-url "wss://telemetry.hydradx.io:9000/submit/ 0" \ - --base-path /var/lib/hydradx - -Restart=always -RestartSec=120 -[Install] -WantedBy=multi-user.target -``` - -在开始您的节点之前，让我们创建基本路径文件夹并赋予它必要的权限和所有权： - -```bash -mkdir /var/lib/hydradx -chown hydra:hydra /var/lib/hydradx -``` - -:::caution -使用 `df -h` 命令确保您为 `base-path` 留有足够的空间。 -::: - -请注意，这 `--prometheus-external` 是可选的，但我们强烈建议您使用它，以便您能够导出 prometheus 指标并通过 Grafana 监控节点的健康状况。有关监控的更多详细信息，请访问 **[此链接](https://docs.hydradx.io/node_monitoring/)**。 - -如果您需要同时监控 `parachain` 和`relaychain` 指标，`--prometheus-external` 则应在这两个部分中设置选项。您还需要为中继链部分设置一个单独的端口，如下所示：`--prometheus-port YOUR_CUSTOM_PORT_NUMBER` 。 - -根据您的设置，您可能还想覆盖某些参数，如 websocket、rpc 或您的节点 p2p 端口。有关可用选项的更多信息，请使用 `hydradx --help` 。 - -保存文件后，运行以下命令启动节点： - -```bash -sudo systemctl enable hydradx-collator -sudo systemctl start hydradx-collator.service -``` - -您的节点现在应该已启动并正在运行。确保您的 `hydra` 用户具有访问您 `base-path` 和密钥文件的必要权限。 -如果您需要对正在运行的服务进行故障排除，可以使用带有拖尾选项的 `journalctl` 命令：`-f` ： - -```bash -journalctl -fu hydradx-collator -``` - -## 生成您的密钥 - -为了让您的节点生成密钥，请运行以下命令： - -```bash -curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params":[]}' http://localhost:9933 -``` - -完成后，您将看到似于以下内容的输出： - -```json -{"jsonrpc":"2.0","result":"0x9257c7a88f94f858a6f477743b4180f0c9a0630a1cea85c3f47dc6ca78e503767089bebe02b18765232ecd67b35a7fb18fc3027613840f27aca5a5cc300775391cf298af0f0e0342d0d0d873b1ec703009c6816a471c64b5394267c6fc583c31884ac83d9fed55d5379bbe1579601872ccc577ad044dd449848da1f830dd3e45","id":1} -``` - -## 设置您的密钥 - -要将生成的会话密钥与您的控制器帐户相关联，请导航到 Polkadot 平行链 HydraDX 上的 **[Polkadot/apps](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics)** 中的以下菜单项：*Developer* > *Extrinsics* 。 - -填写字段: - -- *using selected account*（使用所选帐户）：选择您的控制器帐户； -- *submit the following extrinsic*（提交以下外部内容）：选择 `session` 左侧和`setKeys` 右侧； -- *keys*（密钥）：输入您刚刚生成的会话密钥； -- *proof*（证明）: `0`; - -
- -
- -## 下一步是什么 - -确保您的节点已完全同步。一旦完成，请在专用的 Discord 频道中告诉我们（仅当您已被预选为整理器时）。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/create_account.md b/i18n/cn/docusaurus-plugin-content-docs/current/create_account.md deleted file mode 100644 index 044dbf757..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/create_account.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -id: create_account -title: 创建 HDX 新账户 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -创建 HDX 新帐户的过程包括三个简单的步骤。 - -## 01 安装 Polkadot.js {#01-install-polkadot-js} - -为了创建和管理您的 HDX 钱包，您需要安装 **[Polkadot.js 浏览器扩展程序](https://polkadot.js.org/extension/)**。 - -## 02 升级 metadata（元数据） {#02-upgrade-metadata} - -安装 Polkadot.js 浏览器扩展程序后，您应确保它已更新为最新的链元数据。 为此，可访问以下链接并在出现提示时更新元数据： -**https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/settings/metadata** - -## 03 创建您的 HDX 账户 {#03-create-hdx-account} - -要创建 HDX 新地址，请打开 Polkadot.js 浏览器扩展程序并单击 ` + ` > `Create new account`（创建新账户）。 - -您将看到一个 12 个短语的助记词，可用于恢复您的帐户。 确保在安全的位置备份您的种子短语。 点击 `Next step` （下一步）并填写以下信息： - -* **Network**（网络）: 请选择 `HydraDX` -* **Descriptive name of the account**（账户的描述性名称） -* **Password**（账户密码） - -单击 `Add the account with the generated seed`（使用生成的种子添加账户）后，将创建您的帐户。 - -
- create-account -
- -:::warning - -确保通过将其存储在安全位置来备份您的恢复种子短语。 永远不要与任何人分享您的种子短语。 种子短语可用于访问您的帐户。 如果丢失或泄露，您可能还会丢失帐户中存储的所有 HDX。 请注意，在主网启动之前，所有 HDX 余额都会被锁定，因此您需要确保在此之前保持持有令牌的帐户安全。 - -::: diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_council.md b/i18n/cn/docusaurus-plugin-content-docs/current/democracy_council.md deleted file mode 100644 index 9680d0b56..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_council.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -id: democracy_council -title: HydraDX 议会 ---- - -HydraDX 议会是一个链上实体，在协议的治理中起着关键作用。 本文提供有关议会 **[组成](#composition)**、议会 **[主要任务](#tasks)** 和 **[选举议会成员](#elections)** 等三方面信息。 - -有关如何参与议会选举的分步指导，请参阅 **[本指南](/participate_in_council_elections)** 。 - -## 组成 {#composition} -HydraDX 议会目前由 **13 名成员** 组成。 - -创始团队和投资者（4 名创始人 + 2 名投资者）将获得 6 个席位中的少数席位。 - -剩下的 7 个席位由更广泛的 HDX 持有者社区选举产生。 - -## 任务和职责 {#tasks} -HydraDX 议会的任务涵盖广泛的日常治理活动。 首先，议会控制财政部并批准或拒绝财政部的提案。 - -HydraDX 议会也在公投机制中发挥作用。 议会可以发起全民投票，前提是至少有 60% 的成员支持（绝对多数）并且没有成员行使否决权。 在否决的情况下，可以在冷却期过后重新提交提案。 否决成员不能两次否决同一提案。 - -此外，任何提议的公投都可以在获得议会 2/3 绝对多数票的情况下取消。 这可以用作阻止可能在代码中引入错误的恶意提议或更改的最后手段。 - -最后，HydraDX 议会负责选举技术委员会。 - -## 选举 {#elections} -HDX 令牌的任何持有者都可以 **[申请](/participate_in_council_elections#become_candidate)** 作为 HydraDX 议会的 7 个非常任组的一个候选人。 - -议会选举每 7 天举行一次，届时将在接下来的 7 天内填补 7 个非常任议会席位。 民主模块使用相同的 Phragmen 算法。 - -所有社区成员都可以通过选择锁定他们一定数量的 HDX 令牌在议会选举中 **[投票](/participate_in_council_elections#vote)** 。 锁定的令牌不可转让，将在后续选举中使用（直至取消）。 选民可以也应该按照优先顺序选择一名以上的候选人。 然后，选举算法将所有选票分配给获得最高社区支持的候选人，以确定可获得的议会席位的最优分配。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_intro.md b/i18n/cn/docusaurus-plugin-content-docs/current/democracy_intro.md deleted file mode 100644 index 6ece541b3..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_intro.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -id: democracy_intro -title: 简介 ---- - -HydraDX 正在将其治理完全去中心化。所有影响项目发展的决定都是在一个由 Substrate 民主模块支持的民主程序之后通过的。在利益相关者之间建立共识的核心机制是 **公投** 。 - -本节文章包含了一系列知识，可以让您更好地了解 HydraDX 治理背后的机制。您将找到更多关于 **[公投如何运作](/democracy_referenda)** 的信息，以及关于治理参与者的两个中心组： **[HydraDX 议会](/democracy_council)** 和 **[技术委员会](/democracy_technical_committee)** 。 - -如果您正在寻找有关如何参与 HydraDX 治理的实用指南，请参阅 **[参与公投](/participate_in_referenda)** 和 **[参与议会选举](/participate_in_council_elections)** 的分步指南。 - -## 民主参数 -下面列表包含了影响 HydraDX 治理机制的最重要参数。请注意，这些可能会随着时间的推移而改变。 - -* 发起公投的最低 HDX 存款： **10 000 HDX** -* 公投制定周期： **6 天** -* 公投投票期： **3 天** -* 紧急公投投票时间： **3 小时** -* 公投被否决后的冷静期：**7 天** -* 最大待决公投提案数： **100** - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_referenda.md b/i18n/cn/docusaurus-plugin-content-docs/current/democracy_referenda.md deleted file mode 100644 index 4fc106e7e..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_referenda.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -id: democracy_referenda -title: 公投 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -公投允许利益相关者将提案提交给更广泛的社区进行加权、基于权益的投票。公投的对象是一些影响项目发展的建议行动，例如，财政部支出，甚至运行代码的更改。 - -一般来说，一次只进行一次公投。其他未决的公投提案被放入队列中。公开提交的提案和议会提案有不同的队列。每 3 天，公投机制会选出支持率最高的提案，在两个队列之间交替。在公投通过并被接受后，有一个所谓的 3 天“颁布延迟”期，在此期间，决定生效。这些规则不适用于技术委员会处理重大协议问题并需要快速追踪的紧急提案。 - -## 发起公投 {#referenda-initiate} -有多种方式可以发起公投，下面将进行更详细的描述。公投的发起方式对适用的投票模式具有决定性意义。 - -### 公投 {#referenda-initiate-public} -HDX 令牌的任何持有者都可以通过存入所需最低数量的 HDX 令牌并在链上 **[提出公投提案](/participate_in_referenda#propose)** 。其他社区成员可以通过锁定等量的令牌来 **[支持（拥护）公投提案](/participate_in_referenda#second)** 。在每一个投票周期的开始，支持（总存入令牌）最高的公投提案，可以被社区优先投票。 - -适用于公投的投票模式是 **[正向投票率偏差](#referenda-voting-modes)** 。 - -:::note -所有用于提案或拥护投票的 HDX 令牌在公投进入投票周期之前都被锁定。 重要的是要记住，并不能保证任何给定的提案都能得到足够的支持进入投票阶段，这意味着您的资金可能会无限期地被锁定。 -::: - -### 议会公投 {#referenda-initiate-council} -HydraDX 议会有权提出公投以进行社区投票。如果一致通过，公投适用的投票模式为 **[负向投票率偏差](#referenda-voting-modes)**。如果公投是以议会简单多数票提出的，那么社区接受提案的投票方式为 **[简单多数](#referenda-voting-modes)** 。 - -### 技术委员会的紧急提案 {#referenda-initiate-tech-committee} -技术委员会可以提交处理(关键)错误修复或快速采用经过实战检验的功能的紧急提案。紧急提案无需排队，直接进入投票环节。社区可以在任何常规提案进入投票环节的同时，对紧急提案进行投票。此外，紧急提案的投票时间较短，以确保它们能够快速追踪。 - -### 取消公投 {#cancel} -一旦提议进行全民公决，在进入投票环节之前不能撤销。对于那些被认为对协议有害的提案(例如：代码更改引入了 bug)，这条规则不适用。在这种有限的情况下，公投提案可以由 **[HydraDX 议会](/democracy_council)** (60% 的绝对多数)或 **[技术委员会](/democracy_technical_committee)** (一致)取消。所有支持该提案的支持者锁定的令牌都将被烧毁。 - -## 在公投中投票 {#referenda-vote} -HydraDX 公投有 3 天的启动期。在每个新周期开始时，支持次数最多的提案将从等待队列中取出，并进入一轮投票。每一轮投票的持续时间为 3 天。在此期间，社区成员可以使用加权、基于权益的机制对公投进行投票。它们通过在给定时限内锁定一定数量的 HDX 令牌来做到这一点。 - -:::note -锁定的 HDX 令牌在选定的锁定期内无法转移。但是，它们仍然可以用于质押和投票。 -::: - -### 投票权重 {#referenda-votes-weighing} -有两个因素决定了公投中每张选票的权重。第一个因素是选民锁定以支持投票的 HDX 令牌数量。第二个因素是所谓的信念系数，它反映了选民愿意锁定令牌的持续时间。 - -``` -投票权重=令牌*信念系数 -``` - -投票锁定期与颁布后延迟解锁的时间相同。如果选 1 个锁定期，意味着投票结束后令牌将被锁定 **6 天** 。选民可通过减少或增加令牌的锁定期，影响投票权重。当然，若使用 0 个锁定期进行投票，投票权重仅为很小的一部分（信念系数为 0.1）。另一方面，锁定期每增加一倍，信念系数将增加 1。如下表所示，锁定期最长达 192 天，信念系数也将会提高至 6。 - -| 锁定期 | 信念系数 | -|:-----------------:|:---------------------:| -| 0 | 0.1 | -| 6 | 1 | -| 12 | 2 | -| 24 | 3 | -| 48 | 4 | -| 96 | 5 | -| 192 | 6 | - -``` -一个例子： - -Alice 以 5000 HDX 和 0 个锁定期进行投票。 -Bob 用 100 个 HDX 和 192 个锁定期投票。 - -Alice 权重: 500 -Bob 权重: 600 -``` - -### 投票模式 {#referenda-voting-modes} -民主模块的另一个重要方面，是不同的投票模式。批准或否决公投所需的票数门槛，可能因公投启动方式和投票的投票率而有所差异。投票率是根据在公投中用于投票的 HDX 令牌总量计算的（不包括信念系数）。投票率是否低，取决于投票率与投票者（即有资格投票的 HDX 令牌总量）之间的关系。 - -#### 正向投票率偏差 -这是社区提出公投时默认的投票模式。在投票率较低的情况下，需要获得合格的绝对多数票 `yes` 才能批准公投。随着投票率的增加，阈值会朝着简单多数的方向降低。 - -
- -
- -#### 负向投票率偏差 -这种投票方式，适用于议会一致提出的公投。此类提案需要获得合格的绝对 `no` 多数票才能在投票率低的情况下被否决。随着投票率的增加，拒绝公投的门槛降低到简单多数。 - -
- -
- -#### 简单多数 -由议会以多数同意（即非一致同意）发起的公投，可以由社区以简单多数票（50％ + 1）接受。 - -
- -
- - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_technical_committee.md b/i18n/cn/docusaurus-plugin-content-docs/current/democracy_technical_committee.md deleted file mode 100644 index e49361e09..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/democracy_technical_committee.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -id: democracy_technical_committee -title: 技术委员会 ---- - -技术委员会由 HydraDX 议会直接任命的、一群经验丰富的核心开发人员组成。其主要任务是维护 HydraDX 协议的技术稳定性。 - -技术委员会有权 **制定紧急公投** ，该公投可与任何其他有效公投同时进行快速跟踪和投票。这使委员会能够迅速采取行动并交付关键（代码）更改。 - -技术委员会的另一个重要权力，是有能力 **取消** 被认为对协议有害的 **公投提案** 。取消公投提案，技术委员会必须一致同意。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_bridge.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_bridge.md deleted file mode 100644 index fa26cc0b5..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_bridge.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -id: howto_bridge -title: 桥接资产 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -在此页面上，您将找到有关使用 Acala 通过 Wormhole（虫洞）实现从以太坊生态系统桥接令牌的分步指南。 - -Wormhole 的 Portal Bridge（传送桥）允许您在不同链之间桥接令牌。Wormhole 不是直接交换或转换资产，而是将您的源资产锁定在智能合约中，并在目标链上铸造新的 Wormhole 包装资产。然后，您可以在交易所将 Wormhole 包装的资产，交换成目标链上的其他资产。 - -## 必备条件 -* Polkadot 钱包（Talisman 或 Polkadot.js 应用程序）； -* 一个以太坊钱包（Metamask）； -* 按照 **[Acala 绑定指南](https://guide.acalaapps.wiki/general/address-binding)** 将以太坊钱包和您的 Acala 钱包地址绑定。完成这个动作需要少量的 ACA（＜ 1 ACA）。 - -:::caution -请确保您的钱包中有足够的令牌（ETH 和 ACA）来支付费用。请记住，发送和兑换令牌以及绑定您的钱包地址将收取费用。 -::: - -## 桥接资产 ETH -> Acala -### 01 导航到虫洞令牌桥 -**[https://www.portalbridge.com/#/transfer](https://www.portalbridge.com/#/transfer)** - -
- metadata -
- -### 02 选择网络并连接您的账户 - -* 重新定向到 Token Bridge 页面后，选择您要桥接的链 **（1）**。在我们的例子中，**Ethereum（以太坊）** 为源链，**Acala** 为目标链； -* 点击 `Connect` 连接到您桥接的 Metamask 帐户 **（2）**。 - -### 03 选择要桥接的资产 - -* 连接 Metamask 后，选择您想要桥接的令牌资产 **（3）** 。如果在下拉列表中没有找到令牌，您可以粘贴令牌合约地址（可以通过 Etherscan 确认）； -* 输入您想要桥接的令牌数量 **（4）** ; -* 单击 `Next` **（5）**。这时 Metamask 将出现提示，请求将网络从以太坊切换到 Acala。 - -:::caution -请注意，目前唯一能够从以太坊桥接到 Acala 的资产是： -* DAI: 0x6B175474E89094C44Da98b954EedeAC495271d0F（始终仔细检查合约地址） -::: - -
- metadata -
- -### 04 选择 Gas 支付方式 -* 在网络切换到 Acala 之后，选择 Gas 的支付方式 **（6）** 。请注意，免费桥接的最小值（在 Acala 一侧）为 ≥10 $DAI； -* 单击 `Next` **（7）** 继续。这时将出现 Metamask 提示，请求将网络从 Acala 切换回以太坊。 - -
- metadata -
- -### 05 桥接令牌 -* 在网络切换回以太坊后，单击 `Approve` **（8）** 继续。Metamask 钱包将提示，第一笔令牌转移交易需要批准; -* 执行此操作后，单击 `Transfer` **（8）** （将出现在 Approve 位置）。Metamask 钱包将提示，第二笔交易需要执行以桥接转账。 - -
- metadata -
- -Wormhole 处理交易后，单击 `Redeem` **（9）**（兑换）。此操作，会让您在 Acala 链上收到令牌。 - -
- metadata -
- -至此，您已完成了第一步！ - -## 桥接资产 Acala - > ETH -将桥接资产转回 Acala 后使用（**[跨链转账](/howto_xcm)**），可将它们桥接回以太坊生态系统，如下所示： - -### 01 导航到 Wormhole 令牌桥页面 -**[https://www.portalbridge.com/#/transfer](https://www.portalbridge.com/#/transfer)** - -
- metadata -
- -### 02 选择网络并连接您的账户 -* 重新定向到 Token Bridge（令牌桥）页面后，选择您要桥接的链 **（1）** 。此时，**Acala** 为源链，**Ethereum** 为目标链 -* 点击 `Connect` 连接到您桥接的 Metamask 帐户 **（2）**。 - -### 03 选择要桥接的资产 -* 连接 Metamask 后，选择您想要桥接的令牌资产 **（3）**。如果在下拉列表中没有找到令牌，您可以粘贴令牌合约地址（可以通过 Acala Blockscout 确认）； - -:::caution -请注意，目前唯一能够从以太坊桥接到 Acala 的资产是： -* DAI: 0x6B175474E89094C44Da98b954EedeAC495271d0F（始终仔细检查合约地址） -::: - -* 输入您想要桥接的令牌数量 **（4）**； -* 单击 `Next` **（5）**。这时将出现 Metamask 提示，请求将网络从 Acala 切换到 Ethereum。 - -
- metadata -
- -### 04 选择 Gas 支付方式 -* 在网络切换到以太坊后，选择 Gas 的支付方式 **（6）** 。请注意，手动支付是从 Acala 到 Ethereum 的唯一选择； -* 单击 `Next` **（7）**。这时将出现 Metamask 提示，请求将网络从 Ethereum 切换回 Acala。 - -
- metadata -
- -### 05 桥接令牌 -* 在网络切换回 Acala 后，单击 `Approve` **（8）** 继续。Metamask 钱包将会提示您，第一笔交易需要批准以转移令牌； -* 执行此操作后，单击 `Transfer` **（8）**（将出现在 Approve 的位置）。Metamask 钱包将会提示您，第二笔交易需要执行以桥接转账。 - -
- metadata -
- -Wormhole 交易处理后，单击 `Redeem` **（9）**（兑换）。此操作，会让您在以太坊链上收到令牌。 -
- metadata -
- -恭喜您，您已全部完成！ - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_dca.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_dca.md deleted file mode 100644 index e3bbb2fc7..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_dca.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -id: howto_dca -title: 下达 DCA 订单 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -在此页面，您将找到 **在 HydraDX Omnipool（万能池）中设置 DCA 订单** 的分步指南。 - -正式开始前，请先访问我们的 **[DCA 产品页面](/omnipool_dca)**，熟悉 HydraDX 实施的成本平均策略。 - -
- -
- -### 步骤 1：导航到 HydraDX DCA 页面 - -https://app.hydradx.io/dca - -### 步骤 2：连接您的账户 - -点击 **`Connect Account`**（连接账户）（上图中的 **1**），连接您的钱包至 HydraDX。 - -### 步骤 3：设置 DCA 订单 -* 选择您将用于支付交易费用的资产；输入每笔 DCA 交易的订单金额，以及总订单规模 **(2)**； -* 选择每次 DCA 交易的时间间隔 **(3)**； -* 选择您希望从交易中获得的资产 **(4)**； -* 对于想以特定区块间隔下达订单的高级用户，可以点击 **Advanced Settings**（高级设置）**(5)** 切换开关来设置； -* 如果您想调整滑点首选项，可通过单击 **设置图标 (6)** 来实现； -* 要完成 DCA 订单，请点击 **`Schedule DCA trades`**（实施 DCA 交易）**(7)**，并使用您的钱包应用程序签署交易。 - -### 步骤 4：查看您的 DCA 订单 -* 提交后，您的 DCA 订单将出现在 **DCA Orders**（DCA 订单）下； -* 要查看详情，请点击 **下拉箭头 (8)**; -* 您可以通过点击 **`Terminate`**（终止）**(9)**，取消剩余金额的 DCA 订单。 - -
- -
diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_hydrated_farms.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_hydrated_farms.md deleted file mode 100644 index 0d7498f98..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_hydrated_farms.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -id: howto_hydrated_farms -title: 加入九头蛇农场 ---- -import useBaseUrl from '@docusaurus/useBaseUrl'; - -通过九头蛇农场，除了获得交易费用奖励外，还可通过为选定资产提供流动性获得额外的奖励激励。要了解更多信息，请访问 **[产品专页](/omnipool_hydrated_farms)**。 - -## 00 导航至流动性页面 -[https://app.hydradx.io/liquidity](https://app.hydradx.io/liquidity) - -## 01 提供流动性 -资产激励，可通过 `Farm rewards`（农场奖励）来确定，它显示了该农场的所有可用奖励。 - -
- metadata -
- -要加入农场，您须首先提供流动性，具体请参考 **[分步操作指南](/howto_lp)**。 - -# 02 加入农场 -一旦为激励资产提供了流动性，您就可以加入其农场。 - -
- metadata -
- -为此，请点击您提供流动性头寸旁边的 `Join farms`（加入农场）并用您的钱包签署交易。 - -九头蛇农耕快乐！ diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_lp.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_lp.md deleted file mode 100644 index 43db99a53..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_lp.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -id: howto_lp -title: 提供流动性 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -在这一页中，您将在 HydraDX Omnipool（万能池）中找到一个 **提供流动性的分步指南**。成为流动性提供者，可以让您从池交易中 **获得奖励**。 - -在决定成为流动性提供者之前，我们鼓励您访问我们的 **[产品页面](/)**，从而 **了解熟悉** HydraDX Omnipool 的独特特性。 - -## 00 转移令牌 -如果您想使用非原生资产（例如 DOT 或 DAI）执行交易，您首先需要把这些资产转移到 HydraDX 链。这一步不适用 HDX。 - -有两种不同的机制来转移非原生资产： -* **[跨链转账](https://app.hydradx.io/#/cross-chain)** - 使用此工具，可从其他 Polkadot 平行链或从 Polkadot 自身转移资产。分步指南在 **[这里](howto_xcm)**； -* **[以太坊桥](https://www.portalbridge.com/#/transfer)** - 用于连接以太坊生态系统中的资产。分步指南文档在 **[这里](/bridge_from_ethereum)**。 - -这些解决方案，也可用于 HydraDX 网络之外的令牌传输。 - -## 01 导航至 Omnipool 流动性页面 -**[https://app.hydradx.io/#/liquidity](https://app.hydradx.io/#/liquidity)** - -
- metadata -
- -## 02 连接您的账户 -点击 `Connect Wallet`（连接钱包）**（上图中的 1 ）** 连接到您常用的 Polkadot 钱包。然后，选择您的账户。 - -## 03 管理您的流动性 - -### 添加流动性 -为给定资产添加流动性，点击该资产旁边的 `Add Liquidity`（添加流动性）**（3）**. - -
- metadata -
- -填写您想提供的流动性数量，点击 `Add Liquidity`（添加流动性），使用您的钱包签署交易。 - -### 移除流动性 -
- metadata -
- -要移除流动性，请切换到相关资产 **（1）** 旁边的下拉菜单，并在希望退出的位置上，单击 `Remove Liquidity` （移除流动性）。 - -
- metadata -
- -切换或输入您希望提取的流动性数量 **（3）**，点击 `Remove Liquidity` （移除流动性）并使用您的钱包签署交易。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_stake.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_stake.md deleted file mode 100644 index 0e50db32b..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_stake.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -id: howto_stake -title: 质押 HDX ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -质押，允许用户质押其 HDX 代币，并赚取随时间推移而分配的奖励。 本页面包含了如何质押 HDX 的分步指南，在开始之前，建议您熟悉 **[HDX 质押的基础知识](/staking)**。 - -如果您还没有 HDX，可以在我们的 **[交易页面](https://app.hydradx.io/#/trade)** 上，通过与 Omnipool（万能池） 支持的一系列资产进行交换，来获得一些 HDX。 - -### 步骤 0: 导航至 HydraDX 质押页面 - -https://app.hydradx.io/staking - -单击 **`Connect Account`**（连接账户），将您的钱包连接到 HydraDX。 - -### 步骤 1: 质押您的 HDX - -- 选择并填入您想要质押的 HDX 令牌数量 **(3)**。 -- 点击 **`Stake`**（质押）**(4)** 使用您的钱包应用程序确认并签署交易。 - -
- metadata -
- -### 步骤 2: 保持您的 HDX 质押 - -- 您获得奖励的金额，取决于您质押的 HDX，相对整个质押池的大小。 -- 随着时间的推移，分配给您的大部分奖励，将会被解锁。 解锁率由奖励联合曲线决定。 -- 了解更多信息，请查阅 [质押产品文档](/staking)。 - -### 步骤 3: 提升您的奖励 - -- 收集行动积分，以增加奖励并加快奖励解锁的速度。 -- 您可以通过 **[公投投票](https://hydradx.subsquare.io/democracy/referenda)** 来收集行动积分。 您用于投票的质押 HDX 越多，信念乘数越高，您获得的行动积分就越多。 -- 更多信息可在 [质押产品文档](/staking) 中了解。 - -### 步骤 4: 领取您的奖励 - -- 查看质押统计数据，观察并规划您自己的质押策略 **(5)**。 -- 想要结束质押，可点击 `Claim`（领取），领取您解锁的奖励 **(8)**。 - -
- metadata -
- -:::caution -一旦决定领取解锁的质押奖励，您都会失去其余所有还处于锁定状态的奖励，它们将会被重新分配给所有其他质押者。 此外，您过去的行动积分，也将被重置。 - -例如，如果质押者在获得 75% 的奖励时领取奖励，则剩余的 25% 将被没收。 然后，质押者必须等待相同的时间，才能领取后续批次奖励的 75%。 -::: - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_trade.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_trade.md deleted file mode 100644 index ef54802a3..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_trade.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -id: howto_trade -title: 使用 Omnipool 进行交易 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -本页提供了 **分步指南**，将 **帮您使用 HydraDX Omnipool（万能池）执行您的第一次交易**。 - -HydraDX Omniool 是可释放无与伦比的效率的新一代 AMM，您可以在我们的 **[产品文档](/)** 中找到更多信息。 - -
- metadata -
- -## 00 转移令牌 -如果您想使用非原生资产（例如 DOT 或 DAI）执行交易，您首先需要将这些资产转移到 HydraDX 链上。此步骤不适用于 HDX。 - -有两种不同的机制来转移非原生资产： -* **[跨链传输](https://app.hydradx.io/#/cross-chain)** - 使用此工具，可从其他 Polkadot 平行链或从 Polkadot 自身转移资产。分步指南在 **[这里](howto_xcm)**； -* **[以太坊桥](https://www.portalbridge.com/#/transfer)** - 用于连接以太坊生态系统中的资产。分步指南在 **[这里](/bridge_from_ethereum)**。 - -这些解决方案，也可用于 HydraDX 网络之外的令牌传输。 - -## 01 进入 Omnipool -**[https://app.hydradx.io/#/trade](https://app.hydradx.io/#/trade)** - -## 02 连接您的账户 -点击 `Connect Wallet`（连接钱包）**（上图中的 1 ）** 连接到您的首选钱包。然后，选择您的账户。 - -## 03 执行交易 -HydraDX 的交易界面，可让您直观地执行交易： - -* 选择您打算交易的一对令牌 **（2）**； -* 输入交易的令牌 **（3）**:您可输入您想要支付的令牌数量（如 5000 DAI），您也可以输入想要接收令牌的数量（如 1000 HDX）; -* 如果您想调整滑点偏好，可点击 *设置按钮* **（4）** 完成； -* 要完成交易，点击 `Swap`（互换） **（5）** 并使用您的钱包签署交易。 - -保持流动性，而不是干涸！ - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_wallet_parity_signer.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_wallet_parity_signer.md deleted file mode 100644 index 6fc622df5..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_wallet_parity_signer.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -id: howto_wallet_parity_signer -title: 使用 Parity Signer ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -**[Parity Signer](https://www.parity.io/technologies/signer/)**（奇偶校验签名器）是一个移动应用程序，它可以把您的 IOS 或 Android 设备变成 Polkadot、Kusama 和任何其他基于 Substrate 链的专用硬件钱包。它可以让您保持私钥离线，同时仍能使用二维码以一种物理隔离的方式方便地签署交易。 - -## 设置 Parity Signer -### 在您开始之前：请确保安全 -#### 开始清理 -在安装 Parity Signer 之前，请确保您的手机纯净，如已使用过，请进行出厂设置，且不要安装除 Parity Signer 之外的任何其他应用程序。 - -#### 不要插入 SIM 卡 -如果可能的话，不要打开 WiFi 或者使用安全的 WiFi 连接，最好不要连接其他设备并使用信誉良好的 VPN 提供商来连接、更新设备并安装 Parity signer 应用程序。 - -#### 使用强密码 -为了获得更强的安全性，请为设备和使用设备创建的帐户设置长密码。 - -#### 设置新账户 -不要使用旧的谷歌 ID 或 Apple ID，创建一个专门用于下载更新以及 Parity Signer 的新 ID。对于 Android 设备，最好不要使用 WiFi 或谷歌帐户。我们建议使用一些操作系统加密您的数据，如 **[Lineage O.S](https://lineageos.org)**，如果需要电子邮件，请创建一个新邮箱。或者，您也可以在 IOS 上创建新的 Apple ID 和电子邮件。 - -#### 勿用生物识别 -避免使用指纹扫描、面部识别系统或短数字码，因为它们很容易被利用。请改用强密码。 - -#### 禁用所有信号接收功能 -使用飞行模式，并确保手动禁用所有类似的功能。如果您使用的是 IOS 设备，请将其关闭，以及在 WiFi 设置中请求自动加入网络和热点的功能。包括: - -* 定位服务 -* WiFi（如果需要升级或设置，请在更新后立即禁用） -* 蓝牙 - -#### 退出所有账户 -退出 APP 商店，iCloud 和您加入的任何其他帐户。 - -#### 更新您的设备 -如果您使用 WiFi 更新设备，请记得更新后立即禁用 WiFi，并且仅在安全的环境中使用，最好是通过安全加密的 VPN 通道。更新完成后，忘记 WiFi 网络，以确保您不会自动重新加入。 - -### 安装 Parity Signer -从官方应用商店为您的设备（IOS / Android）安装 Parity Signer。确保您正在下载的应用程序，是由 Parity Technologies 发布的。 - -### 创建一个新账户 -按以下步骤创建新账户。 - -#### 01 添加种子短语 -打开 Parity Signer 应用程序，选择 `New seed`。 -
- metadata -
- -#### 02 备份您的恢复短语 -应用程序将显示您的种子短语。把它写下来，放在安全的地方。 - -
- metadata -
- -完成这些之后，您就可以开始了！您可以在 Parity Signer 中使用您的手机密码或身份验证方法（指纹/面部识别）。 - -:::danger -请确保安全！ - -任何拥有您种子短语的人，都可以访问您的资金，并且对于窃取您种子短语的人没有追索权。 - -为保护您的种子短语，可参考以下建议： -* 不要把您的种子短语做成数字文件保存在任何设备上。 -* 总是选择用纸和笔记录您的种子短语。 -* 把您的种子短语放在安全的地方。 -* 不要向任何人提供您的种子短语，包括客服。 -::: - -### 连接到 Polkadot.js/apps -任何时候，您都可以在 polkadot.js 浏览器扩展程序中添加您的 Parity Signer 帐户，以方便您在 **[polkadot.js 应用程序账户页面](https://polkadot.js.org/apps/#/accounts)** 查看余额及签署事务。 - -#### 在 Polkadot.js 应用程序上 -要添加您的帐户，请打开 polkadot.js 浏览器扩展程序，单击 `+` 并选择 `Attach external QR-signer account`。 - -
- metadata -
- -#### 在 Parity Signer 上 - * 打开底部菜单的 `Keys` 选项卡； - * 从链旁边的下拉菜单中选择您将使用的网络； - * 选择您需要的帐户或子帐户； - * 您会看到一个二维码，您需要用您的设备摄像头扫描。 - -### 添加 HydraDX 链 -要使用 Parity Signer，首先需要向 Parity Signer 添加新链。如果您只想对 Polkadot 或 Kusama 使用 Parity，可跳过此步，继续更新元数据。要添加一条新链，您需扫描带有该链基本信息的二维码。 - -#### 01 获取链规格 -桌面导航至 **https://nova-wallet.github.io/metadata-portal/** ，选择 HydraDX 作为所需的链。然后，点击 `Chain Specs`。 - -
- metadata -
- -#### 02 添加规格 -在您的 Parity Signer 上，点击 `Scanner`（扫描器），扫描二维码并点击 `Add new chain`（添加新链）。 - -## 使用 Parity Signer -:::warning -一定要确保您扫描的二维码，是由可信的验证人签署的。 -::: - -### 签署交易 -为便于使用，我们建议将其添加到 polkadot.js 扩展中。直到更多的链可以直接使用 Parity Signer，这将是桌面应用程序使用它的最佳方式。 - -当使用 Parity Signer 签署交易时，polkadot.js 应用程序将显示二维码。 - -
- metadata -
- -使用 Parity Signer 扫描二维码，然后点击 `Unlock key and sign` （解锁键并签署)。 - -
- metadata -
- -您的 Parity Signer 现在将显示一个二维码。要完成交易的签署，切换回 polkadot.js 应用程序，然后点击 `Scan signature via camera` （通过摄像头扫描签署）。 - -### 更新元数据 -要使用 Parity Signer，您需用最新元数据解码 Parity Signer 中的事务。您可以通过扫描包含此数据的多重部分二维码，来获取元数据，允许 Parity Signer 解码实际交易，并在您签署前正确显示它。这一步，类似于更新分类帐应用程序。 - -#### 01 获取元数据 -桌面导航至 **https://nova-wallet.github.io/metadata-portal/** 并选择所需的链。之后，点击 `Metadata`（元数据）。 - -
- metadata -
- -#### 02 更新 -在您的 Parity Signer 上，点击 `Scanner`（扫描器），扫描二维码更新元数据。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/howto_xcm.md b/i18n/cn/docusaurus-plugin-content-docs/current/howto_xcm.md deleted file mode 100644 index 7fb11f00e..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/howto_xcm.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -id: howto_xcm -title: 跨链转账 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -在本页上，您将找到 **操作跨链转账的分步指南**。 - -跨链转账，允许您将非本地资产从其他 Polkadot 平行链或 Polkadot 本身，转账到 HydraDX 链。 - -目前，HydraDX 支持以下令牌进行跨链转账： -* DOT -* DAI（通过 Acala 虫洞桥） -* HDX - -## 00 前提条件 -在继续之前，请确保您在目标链上有足够数量的令牌来支付费用（ACA 或 DOT）。 - -## 01 导航至跨链转账 -**[https://app.hydradx.io/#/cross-chain](https://app.hydradx.io/#/cross-chain)** - -
- metadata -
- - -## 02 连接您的账户 -点击 `Connect Wallet`（连接钱包），连接到您常用的 Polkadot 钱包。之后，选择您的帐户。 - -## 03 跨链转账 -* 选择源链和目标链； -* 选择您打算转账的资产并输入金额； -* 输入目的地址。它应该会自动填充您的链上地址，您也可以改为另一个地址； -* 点击 `Transfer`（转账），用您的钱包签署交易。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/identity.md b/i18n/cn/docusaurus-plugin-content-docs/current/identity.md deleted file mode 100644 index 270cda850..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/identity.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -id: identity -title: 设置您的身份 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -帐户持有人，可通过提供特定信息并将其存储在链上来设置身份。除此之外，身份信息还可以提交给 HydraDX 注册商进行认证。通过设置并认证身份，有助于验证人及提名人保护其网络信用。 - -:::note -如果您是 HydraDX 整理人，我们 **强烈建议** 您设置身份并通过认证程序。经过认证的整理人似乎更值得信任。 -::: - -## 01 设置身份 {#01-set-identity} -要设置身份，请打开 Polkadot/apps（连接到 *HydraDX* 网络），然后导航到 *My accounts* （我的账户）。或者，直接点击这个链接： -**https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts** - -在帐户页面，找到持有您 HDX 令牌的帐户。然后，点击帐号旁边的三个点（在右侧），并选择 *Set on-chain identity* （设置链上身份）。 - -authorize - -您将看到一个名为 *register identity*（注册身份）的弹窗。在这里，您可以输入以下信息： - -* legal name（法定名称）； -* email（邮件）； -* web（网络）； -* twitter（推特）； -* riot name（roit 姓名）（如果使用 Matrix 信息）。 - -:::note - -所有这些信息都是可选的，您可以有选择地提供。但是，如果您正在运行整理器节点，建议您设置电子邮件，以便在您的节点遇到问题时，方便和您联系。 - -::: - -在弹出窗口的最后一个字段，你可以看到需存入的 HDX 数量，作为存储您身份信息的保证金。以后，一旦决定清除身份信息，您会收回这笔保证金。 - -authorize - -填写完信息后，单击 `Set Identity`（设置身份），并使用 Polkadot.js 浏览器扩展程序对交易进行签名。一旦确认了交易，您的身份就设置好了。 - -## 02 提交身份证明 {#02-verify-identity} -在您设置好身份后，您可以将它提交给网络注册商进行认证。要做到这一点，请打开 Polkadot/apps 并导航到 *Developer*（开发者）> *Extrinsics*（交易）。或者，直接点击这个链接： -**https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics** - -在上一步选择相应 HydraDX 帐户后，您需要填写以下信息： - -* **submit the following extrinsic**（提交下面的外部信息）： 左边选 *identity*（身份）；中间选 *requestJudgement(reg_index, max_fee)*（请求判定）。 -* **regindex**（注册商 ID）: 在这里需要输入您选择的注册商 ID 进行验证。 -HydraDX 有两个注册商：Simon Kraus - HydraSik（ID: **0**）、Jimmy Tudeski - stakenode （ID: **1**） -* **maxFee**（最大费用）：在这里需要输入您愿意用 HDX 支付给注册商的最高费用。费用只有低于您支付最高费用的注册商，才有资格为您认证。 - -若要提交认证请求，请单击 `Submit Transaction`（提交交易）并签署交易。 - -authorize - -请注意，身份认证可能需要一些时间。要查看您的请求状态，导航到 **My accounts**（我的账户）并将鼠标停在显示您身份的部分，您将看到一个显示当前状态的弹出框。 - -## 03 认证结果 {#03-verification-outcome} - -在处理您的认证请求后，注册商将提交以下其中一项判断，该判断将在您的身份状态中显示： - -* **Unknown** - 默认值，尚未开始； -* **Reasonable** - 提供的资料看起来合理，但还没进行深入检查； -* **KnownGood** - 信息正确； -* **OutOfDate** - 信息过去是正确的，现在已过时； -* **LowQuality** - 信息不准确，但可通过修改进行更正； -* **Erroneous** - 提供信息错误，可能存在恶意意图。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/intro.md b/i18n/cn/docusaurus-plugin-content-docs/current/intro.md deleted file mode 100644 index e6c2d9ba1..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/intro.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -id: intro -title: 遇见 Omnipool -slug: / ---- - -HydraDX 是 **旨在为 Polkadot 带来流动性海洋** 的下一代 DeFi 协议。我们的工作工具，是 **HydraDX Omnipool**（万能池）- 一种创新的自动做市商（AMM）模型，通过 **将所有资产合并在一个交易池中** 来 **释放无与伦比的资金效率**。 - -通过 **终结流动性的碎片化**，HydraDX Omnipool 让交易变得更加高效，这是其他 AMM 无法比拟的。得益于 **更低滑点和更少的跃点**，与流动性分散在不同交易池中的典型情况相比，交易者可享受到更高的资本效益（随着 TVL 进一步增加）（**[了解更多](/omnipool_trading)**）。 - -HydraDX Omnipool 的设计，支持 **单边流动性提供** - 任何人都可只为他们喜欢的资产提供流动性，而其余部分将由 Omnipool 负责提供（**[了解更多](/omnipool_lp)**）。在引导成长的早期阶段，为选定资产提供流动性，将获到 **九头蛇农场** 激励 - 随着时间推移，会从交易费用中获得更多奖励（**[了解更多](/omnipool_hydrated_farms)**）。 - -单边提供流动性，对于 **DAO 和其他项目的财政** 来说，是一个特别有诱惑的概念，他们可通过 XCM 无需信任地向 Omnipool 提供资产，并立即融入到资产海洋中。 他们还可以 **通过交易费用建立多样化的 POL**，且没有做市商的隐藏费用（**[了解更多](/omnipool_treasuries)**）。 - -HydraDX Omnipool 具有 **最先进的安全性**：底层代码已经过 **多次审计**，且有一个 **慷慨的漏洞赏金计划**，鼓励 **负责任地披露漏洞**。除此之外，流动性上限、协议费用和熔断机制等尖端机制的组合运用，可以共同确保您提供流动性的安全（**[了解更多](/omnipool_security)**）。 - -经过 **两年多研发**，HydraDX 找到了解决 AMM 另一个痛点 - **无常损失（IL）** 的方法。由于 **结合了非通胀措施**，流动性提供者在向 Omnipool 提供流动性时，将会经受 **更少的 IL**（**[了解更多](/omnipool_impermanent_loss)**）。 - -保持流动性，而不是干涸。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/learn_amm.md b/i18n/cn/docusaurus-plugin-content-docs/current/learn_amm.md deleted file mode 100644 index 2782f1b48..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/learn_amm.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -id: learn_amm -title: 什么是 AMM ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -本文介绍了自动做市商（AMM）及其一些基本概念，例如 **[滑点](#slippage)**、**[流动性供应](#lp)** 和 **[无常损失](#impermanent-loss)**。 - -这些介绍性信息，将帮助您更好了解 HydraDX Omnipool（万能池）背后的机制，您可在我们的 **[产品文档](/)** 中找到相关描述。 - -## AMM 简介 - -为了解释自动做市商（AMM）及其工作原理，我们可以将其与中心化订单薄进行对比。 - -### 订单薄 - -订单簿提供了一种由中心化交易所（CEX）部署的机制，用以促进两种资产间的交易。 用户可在交易所管理的电子清单中下买入或卖出订单。 这个所谓订单簿中的订单，是按价格水平组织的，并随需求变化和订单匹配逐步填写。 - -在中心化背景下，订单簿的局限性显而易见。 - -中央机构“保存”着订单簿，并推动订单匹配进程，这就产生了对中央机构的依赖。 中央机构控制着交易，需要得到参与者的信任。 在交易量大、波动大的时候，中央机构可以决定暂停交易并停止其履行做市的职能。 此外，如果项目方想添加新的可交易资产，须在得到中央机构许可并提前支付费用后，才可让其资产上市交易。 - -### AMM - -自动做市商（AMM），是 DeFi 行业对订单簿的革新。AMM 提供了一种去中心化、无需许可的令牌交易方式，更无需屈服于中央机构的控制。 - -AMM 由持有基础可交易资产可用流动性的流动性池组成。 这种流动性是由用户（所谓“流动性提供者”）提供的，他们这样做的动机是，有可能从池中交易产生的费用中获得奖励。 - -在 AMM 的情况下，任何用户都可以在给定的交易池中执行买入或卖出订单。 交易价格，由确定性算法当场确定。该算法，将交易资产的流动性，与依赖于特定 AMM 实现的其他因素之间的关系，作为输入变量。 - -## 滑点 {#slippage} - -执行交易时，用户可能会遇到 AMM 的常见副作用，即 `滑点`：交易预期价格与交易实际执行价格间的差额。 - -滑点，由交易池中可用的流动性高低决定。 如果为资产提供的流动性较低，则在处理大订单交易时的滑点百分比就会更高。 - -## 提供流动性 {#lp} - -由于 AMM 的去中心化属性，任何人都可以通过存入一定价值的令牌，来换取代表其流动性的仓位，从而成为流动性池的流动性提供者（LP）。 - -流动性提供者提供这种流动性的报酬，来源于其所提供流动性的资产经历的交易活动。 - -## 无常损失（IL）{#impermanent-loss} - -无常损失（IL）是流动性提供者面临的一种风险，它体现了在 AMM 中持有令牌与在钱包中持有令牌之间的价值差异。 - -流动性池，由多个令牌（通常是两个）汇集而成。 当池内令牌价格（与存入时价格）出现差异时，IL 就会发生。 差异越大，流动性提供者的负回报风险就越大。 - -这种风险被称为“无常”，因为只有当流动性从池中撤出时，损失才会产生。 如果池中令牌的相对价格恢复到（令牌存入时）的原始状态，损失将被最小化或消除。 在流动性撤出的那一刻，损失将成为 *永久性的*，从而造成收益减少。 - -因此，流动性提供者需要权衡这两种行为的收益差异：将令牌用于提供流动性赚取费用和奖励，还是简单地放在钱包中。然后，做出自己的选择。 diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/node_monitoring.md b/i18n/cn/docusaurus-plugin-content-docs/current/node_monitoring.md deleted file mode 100644 index 665bdaf68..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/node_monitoring.md +++ /dev/null @@ -1,345 +0,0 @@ ---- -id: node_monitoring -title: 节点监控 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -在本节中，我们将引导您完成整理节点的本地监控。 - -## 前提条件 {#prerequisites} - -您必须启动并运行 **[整理节点](/collator_setup)** 。 - -本指南已在 Ubuntu 20.04 LTS 系统，进行了测试。 - -## Prometheus 设置 {#prometheus-setup} - -在第一步中，我们将设置 Prometheus 服务器。 - -### 用户和目录 {#user-and-directories} - -我们创建一个仅用于监控的用户，该用户没有根目录，无法用于登录： - -```shell script -$ sudo useradd --no-create-home --shell /usr/sbin/nologin prometheus -``` - -然后，我们为可执行文件和配置文件创建目录： - -```shell script -$ sudo mkdir /etc/prometheus -$ sudo mkdir /var/lib/prometheus -``` - -更改目录的所有权，以将其限制为我们的新监控用户： - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus -$ sudo chown -R prometheus:prometheus /var/lib/prometheus -``` - -### 安装 Prometheus {#install-prometheus} - -在 **[GitHub 发布页面](https://github.com/prometheus/prometheus/releases/)** 上检查 Prometheus 的最新版本。 -在撰写本文时，版本是 v2.25.2。 -在以下命令中插入最新发行的版本： - -```shell script -# download prometheus -$ wget https://github.com/prometheus/prometheus/releases/download/v2.25.2/prometheus-2.25.2.linux-amd64.tar.gz - -# unpack the binaries -$ tar xfz prometheus-*.tar.gz - -# enter the unpacked directory -$ cd prometheus-2.25.2.linux-amd64 -``` - -现在，将编译文件复制到本地文件夹中： - -```shell script -$ sudo cp ./prometheus /usr/local/bin/ -$ sudo cp ./promtool /usr/local/bin/ -``` - -现在，我们需要将这些编译文件分配给我们新创建的用户： - -```shell script -$ sudo chown prometheus:prometheus /usr/local/bin/prometheus -$ sudo chown prometheus:prometheus /usr/local/bin/promtool -``` - -接下来，我们将复制 Web 界面和配置预设： - -```shell script -$ sudo cp -r ./consoles /etc/prometheus -$ sudo cp -r ./console_libraries /etc/prometheus -``` - -您可能已经猜到了，我们也要更改这些目录的所有权： - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus/consoles -$ sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries -``` - -现在，我们已从下载的软件包中获取了所需的一切，因此我们将退后一步并进行一些清理： - -```shell script -$ cd .. && rm -rf prometheus* -``` - -让我们使用您选择的编辑器（nano / vim / pico）为 Prometheus 创建一个 `YAML` 配置文件： - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -我们的配置分为三个部分： - -* `global`: 设置 `scrape_interval` 默认值及带有 `evaluation_interval` 的规则执行间隔 -* `rule_files`: 指定 Prometheus 服务器应加载的规则文件 -* `scrape_configs`: 在这里设置监视资源 - -我们将其设置得非常简单，并以这样的方式结束： - -```yaml -global: - scrape_interval: 15s - evaluation_interval: 15s - -rule_files: - # - "weHaveNo.rules" - -scrape_configs: - - job_name: "prometheus" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9090"] - - job_name: "substrate_node" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9615"] -``` - -第一个抓取作业导出 Prometheus 本身的数据，第二个抓取作业导出 HydraDX 节点指标。 我们调整了两个作业的 `scrape_interval` 以获得更详细的统计信息。 这将覆盖全局值。 `static_configs` 中的 `target` 设置导出程序运行的位置，这里我们使用默认端口。 - -保存配置后，我们将再次更改所有权： - -```shell script -$ sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml -``` - -### 启动 Prometheus {#starting-prometheus} - -为了使 Prometheus 自动启动并在后台运行，我们将使用 `systemd` 。创建一个新的配置（同样使用您选择的编辑器）： - -````shell script -$ sudo nano /etc/systemd/system/prometheus.service -```` - -粘贴以下配置并保存文件： - -``` -[Unit] - Description=Prometheus Monitoring - Wants=network-online.target - After=network-online.target - -[Service] - User=prometheus - Group=prometheus - Type=simple - ExecStart=/usr/local/bin/prometheus \ - --config.file /etc/prometheus/prometheus.yml \ - --storage.tsdb.path /var/lib/prometheus/ \ - --web.console.templates=/etc/prometheus/consoles \ - --web.console.libraries=/etc/prometheus/console_libraries - ExecReload=/bin/kill -HUP $MAINPID - -[Install] - WantedBy=multi-user.target -``` - -接下来，我们将执行以下三个步骤：`systemctl deamon-reload` 加载新配置并更新现有配置 `systemctl enable` 激活我们的新服务 `systemctl start` 触发服务执行 - -您可以通过执行以下命令，完成以上步骤： - -```shell script -$ sudo systemctl daemon-reload && systemctl enable prometheus && systemctl start prometheus -``` - -现在，您应该可以在 http：// localhost：9090 / 上访问 Prometheus 的 Web 界面。 - -## Node Exporter（节点导出器） {#node-exporter} - -我们将安装 Node Exporter（节点导出器），来抓取将在仪表盘中使用的服务器指标。 -请在 **[此处](https://github.com/prometheus/node_exporter/releases/)** 检查最新版本的版本号并更新命令。 -在撰写本文时，最新版本为 `1.1.2` 。 - -### 安装 Node Exporter {#install-node-exporter} - -下载最新版本： - -```shell script -$ wget https://github.com/prometheus/node_exporter/releases/download/v1.1.2/node_exporter-1.1.2.linux-amd64.tar.gz -``` - -解压缩刚刚下载的软件包。这将创建一个名为 `node_exporter-1.1.2.linux-amd64` 的文件夹： - -```shell script -$ tar xvf node_exporter-1.1.2.linux-amd64.tar.gz -``` - -接下来，我们将编译文件复制到本地应用程序目录中，并将其分配给我们的监视用户： - -```shell script -# copy binary -$ cp node_exporter-1.1.2.linux-amd64/node_exporter /usr/local/bin - -# set ownership -$ sudo chown prometheus:prometheus /usr/local/bin/node_exporter -``` - -现在，我们可以进行一些清理，并删除下载并解压软件包： - -```shell script -$ rm -rf node_exporter* -``` - -### 创建系统服务 {#create-a-systemd-service} - -与 prometheus 相似，我们希望 Node Exporter 也能作为服务运行。 -使用您选择的编辑器创建系统服务： - -```shell script -$ sudo nano /etc/systemd/system/node_exporter.service -``` - -并将以下配置粘贴进去： - -``` -[Unit] -Description=Node Exporter -Wants=network-online.target -After=network-online.target - -[Service] -User=prometheus -Group=prometheus -Type=simple -ExecStart=/usr/local/bin/node_exporter - -[Install] -WantedBy=multi-user.target -``` - -现在，我们将单线激活并启动该服务： - -```shell script -$ sudo systemctl daemon-reload && systemctl enable node_exporter && systemctl start node_exporter -``` - -### 为 Node Exporter 添加抓取作业 {#add-scrape-job-for-node-exporter} - -Node Exporter 现在已启动并正在运行，但是我们需要授予 Prometheus 权限。 -我们将使用所选的编辑器再次打开配置文件： - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -并且在文件的最底部，我们将追加一个 scrape config。 -粘贴以下内容并保存文件： - -```yaml - - job_name: 'node_exporter' - scrape_interval: 5s - static_configs: - - targets: ['localhost:9100'] -``` - -应用更改配置，需要重新启动 Prometheus 服务： - -```shell script -$ sudo systemctl restart prometheus.service -``` - -现在，您的服务器指标已被抓取，可以在 Prometheus Web 界面中找到。 -我们稍后将需要它们用于仪表盘。 - -## Grafana 设置 {#grafana-setup} - -我们可以在 Web 界面中查看指标，但这不是我们想要的监视方式。 -我们希望它好看又简洁， Grafana 能帮我们做到这些。 - -### 安装 Grafana {#install-grafana} - -请通过 **[此链接](https://grafana.com/grafana/download?platform=linux)** 检查最新的 Grafana 版本。 -您可以在以下命令中更改版本号，也可以直接从链接复制安装命令。 -在撰写本文时，最新版本为 `7.5.1` 。 - -```shell script -$ sudo apt-get install -y adduser libfontconfig1 -$ wget https://dl.grafana.com/oss/release/grafana_7.5.1_amd64.deb -$ sudo dpkg -i grafana_7.5.1_amd64.deb -``` - -该软件包带有内置的 `systemd`-service ，我们将像 Prometheus 服务一样配置和启动： - -```shell script -$ sudo systemctl daemon-reload && sudo systemctl enable grafana-server && sudo systemctl start grafana-server -``` - -### 访问 Web 界面 {#accessing-the-web-interface} - -我们将能够在 http://localhost:3000/ 上打开 Grafana Web 界面。 -默认登录 Grafana 为： -User: `admin` -Password: `admin` - -
- -
- -### 配置数据源 {#configuring-the-datasource} - -请点击菜单中的设置（齿轮按钮），然后选择数据源。 -在下一个窗口中，单击 `Add Datasource`，然后选择 *Prometheus* 。 - -在下表中，您无需更改 URL。 -设置 `http://localhost:9090/`，然后单击 `Save and Test`。 - -
- -
- -### 导入仪表盘 {#importing-the-dashboard} - -请单击主导航中的 `Plus` 按钮，然后选择 `import`： - -
- -
- -我们将使用 **[HydraDX Dashboard（仪表盘）](https://grafana.com/grafana/dashboards/14158)** 进行加载，您只需输入id `14158` 并点击 `Load` 按钮即可加载它： - -
- -
- -您在这里不需要太多配置，只需确保将 Prometheus 用作数据源即可。 -您现在可以完成导入： - -
- -
- -现在，您应该立即看到仪表盘。 -如果某些面板是空的，请确保您在面板上方的选择是这样的： -* `Chain Metrics`: Substrate -* `Chain Instance`: localhost:9615 -* `Server Job`: node_exporter -* `Server Host`: localhost:9100 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/node_setup.md b/i18n/cn/docusaurus-plugin-content-docs/current/node_setup.md deleted file mode 100644 index bf3453b58..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/node_setup.md +++ /dev/null @@ -1,138 +0,0 @@ ---- -id: node_setup -title: 搭建 HydraDX 节点 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -本节将引导您搭建及运行 HydraDX 验证节点。 - -:::warning - -保证验证节点在线运行时间，运行并合理设置节点，需要一定的技术知识。如果对相关技术知识不是很了解，我们建议您把令牌以 **[提名](/start_nominating)** 的方式质押给有经验和技术的验证人。如此一来，您可以同时保护自己和可能质押您节点的提名人免受非自愿损失。 - -::: - -## 00 基本性能要求 {#00-required-technical-specifications} - -以下是运行验证节点的硬件及系统的基本性能要求： - -* 系统：Ubuntu 20.04； -* CPU：Intel Core i7-7700K @ 4.5Ghz (或同等单核性能)； -* 内存：64GB RAM； -* 硬盘：NVMe SSD ≥200GB (随着链的增长，数据会越来越多)。 - -:::note - -以上是运行验证节点的最低要求。如果您不确定自己的计算机是否满足要求，请您做 **[基本性能测试](/performance_benchmark)** 。 - -::: - -## 01 确保系统时间同步 {#01-check-whether-your-system-clock-is-synchronized} - -在运行验证节点之前，请确认您的系统时间已经与网络同步。所有的验证节点是在同步工作的，因此这一步很关键。Ubuntu 20.04 的时钟默认是与网络同步的，如要验证，执行以下命令，并检查输出： - -```bash -$ timedatectl | grep "System clock" -System clock synchronized: yes -``` - -如果输出不一样，那么您可以手动安装 NTP，并再次验证您的系统时钟是同步的： - -```bash -$ apt install ntp -$ ntpq -p -``` - -## 02 调整防火墙设置 {#02-adjust-your-firewall-settings} - -端口 `30333` 是 Hydradx 用于网络所有节点服务器的 P2P 服务。如果您的计算机是以验证人的身份运行的，我们建议把防火墙设置为仅可以此端口用于远端访问。 - -如果您的机器 *不* 用作验证节点，那您可考虑同时打开端口 `9944`（用于 RPC Websocket 服务）和端口 `9933`（用于 HTTP 服务）。您可以使用端口 `9944` 通过 **[Polkadot/apps](/polkadotjs_apps_local)** 连接到您的节点。 - -## 03 下载或安装编译文件 {#03-download-or-build-a-binary} -您可以在 **[GitHub](https://github.com/galacticcouncil/HydraDX-node/releases)** 上下载最新的编译文件。 - -或者您可以用以下代码自己构建： - -```bash -# Install dependencies -$ curl https://getsubstrate.io -sSf | bash -s -- --fast - -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable - -# Build the binary -$ cd HydraDX-node/ -$ cargo build --release -``` - -如果您是用以上代码来构建的，您的编译文件就在： -``` -target/release/hydra-dx -``` - -## 04 运行编译文件 {#04-run-the-binary} -您可以通过以下命令来运行编译文件： - -```bash -$ {PATH_TO_YOUR_BINARY} --chain lerna --name {YOUR_NODE_NAME} --validator -``` - -:::note - -验证节点需要完整的数据链。如果您之前设置过节点并没有开启 `--validator` 的话，在加入并运行您的验证节点之前需要重置及更新数据链： -```bash -$ {PATH_TO_YOUR_BINARY} purge-chain --chain lerna -``` - -::: - -在运行编译文件前，您需要为您的节点起名，这个名称将会和所有在 Hydradx Snakenet （蛇网）运行的节点一起，在 **[遥测页面](https://telemetry.hydradx.io/#/HydraDX%20Snakenet%20Gen2)** 中列出。 - -## 05 将程序设置为开机自动运行 {#05-running-with-systemd} -我们建议将 Hydradx 节点加入系统服务，以避免重启后程序不会自动开启。为此，请创建以下文件，并替换 `{VARIABLE}` 中的变量为您的节点名称： - -```bash -$ touch /etc/systemd/system/hydradx-validator.service -``` - -``` -[Unit] -Description=HydraDX validator - -[Service] -Type=exec -User={UNIX_USER} -ExecStart={PATH_TO_YOUR_BINARY} --chain lerna --name {YOUR_NODE_NAME} --validator -Restart=always -RestartSec=120 - -[Install] -WantedBy=multi-user.target -``` - -:::note -建议设置 RestartSec，如果发生崩溃，它会延迟节点的重新启动。延迟重启，为计算机将所有非持久性数据（如共识投票）写入磁盘，预留了时间。如果在程序崩溃后立即重启节点，可能会导致混乱或二次签名，从而触发责罚机制。 -::: - -在将 Hydradx 设置为系统运行程序后，可以通过以下代码与程序交流： - -```bash -# Start the node at system boot -$ systemctl enable hydradx-validator.service - -# Start the node manually -$ systemctl start hydradx-validator.service - -# Check the status of the node -$ systemctl status hydradx-validator.service - -# Check the logs of the node -$ journalctl -f -u hydradx-validator.service -``` - -恭喜您，现在您已经完成验证节点搭建并正在运行！ - -接下来前往 **[开始验证](/start_validating)** ，完成剩下的步骤。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_dca.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_dca.md deleted file mode 100644 index 6f243e9c3..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_dca.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -id: omnipool_dca -title: DCA 交易 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -**[HydraDX DCA](https://app.hydradx.io/dca)** 和 **[拆分交易](https://app.hydradx.io/trade)** (简易 DCA) ，是两个用户友好型功能，允许交易者在 Omnipool 中进行交易时，以无需许可和非托管的方式，实施美元成本平均（DCA）策略。 - -按照 DCA 策略，订单不是一次下达，而是分成较小的交易后定期执行。通过这样做，交易员可以保护自己免受价格波动的影响，并获得平均价格。此外，将大订单分成较小的块，滑点会减少。 - -HydraDX DCA 有两种实现方式 - **[完整功能 DCA](#hydradx-dca)** 和 **[拆分交易](#split-trade)**（简易 DCA），您可在主交易页面上找到它们。 往下，您可以了解这些功能的更多有关信息。 - -如果您正在寻找分步指南，请查看 **[下达 DCA 订单指南](/howto_dca)**。 - -## HydraDX DCA {#hydradx-dca} - -**[HydraDX DCA](https://app.hydradx.io/dca)** 提供了直观的 UI，用户可以在 Omnipool 中微调 DCA 订单。 - -在设置订单时，用户可以指定他们想花费的资产 A 数量，以获得资产 B，以及交易频率 - 以小时（近似值）或区块（更精细）为单位。 - -下达订单后，HydraDX DCA 托盘，确定会按照指定的时间间隔安排交易，直到预设数量的资产 A 被花完。支持下达多个并列执行的 DCA 订单。 - -用户可在 UI 上跟踪订单状态。未平仓的订单，可随时终止剩余的金额。 - -
- -
- - -## 拆分交易 (简易 DCA) {#split-trade} - -**[拆分交易](https://app.hydradx.io/trade)** 是在交易页面上更加直接简单地实现 DCA。它为用户提供了“一键”解决方案，用于拆分较大的订单，以保护自己免受滑点影响。 - -激活后，拆分交易会将订单分割成更小的块，直到交易规模小到可以实现 < 0.1% 的滑点（这仅是估计 - 未来确切的交易滑点，永远无法预测）。 - -用户可以随时终止执行中的拆分交易订单，就像常规的 DCA 订单一样。 diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_design.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_design.md deleted file mode 100644 index f002c355a..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_design.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -id: omnipool_design -title: Omnipool 设计 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -HydraDX Omnipool（万能池）是一种新型的 AMM，它将所有流动性集中在一个交易池中，从而提高了一系列效率。本文档包含 Omnipool 的机制的理论规范。 - -## Omnipool - -### 枢纽令牌 - -Omnipool 使用 LRNA 作为“中枢”令牌，通过它链接所有交易，避免了传统 AMM 因需要为一对令牌提供流动性造成的流动性碎片化。 交易费用和部分无常损失补偿都以 LRNA 支付。 - -### 符号定义 - -在本节中，我们把 $A$ 数量上的一些变化称为 $\Delta A$。当 $A$ 是池变量（如池中某些资产的数量）时，我们约定：如果池变量正在减少（如一些资产正在离开池），则 $\Delta A$ 是负值；相反，如果池变量正在增加（如一些资产正在进入池），则为正值。特别要注意的是，当我们考虑将一种资产的 $\Delta A$ 换成另一种资产的 $\Delta B$ 时，这意味着其中一个将为负值。 - -与此同时，约定一个变量 $s$，流向用户的用 $+\Delta s$ 表示，而从用户流出的用 $-\Delta s$ 表示。特别是对于某些令牌转入/转出池，我们将有 $\Delta t = -\Delta T$。 - -我们还采用以下符号约定 $A^+ = A + \Delta A$。 - -### 执行交易 - -在版本 1 中，价格表现得好像每个 TKN1/LRNA 池都是一个不变的结果 CFMM，尽管其他的 CFMM 仍在研究分析中。 - -设 $Q_1$ 为 TKN1 池中 LRNA 的数量，$T_1$ 是 TKN1 的数量。假设交易者规定他们希望为 TKN2 出售 TKN1 的 $\Delta T_1$，那么 $Q_1 T_1 = Q_1^+ T_1^+$，所以有了资产费用 $f_A$ 和协议 /LRNA 费用 $f_P$，我们有： - -$$ -\Delta Q_1 = Q_1 \frac{-\Delta T_1}{T_1^+}\\ -\Delta Q_2 = -\Delta Q_1 (1 - f_P)\\ -\Delta T_2 = T_2 \frac{-\Delta Q_2}{Q_2^+} (1 - f_A)\\ -$$ - -LRNA 或“协议”费是 $- f_P \Delta Q_1$（此为正值，因 $\Delta Q_1$ 为负值)，资产费是 $- f_A T_2 \frac{-\Delta Q_2}{Q_2^+}$ 。 - -### 为 Omnipool 提供流动性 -流动性提供者（LPs）可以提供单一资产，作为回报他们可以获得该资产池权益的一部分。 当 LP 移除流动性时，他们可能会同时收到他们提供的资产和 LRNA。 -某些 TKN 的单一资产流动性提供者，不能总是只获得他们贡献的令牌，因为如果 TKN 的价格上涨且大量的 TKN 离开池子，TKN 的 LP 将共享一个更小的池子。 与此同时，该协议有大量的 LRNA 已被交易为 TKN。 该协议不是简单地让 LP 承担损失，而是将匹配池与 LP 分开。 如果 TKN 的价格上涨（通过将 LRNA 交易到 TKN 池中），LP 有权获得部分 LRNA。 另一方面，如果 TKN 的价格下降（通过将 TKN 出售给 LRNA 池），协议有权获得一些 TKN。 - -令 $p$ 为 TKN 的当前价格，$p_0$ 为 LP 最初提高流动性时的价格，$\Delta s$ 是 LP 希望提取的权益数量，$B$ 为协议拥有的 TKN 权益数量。请注意，由于当流动性移除时权益被销毁，$\Delta s < 0$。 - -如果 TKN 的价格下降了（$p < p_0$），LP 将仅提取 TKN（无 LRNA）。该协议将从他们那里拿走一些 TKN 份额，而一些份额将被销毁。 -我们首先计算 TKN 协议份额所有权的变化： - -$$ -\Delta B = max\left(-\frac{p_0 - p}{p + p_0} \Delta s, 0\right) -$$ - -请注意，如果 $p < p_0$ （TKN 的价格已经下跌），$\Delta B$ 为正值, 这意味着该协议正在从 LP 那里索取部分 $\Delta s$ 权益。如果 $p > p0$，协议就不向 LP 索取任何资产权益。 - -接下来，我们找到要销毁的权益数量: -$$ -\Delta S = \Delta s + \Delta B -$$ -然后我们可以计算出 LP 收到的 TKN 总量，这是成比例的: -$$ -\Delta T = T \frac{\Delta S}{S}\\ -\Delta t = -\Delta T -$$ -如果 $p > p_0$，很多 LRNA 被交易到 Ominipool 来换取 TKN，所以协议有额外的 LRNA 去给 LP。总的来说， -$$ -\Delta q = - p \left(\frac{2p}{p + p0} \frac{\Delta s}{S} T + \Delta t\right)\\ -\Delta Q = Q \frac{\Delta T}{T} -$$ -请注意，由于 $\Delta Q \neq -\Delta q$，没有分配给正在提取流动性的 LP 的 LRNA 被协议销毁。 - -### 单一资产流动性提供者的暂时性损失 -鉴于上述机制，单个资产 LP 的“无常损失”是 -$$ -\frac{2\sqrt{p p_0}}{p_0 + p} - 1 -$$ -单一资产 LP 仅对 TKN/LRNA 价格敏感，对 Omnipool 中其他令牌的价格不敏感（间接通过 LRNA 除外）。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_hydrated_farms.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_hydrated_farms.md deleted file mode 100644 index ebce71bba..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_hydrated_farms.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -id: omnipool_hydrated_farms -title: 九头蛇农场 ---- - -九头蛇农场是一种有时间限制的激励计划，除了交易费奖励外，还为特定资产提供流动性，提供了额外奖励。 - -与传统流动性挖矿项目不同，九头蛇农场有几个独特的功能：使用 **[农场 NFT](#farm-nfts)** 代表农场位置，支持 **[奖励叠加](#rewards-stacking)** ，并且基于 **[忠诚度系数](#loyalty-multiplier)** 的奖励，会随时间推移而增长。 - -在本页，您可以找到更多关于九头蛇农场的细节。如果想参与，请访问我们的 **[九头蛇农场分步指南](/howto_hydrated_farms)**。 - -## 农场 NFT {#farm-nfts} -当用户向 Omnipool（万能池）提供流动性并加入一个九头蛇农场时，HydraDX 协议将为其生成一个特有的 NFT。该 NFT 代表了用户在农场中的位置，并存储了某些详细信息，如：进入的时间。这使得协议能够提供可持续的激励，且奖励会随着时间推移而增长。 - -农场 NFT 所有者，控制着农场中的头寸，以及 Omnipool 的基础流动性。 未来，协议的利益相关方，可能会决定开放农场 NFT 市场，或将其用作抵押品。 - -:::note -由于农场 NFT 的独特属性，多次加入特定农场，将产生多个 NFT。 -::: - -## 奖励叠加 {#rewards-stacking} -九头蛇农场支持提供多种资产奖励的可能性。换句话说，奖励是可以叠加的。 - -任何团队都可以联系 HydraDX 的利益相关者，请求创建一个由自己 TKN 激励的九头蛇农场。 按照此例，HydraDX 通过治理还可以决定，提供 HDX 作为该农场的激励措施。 因此，九头蛇的农场主们，将同时获得 HDX 和 TKN 奖励。 - -## 忠诚度系数 {#loyalty-multiplier} -为了鼓励更可持续的流动性供应，九头蛇农场引入了忠诚度系数 - 随着流动性持续留在农场，奖励会随时间推移而增长。您可在农场详情页面，查看具体的奖励分配曲线。 - -一旦用户决定离开农场，他们的忠诚度系数就会重置。如果重新加入，忠诚度系数将从基础级别重新开始。 diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_impermanent_loss.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_impermanent_loss.md deleted file mode 100644 index 1a88a692b..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_impermanent_loss.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -id: omnipool_impermanent_loss -title: 减少无常损失 ---- - -:::note -这一部分的 HydraDX Omnipool（万能池）文档，正在构建中... 🚧 -::: diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_lp.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_lp.md deleted file mode 100644 index 800c92a23..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_lp.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -id: omnipool_lp -title: 单边提供流动性 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -HydraDX Omnipool（万能池）的尖端设计提供了单边流动性供应的可能性：任何人都可以只为他们想要的资产提供流动性，而且数量不限（不超过 Omnipool 设定的资产 TVL 上限）。 这根除了标准 XYK AMM 的一个主要痛点：流动性提供者（LP）必须存入一对等价值的资产。 - -HydraDX Omnipool 的流动性是集中的，这意味着通过提供资产，您可以获得在 Omnipool 中所有其他资产面前即时曝光的机会。请忘掉流动性碎片化和将流动性分散到多个交易池的需求吧！ - -## 枢纽令牌 LRNA - -我们的枢纽令牌 Lerna（LRNA）让提供单边流动性成为可能。 每次增加流动性时，Omnipool 都会铸造相应数量的 LRNA 以保持池的平衡。同理，LRNA 销毁，将被用于反映任何流动性的去除。 这些机制确保了在 Omnipool 中添加或移除资产时，LRNA 的价值不会出现明显波动。 - -
- login -
- - -理解枢纽令牌概念的另一种方法是，将 Omnipool 中的每项资产，想象成为一个合成的 50/50 流动性资产对池。唯一的区别，是该资产对的“第二条腿”，始终是 LRNA，即 TKN:LRNA。 - -这种设计允许协议以 LRNA 为代理，以抽象的方式反映 Omnipool 中锁定的价值，包括交易活动和价格波动。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_security.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_security.md deleted file mode 100644 index af53c146e..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_security.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -id: omnipool_security -title: 最先进的安全性 ---- - -HydraDX 协议采用多层安全策略，该策略专为确保您的资金安全量身定制。HydraDX Omnipool（万能池）背后的概念，以及它们在 Rust 中的运行时实现，都经过了 **[严格的审计](#audits)**。我们防御策略的第二层，是慷慨的漏洞赏金计划，奖励负责任的漏洞披露。 最后，还有一系列措施共同来 **[保护您的流动性](#protecting-liquidity)**（抵御有毒资产或黑客攻击等不幸事件）。 - -## 审计 {#audits} - -对 HydraDX Omnipool 的 Rust 实现安全审计，是由 **[Runtime Verification](https://runtimeverification.com/)** 执行的。 Runtime Verification 是知名的行业领导者，客户包括 NASA、Ethereum 和 Polkadot。安全审计的范围包括 **[HydraDX Omnipool pallet](https://github.com/galacticcouncil/HydraDX-node/blob/master/pallets/omnipool/src/)** 源代码，及其 **[数学逻辑](https://github.com/galacticcouncil/HydraDX-math/tree/main/src/omnipool)** 和 **[资产注册表](https://github.com/galacticcouncil/warehouse/tree/main/asset-registry)**，以及作为（Substrate）依赖项包含的第三方库。 审计结果于 2022 年 9 月公布，您可以在 **[此处](https://github.com/galacticcouncil/HydraDX-audit-reports/blob/main/220907-Runtime-Verification-Security-Audit.pdf)** 查阅完整报告。 - -2022 年 3 月，Omnipool 的经济/数学审计由 **[BlockScience](https://block.science/)** 完成。 BlockScience 是一家领先的 web3 原生公司，致力于为 Graph Protocol 和 Protocol Labs（Filecoin）等分析复杂系统。本次审计的范围是概述 AMM 规范，特别关注支撑 Omnipool 的数学和经济概念，以及这些机制对流动性供应和交易活动的影响。 您可以在 **[此处](https://github.com/galacticcouncil/HydraDX-audit-reports/blob/main/220322-BlockScience-Omnipool-Report%2Baddendum-by-HydraDX.pdf)** 查阅完整报告，包括我们事后整改的附录。 - -## 漏洞赏金计划 {#bug-bounties} - -HydraDX 正在与区块链安全领域的另一行业领导者 **[Immunefi](https://immunefi.com/)** 合作， 建立一个全面的激励系统，奖励负责任的漏洞和潜在漏洞披露行为。 - -基于 **[Immunefi 漏洞严重程度分级系统 V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/)**，根据漏洞的影响进行奖励分配。这是一个简化的 5 级量表，网站/apps、智能合约和区块链/分布式账本技术具有单独的量表，重点关注所报告漏洞的影响。 - -我们正处在设置漏洞赏金计划的最后阶段，很快就会有更多信息。 - -## Omnipool 流动性保护机制 {#protecting-liquidity} - -我们花了一年多的时间研究和设计机制，这些机制将在以下不幸情况下（并非不可能）被激活：参与者试图通过滥用有害资产（类似 LUNA 的情况）或一些恶意利用，来耗尽 Omnipool 的流动性。 我们提出了一系列措施并进行整合，建立了行业领先的安全标准。 - -其中一项措施，是 *TVL 上限*（又名 Omnipool 权重），它定义了为特定资产提供流动性相对于池中其他所有资产的最大比例。 TVL 上限，将依据 HydraDX 民主决策流程对每项资产进行设置。 与新项目令牌相比，为 DOT 或 DAI 等已上市资产设置更高的上限，是合理的。 这将限制潜在的流动性攻击可能会造成的损害。 - -另一种防御机制，是 *目标函数暂停*。通过这一机制，HydraDX 技术委员会可暂停调用我们 pallet 特定函数的交易，以便我们能够做出快速反应（如暂停提款）从而保护 Omnipool 的流动性。 - -以上这些，只是我们已经实施的一些机制。 作为未来迭代的一部分，我们正在研究和开发其他的机制，例如可靠的预言机、动态费用（在累积 POL 的同时，降低砸盘的经济效益）、自动交易节流和其它熔断机制的使用。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_trading.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_trading.md deleted file mode 100644 index 8a711fcc9..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_trading.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -id: omnipool_trading -title: 高效交易 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -传统 DeFi 系统的特点是流动性分散化，即：流动性分散在多个交易池中。这个系统跃点较多，流动性较浅，导致价格影响变大滑点升高、经济效率低下。HydraDX Omnipool（万能池）通过将所有流动性合并到一个交易池中，实现了其它 AMM 无法比拟的高效率交易。 - -## 传统 AMM：流动性碎片化 - -先驱 XYK AMM 的出现，标志着 DeFi 领域一个关键时刻的到来，因为它让去中心化和无需许可交易成为了可能。 简单的 XYK 池，对 DeFi 初期的广泛采用，起到了促进作用。但时值今日，我们不得不面临这样一个局面： XYK 模型低下的经济效率，已经阻碍了 DeFi 应用的进一步发展。 - -
- Omnipool -
- -XYK 模型的缺陷之一，是交易池只能由成对的资产构成。 流动性碎片化，导致更大的价格影响和更高的跃点和滑点。 上面截图 ETH-AAVE 的交易路线，为我们提供了一个生动的例子： -- 85% 的交易，将 ETH 直接交换成 AAVE（产生 0.3% 的费用）; -- 余下的 15% 交易，则要先将 ETH 交换成 UNI，然后再将 UNI 交换为 AAVE（在两个交易池里分别产生了 0.3% 的交易费用）。 - -## HydraDX Omnipool：统一流动性 - -得益于 Omnipool 的尖端设计，流动性才真正发挥出它应有的作用。 通过 LRNA 连接所有流动性，Omnipool 的任一资产，可直接访问池中所有资产统一形成的全部流动性，且与链上执行无缝衔接，交换在一次交易中完成，无需在彼此独立的交易池中间进行任何跳转。 - -此外，根据内在研究，随着 Omnipool 令牌数量和锁定价值（TVL）的不断增加，对于滑点的减少将呈指数级改善。 - -
- login -
- -举个例子（如上图），假设资产 TKN 分布在 4 个不同的流动池中，4 池流动性水平各不相同。 交易者如果想用（少量的）DAI 交换 TKN，他们可选择拥有 100 万美元流动性的 TKN-DAI 池。 但如果交易规模加大，如 10 万美元以上，大部分的交易，可能要先通过 DAI-ETH 池，然后是传统 XYK 环境的 TKN-ETH 池来完成。 - -然而，对于 HydraDX Omnipool，同样的 500 万美元 TKN 资产（1000 万美元 TVL 的 50%）和 300 万美元 DAI，将会集中到一个池子里。 如果交易者在 Omnipool 中执行以上相同的交易，他们将享受由 500 万美元 TKN 和 300 万美元 DAI 所形成的全部流动性效益，并在一次交换中完成交易，整体上的价格影响将大大降低。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_treasuries.md b/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_treasuries.md deleted file mode 100644 index 579038c96..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/omnipool_treasuries.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -id: omnipool_treasuries -title: 让您的财政苏醒（B2B） ---- - -HydraDX Omnipool（万能池）对任何项目或 DAO 的财政，都有明确的价值主张。 忘掉中心化做市商和流动性挖矿的通膨奖励吧！Omnipool 可以用更经济高效的方式，为您的令牌创建市场 - 无需信任，没有隐藏成本，同时通过交易费用建立您的 POL。 - -得益于其尖端的设计，HydraDX Omnipool 支持 **[单边提供流动性](/omnipool_lp)**。 与其浪费地分配流动性挖矿奖励来激励其他用户提供流动性，项目和 DAO 可以将部分资金存入 Omnipool，并获得 **在流动性海洋中所有其他资产面前** 的即时曝光机会：多样化和深度（HydraDX 有 2000 万美元 POL 正在逐步部署）。 - -HydraDX Omnipool 的流动性提供，是 **真正地**、**无需许可** 的。利用 Polkadot 独特的 **跨链通信（XCM）** 功能，Omnipool 使您能够始终控制自己的资金：您既可以提供流动性，也可以在不依赖第三方的情况下进行资金管理。 - -为 HydraDX Omnipool 提供流动性，不仅具有成本效益，而且还 **有利可图**。与其让您的令牌闲置在财政中，不如让它们发挥作用。 您将会 **从交易费中获得奖励**，还可随时间推移 **建立 POL**。很快，我们会推出 **TWAMM/DCA** 功能，将允许您 **把累积的 POL 分散** 到其他资产中（例如，美元稳定币或 DOT，您可用它来竞标下一个平行链插槽）。 - -最后，HydraDX Omnipool 享有最先进的安全性。 除了严格的审计和慷慨的漏洞赏金计划外，我们还制定了一系列措施，共同确保您的流动性安全。 点击 **[这里](/omnipool_security)** 了解更多。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/participate_in_council_elections.md b/i18n/cn/docusaurus-plugin-content-docs/current/participate_in_council_elections.md deleted file mode 100644 index fd97efb76..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/participate_in_council_elections.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -id: participate_in_council_elections -title: 参与议会选举 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -本文提供了关于如何参与议会选举的分步指导： 为议会成员投票和成为议会候选人。 - -如果您对选举如何进行感兴趣，请阅读 **[此文章](/democracy_council#elections)**。 - -:::caution -HydraDX民主选举将在 **2021 年 9 月 15 号** 后上线，请勿在此日期前尝试任何显示的操作。 -::: - -## 使用 Polkadot/apps {#polkajs} - -### 在议会成员选举中投票 {#polkajs-vote} -您将在 **[*Governance*（治理）> *Council*（议会）页面](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council)** 中看到现有议员及候选者。 - -要为议会成员投票，请单击 `Vote`（投票）。 - -
- -
- -输入您愿意锁定以支持候选人的令牌数量。 - -之后，通过将候选人从左侧列表移到右侧列表，按偏好顺序选择您的候选人。 记住选择多个候选人 - 这将有助于算法选择最佳候选人分配给议会。 - -要投票，请单击 `Vote`（投票）并签署交易。 - -:::note -锁定的令牌不可转账，但仍可用于质押和公投投票。直到你手动解锁令牌之前，您的令牌将被锁定并用于下次的选举。 -::: - -### 申请成为议会候选人 {#polkajs-become_candidate} -您可以通过导航到 Polkadot/apps 中的 **[*Governance*（治理）> *Council*（议会）](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council)** 来提交您的议会成员申请。 - -单击 `Submit candidacy`（提交候选资格），这将触发一个弹出窗口。 - -
- -
- -选择正在运行的议会成员账户，点击 `Submit`（提交）并签署交易。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/participate_in_referenda.md b/i18n/cn/docusaurus-plugin-content-docs/current/participate_in_referenda.md deleted file mode 100644 index 615a1dd75..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/participate_in_referenda.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -id: participate_in_referenda -title: 参加公投 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -这篇文章提供了关于如何参与公投的分步指南：投票和提案。为此，您可以选择使用两种工具：**[Commonwealth.im](#cw)** 或 **[Polkadot/apps](#polkajs)**。 - -在您决定参与之前，我们强烈建议您通读“学习/民主”部分中的 **[知识文章](/democracy_referenda)** 。在那里你会找到一些关于公投背后机制的重要细节。 - -:::caution -HydraDX 民主模块将于 **2021 年 9 月 15 日** 或之后推出。请不要在该日期之前尝试任何显示的操作。 -::: - -## 使用 Commonwealth.im {#cw} - -### 在公投中投票 {#cw-vote} -您可以通过导航到 HydraDX Commonwealth 页面上的 **[公投选项卡](https://commonwealth.im/hydradx/referenda)** 来查看所有可供投票的公投。 - -要对正在进行的公投进行投票，您需要单击它。之后，您将看到一个显示所有相关详细信息的页面。 - -在 *Cast Your Vote* （投您的票）部分，填写以下信息： - -* Amount to vote （投票数量）- 这是您愿意锁定以支持公投的 HDX 令牌数量 -* Conviction multiplier （信念系数）- 这是共同决定您 **[投票权重](/democracy_referenda#referenda-votes-weighing)** 的系数。 - -之后，通过单击 `Vote yes`（投票是）或 `Vote no`（投票否）并签署交易进行投票。 - -### 提出公投提案 {#cw-propose} -要提出公投，请访问 **[HydraDX Commonwealth 页面](https://commonwealth.im/hydradx/)**，然后单击顶部菜单中的 *New Thread*（新帖子）> *New democracy proposal*（民主新提案）。 - -
- -
- -在上面显示的字段中填写信息。最重要的参数是： -* Module（模块） -* Function（功能） -* 您提议调用的函数指定的任何附加信息 -* Deposit（存款）- 您愿意为支持该提案而存入的 HDX 令牌数量 - -在上面的例子中，Module（模块）是 *余额*，而 Function（功能）是 *设置余额*，用于修改一个给定帐户的自由和储备余额。 - -要提交提案，请单击 `Send transaction`（发送交易）并使用您的钱包签名。 - -在链上提交提案并签署交易后，您的提案应出现在 **[提议公投列表](https://commonwealth.im/hydradx/referenda)** 中。 - -:::caution -每个投票期间，获得最高支持（*附议* ）的公投提案进入投票轮次。随着公投数量的增加，无法保证您的提案将获得足够的支持以进入投票。无法撤回公投提案，这意味着您的资金可能会被长期锁定。 - -恶意公投提案受到惩罚。HydraDX 议会和技术委员会有权取消任何恶意提出的公投。结果是存入的令牌将被烧毁。 -::: - -## 使用 Polkadot/apps {#polkajs} - -### 在公投中投票 {#polkajs-vote} -您可以通过导航到 Polkadot/apps 中的 **[*Governance*（治理）> *Democracy*（民主）](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy)** 来查看所有公开投票的公投。 - -要在公投中投票，请单击旁边的 `Vote`（投票）按钮。 - -在弹出窗口中，填写以下信息： - -* Vote value（投票值） - 这是您愿意锁定以支持公投的 HDX 令牌数量 -* Conviction multiplier（信念系数） - 这是共同决定您 **[投票权重](/democracy_referenda#referenda-votes-weighing)** 的系数 - -之后，通过单击 `Vote Nay`（否） 或 `Vote Aye`（是）来投票并签署交易。 - -### 提出公投 {#polkajs-propose} -通过 Polkadot/apps 提出公投包括两个步骤：提交原像，以及在链上提交提案。 - -#### 01 提交原像 {#polkajs-propose-01} -要提交原像，请访问 Polkadot/apps 并导航至 **[*Governance*（治理） > *Democracy*（民主）](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy)**。 - -单击 `Submit preimage`（提交原像）后，您应该会看到以下弹出窗口： - -
- -
- -在上面显示的字段中填写信息。最重要的参数是： -* 发送提案的帐户 -* 提案范围 -* 提案操作 - -在上面的例子中，提案范围是 *余额* ，操作是将令牌从一个帐户 *强制转移* 到另一个帐户。 - -在提交原像并签署交易之前，请确保复制原像哈希以在下一步使用它。 - -#### 02 提交提案 {#polkajs-propose-02} -要提交公投提案，请访问 Polkadot/apps 中的 **[*Governance*（治理）> *Democracy*（民主）](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy)**。 - -单击 `Submit proposal`（提交提案）后，您应该会看到以下弹出窗口： - -
- -
- -输入上一步中的原像哈希值，以及您愿意为提案存入的令牌数量。最低为 10,000 HDX。 - -在链上提交提案并签署交易后，您的提案应出现在提议的公投列表中。 - -:::caution -每个投票期间，获得最高支持（*附议* ）的公投提案进入投票轮次。随着公投数量的增加，无法保证您的提案将获得足够的支持以进入投票。无法撤回公投提案，这意味着您的资金可能会被长期锁定。 - -恶意公投提案受到惩罚。HydraDX 议会和技术委员会有权取消任何恶意提出的公投。结果是存入的令牌将被烧毁。 -::: - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/performance_benchmark.md b/i18n/cn/docusaurus-plugin-content-docs/current/performance_benchmark.md deleted file mode 100644 index 3f45515bc..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/performance_benchmark.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -id: performance_benchmark -title: 基本性能测试 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -您可以通过运行测试程序来确定自己的计算机是否符合 **[基本性能要求](/collator_setup#technical-specifications)** 。 请运行一下代码： - -```bash -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable -$ cd HydraDX-node/ - -# Prepare for running the benchmark -## Install Rust following https://rustup.rs -$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh - -## Configure Rust -$ ./scripts/init.sh -$ rustup default nightly - -## Install additional libraries -$ apt install python3-pip -$ apt install clang - -# Run the benchmark -$ ./scripts/check_performance.sh -``` - -在测试程序运行完毕后，您可以看到与以下类似的输出结果： - -``` - Pallet | Time comparison (µs) | diff* (µs) | diff* (%) | | Rerun -amm | 773.00 vs 680.00 | 93.00 | 12.03 | OK | -exchange | 804.00 vs 720.00 | 84.00 | 10.44 | OK | -transaction_multi_payment| 218.00 vs 198.00 | 20.00 | 9.17 | OK | - -Notes: -- in the diff fields you can see the difference between the reference benchmark time and the benchmark time of your machine -- if diff is positive for all three pallets, your machine covers the minimum requirements for running a HydraDX node -- if diff deviates by -10% or more for some of the pallets, your machine might not be suitable to run a node -``` - -您可以在 **diff* (%)** 列中看到您的计算机绩效参数与启动节点所需最低要求之间的差异。 如果此列的三个数值均为正数，则表示您的计算机可以正常运行 HydraDX 验证节点。 三个数值，如果任何一个数值低于 *-10％* ，则不建议使用该机运行 HydraDX 节点。 - -如果您想讨论基本性能测试结果，请加入我们的 Discord ，社区很乐意提供您！ - -*（如发现翻译错误，请电报联系 @PDMCnode）* diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md b/i18n/cn/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md deleted file mode 100644 index c0ad12f18..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -id: polkadotjs_apps_local -title: 连接到本地节点 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -您可以使用 Polkadot/apps 连接到 HydraDX 本地节点。为此，需要访问用于 RPC Websocket 连接的 `9944` 端口。 - -:::warning - -如果您是运行验证节点的验证人，我们强烈建议您将 `9944` 端口列入黑名单，以禁止第三方进行远程连接。第三方可能会滥用此端口，从而降低您的节点性能，并可能导致严厉惩罚或资金的非自愿损失。仅当您的验证节点处于本地网络时，才可使用 `9944` 端口连接。 - -::: - -### 使用 Polkadot/apps 连接本地节点 {#accessing-your-local-node-using-polkadotapps} - -请打开 **[Polkadot/apps](https://polkadot.js.org/apps/)** ，单击左上角来更改网络去访问您的节点： - -
- -
- -打开菜单后，单击 **DEVELOPMENT** (开发)，然后选择 **Local Node** （本地节点）： -
- -
- -如有必要，请调整IP后，单击 ***Switch***（转换）以切换到您的本地节点： - -
- -
- -至此，您应该已连接到您的本地节点，并能够进行交互。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md b/i18n/cn/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md deleted file mode 100644 index 46f2162a5..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -id: polkadotjs_apps_public -title: 连接到公共节点 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -HydraDX 和我们的合作伙伴运营着两个公共 RPC 节点。使用这些节点，您可以与 Snakenet（蛇网） 进行交互。您可以通过单击以下链接，直接使用 Polkadot/apps 连接到公共节点： - -* **[由 HydraDX 运营的 RPC 节点](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer)** - - -## 手动连接到一个 RPC 节点 {#connect-manually-to-an-rpc-node} - -手动访问公共 RPC 节点，请打开 **[Polkadot/apps](https://polkadot.js.org/apps/)** ，然后单击左上角来更改网络： - -
- -
- -单击 **LIVE NETWORKS**（现行网络），然后选择 **HydraDX**： - -
- -
- -选择其中一个 RPC 节点，单击 **Switch**（转换）： - -
- -
- -至此，您应该已经连接到选定的公共 RPC 节点。 diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/spending_fw.md b/i18n/cn/docusaurus-plugin-content-docs/current/spending_fw.md deleted file mode 100644 index e96e4084d..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/spending_fw.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -id: spending_fw -title: 为 HydraDX 做贡献 ---- - -# 奖励为 HydraDX 做出的贡献 - -HydraDX 欢迎大家参与社区共建。每个人都可以通过做贡献，获得 HydraDX 财政奖励。 - -本文列出了社区贡献奖励支付的总体框架。该框架已获 HydraDX 社区 **[投票](https://hydradx.subsquare.io/democracy/referendum/11)** 批准，授权 HydraDX 议会在规定限额内对下述类别贡献兑付奖励。 - -首先请注意，本文提到的所有赏金及小费支付，均由 HydraDX 议会全权酌情决定。如果不确定您的努力是否有资格获得赏金，请提前联系。 - -您可在 HydraDX Discord 的 #bounties 中提问。 - -## 1. 漏洞赏金 {#bug-bounties} - -HydraDX 在 Immunefi 上运行漏洞赏金计划（Bug Bounty）。错误和漏洞，按严重程度分成三到四类，这决定了赏金的上限： - -### 区块链： {#bug-bounties-blockchain} - -* 关键：$50,000 ~ $1,000,000； -* 高：$5,000 ~ $50,000; -* 中：$5,000; -* 低：$1,000. - -### 网站和 APP {#bug-bounties-apps} - -* 关键：$5,000 ~ $50,000; -* 高：$5,000; -* 中：$1,000. - -:::note - -* 为了获得赏金，必须根据认可的纰漏程序以及 HydraDX Immunefi 页面发布的相关指南上报漏洞； -* 区块链关键漏洞赏金上限，为潜在经济损失的 10%； -* 奖励赏金的实际数额，由议会根据情况决定； -* 赏金由财政的 HDX 以交易所 7d MA 美元的价格支付（一旦 Oracles 可用，CEX 或 DEX - 如有疑问，请在 #bounties 中与 HydraDX 议会讨论）。 - -::: - -## 2. 开发赏金 {#dev-bounties} - -HydraDX 开发团队，将启动一个带有开发奖励的仪表板，以尽量分散协议的技术工作。仪表板将显示最新的赏金，以及赏金描述、技术规格和数额。 - -目前的框架，授权 HydraDX 议会提出高达 $100,000 的开发赏金，这些赏金将由财政按 **交易所 7d MA 美元价** 以 HDX 形式支付。超过该数额的赏金，仍需要通过社区治理批准。 - -## 3. 社区管理 {#community-mgmt} - -为社区管理做出努力，可从 HydraDX 财政按每小时 20 美元的标准（使用交易所 7d MA 美元价格）获得奖励。 - -新进社区经理，需事先得到团队批准。 - -以下是对这一角色的期望： - -* 担任 Telegram 和 Discord 的 MOD（管理员）； -* 成为项目大使； -* 社交活跃； -* 与其他社区经理一起，参加双周电话会议； -* 协调完成翻译任务； -* 最好已是 Hydra 社区的活跃成员。 - - -## 4. 翻译 {#translations} - -翻译工作，可从 HydraDX 财政按每小时 20 美元的标准获得 HDX 奖励（使用交易所 7d MA 美元价格）。目前，HydraDX 欢迎以下语言的翻译（可通过公投扩充列表）： - -* 中文普通话； -* 西班牙语； -* 俄语； -* 斯洛伐克语。 - -新进译员，需事先得到社区经理或 HydraDX 议会的批准。 - -## 5. 其它社区贡献 {#other-contributions} - -您想做出上述类别之外的贡献吗？请随时与我们联系，HydraDX 议会已准备好考虑您的个案。 - -该框架授权 HydraDX 议会，提供价值高达 100,000 美元的奖金（使用交易所 7d MA 美元价格）。 - -以下是一些可以获得奖励的贡献示例： - -* 创建良好的教育内容，例如指南、解释性博客或视频。**内容创建者，在制作前和制作中，应与社区经理和 HydraDX 议会保持联系，确保提供内容的质量**； -* 提供去中心化的基础设施； -* 推进对协议或社区有贡献的整合； -* MEME（!!）、表情符号、商品和贴纸。 - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/staking.md b/i18n/cn/docusaurus-plugin-content-docs/current/staking.md deleted file mode 100644 index 576b1bdc1..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/staking.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -id: staking -title: 质押 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -HydraDX 有一个**长期的 HDX 质押计划**，用于 **激励对协议有利的活动**。 在这个页面上，您将找到 **HDX 质押计划背后机制** 的有关信息。 您也可以查看我们的 **[质押分步指南](/howto_stake)**。 - -## 质押基础知识 {#basics} - -HDX 持有者，可以 **质押其 HDX 并获得奖励**，这些奖励奖随着时间推移变为 **可领取**。 质押奖励将从一个专用的池分配，该池由 **不同的协议收入流** 汇聚而成。 最初，池子的主要收入来源，是 HydraDX 协议的 HDX 在 Omnipool（万能池）中提供流动性产生的 **LP 费用**。 此外，HydraDX 社区已经批准一项提案，对质押计划实施的第一年，进行 APR 支持，即：由 HydraDX 财政提供 **约 2200 万 HDX** 的额外补贴，每天一次逐步分配到质押奖励池中。 - -进入质押池的奖励，会是在任何的特定时刻，直接分配给所有质押者。 用户有权获得的金额，与他们在质押池中质押量的相对大小成正比。 然而，奖励不会自动出现在质押者的账户上 —— 相反，质押者需要手动领取它们。 - -领取奖励时，HDX 质押的所有参与者，都应该了解 **忠诚度和游戏化** 这两个要素在其中所起的作用。 一旦奖励被分配，无法立即全额领取 —— 即使您这样做了，也只会领取分配总奖励的一小部分，其余的将返还给其他所有利益相关者。 - -用户若想要领取尽可能多的奖励，应该保持其 HDX 质押，直到经过足够的时间才领取（奖励按照联合曲线“归属”）。 等待时间是动态的，这取决于用户的具体动作。 仅 **被动质押** 的用户，需要 **等待大约 2 年才能领取 95% 的奖励**。 相比之下，收集最大数量行动积分（更多内容见下文）的 **主动质押者**，可在短短 2 个多月内，就能领取 **95% 的奖励**。 这仅仅是粗略的估计，实际的时间表，根据用户的具体操作和公投数量，会有所不同。 - -## 提高您的奖励 {#boosting-your-rewards} - -质押者可以通过 **收集行动积分** 和 **提高奖励** 来加快领取奖励的速度。 行动积分，可以通过执行协议鼓励的某些行动来获取。 最初，收集行动积分的唯一方法，是 **通过使用质押的 HDX 参与 HydraDX 治理，[对社区发起的公投进行投票](https://hydradx.subsquare.io/democracy/referenda)**。 - -
- login -
- -有两个因素，决定了质押者获得行动积分的数量： **投票规模**（相对于质押 HDX 总规模）和 **信念乘数**。 投票的信念乘数越高，权重就越大。 请记住，使用信念乘数进行投票，会 **对令牌进行临时锁定**。 希望获得最高奖励提升的质押者，可使用 6 倍信念乘数进行投票，从而将其 HDX 锁定 192 天（从使用此信念系数的最后一次投票开始算起）。 只是提醒一下，**此锁定与质押无关** —— 相反，它是 Polkadot 生态系统治理的标准功能（更多信息请查阅 **[我们的相关文档](/democracy_referenda#referenda-votes-weighing)**） 。 - -| 信念乘数 | 锁定天数 | -|:---------------------:|:------------:| -| 0.1x | 0天 | -| 1x | 6天 | -| 2x | 12天 | -| 3x | 24天 | -| 4x | 48天 | -| 5x | 96天 | -| 6x | 192天 | - -## 领取您的奖励 - -当 HDX 保持质押时，**用户会随着时间的推移积累奖励**。 这些奖励可根据联合曲线领取，该曲线受行动积分的提升影响（见上文）。 - -在任何特定的时刻，**质押者都可以领取** 其可领取的奖励。 然而，一旦这样做了，他们就会 **失去剩余不可领取的奖励**。 这些奖励将 **自动转回质押奖励池，并被重新分配给所有其他的质押者**。 此外，领取行为会 **重置用户以往的行积分点**，用户将被送回联合曲线的起点，以领取未来获得的质押奖励。 - -这种机制，创造了一个有趣的 **游戏化动态**：通过 **在利益相关池中停留更长时间**，用户不仅 **可以解锁分配奖励的大部分** ，还有机会获得 **来自其他提前领取或退出的利益相关者丰厚的部分奖励回报**。 - -祝您质押快乐！ diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/tip_request.md b/i18n/cn/docusaurus-plugin-content-docs/current/tip_request.md deleted file mode 100644 index 100da1019..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/tip_request.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -id: tip_request -title: 申请财政小费 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -作为社区成员对协议贡献的奖励，他们可向 HydraDX 财政申请 HDX 小费。本指南将指导您如何申请小费。您可以在 **[这篇文章](/spending_fw)** 中找到更多获得奖励的各种活动信息。 - -申请财政小费的流程，包括两个步骤：第一步，贡献者需要在 Subsquare 中 **[发布小费申请](#01-publish-tip-request)**，并附上贡献描述；第二步，财政小费申请必须使用 Polkadot/apps **[链上提交](#02-submit-on-chain)**。 - -## 01 在 Subsquare 发布 {#01-publish-tip-request} - -为确保透明度，所有财政小费申请必须在 **[HydraDX Subsquare 页面](https://hydradx.subsquare.io/discussions)** 上以讨论帖子的形式公布。 - -:::note -打开帖子之前，请确保 Subsquare 链接到您的 HDX 钱包。点击 `Sign-Up`（注册）（首次使用）或 `Login`（登录）（二次使用），并选择 `with Web3 address`（Web3 地址）选项。在弹出窗口中选择您的 HDX 地址后，您将被要求使用钱包签署消息。 -::: - -登录后，您需要为小费申请创建一个新讨论帖。您可以点击以下链接：**https://hydradx.subsquare.io/post/create** - -您可以使用帖子标题来表明主旨（小费申请）和贡献主题。在帖子正文中，请提供以下信息: - -* 贡献期间； -* 贡献摘要； -* 申请小费金额（HDX）； -* 贡献耗时（h）； -* 如果可能，请提供更详细的信息，例如：与 HydraDX 贡献相关的链接和 PR 链接（若是技术贡献）。 - -发布帖子之前，请确保选择 `Treasury`（财政）标签，以表明讨论性质。 - -作为参考，您可以查看这个 **[小费申请示例](https://hydradx.subsquare.io/post/192)**。 - -
- login -
- -点击 `Create`（创建）发布您的讨论帖子。此时，它应该立即在 **[讨论列表](https://hydradx.subsquare.io/discussions)** 中可见。 - -## 02 链上提交 {#02-submit-on-chain} - -发布财政小费申请后，您需在链上提交。出于这个目的，您的钱包需要持有少量 HDX 来支付交易费用。如果您目前没有任何 HDX，则不需要执行此步骤 - 其他人会帮您完成小费申请的链上提交。 - -财政小费申请，可通过以下链接在 Polkadot/app 上完成链上提交：**https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/treasury/tips** - -要提交新的小费请求，请点击 `Propose tip`（提出小费）并提供以下信息： - -* **submit with account**（随账户提交）- 选择签署交易、小费申请提交链上的帐户。这个账户需要持有少量 HDX 作为交易费用。 -* **beneficiary**（受益者）- 选择或输入接收财政小费的帐户地址。此帐户必须与打开 Subsquare 帖子的帐户相对应。 -* **tip reason**（小费原因）- 提供一个 Subsquare 帖子的 URL。 - -
- login -
- -要提交小费请求，请点击 `Propose tip`（提出小费）并签署交易。 - -确认交易后，您应该能在 Overview （概览）页面上看到小费申请。 - -
- login -
- - diff --git a/i18n/cn/docusaurus-plugin-content-docs/current/tokenomics.md b/i18n/cn/docusaurus-plugin-content-docs/current/tokenomics.md deleted file mode 100644 index 6f0f19b19..000000000 --- a/i18n/cn/docusaurus-plugin-content-docs/current/tokenomics.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -id: tokenomics -title: HDX 令牌经济学 ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -## 供应分布 -
- -
- -### 说明： -HDX 供应总量 6,500,000,000，分布及占比如下： -* LBP 参与者：1,983,002,235HDX（30.51%） -* 团队：810,000,000HDX（12.46%） -* 种子轮：540,000,000HDX（8.31%） -* 战略轮：150,000,000HDX（2.31%） -* BSX 众贷：120,714,086HDX（1.86%） -* 财政：354,484,118HDX（5.45%） -* HDX 众贷：494,588,589HDX（7.61%） -* 整理器奖励：251,548,200HDX（3.87%） -* 成长（LM 奖励、赏金等）：1,795,662,772HDX（27.63%） - -## 供应归属 -
- -
- diff --git a/i18n/cn/docusaurus-theme-classic/footer.json b/i18n/cn/docusaurus-theme-classic/footer.json deleted file mode 100644 index 8f1437b4d..000000000 --- a/i18n/cn/docusaurus-theme-classic/footer.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "link.title.Community": { - "message": "社区", - "description": "The title of the footer links column with title=Community in the footer" - }, - "link.item.label.Discord": { - "message": "Discord", - "description": "The label of footer link with label=Discord linking to https://discord.gg/HDNPFFrcnW" - }, - "link.item.label.Twitter": { - "message": "Twitter", - "description": "The label of footer link with label=Twitter linking to https://twitter.com/hydra_dx" - }, - "copyright": { - "message": "版权 © 2021 Intergalactic, Inc.（星际公司） 用 Docusaurus 创建", - "description": "The footer copyright" - } -} \ No newline at end of file diff --git a/i18n/cn/docusaurus-theme-classic/navbar.json b/i18n/cn/docusaurus-theme-classic/navbar.json deleted file mode 100644 index 3ad4e934d..000000000 --- a/i18n/cn/docusaurus-theme-classic/navbar.json +++ /dev/null @@ -1,14 +0,0 @@ -{ - "title": { - "message": "HydraDX 文档", - "description": "The title in the navbar" - }, - "item.label.Docs": { - "message": "文档", - "description": "Navbar item with label Docs" - }, - "item.label.HydraDX Homepage": { - "message": "HydraDX 主页", - "description": "Navbar item with label HydraDX Homepage" - } -} \ No newline at end of file diff --git a/i18n/de/code.json b/i18n/de/code.json deleted file mode 100644 index 0bef0efc6..000000000 --- a/i18n/de/code.json +++ /dev/null @@ -1,158 +0,0 @@ -{ - "theme.NotFound.title": { - "message": "Seite nicht gefunden", - "description": "The title of the 404 page" - }, - "theme.NotFound.p1": { - "message": "Wir konnten nicht finden, wonach Sie gesucht haben.", - "description": "The first paragraph of the 404 page" - }, - "theme.NotFound.p2": { - "message": "Bitte kontaktieren Sie den Besitzer der Seite, die Sie mit der ursprünglichen URL verlinkt hat, und teilen Sie ihm mit, dass der Link nicht mehr funktioniert.", - "description": "The 2nd paragraph of the 404 page" - }, - "theme.blog.paginator.navAriaLabel": { - "message": "Navigation der Blog-Listenseite", - "description": "The ARIA label for the blog pagination" - }, - "theme.blog.paginator.newerEntries": { - "message": "Neuere Einträge", - "description": "The label used to navigate to the newer blog posts page (previous page)" - }, - "theme.blog.paginator.olderEntries": { - "message": "Ältere Einträge", - "description": "The label used to navigate to the older blog posts page (next page)" - }, - "theme.blog.post.readingTime.plurals": { - "message": "Eine Minute Lesezeit|{readingTime} Minuten Lesezeit", - "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.tags.tagsListLabel": { - "message": "Tags:", - "description": "The label alongside a tag list" - }, - "theme.blog.post.readMore": { - "message": "Mehr lesen", - "description": "The label used in blog post item excerpts to link to full blog posts" - }, - "theme.AnnouncementBar.closeButtonAriaLabel": { - "message": "Schließen", - "description": "The ARIA label for close button of announcement bar" - }, - "theme.blog.post.paginator.navAriaLabel": { - "message": "Blog Post Seiten Navigation", - "description": "The ARIA label for the blog posts pagination" - }, - "theme.blog.post.paginator.newerPost": { - "message": "Neuer Post", - "description": "The blog post button label to navigate to the newer/previous post" - }, - "theme.blog.post.paginator.olderPost": { - "message": "Älterer Post", - "description": "The blog post button label to navigate to the older/next post" - }, - "theme.tags.tagsPageTitle": { - "message": "Tags", - "description": "The title of the tag list page" - }, - "theme.blog.post.plurals": { - "message": "Ein post|{count} posts", - "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.blog.tagTitle": { - "message": "{nPosts} getaggt mit \"{tagName}\"", - "description": "The title of the page for a blog tag" - }, - "theme.tags.tagsPageLink": { - "message": "Alle Tags anzeigen", - "description": "The label of the link targeting the tag list page" - }, - "theme.CodeBlock.copyButtonAriaLabel": { - "message": "In die Zwischenablage kopieren", - "description": "The ARIA label for copy code blocks button" - }, - "theme.CodeBlock.copied": { - "message": "Kopiert", - "description": "The copied button label on code blocks" - }, - "theme.CodeBlock.copy": { - "message": "Kopieren", - "description": "The copy button label on code blocks" - }, - "theme.docs.sidebar.expandButtonTitle": { - "message": "Seitenleiste ausklappen", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.expandButtonAriaLabel": { - "message": "Seitenleiste ausklappen", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.paginator.navAriaLabel": { - "message": "Dokumentation Seiten Navigation", - "description": "The ARIA label for the docs pagination" - }, - "theme.docs.paginator.previous": { - "message": "Zurück", - "description": "The label used to navigate to the previous doc" - }, - "theme.docs.paginator.next": { - "message": "Weiter", - "description": "The label used to navigate to the next doc" - }, - "theme.docs.sidebar.responsiveCloseButtonLabel": { - "message": "Menü schließen", - "description": "The ARIA label for close button of mobile doc sidebar" - }, - "theme.docs.sidebar.responsiveOpenButtonLabel": { - "message": "Menü öffenen", - "description": "The ARIA label for open button of mobile doc sidebar" - }, - "theme.docs.sidebar.collapseButtonTitle": { - "message": "Seitenleiste einklappen", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.sidebar.collapseButtonAriaLabel": { - "message": "Seitenleiste einklappen", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.versions.unreleasedVersionLabel": { - "message": "Dies ist eine unveröffentlichte Version von {siteTitle} {versionLabel}.", - "description": "The label used to tell the user that he's browsing an unreleased doc version" - }, - "theme.docs.versions.unmaintainedVersionLabel": { - "message": "Dies ist eine Dokumentation für {siteTitle} {versionLabel}, die nicht mehr gepflegt wird.", - "description": "The label used to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionSuggestionLabel": { - "message": "Für aktuelle Dokumentation lesen sie {latestVersionLink} ({versionLabel}).", - "description": "The label userd to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionLinkLabel": { - "message": "aktuellste version", - "description": "The label used for the latest version suggestion link label" - }, - "theme.common.editThisPage": { - "message": "Diese Seite bearbeiten", - "description": "The link label to edit the current page" - }, - "theme.common.headingLinkTitle": { - "message": "Direkter Link zur Überschrift", - "description": "Title for link to heading" - }, - "theme.lastUpdated.atDate": { - "message": " am {date}", - "description": "The words used to describe on which date a page has been last updated" - }, - "theme.lastUpdated.byUser": { - "message": " von {user}", - "description": "The words used to describe by who the page has been last updated" - }, - "theme.lastUpdated.lastUpdatedAtBy": { - "message": "Zuletzt aktualisiert{atDate}{byUser}", - "description": "The sentence used to display when a page has been last updated, and by who" - }, - "theme.common.skipToMainContent": { - "message": "Zum Hauptinhalt springen", - "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation" - } -} \ No newline at end of file diff --git a/i18n/de/docusaurus-plugin-content-docs/current.json b/i18n/de/docusaurus-plugin-content-docs/current.json deleted file mode 100644 index 4f8ce9c01..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current.json +++ /dev/null @@ -1,54 +0,0 @@ -{ - "version.label": { - "message": "Weiter", - "description": "The label for version current" - }, - "sidebar.sidebar.category.Intro": { - "message": "Intro", - "description": "The label for category Intro in sidebar sidebar" - }, - "sidebar.sidebar.category.Knowledge Base": { - "message": "Wissensdatenbank", - "description": "The label for category Knowledge Base in sidebar sidebar" - }, - "sidebar.sidebar.category.Snakenet": { - "message": "Snakenet", - "description": "The label for category Snakenet in sidebar sidebar" - }, - "sidebar.sidebar.category.Become a validator": { - "message": "Werde ein Validator", - "description": "The label for category Become a validator in sidebar sidebar" - }, - "sidebar.sidebar.category.Connect to a Node": { - "message": "Mit einer Node verbinden", - "description": "The label for category Connect to a Node in sidebar sidebar" - }, - "sidebar.sidebar.category.Other": { - "message": "Andere", - "description": "The label for category Other in sidebar sidebar" - }, - "sidebar.sidebar.category.Contribute": { - "message": "Beitragen", - "description": "The label for category Contribute in sidebar sidebar" - }, - "sidebar.sidebar.category.How-to": { - "message": "How-to", - "description": "The label for category How-to in sidebar sidebar" - }, - "sidebar.sidebar.category.Learn": { - "message": "Lernen", - "description": "The label for category Learn in sidebar sidebar" - }, - "sidebar.sidebar.category.Democracy": { - "message": "Demokratie", - "description": "The label for category Democracy in sidebar" - }, - "sidebar.sidebar.category.Maintain": { - "message": "Verwalten", - "description": "The label for category Maintain in sidebar sidebar" - }, - "sidebar.sidebar.category.Build": { - "message": "Bauen", - "description": "The label for category Build in sidebar sidebar" - } -} \ No newline at end of file diff --git a/i18n/de/docusaurus-plugin-content-docs/current/build_dev_chain.md b/i18n/de/docusaurus-plugin-content-docs/current/build_dev_chain.md deleted file mode 100644 index 2b121f6e8..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/build_dev_chain.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -id: build_dev_chain -title: Einrichten einer Dev-Chain ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Dieser Abschnitt führt Sie durch den Prozess des Einrichtens einer lokalen HydraDX-Chain für die Entwicklung. - -:::note -Möchten Sie eine Validator Node einrichten? Bitte lesen Sie unseren [collator setup guide](/collator_setup). -::: - -## 01 Abhängigkeiten installieren {#01-install-dependencies} - -Um eine lokale HydraDX-Chain für die Entwicklung vorzubereiten, muss Ihr Computer alle Abhängigkeiten für die Ausführung einer Substrat-Chain abdecken. Sie müssen eine Rust-Entwicklerumgebung installieren und sicherstellen, dass sie ordnungsgemäß für das Kompilieren des Substrate-Laufzeitcodes auf das WebAssembly (Wasm) konfiguriert ist. - -Sie können alle Abhängigkeiten manuell installieren und konfigurieren, lesen Sie dazu bitte den [Substrate guide](https://substrate.dev/docs/en/knowledgebase/getting-started), oder Sie können dieses Skript die ganze Arbeit für Sie erledigen lassen: - -```bash -$ curl https://getsubstrate.io -sSf | bash -s -- --fast -$ source ~/.cargo/env -``` - -## 02 Build {#02-build} - -Erstellen Sie die Wasm- und native Ausführungsumgebungen: - -```bash -# Rufen Sie die Quelle der neuesten stabilen Version ab -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable - -# Erstellen Sie die Binärdatei -$ cd HydraDX-node/ -$ cargo build --release -``` - -Sie können die Binärdatei hier finden: `./target/release/hydra-dx`. - -## 03 Ausführen {#03-run} - -Bevor Sie Ihr Build ausführen, können Sie alle vorhandenen Dev-Chains auf Ihrem Computer löschen (dies müssen Sie im Entwicklungsprozess häufig tun): - -```bash -$ ./target/release/hydra-dx purge-chain --dev -``` - -Führen Sie Ihr Build mit einem der folgenden Befehle aus: - -```bash -$ ./target/release/hydra-dx --dev - -# Führen Sie mit detaillierter Protokollierung aus -$ RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/hydra-dx -lruntime=debug --dev -``` - -## 04 Mit der lokalen Chain verbinden {#04-connect-to-your-local-chain-instance} - -Sie können mit Polkadot/apps eine Verbindung zu Ihrer HydraDX Dev-Node herstellen indem Sie das Netzwerk in "Development" ändern. Sie können auch diesen Link verwenden: -https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/explorer - -connect to node diff --git a/i18n/de/docusaurus-plugin-content-docs/current/claim.md b/i18n/de/docusaurus-plugin-content-docs/current/claim.md deleted file mode 100644 index 476ed6191..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/claim.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -id: claim -title: HDX beanspruchen ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Sie können ihre HDX Token aus der xHDX ERC-20 Token-Repräsentation beanspruchen, die Sie während des [Balancer LBP](https://hydradx.substack.com/p/lbp-announcement) erworben haben. - -## Vorbereitung {#prequisites} - -Es gibt zwei Voraussetzungen die für das Starten des Claim-Prozesses erfüllt sein müssen. Zum Einen benötigen Sie die [Polkadot.js Browsererweiterung](https://polkadot.js.org/extension/), mit welcher wir später das HDX Wallet erstellen werden und zum Anderen benötigen Sie Zugriff auf Ihr Wallet, in dem die xHDX Token aufbewahrt werden. Das Wallet muss in der Lage sein eine Nachricht signieren zu können. - -Sollten Sie ihre xHDX Token in einem Coinbase Wallet oder Trust Wallet aufbewahren müssen Sie einen weiteren Schritt in der Vorbereitung erledigen, da diese Wallets nicht in der Lage sind eine Nachricht zu signieren: -* Metamask: Sie können die Metamask Browsererweiterung benutzen und das Wallet über die Recovery Seed Phrase importieren. -* MEW (MyEtherWallet): Sie können auch MEW benutzen und Ihr Wallet entweder mit der Recovery Seed Phrase(*Mnemonic Phrase*) importieren oder aber Ihr Wallet mit MEW verbinden. Auf beide Optionen können Sie über die [MEW wallet access Seite](https://www.myetherwallet.com/access-my-wallet) zugreifen. Wenn Sie Coinbase Wallet nutzen können Sie die WalletLink Funktion wählen, die Sie in den Einstellungen der Coinbase Wallet App finden. - -## Beanspruchungsprozess {#claim-process} - -Wenn alle Vorbereitungen abgeschlossen sind können Sie die [HydraDX Claim App](https://claim.hydradx.io) besuchen und den Prozess starten. - -Während des Claim-Prozesses werden Sie ihre xHDX Token (ERC-20) verwenden um Ihre HDX Token zu erhalten. - -### 00 Authorisierung {#00-authorize} - -Sie werden daraufhin von der polkadot.js Erweiterung aufgefordert die Benutzung der Beanspruchungsseite zu authorisieren. - -:::warning -Stellen Sie sicher, dass die Aufforderung CLAIM.HYDRADX.IO anzeigt und https://claim.hydradx.io, andererseits könnten Sie einem Phishing Angriff zum Opfer fallen! -::: - -authorize - - -Nach der Authorisierung, werden Sie aufgefordert ihre Metadaten für die polkadot.js Erweiterung zu aktualisieren. Dies bedeutet, dass die Polkadot.js Erweiterung dazu in der Lage sein wird HydraDX spezifische Adressen zu erstellen, welche notwendig sind um den Beanspruchungsprozess in der Benutzeroberfläche zu vervollständigen. - -Nachdem Sie Ihre Ethereum-Adresse eingegeben haben sollten Sie die Menge an HDX Token sehen, die Sie beanspruchen können und die [erstatteten Gas-Gebühren](https://hydradx.substack.com/p/first-governance-vote), die Sie während des Kaufvorgangs der xHDX Token bei Balancer bezahlt haben. - -:::note -Sie sind nicht zur Erstattung der Gas-Gebühren berechtigt, falls Sie ihre xHDX an einem anderen Ort als dem offiziellen Balancer Pool (wie bspw. Uniswap) gekauft haben oder die xHDX in ein anderes Wallet deponiert haben als das mit dem Sie die Token gekauft haben. -::: - -authorize - -### 01 ETH Adresse auswählen {#01-select-your-eth-address} - -Im ersten Schritt, müssen Sie einen Account auswählen von dem Sie die Token beanspruchen wollen. Dies geschieht entweder durch die Verbindung zu Metamask oder indem Sie Ihre Adresse in das Feld eingeben. Im Falle der zweiten Variante müssen Sie später die Nachricht manuell signieren. - -authorize - -### 02 HDX Adresse erstellen und auswählen {#02-create-and-select-an-hdx-address} - -Im zweiten Schritt müssen Sie ihre HDX Adresse auswählen. - -Um eine neue HDX Adresse zu erstellen öffnen Sie die Polkadot.js Browserextension und klicken das + Symbol. -Im ersten Schritt der Accounterstellung sehen Sie ihre Mnemonic Phrase, welche aus 12 Worten besteht und dazu verwendet werden kann den Account später wiederherzustellen. -Nachdem Sie ihre Seed Phrase an einem sicheren Ort gespeichert haben klicken Sie auf *Next step*. -Hier müssen Sie das **Network** auf **HydraDX Snakenet Gen2** umstellen. -Vergeben Sie einen Namen und ein Passwort für den Account und beenden die Accounterstellung. - -authorize - -:::warning -Geben Sie Ihre Seed Phrase an niemanden weiter. Erstellen Sie davon ein Backup und bewahren Sie sie an einem sicheren Platz auf. Es ist der einzige Weg ihren Account wiederzuerlangen und wenn Sie ihn verlieren oder versehentlich veröffentlichen, sind ihre Anlagen in Gefahr. Bitte nehmen Sie zu Kenntnis das Sie dieses Wallet bis zum Start des Mainnets behalten müssen, da alle Bestände bis dahin gesperrt bleiben. Wenn Sie den Zugang zu ihrer Wallet verlieren, verlieren sie auch Ihre HDX. Bitte passen Sie auf sich auf! -::: - -Sobald Sie Ihre Adresse erstellt haben, können Sie diese in der Benutzeroberfläche auswählen. -Danach sollten Sie eine Übersicht Ihrer ETH und HDX Adressen sehen, die für den Claiming-Prozess verwendet werden. -Klicken Sie auf _next_ um fortzufahren und die Nachricht zu signieren. - -authorize - -### 03 Signieren {#03-sign} - -Im dritten Schritt müssen Sie die Nachricht signieren um Ihre Account-Inhaberschaft zu bestätigen und den Claiming-Prozess abzuschließen. - -:::note -Aufgrund der Eigenschaften des [ss58](https://polkadot.js.org/docs/keyring/start/ss58/) Adressformats welche die Polkadot Chain benutzt um Adressen in einer für Menschen lesbaren Darstellung anzuzeigen, werden die Adresse die Sie signieren und der Adresse die Sie in der Polkadot.js Erweiterung sehen werden, nicht übereinstimmen. -Was Sie in der Mitteilungsbox sehen ist Ihr öffentlicher Schlüssel zu Ihrer Adresse, während Sie in der Erweiterung eine für Menschen lesbare Repräsentation Ihrer Adresse sehen werden. -Dies ist vollständig sicher da wir die Adresse die Sie signieren, mit der Adresse des von Ihnen zur Beanspruchung verwendeten Accounts abgleichen. Dadurch ist es nicht möglich HDX von einer anderen Adresse zu beanspruchen außer von der die Sie im vorangegangen Schritt verwendet haben. -::: - -Abhängig von der von Ihnen verwendeten Möglichkeit die Sie in Schritt Eins ausgewählt haben werden Ihnen hier nun eine von Zwei möglichen Optionen angezeigt. -* Wenn Sie Ihr **Metamask** verbunden haben, werden Sie aufgefordert eine Nachricht zu signieren wenn Sie auf den _Sign_-Button klicken. Folgen Sie den Anweisungen in Metamask um die Nachricht zu signieren. -* Wenn Sie Ihre Ethereum Adresse manuell eingegeben haben müssen Sie die Nachricht mit Ihrem externen Wallet signieren, das Sie zum Kauf der Token verwendet haben. Sobald sie Ihre Nachricht signiert haben, fügen Sie die Signatur (beginnt mit "0x") in das dafür vorgesehene Feld ein. - -authorize - -### 04 Beanspruchen {#04-claim} - -Sobald die Nachricht signiert ist, müssen Sie eine Transaktion senden und Sie mit ihrer Polkadot.js Erweiterung signieren. Wenn Sie dies abgeschlossen haben sind Sie nun offizieller HDX Besitzer. Sie können Ihren HDX Kontostand überprüfen unter [Polkadot.js](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts), falls es nicht bereits in der Erweiterung angezeigt werden sollte. - -authorize - -Sie habenn den Claim-Prozess erfolgreich abgeschlossen und sind nun offiziell ein HDX-Halter! - -Sie können Ihren Kontostand mit Hilfe von Polkadot/apps überprüfen wenn Sie sich mit dem HydraDX Netzwerk verbunden haben: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts diff --git a/i18n/de/docusaurus-plugin-content-docs/current/democracy_council.md b/i18n/de/docusaurus-plugin-content-docs/current/democracy_council.md deleted file mode 100644 index 2814b5777..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/democracy_council.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -id: democracy_council -title: HydraDX-Rat ---- - -Das HydraDX Council ist eine On-Chain-Einheit, die eine Schlüsselrolle bei der Governance des Protokolls spielt. Dieser Artikel informiert über die [Zusammensetzung](#composition) des Rates, seine [Hauptaufgaben](#tasks), und die [Wahl der Ratsmitglieder](#elections). - -Eine Schritt-für-Schritt-Anleitung zur Teilnahme an Ratswahlen finden Sie in [diesem Leitfaden](/participate_in_council_elections). - -## Komposition {#composition} -Der HydraDX-Rat besteht derzeit aus **13 Mitgliedern**. - -Ein Minderheitsanteil von 6 Sitzen ist für das Gründerteam und die Investoren (4 Gründer + 2 Investoren) reserviert. - -Die restlichen 7 Sitze werden von der breiteren Gemeinschaft der HDX-Inhaber gewählt. - -## Aufgaben und Verantwortlichkeiten {#tasks} -Die Aufgaben des HydraDX Council umfassen ein breites Spektrum an täglichen Governance-Aktivitäten. Zunächst kontrolliert der Rat das Finanzministerium und genehmigt oder lehnt Vorschläge des Finanzministeriums ab. - -Der HydraDX-Rat spielt auch eine Rolle beim Referendum-Mechanismus. Der Rat kann eine Volksabstimmung einleiten, sofern mindestens 60 % der Mitglieder dies unterstützen (Supermehrheit) und kein Mitglied ein Vetorecht ausübt. Im Falle eines Vetos kann der Vorschlag nach Ablauf der Cool-Down-Periode erneut eingereicht werden. Das ablehnende Mitglied kann denselben Vorschlag nicht zweimal ablehnen. - -Darüber hinaus kann jedes vorgeschlagene Referendum mit einer 2/3-Supermehrheit der Ratsstimmen annulliert werden. Dies kann als letztes Mittel verwendet werden, um böswillige Vorschläge oder Änderungen zu stoppen, die Fehler im Code verursachen könnten. - -Schließlich ist der HydraDX-Rat für die Wahl des Technischen Komitees verantwortlich. - - -## Wahlen {#elections} -Jeder Inhaber von HDX-Token kann sich für eines der 7 nicht-permanenten Sets des HydraDX Council als Kandidat [bewerben](/participate_in_council_elections#become_candidate). - -Die Ratswahlen finden alle 7 Tage statt, wobei ein Algorithmus die 7 nichtständigen Ratssitze für die Dauer der folgenden 7 Tage besetzt. Das Demokratiemodul verwendet denselben Phragmen-Algorithmus, der verwendet wird, um den aktiven Satz von Validatoren im Polkadot Netzwerk auszuwählen. - -Alle Community-Mitglieder können bei den Ratswahlen [abstimmen](/participate_in_council_elections#vote) indem sie eine bestimmte Anzahl von HDX-Token ihrer Wahl sperren. Gesperrte Token können nicht übertragen werden und werden bei den Folgewahlen (bis auf Widerruf) verwendet. Die Wähler können und sollten mehr als einen Kandidaten in der Reihenfolge ihrer Präferenz auswählen. Der Wahlalgorithmus verteilt dann alle Stimmen, um die optimale Zuteilung der verfügbaren Ratssitze an die Kandidaten mit der höchsten Unterstützung durch die Gemeinschaft zu bestimmen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/democracy_intro.md b/i18n/de/docusaurus-plugin-content-docs/current/democracy_intro.md deleted file mode 100644 index 7bef1fb75..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/democracy_intro.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -id: democracy_intro -title: Einführung ---- - -HydraDX ist dabei, seine Governance vollständig zu dezentralisieren. Alle Entscheidungen, die das Protokoll betreffen, werden nach einem demokratischen Verfahren gefasst, das durch das Modul Substrate Democracy unterstützt wird. Der zentrale Mechanismus zur Konsensbildung unter den Stakeholdern ist das **Referendum**. - -Dieser Abschnitt enthält eine Reihe von Wissensartikeln, die Ihnen ein besseres Verständnis der Mechanismen hinter der Steuerung von HydraDX vermitteln sollen. Weitere Informationen finden Sie unter [Funktionsweise von Volksabstimmungen](/democracy_referenda), sowie zu den beiden zentralen Gruppen von Governance-Akteuren: [HydraDX Council](/democracy_council) und [Technischer Ausschuss](/democracy_technical_committee). - -Wenn Sie praktische Anleitungen zur Teilnahme an der Governance von HydraDX suchen, lesen Sie bitte die Schritt-für-Schritt-Anleitungen zu [Teilnahme an Referenden](/participate_in_referenda) und [Teilnahme an Ratswahlen](/participate_in_council_elections). - -## Demokratieparameter -Die folgende Liste enthält die wichtigsten Parameter, die den Governance-Mechanismus von HydraDX beeinflussen. Bitte beachten Sie, dass sich diese im Laufe der Zeit ändern können. - -* Mindesteinzahlung HDX für die Einleitung eines Referendums: **100.000 HDX** -* Abstimmungsfrist: **3 Tage** -* Abstimmungszeitraum für das Referendum: **3 Tage** -* Abstimmungsperiode für das Notfallreferendum: **3 Stunden** -* Cooloff-Periode nach Ablehnung eines Referendums: **7 Tage** -* Maximal ausstehende Referendumsvorschläge: **100** diff --git a/i18n/de/docusaurus-plugin-content-docs/current/democracy_referenda.md b/i18n/de/docusaurus-plugin-content-docs/current/democracy_referenda.md deleted file mode 100644 index 9d78f5b69..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/democracy_referenda.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -id: democracy_referenda -title: Referenda ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Referenda ermöglicht es Interessenvertretern, einen Vorschlag einer gewichteten, beteiligungsbasierten Abstimmung durch die breitere Gemeinschaft zu unterbreiten. Gegenstand des Referendums ist ein Aktionsvorschlag, der das Protokoll betrifft – zum Beispiel eine Auszahlung durch das Finanzministerium oder sogar eine Änderung des Laufzeitcodes. - -Grundsätzlich wird immer nur über ein Referendum abgestimmt. Andere anhängige Referendumsvorschläge werden in eine Warteschlange gestellt. Für öffentlich eingereichte Vorschläge und für Vorschläge des Rates gibt es separate Warteschlangen. Alle 3 Tage wählt der Referendumsmechanismus den besten Vorschlag mit der höchsten Unterstützung aus, abwechselnd zwischen den beiden Warteschlangen. Nach der Abstimmung und Annahme eines Referendums gibt es eine sogenannte *Verzögerungsfrist* von 3 Tagen, die verstreichen muss, bevor der Beschluss in Kraft tritt. Eine Ausnahme von diesen Regeln gilt für Dringlichkeitsvorschläge des Technischen Komitees, die sich mit größeren Protokollproblemen befassen und beschleunigt werden müssen. - -## Initiierung eines Referendums {#referenda-initiate} -Es gibt mehrere Möglichkeiten, ein Referendum einzuleiten, die im Folgenden genauer beschrieben werden. Die Art und Weise, wie das Referendum eingeleitet wurde, ist entscheidend für den anzuwendenden Abstimmungsmodus. - -### Volksabstimmung {#referenda-initiate-public} -Jeder Inhaber von HDX-Token kann [ein Referendum vorschlagen](/participate_in_referenda#propose) indem er die erforderliche Mindestmenge an HDX-Token einzahlt und den Vorschlag in der Kette einreicht. Andere Community-Mitglieder können [den (*zweiten*) Vorschlag unterstützen](/participate_in_referenda#second) indem sie eine gleiche Anzahl von Token sperren. Zu Beginn jedes Abstimmungszyklus wird der Referendumsvorschlag mit der höchsten Anzahl an *Seconding* (Gesamtzahl der hinterlegten Token) von der Community zur Abstimmung gestellt. - -Der Abstimmungsmodus, der für Volksabstimmungen gilt, ist [Positive Turnout Bias](#referenda-voting-modes). - -:::note -Alle HDX-Token, die hinterlegt werden, um ein Referendum vorzuschlagen oder zu unterstützen, werden für den gesamten Zeitraum gesperrt, bis das Referendum in den Abstimmungszyklus eingetreten ist. Es ist wichtig, sich daran zu erinnern, dass es keine Garantie dafür gibt, dass ein bestimmter Vorschlag jemals genügend Unterstützung erhält, um in die Abstimmungsrunde einzutreten, was bedeutet, dass Ihre Gelder möglicherweise auf unbestimmte Zeit gesperrt bleiben. -::: - -### Council Referendum {#referenda-initiate-council} -Der HydraDX-Rat hat die Befugnis, ein Referendum für eine Gemeinschaftsabstimmung vorzuschlagen. Wenn sie dies einstimmig tut, ist der anwendbare Abstimmungsmodus für das Referendum [Negative Turnout Bias](#referenda-voting-modes). Wenn das Referendum mit einfacher Mehrheit der Ratsstimmen vorgeschlagen wird, ist der Abstimmungsmodus für die Annahme der Vorschläge durch die Gemeinschaft [einfache Mehrheit](#referenda-voting-modes). - -### Dringlichkeitsvorschläge des Technischen Komitees {#referenda-initiate-tech-committee} -Das Technische Komitee kann Notfallvorschläge einreichen, die sich mit (kritischen) Fehlerkorrekturen oder der schnellen Übernahme kampferprobter Funktionen befassen. Notfallvorschläge überspringen die Warteschlange und treten direkt in die Abstimmungsrunde ein. Die Community kann parallel zu allen regulären Vorschlägen, die in die Abstimmungsrunde eingegangen sind, über Dringlichkeitsvorschläge abstimmen. Darüber hinaus haben Dringlichkeitsvorschläge eine kürzere Abstimmungsfrist, um sicherzustellen, dass sie beschleunigt werden können. - -### Absage eines Referendums {#cancel} -Ein einmal vorgeschlagenes Referendum kann erst nach Eintritt in die Abstimmungsrunde widerrufen werden. Eine Ausnahme von dieser Regel gilt für Vorschläge, die als protokollschädlich erachtet werden (z. B. Codeänderungen, die einen Fehler einführen). In diesem begrenzten Fall kann der Referendumsvorschlag vom [HydraDX Council](/democracy_council) (mit 60 % Supermehrheit) oder dem [Technical Committee](/democracy_technical_committee) (einstimmig) annulliert werden.Alle Token, die von Unterstützern gesperrt wurden, die den Vorschlag unterstützen, werden verbrannt. - -## Abstimmung in einem Referendum {#referenda-vote} -HydraDX-Referenden haben einen Startzeitraum von 3 Tagen. Zu Beginn jeder neuen Periode wird der Vorschlag mit der höchsten Anzahl von Entsendungen aus der Warteschlange genommen und in eine Abstimmungsrunde gestellt. Jede Abstimmungsrunde hat eine Dauer von 3 Tagen. Während dieser Zeit können die Mitglieder der Gemeinschaft über ein gewichtetes, stakebasiertes Verfahren über das Referendum abstimmen. Sie tun dies, indem sie eine bestimmte Anzahl von HDX-Token für einen bestimmten Zeitraum sperren. - -:::note -Gesperrte HDX-Token können für die Dauer des gewählten Sperrzeitraums nicht übertragen werden. Sie können jedoch weiterhin zum Abstecken und zur Abstimmung verwendet werden. -::: - -### Stimmengewichtung {#referenda-votes-weighing} -Es gibt zwei Faktoren, die das Gewicht jeder Stimme in einem Referendum bestimmen. Der erste Faktor ist die **Menge an HDX-Token**, die der Wähler zur Unterstützung der Abstimmung einsperrt. Der zweite Faktor ist der sogenannte **Conviction Multiplier**, der die Dauer widerspiegelt, für die der Wähler bereit ist, die Token zu sperren. - -``` -vote_weight = tokens * conviction_multiplier -``` - -Abstimmungssperrfristen haben die gleiche Dauer wie die Inkraftsetzungsverzögerung. Wenn Token für 1 Abstimmungsperiode gesperrt sind, bedeutet dies, dass sie nach Beendigung der Abstimmung noch **3 Tage** gesperrt bleiben. Wähler können das Gewicht ihrer Stimmen beeinflussen, indem sie die Anzahl der Zeiträume, für die die Token gesperrt sind, verringern oder erhöhen. Es ist möglich, eine Stimme mit 0 Sperrperioden herauszubringen, ihr Gewicht wäre jedoch nur ein Bruchteil (Überzeugungsmultiplikator von 0,1x). Andererseits erhöht sich der Überzeugungsmultiplikator um 1 für jede Verdoppelung der Sperrperioden. Wie in der Tabelle unten gezeigt, würde das Sperren der Stimmen für maximal 32 Perioden den Verurteilungsmultiplikator auf das 6-fache erhöhen. - -| Sperrzeiten | Überzeugungsmultiplikator | -|:-----------------:|:---------------------:| -| 0 | 0.1 | -| 1 | 1 | -| 2 | 2 | -| 4 | 3 | -| 8 | 4 | -| 16 | 5 | -| 32 | 6 | - -``` -Beispiel: - -Alice stimmt mit 5000 HDX und 0 Sperrzeiten. -Bob stimmt mit 100 HDX und 32 Sperrperioden ab. - -Alice Gewicht: 500 -Bob Gewicht: 600 - -``` - -### Abstimmungsmodi {#referenda-voting-modes} -Ein weiterer wichtiger Aspekt des Demokratiemoduls sind die unterschiedlichen Wahlmodi. Die für die Annahme oder Ablehnung eines Referendums erforderliche Stimmenschwelle kann je nach Einleitung des Referendums und der Wahlbeteiligung variieren. Die Wahlbeteiligung wird anhand der Gesamtmenge der HDX-Token berechnet, die zur Abstimmung im Referendum verwendet wurden (ohne Überzeugungsmultiplikatoren). Ob die Wahlbeteiligung niedrig war oder nicht, wird durch das Verhältnis zwischen Wahlbeteiligung und Elaktorate (d. h. der Gesamtzahl der stimmberechtigten HDX-Token) bestimmt.. - -#### Positive Turnout Bias -Dies ist der Standard-Abstimmungsmodus, wenn von der Gemeinschaft ein Referendum vorgeschlagen wird. Bei geringerer Wahlbeteiligung ist eine qualifizierte Supermehrheit von Ja-Stimmen erforderlich, um das Referendum zu genehmigen. Mit steigender Wahlbeteiligung sinkt die Schwelle in Richtung einer einfachen Mehrheit. - -
- -
- -#### Negative Turnout Bias -Dieser Abstimmungsmodus gilt für Referenden, die vom Rat einstimmig vorgeschlagen wurden. Solche Vorschläge erfordern eine qualifizierte Supermehrheit von "Nein"-Stimmen, um bei geringer Wahlbeteiligung abgelehnt zu werden. Mit steigender Wahlbeteiligung sinkt die Schwelle zur Ablehnung des Referendums in Richtung einer einfachen Mehrheit. - -
- -
- -#### Einfache Mehrheit -Volksabstimmungen, die vom Rat mehrheitlich (also nicht einstimmig) initiiert wurden, können von der Gemeinde mit einfacher Stimmenmehrheit (50% + 1) angenommen werden. - -
- -
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/democracy_technical_committee.md b/i18n/de/docusaurus-plugin-content-docs/current/democracy_technical_committee.md deleted file mode 100644 index 3b291a761..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/democracy_technical_committee.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -id: democracy_technical_committee -title: Technischer Ausschuss ---- - -Das Technical Committee ist eine Gruppe erfahrener Kernentwickler, die direkt vom HydraDX Council ernannt wird. Seine Hauptaufgabe besteht darin, die technische Stabilität des Protokolls zu gewährleisten. - -Das Technische Komitee hat das Recht, **Notfallreferenden** durchzuführen, die im Schnellverfahren durchgeführt und parallel zu allen anderen aktiven Referenden abgestimmt werden. Dies ermöglicht dem Ausschuss, schnell zu handeln und kritische (Code-)Änderungen vorzunehmen. - -Eine weitere wichtige Befugnis des Technischen Komitees ist die Möglichkeit, Referendumsvorschläge, die als nachteilig für das Protokoll angesehen werden, **zurückzuziehen**. Um einen Referendumsvorschlag aufzuheben, muss der Ausschuss einstimmig zustimmen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/identity.md b/i18n/de/docusaurus-plugin-content-docs/current/identity.md deleted file mode 100644 index 2cb062a47..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/identity.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -id: identity -title: Identität festlegen ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Kontoinhaber haben die Möglichkeit, ihre eigene Identität festzulegen, indem sie bestimmte Informationen bereitstellen und in der Blockchain speichern. Außerdem können die Identitätsinformationen optional zur Überprüfung an die HydraDX-Registratoren übermittelt werden. Durch das Festlegen und Überprüfen ihrer Identität tragen Validatoren und Nominatoren dazu bei, das Vertrauen in das Netzwerk zu stärken. - -:::note -Wenn Sie als HydraDX-Validator teilnehmen, empfehlen wir Ihnen dringend, sowohl Ihre Identität festzulegen als auch den Überprüfungsprozess durchzuführen. Verifizierte Validatoren erscheinen vertrauenswürdiger und ziehen mehr Nominierungen an, wodurch sich ihre Chancen erhöhen, in die Gruppe der aktiven Validatoren aufgenommen zu werden. -::: - -## 01 Identität festlegen {#01-set-identity} - -Um Ihre Identität festzulegen, öffnen Sie Polkadot/apps (verbunden mit *HydraDX Snakenet* network) und navigieren Sie zu *My accounts*. Man kann auch diesem Link folgen: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts - -Suchen Sie auf der Kontoseite das Konto, auf dem sich Ihre gebundenen HDX-Token befinden. Klicken Sie auf die drei Punkte neben dem Konto (auf der rechten Seite) und wählen Sie *Set on-chain identity*. - -authorize - -Sie sehen ein Popup mit dem Namen *register identity*. Hier können Sie folgende Informationen eingeben: - -* Offizieller Name -* E-Mail -* Webadresse -* Twitter -* Riotname (falls Sie Matrix verwenden) - -:::note -Sämtliche Angaben sind optional. Sie können nach Belieben entscheiden welche Angaben Sie hinterlegen möchten. Wenn Sie jedoch eine Validator Node betreiben möchten wir Sie darum bitten Ihre E-Mail-Adresse anzugeben. Dies ermöglicht es uns Sie zu kontaktieren, falls wir Probleme an Ihrer Node feststellen. -::: - -Im letzten Feld des Popups sehen Sie die Menge von HDX, die Sie hinterlegen müssen, um Ihre Identitätsinformationen zu speichern. Sie erhalten diese Kaution zurück, sobald Sie sich entschließen, Ihre Identität zu einem späteren Zeitpunkt zu löschen. - -authorize - -Klicken Sie nach dem Ausfüllen der Informationen auf *Set Identity* und signieren Sie die Transaktion mit der Browsererweiterung Polkadot.js. Sobald die Transaktion bestätigt würde, wird Ihre Identität festgelegt. - -## 02 Senden Sie Ihre Identität zur Überprüfung {#02-verify-identity} - -Nachdem Sie Ihre Identität festgelegt haben, kann man sie zur Überprüfung an die Netzwerkregister senden. Öffnen Sie dazu Polkadot / apps und navigieren Sie zu *Developer* > *Extrinsics*. Man kann auch diesem Link folgen: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics - -Nachdem Sie im letzten Schritt das entsprechende HydraDX-Konto ausgewählt haben, müssen Sie die folgenden Informationen eingeben: - -* **extrinsic**: identity -* **action**: requestJudgment -* **reg_index**: Hier müssen Sie die ID des Registers eingeben, den Sie für die Überprüfung ausgewählt haben. -HydraDX hat 2 Registratoren: Simon Kraus - HydraSik (ID: **0**) and Jimmy Tudeski - stakenode (ID: **1**). -* **max_fee**: Hier müssen Sie die maximale Gebühr in HDX eingeben, die Sie zur Überprüfung an den Registrator zahlen möchten. Nur Registratoren mit einer Gebühr unter Ihrer max_fee können die Überprüfung durchführen. - -Um Ihre Bestätigungsanfrage einzureichen, klicken Sie auf *Submit Transaction* und signieren Sie die Transaktion. - -authorize - -Bitte beachten Sie, dass der Vorgang der Identitätsprüfung einige Zeit in Anspruch nehmen kann. Um den Status Ihrer Anfrage anzuzeigen, navigieren Sie zu **My accounts** und bewegen Sie den Mauszeiger über den Abschnitt, in dem Ihre Identität angezeigt wird. Es wird ein Popup mit dem aktuellen Status angezeigt. - -## 03 Ergebnis des Überprüfungsverfahrens {#03-verification-outcome} - -Nach der Bearbeitung Ihrer Bestätigungsanfrage wird der Registrator einen der folgenden Status festlegen, die in Ihrem Identitätsstatus sichtbar werden: - -* **Unknown** - Standardwert, es wurde noch kein Urteil gefällt. -* **Reasonable** - Die bereitgestellte Informationen erscheinen angemessen, es wurden jedoch keine eingehenden Überprüfungen durchgeführt. -* **KnownGood** - Die Informationen sind korrekt. -* **OutOfDate** - Die Informationen waren in der Vergangenheit korrekt, sind aber jetzt veraltet. -* **LowQuality** - Die Informationen sind ungenau, können jedoch durch Aktualisierung behoben werden. -* **Erroneous** - Die angegebenen Informationen sind falsch und weist möglicherweise auf eine böswillige Absicht hin. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/intro.md b/i18n/de/docusaurus-plugin-content-docs/current/intro.md deleted file mode 100644 index adf1695e4..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/intro.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -id: intro -title: Erste Schritte -slug: / ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Herzlich Willkommen in der offiziellen HydraDX Dokumentation! -Hier können Sie viele nützliche Resourcen über das HydraDX Protokoll finden. -Wir beabsichtigen dies zu einem großartigen Ort für jedermann zu machen und das komplette Spektrum abzudecken vom normalen Besucher über Nominatoren und Validatoren bis hin zu Entwicklern, die helfen wollen HydraDX aufzubauen. - -HydraDX ist Community-getrieben und das gilt auch für diese Dokumentation. -Wir würden uns freuen Ihre Ergänzungen zu sehen, was sowohl das Schreiben neuer Artikel, als auch das Übersetzen bestehender sein kann. -Schauen Sie sich unser [GitHub Repository](https://github.com/galacticcouncil/HydraDX-docs) und die [Contribution Guidelines](/contributing) an. - -## Was ist HydraDX? {#what-is-hydradx} - -HydraDX ist ein Chain-übergreifendes Liquiditäts-Protokoll, welches auf Substrate aufgebaut ist. -Unsere Mission ist es reibungsloses Bereitstellen von Liquidität in Form jeglicher Crypto-Assets zu ermöglichen indem wir das den ersten multi-asset Liquiditätspol erschaffen - den HydraDX Omnipool. -In diesem Omnipool können verschiedene Assets gegeneinander gewertet werden indem der native HDX-Token als Referenzwert herangezogen wird. -Mit dem Omnipool bricht HydraDX die traditionellen Konzepte des Handels in paarweisen isolierten Pools auf. -Des Weiteren sind wir sehr glücklich ein Teil des Polkadot Ökosystems zu sein und sehen einer Zukunft entgegen, in der wir der meistgennutzte Liquiditäts-Anbieter für alle Substrate-basierten Assets sind. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/node_monitoring.md b/i18n/de/docusaurus-plugin-content-docs/current/node_monitoring.md deleted file mode 100644 index 98951f224..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/node_monitoring.md +++ /dev/null @@ -1,348 +0,0 @@ ---- -id: node_monitoring -title: Node Monitoring ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -In diesem Kapitel durchlaufen wir den Einrichtungsprozess eines lokalen Monoitoring-Systems der Validator Node. - -## Prerequisites {#prerequisites} - -Sie müssen Ihre [Collator Node](/collator_setup) fertig eingerichtet und aktiv haben. -Dieser Guide wurde unter dem Ubuntu 20.04 LTS Release getestet. - -## Prometheus Setup {#prometheus-setup} - -Im ersten Schritt werden wir den Prometheus Server einrichten. - -### Benutzer und Ordner {#user-and-directories} - -Sie erstellen einen separaten Benutzer für die Überwachungszwecke, für den kein Home-Verzeichnis angelegt wird und der sich nicht einloggen kann. - -```shell script -$ sudo useradd --no-create-home --shell /usr/sbin/nologin prometheus -``` - -Als nächstes erstellen Sie Verzeichnisse für die ausführbaren Dateien und die Konfigurationsdateien. - -```shell script -$ sudo mkdir /etc/prometheus -$ sudo mkdir /var/lib/prometheus -``` - -Ändern Sie den Eigentümer der Verzeichnisse auf den neu erstellten Benutzer. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus -$ sudo chown -R prometheus:prometheus /var/lib/prometheus -``` - -### Prometheus installieren {#install-prometheus} - -Schauen Sie nach der aktuellsten Version auf der [GitHub Release Seite](https://github.com/prometheus/prometheus/releases/). -Zum Zeitpunkt der Veröffentlichung ist dies v2.25.2. Setzen Sie die aktuellste Version in die folgenden Befehle ein. - -```shell script -# download prometheus -$ wget https://github.com/prometheus/prometheus/releases/download/v2.25.2/prometheus-2.25.2.linux-amd64.tar.gz - -# unpack the binaries -$ tar xfz prometheus-*.tar.gz - -# enter the unpacked directory -$ cd prometheus-2.25.2.linux-amd64 -``` - -Nun kopieren Sie die Binaries in das lokale Verzeichnis. - -```shell script -$ sudo cp ./prometheus /usr/local/bin/ -$ sudo cp ./promtool /usr/local/bin/ -``` - -Als Besitzer der Dateien wird ebenfalls unser neuer Benutzer gesetzt. - -```shell script -$ sudo chown prometheus:prometheus /usr/local/bin/prometheus -$ sudo chown prometheus:prometheus /usr/local/bin/promtool -``` - -Danach kopieren Sie die Benutzeroberfläche und die Konfigurationsdateien. - -```shell script -$ sudo cp -r ./consoles /etc/prometheus -$ sudo cp -r ./console_libraries /etc/prometheus -``` - -Sie ahnen es sicher bereits, doch wir müssen mal wieder die Benutzer der Verzeichnisse ändern. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus/consoles -$ sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries -``` - -Sie haben nun alles, was Sie aus dem heruntergeladenen Paket benötigen, also navigieren Sie einen Schritt zurück und räumen etwas auf. - -```shell script -$ cd .. && rm -rf prometheus* -``` - -Nun erstellen Sie eine `YAML`-Komnfigurationsdatei für Prometheus mit einem Editor Ihrer Wahl (nano / vim / pico). - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Die Konfigurationsdatei ist in drei Bereiche gegliedert: - -* `global`: setzt die Standardwerte für das Abtastungsintervall `scrape_interval` und das Ausführungsintervall der Regeln `evaluation_interval` -* `rule_files`: legt die Regel-Dateien fest, die Prometheus laden soll -* `scrape_configs`: hier wird festgelegt welche Resourcen überwacht werden sollen - -Wir werden uns auf die Grundsätze beschränken und folgende Konfiguration erstellen: - -```yaml -global: - scrape_interval: 15s - evaluation_interval: 15s - -rule_files: - # - "weHaveNo.rules" - -scrape_configs: - - job_name: "prometheus" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9090"] - - job_name: "substrate_node" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9615"] -``` - -Der erste Job exportiert Daten von Prommetheus selbst, der zweite exportiert die Metriken der HydraDX Node. -Wir ändern das `scrape_interval` beider Jobs um ein detaillierteres Dashboard zu erstellen. Dies überschreibt die globalen Variablen. -Das `target` in `static_configs` legt fest, wo die Exporter laufen, wir belassen dies bei den Standardwerten. - -Nachdem die Konfiguration gespeichert wurde, wird erneut der Besitzer geändert. - -```shell script -$ sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml -``` - -### Prometheus starten {#starting-prometheus} - -Damit Prometheus automatisch startet und im Hintergrund läuft werden wir `systemd` verwenden. -Erstellen Sie eine neue Konfiguration (wieder mit einem Editor Ihrer Wahl): - -````shell script -$ sudo nano /etc/systemd/system/prometheus.service -```` - -Fügen Sie folgende Konfiguration ein und speichern sie ab. - -``` -[Unit] - Description=Prometheus Monitoring - Wants=network-online.target - After=network-online.target - -[Service] - User=prometheus - Group=prometheus - Type=simple - ExecStart=/usr/local/bin/prometheus \ - --config.file /etc/prometheus/prometheus.yml \ - --storage.tsdb.path /var/lib/prometheus/ \ - --web.console.templates=/etc/prometheus/consoles \ - --web.console.libraries=/etc/prometheus/console_libraries - ExecReload=/bin/kill -HUP $MAINPID - -[Install] - WantedBy=multi-user.target -``` - -Danach führen Sie die drei folgenden Schritte aus: -`systemctl deamon-reload` lädt neue Konfigurationen und aktualisiert die bestehende -`systemctl enable` aktiviert Ihren neuen Service -`systemctl start` startet den Service - -Hiermit können Sie alle drei Befehle in einer Zeile ausführen: - -```shell script -$ sudo systemctl daemon-reload && systemctl enable prometheus && systemctl start prometheus -``` - -Sie sollten nun in der Lage sein die Benutzeroberfläche von Prometheus unter http://localhost:9090/ aufzurufen. - -## Node Exporter {#node-exporter} - -Wir werden Node Exporter installieren um Hardware-Werte für das Dashboard abzugreifen. -Bitte schauen Sie [hier](https://github.com/prometheus/node_exporter/releases/) nach, welches die aktuellste Version ist und ersetzen die Versionsnummer im folgenden Befehl. -Zum Veröffentlichungszeitpunkt war die aktuellste Version `1.1.2`. - -### Node Exporter installieren {#install-node-exporter} - -Laden Sie die neuste Version herunter. - -```shell script -$ wget https://github.com/prometheus/node_exporter/releases/download/v1.1.2/node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Entpacken Sie das eben heruntergeladene Paket. Dadurch wird ein Verzeichnis mit dem Namen `node_exporter-1.1.2.linux-amd64` erstellt. - -```shell script -$ tar xvf node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Als Nächstes kopieren Sie die Binary in das lokale Applikationsverzeichnis und weisen es dem entsprechenden Benutzer zu. - -```shell script -# copy binary -$ cp node_exporter-1.1.2.linux-amd64/node_exporter /usr/local/bin - -# set ownership -$ sudo chown prometheus:prometheus /usr/local/bin/node_exporter -``` - -Sie können etwas aufräumen und das heruntergeladene Paket und die entpackten Dateien entfernen. - -```shell script -$ rm -rf node_exporter* -``` - -### Einen Systemd Service erstellen {#create-a-systemd-service} - -Genau wie bei Prometheus starten Sie Node Exporter als Service im Hintergrund. -Erstellen Sie einen systemd Service mit einem Editor Ihrer Wahl. - -```shell script -$ sudo nano /etc/systemd/system/node_exporter.service -``` - -Und fügen Sie folgende Konfiguration ein. - -``` -[Unit] -Description=Node Exporter -Wants=network-online.target -After=network-online.target - -[Service] -User=prometheus -Group=prometheus -Type=simple -ExecStart=/usr/local/bin/node_exporter - -[Install] -WantedBy=multi-user.target -``` - -Aktivieren und starten Sie den Service mit folgendem Einzeiler. - -```shell script -$ sudo systemctl daemon-reload && systemctl enable node_exporter && systemctl start node_exporter -``` - -### Scrape Job für Node Exporter hinzufügen {#add-scrape-job-for-node-exporter} - -Der Node Exporter ist nun einsatzbereit, Sie müssen Prometheus jedoch noch anleiten die Daten zu erheben. -Öffnen Sie die Konfiguration mit einem beliebigen Editor. - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Fügen Sie ganz unten am Ende der Datei eine weitere Scrape-Konfiguration ein. -Kopieren Sie folgenden Codeblock hinein und speichern die Datei. - -```yaml - - job_name: 'node_exporter' - scrape_interval: 5s - static_configs: - - targets: ['localhost:9100'] -``` - -Um die neue Konfiguration anzuwenden muss der Prometheus Service neugestartet werden. - -```shell script -$ sudo systemctl restart prometheus.service -``` - -Ihre Server-Metriken werden nun ausgelesen und können in der Prometheus Benutzeroberfläche eingesehen werden. -Sie werden sie später für das Dashboard benötigen. - -## Grafana Setup {#grafana-setup} - -Sie können die Daten in der Benutzeroberfläche sehen, das war jedoch nicht das Ziel dieser Anleitung. -Wir möchten die Daten hübsch angezeigt bekommen und da kommt Grafana ins Spiel. - -### Grafana installieren {#install-grafana} - -Bitte überprüfen Sie mit [diesem Link](https://grafana.com/grafana/download?platform=linux), welches die neuste Version von Grafana ist. -Sie können entweder die Versionsnummer in folgendem Befehl anpassen oder die Befehle aus der verlinkten Seite kopieren und direkt benutzen. -Zum Veröffentlichungszeitpunkt war die aktuellste Version `7.5.1`. - -```shell script -$ sudo apt-get install -y adduser libfontconfig1 -$ wget https://dl.grafana.com/oss/release/grafana_7.5.1_amd64.deb -$ sudo dpkg -i grafana_7.5.1_amd64.deb -``` - -Das Paket enthält einen fertigen `systemd`-Service, welchen Sie direkt verwenden können. - -```shell script -$ sudo systemctl daemon-reload && sudo systemctl enable grafana-server && sudo systemctl start grafana-server -``` - -### Die Benutzeroberfläche aufrufen {#accessing-the-web-interface} - -Sie können die Benutzeroberfläche von Grafana nun unter http://localhost:3000/ aufrufen. -Die standardmäßigen Login-Daten für Grafana sind: -Benutzer: `admin` -Passwort: `admin` - -
- -
- -### Die Datenquelle konfigurieren {#configuring-the-datasource} - -Bitte klicken Sie das Einstellungs-Zahnrad im Menü und wählen `Datasources`. -Im nächsten Fenster klicken Sie `Add Datasource` und wählen Sie `Prometheus`. - -Im nachfolgenden Formular müssen Sie nichts ändern außer die URL. -Stellen Sie `http://localhost:9090/` ein und klicken `Save and Test`. - -
- -
- -### Das Dashboard importieren {#importing-the-dashboard} - -Bitte klicken Sie den `Plus`-Button im Hauptmenü und wählen `import`. - -
- -
- -Sie können das [HydraDX Dashboard](https://grafana.com/grafana/dashboards/14158) nutzen und um es zu laden geben Sie einfach die ID `14158` ein und klicken auf `Load`. - -
- -
- -Hier müssen Sie nicht viel einstellen, vergewissern Sie sich lediglich, dass `Prometheus` als `Datasource` eingestellt ist. -Sie können den Importvorgang nun abschließen. - -
- -
- -Sie sollten das Dashboard sofort mit ihren Daten sehen. -Falls einzelne Panele leer sind, vergewissern Sie sich bitte, dass die Auswahlfelder ganz oben folgende Werte enthalten: -* `Chain Metrics`: Substrate -* `Chain Instance`: localhost:9615 -* `Server Job`: node_exporter -* `Server Host`: localhost:9100 diff --git a/i18n/de/docusaurus-plugin-content-docs/current/participate_in_council_elections.md b/i18n/de/docusaurus-plugin-content-docs/current/participate_in_council_elections.md deleted file mode 100644 index 5f07a6cb0..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/participate_in_council_elections.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -id: participate_in_council_elections -title: Teilnahme an Ratswahlen ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Dieser Artikel enthält eine Schritt-für-Schritt-Anleitung zur Teilnahme an Ratswahlen - für die Wahl von Ratsmitgliedern und für die Aufnahme als Ratskandidat. - -Wenn Sie daran interessiert sind, wie der Wahlmechanismus funktioniert, lesen Sie bitte [diesen Beitrag](/democracy_council#elections). - -:::caution -Das HydraDX-Demokratiemodul wird am oder nach dem **15. September 2021** eingeführt. Bitte versuchen Sie vor diesem Datum keine der angezeigten Aktionen. -::: - -## Verwundung von Polkadot/apps {#polkajs} -### Abstimmung bei den Wahlen zu den Ratsmitgliedern {#polkajs-vote} -Die aktuellen Ratsmitglieder sowie die Zweitplatzierten sind auf der Seite [*Governance > Council* page](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council) in Polkadot/apps zu sehen. - -Um Ihre Stimme für die Ratsmitglieder herauszubringen, klicken Sie auf *Vote*. - -
- -
- -Geben Sie die Anzahl der Token ein, die Sie zur Unterstützung Ihrer Kandidaten sperren möchten. - -Wählen Sie anschließend Ihre Kandidaten in der Reihenfolge ihrer Präferenz aus, indem Sie sie von der linken Liste in die rechte Liste verschieben. Denken Sie daran, mehrere Kandidaten auszuwählen - dies hilft dem Algorithmus, die optimale Verteilung der Kandidaten an den Rat auszuwählen. - -Um Ihre Stimme herauszubringen, klicken Sie auf *Vote* und unterschreiben Sie die Transaktion. - -:::note -Gesperrte Token können nicht übertragen werden, sie können jedoch weiterhin zum Abstecken und zur Abstimmung in Volksabstimmungen verwendet werden. Ihre Token bleiben erhalten und werden für nachfolgende Wahlen verwendet, bis Sie sich entschieden haben, sie freizuschalten. -::: - -### Bewerben Sie sich als Ratskandidat {#polkajs-become_candidate} -Sie können Ihren Antrag auf Mitgliedschaft im Rat einreichen, indem Sie zu [*Governance > Council*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council) in Polkadot/apps navigieren. - -Klicken Sie auf *Submit candidacy*, um ein Popup-Fenster auszulösen. - -
- -
- -Wählen Sie das Konto aus, das für die Mitgliedschaft im Council läuft, klicken Sie auf *Submit* und unterschreiben Sie die Transaktion. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/participate_in_referenda.md b/i18n/de/docusaurus-plugin-content-docs/current/participate_in_referenda.md deleted file mode 100644 index 3a7131f6b..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/participate_in_referenda.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -id: participate_in_referenda -title: Teilnahme an Referenda ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Dieser Beitrag bietet eine Schritt-für-Schritt-Anleitung zur Teilnahme an Referenden – Abstimmung und Vorschlag. Es gibt zwei alternative Tools, die Sie zu diesem Zweck verwenden können - [Commonwealth.im](#cw) oder [Polkadot/apps](#polkajs). - -Bevor Sie sich für eine Teilnahme entscheiden, empfehlen wir Ihnen dringend, den [Wissensartikel](/democracy_referenda) im Abschnitt Lernen / Demokratie durchzulesen. Dort finden Sie einige wichtige Details zu den Mechanismen hinter Volksabstimmungen. - -:::caution -Das HydraDX-Demokratiemodul wird am oder nach dem **15. September 2021** eingeführt. Bitte versuchen Sie vor diesem Datum keine der angezeigten Aktionen. -::: - -## Verwendung von Commonwealth.im {#cw} -### Abstimmung auf Referendum {#cw-vote} -Sie können alle Volksabstimmungen einsehen, die zur Abstimmung offen sind, indem Sie auf das [Referenda tab](https://commonwealth.im/hydradx/referenda) auf der HydraDX Commonwealth-Seite navigieren. - -Um über ein aktives Referendum abzustimmen, müssen Sie darauf klicken. Danach sehen Sie eine Seite mit allen relevanten Details. - -Geben Sie im Abschnitt *Cast Your Vote* die folgenden Informationen ein: - -* Abstimmungsbetrag - Dies ist die Menge an HDX-Token, die Sie bereit sind, zur Unterstützung des Referendums zu sperren -* Überzeugungsmultiplikator - Dies ist der Multiplikator, der das [Gewicht Ihrer Stimme](/democracy_referenda#referenda-votes-weighing) mitbestimmt. - -Geben Sie anschließend Ihre Stimme durch Klick auf *Vote yes* oder *Vote no* ab und unterschreiben Sie die Transaktion. - -### Referendum vorschlagen {#cw-propose} -Um ein Referendum vorzuschlagen, besuchen Sie die [HydraDX Commonwealth-Seite](https://commonwealth.im/hydradx/) und klicken Sie im oberen Menü auf *New Thread > New democracy proposal*. - -
- -
- -Füllen Sie die Informationen in den oben angezeigten Feldern aus. Die wichtigsten Parameter sind: -* Modul -* Funktion -* Alle zusätzlichen Informationen, die von der Funktion angegeben werden, die Sie aufrufen möchten -* Einzahlung - die Menge an HDX-Token, die Sie bereit sind, zur Unterstützung des Vorschlags einzuzahlen - -Im obigen Beispiel ist das Angebotsmodul *balances* und die Funktion *setBalance*, die die freien und Reservesalden eines bestimmten Kontos ändert. - -Um den Vorschlag einzureichen, klicken Sie auf *Send transaction* und unterschreiben Sie mit Ihrem Wallet. - -Nachdem Sie den Vorschlag in der Kette eingereicht und die Transaktion unterzeichnet haben, sollte Ihr Vorschlag in der [Liste der vorgeschlagenen Referenden](https://commonwealth.im/hydradx/referenda) erscheinen. - -:::caution -In jeder Abstimmungsperiode geht der Referendumsvorschlag mit der höchsten Unterstützung (*Seconding*) in die Abstimmungsrunde. Da die Zahl der Referenden zunimmt, gibt es keine Garantie dafür, dass Ihr Vorschlag jemals genügend Abordnungen erhält, um an der Abstimmung teilzunehmen. Es gibt keine Möglichkeit, einen Referendumsvorschlag zurückzuziehen, was bedeutet, dass Ihre Gelder möglicherweise für einen längeren Zeitraum gesperrt bleiben. - -Böswillige Referendumsvorschläge werden bestraft. Der HydraDX-Rat und das Technische Komitee haben das Recht, ein bösgläubiges Referendum abzubrechen. Infolgedessen werden die hinterlegten Token verbrannt. -::: - -## Verwendung von Polkadot/apps {#polkajs} -### Abstimmung auf Referendum {#polkajs-vote} -Sie können alle Referenden einsehen, die zur Abstimmung offen sind, indem Sie zu [*Governance > Democracy*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy) in Polkadot/apps navigieren. - -Um bei einem Referendum abzustimmen, klicken Sie daneben auf die Schaltfläche *Vote*. - -Geben Sie im Popup die folgenden Informationen ein: - -* Stimmenwert - Dies ist die Menge an HDX-Token, die Sie bereit sind, zur Unterstützung des Referendums zu sperren -* Überzeugungsmultiplikator - Dies ist der Multiplikator, der das [Gewicht Ihrer Stimme] -(/democracy_referenda#referenda-votes-weighing) mitbestimmt. - -Bringen Sie anschließend Ihre Stimme mit einem Klick auf *Vote Nay* (No) or *Vote Aye* (Yes) * heraus und unterschreiben Sie die Transaktion. - -### Referendum vorschlagen {#polkajs-propose} -Der Vorschlag eines Referendums über Polkadot/Apps besteht aus zwei Schritten – dem Einreichen eines Vorabbilds und dem Einreichen des Vorschlags in der Kette. - -#### 01 Vorabbild senden {#polkajs-propose-01} -Um das Preimage einzureichen, besuchen Sie Polkadot/Apps und navigieren Sie zu - [*Governance > Democracy*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy). - -Nachdem Sie auf *Submit preimage* geklickt haben, sollten Sie das folgende Popup sehen: - -
- -
- -Füllen Sie die Informationen in den oben angezeigten Feldern aus. Die wichtigsten Parameter sind: -* Konto, von dem das Angebot gesendet wird -* Angebotsbereich -* Vorgeschlagene Maßnahmen - -Im obigen Beispiel lautet der Angebotsbereich *balances* und die Aktion *forceTransfer* von Token von einem Konto auf ein anderes. - -Bevor Sie das Preimage einreichen und die Transaktion unterzeichnen, kopieren Sie bitte den Preimage-Hash. Sie benötigen es für den nächsten Schritt. - -#### 02 Vorschlag einreichen {#polkajs-propose-02} -Um den Referendumsvorschlag einzureichen, besuchen Sie - [*Governance > Democracy*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy) in Polkadot/apps. - -Nachdem Sie auf *Submit proposal* geklickt haben, sollten Sie das folgende Popup sehen: - -
- -
- -Geben Sie den Preimage-Hash aus dem vorherigen Schritt und die Anzahl der Token ein, die Sie für das Angebot hinterlegen möchten. Das Minimum ist 100.000 HDX. - -Nachdem Sie den Vorschlag in der Kette eingereicht und die Transaktion unterzeichnet haben, sollte Ihr Vorschlag in der Liste der vorgeschlagenen Referenden erscheinen. - -:::caution -In jeder Abstimmungsperiode geht der Referendumsvorschlag mit der höchsten Unterstützung (*Seconding*) in die Abstimmungsrunde. Da die Zahl der Referenden zunimmt, gibt es keine Garantie dafür, dass Ihr Vorschlag jemals genügend Abordnungen erhält, um an der Abstimmung teilzunehmen. Es gibt keine Möglichkeit, einen Referendumsvorschlag zurückzuziehen, was bedeutet, dass Ihre Gelder möglicherweise für einen längeren Zeitraum gesperrt bleiben. - -Böswillige Referendumsvorschläge werden bestraft. Der HydraDX-Rat und das Technische Komitee haben das Recht, ein bösgläubiges Referendum abzubrechen. Infolgedessen werden die hinterlegten Token verbrannt. -::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/performance_benchmark.md b/i18n/de/docusaurus-plugin-content-docs/current/performance_benchmark.md deleted file mode 100644 index 24472f7f4..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/performance_benchmark.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -id: performance_benchmark -title: Leistungs-Benchmark ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Sie können sicherstellen, dass ihre Hardware die [technischen Mindestanforderungen](/collator_setup#technical-specifications) erfüllt, indem Sie einen Leistungs-Benchmark ausführen. -Nutzen Sie hierfür Folgenden Befehl: - -```bash -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable -$ cd HydraDX-node/ - -# Prepare for running the benchmark -## Install Rust following https://rustup.rs -$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh - -## Configure Rust -$ ./scripts/init.sh -$ rustup default nightly - -## Install additional libraries -$ apt install python3-pip -$ apt install clang - -# Run the benchmark -$ ./scripts/check_performance.sh -``` - -Nachdem Ihr Benchmark ausgeführt wurde sollte ihre Ausgabe ähnlich zu folgedem sein: - -``` - Pallet | Time comparison (µs) | diff* (µs) | diff* (%) | | Rerun -amm | 773.00 vs 680.00 | 93.00 | 12.03 | OK | -exchange | 804.00 vs 720.00 | 84.00 | 10.44 | OK | -transaction_multi_payment| 218.00 vs 198.00 | 20.00 | 9.17 | OK | - -Notes: -- in the diff fields you can see the difference between the reference benchmark time and the benchmark time of your machine -- if diff is positive for all three pallets, your machine covers the minimum requirements for running a HydraDX node -- if diff deviates by -10% or more for some of the pallets, your machine might not be suitable to run a node -``` - -Sie können die Unterschiede in der Leistungsfähigkeit zwischen Ihrem Server und den Mindestanforderungen in der diff* (%)-Spalte sehen. -Wenn alle drei Werte positiv sind sollte Ihr Server in der Lage sein eine HydraDX Validator Node zu betreiben. -Wenn einer der Werte niedriger als -10 % ist empfehlen wir Ihnen vom Betreiben eines Validators auf diesem Server abzusehen. - -Sie können gerne unserem Discord Channel beitreten wenn sie Ihre Benchmark Ergebnisse diskutieren wollen oder Hilfe brauchen. Unsere Community hilft Ihnen gerne! \ No newline at end of file diff --git a/i18n/de/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md b/i18n/de/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md deleted file mode 100644 index 9bd0e18f0..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -id: polkadotjs_apps_local -title: Mit einer lokalen Node verbinden ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Sie können Polkadot/apps verwenden um sich mit ihrem Lokalen HydraDX Node zu verbinden. Dafür ist es nötig Zugang zum Port `9944`zu haben, welcher für RPC Websocket verbindungen verwendet wird. -:::warning - -Wenn Sie den Node als Validator verwenden, empfehlen wir den Port `9944`auf die Blacklist für Remote Zugriffe zu setzen. Dieser Port könnte sonst von Dritten dafür verwendet werden die Performance Ihres Nodes einzuschränken, was wiederum in Slashing oder unbeabsichtigen Verlust von Krypto führen könnte. Sie sollten den Port `9944` nur dann zum Verbinden zu Ihrem Node verwenden wenn dieser in Ihrem Lokalen Netzwerk ist. -::: - -### Über Polkadot/apps mit einer lokalen Node verbinden {#accessing-your-local-node-using-polkadotapps} - -Um auf Ihren Node zuzugreifen öffnen Sie[Polkadot/apps](https://polkadot.js.org/apps/) und klicken Sie in die obere linke Ecke um das Netzwerk zu wechseln. -
- -
- -Nachdem das Menü sich öffnet klicken sie auf **Development** und wählen sie **Local node**. - -
- -
- -Passen Sie die IP wenn nötig an und klicken Sie auf ***Switch*** um zu Ihrer lokalen Node zu wechseln. - -
- -
- -Jetzt sollten Sie mit Ihrer lokalen Node verbunden sein und können nun darauf zugreifen. \ No newline at end of file diff --git a/i18n/de/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md b/i18n/de/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md deleted file mode 100644 index 8a448c61d..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -id: polkadotjs_apps_public -title: Mit einer öffentlichen Node verbinden ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Es gibt zwei Öffentliche RPC Nodes die von HydraDX und unseren Partnern unterhalten werden. Diese können von Ihnen verwendet werden um mit dem Snakenet zu interagieren. Sie können sich direkt mit einem der öffentlichen Nodes verbinden indem Sie auf die unten angeführten Links klicken: - -* [RPC node hosted by HydraDX](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer) - -## Manuell mit einer RPC Node verbinden {#connect-manually-to-an-rpc-node} - -Um einen öffentlichen RPC Node manuell zuzugreifen, öffnen Sie die [Polkadot/apps](https://polkadot.js.org/apps/) und klicken Sie in die obere linke Ecke um das Netzwerk zu wechseln. - - -
- -
- -Klicken sie auf **LIVE NETWORKS** und wählen Sie **HydraDX**. - -
- -
- -Wählen Sie einen der Nodes aus und klicken sie auf **Switch**. - -
- -
- -Nun sollten sie mit dem von Ihnen ausgewählten öffentlichen Node verbunden sein. \ No newline at end of file diff --git a/i18n/de/docusaurus-plugin-content-docs/current/tip_request.md b/i18n/de/docusaurus-plugin-content-docs/current/tip_request.md deleted file mode 100644 index e52ad1cec..000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/tip_request.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -id: tip_request -title: Die Anfrage vom Finanzministerium ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Mit der Einführung des [HydraDX New Deal-Incentive-Programms](#link-to-new-deal) können Community-Mitglieder HDX-Tipps vom Finanzministerium als Belohnung für ihre Beiträge anfordern. Dieser Leitfaden führt Sie durch den Prozess der Trinkgeldanfragen. Weitere Informationen zu den verschiedenen Arten von Aktivitäten, die belohnt werden, finden Sie in [diesem Beitrag](/spending_fw). - -Das Anfordern eines Treasury-Tipps besteht aus zwei Schritten. Im ersten Schritt müssen Beitragende ihre Tipp-Anfrage in Commonwealth.im mit einer Beschreibung des Beitrags veröffentlichen. Als zweiter Schritt muss die Treasury-Tipp-Anfrage mithilfe von Polkadot/Apps on-chain eingereicht werden. - -## 01 Veröffentlichung der Trinkgeldanfrage in Commonwealth.im {#01-publish-tip-request} - -Um die Transparenz zu gewährleisten, müssen alle Treasury-Tipp-Anfragen in einem Thread auf der [HydraDX Commonwealth-Seite] (https://commonwealth.im/hydradx) veröffentlicht werden. Bevor Sie einen Thread öffnen, müssen Sie Ihre HydraDX-Brieftasche mit Commonwealth.im verknüpfen: Klick *Log in* (obere rechte Ecke) und wähl *Connect with wallet > polkadot-js*. - -
- login -
- -Nachdem Sie im Popup Ihre HDX-Adresse ausgewählt haben, werden Sie aufgefordert, die Nachricht mit Ihrem Wallet zu signieren und einen Anzeigenamen für dieses Wallet festzulegen. - -Nachdem Sie sich eingeloggt haben, müssen Sie einen neuen Thread für Ihre Trinkgeldanfrage erstellen. Navigieren Sie zum oberen rechten Teil der Seite und klicken Sie auf *New thread > New thread*. Sie können auch direkt diesen Link verwenden: https://commonwealth.im/hydradx/new/thread. - -Sie können den Titel des Threads verwenden, um das Thema (Tippanfrage) und das Thema des Beitrags anzugeben. Geben Sie im Hauptteil des Threads bitte die folgenden Informationen an: - -* Zeitraum, in dem der Beitrag geleistet wurde -* Eine kurze Zusammenfassung des Beitrags -* Die Höhe des angeforderten Trinkgelds (in HDX) -* Zeitaufwand für den Beitrag (in Stunden) -* Bei Bedarf eine genauere Beschreibung einschließlich der Relevanz des Beitrags zu HydraDX -* Geben Sie ggf. weitere Informationen an, z. B. die Relevanz des Beitrags zu HydraDX und einen Link zur PR (bei technischen Beiträgen) - -Als Referenz können Sie einen Blick auf [diese Beispiel-Tipp-Anfrage] (https://commonwealth.im/hydradx/proposal/discussion/1165-tip-request-add-documentation-for-staking) werfen. - -Nachdem Sie die Informationen ausgefüllt haben, posten Sie den Thread und er sollte in der allgemeinen Liste verfügbar sein. - -:::note - -Nominatoren und Validatoren, die ihr HDX überschuldet haben und „steckengeblieben“ sind, können ein Treasury-Tipp von 1 HDX anfordern, das es ihnen ermöglicht, einige ihrer Token aufzulösen. Wenn dies auf Ihren Fall zutrifft, erstellen Sie bitte einen Commonwealth-Thread nach [diesem Beispiel](https://commonwealth.im/hydradx/proposal/discussion/1166-tip-request-overbonded-staker). - -::: - -## 02 Senden der Tippanforderung On-Chain {#02-submit-on-chain} - -Nachdem Sie Ihre Treasury-Tipp-Anfrage veröffentlicht haben, müssen Sie sie in der Kette einreichen. Zu diesem Zweck muss Ihr Wallet eine kleine Menge HDX enthalten, um die Transaktionsgebühren zu decken. Wenn Sie derzeit kein HDX besitzen, müssen Sie diesen Schritt nicht ausführen – jemand anderes wird Ihre Trinkgeldanforderung für Sie in der Kette einreichen. - -Treasury-Tipp-Anfragen können mit Polkadot / Apps über den folgenden Link in der Kette eingereicht werden: https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/treasury/tips. - -Um eine neue Trinkgeldanfrage zu stellen, klicken Sie auf *Propose tip* und geben Sie die folgenden Informationen ein: - -* **submit with account** - wählen Sie das Konto aus, das die Transaktion zum Senden der Trinkgeldanforderung in der Kette unterschreibt. Dieses Konto muss eine kleine Menge HDX für Transaktionskosten halten. -* **beneficiary** - wählen oder geben Sie die Adresse des Kontos ein, das den Treasury-Tipp erhält. Dieses Konto muss dem Konto entsprechen, das den Commonwealth-Thread eröffnet hat. -* **tip reason** - geben Sie eine URL zum Commonwealth-Thread an. - -
- login -
- -Um die Trinkgeldanfrage zu senden, klicken Sie auf *Propose tip* und unterschreiben Sie die Transaktion. - -Sobald die Transaktion bestätigt ist, sollten Sie die Trinkgeldanfrage auf der Übersichtsseite sehen. - -
- login -
diff --git a/i18n/de/docusaurus-theme-classic/footer.json b/i18n/de/docusaurus-theme-classic/footer.json deleted file mode 100644 index 0ec613d2a..000000000 --- a/i18n/de/docusaurus-theme-classic/footer.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "link.title.Community": { - "message": "Community", - "description": "The title of the footer links column with title=Community in the footer" - }, - "link.item.label.Discord": { - "message": "Discord", - "description": "The label of footer link with label=Discord linking to https://discord.gg/HDNPFFrcnW" - }, - "link.item.label.Twitter": { - "message": "Twitter", - "description": "The label of footer link with label=Twitter linking to https://twitter.com/hydra_dx" - }, - "copyright": { - "message": "Copyright © 2021 Intergalactic, Inc. Built with Docusaurus.", - "description": "The footer copyright" - } -} \ No newline at end of file diff --git a/i18n/de/docusaurus-theme-classic/navbar.json b/i18n/de/docusaurus-theme-classic/navbar.json deleted file mode 100644 index 1843473a5..000000000 --- a/i18n/de/docusaurus-theme-classic/navbar.json +++ /dev/null @@ -1,14 +0,0 @@ -{ - "title": { - "message": "HydraDX Dokumentation", - "description": "The title in the navbar" - }, - "item.label.Docs": { - "message": "Doku", - "description": "Navbar item with label Docs" - }, - "item.label.HydraDX Homepage": { - "message": "HydraDX Webseite", - "description": "Navbar item with label HydraDX Homepage" - } -} \ No newline at end of file diff --git a/i18n/es/code.json b/i18n/es/code.json deleted file mode 100644 index 2e84e9af8..000000000 --- a/i18n/es/code.json +++ /dev/null @@ -1,158 +0,0 @@ -{ - "theme.NotFound.title": { - "message": "Página no encontrada", - "description": "The title of the 404 page" - }, - "theme.NotFound.p1": { - "message": "No pudimos encontrar lo que buscabas.", - "description": "The first paragraph of the 404 page" - }, - "theme.NotFound.p2": { - "message": "Comuníquese con el propietario del sitio que lo vinculó a la URL original y hágale saber que su vínculo no funciona.", - "description": "The 2nd paragraph of the 404 page" - }, - "theme.blog.paginator.navAriaLabel": { - "message": "Navegación por la página de la lista de blogs", - "description": "The ARIA label for the blog pagination" - }, - "theme.blog.paginator.newerEntries": { - "message": "Entradas más recientes", - "description": "The label used to navigate to the newer blog posts page (previous page)" - }, - "theme.blog.paginator.olderEntries": { - "message": "Entradas viejas", - "description": "The label used to navigate to the older blog posts page (next page)" - }, - "theme.blog.post.readingTime.plurals": { - "message": "Lectura de un minuto|{readingTime} minutos de lectura ", - "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.tags.tagsListLabel": { - "message": "Etiquetas:", - "description": "The label alongside a tag list" - }, - "theme.blog.post.readMore": { - "message": "Leer mas", - "description": "The label used in blog post item excerpts to link to full blog posts" - }, - "theme.AnnouncementBar.closeButtonAriaLabel": { - "message": "Cerrar", - "description": "The ARIA label for close button of announcement bar" - }, - "theme.blog.post.paginator.navAriaLabel": { - "message": "Navegación de la página de publicación de blog", - "description": "The ARIA label for the blog posts pagination" - }, - "theme.blog.post.paginator.newerPost": { - "message": "Publicación más reciente", - "description": "The blog post button label to navigate to the newer/previous post" - }, - "theme.blog.post.paginator.olderPost": { - "message": "Entrada antigua", - "description": "The blog post button label to navigate to the older/next post" - }, - "theme.tags.tagsPageTitle": { - "message": "Etiquetas", - "description": "The title of the tag list page" - }, - "theme.blog.post.plurals": { - "message": "Una publicación|{count} publicaciones", - "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.blog.tagTitle": { - "message": "{nPosts} Etiquetado con\"{tagName}\"", - "description": "The title of the page for a blog tag" - }, - "theme.tags.tagsPageLink": { - "message": "Ver todas las etiquetas", - "description": "The label of the link targeting the tag list page" - }, - "theme.CodeBlock.copyButtonAriaLabel": { - "message": "Copiar código al portapapeles", - "description": "The ARIA label for copy code blocks button" - }, - "theme.CodeBlock.copied": { - "message": "Copiado", - "description": "The copied button label on code blocks" - }, - "theme.CodeBlock.copy": { - "message": "Copiar", - "description": "The copy button label on code blocks" - }, - "theme.docs.sidebar.expandButtonTitle": { - "message": "Expandir barra lateral", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.expandButtonAriaLabel": { - "message": "Expandir barra lateral", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.paginator.navAriaLabel": { - "message": "Navegación de páginas de documentos", - "description": "The ARIA label for the docs pagination" - }, - "theme.docs.paginator.previous": { - "message": "Previo", - "description": "The label used to navigate to the previous doc" - }, - "theme.docs.paginator.next": { - "message": "Siguiente", - "description": "The label used to navigate to the next doc" - }, - "theme.docs.sidebar.responsiveCloseButtonLabel": { - "message": "Cerrar menú", - "description": "The ARIA label for close button of mobile doc sidebar" - }, - "theme.docs.sidebar.responsiveOpenButtonLabel": { - "message": "Abrir menú", - "description": "The ARIA label for open button of mobile doc sidebar" - }, - "theme.docs.sidebar.collapseButtonTitle": { - "message": "Contraer barra lateral", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.sidebar.collapseButtonAriaLabel": { - "message": "Contraer barra lateral", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.versions.unreleasedVersionLabel": { - "message": "Esta es documentación inédita para {siteTitle} {versionLabel} versión.", - "description": "The label used to tell the user that he's browsing an unreleased doc version" - }, - "theme.docs.versions.unmaintainedVersionLabel": { - "message": "Esta es documentación para {siteTitle} {versionLabel}, que ya no se mantiene activamente.", - "description": "The label used to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionSuggestionLabel": { - "message": "Para obtener documentación actualizada, consulte {latestVersionLink} ({versionLabel}).", - "description": "The label userd to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionLinkLabel": { - "message": "Última versión", - "description": "The label used for the latest version suggestion link label" - }, - "theme.common.editThisPage": { - "message": "Edita esta página", - "description": "The link label to edit the current page" - }, - "theme.common.headingLinkTitle": { - "message": "Enlace directo al encabezado", - "description": "Title for link to heading" - }, - "theme.lastUpdated.atDate": { - "message": " de {date}", - "description": "The words used to describe on which date a page has been last updated" - }, - "theme.lastUpdated.byUser": { - "message": " por {user}", - "description": "The words used to describe by who the page has been last updated" - }, - "theme.lastUpdated.lastUpdatedAtBy": { - "message": "Última actualización{atDate}{byUser}", - "description": "The sentence used to display when a page has been last updated, and by who" - }, - "theme.common.skipToMainContent": { - "message": "Saltar al contenido principal", - "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation" - } -} \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current.json b/i18n/es/docusaurus-plugin-content-docs/current.json deleted file mode 100644 index bfb45c78b..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current.json +++ /dev/null @@ -1,54 +0,0 @@ -{ - "version.label": { - "message": "Siguiente", - "description": "The label for version current" - }, - "sidebar.sidebar.category.Intro": { - "message": "Intro", - "description": "The label for category Intro in sidebar sidebar" - }, - "sidebar.sidebar.category.Knowledge Base": { - "message": "Base de Conocimientos", - "description": "The label for category Knowledge Base in sidebar sidebar" - }, - "sidebar.sidebar.category.Snakenet": { - "message": "Snakenet", - "description": "The label for category Snakenet in sidebar sidebar" - }, - "sidebar.sidebar.category.Become a validator": { - "message": "Conviértete en validador", - "description": "The label for category Become a validator in sidebar sidebar" - }, - "sidebar.sidebar.category.Connect to a Node": { - "message": "Conectando al nodo", - "description": "The label for category Connect to a Node in sidebar sidebar" - }, - "sidebar.sidebar.category.Other": { - "message": "Otro", - "description": "The label for category Other in sidebar sidebar" - }, - "sidebar.sidebar.category.Contribute": { - "message": "Contribuyendo", - "description": "The label for category Contribute in sidebar sidebar" - }, - "sidebar.sidebar.category.How-to": { - "message": "Cómo", - "description": "The label for category How-to in sidebar sidebar" - }, - "sidebar.sidebar.category.Learn": { - "message": "Aprender", - "description": "The label for category Learn in sidebar sidebar" - }, - "sidebar.sidebar.category.Democracy": { - "message": "Democracia", - "description": "The label for category Democracy in sidebar" - }, - "sidebar.sidebar.category.Maintain": { - "message": "Mantener", - "description": "The label for category Maintain in sidebar sidebar" - }, - "sidebar.sidebar.category.Build": { - "message": "Build", - "description": "The label for category Build in sidebar sidebar" - } -} \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build_dev_chain.md b/i18n/es/docusaurus-plugin-content-docs/current/build_dev_chain.md deleted file mode 100644 index 65cd0f0ea..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/build_dev_chain.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -id: build_dev_chain -title: Configura una Cadena para desarrolladores. ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Esta sección le muestra el proceso de configuración de una instancia de cadena HydraDX local para el desarrollo. - -## 01 Instalar dependencias - -Para preparar una instancia local de HydraDX Chain para el desarrollo, su máquina debe cubrir todas las dependencias para ejecutar una cadena de substrate. Deberá instalar un entorno de desarrollador de Rust y asegurarse de que esté configurado correctamente para compilar el Substrate runtime code para el destino WebAssembly (Wasm). - - -Puede instalar y configurar todas las dependencias manualmente siguiendo la [Substrate guide](https://substrate.dev/docs/en/knowledgebase/getting-started), o puede dejar que este script haga todo el trabajo por usted. - -```bash -$ curl https://getsubstrate.io -sSf | bash -s -- --fast -$ source ~/.cargo/env -``` - -## 02 Crea - -Cree los entornos de ejecución nativos y de Wasm: - -```bash -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable - -# Build the binary -$ cd HydraDX-node/ -$ cargo build --release -``` - -Debería poder encontrar la compilación bajo `./target/release/hydra-dx`. - -## 03 Ejecuta - -Antes de ejecutar su compilación, puede purgar cualquier cadena de desarrollo existente en su máquina (deberá hacer esto a menudo en el proceso de desarrollo): - - - -```bash -$ ./target/release/hydra-dx purge-chain --dev -``` - -Ejecute su compilación usando uno de los siguientes comandos: - - - -```bash -$ ./target/release/hydra-dx --dev - -# Run with detailed logging -$ RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/hydra-dx -lruntime=debug --dev -``` - -## 04 Conéctese a su instancia de cadena local - -Puede conectarse a su nodo de desarrollo HydraDX usando Polkadot / apps y cambiando la red a Desarrollo. También puede utilizar este enlace: -https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/explorer - -connect to node diff --git a/i18n/es/docusaurus-plugin-content-docs/current/claim.md b/i18n/es/docusaurus-plugin-content-docs/current/claim.md deleted file mode 100644 index 76d055d13..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/claim.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -id: claim -title: Reclamar tus HDX ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - - -Tu puedes reclamar tus HDX con los xHDX tokens (ERC-20) que obtuvo durante nuestro [Balancer LBP](https://hydradx.substack.com/p/lbp-announcement) mientras etsuvo activo. - -## Pre-requisitos {#prequisites} -Hay dos requisitos previos para reclamar su HDX. En primer lugar, debe instalar la [extensión del navegador Polkadot.js](https://polkadot.js.org/extension/) que se utilizará para crear su billetera HDX. En segundo lugar, necesita acceso a sus tokens xHDX, que deben almacenarse en una billetera que admita la firma de mensajes relacionados con tokens ERC-20 (por ejemplo, Metamask). - -Si sus tokens xHDX están almacenados en Coinbase Wallet o Trust Wallet, deberá utilizar una de las siguientes soluciones para reclamar su HDX, ya que estas carteras no admiten la firma de mensajes: -* Metamask: puede usar la extensión del navegador Metamask e importar su billetera usando la frase inicial de recuperación. -* MEW (MyEtherWallet): también puede usar MEW importando su frase inicial de recuperación (* Frase mnemónica *) o usando la opción de conexión WalletLink. Se puede acceder a ambas opciones desde la [página de acceso a la billetera MEW](https://www.myetherwallet.com/access-my-wallet). Si está utilizando Coinbase Wallet, puede usar WalletLink, que puede encontrar la Configuración de Coinbase Wallet. - -## Proceso de Reclamo {#claim-process} - -Después de asegurarse de que ha cumplido con los requisitos previos descritos anteriormente, puede navegar a la [aplicación HydraDX Claim](https://claim.hydradx.io) y continuar con el proceso de reclamación. - -Durante el proceso de reclamo, usará sus tokens xHDX (ERC-20) para reclamar su parte de tokens HDX. - -### 00 Autorización {#00-authorize} - -La aplicación HydraDX Claim solicitará la autorización de la extensión del navegador Polkadot.js. - -:::warning -Asegúrese de no ser víctima de un ataque de phishing y preste atención a la ventana emergente de autorización: la aplicación debe identificarse como **CLAIM.HYDRADX.IO** y la solicitud debe provenir de **https://reclamo .hidradx.io**. - -::: - -authorize - -Después de autorizar, se le pedirá que actualice los metadatos para la extensión del navegador Polkadot.js. Esto permitirá que Polkadot.js cree direcciones específicas de HydraDX que se requieren para completar el proceso de reclamo. - -authorize - -### 01 Selecciona tu dirección ETH {#01-select-your-eth-address} - -En el primer paso del proceso de reclamo, se le pedirá que seleccione la cuenta que contiene sus tokens xHDX. Esto se puede hacer conectándose a su billetera con los tokens ERC-20 (por ejemplo, Metamask) o ingresando su dirección ETH manualmente en el cuadro de entrada (en ese caso, deberá firmar el mensaje manualmente más tarde). - -Después de ingresar su dirección ETH, debería ver el saldo de tokens HDX que puede reclamar, incluido el [reembolso de las tarifas del gas](https://hydradx.substack.com/p/first-governance-vote) que ha gastado para obtener su xHDX en Balancer. - -:::note - -No es elegible para un reembolso de gasolina si ha obtenido su xHDX en algún otro lugar que no sea el grupo oficial de Balancer (como Uniswap), o si ha sacado sus tokens de la billetera de compra original. - -::: - -authorize - -### 02 Crea y Selecciona una dirección HDX {#02-create-and-select-an-hdx-address} - -En el segundo paso, se le pedirá que seleccione su dirección HDX. - -Para crear una nueva dirección HDX, abra la extensión del navegador Polkadot.js y haga clic en el signo + para crear una nueva cuenta. En el primer paso de la creación de la cuenta, verá la frase mnemotécnica de 12 trabajos que se puede utilizar para recuperar su cuenta. Después de guardar su frase inicial en un lugar seguro, haga clic en *Siguiente paso*. Aquí, debe cambiar la **Red** seleccionando la opción **HydraDX Snakenet**. Ingrese un nombre y contraseña para su cuenta y finalice la creación de la cuenta. - -authorize - -:::warning - -Asegúrese de hacer una copia de seguridad de su frase inicial de recuperación guardándola en un lugar seguro y nunca la comparta con nadie. Usar la frase inicial es la única forma en que puede recuperar su cuenta y, si la pierde o filtra, sus fondos podrían verse comprometidos. Tenga en cuenta que debe proteger su acceso a esta billetera hasta que se inicie la red principal, ya que todos los saldos de HDX están actualmente bloqueados. Si pierde el acceso a su billetera HDX, también perderá su HDX. - -::: - -Después de crear su cuenta HDX, debería poder seleccionarla en la aplicación HydraDX Claim. Después de hacerlo, la aplicación debería proporcionarle una descripción general de las direcciones ETH y HDX utilizadas para el proceso de reclamo. Haga clic en siguiente para continuar con la firma del mensaje. - -authorize - -### 03 Firma {#03-sign} - -En el tercer paso del proceso de reclamo utilizando la aplicación HydraDX Claim, se le proporcionará la opción de firmar el mensaje para usar sus tokens xHDX para reclamar HDX. - -:::note - -Tenga en cuenta que en este paso verá la **clave pública** de su dirección HDX, y no la dirección en su forma legible por humanos como se mostró en el paso anterior y en la extensión de su navegador Polkadot.js (para más detalles consulte los [ss58 docs](https://polkadot.js.org/docs/keyring/start/ss58)). Si ha seguido todos los pasos descritos anteriormente, no hay nada de qué preocuparse y es seguro continuar con la firma del mensaje. También verificaremos que la cuenta HDX que está utilizando para firmar la transacción de reclamo en el paso final corresponda con la cuenta que recibe el HDX reclamado. - -::: - -Dependiendo de la elección que haya hecho en el primer paso, tiene dos opciones para firmar el mensaje para usar los tokens xHDX en el proceso de reclamo: - -* Si está utilizando **Metamask**, después de hacer clic en el botón *Firmar*, Metamask le pedirá que firme el mensaje. Siga las instrucciones en Metamask. - -* Si ingresó su dirección ETH manualmente, deberá firmar el mensaje a través de la billetera externa que contiene las claves privadas de sus tokens xHDX. Una vez que haya firmado el mensaje, copie la firma (comenzando con *0x*) en el campo respectivo en la aplicación HydraDX Claim. - -authorize - -### 04 Reclamo {#04-claim} - -Después de firmar el mensaje con la billetera que contiene sus tokens xHDX, la extensión Polkadot.js debería abrirse y se le pedirá que firme la transacción para reclamar el HDX a su cuenta. Ingrese la contraseña de su cuenta HDX y haga clic en *Firmar la transacción*. - -¡Ya ha completado el proceso de reclamación, convirtiéndose así oficialmente en propietario de HDX! - -Puede consultar su saldo utilizando [Polkadot/apps](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts) conectado a HydraDX Red: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts diff --git a/i18n/es/docusaurus-plugin-content-docs/current/democracy_council.md b/i18n/es/docusaurus-plugin-content-docs/current/democracy_council.md deleted file mode 100644 index 2efbd46a4..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/democracy_council.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -id: democracy_council -title: Consejo de HydraDX ---- - - -El Consejo HydraDX es una entidad on-chain que desempeña un papel clave en la gobernanza del protocolo. Este artículo proporciona información sobre la [composición](#composition) del Consejo, sus [tareas principales](#tasks) y la [elección de los miembros del Consejo](#elections) - -Para obtener orientación paso a paso sobre cómo participar en las elecciones del Consejo, consulte [esta guía](/participate_in_council_elections). - -## Composición {#composition} -El Consejo HydraDX consta actualmente de **13 miembros**. - -Se reserva una participación minoritaria de 6 asientos para el equipo fundador y los inversores (4 fundadores + 2 inversores). - -Los 7 asientos restantes son elegidos por la comunidad más amplia de titulares de HDX - -## Tareas y responsabilidades {#tasks} - -Las tareas del Consejo HydraDX cubren una amplia gama de actividades de gobernanza diarias. Para empezar, el Consejo controla el Tesoro y aprueba o rechaza las propuestas de la Tesorería. - -El Consejo HydraDX también juega un papel en el mecanismo de referéndum. El Consejo puede iniciar un referéndum, siempre que al menos el 60% de los miembros lo apoyen (supermayoría) y ningún miembro ejerza un veto. En caso de veto, la propuesta puede volver a presentarse una vez transcurrido el período Cool-down. El miembro vetador no puede vetar la misma propuesta dos veces. - -Además, cualquier referéndum propuesto puede cancelarse con una supermayoría de 2/3 de los votos del Consejo. Esto se puede utilizar como medida de último recurso para detener propuestas o cambios maliciosos que podrían introducir errores en el código. - -Finalmente, el Consejo de HydraDX es responsable de elegir al Comité Técnico. - -## Elecciones {#elections} -Cualquier titular de tokens HDX puede [aplicar](/participate_in_council_elections) para uno de los 7 asientos no permanentes del Consejo HydraDX como candidato. - -Las elecciones del Consejo se llevan a cabo cada 7 días, momento en el que un algoritmo llena los 7 puestos no permanentes del Consejo durante los 7 días siguientes. El módulo de democracia utiliza el mismo algoritmo Phragmen que se utiliza para elegir el conjunto activo de validadores in Polkadot. - -Todos los miembros de la comunidad pueden [votar](/participate_in_council_elections) en las elecciones del Consejo bloqueando una cierta cantidad de tokens HDX de su elección. Los tokens bloqueados no están disponibles para su transferencia y se utilizarán en las elecciones de seguimiento (hasta que se cancelen). Los votantes pueden y deben seleccionar más de un candidato en orden de preferencia. Luego, el algoritmo de elección distribuye todos los votos para determinar la asignación óptima de los puestos disponibles en el Consejo a los candidatos con el mayor respaldo de la comunidad. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/democracy_intro.md b/i18n/es/docusaurus-plugin-content-docs/current/democracy_intro.md deleted file mode 100644 index 44ef44088..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/democracy_intro.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -id: democracy_intro -title: Introducción ---- - -HydraDX está en proceso de descentralizar completamente su gobernanza. Todas las decisiones que afectan al protocolo se adoptan siguiendo un proceso democrático que está respaldado por el módulo de democracia de Substrate. El mecanismo central para establecer un consenso entre las partes interesadas es el **referéndum**. - -Esta sección contiene una serie de artículos que deberían proporcionarle una mejor comprensión de los mecanismos detrás de la gobernanza de HydraDX. Encontrará más información sobre [cómo funcionan los referendos](/democracy_referenda), así como sobre los dos grupos centrales de actores de la gobernanza: el [Consejo HydraDX](/democracy_council) y el [Comité Técnico](/democracy_technical_committee). - -Si está buscando una guía práctica sobre cómo participar en la gobernanza de HydraDX, consulte las guías paso a paso sobre [participando en los referendos](/participate_in_referenda y [participar en las elecciones del Consejo](/participate_in_council_elections). - -## Parámetros de democracia - -La siguiente lista contiene los parámetros más importantes que influyen en el mecanismo de gobernanza de HydraDX. Tenga en cuenta que estos pueden cambiar con el tiempo. - -* Depósito mínimo de HDX para iniciar un referéndum: **100,000 HDX** -* Período de promulgación del referéndum: **3 días** -* Periodo de votación del referéndum: **3 días** -* Período de votación de referéndum de emergencia: **3 horas** -* Período Cooloff después del rechazo de un referéndum: **7 días** -* Máximo de propuestas de referéndum pendientes: **100** diff --git a/i18n/es/docusaurus-plugin-content-docs/current/democracy_referenda.md b/i18n/es/docusaurus-plugin-content-docs/current/democracy_referenda.md deleted file mode 100644 index 5b852e22d..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/democracy_referenda.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -id: democracy_referenda -title: Referéndum ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - - -Los referéndums permiten a las partes interesadas someter una propuesta a una votación ponderada y basada en stake por parte de la comunidad en general. El objeto del referéndum es alguna acción sugerida que afecte al protocolo, por ejemplo, un pago de la Tesorería o incluso un cambio en el código runtime - -En términos generales, solo se somete a votación un referéndum a la vez. Otras propuestas de referéndum pendientes se ponen en cola. Hay colas separadas para las propuestas presentadas públicamente y para las propuestas del Consejo. Cada 3 días, el mecanismo de referéndum elige la primera propuesta con la mayor cantidad de apoyo, alternando entre las dos colas. Una vez que se ha votado y aceptado un referéndum, hay un período de * promulgación* de 3 días que debe transcurrir antes de que la decisión entre en vigor. Se aplica una excepción a estas reglas para las propuestas de emergencia del Comité Técnico que se ocupan de los principales problemas de protocolo y deben acelerarse. - -## Iniciando un referéndum {#referenda-initiate} - -Hay varias formas de iniciar un referéndum que se describen con mayor detalle a continuación. La forma en que se inició el referéndum es decisiva para el modo de votación aplicable. - -### Referéndum Público {#referenda-initiate-public} - -Cualquier titular de tokens HDX puede [proponer un referéndum](/participate_in_referenda)) depositando la cantidad mínima requerida de tokens HDX y enviando la propuesta on-chain. Otros miembros de la comunidad pueden [apoyar (*secundar*) la propuesta](/participate_in_referenda) para un referéndum bloqueando una cantidad igual de tokens. Al comienzo de cada ciclo de votación, la propuesta de referéndum con la mayor cantidad de *secundaciones* (total de tokens depositados) se avanza a votación por parte de la comunidad. - -El modo de votación que se aplica a los referendos públicos es [Sesgo de participación positiva](#referenda-voting-modes) - -:::note -Todos los tokens HDX que se depositan para proponer o apoyar un referéndum se bloquean durante todo el período hasta que el referéndum haya entrado en el ciclo de votación. Es importante recordar que no hay garantía de que una propuesta determinada reciba el respaldo suficiente para pasar a la ronda de votación, lo que significa que sus fondos pueden permanecer bloqueados por un período indefinido. -::: - -### Referéndum del Consejo {#referenda-initiate-council} - -El Consejo de HydraDX tiene el poder para proponer un referéndum para que la comunidad lo vote.Si lo hace por unanimidad, el modo de votación aplicable para el referéndum es [Sesgo de participación negativa](#referenda-voting-modes). Si el referéndum se propone con una mayoría simple de los votos del Consejo, entonces el modo de votación para aceptar las propuestas de la comunidad es [Mayoría simple](#referenda-voting-modes). - -### Propuestas de emergencia del Comité Técnico {#referenda-initiate-tech-committee} - -El Comité Técnico puede enviar propuestas de emergencia que se ocupen de la corrección de errores (críticos) o la rápida adopción de funciones probadas en batalla. Las propuestas de emergencia se saltan la cola de espera y entran directamente en la ronda de votación. La comunidad puede votar sobre propuestas de emergencia en paralelo a cualquier propuesta regular que haya entrado en la ronda de votación. Además, las propuestas de emergencia tienen un período de votación más corto para garantizar que puedan acelerarse. - -### Cancelar un referéndum {#cancel} - -Una vez que se ha propuesto un referéndum, no se puede revocar hasta que no haya entrado en la ronda de votación. Se hace una excepción a esta regla para las propuestas que se consideran perjudiciales para el protocolo (por ejemplo, cambios de código que introducen un error). En este caso limitado, la propuesta de referéndum puede ser cancelada por el [Consejo de HydraDX](/democracy_council) (con una supermayoría del 60%) o el [Comité Técnico](/democracy_technical_committee) (por unanimidad). Todos los tokens que fueron bloqueados por los partidarios que secundaban la propuesta se queman. - -## Votación de un Referendum {#referenda-vote} - -Los referendos de HydraDX tienen un período de lanzamiento de 3 días. Al comienzo de cada nuevo período, la propuesta con la mayor cantidad de apoyo se toma de la cola de espera y se coloca en una ronda de votación. Cada ronda de votación tiene una duración de 3 días. Durante este período, los miembros de la comunidad pueden votar en el referéndum utilizando un mecanismo ponderado de base de intereses. Lo hacen bloqueando una cierta cantidad de tokens HDX durante un período de tiempo determinado. - -:::note -Los tokens HDX bloqueados no se pueden transferir durante el período de bloqueo elegido. Sin embargo, todavía se pueden usar para votar. -::: - -### Ponderación de votos {#referenda-votes-weighing} - -Hay dos factores que determinan el peso de cada voto en un referéndum. El primer factor es la **cantidad de tokens HDX** que el votante bloquea en apoyo del voto. El segundo factor es el llamado **multiplicador de convicciones** que refleja la duración durante la cual el votante está dispuesto a bloquear los tokens. - -``` -vote_weight = tokens * conviction_multiplier -``` - -Los períodos de bloqueo de votos tienen la misma duración que el periodo de promulgación. Si los tokens están bloqueados durante 1 período de votación, esto significa que permanecerán bloqueados durante **3 días** después de que finalice la votación. Los votantes pueden influir en el peso de sus votos disminuyendo o aumentando la cantidad de períodos durante los cuales los tokens están bloqueados. Es posible generar un voto con 0 períodos de bloqueo, sin embargo, su peso sería solo una fracción (multiplicador de convicción de 0.1x). Por otro lado, el multiplicador de convicciones aumenta en 1 por cada duplicación de los períodos de bloqueo. Como se muestra en la tabla a continuación, bloquear los votos por un máximo de 32 períodos elevaría el multiplicador de convicciones a 6x. - -| Períodos de bloqueo | Multiplicador de convicciones | -|:-----------------:|:---------------------:| -| 0 | 0.1 | -| 1 | 1 | -| 2 | 2 | -| 4 | 3 | -| 8 | 4 | -| 16 | 5 | -| 32 | 6 | - -``` -Un ejemplo: - -Alice vota con 5000 HDX y 0 períodos de bloqueo. -Bob vota con 100 HDX y 32 períodos de bloqueo. - -Peso de Alice: 500 -Peso de Bob: 600 -``` - -### Modos de votación {#referenda-voting-modes} - -Otro aspecto importante del módulo de democracia son los diferentes modos de votación que se aplican. El umbral de votos necesarios para aprobar o rechazar un referéndum puede variar dependiendo de cómo se inició el referéndum y de la participación de la votación. La participación se calcula en función de la cantidad total de tokens HDX que se utilizaron para votar en el referéndum (se excluyen los multiplicadores de convicciones). Si la participación fue baja o no está determinada por la relación entre la participación y el elactorado (es decir, la cantidad total de tokens HDX elegibles para votar). - -#### Sesgo de participación positiva - -Este es el modo de votación predeterminado cuando la Comunidad propone un referéndum. En participaciones más bajas, se requiere una supermayoría calificada de votos a favor para aprobar el referéndum. A medida que aumenta la participación, el umbral disminuye hacia una mayoría simple. - -
- -
- -#### Sesgo de participación negativa - -Este modo de votación se aplica a los referendos propuestos por el Consejo por unanimidad. Tales propuestas requieren una supermayoría calificada de votos "no" para ser rechazadas con baja participación. A medida que crece la participación, el umbral para rechazar el referéndum disminuye hacia una mayoría simple. - -
- -
- -#### Mayoría simple -Los referémdus iniciados por el Consejo con un acuerdo mayoritario (es decir, no unánimemente) pueden ser aceptados por la comunidad con una mayoría simple de los votos (50% + 1). - -
- -
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/democracy_technical_committee.md b/i18n/es/docusaurus-plugin-content-docs/current/democracy_technical_committee.md deleted file mode 100644 index 24f2ef64e..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/democracy_technical_committee.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -id: democracy_technical_committee -title: Comité técnico ---- - -El Comité Técnico es un grupo de desarrolladores centrales experimentados que es designado directamente por el Consejo de HydraDX. Su tarea principal es salvaguardar la estabilidad técnica del protocolo. - -El Comité Técnico tiene derecho a **producir referendum de emergencia** que se aceleran y se votan en paralelo con cualquier otro referendum activo. Esto permite que el Comité actúe rápidamente y realice cambios críticos (de código). - -Otro poder importante del Comité Técnico es la capacidad de **cancelar propuestas de referéndum** que se consideren perjudiciales para el protocolo. Para cancelar una propuesta de referéndum, el Comité debe estar de acuerdo por unanimidad. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/identity.md b/i18n/es/docusaurus-plugin-content-docs/current/identity.md deleted file mode 100644 index 6d9a178df..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/identity.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -id: identity -title: Establecer tu Identidad ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Los titulares de cuentas tienen la posibilidad de establecer su identidad proporcionando información específica y almacenándola en la cadena. Además de eso, la información de identidad se puede enviar opcionalmente a los registradores de HydraDX para su verificación. Al establecer y verificar su identidad, los validadores y nominadores ayudan a salvaguardar la confianza en la red. - -:::note -Si participa como validador de HydraDX, le recomendamos encarecidamente que establezca su identidad y se someta al proceso de verificación. Los validadores verificados parecen más confiables y atraen más nominaciones, lo que aumenta sus posibilidades de ser incluidos en el conjunto de validadores activos. -::: - -## 01 Establece tu identidad {#01-set-identity} - -Para establecer su identidad, abra Polkadot / apps (conectado a la red HydraDX Snakenet ) y navegue hasta Cuentas . Alternativamente, puede seguir este enlace: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts - -En dicha sección de "Cuentas", ubique la cuenta que contiene sus tokens HDX vinculados. Después de eso, haga clic en los tres puntos junto a la cuenta (en el lado derecho) y seleccione *Establecer identidad en cadena* . - -authorize - -Verá una ventana emergente llamada *identidad de registro* . Aquí, puede ingresar la siguiente información: - -* Nombre legal -* Correo electrónico -* Direccion web -* twitter -* riot name (en caso de que esté utilizando mensajes de Matrix) - -:::note -Toda esta información es opcional; no dude en proporcionar solo la información que desee. Sin embargo, si está ejecutando un nodo de validación, le recomendamos que establezca su correo electrónico. Esto nos permitiría comunicarnos con usted en caso de que encontremos problemas con su nodo. -::: - -En el último campo de la ventana emergente, puede ver la cantidad de HDX que necesita depositar para almacenar su información de identidad. Recibirá este depósito una vez que decida borrar su identidad en un momento posterior. - -authorize - -Después de completar la información, haga clic en *Establecer identidad* y firme la transacción con la extensión del navegador Polkadot.js. Una vez que se confirma la transacción, se establece su identidad. - -## 02 Envie su identidad para verificación {#02-verify-identity} - -Una vez que haya establecido su identidad, puede enviarla a los registradores de la red para su verificación. Para hacerlo, abra Polkadot / apps y vaya a *Desarrollador* > *Extrinsics* . Alternativamente, puede seguir este enlace: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics - -After selecting the relevant HydraDX account from the last step, you need to fill out the following information: - -* **extrinsic**: identity -* **action**: requestJudgement -* **reg_index**: aquí debe ingresar el ID del registrador que elija para realizar la verificación. -HydraDX tiene 2 registradores: Simon Kraus - HydraSik (ID: **0** ) y Jimmy Tudeski - stakenode (ID: **1** ). -* **max_fee**:aquí debe ingresar la tarifa máxima en HDX que está dispuesto a pagar al registrador por la verificación. Solo los registradores con una tarifa inferior a su max_fee serán elegibles para llevar a cabo la verificación. - -Para enviar su solicitud de verificación, haga clic en *Enviar transacción* y firme la transacción. - -authorize - -Tenga en cuenta que el proceso de verificación de identidad puede tardar algún tiempo en completarse. Para ver el estado de su solicitud, vaya a *Cuentas* y coloque el cursor sobre la sección que muestra su identidad; verá una ventana emergente que muestra el estado actual. - -## 03 Resultado del procedimiento de verificación {#03-verification-outcome} - -Después de procesar su solicitud de verificación, el registrador enviará uno de los siguientes juicios que se harán visibles en su estado de identidad: - -* **Desconocido** : valor predeterminado, aún no se ha emitido ningún juicio. -* **Razonable** : la información proporcionada parece razonable, sin embargo, no se realizaron verificaciones en profundidad. -* **Conocido Bueno**: la información es correcta. -* **OutOfDate** : la información era correcta en el pasado, pero ahora está desactualizada. -* **Baja calidad** : la información no es precisa, pero se puede corregir actualizándola. -* **Erróneo** : la información proporcionada es incorrecta y puede indicar una intención maliciosa. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/intro.md b/i18n/es/docusaurus-plugin-content-docs/current/intro.md deleted file mode 100644 index 36205236f..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/intro.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -id: intro -title: Intro -slug: / ---- - - -Bienvenido a los documentos oficiales de HydraDX! Aquí puede encontrar todo tipo de recursos útiles sobre el protocolo HydraDX. Nuestra intención es hacer de este un gran lugar para todos, cubriendo el espectro completo entre visitantes ocasionales, validadores, nominadores y desarrolladores que desean ayudar a construir HydraDX. - -HydraDx esta impulsado por la comunidad, y un ejemplo de ello, son estos documentos. Nos complace ver que todas sus contribuciones, toman formas distintas, por ejemplo, podría escribir un nuevo articulo o traducir uno existente. Si desea contribuir, consulte nuestro, [repoositorio de GitHub](https://github.com/galacticcouncil/HydraDX-docs), asi como algunas [pautas de contribución.](/contributing). - - -# ¿Qué es HydraDX? {#what-is-hydradx} -HydraDX es un protocolo de liquidez de cadena cruzada basado en Substrate. Nuestra misión es permitir una liquidez sin fricciones para todos los criptoactivos mediante la creación del primer pool de liquidez de activos múltiples de su tipo: HydraDX Omnipool. En el Omnipool, varios activos se comparan entre sí mediante el uso de nuestro token nativo HDX como proxy para determinar su valor relativo. Con Omnipool, HydraDX rompe con la concepción tradicional según la cual los activos se negocian por pares utilizando pools aislados. Además de eso, estamos felices de ser parte del ecosistema Polkadot y esperamos convertirnos en el proveedor de liquidez de referencia para todos los activos construidos en Substrate. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/node_monitoring.md b/i18n/es/docusaurus-plugin-content-docs/current/node_monitoring.md deleted file mode 100644 index 66842471f..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/node_monitoring.md +++ /dev/null @@ -1,348 +0,0 @@ ---- -id: node_monitoring -title: Monitoreo de nodo ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -En este capítulo, lo guiaremos a través de la configuración del monitoreo local para su nodo validador. - -## Pre-requisitos {#prerequisites} - -Debe tener su [Nodo collator](/collator_setup) en funcionamiento. -Esta guía se probó en la versión Ubuntu 20.04 LTS. - -## Configuración de Prometheus {#prometheus-setup} - -En el primer paso, configuraremos el servidor Prometheus. - -### Usuario y directorios {#user-and-directories} - -Creamos un usuario solo para fines de monitoreo que no tiene un directorio de inicio y no se puede usar para iniciar sesión. - -```shell script -$ sudo useradd --no-create-home --shell /usr/sbin/nologin prometheus -``` - -Luego creamos directorios para el ejecutable y el archivo de configuración. - -```shell script -$ sudo mkdir /etc/prometheus -$ sudo mkdir /var/lib/prometheus -``` - -Cambie la propiedad de los directorios para restringirlos a nuestro nuevo usuario de monitoreo. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus -$ sudo chown -R prometheus:prometheus /var/lib/prometheus -``` - -### Instalar Prometheus {#install-prometheus} - -Consulte el número de versión más reciente de Prometheus en [GitHub release page](https://github.com/prometheus/prometheus/releases/). -En el momento de escribir este artículo es la v2.25.2. Inserte la última versión de lanzamiento en los siguientes comandos. - -```shell script -# download prometheus -$ wget https://github.com/prometheus/prometheus/releases/download/v2.25.2/prometheus-2.25.2.linux-amd64.tar.gz - -# unpack the binaries -$ tar xfz prometheus-*.tar.gz - -# enter the unpacked directory -$ cd prometheus-2.25.2.linux-amd64 -``` - -Ahora copie los binarios en la carpeta local. - -```shell script -$ sudo cp ./prometheus /usr/local/bin/ -$ sudo cp ./promtool /usr/local/bin/ -``` - -Ahora necesitamos asignar esos binarios a nuestro usuario recién creado. - -```shell script -$ sudo chown prometheus:prometheus /usr/local/bin/prometheus -$ sudo chown prometheus:prometheus /usr/local/bin/promtool -``` - -A continuación, copiaremos la interfaz web y los ajustes preestablecidos de configuración.. - -```shell script -$ sudo cp -r ./consoles /etc/prometheus -$ sudo cp -r ./console_libraries /etc/prometheus -``` - -Y Puede que ya lo hayas adivinado, pero también estamos cambiando la propiedad de esos directorios. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus/consoles -$ sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries -``` - -Ahora tenemos todo lo que necesitamos del paquete descargado, así que daremos un paso atrás y realizaremos una limpieza. - -```shell script -$ cd .. && rm -rf prometheus* -``` - -Creemos un archivo de configuración `YAML` para Prometheus con el editor de su elección (nano / vim / pico). - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Nuestra configuración se divide en tres secciones: - -* `global`: establece los valores predeterminados para `scrape_interval` y el intervalo de ejecución de reglas con `Evaluation_interval´ -* `rule_files`: especifica los archivos de reglas que el servidor Prometheus debe cargar -* `scrape_configs`: aquí es donde configuras los recursos de monitoreo - -Lo mantendremos muy básico y terminaremos con algo como esto: - -```yaml -global: - scrape_interval: 15s - evaluation_interval: 15s - -rule_files: - # - "weHaveNo.rules" - -scrape_configs: - - job_name: "prometheus" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9090"] - - job_name: "substrate_node" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9615"] -``` - -El primer trabajo de scrape exporta datos del propio Prometheus, el segundo exporta las métricas del nodo HydraDX. -Ajustamos el `scrape_interval` de ambos trabajos para obtener estadísticas más detalladas. Esto anula los valores globales. -El `target` en` static_configs` establece dónde se ejecutan los exportadores, aquí nos ceñimos a los puertos predeterminados. - -Después de guardar la configuración, cambiaremos, una vez más, la propiedad. - -```shell script -$ sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml -``` - -### Iniciando Prometheus {#starting-prometheus} - -Para que Prometheus se inicie automáticamente y se ejecute en segundo plano, usaremos `systemd`. -Cree una nueva configuración (nuevamente con el editor de su elección): - -````shell script -$ sudo nano /etc/systemd/system/prometheus.service -```` - -Pegue la siguiente configuración y guarde el archivo. - -``` -[Unit] - Description=Prometheus Monitoring - Wants=network-online.target - After=network-online.target - -[Service] - User=prometheus - Group=prometheus - Type=simple - ExecStart=/usr/local/bin/prometheus \ - --config.file /etc/prometheus/prometheus.yml \ - --storage.tsdb.path /var/lib/prometheus/ \ - --web.console.templates=/etc/prometheus/consoles \ - --web.console.libraries=/etc/prometheus/console_libraries - ExecReload=/bin/kill -HUP $MAINPID - -[Install] - WantedBy=multi-user.target -``` - -A continuación realizaremos los siguientes tres pasos: -`systemctl deamon-reload` carga nuevas configuraciones y actualiza las existentes -`systemctl enable` activa nuestro nuevo servicio -`systemctl start` desencadena la ejecución del servicio - -Puede realizar los pasos anteriores en un comando ejecutando: - -```shell script -$ sudo systemctl daemon-reload && systemctl enable prometheus && systemctl start prometheus -``` - -Ahora debería poder acceder a la interfaz web de Prometheus en http://localhost:9090/. - -## Exportador de nodor {#node-exporter} - -Instalaremos Node Exporter para extraer las métricas del servidor que se utilizarán en el panel. -Compruebe el número de versión de la última versión. [Aqui](https://github.com/prometheus/node_exporter/releases/) y actualice el comando. -En el momento de redactar este artículo, la última versión estaba `1.1.2`. - -### Instalar Node Exporter {#install-node-exporter} - -Descargue la última versión. - -```shell script -$ wget https://github.com/prometheus/node_exporter/releases/download/v1.1.2/node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Desempaquete el archivo que acaba de descargar. Esto creará una carpeta llamada `node_exporter-1.1.2.linux-amd64`. - -```shell script -$ tar xvf node_exporter-1.1.2.linux-amd64.tar.gz -``` - -A continuación, copiamos el binario en nuestro directorio de aplicaciones local y lo asignamos a nuestro usuario de monitoreo. - -```shell script -# copy binary -$ cp node_exporter-1.1.2.linux-amd64/node_exporter /usr/local/bin - -# set ownership -$ sudo chown prometheus:prometheus /usr/local/bin/node_exporter -``` - -Ahora podemos hacer una limpieza y eliminar el paquete descargado y descomprimido. - -```shell script -$ rm -rf node_exporter* -``` - -### Crear un servicio Systemd {#create-a-systemd-service} - -Al igual que prometheus, queremos que Node Exporter también se ejecute como un servicio. -Cree un servicio systemd con su editor de elección. - -```shell script -$ sudo nano /etc/systemd/system/node_exporter.service -``` - -Y pega la siguiente configuración en él. - -``` -[Unit] -Description=Node Exporter -Wants=network-online.target -After=network-online.target - -[Service] -User=prometheus -Group=prometheus -Type=simple -ExecStart=/usr/local/bin/node_exporter - -[Install] -WantedBy=multi-user.target -``` - -Ahora activaremos e iniciaremos el servicio con este resumen. - -```shell script -$ sudo systemctl daemon-reload && systemctl enable node_exporter && systemctl start node_exporter -``` - -### Añade Scrape Job para Node Exporter {#add-scrape-job-for-node-exporter} - -El Exportador de nodos ya está en funcionamiento, pero debemos decirle a Prometheus que extraiga sus datos. -Abriremos el archivo de configuración una vez más con el editor que elijamos. - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Y en la parte inferior del archivo, agregaremos una configuración de scrape más. -Pegue el siguiente contenido y guarde el archivo. - -```yaml - - job_name: 'node_exporter' - scrape_interval: 5s - static_configs: - - targets: ['localhost:9100'] -``` - -Para aplicar la configuración de cambios, es necesario reiniciar el servicio Prometheus. - -```shell script -$ sudo systemctl restart prometheus.service -``` - -Las métricas de su servidor ahora se raspan y se pueden encontrar en la interfaz web de Prometheus. -Los necesitaremos más tarde para nuestro tablero. - -## Grafana Configuración {#grafana-setup} - -Podemos ver nuestras métricas en la interfaz web, pero no es así como queremos monitorearlas. -Lo queremos bonito y bonito. Ahí es donde entra en juego Grafana. - -### Instalar Grafana {#install-grafana} - -Compruebe cuál es la última versión de Grafana [con este link](https://grafana.com/grafana/download?platform=linux). -Puede cambiar el número de versión en los siguientes comandos o copiar los comandos de instalación directamente desde el enlace. -En el momento de escribir este artículo, la última versión era "7.5.1". - -```shell script -$ sudo apt-get install -y adduser libfontconfig1 -$ wget https://dl.grafana.com/oss/release/grafana_7.5.1_amd64.deb -$ sudo dpkg -i grafana_7.5.1_amd64.deb -``` - -El paquete viene con un servicio `systemd` incorporado que configuraremos e iniciaremos como el servicio Prometheus. - -```shell script -$ sudo systemctl daemon-reload && sudo systemctl enable grafana-server && sudo systemctl start grafana-server -``` - -### Acceder a la interfaz web {#accessing-the-web-interface} - -Podremos abrir la interfaz web de Grafana en http://localhost:3000/. -El inicio de sesión predeterminado de Grafana es: -User: `admin` -Password: `admin` - -
- -
- -### Configuración de la fuente de datos {#configuring-the-datasource} - -Haga clic en el engranaje de configuración en el menú y seleccione fuentes de datos. -En la siguiente ventana, haga clic en "Agregar fuente de datos" y seleccione "Prometheus".. - -En el siguiente formulario, no necesita cambiar nada más que la URL. -Colocar`http://localhost:9090/` y clic `Save and Test`. - -
- -
- -### Importando the Dashboard {#importing-the-dashboard} - -Por favor presione el bonton `Plus`en la navegacion principal y selecciona `import`. - -
- -
- -Nosotros usaremos el [HydraDX Dashboard](https://grafana.com/grafana/dashboards/14158) y para cargarlo, simplemente ingrese el id `14158` y presione el botón `Load`. - -
- -
- -No necesita mucha configuración aquí, solo asegúrese de que Prometheus se use como fuente de datos. -Ahora puede finalizar la importación. - -
- -
- -Ahora debería ver su panel de control de inmediato. -Si algunos paneles están vacíos, asegúrese de que su selección sobre los paneles sea así: -* `Chain Metrics`: Substrate -* `Chain Instance`: localhost:9615 -* `Server Job`: node_exporter -* `Server Host`: localhost:9100 diff --git a/i18n/es/docusaurus-plugin-content-docs/current/participate_in_council_elections.md b/i18n/es/docusaurus-plugin-content-docs/current/participate_in_council_elections.md deleted file mode 100644 index 3a39721c5..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/participate_in_council_elections.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -id: participate_in_council_elections -title: Participar en las elecciones del consejo ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Este artículo proporciona una guía paso a paso sobre cómo participar en las elecciones del Consejo: votar por los miembros del Consejo y convertirse en candidato al Consejo. - -Si está interesado en cómo funciona el mecanismo de elección, consulte [esta publicación](/democracy_council#elections). - -:::caution -El módulo de democracia HydraDX se lanzará a partir del **15 de septiembre de 2021**. No intente ninguna de las acciones mostradas antes de esa fecha. -::: - -## Usando Polkadot/apps {#polkajs} -### Votar en las elecciones de miembros del Consejo {#polkajs-vote} - -Puede ver a los miembros actuales del Consejo, así como a los runners-up en la página [*Governance> Consejo*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council) en Polkadot/apps - -Para mostrar su voto por los miembros del Consejo, haga clic en * Voto*. - -
- -
- -Ingrese la cantidad de tokens que está dispuesto a bloquear para apoyar a sus candidatos. - -Después de eso, seleccione sus candidatos en orden de preferencia moviéndolos de la lista de la izquierda a la derecha. Recuerde seleccionar varios candidatos: esto ayudará al algoritmo a seleccionar la distribución óptima de candidatos al Consejo. - -Para mostrar su voto, haga clic en * Voto* y firme la transacción. - -:::note -Los tokens bloqueados no se pueden transferir, sin embargo, aún se pueden usar para votar en referendos. Tus tokens seguirán siendo afortunados y se usarán para elecciones posteriores hasta que decidas desbloquearlos. -::: - -### Aplicar a candidato del Consejo {#polkajs-become_candidate} - -Puede enviar su solicitud para ser miembro del Consejo navegando a [*Governance> Consejo*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council) en Polkadot/apps. - -Click en *Presentar a la candidatura* que activará una ventana emergente. - -
- -
- -Seleccione la cuenta que se está ejecutando para ser miembro del Consejo, haga clic en *Enviar* y firme la transacción. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/participate_in_referenda.md b/i18n/es/docusaurus-plugin-content-docs/current/participate_in_referenda.md deleted file mode 100644 index f4f71396b..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/participate_in_referenda.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -id: participate_in_referenda -title: Participar en Referéndums ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Esta publicación proporciona una guía paso a paso sobre cómo participar en referéndums: votar y proponer. Hay dos herramientas alternativas que puede utilizar para este propósito: [Commonwealth.im](#cw) o [Polkadot/apps](#polkajs). - -Antes de que decida participar, le recomendamos encarecidamente que lea [este artículo](/democracy_referenda) en la sección Aprender / Democracia. Allí encontrará algunos detalles importantes sobre la mecánica de los referendos. - -:::caution -El módulo de democracia HydraDX se lanzará a partir del **15 de septiembre de 2021**. No intente ninguna de las acciones mostradas antes de esa fecha. -::: - -## Usando Commonwealth.im {#cw} -### Votar en un referéndum {#cw-vote} -Puede ver todos los referendos que están abiertos para votación navegando a la [Referenda tab](https://commonwealth.im/hydradx/referenda) en la página HydraDX Commonwealth. - -Para votar en un referéndum activo, debe hacer clic en él. Después de eso, verá una página que muestra todos los detalles relevantes.. - -En la sección *Cast Your Vote*, complete la siguiente información: - -* Cantidad para votar: esta es la cantidad de tokens HDX que está dispuesto a bloquear en apoyo del referéndum. -* Multiplicador de convicciones: este es el multiplicador que co-determina el [peso de su voto](/democracy_referenda#referenda-votes-weighing) - -Después de eso, saque su voto haciendo clic en * Vote yes * o * Vote no * y firme la transacción. - -### Proponer un referéndum {#cw-propose} - -Para proponer un referéndum, visite la [página de HydraDX Commonwealth](https://commonwealth.im/hydradx/) y haga clic en el menú superior en *New Thread > New democracy proposal*. - -
- -
- -Complete la información en los campos que se muestra arriba. Los parámetros más importantes son: -* Module -* Function -* Cualquier información adicional según lo especificado por la función a la que está proponiendo que se realice -* Depósito: la cantidad de tokens HDX que está dispuesto a depositar para respaldar la propuesta. - -En el ejemplo anterior, el módulo de propuesta es *balances* y la función es *setBalance*, que modifica los saldos libres y de reserva de una cuenta determinada. - -Para enviar la propuesta, haga clic en *Send transaction* y firme con su billetera. - -Después de enviar la propuesta on-chain y firmar la transacción, su propuesta debe aparecer en la [list of proposed referenda](https://commonwealth.im/hydradx/referenda). - -:::caution -En cada período de votación, la propuesta de referéndum con el mayor respaldo (*secundando*) ingresa a la ronda de votación. A medida que aumenta la cantidad de referendos, no hay garantía de que su propuesta obtenga el apoyo suficiente para entrar en votación. No hay opción para retirar una propuesta de referéndum, lo que significa que sus fondos pueden permanecer bloqueados por un período de tiempo más largo. - -Las propuestas de referéndum maliciosas son castigadas. El Consejo de HydraDX y el Comité Técnico tienen derecho a cancelar cualquier referéndum propuesto de mala fe. Como resultado, los tokens depositados se quemarán. -::: - -## Usando Polkadot/apps {#polkajs} - -### Votar en un referéndum {#polkajs-vote} - -Puede ver todos los referendos que están abiertos para votación navegando a [*Governance> Democracia*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy) en Polkadot/apps. - - -Para votar en un referéndum, haga clic en el botón *Votar* al lado - -En la ventana emergente, complete la siguiente información: - -* Valor de voto: esta es la cantidad de tokens HDX que está dispuesto a bloquear en apoyo del referéndum. -* Multiplicador de convicciones: este es el multiplicador que co-determina el [peso de su voto](/democracy_referenda#referenda-votes-weighing). - -Después de eso, saque su voto haciendo clic en *Vote Nay* (No) o *Vote Aye* (Sí) y firme la transacción. - -### Proponer un referéndum {#polkajs-propose} - -Proponer un referéndum a través de Polkadot/apps consta de dos pasos: enviar una preimagen y enviar la propuesta on-chain. - -#### 01 Enviar preimagen {#polkajs-propose-01} -Para enviar la preimagen, visite Polkadot/apps y navegue hasta [*Governance > Democracia*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy). - -Después de hacer clic en *Enviar preimagen*, debería ver la siguiente ventana emergente: - -
- -
- -Complete la información en los campos que se muestran arriba. Los parámetros más importantes son: -* Enviar desde la cuenta -* Área donde dice Proponer -* Acción propuesta - -En el ejemplo anterior, el área de propuesta es *balances* y la acción es *forceTransfer* de tokens de una cuenta a otra. - -Antes de enviar la preimagen y firmar la transacción, asegúrese de copiar el hash de la preimagen. Lo necesitará para el siguiente paso. - -#### 02 Subir propuesta {#polkajs-propose-02} -Para presentar la propuesta de referéndum, visite [*Governance > Democracia*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy) en Polkadot/apps. - -Después de hacer clic en *Subir propuesta*, debería ver la siguiente ventana emergente: - -
- -
- - -Ingrese el hash de la preimagen del paso anterior y la cantidad de tokens que está dispuesto a depositar para la propuesta. El mínimo es 100.000 HDX. - -Después de enviar la propuesta on-chain y firmar la transacción, su propuesta debería aparecer en la lista de referendos propuestos. - -:::caution -En cada período de votación, la propuesta de referéndum con el mayor respaldo (*secundando*) ingresa a la ronda de votación. A medida que aumenta la cantidad de referendos, no hay garantía de que su propuesta obtenga el apoyo suficiente para entrar en votación. No hay opción para retirar una propuesta de referéndum, lo que significa que sus fondos pueden permanecer bloqueados por un período de tiempo más largo. - -Las propuestas de referéndum maliciosas son castigadas. El Consejo de HydraDX y el Comité Técnico tienen derecho a cancelar cualquier referéndum propuesto de mala fe. Como resultado, los tokens depositados se quemarán. -::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/performance_benchmark.md b/i18n/es/docusaurus-plugin-content-docs/current/performance_benchmark.md deleted file mode 100644 index 47186b8c2..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/performance_benchmark.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -id: performance_benchmark -title: Benchmark de desempeño ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Puede asegurarse de que su máquina cumpla con las [especificaciones técnicas requeridas](/collator_setup#technical-specifications) ejecutando una evaluación comparativa de rendimiento. Para hacerlo, siga los pasos a continuación: - -```bash -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable -$ cd HydraDX-node/ - -# Prepare for running the benchmark -## Install Rust following https://rustup.rs -$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh - -## Configure Rust -$ ./scripts/init.sh -$ rustup default nightly - -## Install additional libraries -$ apt install python3-pip -$ apt install clang - -# Run the benchmark -$ ./scripts/check_performance.sh -``` - -Después de que se ejecute benchmark, debería ver un resultado similar al siguiente: - -``` - Pallet | Time comparison (µs) | diff* (µs) | diff* (%) | | Rerun -amm | 773.00 vs 680.00 | 93.00 | 12.03 | OK | -exchange | 804.00 vs 720.00 | 84.00 | 10.44 | OK | -transaction_multi_payment| 218.00 vs 198.00 | 20.00 | 9.17 | OK | - -Notes: -- in the diff fields you can see the difference between the reference benchmark time and the benchmark time of your machine -- if diff is positive for all three pallets, your machine covers the minimum requirements for running a HydraDX node -- if diff deviates by -10% or more for some of the pallets, your machine might not be suitable to run a node -``` - -Puede ver la diferencia en el rendimiento entre su máquina y la configuración mínima requerida en la columna **diff* (%)**. Si los tres valores de esta columna son positivos, su máquina debería ser adecuada para ejecutar un nodo validador HydraDX. Si alguno de los valores está por debajo de *-10%*, no recomendamos ejecutar un nodo HydraDX. - -Únase a nosotros en Discord si desea discutir sus resultados de referencia, nuestra comunidad siempre estará feliz de ayudar. \ No newline at end of file diff --git a/i18n/es/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md b/i18n/es/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md deleted file mode 100644 index 4c35f6ca4..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -id: polkadotjs_apps_local -title: Conectarse a un nodo local ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Puede usar Polkadot/apps para conectarse a su nodo HydraDX local. Para este propósito, necesita tener acceso al puerto `9944` que se usa para conexiones de websocket RPC. - -:::warning - -Si está ejecutando el nodo como un validador, le recomendamos encarecidamente que ponga en la lista negra el puerto `9944` para conexiones remotas. Este puerto podría ser abusado por terceros para degradar el rendimiento de su nodo, lo que puede resultar en cortes y pérdidas involuntarias de fondos. Debe usar el puerto `9944` para conectarse a su nodo validador solo cuando el nodo está en su red local. - -::: - -### Accediendo a su nodo local usando Polkadot/apps {#accessing-your-local-node-using-polkadotapps} - -Para acceder a tu nodo usa [Polkadot/apps](https://polkadot.js.org/apps/) y haga clic en en la esquina superior izquierda para cambiar la red. - -
- -
- -Luego de abrir el menu, haga clic en **desarrollo** y selecciona **Nodo local**. -
- -
- -Ajuste la IP si es necesario y haga clic en ***Switch*** para cambiar a su nodo local. - -
- -
- -Ahora debería estar conectado a su nodo local y poder interactuar con él. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md b/i18n/es/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md deleted file mode 100644 index ef70afa7b..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -id: polkadotjs_apps_public -title: Conectarse a un nodo público ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Hay dos nodos RPC públicos que son mantenidos por HydraDX y nuestros socios. Puede utilizar estos nodos para interactuar con Snakenet. Puede conectarse directamente a un nodo público con Polkadot/apps haciendo clic en los enlaces a continuación: - -* [Nodo RPC alojado por HydraDX](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer) - -## Conectarse manualmente a un nodo RPC {#connect-manually-to-an-rpc-node} - -Para acceder a un nodo RPC público manualmente, abra [Polkadot/apps](https://polkadot.js.org/apps/) y haga clic en en la esquina superior izquierda para cambiar la red. - -
- -
- -Clic en **REDES EN FUNCIONAMIENTO** y selecciona **HydraDX**. - -
- -
- -Seleccione uno de los nodos y haga clic en **Switch**. - -
- -
- -Ahora debería estar conectado al nodo RPC público seleccionado. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tip_request.md b/i18n/es/docusaurus-plugin-content-docs/current/tip_request.md deleted file mode 100644 index 2733b50e1..000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/tip_request.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -id: tip_request -title: Soliciar tips de la Tesorería ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Con el lanzamiento del [Programa de incentivos HydraDX New Deal ](#link-to-new-deal), los miembros de la comunidad pueden solicitar tips a la Tesorería como recompensa por sus contribuciones. Con esta guía, podra tener un paso a paso, del proceso de solicitud de tips. Puede encontrar más información sobre los diferentes tipos de actividades que se recompensan en [este post](/spending_fw). - -El proceso para solicitar tips a la Tesorería consta de dos pasos. En el primer paso, los contribuyentes deben publicar su solicitud de tips en Commonwealth.im con una descripción de la contribución. Como segundo paso, la solicitud de tips a la Tesorería debe enviarse on-chain utilizando Polkadot/apps. - -## 01 Publica la solicitud del tips en Commonwealth.im {#01-publish-tip-request} - -Para salvaguardar la transparencia, todas las solicitudes de tips a la Tesorería deben publicarse en un hilo en la [pagina de HydraDX Commonwealth](https://commonwealth.im/hydradx). Before opening a thread, you need to link your HydraDX wallet to Commonwealth.im: Click *Log in* (top right corner) and select *Connect with wallet > polkadot-js*.Antes de abrir un hilo, debe vincular su billetera HydraDX a Commonwealth.im: haga clic en *Log in* (esquina superior derecha) y seleccione *Continue with wallet > polkadot-js* - -
- login -
- -Después de seleccionar su dirección HDX en la ventana emergente, se le pedirá que firme el mensaje con su billetera y que configure un nombre para mostrar con esta billetera. - -Una vez que haya iniciado sesión, debe crear un nuevo hilo para su solicitud del tip. Navegue a la parte superior derecha de la página y haga clic en on *New thread > New thread*. También puede utilizar este link directamente: https://commonwealth.im/hydradx/new/thread . - -Puede utilizar el título del hilo para indicar el tema (tip request) y el tema de la contribución. En el cuerpo del hilo, proporcione la siguiente información en ingles por favor: - -* Periodo en el que se realizó la contribución -* Un breve resumen de la contribución -* El monto del tip solicitado (en HDX) -* Tiempo dedicado a la contribución (en horas) -* Si es apropiado, proporcione información más detallada así como la relevancia de la contribución a HydraDX, y a su vez el link al PR(en caso de ser una contribución técnica) - -Como referencia, puede echar un vistazo a [esta solicitud como ejemplo](https://commonwealth.im/hydradx/proposal/discussion/1165-tip-request-add-documentation-for-staking). - -Después de completar la información, publique el hilo y debería estar disponible en la lista general. - -:::note - -Los nominadores y validadores que hicieron bond de todo su HDX y se "atascaron" pueden solicitar un tip de la Tesorería con valor de 1 HDX que les permitirá hacer unbond de algunos de sus tokens. Si esto se aplica a su caso, cree un hilo de Commonwealth siguiendo [este ejemplo](https://commonwealth.im/hydradx/proposal/discussion/1166-tip-request-overbonded-staker). - -::: - -## 02 Envía la solicitud del Tip On-Chain {#02-submit-on-chain} - -Después de publicar su solicitud de Tips de la Tesorería, debe enviarla de modo on-chain. Para este propósito, su billetera debe contener una pequeña cantidad de HDX para cubrir el fees de la transacción. Si actualmente no tiene ningún HDX, no es necesario que ejecute este paso; alguien más enviará su solicitud del tip on-chain por usted. - -Las solicitudes de los tips de la Tesorería se pueden enviar on-chain con Polkadot/apps usando el siguiente link: https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/treasury/tips. - -Para enviar una nueva solicitud de propina, haga clic en *Proponer gratificación* y proporcione la siguiente información: - -* **enviar con la cuenta** - seleccione la cuenta que firmará la transacción para enviar la solicitud del tip on-chain. Esta cuenta debe tener una pequeña cantidad de HDX para los fees. -* **beneficiario** - seleccione o ingrese la dirección de la cuenta que recibirá el tip de la Tesorería. Esta cuenta debe corresponder a la cuenta que abrió el hilo de Commonwealth. -* **razón de la propina** - proporcione el URL al hilo correspondiente a su Tip de Commonwealth. - -
- login -
- -Para enviar la solicitud del tip, haga clic en *Proponer gratificación* y firme la transacción. - -Una vez que se confirma la transacción, debería ver la solicitud de propina en la página de descripción general. - -
- login -
diff --git a/i18n/es/docusaurus-theme-classic/footer.json b/i18n/es/docusaurus-theme-classic/footer.json deleted file mode 100644 index 95a22fc96..000000000 --- a/i18n/es/docusaurus-theme-classic/footer.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "link.title.Community": { - "message": "Comunidad", - "description": "The title of the footer links column with title=Community in the footer" - }, - "link.item.label.Discord": { - "message": "Discord", - "description": "The label of footer link with label=Discord linking to https://discord.gg/HDNPFFrcnW" - }, - "link.item.label.Twitter": { - "message": "Twitter", - "description": "The label of footer link with label=Twitter linking to https://twitter.com/hydra_dx" - }, - "copyright": { - "message": "Copyright © 2021 Intergalactic, Inc. Built with Docusaurus.", - "description": "The footer copyright" - } -} \ No newline at end of file diff --git a/i18n/es/docusaurus-theme-classic/navbar.json b/i18n/es/docusaurus-theme-classic/navbar.json deleted file mode 100644 index 18947c3d2..000000000 --- a/i18n/es/docusaurus-theme-classic/navbar.json +++ /dev/null @@ -1,14 +0,0 @@ -{ - "title": { - "message": "HydraDX Documentación", - "description": "The title in the navbar" - }, - "item.label.Docs": { - "message": "Documentos", - "description": "Navbar item with label Docs" - }, - "item.label.HydraDX Homepage": { - "message": "HydraDX Página Principal", - "description": "Navbar item with label HydraDX Homepage" - } -} \ No newline at end of file diff --git a/i18n/fr/code.json b/i18n/fr/code.json deleted file mode 100644 index b39c7c98b..000000000 --- a/i18n/fr/code.json +++ /dev/null @@ -1,158 +0,0 @@ -{ - "theme.NotFound.title": { - "message": "Page introuvable", - "description": "The title of the 404 page" - }, - "theme.NotFound.p1": { - "message": "Nous n'avons pas trouvé ce que vous recherchez.", - "description": "The first paragraph of the 404 page" - }, - "theme.NotFound.p2": { - "message": "Veuillez contacter le propriétaire du site qui vous a lié à l'URL d'origine et leur faire savoir que leur lien est cassé.", - "description": "The 2nd paragraph of the 404 page" - }, - "theme.AnnouncementBar.closeButtonAriaLabel": { - "message": "Fermer", - "description": "The ARIA label for close button of announcement bar" - }, - "theme.blog.post.paginator.navAriaLabel": { - "message": "Pagination des blog posts", - "description": "The ARIA label for the blog posts pagination" - }, - "theme.blog.post.paginator.newerPost": { - "message": "Article plus récent", - "description": "The blog post button label to navigate to the newer/previous post" - }, - "theme.blog.post.paginator.olderPost": { - "message": "Article plus ancien", - "description": "The blog post button label to navigate to the older/next post" - }, - "theme.tags.tagsPageTitle": { - "message": "Tags", - "description": "The title of the tag list page" - }, - "theme.blog.paginator.navAriaLabel": { - "message": "Pagination de la liste des posts du blog", - "description": "The ARIA label for the blog pagination" - }, - "theme.blog.paginator.newerEntries": { - "message": "Nouvelles entrées", - "description": "The label used to navigate to the newer blog posts page (previous page)" - }, - "theme.blog.paginator.olderEntries": { - "message": "Anciennes entrées", - "description": "The label used to navigate to the older blog posts page (next page)" - }, - "theme.blog.post.readingTime.plurals": { - "message": "Une minute de lecture|{readingTime} minutes de lecture", - "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.tags.tagsListLabel": { - "message": "Tags :", - "description": "The label alongside a tag list" - }, - "theme.blog.post.readMore": { - "message": "Lire plus", - "description": "The label used in blog post item excerpts to link to full blog posts" - }, - "theme.CodeBlock.copyButtonAriaLabel": { - "message": "Copier le code", - "description": "The ARIA label for copy code blocks button" - }, - "theme.CodeBlock.copied": { - "message": "Copié", - "description": "The copied button label on code blocks" - }, - "theme.CodeBlock.copy": { - "message": "Copier", - "description": "The copy button label on code blocks" - }, - "theme.blog.post.plurals": { - "message": "Un article|{count} articles", - "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.blog.tagTitle": { - "message": "{nPosts} tagués avec « {tagName} »", - "description": "The title of the page for a blog tag" - }, - "theme.tags.tagsPageLink": { - "message": "Voir tous les tags", - "description": "The label of the link targeting the tag list page" - }, - "theme.docs.sidebar.expandButtonTitle": { - "message": "Déplier le menu latéral", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.expandButtonAriaLabel": { - "message": "Déplier le menu latéral", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.paginator.navAriaLabel": { - "message": "Pagination des documents", - "description": "The ARIA label for the docs pagination" - }, - "theme.docs.paginator.previous": { - "message": "Précédent", - "description": "The label used to navigate to the previous doc" - }, - "theme.docs.paginator.next": { - "message": "Suivant", - "description": "The label used to navigate to the next doc" - }, - "theme.docs.sidebar.responsiveCloseButtonLabel": { - "message": "Fermer le menu latéral", - "description": "The ARIA label for close button of mobile doc sidebar" - }, - "theme.docs.sidebar.responsiveOpenButtonLabel": { - "message": "Ouvrir le menu latéral", - "description": "The ARIA label for open button of mobile doc sidebar" - }, - "theme.docs.sidebar.collapseButtonTitle": { - "message": "Réduire le menu latéral", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.sidebar.collapseButtonAriaLabel": { - "message": "Réduire le menu latéral", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.versions.unreleasedVersionLabel": { - "message": "Ceci est la documentation de la prochaine version {versionLabel} de {siteTitle}.", - "description": "The label used to tell the user that he's browsing an unreleased doc version" - }, - "theme.docs.versions.unmaintainedVersionLabel": { - "message": "Ceci est la documentation de {siteTitle} {versionLabel}, qui n'est plus activement maintenue.", - "description": "The label used to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionSuggestionLabel": { - "message": "Pour une documentation à jour, consultez la {latestVersionLink} ({versionLabel}).", - "description": "The label userd to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionLinkLabel": { - "message": "dernière version", - "description": "The label used for the latest version suggestion link label" - }, - "theme.common.editThisPage": { - "message": "Éditer cette page", - "description": "The link label to edit the current page" - }, - "theme.common.headingLinkTitle": { - "message": "Lien direct vers le titre", - "description": "Title for link to heading" - }, - "theme.lastUpdated.atDate": { - "message": " le {date}", - "description": "The words used to describe on which date a page has been last updated" - }, - "theme.lastUpdated.byUser": { - "message": " par {user}", - "description": "The words used to describe by who the page has been last updated" - }, - "theme.lastUpdated.lastUpdatedAtBy": { - "message": "Dernière mise à jour{atDate}{byUser}", - "description": "The sentence used to display when a page has been last updated, and by who" - }, - "theme.common.skipToMainContent": { - "message": "Aller au contenu principal", - "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation" - } -} \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current.json b/i18n/fr/docusaurus-plugin-content-docs/current.json deleted file mode 100644 index 8fcca6e37..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current.json +++ /dev/null @@ -1,34 +0,0 @@ -{ - "version.label": { - "message": "Suivant", - "description": "The label for version current" - }, - "sidebar.sidebar.category.Intro": { - "message": "Introduction", - "description": "The label for category Intro in sidebar sidebar" - }, - "sidebar.sidebar.category.How-to": { - "message": "Comment", - "description": "The label for category How-to in sidebar sidebar" - }, - "sidebar.sidebar.category.Connect to a Node": { - "message": "Se connecter à une Node", - "description": "The label for category Connect to a Node in sidebar sidebar" - }, - "sidebar.sidebar.category.Learn": { - "message": "Apprendre", - "description": "The label for category Learn in sidebar sidebar" - }, - "sidebar.sidebar.category.Maintain": { - "message": "Maintenance", - "description": "The label for category Maintain in sidebar sidebar" - }, - "sidebar.sidebar.category.Contribute": { - "message": "Contribuer", - "description": "The label for category Contribute in sidebar sidebar" - }, - "sidebar.sidebar.category.Build": { - "message": "Build", - "description": "The label for category Build in sidebar sidebar" - } -} \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/build_dev_chain.md b/i18n/fr/docusaurus-plugin-content-docs/current/build_dev_chain.md deleted file mode 100644 index 1c1016a7c..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/build_dev_chain.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -id: build_dev_chain -title: Configurer une chaîne de développement ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Cette section vous guide tout au long du processus de configuration de votre instance locale HydraDX à des fins de développement. - -## 01 installer les dépendances {#01-install-dependencies} - -Pour préparer une instance locale HydraDX pour le développement, votre machine doit avoir toutes les dépendances pour faire fonctionner une chaîne Substrate. Vous devrez installer un environnement de développement Rust et vous assurer qu'il est configuré convenablement pour compiler du code d'exécution Substrate pour une finalité en WebAssembly (Wasm). - -Vous pouvez installer et configurer toutes les dépendances manuellement en suivant le [guide de Substrate](https://substrate.dev/docs/en/knowledgebase/getting-started), ou vous pouvez utiliser le script suivant : - -```bash -$ curl https://getsubstrate.io -sSf | bash -s -- --fast -$ source ~/.cargo/env -``` - -## 02 Construire (build) {#02-build} - -Construire le Wasm et les environnements d'exécution natifs: - -```bash -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable - -# Build the binary -$ cd HydraDX-node/ -$ cargo build --release -``` - -Vous trouverez le build (la construction) dans le dossier suivant `./target/release/hydra-dx`. - -## 03 exécuter {#03-run} - -Avant d'exécuter votre build vous pouvez purger n'importe quel chaîne de développement existante sur votre machine (vous devrez faire ça souvent dans le processus de développement): - -```bash -$ ./target/release/hydra-dx purge-chain --dev -``` - -Exécuter votre build en utilisant une des commandes suivantes: - -```bash -$ ./target/release/hydra-dx --dev - -# Run with detailed logging -$ RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/hydra-dx -lruntime=debug --dev -``` - -## 04 Connectez vous à voitre instance de chaîne locale {#04-connect-to-your-local-chain-instance} - -Vous pouvez vous connecter à votre node de développement HydraDX en utilisant Polkadot/apps et en changeant le réseau en `Développement`. Vous pouvez aussi utilisez ce lien: -https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/explorer - -connect to node diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/claim.md b/i18n/fr/docusaurus-plugin-content-docs/current/claim.md deleted file mode 100644 index 296b37ae7..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/claim.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -id: claim -title: Récupérer vos HDX ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Vous pouvez récupérer vos HDX avec les tokens xHDX (ERC-20) que vous avez obtenus pendant la période où notre [Balancer LBP](https://hydradx.substack.com/p/lbp-announcement) était opérationnel. - -## Prérequis {#prequisites} - -Il y a deux conditions préalables pour récupérer vos HDX. En premier lieu, vous devez installer [l'extension de navigateur Polkadot.js](https://polkadot.js.org/extension/) qui sera utilisée pour créer votre portefeuille HDX. En second lieu, vous devez accéder à vos xHDX qui devraient être stockés dans un portefeuille supportant la signature de messages relatifs aux tokens ERC-20 (par exemple : Metamask). - -Si vos tokens xHDX sont stockés dans un portefeuille Coinbase ou un portefeuille Trust, vous devrez utiliser une des solutions alternatives suivantes pour récupérer vos HDX, puisque ces portefeuilles ne supportent pas la signature de messages: -* Metamask: vous pouvez utiliser l'extension de navigateur Metamask et importer votre portefeuille en utilisant la "seed phrase" de récupération. -* MEW (MyEtherWallet): vous pouvez aussi utiliser MEW soit en important votre "seed phrase" de récupération (*Phrase Mnémontechnique*) ou en utilisant l'option de connexion WalletLink. Les deux options sont accessibles depuis [MEW wallet access page](https://www.myetherwallet.com/access-my-wallet). Si vous utilisez un portefeuille Coinbase, vous pouvez utiliser WalletLink que vous pouvez trouver dans les paramètres du portefeuille Coinbase. - - -## procédure de réclamation {#claim-process} - -Après vous être assuré que vous satisfaites les prérequis décris ci-dessus, vous pouvez vous rendre sur [application de réclamation HydraDX](https://claim.hydradx.io) et effectuer le procédé de récupération. - -Pendant la procédure de récupération, vous allez utiliser vos tokens xHDX (ERC-20) pour récupérer votre part de tokens HDX. - -### 00 Autoriser {#00-authorize} - -L'application de réclamation HydraDX va requérir une autorisation de l'extension de navigateur Polkadot.js. - -:::warning - -assurez vous que vous n'êtes pas victime d'une attaque d'hameçonnage, et soyez attentif au pop-up d'autorisation: L'application devrait s'identifier elle-même comme **CLAIM.HYDRADX.IO** et la requête devrait venir de **https://claim.hydradx.io**. - -::: - -authorize - -Après autorisation, vous serez invité à mettre à jour les métadonnées pour l'extension de navigateur Polkadot.js. Cela permettra à Polkadot.js de créer des adresses spécifiques à HydraDX qui seront nécessaires pour terminer la procédure de récupération. - -authorize - -### 01 Sélectionnez votre adresse ETH {#01-select-your-eth-address} - -Dans la première étape de la procédure de récupération, on vous demandera de choisir votre compte contenant vos tokens xHDX. Ca peut être fait soit en connectant votre portefeuille contenant les tokens ERC-20 (par exemple : Metamask), soit en entrant manuellement votre adresse ETH dans la zone de saisie (auquel cas vous devrez signer le message manuellement plus tard). - -Après avoir entré votre adresse ETH, vous devriez voir le solde de tokens HDX que vous pouvez réclamer, dont le [remboursement des frais de gaz](https://hydradx.substack.com/p/first-governance-vote) que vous avez dépensé pour obtenir vos xHDX sur le Balancer. - -:::note - -Vous n'êtes pas éligible pour un remboursement de gaz si vous avez obtenu vos xHDX à un autre endroit que sur le Balancer pool officiel (par exemple sur Uniswap), ou si vous avez déplacé vos tokens en dehors de votre portefeuille utilisé au moment de l'achat. - -::: - -authorize - -### 02 créez et sélectionnez une adresse HDX {#02-create-and-select-an-hdx-address} - -Dans la seconde étape, on vous demandera de choisir votre adresse HDX. - -Pour créer une nouvelle adresse HDX, ouvre l'extension de navigateur Polkadot.js et cliquez sur le signe "+" pour créer un nouveau compte. Dans la première étape de création de compte, vous verrez la phrase mnémotechnique de 12 mots qui pourra être utilisée pour récupérer votre compte. Après avoir enregistré votre "seed phrase" dans un endroit sûr, cliquez sur *Next step*. Ici, vous devriez changer le **Network** en choisissant l'option **HydraDX Snakenet**. -Saisissez un nom et un mot de passe pour votre compte, et finissez la création de compte. - -authorize - -:::warning - -Assurez vous de conserver votre "seed phrase" de récupération en la stockant dans un endroit sûr et ne la partagez avec personne. Utilisez cette "seed phrase" est le seul moyen pour vous de recouvrer votre compte et si vous la perdez ou la faites fuiter, vos fonds pourraient être compromis. Veuillez noter que vous avez besoin de protéger l'accès à ce portefeuille jusqu'à ce que le mainnet commence, puisque tous les soldes HDX sont actuellement verrouillés. Si vous perdez l'accès à votre portefeuille HDX, vous perdrez en même temps vos HDX. - -::: - -Après avoir créé votre compte HDX, vous devriez être capable de le séléctionner dans l'application de récupération HydraDX. Après l'avoir fait, l'application devrait vous fournir un aperçu des adresses ETH et HDX utilisées pour la procédure de récupération. Cliquez sur suivant pour procéder à la signature du message. - -authorize - -### 03 Signer {#03-sign} - -Dans la troisième étape du processus de récupération en utilisant l'application de récupération HydraDX, vous aurez l'option de signer le message en utilisant vos tokens xHDX pour réclamer vos HDX. - -:::note - -Veuillez noter que dans cette étape vous verrez la **public key** (clé publique) de votre adresse HDX, et non pas l'adresse dans sa forme humainement lisible comme elle était présentée dans les étapes précédentes dans votre extension de navigateur Polkadot.js (pour plus de détails référez vous à [ss58 docs](https://polkadot.js.org/docs/keyring/start/ss58)). Si vous avez suivi toutes les étapes comme décrites ci-dessus, Il n'y a pas d'inquiétude à avoir et il est sûr de continuer avec la signature du message. Nous allons aussi vérifier que le compte HDX que vous utilisez pour signer la transaction de récupération à l'étape finale correspond au compte qui reçoit les HDX réclamés. - -::: - -Selon le choix que vous avez fait à la première étape, vous avez deux options de signature de message pour utiliser les tokens xHDX dans le processus de récupération: - -* Si vous utilisez **Metamask**, après avoir cliqué sur le bouton *sign* (signez) vous serez invité par Metamask à signer le message. Suivez les instructions dans Metamask. - -* Si vous avez entré votre adresse ETH manuellement, vous devrez signer le message via le portefeuille externe qui contient la clé privée de vos tokens xHDX. Une fois que vous avez signé le message, copiez la signature (qui commence par "0x") dans le champ respectif sur l'application de récupération HydraDX. - -authorize - -### 04 Récupération {#04-claim} - -Après avoir signé le message avec le portefeuille contenant vos tokens xHDX, l'extension Polkadot.js devrait s'ouvrir et il vous sera demandé de signer la transaction pour récupérer les HDX sur votre compte. Entrez votre mode de passe de votre compte HDX, et clickez sur *Sign the transaction* (signez la transaction). - -authorize - -Vous avez terminé la procédure de récupération, faisant ainsi de vous un propriétaire de HDX. - -Vous pouvez visualiser votre solde en utilisant Polkadot/apps connecté au réseau HydraDX: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_council.md b/i18n/fr/docusaurus-plugin-content-docs/current/democracy_council.md deleted file mode 100644 index 5be53492e..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_council.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -id: democracy_council -title: HydraDX Council ---- - -Le conseil HydraDX est une entité sur-chaîne qui joue un rôle majeur dans la gouvernance du protocole. Cet article fournit les informations sur la [composition](#composition) du Conseil, ses [tâches principales](#tasks), et l'[élection des membres du Conseil](#elections). - -Pour un guide étape par étape sur comment participer aux élections du Conseil, veuillez vous référer à [ce guide](/participate_in_council_elections). - -## Composition {#composition} -Le conseil HydraDX est composé actuellement de **13 membres**. - -Une part minoritaire de 6 sièges est réservée pour l'équipe fondatrice et les investisseurs (4 fondateurs + 2 investisseurs). - -Les 7 sièges restans sont élus par une communauté plus large de détenteurs de HDX. - -## Tâches et responsabilités {#tasks} -Les tâches du Conseil HydraDX couvrent un large éventail d'activités de gouvernance. Pour commencer, le Conseil contrôle la trésorerie et approuve ou rejette les propositions de trésorerie. - -Le conseil HydraDX joue aussi un rôle dans le mécanisme de référendum. Le Conseil peut initier un référendum, à condition qu'au moins 60% des membres le soutienne (super-majorité) et qu'aucun membre n'exerce un veto. Dans le cas d'un veto, la proposition peut être resoumise après que la période de repos soit passée. Le membre du veto ne peut pas utiliser son veto pour la même proposition deux fois. - -De plus, chaque référendum proposé peut être annulé avec un super-majorité de 2/3 des votes du conseil. Cela peut être utilisé comme dernier recours pour stopper des propositions mal intentionnées ou des changements qui pourraient introduire des bugs dans le code. - -Enfin, le Conseil HydraDX est responsable de l'élection du Comité Technique. - -## Élections {#elections} -Chaque détenteur de token HDX peut [se présenter](/participate_in_council_elections) pour l'un des 7 siège non permanent du Conseil HydraDX en tant que candidat. - -Les élections du conseil prennent place tous les 7 jours, après quoi un algorithme remplit les 7 sièges non-permanents pour la durée des 7 jours suivants. Le module de démocratie utilise le même algorithme Phragmen qui est utilisé pour élire le set de validateurs actifs. - -Tous les membres de la communauté peuvent [voter](/participate_in_council_elections) aux élections du Conseil en verrouillant un certain montant de leur choix de tokens HDX. Les tokens verrouillés ne sont pas disponibles pour transfert et seront utilisés dans les élections suivantes (jusqu'à annulation). Les votants peuvent et devront sélectionner plus d'une candidature dans leur ordre de préférence. L'algorithme d'élection distribue ensuite tous les votes pour déterminer l'allocation optimale des sièges du Conseil disponibles aux candidats avec les plus grands soutiens de la communauté. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_intro.md b/i18n/fr/docusaurus-plugin-content-docs/current/democracy_intro.md deleted file mode 100644 index 974bbc10a..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_intro.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -id: democracy_intro -title: Introduction ---- - -HydraDX est en train de décentraliser complètement sa gouvernance. Toutes les décisions qui affectent le protocole sont adopté selon un processus démocratique qui est supporté par le module de démocratie Substrate. Le mécanisme central pour établir le consensus parmi les parties prenantes est le **référendum**. - -Cette section contient une série d'articles informatifs qui devraient vous fournir une meilleure compréhension des mécanismes derrière la gouvernance de HydraDX. Vous trouverez plus d'informations sur [comment fonctionnent les référendums](/democracy_referenda), ainsi que sur les deux groupes centraux d'acteurs de la gouvernance: le [Conseil HydraDX](/democracy_council) et le [Comité Technique](/democracy_technical_committee). - -Si vous êtes à la recherche de conseils pratiques sur comment participer à la gouvernance de HydraDX, veuillez vous référer aux guides pas à pas sur [participer aux référendums](/participate_in_referenda) et [participer aux élections du conseil](/participate_in_council_elections). - -## Paramètres de démocratie -La liste ci-dessous contient les paramètres les plus importants qui influencent la mécanique de gouvernance sur HydraDX. veuillez noter qu'ils peuvent être amener à changer dans le futur. - - -* Dépôt minimum de HDX pour commencer un référendum: **100 000 HDX** -* Période d'adoption du référendum: **3 jours** -* Période de vote du référendum: **3 jours** -* Période de vote du référendum d'urgence: **3 heures** -* Période de repos après qu'un référendum a été rejeté: **7 jours** -* Maximum de propositions de référendum en attente: **100** \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_referenda.md b/i18n/fr/docusaurus-plugin-content-docs/current/democracy_referenda.md deleted file mode 100644 index f024f4099..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_referenda.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -id: democracy_referenda -title: Référendums ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Les référendums permettent aux parties prenantes de soumettre une proposition à un vote pondéré, basé sur la délégation, par la communauté au sens large. L'objet du référendum est une action suggérée qui affecte le protocole - par exemple, un paiement de trésorerie, ou même un changement dans le code runtime. - -De manière générale, seul un référendum est amené à être voté à la fois. Les autres propositions de référendums en suspens sont mis dans une file d'attente. Il y a des files séparées pour des propositions soumises publiquement et pour des des propositions de Conseil. Tous les 3 jours, le mécanisme de référendums choisit la meilleure proposition avec le plus haut montant de soutient, en alternant entre les deux files d'attente. Après qu'un référendum a été voté et accepté, il y a une période de *délai d'adoption* de 3 jours qui devront s'écouler avant que la décision ne soit effective. Une exception à ces règles s'applique pour les propositions d'urgence par le Comité Technique qui gèrent les problèmes majeurs de protocole et ont besoin d'être accélérées. - -## Lancer un Référendum {#referenda-initiate} -Il y a plusieurs façons de lancer un référendum qui sont décrites plus en détail ci-dessous. La façon dont un référendum est initié est décisive pour le mode de vote applicable. - -### Référendum Public {#referenda-initiate-public} -N'importe quel détenteur de tokens HDX peut [proposer un référendum](/participate_in_referenda) en déposant le montant minimum requis de tokens HDX et en soumettant la proposition sur-chaîne. D'autres membres de la communauté peuvent [soutenir (*appuyer*) la proposition](/participate_in_referenda) pour un référendum en verrouillant un montant égal de tokens. Au début de chaque cycle de vote, la proposition de référendum avec le plus important montant d'*appui* (tokens totaux déposés) est avancé pour un vote par la communauté. - -Le mode de vote qui s'applique aux référendums publics est [Biais de Participation Positif](#referenda-voting-modes). - -:::note -Tous les tokens HDX qui sont déposés pour proposer ou appuyer un référendum sont verouillés jusqu'à ce que le référendum soit entré dans un cycle de vote. Il est important de se rappeler qu'il n'y a pas de garantie qu'une proposition donnée va recevoir assez de soutient pour entrer dans un tour de scrutin, ce qui veut dire que vos fonds pourraient rester verrouillés pendant une période indéfinie. -::: - -### Référendum du Conseil {#referenda-initiate-council} -Le Conseil HydraDX a les pouvoirs de proposer un référendum pour un vote à la communauté. Si cela se fait anonymement, le mode de vote applicable pour le référendum est le [Biais de Participation Négatif](#referenda-voting-modes). Si le référendum est proposé avec une majorité simple des votes du Conseil, alors le mode de vote pour accepter les propositions par la communauté est la [Simple Majorité](#referenda-voting-modes). - -### Propositons d'Urgence par le Comité Technique {#referenda-initiate-tech-committee} -Le comité technique peut soumettre des propositions d'urgence qui gère les corrections de bugs (critiques) ou l'adoption rapide de fonctionalité éprouvée. Les propositions d'urgence sautent la file d'attente et entre directement dans la phase de scrutin. La communauté peut voter les propositions d'urgence en parallèle avec n'importe quelle autre proposition qui a intégré le tour de scrutin. De plus, les propositions d'urgence ont une période de vote plus courtes afin de s'assurer qu'elles sont accélérées. - -### Annuler un Référendum {#cancel} -Une fois qu'un référendum a été proposé, il ne peut pas être révoqué avant d'entrer le tour de scrutin. Une exception à cette règle est faite pour les propositions qui sont jugées préjudiciables au protocole (ex: des changement de code qui introduisent un bug). Dans ce cas précis, la proposition de référendum peut être annulée par le [conseil HydraDX](/democracy_council) (avec une super majorité de 60%) ou le [Comité Technique](/democracy_technical_committee) (à l'unanimité). Tous les tokens qui étaient verrouillés par les soutiens appuyant la proposition sont détruits. - -## Voter dans un référendum {#referenda-vote} -Les référendums HydraDX ont une période de lancement de 3 jours. Au début de chaque période, la proposition avec le plus au montant d'appuis est prise depuis la file d'attente et soumise au tour de scrutin. Chaque tour de scrutin a une durée de 3 jours. Pendant cette période, les membres de la communauté peuvent voter au référendum en utilisant un mécanisme pondéré, basé sur la délégation. Ils le font en verrouillant un certain montant de tokens HDX pour une période de temps donnée. - -:::note -Les tokens HDX verrouillés ne peuvent pas être transférés pendant la durée de la période de verrouillage choisie. Cependant, ils peuvent toujours être utilisés pour la délégation et le vote. -::: - -### Pesée des Votes {#referenda-votes-weighing} -Il y a deux facteurs qui déterminent le poids de chaque vote dans un référendum. Le premier facteur est le **montant de tokens HDX** que le votant verrouille en soutient au vote. Le second facteur est le soi-disant **conviction multiplier (multiplicateur de conviction)** qui reflète la durée pendant laquelle le votant est prêt à verrouiller ses tokens. - -``` -poids_du_vote = tokens * multiplicateur_de_conviction -``` - -Les périodes de verrouillage de vote ont la même durée que les délais d'adoption. Si les tokens sont verrouillés pour 1 période de vote, cela signifie qu'ils vont rester verrouillés pour **3 jours** après que le vote soit terminé. Les votants peuvent influencer le poids de leur vote en diminuant ou en augmentant le montant de périodes pendant lesquelles les tokens seront verrouillés. Il est possible de participer à un vote avec une période de verrouillage de 0 jour, cependant son poids serait seulement une fraction de ce qu'il serait autrement (multiplicateur de conviction de 0,1). D'un autre côté, le multiplicateur de conviction augmente de 1 pour chaque doublement des périodes de verrouillages. Comme montré dans le tableau ci-dessous, verrouiller les votes pour un maximum de 32 période augmenterait le multiplicateur de conviction à 6. - -| Périodes de verrouillages | Multiplicateur de conviction | -|:------------------------------:|:----------------------------:| -| 0 | 0.1 | -| 1 | 1 | -| 2 | 2 | -| 4 | 3 | -| 8 | 4 | -| 16 | 5 | -| 32 | 6 | - -``` -Un exemple: - -Alice vote avec 5000 HDX et 0 période de verrouillage. -Bob vote avec 100 HDX et une 32 périodes de verrouillage. - -Poids du vote d'Alice: 500 -Poids du vote de Bob: 600 -``` - -### Modes de Scrutins {#referenda-voting-modes} -Un autre aspect important du module de démocratie sont les différents modes de scrutin qui s'appliquent. Le seuil de votes requis pour approuver ou rejeter un référendum peut varier selon comment le référendum a été lancer et selon la participation au vote. La participation est calculée en se basant sur le montant total de HDX qui étaient utilisés pour voter le référendum (multiplicateurs de conviction exclus). Que la participation soit basse ou non est déterminé par la relation entre la participation et l'électorat (Le nombre total de HDX éligible au vote). - -#### Biais de Participation Positif -C'est le mode de scrutin par défaut quand un référendum est proposé par la communauté. Avec des participations basses, une super majorité qualifié de `yes`/`oui` est requise afin d'approuver le référendum. Au fur et à mesure que la participation augmente, le seuil diminue jusqu'à une simple majorité. -
- -
- -#### Biais de Participation Négatif -Ce mode de scrutin s'applique aux référendums qui ont été proposés par le Conseil à l'unanimité. De telles propositions exigent une super majorité qualifiée de vote `no`/`non` pour être rejetées avec des participations basses. Au fur et à mesure que la participation augmente, le seuil pour rejeter le référendum diminue à une simple majorité. - -
- -
- -#### Simple Majorité -Les référendums qui ont été lancés par le Conseil avec un accord majoritaire (non anonymement) peuvent être acceptés par la communauté avec une simple majorité des votes (50% + 1). - -
- -
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_technical_committee.md b/i18n/fr/docusaurus-plugin-content-docs/current/democracy_technical_committee.md deleted file mode 100644 index 2659585f4..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/democracy_technical_committee.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -id: democracy_technical_committee -title: Comité Technique ---- - -Le comité technique est un groupe de développeurs expérimentés phares qui sont nommés directement par le Conseil HydraDX. Sa tâche principale est de sauvegarder la stabilité technique du protocole. - -Le Comité Technique a le droit de **produire des référendums d'urgence** qui sont accélérés et votés en parallèle avec tout autre référendum actif. Cela permet au Comité d'agir rapidement et de délivrer des changements (de codes) critiques. - -Un autre pouvoir important du Comité Technique est la capacité à **annuler des propositions de référendum** qui sont jugées nocives pour le protocole. De façon à annuler une proposition de référendum, le Comité doit unanimement tomber d'accord. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/identity.md b/i18n/fr/docusaurus-plugin-content-docs/current/identity.md deleted file mode 100644 index 36fba7907..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/identity.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -id: identity -title: définir votre identité ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Les titulaires de compte ont la possibilité de définir leur identité en fournissant des informations spécifiques et en les stockant on-chain (sur la chaîne). Par ailleurs, l'information de l'identité peut optionnellement être soumise aux gérants de registres pour vérification. En définissant et en vérifiant leur identité, les validateurs et les nominateurs aident à maintenir la confiance du réseau. - -:::note -Si vous participez en tant que validateur HydradDX nous **recommandons fortement** de vérifier votre identité et fassiez les étapes de vérification. Les validateurs vérifiés paraissent plus fiables et attirent plus de nominations, et augmente ainsi leurs chances d'être inclus dans l'ensemble des validateurs actifs. -::: - -## 01 Définir votre identité {#01-set-identity} - -Pour définir votre identité, ouvrez Polkadot/apps (connecté au réseau *HydraDX Snakenet* ) et naviguez jusqu'à *Mes comptes*. Sinon, vous pouvez suivre ce lien: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts - -Sur la page des comptes, repérez le compte qui contient vos tokens HDX engagés. Après ça, cliquez sur les trois points à côté du compte (sur la droite) et sélectionnez *Définir l'identité sur la chaîne de bloc*. - -authorize - -Vous verrez une nouvelle fenêtre appelée *enregistrer votre identité*. Ici, vous pouvez entrer les informations suivantes: - -* nom légal -* email -* adresse web (web) -* twitter -* nom matrix (riot name en anglais) (au cas où vous utilisez la messagerie Matrix) - -:::note -Toutes ces informations sont facultatives - renseignez seulement les informations que vous souhaitez. Si vous gérez un node de validation, nous vous encourageons à renseigner votre email, cela nous permettra de vous contacter en cas de soucis avec votre node de validation -::: - -Dans le dernier champ de la fenêtre, vous pouvez voir le montant de HDX que vous devez déposer pour garder les informations relatives à votre identité. Vous récupérerez la caution si vous déciderez de supprimer votre identité. - -authorize - -Après avoir rempli les informations, cliquez sur *Définir l'identité* et signer la transaction en utilisant l'extension de navigateur Polkadot.js. Une fois que la transaction est confirmée, votre identité est définie. - -## 02 Soumettre votre identité pour vérification {#02-verify-identity} - -Après avoir défini votre identité, vous pouvez la soumettre aux gérants de registres pour vérification. Ouvrez Polkadot/apps et naviguez jusqu'à *Développeur* > *Extrinsics*. Ou cliquez sur le lien suivant: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics - -Après avoir sélectionné le compte HydraDX approprié (de l'étape précédente), vous devez remplir les informations suivantes: - -* **extrinsic**: identity -* **action**: requestJudgment -* **reg_index**: Ici vous devez entrez l'ID du gérant de registre que vous choisissez pour procéder à la vérification. HydraDX a deux gérants de registres: Simon Kraus - HydraSik (ID: **0**) et Jimmy Tudeski - stakenode (ID: **1**). -* **max_fee**: Ici vous devez entrer le montant de frais maximum en HDX que vous êtes prêt à payer au registraire pour la vérification. Seuls les registraires avec des frais inférieurs à votre max_fee vont être éligible pour effectuer la vérification. - -Pour soumettre la requête de vérification, cliquez sur *Soumettre la transaction* (*Submit Transaction* en anglais) et signez la transaction. - -authorize - -Veuillez noter que le processus de vérification d'identité peut prendre du temps. Pour voir le statut de votre requête, naviguez jusque **Mes comptes** et passez le curseur sur la section montrant votre identité - vous verrez une fenêtre popup montrant le statut actuel. - -## 03 Résultat de la procédure de vérification {#03-verification-outcome} - -Après avoir effectué votre requête de vérification, le registraire va soumettre un des jugements suivants qui va devenir visible dans votre statut d'identité: - -* **Unknown** - valeur par défaut, aucun jugement n'a encore été émis. -* **Reasonable** - les informations fournies paraissent raisonnables, cependant, aucune vérification en profondeur n'a été effectuée. -* **KnownGood** - l'information est correcte. -* **OutOfDate** - l'information était correcte avant, mais est n'est plus à jour. -* **LowQuality** - l'information est imprécise mais peut être corrigée en la mettant à jour. -* **Erroneous** - l'information fournie est fausse et pourrait indiquer une intention malveillante. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/intro.md b/i18n/fr/docusaurus-plugin-content-docs/current/intro.md deleted file mode 100644 index f92a5585e..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/intro.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -id: intro -title: Commencer -slug: / ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Bienvenue sur les documentations officielles HydraDX ! Ici vous pouvez trouver toutes les ressources utiles sur le protocole HydraDX. Notre intention est d'en faire un endroit incontournable pour tous, couvrant le spectre complet, des visiteurs occasionnels, en passant pas les validateurs, les nominateurs, jusqu'aux développeurs qui veulent aider à construire HydraDX. - -HydraDX est conduit par sa communauté, ainsi que les sont ces documentations. Nous sommes heureux de voir vos contributions, qui peuvent prendre plusieurs formes - par exemple, vous pourriez écrire un nouvel article ou en traduire un existant. Regardez notre [dépôt GitHub](https://github.com/galacticcouncil/HydraDX-docs) ainsi que certaines [lignes directrices de contribution](/contributing). - -## Qu'est-ce que HydraDX? {#what-is-hydradx} - -HydraDX est un protocole de liquidité inter-chaînes construit sur la technologie Substrate. Notre mission est de permettre les liquidités fluides ("frictionless" en anglais) pour tous les actifs crypto en construisant la première réserve de liquidité (liquidity pool) multi-actifs de son genre - L'Omnipool HydraDX (ou Omniréserve). Dans l'Omnipool, -différents actifs sont évalués les uns par rapport aux autres en utilisant nos token HDX natifs comme un intermédiaire pour déterminer leur valeur relative. Avec l'Omnipool, HydraDX rompt avec la conception traditionnelle selon laquelle les actifs sont négociés par paires en utilisant des réserves (pools) isolées. En outre, nous sommes heureux de faire partie de l'écosystème Polkadot et nous espérons devenir le fournisseur de liquidités principal pour tous les actifs construits sur Substrate. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/node_monitoring.md b/i18n/fr/docusaurus-plugin-content-docs/current/node_monitoring.md deleted file mode 100644 index 1684ace94..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/node_monitoring.md +++ /dev/null @@ -1,348 +0,0 @@ ---- -id: node_monitoring -title: Supervision de node ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Dans ce chapitre nous allons vous guider tout au long du réglage d'une solution de monitoring locale pour votre node validateur. - -## Prérequis {#prerequisites} - -Vous devez avoir votre [node collateur](/collator_setup) installé et actif. -Ce guide a été testé sous la version Ubuntu 20.04 LTS. - -## Réglages de Prometheus {#prometheus-setup} - -Dans la première étape nous allons installer le serveur Prometheus. - -### User et Directories {#user-and-directories} - -Nous créons un user (utilisateur), _prometheus_, juste à des fins de monitoring qui n'a pas de répertoire home et ne peut pas être utilisé pour ouvrir une session. - -```shell script -$ sudo useradd --no-create-home --shell /usr/sbin/nologin prometheus -``` - -Puis nous créons des répertoires pour le fichier exécutable et les fichiers de configuration. - -```shell script -$ sudo mkdir /etc/prometheus -$ sudo mkdir /var/lib/prometheus -``` - -Nous allons changer le propriétaire des répertoires pour restreindre l'accès au nouvel utilisateur, _prometheus_. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus -$ sudo chown -R prometheus:prometheus /var/lib/prometheus -``` - -### Installer Prometheus {#install-prometheus} - -Vérifier le numéro de la dernière version de Prometheus sur la [page de sorties GitHub](https://github.com/prometheus/prometheus/releases/). -Au moment de l'écriture de l'article, la dernière version est la v2.25.2. Insérer la dernière version dans les lignes de commandes suivantes. - -```shell script -# download prometheus -$ wget https://github.com/prometheus/prometheus/releases/download/v2.25.2/prometheus-2.25.2.linux-amd64.tar.gz - -# unpack the binaries -$ tar xfz prometheus-*.tar.gz - -# enter the unpacked directory -$ cd prometheus-2.25.2.linux-amd64 -``` - -Maintenant copier les binaires dans votre dossier local. - -```shell script -$ sudo cp ./prometheus /usr/local/bin/ -$ sudo cp ./promtool /usr/local/bin/ -``` - -Nous devons maintenant définir le nouvel utilisateur, _prometheus_, comme étant propriétaire de ces binaires. - -```shell script -$ sudo chown prometheus:prometheus /usr/local/bin/prometheus -$ sudo chown prometheus:prometheus /usr/local/bin/promtool -``` - -Ensuite nous allons copier l'interface web et les pré-configurations. - -```shell script -$ sudo cp -r ./consoles /etc/prometheus -$ sudo cp -r ./console_libraries /etc/prometheus -``` - -Vous l'avez peut-être deviné, mais nous allons aussi changer le propriétaire de ces répertoires. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus/consoles -$ sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries -``` - -Maintenant que nous avons tous les paquets nécessaires, nous pouvons remonter d'un niveau et supprimer le dossier contenant les sources. - -```shell script -$ cd .. && rm -rf prometheus* -``` - -Création du fichier de configuration, _prometheus.yml_, avec l'éditeur de votre choix (nano / vim / pico). - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Notre config est divisé en trois sections: - -* `global`: sets the default values for `scrape_interval` and the rule-execution interval with `evaluation_interval` -* `rule_files`: specify rule-files the Prometheus server should load -* `scrape_configs`: this is where you set the monitoring-resources - -Nous allons rester simples et terminer avec cette configuration: - -```yaml -global: - scrape_interval: 15s - evaluation_interval: 15s - -rule_files: - # - "weHaveNo.rules" - -scrape_configs: - - job_name: "prometheus" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9090"] - - job_name: "substrate_node" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9615"] -``` - -La première tâche d'organisation de données (scrape) exporte les données de Prometheus, la seconde exporte les mesures du node HydraDX. -Nous avons réglé le `scrape_interval` de chaque tâche pour avoir des statistiques plus détaillées. Cela remplace les valeurs globales. -Le `target` dans `static_configs` définit où les exportateurs fonctionnent, nous nous en tenons aux ports par défaut ici. - -Après avoir sauvegardé la configuration nous allons - encore une fois - changer le propriétaire. - -```shell script -$ sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml -``` - -### Démarrer Prometheus {#starting-prometheus} - -Pour faire démarrer Prometheus automatiquement et fonctionner en arrière-plan nous allons créer un service Prometheus avec `systemd`. -Créez un nouveau config (encore avec l'éditeur de votre choix): - -````shell script -$ sudo nano /etc/systemd/system/prometheus.service -```` - -Coller les configurations suivantes et sauvegardez le fichier. - -``` -[Unit] - Description=Prometheus Monitoring - Wants=network-online.target - After=network-online.target - -[Service] - User=prometheus - Group=prometheus - Type=simple - ExecStart=/usr/local/bin/prometheus \ - --config.file /etc/prometheus/prometheus.yml \ - --storage.tsdb.path /var/lib/prometheus/ \ - --web.console.templates=/etc/prometheus/consoles \ - --web.console.libraries=/etc/prometheus/console_libraries - ExecReload=/bin/kill -HUP $MAINPID - -[Install] - WantedBy=multi-user.target -``` - -Ensuite nous allons effectuer les trois étapes suivantes: -`systemctl daemon-reload` charge les nouvelles configurations et met à jour celles existantes. -`systemctl enable` active notre nouveau service -`systemctl start` déclenche l'exécution du service. - -Vous pouvez effectuer les étapes au dessus en une commande en exécutant: - -```shell script -$ sudo systemctl daemon-reload && systemctl enable prometheus && systemctl start prometheus -``` - -Vous devriez maintenant être capable d'accéder à l'interface web de Prometheus à http://localhost:9090/. - -## Node Exporter {#node-exporter} - -Nous allons installer Node Exporter pour organiser les métriques du serveur qui vont être remontées dans le tableau de bord. -Veuillez vérifier le numéro de la dernière version [ici](https://github.com/prometheus/node_exporter/releases/) et mettez la commande à jour. -Au moment de l'écriture de l'article la dernière version est `1.1.2`. - -### Installer Node Exporter {#install-node-exporter} - -Télécharger la dernière version. - -```shell script -$ wget https://github.com/prometheus/node_exporter/releases/download/v1.1.2/node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Extraire l'archive que vous venez de télécharger. Cela créera un dossier appelé `node_exporter-1.1.2.linux-amd64`. - -```shell script -$ tar xvf node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Ensuite nous copions le binaire dans notre répertoire local d'application and l'assignons à notre utilisateur superviseur. - -```shell script -# copy binary -$ cp node_exporter-1.1.2.linux-amd64/node_exporter /usr/local/bin - -# set ownership -$ sudo chown prometheus:prometheus /usr/local/bin/node_exporter -``` - -Nous pouvons maintenant faire un peu de ménage et supprimer les paquets téléchargés et extraits. - -```shell script -$ rm -rf node_exporter* -``` - -### Créer un Service Systemd {#create-a-systemd-service} - -De la même façon que Prometheus nous voulons que Node Exporter fonctionne comme un service aussi. -Créez un service systemd avec l'éditeur de votre choix. - -```shell script -$ sudo nano /etc/systemd/system/node_exporter.service -``` - -Et copiez y la configuration suivante. - -``` -[Unit] -Description=Node Exporter -Wants=network-online.target -After=network-online.target - -[Service] -User=prometheus -Group=prometheus -Type=simple -ExecStart=/usr/local/bin/node_exporter - -[Install] -WantedBy=multi-user.target -``` - -Nous allons maintenant activer et démarrer le service avec cette simple ligne de commande. - -```shell script -$ sudo systemctl daemon-reload && systemctl enable node_exporter && systemctl start node_exporter -``` - -### Ajouter Scrape Job pour Node Exporter {#add-scrape-job-for-node-exporter} - -Le Node Exporter est maintenant actif et opérationnel mais nous devons dire à Prometheus d'organiser (scrape) ses données. -Nous allons ouvre le fichier de configuration, _prometheus.yml_, encore une fois avec l'éditeur de votre choix. - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Et à la toute fin du fichier nous allons ajouter un scrape config de plus. -Coller le contenu suivant et sauvegarder le ficher. - -```yaml - - job_name: 'node_exporter' - scrape_interval: 5s - static_configs: - - targets: ['localhost:9100'] -``` - -L'application des changements de configuration au redémarrage du service Prometheus est requise. - -```shell script -$ sudo systemctl restart prometheus.service -``` - -Les métriques de votre serveur sont maintenant organisées (scraped) et peuvent être trouvées dans l'interface web Prometheus. -Nous allons en avoir besoin plus tard pour notre tableau de bord. - -## Configuration de Grafana {#grafana-setup} - -Nous pouvons voir nos métriques dans l'interface web, mais ce n'est pas la façon dont on veut les superviser. -On les veut belles et propres. C'est là que Grafana entre en jeu. - -### Installer Grafana {#install-grafana} - -Veuillez vérifier quelle est la dernière version de Grafana [avec ce lien](https://grafana.com/grafana/download?platform=linux). -Vous pouvez soit changer le numéro de version dans les commandes suivantes ou copier les commandes d'installation directement depuis le lien. -Au moment de l'écriture de l'article la dernière version est `7.5.1`. - -```shell script -$ sudo apt-get install -y adduser libfontconfig1 -$ wget https://dl.grafana.com/oss/release/grafana_7.5.1_amd64.deb -$ sudo dpkg -i grafana_7.5.1_amd64.deb -``` - -Le paquet est fourni avec un service `systemd` intégré que nous allons configurer et démarrer exactement comme le service Prometheus. - -```shell script -$ sudo systemctl daemon-reload && sudo systemctl enable grafana-server && sudo systemctl start grafana-server -``` - -### Accéder à l'interface web {#accessing-the-web-interface} - -Nous allons être capable d'ouvrir l'interface web Grafana à http://localhost:3000/. -Les identifiants de session de Grafana par défaut sont: -User: `admin` -Password: `admin` - -
- -
- -### Configurer les Datasource {#configuring-the-datasource} - -Veuillez cliquer sur la roue des paramètres dans le menu et choisissez source de données (datasource). -Dans la fenêtre suivante cliquez "ajouter Datasource" et sélectionnez "Prometheus". - -Dans le formulaire suivant vous n'avez pas besoin de changer quoi que ce soit excepté l'URL. -Entrez `http://localhost:9090/` et cliquez `Save and Test`. - -
- -
- -### Importer le tableau de bord {#importing-the-dashboard} - -Veuillez cliquer sur le bouton `Plus` dans le menu principal de navigation et sélectionnez `import`. - -
- -
- -Nous allons utiliser le [Tableau de bord HydraDX](https://grafana.com/grafana/dashboards/14158) pour le charger vous entrez l'id `14158` et cliquez sur le bouton `Load`. - -
- -
- -Il n'y a pas besoin de beaucoup de configuration ici, assurez vous juste que Prometheus est utilisé comme source de donnée. -Vous pouvez maintenant terminer l'importation. - -
- -
- -Vous devriez maintenant voir votre tableau de bord directement. -Si certains panneaux sont vides, assurez vous que la sélection au dessus des panneaux est comme suit: -* `Chain Metrics`: Substrate -* `Chain Instance`: localhost:9615 -* `Server Job`: node_exporter -* `Server Host`: localhost:9100 diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/participate_in_council_elections.md b/i18n/fr/docusaurus-plugin-content-docs/current/participate_in_council_elections.md deleted file mode 100644 index 34a2a6f41..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/participate_in_council_elections.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -id: participate_in_council_elections -title: Participer aux Elections du Conseil ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Cet article fournit des directions pas à pas sur comment participer aux élections du Conseil - comment voter pour les membres du conseil et devenir un candidat au Conseil. Il y a deux outils que vous pouvez utiliser à ces fins - [Commonwealth.im](#cw) ou [Polkadot/apps](#polkajs). - - -Si vous vous intéressez au fonctionnement des élections, veuillez vous référer à [cet article](/democracy_council#elections). - -:::caution -Le module de démocratie HydraDX sera lancé le, ou après le, **15 septembre 2021**. Veuillez ne pas tenter les actions montrées avant cette date. -::: - -## Utilisation de Commonwealth.im {#cw} - -### Voter aux élections des membres du Conseil {#cw-vote} -Vous pouvez voir les membres du Conseil actuels ainsi que les finalistes dans [L'onglet conseillers](https://commonwealth.im/hydradx/council) sur la page Commonwealth de HydraDX. - -Pour voter pour les membres du Conseil, Cliquez sur *Vote*. - -
- -
- -Entrez le montant de tokens que vous êtes prêt à verrouiller en soutient à vos candidats. - -Après ça, choisissez vos candidats préférés en cliquant sur leurs noms. Rappelez vous de choisir plusieurs candidats - Cela aidera l'algorithme à choisir la distribution optimale de candidats pour le Conseil. - -Pour voter, cliquez sur *Submit vote* et signez la transaction. - -:::note -Les tokens verrouillés ne peuvent pas être transférés, cependant ils peuvent être utilisés pour voter aux référendums. Vos tokens vont rester verrouillés et utilisés pour les élections suivantes jusqu'à ce que vous décidiez de les déverrouiller. -::: - -### Postuler comme candidat au Conseil {#cw-become_candidate} -Vous pouvez soumettre votre candidature d'adhésion au Conseil en naviguant jusqu'à [l'onglet Conseillers](https://commonwealth.im/hydradx/council) sur la page Commonwealth de HydraDX. - -Cliquez sur *Run for council* (se présenter au Conseil) ce qui vous emmènera à un page montrant le dépôt minimum pour l'adhésion. - -Pour soumettre votre candidature, cliquez sur *Sign and send transaction* (Signer et envoyer la transaction) et signer en utilisant votre portefeuille. - -## Utilisation de Polkadot/apps {#polkajs} -### Voter aux élection de membres du Conseil {#polkajs-vote} -Vous pouvez voir les membres du Conseil actuels ainsi que les finalistes sur [*Gouvernance > Conseil* page](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council) dans Polkadot/apps. - -Pour voter pour les membres du Conseil, cliquez sur *Voter*. - -
- -
- -Entrez le montant de tokens que vous êtes prêt à verrouiller en soutient à vos candidats. - -Après ça, choisissez vos candidats dans l'ordre de préférence en les déplaçant de la liste de gauche à la liste de droite. Rappelez vous d'en choisir plusieurs - cela aidera l'algorithme à choisir la distribution optimale de candidats pour le Conseil. - -Pour voter, cliquez sur *Voter* et signer la transaction. - -:::note -Les tokens verrouillés ne peuvent pas être transférés, cependant ils peuvent être utilisés pour voter aux référendums. Vos tokens vont rester verrouillés et utilisés pour les élections suivantes jusqu'à ce que vous décidiez de les déverrouiller. -::: - -### Postuler comme candidat au Conseil {#polkajs-become_candidate} -Vous pouvez soumettre votre candidature d'adhésion au Conseil en naviguant jusqu'à [*Gouvernance > Conseil*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/council) dans Polkadot/apps. - -Cliquez sur *Soumettre la candidature* va faire apparaître une fenêtre contextuelle. - -
- -
- -Sélectionnez le compte que vous voulez voir participer à l'adhésion au Conseil, cliquez sur *Soumettre*, et signez la transaction. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/participate_in_referenda.md b/i18n/fr/docusaurus-plugin-content-docs/current/participate_in_referenda.md deleted file mode 100644 index ea584cb8a..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/participate_in_referenda.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -id: participate_in_referenda -title: Participer aux Référendums ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Ce post fournit un guide détaillé sur comment participer aux référendums - voter et proposer. Il y a deux outils que vous pouvez utiliser à ces fins - [Commonwealth.im](#cw) ou [Polkadot/apps](#polkajs). - -Avant de vous décider à participer, nous vous encourageons fortement à lire [l'article informatif](/democracy_referenda) dans la section Apprendre / Démocratie. Là, vous trouverez des détails importants sur les mécanismes derrière les référendums. - -:::caution -Le module de démocratie HydraDX sera lancé le, ou après le, **15 septembre 2021**. Veuillez ne pas tenter les actions montrées avant cette date. -::: - -## Utiliser Commonwealth.im {#cw} -### Voter dans un Référendum {#cw-vote} -Vous pouvez voir tous les référendums qui sont ouverts au vote en naviguant sur [l'onglet Référendums](https://commonwealth.im/hydradx/referenda) sur la page Commonwealth de HydraDX. - -Pour voter sur un référendum actif, vous devez cliquer dessus. Après quoi, vous verrez une page montrant tous les détails pertinents. - -Dans la section *Cast Your Vote* (*Voter*), remplissez les information suivantes: - -* Le montant du vote - c'est le montant de tokens HDX que vous êtes prêt à verrouiller pour soutenir le référendum. -* Le multiplicateur de conviction (Conviction multiplier) - c'est le multiplicateur qui co-détermine le [poids de votre vote](/democracy_referenda#referenda-votes-weighing). - -Après ça, votez en cliquant sur *Vote yes/oui* ou *Vote no/non* et signez la transaction. - -### Proposer un Référendum {#cw-propose} -Pour proposer un référendum, visitez la [page Commonwealth HydraDX](https://commonwealth.im/hydradx/) et cliquez sur le menu du dessus sur *New Thread > New democracy proposal*. - -
- -
- -Remplissez les information des champs montrés ci-dessus. Les paramètres les plus importants sont: -* Module -* Function -* Toute information supplémentaire comme spécifié par la fonction que proposer à être appelée -* Deposit - le montant de tokens HDX que vous êtes prêt à déposer en soutient à la proposition - -Dans l'exemple ci-dessus, le module de proposition est *balances*, et la fonction est *SetBalance* qui modifie l'équilibre de solde libre et réservé d'un compte donnée. - -Pour soumettre la proposition, cliquez sur *Send transaction* et signer en utilisant votre portefeuille (wallet). - -Après avoir soumis la proposition sur-chaîne et avoir signé la transaction, la proposition devrait apparaître dans la [liste des référendums proposés](https://commonwealth.im/hydradx/referenda). - -:::caution -À chaque période de vote, la proposition de référendum avec le soutient le plus important (*seconding* / *appui*) entre dans le tour de scrutin. À mesure que le nombre de référendums augmente, il n'y a aucune garantie que votre proposition atteigne jamais un appui suffisant pour entrer dans le scrutin. Il n'y a pas d'option pour retirer une proposition de référendum, ce qui veut dire que vos fonds peuvent rester verrouillés pour une période de temps plus longue. - -Les propositions de référendum malveillantes sont sanctionnées. Le Conseil HydraDX et le Comité Technique ont le droit d'annuler tout référendum qui a été proposé de mauvaise foi. Par conséquent, les tokens déposés seront détruits. -::: - -## Utiliser Polkadot/apps {#polkajs} - -### Voter dans un Référendum {#polkajs-vote} -Vous pouvez voir tous les référendums qui sont ouverts au vote en naviguant sur [*Gouvernance > Démocratie*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy) dans Polkadot/apps. - -Pour voter dans un référendum, cliquez sur le bouton *Vote* à son côté. - -Dans la fenêtre contextuelle, remplissez les informations suivantes: - -* Vote value - c'est le montant de tokens HDX que vous êtes prêts à verrouiller en soutient au référendum -* Conviction multiplier - c'est le multiplicateur qui co-détermine le [poids de votre vote](/democracy_referenda#referenda-votes-weighing). - -Après ça, apportez votre vote en cliquant sur *Vote Nay* (Non) or *Vote Aye* (Oui) et signez la transaction. - -### Proposer un Référendum {#polkajs-propose} -Proposer un référendum via Polkadot/apps consiste en deux étapes - soumettre une pré-image, et soumettre une proposition sur-chaîne. - -#### 01 Soumettre une pré-image {#polkajs-propose-01} -Pour soumettre une pré-image, visitez Polkadot/apps et naviguez jusqu'à [*Gouvernance > Démocratie*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy). - -Après avoir cliqué sur *Soumette la pré-image*, vous devriez voir la fenêtre contextuelle suivante: - -
- -
- -Remplissez les informations des champs montrés ci-dessus. Les paramètres les plus importants sont: -* Le compte depuis lequel la proposition est envoyée. -* La zone de proposition -* L'action de la proposition - -Dans l'exemple ci-dessus, la zone de proposition est *balances*, et l'action est *forceTransfer* des tokens d'un compte vers un autre. - -Avant de soumettre la pré-image et de signer la transaction, veuillez vous assurer de copier le "preimage hash" (hachage de la pré-image). vous en aurez besoin pour l'étape suivante. -#### 02 Soumettre la proposition {#polkajs-propose-02} -Pour soumettre la proposition de référendum, visitez [*Gouvernance > Démocratie*](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/democracy) dans Polkadot/apps. - -Après avoir cliqué sur *Soumettre la proposition*, vous devriez voir la fenêtre contextuelle suivante: - -
- -
- -Entrez le hachage (hash) de la pré-image de l'étape précédente, et le montant de tokens que vous êtes prêt à déposer pour la proposition. Le minimum est de 100 000 HDX. - -Après avoir soumis la proposition sur-chaîne, et avoir signé la transaction, votre proposition devrait apparaître dans la liste des référendums proposés. - -:::caution -À chaque période de vote, la proposition de référendum avec le soutient le plus important (*seconding* / *appui*) entre dans le tour de scrutin. À mesure que le nombre de référendums augmente, il n'y a aucune garantie que votre proposition atteigne jamais un appui suffisant pour entrer dans le scrutin. Il n'y a pas d'option pour retirer une proposition de référendum, ce qui veut dire que vos fonds peuvent rester verrouillés pour une période de temps plus longue. - -Les propositions de référendum malveillantes sont sanctionnées. Le Conseil HydraDX et le Comité Technique ont le droit d'annuler tout référendum qui a été proposé de mauvaise foi. Par conséquent, les tokens déposés seront détruits. -::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/performance_benchmark.md b/i18n/fr/docusaurus-plugin-content-docs/current/performance_benchmark.md deleted file mode 100644 index 6d456654f..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/performance_benchmark.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -id: performance_benchmark -title: Benchmark de performance ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Vous pouvez vous assurer que votre machine correspond aux [spécifications techniques requises](/collator_setup#technical-specifications) en exécutant un benchmark de performance. Pour ce faire, suivez les étapes ci-dessous: - -```bash -# Fetch source of the latest stable release -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable -$ cd HydraDX-node/ - -# Prepare for running the benchmark -## Install Rust following https://rustup.rs -$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh - -## Configure Rust -$ ./scripts/init.sh -$ rustup default nightly - -## Install additional libraries -$ apt install python3-pip -$ apt install clang - -# Run the benchmark -$ ./scripts/check_performance.sh -``` - -Après que le benchmark s'exécute, vous devriez voir une sortie similaire à ce qui suit: - -``` - Pallet | Time comparison (µs) | diff* (µs) | diff* (%) | | Rerun -amm | 773.00 vs 680.00 | 93.00 | 12.03 | OK | -exchange | 804.00 vs 720.00 | 84.00 | 10.44 | OK | -transaction_multi_payment| 218.00 vs 198.00 | 20.00 | 9.17 | OK | - -Notes: -- dans les champs "diff" vous pouvez voir la différence entre le temps benchmark de référence et le temps benchmark de votre machine -- Si diff est positif pour les trois données, votre machine répond aux exigences minimums pour faire fonctionner un node HydraDX -- Si diff dévie de -10% ou plus pour certaines données, votre machine pourrait ne pas convenir pour faire fonctionner un node -``` - -Vous pouvez voir la différence de performance entre votre machine et la configuration minimale requise dans la colonne **diff* (%)**. Si les trois valeurs dans cette colonne sont positives, votre machine devrait convenir pour faire fonctionner un node validateur HydraDX. Si une des valeurs est en dessous de *-10 %*, il est déconseillé de faire fonctionner un node HydraDX. - -Rejoignez nous sur Discord si vous voulez discuter des résultats du benchmark, notre communauté vous aidera volontiers. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md b/i18n/fr/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md deleted file mode 100644 index 3b7eaccd3..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -id: polkadotjs_apps_local -title: Se connecter à un node local ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Vous pouvez utiliser Polkadot/apps pour vous connecter à votre node HydraDX local. Pour ce faire, vous devez avoir accès au port `9944` qui est utilisé connexions websockets RPC. - -:::caution - -Si vous faites fonctionner un node en tant que validateur, nous recommandons fortement que vous blacklistiez le port `9944` pour des connexions à distance (hors LAN). Ce port pourrait être exploité par des personnes tierces pour altérer la performance de votre node, ce qui peut résulter par un slashing et une perte involontaire de fonds. Vous devriez utiliser le port `9944` pour vous connecter à votre node validateur seulement quand le node est dans votre réseau local. - -::: - -### Accéder à votre node local en utilisant Polkadot/apps {#accessing-your-local-node-using-polkadotapps} - -Pour accéder à votre node, ouvrez [Polkadot/apps](https://polkadot.js.org/apps/) et cliquez dans le coin supérieur gauche pour changer de réseau. - -
- -
- -Après avoir ouvert le menu, cliquez sur **Development** et choisissez **Local node**. - -ou dans l'interface en français: - -**Développement** et choisissez **Nœud local(propre Nœud)** -
- -
- -Régler l'IP si nécessaire et cliquez sur ***Switch*** pour passer à votre node local. - -
- -
- -Maintenant vous devriez être connecté à votre node local et être capable d'interagir avec. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md b/i18n/fr/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md deleted file mode 100644 index 5a17d53e3..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -id: polkadotjs_apps_public -title: Se connecter à un node publique ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Il y a deux nodes publiques RPC qui sont maintenus par HydraDX et nos partenaires. Vous pouvez utilisez ces nodes pour interagir avec Snakenet. Vous pouvez vous connecter directement à un node publique avec Polkadot/apps en cliquant sur les liens ci-dessous: - -* [Node RPC hébergé par HydraDX](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer) - -## Se connecter manuellement à un node RPC {#connect-manually-to-an-rpc-node} - -Pour accéder à un node RPC publique manuellement, ouvrez [Polkadot/apps](https://polkadot.js.org/apps/) et cliquez dans le coin supérieur gauche pour changer le réseau. - -
- -
- -Cliquez sur **LIVE NETWORKS** (ou **Réseau live** dans l'interface en français) et choisissez **HydraDX**. - - -
- -
- -Choisissez un des nodes et cliquez **Switch** (ou **Appliquer** dans l'interface en français). - -
- -
- -Maintenant vous devriez être connecté au node PRC publique selectionné. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/tip_request.md b/i18n/fr/docusaurus-plugin-content-docs/current/tip_request.md deleted file mode 100644 index 0326ddfe0..000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/tip_request.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -id: tip_request -title: Réclamer une récompense de trésorerie ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Avec le lancement du [Programme récompensé de Nouvel Accord HydraDX](#link-to-new-deal), les membres de la communauté peuvent réclamer des récompenses HDX de la trésorerie en tant que récompense pour leurs contributions. Ce guide va vous guider tout au long du procédé de réclamation de récompense. Vous pouvez trouver plus d'informations sur les différents types d'activités qui sont récompensées dans [ce post](/spending_fw). - -Le processus pour réclamer une récompense de trésorie se compose de deux étapes. Dans un premier temps, les contributeurs doivent publier leur requête de récompense sur Commonwealth.im avec une description de la contribution. dans un second temps, la récompense de trésorerie doit être soumit sur la chaîne (on-chain) en utilisant Polkadot/apps. - -## 01 Publier la requête de pourboire dans Commonwealth.im{#01-publish-tip-request} - -Par soucis de transparence, toutes les réclamations de récompense doivent être publiées dans un fil (thread) sur la [Page HydraDX Commonwealth](https://commonwealth.im/hydradx). Avant d'ouvrir un thread, vous devez lier votre portefeuille HydraDX à Commonwealth.im: -Cliquez sur *Log in* (en haut à droite) et sélectionnez *Connect with wallet > polkadot-js*. - -
- login -
- -Après avoir choisi votre adresse HDX dans le popup, on vous demandera de signer le message en utilisant votre portefeuille et de configurer un nom d'affichage pour ce portefeuille. - -Une fois connecté, vous devez créer un nouveau thread pour votre requête de récompense. Naviguez jusqu'à la partie en haut à droite de la page et cliquez sur *New thread > New thread*. Vous pouvez aussi directement utiliser ce lien: https://commonwealth.im/hydradx/new/thread. - -Vous pouvez utiliser le titre de ce thread pour indiquer le sujet (tip request) et la nature de la contribution. Dans le corps du thread, veuillez fournir les informations suivantes: - -* La période pendant laquelle la contribution a été effectuée -* Un bref résumé de la contribution -* Le montant de la récompense réclamée (en HDX) -* Le temps passé pour la contribution (en heures) -* Si besoin est, un descriptif plus détaillé incluant la pertinence de la contribution à HydraDX -* * Si c'est approprié, fournissez des informations plus détaillées comme la pertinence de la contribution à HydraDX et un lien vers le PR (dans le cas d'une contribution technique). - -Pour référence, vous pouvez regarder [cet exemple de requête de pourboire](https://commonwealth.im/hydradx/proposal/discussion/1165-tip-request-add-documentation-for-staking). - -Après avoir rempli les informations, postez ce thread et il devrait devenir disponible dans la liste générale. - -:::note - -Les nominateurs et les validateurs qui ont alloués tout leurs HDXs et qui se retrouvent "coincés" peuvent réclamer une récompense de trésorerie de 1 HDX qui leur permettra de délier certains de leurs tokens. Si cela s'applique à votre cas, veuillez créer un thread Commonwealth en suivant [cet exemple](https://commonwealth.im/hydradx/proposal/discussion/1166-tip-request-overbonded-staker). - -::: - -## 02 Soumettre la réclamation de pouboire sur la chaîne (On-Chain) {#02-submit-on-chain} - -Après avoir publié votre réclamation de récompense de trésorerie, vous devez la soumettre sur chaîne (on-chain). À cet effet, votre portefeuille doit contenir un petit montant de HDX pour couvrir les frais de transaction. Si vous n'avez pas de HDX actuellement, vous n'avez pas besoin d'effectuer cette étape - quelqu'un d'autre va soumettre votre requête de récompense sur chaîne pour vous. - -Les réclamations de récompense de trésorerie peuvent être soumises sur chaîne avec Polkadot/apps en utilisant le lien suivant: -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/treasury/tips. - -pour soumettre une nouvelle requête de récompense, cliquez sur *Proposez une récompense* - -* **soumettre avec le compte** ou **submit with account** (en anglais) - choisissez le compte qui va signer la transaction pour soumettre la requête de récompense sur chaîne. Ce compte doit contenir un petit montant de HDX pour les coûts de transaction. -* **bénéficiaire** ou **beneficiary** (en anglais) - choisissez ou entrez l'adresse du compte qui recevra la récompense de trésorerie. Ce compte doit correspondre au compte qui a ouvert le thread Commonwealth. -* **raison de la récompense** ou **tip reason** (en anglais) - fournissez l'URL du thread Commonwealth. - -
- login -
- -Pour soumettre la requête de récompense, cliquez sur *Proposez une récompense* ou *Propose tip* (en anglais) et signez la transaction. - -Une fois la transaction confirmée, vous devriez pouvoir voir votre réclamation de récompense sur la page overview. - -
- login -
diff --git a/i18n/fr/docusaurus-theme-classic/footer.json b/i18n/fr/docusaurus-theme-classic/footer.json deleted file mode 100644 index 35f6b1d92..000000000 --- a/i18n/fr/docusaurus-theme-classic/footer.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "link.title.Community": { - "message": "Communauté", - "description": "The title of the footer links column with title=Community in the footer" - }, - "link.item.label.Discord": { - "message": "Discord", - "description": "The label of footer link with label=Discord linking to https://discord.gg/HDNPFFrcnW" - }, - "link.item.label.Twitter": { - "message": "Twitter", - "description": "The label of footer link with label=Twitter linking to https://twitter.com/hydra_dx" - }, - "copyright": { - "message": "Tous droits réservés © 2021 Intergalactic, Inc. Construit avec Docusaurus.", - "description": "The footer copyright" - } -} \ No newline at end of file diff --git a/i18n/fr/docusaurus-theme-classic/navbar.json b/i18n/fr/docusaurus-theme-classic/navbar.json deleted file mode 100644 index ef4edc6f8..000000000 --- a/i18n/fr/docusaurus-theme-classic/navbar.json +++ /dev/null @@ -1,14 +0,0 @@ -{ - "title": { - "message": "Documentation HydraDX", - "description": "The title in the navbar" - }, - "item.label.Docs": { - "message": "Documents", - "description": "Navbar item with label Docs" - }, - "item.label.HydraDX Homepage": { - "message": "Page d'accueil de HydraDX", - "description": "Navbar item with label HydraDX Homepage" - } -} \ No newline at end of file diff --git a/i18n/ru/code.json b/i18n/ru/code.json deleted file mode 100644 index f7f7b1a6e..000000000 --- a/i18n/ru/code.json +++ /dev/null @@ -1,158 +0,0 @@ -{ - "theme.NotFound.title": { - "message": "Страница не найдена", - "description": "The title of the 404 page" - }, - "theme.NotFound.p1": { - "message": "К сожалению, мы не смогли найти запрашиваемую вами страницу.", - "description": "The first paragraph of the 404 page" - }, - "theme.NotFound.p2": { - "message": "Пожалуйста, обратитесь к владельцу сайта, с которого вы перешли на эту ссылку, чтобы сообщить ему ссылка не работает.", - "description": "The 2nd paragraph of the 404 page" - }, - "theme.blog.post.readingTime.plurals": { - "message": "{readingTime} мин. чтения", - "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.tags.tagsListLabel": { - "message": "Теги:", - "description": "The label alongside a tag list" - }, - "theme.blog.post.readMore": { - "message": "Читать дальше", - "description": "The label used in blog post item excerpts to link to full blog posts" - }, - "theme.AnnouncementBar.closeButtonAriaLabel": { - "message": "Закрыть", - "description": "The ARIA label for close button of announcement bar" - }, - "theme.blog.paginator.navAriaLabel": { - "message": "Навигация по странице списка блогов", - "description": "The ARIA label for the blog pagination" - }, - "theme.blog.paginator.newerEntries": { - "message": "Следующие записи", - "description": "The label used to navigate to the newer blog posts page (previous page)" - }, - "theme.blog.paginator.olderEntries": { - "message": "Предыдущие записи", - "description": "The label used to navigate to the older blog posts page (next page)" - }, - "theme.blog.post.paginator.navAriaLabel": { - "message": "Навигация по странице поста блога", - "description": "The ARIA label for the blog posts pagination" - }, - "theme.blog.post.paginator.newerPost": { - "message": "Следующий пост", - "description": "The blog post button label to navigate to the newer/previous post" - }, - "theme.blog.post.paginator.olderPost": { - "message": "Предыдущий пост", - "description": "The blog post button label to navigate to the older/next post" - }, - "theme.tags.tagsPageTitle": { - "message": "Теги", - "description": "The title of the tag list page" - }, - "theme.blog.post.plurals": { - "message": "{count} запись|{count} записи|{count} записей", - "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)" - }, - "theme.blog.tagTitle": { - "message": "{nPosts} с тегом \"{tagName}\"", - "description": "The title of the page for a blog tag" - }, - "theme.tags.tagsPageLink": { - "message": "Посмотреть все теги", - "description": "The label of the link targeting the tag list page" - }, - "theme.CodeBlock.copyButtonAriaLabel": { - "message": "Скопировать в буфер обмена", - "description": "The ARIA label for copy code blocks button" - }, - "theme.CodeBlock.copied": { - "message": "Скопировано", - "description": "The copied button label on code blocks" - }, - "theme.CodeBlock.copy": { - "message": "Скопировать", - "description": "The copy button label on code blocks" - }, - "theme.docs.sidebar.expandButtonTitle": { - "message": "Развернуть сайдбар", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.expandButtonAriaLabel": { - "message": "Развернуть сайдбар", - "description": "The ARIA label and title attribute for expand button of doc sidebar" - }, - "theme.docs.sidebar.responsiveCloseButtonLabel": { - "message": "Закрыть меню", - "description": "The ARIA label for close button of mobile doc sidebar" - }, - "theme.docs.sidebar.responsiveOpenButtonLabel": { - "message": "Открыть меню", - "description": "The ARIA label for open button of mobile doc sidebar" - }, - "theme.docs.sidebar.collapseButtonTitle": { - "message": "Свернуть сайдбар", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.sidebar.collapseButtonAriaLabel": { - "message": "Свернуть сайдбар", - "description": "The title attribute for collapse button of doc sidebar" - }, - "theme.docs.paginator.navAriaLabel": { - "message": "Навигация по странице документации", - "description": "The ARIA label for the docs pagination" - }, - "theme.docs.paginator.previous": { - "message": "Предыдущая страница", - "description": "The label used to navigate to the previous doc" - }, - "theme.docs.paginator.next": { - "message": "Следующая страница", - "description": "The label used to navigate to the next doc" - }, - "theme.docs.versions.unreleasedVersionLabel": { - "message": "Это документация для будущей версии {siteTitle} {versionLabel}.", - "description": "The label used to tell the user that he's browsing an unreleased doc version" - }, - "theme.docs.versions.unmaintainedVersionLabel": { - "message": "Это документация {siteTitle} для версии {versionLabel}, которая уже не поддерживается.", - "description": "The label used to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionSuggestionLabel": { - "message": "Актуальная документация находится на странице {latestVersionLink} ({versionLabel}).", - "description": "The label userd to tell the user that he's browsing an unmaintained doc version" - }, - "theme.docs.versions.latestVersionLinkLabel": { - "message": "последней версии", - "description": "The label used for the latest version suggestion link label" - }, - "theme.common.headingLinkTitle": { - "message": "Прямая ссылка на этот заголовок", - "description": "Title for link to heading" - }, - "theme.common.editThisPage": { - "message": "Отредактировать эту страницу", - "description": "The link label to edit the current page" - }, - "theme.lastUpdated.atDate": { - "message": " {date}", - "description": "The words used to describe on which date a page has been last updated" - }, - "theme.lastUpdated.byUser": { - "message": " от {user}", - "description": "The words used to describe by who the page has been last updated" - }, - "theme.lastUpdated.lastUpdatedAtBy": { - "message": "Последнее обновление{atDate}{byUser}", - "description": "The sentence used to display when a page has been last updated, and by who" - }, - "theme.common.skipToMainContent": { - "message": "Перейти к основному содержимому", - "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation" - } -} \ No newline at end of file diff --git a/i18n/ru/docusaurus-plugin-content-docs/current.json b/i18n/ru/docusaurus-plugin-content-docs/current.json deleted file mode 100644 index f5fb845f9..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current.json +++ /dev/null @@ -1,46 +0,0 @@ -{ - "version.label": { - "message": "Далее", - "description": "The label for version current" - }, - "sidebar.sidebar.category.Intro": { - "message": "Введение", - "description": "The label for category Intro in sidebar sidebar" - }, - "sidebar.sidebar.category.Knowledge Base": { - "message": "База знаний", - "description": "The label for category Knowledge Base in sidebar sidebar" - }, - "sidebar.sidebar.category.Become a validator": { - "message": "Стать валидатором", - "description": "The label for category Become a validator in sidebar sidebar" - }, - "sidebar.sidebar.category.Connect to a Node": { - "message": "Подключение к ноде", - "description": "The label for category Connect to a Node in sidebar sidebar" - }, - "sidebar.sidebar.category.Other": { - "message": "Другое", - "description": "The label for category Other in sidebar sidebar" - }, - "sidebar.sidebar.category.Contribute": { - "message": "Сделать вклад", - "description": "The label for category Contribute in sidebar sidebar" - }, - "sidebar.sidebar.category.How-to": { - "message": "Как это сделать", - "description": "The label for category How-to in sidebar sidebar" - }, - "sidebar.sidebar.category.Learn": { - "message": "База знаний", - "description": "The label for category Learn in sidebar sidebar" - }, - "sidebar.sidebar.category.Maintain": { - "message": "Обслуживание", - "description": "The label for category Maintain in sidebar sidebar" - }, - "sidebar.sidebar.category.Build": { - "message": "Сборка", - "description": "The label for category Build in sidebar sidebar" - } -} \ No newline at end of file diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/build_dev_chain.md b/i18n/ru/docusaurus-plugin-content-docs/current/build_dev_chain.md deleted file mode 100644 index 2a63cf11d..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/build_dev_chain.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -id: build_dev_chain -title: Создание цепочки разработки ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -В этом разделе вы познакомитесь с процессом настройки локального экземпляра цепочки HydraDX для разработки. - -## 01 Установить зависимостей - -Чтобы подготовить локальный экземпляр цепочки HydraDX для разработки, ваш сервер должен покрыть все зависимости для запуска цепочки субстратов. Вам нужно будет установить среду разработчика Rust и убедиться, что она правильно настроена для компиляции кода среды выполнения Substrate для цели WebAssembly (Wasm). - -Вы можете установить и настроить все зависимости вручную, следуя [Руководству по субстратам](https://substrate.dev/docs/en/knowledgebase/getting-started), или вы можете позволить этому скрипту сделать всю работу за вас: - -```bash -$ curl https://getsubstrate.io -sSf | bash -s -- --fast -$ source ~/.cargo/env -``` - -## 02 Сборка - -Соберите Wasm и родную среду выполнения: - -```bash -# Получить исходный код последней стабильной версии -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable - -# Сборка бинарных файлов -$ cd HydraDX-node/ -$ cargo build --release -``` - -Вы должны найти результат сборки в `./target/release/hydra-dx`. - -## 03 Запуск - -Перед запуском сборки вы можете очистить все существующие цепочки разработки на вашем компьютере (вам нужно будет часто делать это в процессе разработки): - -```bash -$ ./target/release/hydra-dx purge-chain --dev -``` - -Запустите вашу сборку, используя одну из следующих команд: - -```bash -$ ./target/release/hydra-dx --dev - -# Запуск с подробным ведением журнала -$ RUST_LOG=debug RUST_BACKTRACE=1 ./target/release/hydra-dx -lruntime=debug --dev -``` - -## 04 Подключитесь к экземпляру локальной сети - -Вы можете подключиться к своей ноде разработки HydraDX, используя Polkadot/apps и изменив сеть на `Development`. Вы также можете использовать эту ссылку: -https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/explorer - -connect to node diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/claim.md b/i18n/ru/docusaurus-plugin-content-docs/current/claim.md deleted file mode 100644 index 490eba5da..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/claim.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -id: claim -title: Получение ваших HDX ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Вы можете запросить свои токены HDX с помощью токенов xHDX (ERC-20), которые вы получили во время аукциона на [Balancer LBP](https://hydradx.substack.com/p/lbp-announcement) - -## Предварительные требования {#prequisites} - -Есть два предварительных условия для подачи заявки на HDX. Во-первых, вам необходимо установить [ расширение для браузера](https://polkadot.js.org/extension/), которое будет использоваться для создания вашего кошелька HDX. Во-вторых, вам нужен доступ к вашим токенам xHDX, которые должны храниться в кошельке, поддерживающем подпись сообщений, относящихся к токенам ERC-20 (например, Metamask). - -Если ваши токены xHDX хранятся в кошельке Coinbase или Trust Wallet, вам нужно будет использовать один из следующих обходных путей для получения своих токенов HDX, поскольку эти кошельки не поддерживают подписание сообщений: -* Metamask: вы можете использовать расширение для браузера Metamask и импортировать свой кошелек, используя seed-фразу восстановления. -* MEW (MyEtherWallet): вы также можете использовать MEW, импортировав seed-фразу восстановления (*Мнемоническую Фразу*) или используя параметр подключения WalletLink. Оба варианта доступны на [странице доступа к кошельку MEW](https://www.myetherwallet.com/access-my-wallet). Если вы используете кошелек Coinbase, вы можете использовать WalletLink, который вы можете найти в настройках кошелька Coinbase. - -## Процесс запроса токенов {#claim-process} - -Убедившись, что вы выполнили предварительные условия, описанные выше, вы можете перейти в [приложение HydraDX Claim](https://claim.hydradx.io) и продолжить процесс запроса. - -Во время процесса заявки вы будете использовать свои токены xHDX (ERC-20), чтобы потребовать свою долю токенов HDX. - -### 00 Авторизация {#00-authorize} - -Приложение HydraDX Claim запросит авторизацию у расширения браузера Polkadot.js. - -:::warning - -Убедитесь, что вы не являетесь жертвой фишинг-атаки, и обратите внимание на всплывающее окно авторизации: приложение должно идентифицировать себя как **CLAIM.HYDRADX.IO**, а запрос должен исходить с **https://claim.hydradx.io** - -::: - -authorize - -После авторизации вам будет предложено обновить метаданные для расширения polkadot.js. Это означает, что polkadot.js сможет создавать специальные адреса HydraDX, которые необходимы для завершения процесса запроса токенов в пользовательском интерфейсе. - -authorize - -### 01 Выбор вашего адреса ETH {#01-select-your-eth-address} - -На первом этапе процесса запроса вам будет предложено выбрать учетную запись, в которой хранятся ваши токены xHDX. Это можно сделать, подключившись к вашему кошельку с токенами ERC-20 (например, Metamask), или введя свой адрес ETH вручную в поле ввода (в этом случае вам нужно будет подписать сообщение вручную позже). - -После ввода адреса ETH вы должны увидеть остаток токенов HDX, которые вы можете запросить, включая [возмещение платы за газ](https://hydradx.substack.com/p/first-governance-vote), потраченной на получение xHDX на балансировщике. - -:::note - -Вы не имеете права на возврат газа, если вы получили свой xHDX в другом месте, кроме официального пула балансировщика (например, Uniswap), или если вы переместили свои токены из исходного кошелька для покупки. - -::: - -authorize - -### 02 Создание и выбор адреса HDX {#02-create-and-select-an-hdx-address} - -На втором этапе вам будет предложено выбрать ваш адрес HDX. - -Чтобы создать новый адрес HDX, откройте расширение браузера Polkadot.js и щелкните значок +, чтобы создать новую учетную запись. На первом этапе создания учетной записи вы увидите мнемоническую фразу из 12 слов, которую можно использовать для восстановления вашей учетной записи. После сохранения исходной фразы в надежном месте нажмите «Следующий шаг». Здесь вы должны изменить **Network**, выбрав опцию **HydraDX Snakenet**. Введите имя и пароль для своей учетной записи и завершите создание учетной записи. - -authorize - -:::warning - -Никогда никому не передавайте свою seed-фразу. Сделайте резервную копию и храните в надежном месте. Это единственный способ восстановить свою учетную запись, и в случае ее потери или утечки ваши средства будут скомпрометированы. Обратите внимание, что вам нужно хранить этот кошелек до запуска основной сети, поскольку балансы будут заблокированы, и если вы потеряете доступ к кошельку, вы также потеряете свой HDX. Пожалуйста, сохраните это в безопасности. - -::: - -После создания учетной записи HDX вы сможете выбрать ее в приложении HydraDX Claim. После этого приложение должно предоставить вам обзор адресов ETH и HDX, используемых для процесса заявки. Нажмите «Далее», чтобы подписать сообщение. - -authorize - -### 03 Подписание {#03-sign} - -На третьем этапе процесса запроса с использованием приложения HydraDX Claim вам будет предоставлена возможность подписать сообщение об использовании ваших токенов xHDX для запроса HDX. - -:::note - -Обратите внимание, что на этом этапе вы увидите **публичный ключ** вашего адреса HDX, а не адрес в его удобочитаемой форме, как он был отображен на предыдущем шаге и в расширении браузера Polkadot.js (подробнее см. [ss58 docs](https://polkadot.js.org/docs/keyring/start/ss58)). Если вы выполнили все шаги, описанные выше, беспокоиться не о чем, и можно безопасно приступить к подписанию сообщения. Мы также проверим, что учетная запись HDX, которую вы используете для подписания транзакции запроса токенов на последнем этапе, соответствует учетной записи, которая получает запрашиваемые HDX. - -::: - -В зависимости от варианта, который вы выбрали на первом шаге, здесь вам будет представлен один из двух вариантов. - -* Если вы используете **Metamask**, после нажатия кнопки *Sign* Metamask предложит вам подписать сообщение. Следуйте инструкциям в Metamask. - -* Если вы ввели свой адрес ETH вручную, вам нужно будет подписать сообщение через внешний кошелек, в котором хранятся закрытые ключи ваших токенов xHDX. После того, как вы подписали сообщение, скопируйте подпись (начиная с *0x*) в соответствующее поле в приложении HydraDX Claim. - -authorize - -### 04 Запрос токенов {#04-claim} - -После подписания сообщения кошельком с вашими токенами xHDX должно открыться расширение Polkadot.js, и вам будет предложено подписать транзакцию для запроса токенов HDX на вашу учетную запись. Введите пароль своей учетной записи HDX и нажмите *Sign the transaction*. - -authorize - -Вы завершили процесс подачи заявки и официально стали владельцем HDX! - -Вы можете проверить свой баланс с помощью Polkadot/apps, подключившись к сети HydraDX: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.hydradx.cloud#/accounts diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/identity.md b/i18n/ru/docusaurus-plugin-content-docs/current/identity.md deleted file mode 100644 index ae3353ac8..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/identity.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -id: identity -title: Установите свою личность ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Владельцы счетов имеют возможность установить свою личность, предоставив определенную информацию и сохранив ее в сети. Кроме того, идентификационная информация может быть отправлена регистраторам HydraDX для проверки. Устанавливая и проверяя свою личность, валидаторы и номинаторы помогают повысить доверие к сети. - -:::note -Если вы участвуете в качестве валидатора HydraDX, мы **настоятельно рекомендуем** вам указать свою личность и пройти процесс проверки. Проверенные валидаторы выглядят более надежными и привлекают больше номинаций, тем самым увеличивая шансы быть включенными в набор активных валидаторов. -::: - -## 01 Установка идентичности {#01-set-identity} - -Чтобы установить свою личность, откройте Polkadot/apps (подключенный к сети *HydraDX Snakenet*) и перейдите в *Мои учетные записи*. Как вариант, вы можете перейти по этой ссылке: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/accounts - -На странице учетных записей найдите учетную запись, в которой хранятся ваши привязанные токены HDX. После этого нажмите на три точки рядом с учетной записью (справа) и выберите *Установить идентификацию в сети*. - -authorize - -Вы увидите всплывающее окно с названием *зарегистрировать личность*. Здесь вы можете ввести следующую информацию: - -* legal name -* email -* web address -* twitter -* riot name (если вы используете систему обмена сообщениями Matrix) - -:::note -Вся эта информация является необязательной - не стесняйтесь предоставлять только те детали, которые вы выбираете. Однако, если вы используете узел валидатора, мы рекомендуем вам указать свой адрес электронной почты. Это позволит нам связаться с вами в случае возникновения проблем с вашим узлом. -::: - -В последнем поле всплывающего окна вы можете увидеть сумму HDX, которую вам нужно внести для хранения вашей идентификационной информации. Вы получите этот депозит обратно, как только решите очистить информацию о своей личности. - -authorize - -После заполнения информации нажмите *Set Identity* и подпишите транзакцию с помощью расширения браузера Polkadot.js. После подтверждения транзакции данные ваша личности установлены. - -## 02 Отправьте вашу личность для проверки {#02-verify-identity} - -После того, как вы установили свою личность, вы можете отправить ее регистраторам сети для проверки. Для этого откройте Polkadot/apps и перейдите в *Developer*>*Extrinsics*. Как вариант, вы можете перейти по этой ссылке: - -https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/extrinsics - -После выбора соответствующей учетной записи HydraDX на последнем шаге вам необходимо заполнить следующую информацию: - -* **extrinsic**: identity -* **action**: requestJudgement -* **reg_index**: здесь вам нужно ввести идентификатор регистратора, которого вы выбираете для проведения проверки. -HydraDX has 2 registrars: Simon Kraus - HydraSik (ID: **0**) and Jimmy Tudeski - stakenode (ID: **1**). -* **max_fee**: здесь вам нужно ввести максимальную плату в HDX, которую вы готовы заплатить регистратору за проверку. Только регистраторы с комиссией ниже вашего max_fee будут иметь право проводить проверку. - -Чтобы отправить запрос на подтверждение, нажмите *Отправить транзакцию* (или *Submit Transaction*) и подпишите транзакцию. - -authorize - -Обратите внимание, что процесс подтверждения личности может занять некоторое время. Чтобы увидеть статус вашего запроса, перейдите в **Мои учетные записи** (или **My accounts**) и наведите указатель мыши на раздел, отображающий вашу личность - вы увидите всплывающее окно с текущим статусом. - -## 03 Результаты проверки {#03-verification-outcome} - -После обработки вашего запроса на подтверждение регистратор представит одно из следующих решений, которые станут видны в вашем статусе личности: - -* **Unknown** - значение по умолчанию, суждение еще не вынесено. -* **Reasonable** - предоставленная информация кажется разумной, однако никаких углубленных проверок не проводилось. -* **KnownGood** - информация верна. -* **OutOfDate** - информация была верной в прошлом, но теперь она устарела. -* **LowQuality** - информация неточная, но ее можно исправить, обновив. -* **Erroneous** - предоставленная информация неверна и может указывать на злой умысел. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/intro.md b/i18n/ru/docusaurus-plugin-content-docs/current/intro.md deleted file mode 100644 index 21a9465d0..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/intro.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -id: intro -title: Приступая к работе -slug: / ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Добро пожаловать в официальную документацию HydraDX! Здесь вы можете найти всевозможные полезные ресурсы по протоколу HydraDX. Наше намерение состоит в том, чтобы сделать это прекрасным местом для всех, охватывая весь спектр случайных посетителей, валидаторов, номинантов и разработчиков, которые хотят помочь в создании HydraDX. - -HydraDX управляется сообществом, как и эти Документы. Мы рады видеть ваш вклад, который может принимать различные формы - например, вы можете написать новую статью или перевести существующую. Ознакомьтесь с нашим [репозиторием GitHub](https://github.com/galacticcouncil/HydraDX-docs), а также с некоторыми [правилами участия](/contributing). - -## Что такое HydraDX? {#what-is-hydradx} - -HydraDX-это кросс-цепной протокол ликвидности, построенный на субстрате. Наша миссия состоит в том, чтобы обеспечить бесперебойную ликвидность для всех криптоассетов путем создания первого в своем роде пула ликвидности с несколькими активами-HydraDX Omnipool. В Omnipool различные активы оцениваются друг с другом с помощью нашего собственного токена HDX в качестве прокси-сервера для определения их относительной стоимости. Создав Omnipool, HydraDX нарушает традиционную концепцию, согласно которой активы торгуются парами с использованием изолированных пулов. Кроме того, мы рады быть частью экосистемы Polkadot и с нетерпением ждем возможности стать поставщиком ликвидности для всех активов, построенных на Substrate. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/node_monitoring.md b/i18n/ru/docusaurus-plugin-content-docs/current/node_monitoring.md deleted file mode 100644 index 2e907aa2b..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/node_monitoring.md +++ /dev/null @@ -1,345 +0,0 @@ ---- -id: node_monitoring -title: Мониторинг Ноды ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -В этой главе мы проведем вас через настройку локального мониторинга для вашей Ноды валидатора. - -## Предпосылки {#prerequisites} - -У вас должна быть запущена [Нода колатора](/collator_setup). -Это руководство было протестировано на версии Ubuntu 20.04 LTS. - -## Установка Prometheus {#prometheus-setup} - -На первом этапе мы настроим сервер Prometheus. - -### Пользователь и Каталоги {#user-and-directories} - -Мы создаем пользователя только для целей мониторинга, у которого нет домашнего каталога и который не может использоваться для входа в систему. - -```shell script -$ sudo useradd --no-create-home --shell /usr/sbin/nologin prometheus -``` - -Затем мы создаем каталоги для исполняемого файла и файла конфигурации. - -```shell script -$ sudo mkdir /etc/prometheus -$ sudo mkdir /var/lib/prometheus -``` - -Измените владельца каталогов, чтобы разрешить доступ к ним нашему новому пользователю мониторинга. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus -$ sudo chown -R prometheus:prometheus /var/lib/prometheus -``` - -### Установим Prometheus {#install-prometheus} - -Проверьте номер последней версии Prometheus на [странице проекта в GitHub](https://github.com/prometheus/prometheus/releases/). -На момент написания данной стать актуальная версия v2.25.2. Вставьте ссылку с последней версией в следующие команды. -```shell script -# скачайте prometheus -$ wget https://github.com/prometheus/prometheus/releases/download/v2.25.2/prometheus-2.25.2.linux-amd64.tar.gz - -# распакуйте архив с бинарными файлами -$ tar xfz prometheus-*.tar.gz - -# войдите в распакованную директорию -$ cd prometheus-2.25.2.linux-amd64 -``` - -Теперь скопируйте двоичные файлы в локальную папку. - -```shell script -$ sudo cp ./prometheus /usr/local/bin/ -$ sudo cp ./promtool /usr/local/bin/ -``` - -Теперь нам нужно назначить эти двоичные файлы нашему только что созданному пользователю. - -```shell script -$ sudo chown prometheus:prometheus /usr/local/bin/prometheus -$ sudo chown prometheus:prometheus /usr/local/bin/promtool -``` - -Далее мы скопируем веб-интерфейс и предустановки конфигурации. - -```shell script -$ sudo cp -r ./consoles /etc/prometheus -$ sudo cp -r ./console_libraries /etc/prometheus -``` - -Возможно, вы уже догадались, но мы также меняем владельца этих каталогов. - -```shell script -$ sudo chown -R prometheus:prometheus /etc/prometheus/consoles -$ sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries -``` - -Теперь у нас есть все, что нам нужно из загруженного архива, поэтому мы вернемся на шаг назад и проведем некоторую чистку. - -```shell script -$ cd .. && rm -rf prometheus* -``` - -Давайте создадим файл конфигурации YAML для Prometheus с помощью редактора по вашему выбору (nano / vim / pico). - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -Наш конфигурационный файл разделен на три раздела: - -* `global`: устанавливает значения по умолчанию для `scrape_interval` и интервала выполнения правила с `evaluation_interval` -* `rule_files`: указывает файлы правил, которые должен загружать сервер Prometheus -* `scrape_configs`: здесь вы устанавливаете ресурсы для мониторинга - -Он будет у нас очень простым и в итоге получим что-то вроде этого: - -```yaml -global: - scrape_interval: 15s - evaluation_interval: 15s - -rule_files: - # - "weHaveNo.rules" - -scrape_configs: - - job_name: "prometheus" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9090"] - - job_name: "substrate_node" - scrape_interval: 5s - static_configs: - - targets: ["localhost:9615"] -``` - -Первое задание по очистке экспортирует данные самого Prometheus, второе - метрики узла HydraDX. Мы скорректировали `scrape_interval` обоих заданий, чтобы получить более подробную статистику. Это переопределит глобальные значения. Параметр `targets` в `static_configs` устанавливает, на каком порту запускаются экспортеры, здесь мы придерживаемся значений по умолчанию. - -После сохранения конфигурации мы снова сменим владельца. - -```shell script -$ sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml -``` - -### Запуск Prometheus {#starting-prometheus} - -Чтобы Prometheus запускался автоматически и работал в фоновом режиме, мы будем использовать `systemd`. Создайте новую конфигурацию (опять же с выбранным вами редактором): - -````shell script -$ sudo nano /etc/systemd/system/prometheus.service -```` - -Вставьте следующую конфигурацию и сохраните файл. - -``` -[Unit] - Description=Prometheus Monitoring - Wants=network-online.target - After=network-online.target - -[Service] - User=prometheus - Group=prometheus - Type=simple - ExecStart=/usr/local/bin/prometheus \ - --config.file /etc/prometheus/prometheus.yml \ - --storage.tsdb.path /var/lib/prometheus/ \ - --web.console.templates=/etc/prometheus/consoles \ - --web.console.libraries=/etc/prometheus/console_libraries - ExecReload=/bin/kill -HUP $MAINPID - -[Install] - WantedBy=multi-user.target -``` - -Далее мы выполним следующие три шага: -`systemctl deamon-reload` загружает новые конфигурации и обновляет существующие -`systemctl enable` активирует нашу новую службу -`systemctl start` запускает выполнение службы. - -Вы можете выполнить описанные выше шаги одной командой, выполнив: - -```shell script -$ sudo systemctl daemon-reload && systemctl enable prometheus && systemctl start prometheus -``` - -Теперь у вас должен быть доступ к веб-интерфейсу Prometheus по адресу http://localhost:9090/. - -## Node Exporter {#node-exporter} - -Мы установим Node Exporter для очистки метрик сервера, которые будут использоваться в панели инструментов. -Пожалуйста, проверьте номер версии последнего выпуска [здесь](https://github.com/prometheus/node_exporter/releases/) и обновите команду. -На момент написания последней версии была `1.1.2`. - -### Установка Node Exporter {#install-node-exporter} - -Загрузите последнюю версию. - -```shell script -$ wget https://github.com/prometheus/node_exporter/releases/download/v1.1.2/node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Распакуйте только что скачанный архив. Это создаст папку с именем `node_exporter-1.1.2.linux-amd64`. - -```shell script -$ tar xvf node_exporter-1.1.2.linux-amd64.tar.gz -``` - -Затем мы копируем двоичный файл в наш локальный каталог приложения и назначаем его нашему пользователю мониторинга. - -```shell script -# copy binary -$ cp node_exporter-1.1.2.linux-amd64/node_exporter /usr/local/bin - -# set ownership -$ sudo chown prometheus:prometheus /usr/local/bin/node_exporter -``` - -Теперь мы можем выполнить некоторую очистку и удалить загруженный и распакованный пакет. - -```shell script -$ rm -rf node_exporter* -``` - -### Создание службы Systemd {#create-a-systemd-service} - -Как и в случае с prometheus, мы хотим, чтобы Node Exporter работал в качестве службы. -Создайте службу systemd с помощью выбранного вами редактора. - -```shell script -$ sudo nano /etc/systemd/system/node_exporter.service -``` - -И вставьте в него следующую конфигурацию. - -``` -[Unit] -Description=Node Exporter -Wants=network-online.target -After=network-online.target - -[Service] -User=prometheus -Group=prometheus -Type=simple -ExecStart=/usr/local/bin/node_exporter - -[Install] -WantedBy=multi-user.target -``` - -Теперь мы активируем и запустим службу командой в одну строку. - -```shell script -$ sudo systemctl daemon-reload && systemctl enable node_exporter && systemctl start node_exporter -``` - -### Добавление задания очистки для Node Exporter {#add-scrape-job-for-node-exporter} - -Теперь Node Exporter запущен и работает, но нам нужно сказать Prometheus, чтобы он очистил свои данные. -Мы снова откроем файл конфигурации с помощью выбранного редактора. - -```shell script -$ sudo nano /etc/prometheus/prometheus.yml -``` - -А в самом низу файла мы добавим еще один конфиг для очистки. -Вставьте следующее содержимое и сохраните файл. - -```yaml - - job_name: 'node_exporter' - scrape_interval: 5s - static_configs: - - targets: ['localhost:9100'] -``` - -Для применения конфигурации изменений требуется перезапуск службы Prometheus. - -```shell script -$ sudo systemctl restart prometheus.service -``` - -Метрики вашего сервера теперь очищены и могут быть найдены в веб-интерфейсе Prometheus. -Они нам понадобятся позже для нашей панели. - -## Установка Grafana {#grafana-setup} - -Мы можем видеть наши метрики в веб-интерфейсе, но не так, как мы хотим их отслеживать. -Мы хотим, чтобы это было красиво и лаконично. Вот где в игру вступает Grafana. - -### Установим Grafana {#install-grafana} - -Пожалуйста, проверьте последнюю версию Grafana [по этой ссылке](https://grafana.com/grafana/download?platform=linux). -Вы можете изменить номер версии в следующих командах или скопировать команды установки прямо из ссылки. -На момент написания последней версии была `7.5.1`. - -```shell script -$ sudo apt-get install -y adduser libfontconfig1 -$ wget https://dl.grafana.com/oss/release/grafana_7.5.1_amd64.deb -$ sudo dpkg -i grafana_7.5.1_amd64.deb -``` - -Пакет поставляется со встроенной службой systemd, которую мы настроим и запустим так же, как службу Prometheus. - -```shell script -$ sudo systemctl daemon-reload && sudo systemctl enable grafana-server && sudo systemctl start grafana-server -``` - -### Доступ к веб-интерфейсу Grafana {#accessing-the-web-interface} - -Мы сможем открыть веб-интерфейс Grafana по адресу http://localhost:3000/. -Логин Grafana по умолчанию: -Пользователь: `admin` -Пароль: `admin` - -
- -
- -### Configuring the Datasource {#configuring-the-datasource} - - -Пожалуйста, нажмите на значок настроек в меню и выберите источники данных. -В следующем окне вы нажимаете "Add Datasource" и выбираете "Prometheus". - -В следующей форме вам не нужно ничего менять, кроме URL-адреса. -Установите `http://localhost:9090/` и нажмите `Save and Test`. - -
- -
- -### Настройка источника данных {#importing-the-dashboard} - -Нажмите кнопку `Plus` на главной панели навигации и выберите `import`. - -
- -
- -Мы будем использовать [панель управления HydraDX](https://grafana.com/grafana/dashboards/14158), и для ее загрузки вы просто вводите идентификатор `14158` и нажимаете кнопку `Load`. - -
- -
- -Здесь вам не нужно много настраивать, просто убедитесь, что Prometheus используется в качестве источника данных. -Теперь вы можете завершить импорт. - -
- -
- -Теперь вы должны сразу увидеть свою панель управления. -Если некоторые панели пусты, убедитесь, что ваш выбор над панелями выглядит следующим образом: -* `Chain Metrics`: Substrate -* `Chain Instance`: localhost:9615 -* `Server Job`: node_exporter -* `Server Host`: localhost:9100 diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/performance_benchmark.md b/i18n/ru/docusaurus-plugin-content-docs/current/performance_benchmark.md deleted file mode 100644 index 6e42c6e45..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/performance_benchmark.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -id: performance_benchmark -title: Тест производительности ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Вы можете убедиться, что ваш сервер соответствует [требуемым техническим характеристикам](/collator_setup#technical-specifications), выполнив тест производительности. Для этого выполните следующие действия: - -```bash -# Получить исходный код последней стабильной версии -$ git clone https://github.com/galacticcouncil/HydraDX-node -b stable -$ cd HydraDX-node/ - -# Подготовьтесь к запуску теста -$ ./scripts/init.sh -$ rustup default nightly -$ apt install python3-pip -$ pip3 install bench-wizard - -# Запустите тест -$ ./scripts/check_performance.sh -``` - -После выполнения теста вы должны увидеть результат, подобный следующему: - -``` - Pallet | Time comparison (µs) | diff* | | Rerun -amm | 1066.00 vs 1045.80 | 20 | OK | -exchange | 1105.00 vs 1049.10 | 55 | OK | -transaction_multi_payment| 289.00 vs 279.96 | 9 | OK | -``` - -Вы можете увидеть разницу в производительности вашего компьютера и минимально необходимой настройки в столбце **diff* (%)**. Если все три значения в этом столбце положительны, ваша машина должна быть подходящей для запуска узла валидатора HydraDX. Если какое-либо из значений ниже *-10 %*, мы не рекомендуем запускать узел HydraDX. - -Присоединяйтесь к нам в Discord, если вы хотите обсудить результаты своих тестов, наше сообщество всегда рады помочь. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md b/i18n/ru/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md deleted file mode 100644 index 896376d17..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/polkadotjs_apps_local.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -id: polkadotjs_apps_local -title: Подключение к локальному узлу HydraDX ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Вы можете использовать Polkadot/apps для подключения к локальному узлу HydraDX. Для этого вам необходимо иметь доступ к порту `9944`, который используется для подключений через веб-сокеты RPC. - -:::warning - -Если вы запускаете узел в качестве валидатора, мы настоятельно рекомендуем вам занести в черный список порт `9944` для удаленных подключений. Этот порт может быть использован третьими сторонами для снижения производительности вашего узла, что может привести к резкому сокращению и непроизвольной потере средств. Вы должны использовать порт `9944` для подключения к узлу валидатора только тогда, когда узел находится в вашей локальной сети. - -::: - -### Доступ к вашему локальному узлу с помощью Polkadot/apps {#accessing-your-local-node-using-polkadotapps} - -Чтобы получить доступ к своему узлу, откройте [Polkadot/apps](https://polkadot.js.org/apps/) и щелкните в верхнем левом углу, чтобы изменить сеть. - -
- -
- -После открытия меню нажмите **Development** и выберите **Local node**. - -
- -
- -При необходимости измените IP-адрес и нажмите ***Switch***, чтобы переключиться на локальный узел. - -
- -
- -Теперь вы должны быть подключены к своему локальному узлу и иметь возможность взаимодействовать с ним. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md b/i18n/ru/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md deleted file mode 100644 index a1c8d9a97..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/polkadotjs_apps_public.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -id: polkadotjs_apps_public -title: Подключение к публичной ноде ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -Есть два общедоступных узла RPC, которые обслуживаются HydraDX и нашими партнерами. Вы можете использовать эти узлы для взаимодействия со Snakenet. Вы можете напрямую подключиться к общедоступному узлу с помощью Polkadot/apps, нажав на ссылки ниже: - -* [RPC node hosted by HydraDX](https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/explorer) - -## Подключиться к узлу RPC вручную {#connect-manually-to-an-rpc-node} - -Чтобы получить доступ к общедоступному узлу RPC вручную, откройте [Polkadot/apps](https://polkadot.js.org/apps/) и щелкните в верхнем левом углу, чтобы изменить сеть. - -
- -
- -Щелкните по **LIVE NETWORKS** и выберите **HydraDX**. - -
- -
- -Выберите один из узлов и нажмите **Switch**. - -
- -
- -Теперь вы должны подключиться к выбранному общедоступному узлу RPC. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/tip_request.md b/i18n/ru/docusaurus-plugin-content-docs/current/tip_request.md deleted file mode 100644 index 2a944143e..000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/tip_request.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -id: tip_request -title: Request a Treasury Tip ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -With the launch of the [HydraDX New Deal incentives program](#link-to-new-deal), community members can request HDX tips from the Treasury as a reward for their contributions. This guide walks you through the process of tip requests. You can find more information about the different types of activities that get rewarded in [this post](/spending_fw). - -The process of requesting a Treasury tip consists of two steps. In the first step, contributors need to publish their tip request in Commonwealth.im with a description of the contribution. As a second step, the Treasury tip request must be submitted on-chain using Polkadot/apps. - -## 01 Publish the Tip Request in Commonwealth.im {#01-publish-tip-request} - -To safeguard transparency, all Treasury tip requests must be published in a thread on the [HydraDX Commonwealth page](https://commonwealth.im/hydradx). Before opening a thread, you need to link your HydraDX wallet to Commonwealth.im: Click *Log in* (top right corner) and select *Connect with wallet > polkadot-js*. - -
- login -
- -After selecting your HDX address in the popup, you will be asked to sign the message using your wallet and to set a display name for this wallet. - -Once logged in, you need to create a new thread for your tip request. Navigate to the top-right part of the page and click on *New thread > New thread*. You can also directly use this link: https://commonwealth.im/hydradx/new/thread. - -You can use the title of the thread to indicate the subject (tip request) and the topic of the contribution. In the body of the thread, please provide the following information: - -* Period when the contribution was made -* A brief summary of the contribution -* The amount of the requested tip (in HDX) -* Time spent on the contribution (in hours) -* If needed, a more detailed description including the relevance of the contribution to HydraDX - -For reference, you can take a look at [this example tip request](https://commonwealth.im/hydradx/proposal/discussion/1165-tip-request-add-documentation-for-staking). - -After filling out the information, post the thread and it should become available in the general list. - -:::note - -Nominators and validators who overbonded their HDX and got "stuck" can request a Treasury tip of 1 HDX which will allow them to unbond some of their tokens. If this applies to your case, please create a Commonwealth thread following [this example](https://commonwealth.im/hydradx/proposal/discussion/1166-tip-request-overbonded-staker). - -::: - -## 02 Submit the Tip Request On-Chain {#02-submit-on-chain} - -After publishing your Treasury tip request, you need to submit it on-chain. For this purpose, your wallet needs to hold a small amount of HDX to cover the transaction fees. If you currently do not hold any HDX, you do not need to execute this step - someone else will submit your tip request on-chain for you. - -Treasury tip requests can be submitted on-chain with Polkadot/apps using the following link: https://polkadot.js.org/apps/?rpc=wss%253A%252F%252Frpc.hydradx.cloud#/treasury/tips. - -To submit a new tip request, click on *Propose tip* and provide the following information: - -* **submit with account** - select the account which will sign the transaction for submitting the tip request on-chain. This account needs to hold a small amount of HDX for transaction costs. -* **beneficiary** - select or enter the address of the account which will receive the Treasury tip. This account must correspond to the account which opened the Commonwealth thread. -* **tip reason** - provide a URL to the Commonwealth thread. - -
- login -
- -To submit the tip request, click on *Propose tip* and sign the transaction. - -Once the transaction is confirmed, you should see the tip request on the overview page. - -
- login -
diff --git a/i18n/ru/docusaurus-theme-classic/footer.json b/i18n/ru/docusaurus-theme-classic/footer.json deleted file mode 100644 index d9a9e39bb..000000000 --- a/i18n/ru/docusaurus-theme-classic/footer.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "link.title.Community": { - "message": "Сообщество", - "description": "The title of the footer links column with title=Community in the footer" - }, - "link.item.label.Discord": { - "message": "Дискорд", - "description": "The label of footer link with label=Discord linking to https://discord.gg/HDNPFFrcnW" - }, - "link.item.label.Twitter": { - "message": "Твиттер", - "description": "The label of footer link with label=Twitter linking to https://twitter.com/hydra_dx" - }, - "copyright": { - "message": "Copyright © 2021 Intergalactic, Inc. Built with Docusaurus.", - "description": "The footer copyright" - } -} \ No newline at end of file diff --git a/i18n/ru/docusaurus-theme-classic/navbar.json b/i18n/ru/docusaurus-theme-classic/navbar.json deleted file mode 100644 index 6f3226c3d..000000000 --- a/i18n/ru/docusaurus-theme-classic/navbar.json +++ /dev/null @@ -1,14 +0,0 @@ -{ - "title": { - "message": "HydraDX Документация", - "description": "The title in the navbar" - }, - "item.label.Docs": { - "message": "Документы", - "description": "Navbar item with label Docs" - }, - "item.label.HydraDX Homepage": { - "message": "HydraDX Домашняя страница", - "description": "Navbar item with label HydraDX Homepage" - } -} \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index 3ace9039b..8afa5fbdd 100644 --- a/sidebars.js +++ b/sidebars.js @@ -1,6 +1,6 @@ module.exports = { sidebar: { - HydraDX: [ + Hydration: [ "intro", "omnipool_trading", "omnipool_dca", diff --git a/src/css/custom.css b/src/css/custom.css index 0bd84a9a7..eb2e4d2a7 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -6,13 +6,13 @@ /* You can override the default Infima variables here. */ :root { - --ifm-color-primary: #f653a2; - --ifm-color-primary-dark: #f43491; - --ifm-color-primary-darker: #f42489; - --ifm-color-primary-darkest: #db0b70; - --ifm-color-primary-light: #f872b3; - --ifm-color-primary-lighter: #f882bb; - --ifm-color-primary-lightest: #fbb1d5; + --ifm-color-primary: #E53E76; + --ifm-color-primary-dark: #e22464; + --ifm-color-primary-darker: #da1d5d; + --ifm-color-primary-darkest: #b4184c; + --ifm-color-primary-light: #e85888; + --ifm-color-primary-lighter: #ea6491; + --ifm-color-primary-lightest: #ef8bad; --ifm-code-font-size: 95%; } diff --git a/static/CNAME b/static/CNAME index 0d8c274d2..2c8026d85 100644 --- a/static/CNAME +++ b/static/CNAME @@ -1 +1 @@ -docs.hydradx.io \ No newline at end of file +docs.hydration.net \ No newline at end of file diff --git a/static/img/favicon.png b/static/img/favicon.png index 5c7bd3054..5ab798a93 100644 Binary files a/static/img/favicon.png and b/static/img/favicon.png differ diff --git a/static/img/logo.svg b/static/img/logo.svg index 9f185bd3c..e39e3163f 100644 --- a/static/img/logo.svg +++ b/static/img/logo.svg @@ -1 +1,3 @@ - \ No newline at end of file + + + diff --git a/yarn.lock b/yarn.lock index 3f21fa601..745f71010 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3976,25 +3976,10 @@ caniuse-api@^3.0.0: lodash.memoize "^4.1.2" lodash.uniq "^4.5.0" -caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001181: - version "1.0.30001191" - resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001191.tgz#bacb432b6701f690c8c5f7c680166b9a9f0843d9" - integrity sha512-xJJqzyd+7GCJXkcoBiQ1GuxEiOBCLQ0aVW9HMekifZsAVGdj5eJ4mFB9fEhSHipq9IOk/QXFJUiIr9lZT+EsGw== - -caniuse-lite@^1.0.30001280: - version "1.0.30001286" - resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001286.tgz#3e9debad420419618cfdf52dc9b6572b28a8fff6" - integrity sha512-zaEMRH6xg8ESMi2eQ3R4eZ5qw/hJiVsO/HlLwniIwErij0JDr9P+8V4dtx1l+kLq6j3yy8l8W4fst1lBnat5wQ== - -caniuse-lite@^1.0.30001400, caniuse-lite@^1.0.30001426: - version "1.0.30001442" - resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001442.tgz#40337f1cf3be7c637b061e2f78582dc1daec0614" - integrity sha512-239m03Pqy0hwxYPYR5JwOIxRJfLTWtle9FV8zosfV5pHg+/51uD4nxcUlM8+mWWGfwKtt8lJNHnD3cWw9VZ6ow== - -caniuse-lite@^1.0.30001587, caniuse-lite@^1.0.30001591: - version "1.0.30001599" - resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001599.tgz#571cf4f3f1506df9bf41fcbb6d10d5d017817bce" - integrity sha512-LRAQHZ4yT1+f9LemSMeqdMpMxZcc4RMWdj4tiFe3G8tNkWK+E58g+/tzotb5cU6TbcVJLr4fySiAW7XmxQvZQA== +caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001181, caniuse-lite@^1.0.30001280, caniuse-lite@^1.0.30001400, caniuse-lite@^1.0.30001426, caniuse-lite@^1.0.30001587, caniuse-lite@^1.0.30001591: + version "1.0.30001627" + resolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001627.tgz" + integrity sha512-4zgNiB8nTyV/tHhwZrFs88ryjls/lHiqFhrxCW4qSTeuRByBVnPYpDInchOIySWknznucaf31Z4KYqjfbrecVw== ccount@^2.0.0: version "2.0.1"