From 9c08f2e8292923103930ac2c210d000c513e167e Mon Sep 17 00:00:00 2001 From: Filippo <110459737+filippoweb3@users.noreply.github.com> Date: Wed, 18 Dec 2024 16:27:51 +0100 Subject: [PATCH] Bug fix links (#6460) * edits * minor fix --- docs/general/faq.md | 4 ++-- docs/learn/learn-nft-projects.md | 2 +- docs/learn/learn-nominator.md | 8 ++++---- docs/learn/learn-parachains-protocol.md | 6 +++--- docs/learn/learn-polkadot-opengov.md | 2 +- docs/learn/learn-staking.md | 19 ++++++++++--------- docs/learn/learn-xcm-transport.md | 2 +- ...aintain-guides-how-to-validate-polkadot.md | 11 ++++++----- 8 files changed, 28 insertions(+), 26 deletions(-) diff --git a/docs/general/faq.md b/docs/general/faq.md index 202946db0927..6780a597e93b 100644 --- a/docs/general/faq.md +++ b/docs/general/faq.md @@ -41,7 +41,7 @@ DOT. ## Polkadot Roadmap For more information on the Polkadot roadmap please visit the -[official Polkadot website](https://polkadot.network/technology/#roadmap). +[official Polkadot website](https://www.opengov.watch/polkadot-roadmap). ## Consensus @@ -215,7 +215,7 @@ ten billion) Plancks, meaning that the new DOT was valued at ten decimal places. The inflation rate is approximately 120,000,000 DOT per year. The 85% of inflation is rewarded to validators for performing their duties, while the 15% goes to -the treasury. Please see the article on [inflation](../learn/learn-staking.md/#inflation) for more +the treasury. Please see the article on [inflation](../learn/learn-inflation.md) for more information. ### Why can't crowdloaned DOT be staked? diff --git a/docs/learn/learn-nft-projects.md b/docs/learn/learn-nft-projects.md index 0857e9a0ca8c..845f7daa9f68 100644 --- a/docs/learn/learn-nft-projects.md +++ b/docs/learn/learn-nft-projects.md @@ -193,7 +193,7 @@ read [the non-technical docs](https://docs.rmrk.app). The Asset Hub is a generic assets parachain which provides functionality for deploying and transferring assets — both Fungible and Non-Fungible Tokens (NFTs). The Asset Hub currently hosts -[Uniques pallet](./learn-nft-pallets.md/#uniques-pallet) and the +[Uniques pallet](./learn-nft-pallets.md#uniques-pallet) and the [NFTs pallet](./learn-nft-pallets.md#nfts-pallet) with NFT 2.0 functionalities. ## Unique Network diff --git a/docs/learn/learn-nominator.md b/docs/learn/learn-nominator.md index 43b61c572589..ede63649539a 100644 --- a/docs/learn/learn-nominator.md +++ b/docs/learn/learn-nominator.md @@ -115,12 +115,12 @@ reasoning for generating distinct accounts for this purpose is elaborated in the You can generate your stash and staking proxy account via any of the recommended methods, which are detailed on the [account generation](../learn/learn-accounts.md#account-generation) page. The first thing you need to do before becoming a nominator is to make sure you have a -[**stash account**](./learn-staking.md/#stash-account-and-staking-proxy) where you can transfer -funds you want to use for staking. For these accounts, it is recommended to use a "cold wallet" -solution such as [Ledger](../general/ledger.md) or [Polkadot Vault](../general/polkadot-vault.md). +[**stash account**](./learn-staking.md#stash-account-and-staking-proxy) where you can transfer funds +you want to use for staking. For these accounts, it is recommended to use a "cold wallet" solution +such as [Ledger](../general/ledger.md) or [Polkadot Vault](../general/polkadot-vault.md). After setting up the stash account, it is recommended to have a -[**staking proxy**](./learn-staking-advanced.md/#staking-proxies). Although you can be a nominator +[**staking proxy**](./learn-staking-advanced.md#staking-proxies). Although you can be a nominator with just a stash account, having a staking proxy is good practice for security reasons. A staking proxy of the stash will be able to sign for all staking-related transactions as well. The diff --git a/docs/learn/learn-parachains-protocol.md b/docs/learn/learn-parachains-protocol.md index 6ed3e8b1b134..11b63cdcaa56 100644 --- a/docs/learn/learn-parachains-protocol.md +++ b/docs/learn/learn-parachains-protocol.md @@ -212,7 +212,7 @@ which the validators distributed their erasure-coded chunks, but it does not gua validity. Because the number of para-validators on each parachain is so low, collusion is a reasonable concern. By separating block production ([BABE](./learn-consensus.md#block-production-babe)) from finality -([GRANDPA](./learn-consensus.md/#finality-gadget-grandpa)), validators can perform extra validity +([GRANDPA](./learn-consensus.md#finality-gadget-grandpa)), validators can perform extra validity checks after a block is produced but before it is finalized. Thus, once the parablock is considered available and part of the parachain, it is still "pending @@ -285,7 +285,7 @@ secondary check). Approved para-blocks are shown as yellow squares. Having a bad parablock on a fork of the relay chain is not catastrophic as long as the block is not approved and finalized by the finality gadget -[GRANDPA](./learn-consensus.md/#finality-gadget-grandpa). If the block is not finalized, the fork on +[GRANDPA](./learn-consensus.md#finality-gadget-grandpa). If the block is not finalized, the fork on the chain containing that block can be ignored in favor of another fork containing good blocks. Dealing with a bad parablock includes the following stages: @@ -343,7 +343,7 @@ b) in another relay chain block notes are fed into the approval code. The gossiped messages are of two types, assignment notices, and approval votes, and are signed with [approval keys](https://paritytech.github.io/polkadot/book/protocol-approval.html#approval-keys). -Such keys are part of the [session keys](./learn-cryptography.md/#session-keys) used by validators. +Such keys are part of the [session keys](./learn-cryptography.md#session-keys) used by validators. Briefly, approval keys are: - **Approval assignment keys** that are sr25519 keys used only for assignment criteria diff --git a/docs/learn/learn-polkadot-opengov.md b/docs/learn/learn-polkadot-opengov.md index 884fd2d578bf..2986887ee8e4 100644 --- a/docs/learn/learn-polkadot-opengov.md +++ b/docs/learn/learn-polkadot-opengov.md @@ -298,7 +298,7 @@ The maximum number of "doublings" of the [lock period](../general/chain-state-values.md#conviction-voting-lock-period) is set to 6 (and thus 32 lock periods in total). For additional information regarding the timeline of governance events, check out the governance section on the -[Polkadot Parameters page](maintain-polkadot-parameters/#governance). +[Polkadot Parameters page](../maintain/maintain-polkadot-parameters.md#governance). Votes are always "counted" at the same time (at the end of the voting period), no matter how long the tokens are locked. diff --git a/docs/learn/learn-staking.md b/docs/learn/learn-staking.md index 843f41f8496e..0ec79fa13c36 100644 --- a/docs/learn/learn-staking.md +++ b/docs/learn/learn-staking.md @@ -51,7 +51,7 @@ actions: - **Block production**, i.e. the way multiple blocks candidates are produced, and - **Block finality**, i.e. the way only one block out of many candidates is selected and added to - the canonical chain (see [this](learn-consensus.md/#probabilistic-vs-provable-finality) article + the canonical chain (see [this](./learn-consensus.md#probabilistic-vs-provable-finality) article for more information about finality). Proof-of-Work (PoW) and Proof-of-Stake (PoS) are well-known mechanisms used to reach consensus in a @@ -84,10 +84,11 @@ to get rewarded, and the PoS network rewards good behavior and punishes bad beha ## Nominated Proof-of-Stake (NPoS) -Polkadot implements [Nominated Proof-of-Stake (NPoS)](learn-consensus.md/#nominated-proof-of-stake), -a relatively novel and sophisticated mechanism to select the validators who are allowed to -participate in its [consensus](learn-consensus.md) protocol. NPoS encourages token holders to -participate as **nominators**. +Polkadot implements +[Nominated Proof-of-Stake (NPoS)](./learn-consensus.md#nominated-proof-of-stake), a relatively novel +and sophisticated mechanism to select the validators who are allowed to participate in its +[consensus](learn-consensus.md) protocol. NPoS encourages token holders to participate as +**nominators**. Any potential validators can indicate their intention to be a validator candidate. Their candidacies are made public to all nominators, and a nominator, in turn, submits a @@ -192,8 +193,8 @@ contribute to the economic security of the network will be nominators, thus here role of nominators. However, it is worth mentioning that validators do most of the heavy lifting: they run the validator nodes and manage [session keys](https://research.web3.foundation/Polkadot/security/keys/session), produce new block -candidates in [BABE](learn-consensus.md/#block-production-babe), vote and come to consensus in -[GRANDPA](learn-consensus.md/#finality-gadget-grandpa), validate the state transition function of +candidates in [BABE](./learn-consensus.md#block-production-babe), vote and come to consensus in +[GRANDPA](./learn-consensus.md#finality-gadget-grandpa), validate the state transition function of parachains, and possibly some other responsibilities regarding data availability and [XCM](learn-xcm.md). For more information, you can take a look at the [validator docs](learn-validator.md) to understand what you need to do as a validator. If you want @@ -349,7 +350,7 @@ the higher its vulnerability for hacks or scams. So, if one uses a key for multi blockchain network, it is likely that the account can get compromised. Note that the damage linked to stolen private keys is different depending on the type of account derivation. In the case of soft derivation, all derived accounts are compromised. More information about account derivation can be -found [here](../learn/learn-accounts.md/#derivation-paths). +found [here](./learn-account-advanced.md#derivation-paths). :::info @@ -451,7 +452,7 @@ automatically check if you qualify. For more information, visit the - Low barrier of entry through [Nomination Pools](learn-nomination-pools.md). - Can choose [multiple validators](../general/chain-state-values.md#maximum-votes-per-nominator) which can help to decentralize the network through the sophisticated - [NPoS system](learn-consensus.md/#nominated-proof-of-stake) + [NPoS system](./learn-consensus.md#nominated-proof-of-stake) - 85% of inflation/year of the tokens is primarily intended for staking rewards. Check the [inflation](learn-staking-advanced.md#inflation) section on the Wiki for more information. diff --git a/docs/learn/learn-xcm-transport.md b/docs/learn/learn-xcm-transport.md index 466b146e2a4d..8431878c450c 100644 --- a/docs/learn/learn-xcm-transport.md +++ b/docs/learn/learn-xcm-transport.md @@ -63,7 +63,7 @@ For detailed information about VMP see dedicated section in _Vertical Message Passing_ message passing between the relay chain itself and a parachain. Message data in both cases exists on the relay chain and are interpreted by the relay chain according to -[XCM](./learn-xcm.md/#cross-consensus-message-format-xcm) standards. This includes: +[XCM](./learn-xcm.md#cross-consensus-message-format-xcm-format) standards. This includes: - #### UMP (Upward Message Passing) diff --git a/docs/maintain/maintain-guides-how-to-validate-polkadot.md b/docs/maintain/maintain-guides-how-to-validate-polkadot.md index 4c7ad3c1d206..4ae9ab14e9c6 100644 --- a/docs/maintain/maintain-guides-how-to-validate-polkadot.md +++ b/docs/maintain/maintain-guides-how-to-validate-polkadot.md @@ -560,11 +560,12 @@ First, go to the [Staking](https://polkadot.js.org/apps/#/staking/actions) secti later. However, _withdrawing_ any bonded amount requires the duration of the unbonding period. On Kusama, the unbonding period is 7 days. On Polkadot, the planned unbonding period is 28 days. - **Payment destination** - The account where the rewards from validating are sent. More info - [here](../learn/learn-staking.md/#reward-distribution). Starting with runtime version v23 natively - included in client version [0.9.3](https://github.com/paritytech/polkadot/releases/tag/v0.9.3), - payouts can go to any custom address. If you'd like to redirect payments to an account that is not - the stash account, you can do it by entering the address here. Note that it is extremely unsafe to - set an exchange address as the recipient of the staking rewards. + [here](../learn/learn-staking.md#claiming-staking-rewards). Starting with runtime version v23 + natively included in client version + [0.9.3](https://github.com/paritytech/polkadot/releases/tag/v0.9.3), payouts can go to any custom + address. If you'd like to redirect payments to an account that is not the stash account, you can + do it by entering the address here. Note that it is extremely unsafe to set an exchange address as + the recipient of the staking rewards. Once everything is filled in properly, click `Bond` and sign the transaction with your Stash account.