diff --git a/docs/build/build-parachains.md b/docs/build/build-parachains.md
index 734fde12fbfc..a1aa17d57fb7 100644
--- a/docs/build/build-parachains.md
+++ b/docs/build/build-parachains.md
@@ -66,7 +66,7 @@ validators to participate in your network security are reduced.
decentralised application projects wishing to benefit from this security would want to become a
parachain to share in that pooled security.
-#### [On-Chain Governance](../learn/learn-governance.md) (Thought-through Governance)
+#### [On-Chain Governance](../learn/learn-polkadot-opengov.md) (Thought-through Governance)
Most governance systems in blockchains use an off-chain governance mechanism.
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}'s on-chain governance encourages
diff --git a/docs/build/build-protocol-info.md b/docs/build/build-protocol-info.md
index 80c58d851b8c..9c48a127892c 100644
--- a/docs/build/build-protocol-info.md
+++ b/docs/build/build-protocol-info.md
@@ -33,7 +33,7 @@ decided to redenominate the DOT token. The redenomination does not change the nu
The redenomination took effect 72 hours after transfers were enabled, at block 1_248_326, which
occurred at approximately 16:50 UTC on 21 Aug 2020. You can find more information about the
-redenomination [here](../learn/learn-redenomination.md).
+redenomination [here](../learn/archive/learn-redenomination.md).
## Addresses
diff --git a/docs/general/faq.md b/docs/general/faq.md
index 6cfd9829f76c..32262d5aec38 100644
--- a/docs/general/faq.md
+++ b/docs/general/faq.md
@@ -189,7 +189,7 @@ to consider precisely how benchmarking was performed for Polkadot.
The DOT (old) unit on Polkadot was at twelve decimal places, otherwise known as 1e12 Plancks. On 21
August, 2020, Denomination Day, the DOT (old) value was redenominated to 1e10 (10_000_000_000, or
ten billion) Plancks, meaning that the new DOT was valued at ten decimal places. Following the
-[redenomination](../learn/learn-redenomination.md), the new DOT is called DOT.
+[redenomination](../learn/archive/learn-redenomination.md), the new DOT is called DOT.
### What is the inflation rate of the DOT?
@@ -247,7 +247,7 @@ determined minority to overrule the vote of an apathetic majority in certain sit
mechanism is known as Adaptive Quorum Biasing. This makes proposals have a varying threshold for
approval or rejection based on what part of the governance protocol the proposal originated in. For
details on the subtleties of Polkadot's governance system, please see the
-[governance page](../learn/learn-governance.md).
+[governance page](../learn/learn-polkadot-opengov.md).
## Parachains
diff --git a/docs/general/getting-started.md b/docs/general/getting-started.md
index 8ef270d9ac48..ef2cdd207e0f 100644
--- a/docs/general/getting-started.md
+++ b/docs/general/getting-started.md
@@ -199,8 +199,8 @@ requirement to create proposals, to endorse them and to vote on them when they b
Bonding
{{ polkadot: :polkadot }}
or 5% of requested funding is a requirement to make a
-[treasury proposal](../learn/learn-treasury.md#creating-a-treasury-proposal). DOT can also enable
-you to participate in programs like the
+[treasury proposal](../learn/learn-polkadot-opengov-treasury.md). DOT can also enable you to
+participate in programs like the
[Thousand Validators Program](../general/thousand-validators.md#polkadot).
## Polkadot Gifts
diff --git a/docs/general/grants.md b/docs/general/grants.md
index a914eff6a9e8..e46e18527d92 100644
--- a/docs/general/grants.md
+++ b/docs/general/grants.md
@@ -43,7 +43,7 @@ The Polkadot Treasury is a pot of on-chain funds collected through transaction f
staking inefficiencies, etc. The funds held in the treasury can be spent on spending proposals. Both
Polkadot and Kusama offer everyone the opportunity to apply for funding via the treasury. See:
-- [Treasury Wiki](../learn/learn-treasury.md)
+- [Treasury Wiki](../learn/learn-polkadot-opengov-treasury.md)
- [Polkadot Treasury Guide](https://docs.google.com/document/d/1IZykdp2cyQavcRyZd_dgNj5DcgxgZR6kAqGdcNARu1w)
- [Kusama Treasury Guide](https://docs.google.com/document/d/1p3UQUjph5t8TVaWnTkfrI5mE-BABnM9Xvtuhdlhl6JE)
@@ -53,8 +53,9 @@ Due to high demand and spamming issues, the Kusama faucet is no longer in operat
Foundation has considered new ways to distribute KSM for people who need KSM to build.
If you are interested in obtaining KSM for building or research, you can apply through the
-[Treasury](../learn/learn-treasury.md#creating-a-treasury-proposal) or receive a
-[tip](../learn/learn-treasury.md#tipping) for doing something cool in the community.
+[Treasury](../learn/learn-polkadot-opengov-treasury.md) or receive a
+[tip](../learn/learn-polkadot-opengov-treasury.md#treasury-tracks) for doing something cool in the
+community.
:::
diff --git a/docs/general/kusama/kusama-claims.md b/docs/general/kusama/kusama-claims.md
index f7d4432e278b..30446641106d 100644
--- a/docs/general/kusama/kusama-claims.md
+++ b/docs/general/kusama/kusama-claims.md
@@ -260,7 +260,7 @@ Polkadot-JS UI and click "Confirm Claim."
At this point, you will see a success message if everything went right and your KSM will now be in
the account that you claimed to. Congratulations you can now participate in aspects of the Kusama
-network such as [governance](../../learn/learn-governance.md) and
+network such as [governance](../../learn/learn-polkadot-opengov.md) and
[staking](../../learn/learn-staking.md). During the soft launch period balance transfers will not be
enabled.
diff --git a/docs/general/kusama/kusama-getting-started.md b/docs/general/kusama/kusama-getting-started.md
index aa57f7f97380..92cbeb5a2adf 100644
--- a/docs/general/kusama/kusama-getting-started.md
+++ b/docs/general/kusama/kusama-getting-started.md
@@ -192,7 +192,7 @@ requirement to create proposals, to endorse them and to vote on them when they b
Bonding
{{ kusama: :kusama }}
or 5% of requested funding is a requirement to make a
-[treasury proposal](../../learn/learn-treasury.md#creating-a-treasury-proposal).
+[treasury proposal](../../learn/learn-polkadot-opengov-treasury.md).
### Kusama Gifts
diff --git a/docs/general/kusama/kusama-social-recovery.md b/docs/general/kusama/kusama-social-recovery.md
index 3872d995cdc1..c880d46301c9 100644
--- a/docs/general/kusama/kusama-social-recovery.md
+++ b/docs/general/kusama/kusama-social-recovery.md
@@ -162,8 +162,7 @@ The recovery process is now complete and successful.
There is still one possible way to recover the account without going through the recovery process.
That is by using the `Root` origin. However, in order to use root permissions, you will need to
-either go through the council or submit a public proposal. To learn more about governance, see
-[here](../../learn/learn-governance.md).
+either go through [governance](../../learn/learn-polkadot-opengov.md).
:::
diff --git a/docs/learn/learn-controller.md b/docs/learn/archive/learn-controller.md
similarity index 86%
rename from docs/learn/learn-controller.md
rename to docs/learn/archive/learn-controller.md
index f0ad563b8068..9dee90f9aa1a 100644
--- a/docs/learn/learn-controller.md
+++ b/docs/learn/archive/learn-controller.md
@@ -7,19 +7,20 @@ keywords: [nominated proof of stake, staking, controller]
slug: ../learn-controller
---
-:::info Controller accounts are deprecated
+
+
-Controller accounts are deprecated. For more information, see
+The content on this page is archived. Controller accounts are deprecated. For more information, see
[this discussion](https://forum.polkadot.network/t/staking-controller-deprecation-plan-staking-ui-leads-comms/2748).
-:::
+
Controller accounts were used for staking and were a "less-powerful" version of staking proxies.
Controllers could only sign for unbonding and rebonding funds, nominating and changing the reward
destination. The stash account was still used to bond more funds and change the controller.
Controller accounts became redundant and added unnecessary complexity to the staking mechanics.
-
+
With the setup shown above, the stash account was not entirely isolated. More complicated designs to
fully isolate the stash account included having both controller and staking proxies (see below).
@@ -31,7 +32,7 @@ set to be the controller, and the account security would not have been compromis
proxy was used to sign all staking-relate transactions. Note that you needed to sign with the stash
to change the staking proxy.
-
+
This past situation was similar to the present setup, except that now there is no option to set the
stash as controller and that the action of "changing the controller" is missing. From a practical
@@ -45,7 +46,7 @@ If the stash and controller were different accounts, the staking proxy was used
and change the controller. Thus the staking proxy was used to sign for those transactions that were
used less often and usually signed by the stash.
-
+
From a practical perspective, there were two accounts, and we needed to remember two passwords. From
a security perspective, the party who wanted to control our staking actions was required to control
diff --git a/docs/learn/learn-governance.md b/docs/learn/archive/learn-governance.md
similarity index 93%
rename from docs/learn/learn-governance.md
rename to docs/learn/archive/learn-governance.md
index 0e3f2b9bd75d..34b0c4c4194d 100644
--- a/docs/learn/learn-governance.md
+++ b/docs/learn/archive/learn-governance.md
@@ -7,22 +7,22 @@ keywords: [governance, referenda, proposal, voting, endorse]
slug: ../learn-governance
---
+
+
+
+The content on this page is archived. For up-to-date information about governance, see the
+[Polkadot OpenGov page](../../learn/learn-polkadot-opengov.md).
+
+
+
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} uses a sophisticated governance
mechanism that allows it to evolve gracefully overtime at the ultimate behest of its assembled
stakeholders. The stated goal is to ensure that the majority of the stake can always command the
network.
-:::info Polkadot OpenGov is live on Kusama Network
-
-Learn about the upcoming changes to the governance on
-{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} in this
-[Wiki doc on Polkadot OpenGov](./learn-polkadot-opengov.md).
-
-:::
-
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} brings together various novel
mechanisms, including an amorphous (abstract) form of state-transition function stored on-chain
-defined in a platform-agnostic language (i.e. [WebAssembly](learn-wasm.md)). It also allows for
+defined in a platform-agnostic language (i.e. [WebAssembly](../learn-wasm.md)). It also allows for
several on-chain voting mechanisms, such as referenda with the novel concept of
[Adaptive Quorum Biasing](#adaptive-quorum-biasing) and batch approval voting. All changes to the
protocol must be agreed upon by stake-weighted referenda.
@@ -37,7 +37,7 @@ a referendum to let all holders, weighted by stake, make the decision.
The figure below shows an overview of Governance V1 with the key actors and different paths for
submitting a proposal that can potentially be voted on as a referendum.
-
+
The public (i.e. token holders) can submit a proposal that gets added to the proposal queue. Here,
proposals are [endorsed](#endorsing-proposals), and the one that gets the most support will climb to
@@ -90,7 +90,7 @@ Referenda can be started in different ways:
:::info Starting a proposal in Governance V1
For more information about how to start a proposal, see the
-[dedicated page](../maintain/archive/maintain-guides-democracy.md#proposing-an-action).
+[dedicated page](../../maintain/archive/maintain-guides-democracy.md#proposing-an-action).
:::
@@ -99,9 +99,9 @@ For more information about how to start a proposal, see the
Anyone can submit a proposal by depositing the minimum amount of tokens for a certain period (number
of blocks). If someone agrees with the proposal, they may deposit the same amount of tokens to
support it - this action is called
-[_endorsing_](../maintain/archive/maintain-guides-democracy.md#endorsing-a-proposal). The proposal
-with the highest amount of bonded support will be selected to be a referendum in the next voting
-cycle based on an [alternating voting timetable](#alternating-voting-timetable).
+[_endorsing_](../../maintain/archive/maintain-guides-democracy.md#endorsing-a-proposal). The
+proposal with the highest amount of bonded support will be selected to be a referendum in the next
+voting cycle based on an [alternating voting timetable](#alternating-voting-timetable).
### Cancelling Proposals
@@ -145,7 +145,7 @@ options in voting are "aye", "nay", or abstaining entirely.
The structure of the timeline for all referenda is the same regardless of who initiates the
proposal, although the timeline length can vary (see below).
-
+
The figure above provides a summary view of the referenda timeline for Governance V1.
@@ -244,7 +244,7 @@ selection depends on which entity proposed the proposal and whether all Council
Let's use the image below as an example.
-
+
If a publicly submitted referendum only has a 25% turnout, the tally of _aye_ votes has to reach 66%
for it to pass since we applied **Positive Turnout Bias**. In contrast, when it has a 75% turnout,
@@ -356,19 +356,19 @@ below).
:::info Voluntary Locking
For more information about voluntary locking or conviction voting see
-[Polkadot OpenGov](./learn-polkadot-opengov.md#voluntary-locking).
+[Polkadot OpenGov](../learn-polkadot-opengov.md#voluntary-locking).
:::
### Delegations
In {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} you can
-[delegate your voting power](../maintain/archive/maintain-guides-democracy.md#delegate-a-vote) to
+[delegate your voting power](../../maintain/archive/maintain-guides-democracy.md#delegate-a-vote) to
another account you trust if you are not willing to stay up-to-date with all referenda.
-You can also use a [governance proxy](./learn-proxies.md#governance-proxy) to vote on behalf of your
-stash account. The proxy can be yours, or you can authorize a third-party governance proxy to vote
-with your stash. Learn more from the [dedicated page on Proxy Accounts](./learn-proxies.md).
+You can also use a [governance proxy](../learn-proxies.md#governance-proxy) to vote on behalf of
+your stash account. The proxy can be yours, or you can authorize a third-party governance proxy to
+vote with your stash. Learn more from the [dedicated page on Proxy Accounts](../learn-proxies.md).
## Council
@@ -378,7 +378,7 @@ each represented as an on-chain account. On
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}, the council currently consists of
{{ polkadot: 13 :polkadot }} {{ kusama: 19 :kusama }} members.
-Along with [controlling the treasury](learn-treasury.md), the council is called upon primarily for
+Along with [controlling the treasury](./learn-treasury.md), the council is called upon primarily for
three tasks of governance:
- Proposing sensible referenda
@@ -438,18 +438,18 @@ simultaneously. Voting on one does not prevent a user from voting on the other.
### How to be a council member?
-
+
All stakeholders can signal their approval of any of the registered candidates.
-Council elections are handled by the same [Phragmén election](../docs/learn-phragmen) process that
+Council elections are handled by the same [Phragmén election](../learn-phragmen.md) process that
selects validators from the available pool based on nominations. However, token holders' votes for
councilors are isolated from any nominations they may have on validators. Council terms last for one
{{ kusama: day :kusama }}{{ polkadot: week :polkadot }}.
-At the end of each term, [Phragmén election algorithm](../docs/learn-phragmen#algorithm) runs and
-the result will choose the new councilors based on the vote configurations of all voters. The
-election also chooses a set number of runners-up, which is currently
+At the end of each term, [Phragmén election algorithm](../learn-phragmen#algorithm) runs and the
+result will choose the new councilors based on the vote configurations of all voters. The election
+also chooses a set number of runners-up, which is currently
{{ kusama: 12 :kusama }}{{ polkadot: 20 :polkadot }} that will remain in the queue with their votes
intact.
diff --git a/docs/learn/learn-launch.md b/docs/learn/archive/learn-launch.md
similarity index 90%
rename from docs/learn/learn-launch.md
rename to docs/learn/archive/learn-launch.md
index 6c088fea68fc..5bb143fc6d2e 100644
--- a/docs/learn/learn-launch.md
+++ b/docs/learn/archive/learn-launch.md
@@ -7,6 +7,13 @@ keyword: [launch, phases, polkadot, DOT, claim, token sale, redenomination]
slug: ../learn-launch
---
+
+
+
+The content on this page is archived.
+
+
+
The Polkadot network has a phased roll-out plan, with important milestones toward decentralization
marking each phase. Keep up-to-date with the Polkadot's phased roll-out plan at by viewing the
[roadmap](https://polkadot.network/launch-roadmap/)
@@ -39,7 +46,7 @@ Once Web3 Foundation was confident in the stability of the network and there was
of validator intentions, Web3 Foundation used [Sudo](https://youtu.be/InekMjJpVdo) — a
superuser account with access to governance functions — to initiate the first validator
election. Following this election, the network transitioned from PoA into its second phase,
-[Nominated Proof of Stake (NPoS)](learn-staking.md), on June 18, 2020.
+[Nominated Proof of Stake (NPoS)](../learn-staking.md), on June 18, 2020.
## Governance
@@ -59,9 +66,8 @@ under control of any centralized authority.
## Balance Transfers
-To enable balance transfers, the community
-made a public proposal for a runtime upgrade that lifted the
-restriction on balance transfers. Transfer functionality was subsequently enabled on Polkadot at
+To enable balance transfers, the community made a public proposal for a runtime upgrade that lifted
+the restriction on balance transfers. Transfer functionality was subsequently enabled on Polkadot at
block number 1_205_128 on August 18, 2020, at 16:39 UTC.
## Core Functionality
diff --git a/docs/learn/learn-redenomination.md b/docs/learn/archive/learn-redenomination.md
similarity index 97%
rename from docs/learn/learn-redenomination.md
rename to docs/learn/archive/learn-redenomination.md
index 71eab906fe83..aecf3785641d 100644
--- a/docs/learn/learn-redenomination.md
+++ b/docs/learn/archive/learn-redenomination.md
@@ -7,6 +7,13 @@ keywords: [DOT, redenomination]
slug: ../learn-redenomination
---
+
+
+
+The content on this page is archived.
+
+
+
On August 21, 2020, the redenomination of DOT, the native token on Polkadot, occurred. From this
date, one DOT (old) equals 100 new DOT.
@@ -17,7 +24,7 @@ The DOT redenomination took place on 21 August 2020, known as Denomination Day,
:::
-While [DOT](../learn/learn-DOT.md) is the unit of currency on Polkadot that most people use when
+While [DOT](../../learn/learn-DOT.md) is the unit of currency on Polkadot that most people use when
interacting with the system, the smallest unit of account is the Planck. A Planck's relation to DOT
is like the relation of a Satoshi to Bitcoin. Before 21 August, the DOT was denominated as 1e12
Plancks, that is, twelve decimal places. After Denomination Day, DOT is denominated as 1e10 Plancks,
@@ -132,7 +139,7 @@ community for a final, binding decision.
## The Outcome
-
+
After two weeks of voting, the [results](https://polkadot.network/the-results-are-in/) of the
redenomination vote were tallied. About one-third of the total DOT in the network participated in
diff --git a/docs/learn/learn-treasury.md b/docs/learn/archive/learn-treasury.md
similarity index 93%
rename from docs/learn/learn-treasury.md
rename to docs/learn/archive/learn-treasury.md
index fd4a6909881e..606ca9fe4f52 100644
--- a/docs/learn/learn-treasury.md
+++ b/docs/learn/archive/learn-treasury.md
@@ -7,19 +7,18 @@ keywords: [treasury, funds, funding, tips, tipping]
slug: ../learn-treasury
---
-:::info Use OpenGov to access treasury funds
+
+
-Governance v1 is deprecated. To access
-{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} treasury funds use
-[OpenGov](./learn-polkadot-opengov.md). For more information about OpenGov Treasury see the
-[dedicated wiki page](./learn-polkadot-opengov-treasury.md).
+The content on this page is archived. For up-to-date information about treasury, see the
+[Polkadot OpenGov Treasury page](../../learn/learn-polkadot-opengov-treasury.md).
-:::
+
The Treasury is a pot of funds collected through a portion of block production rewards, transaction
-fees, slashing, [staking inefficiencies](learn-staking.md#inflation), etc.
+fees, slashing, [staking inefficiencies](../learn-staking.md#inflation), etc.
-The Treasury funds are held in a [system account](./learn-account-advanced.md#system-accounts) not
+The Treasury funds are held in a [system account](../learn-account-advanced.md#system-accounts) not
accessible by anyone; only the system internal logic can access it. Funds can be spent by making a
spending proposal that, if approved by the [Council](learn-governance.md#council), will enter a
waiting period before distribution. This waiting period is known as the _spend period_, and its
@@ -71,13 +70,13 @@ The Treasury is funded from different sources:
taken from the slash amount and varies per offence and number of reporters.
2. Transaction fees: A portion of each block's transaction fees goes to the Treasury, with the
remainder going to the block author.
-3. Staking inefficiency: [Inflation](learn-staking.md#inflation) is designed to be 10% in the first
- year, and the ideal staking ratio is set at 50%, meaning half of all tokens should be locked in
- staking. Any deviation from this ratio will cause a proportional amount of the inflation to go to
- the Treasury. In other words, if 50% of all tokens are staked, then 100% of the inflation goes to
- the validators as reward. If the staking rate is greater than or less than 50%, then the
- validators will receive less, with the remainder going to the Treasury.
-4. Parathreads: [Parathreads](learn-parathreads.md) participate in a per-block auction for block
+3. Staking inefficiency: [Inflation](../learn-staking.md#inflation) is designed to be 10% in the
+ first year, and the ideal staking ratio is set at 50%, meaning half of all tokens should be
+ locked in staking. Any deviation from this ratio will cause a proportional amount of the
+ inflation to go to the Treasury. In other words, if 50% of all tokens are staked, then 100% of
+ the inflation goes to the validators as reward. If the staking rate is greater than or less than
+ 50%, then the validators will receive less, with the remainder going to the Treasury.
+4. Parathreads: [Parathreads](../learn-parathreads.md) participate in a per-block auction for block
inclusion. Part of this bid goes to the validator that accepts the block and the remainder goes
to the Treasury.
diff --git a/docs/learn/learn-DOT.md b/docs/learn/learn-DOT.md
index 46df7f26773c..7e46a5beab0b 100644
--- a/docs/learn/learn-DOT.md
+++ b/docs/learn/learn-DOT.md
@@ -35,8 +35,8 @@ equals to 1012 Planck.
:::note DOT was redenominated at block #1_248_328
DOT was originally equal to 1012 Planck just like Kusama (which is referred to as "DOT
-(old)"), but went through a process of [redenomination](./learn-redenomination.md) which increased
-DOT's supply by 100x. As a consequence, 1 DOT now equals to 1010 Planck.
+(old)"), but went through a process of [redenomination](./archive/learn-redenomination.md) which
+increased DOT's supply by 100x. As a consequence, 1 DOT now equals to 1010 Planck.
:::
@@ -211,7 +211,8 @@ in the faucets repo
Unlike testnet DOT, Kusama tokens are not freely given away. Kusama tokens are available via the
[claims process](https://claim.kusama.network/) (if you had DOT at the time of Kusama genesis) or
-through the [Treasury](learn-treasury.md). Alternatively, they can be obtained on the open market.
+through the [Treasury](./archive/learn-treasury.md). Alternatively, they can be obtained on the open
+market.
## Polkadot Mainnet DOT
diff --git a/docs/learn/learn-archive.md b/docs/learn/learn-archive.md
new file mode 100644
index 000000000000..d8b44d8017f4
--- /dev/null
+++ b/docs/learn/learn-archive.md
@@ -0,0 +1,20 @@
+---
+id: learn-archive
+title: Learn Archive
+sidebar_label: Archive
+description: Archive for the Learn Section.
+keywords: [Gov1, Gov1 Treasury, Launch, Redenomination, Controller]
+slug: ../learn-archive
+---
+
+import DocCardList from '@theme/DocCardList';
+
+
+
+
+This section contains archived pages. The content in them no longer applies to Polkadot but can
+still be relevant for parachains and related projects.
+
+
+
+
diff --git a/docs/learn/learn-comparisons-cosmos.md b/docs/learn/learn-comparisons-cosmos.md
index f0ed472aa9fd..9c45c0084199 100644
--- a/docs/learn/learn-comparisons-cosmos.md
+++ b/docs/learn/learn-comparisons-cosmos.md
@@ -146,8 +146,9 @@ IBC, as chains do not share state, receiving chains must trust the security of a
Polkadot has [OpenGov](learn-polkadot-opengov.md) framewok with several trackss to pass proposals as
public referenda, where the majority of tokens can always control the outcome. Referenda can contain
-a variety of proposals, including fund allocation from an on-chain [Treasury](learn-treasury.md).
-Decisions get enacted on-chain and are binding and autonomous.
+a variety of proposals, including fund allocation from an on-chain
+[Treasury](./learn-polkadot-opengov-treasury.md). Decisions get enacted on-chain and are binding and
+autonomous.
Cosmos uses coin-vote signaling to pass referenda. The actual enactment of governance decisions is
carried out via a protocol fork, much like other blockchains. All token holders can vote, however,
diff --git a/docs/learn/learn-inflation.md b/docs/learn/learn-inflation.md
index 8a9bb59bdcf0..49fe863a9171 100644
--- a/docs/learn/learn-inflation.md
+++ b/docs/learn/learn-inflation.md
@@ -20,8 +20,8 @@ inflation is distributed to the stakers and part to the
:::info
-DOT went through [redenomination](./learn-redenomination.md) in 2020 that saw the DOT token supply
-increase by 100 times.
+DOT went through [redenomination](./archive/learn-redenomination.md) in 2020 that saw the DOT token
+supply increase by 100 times.
The current token supply on {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} is
{{ polkadot: (1.4 Billion DOT). :polkadot }}
diff --git a/docs/learn/learn-parachains-faq.md b/docs/learn/learn-parachains-faq.md
index 9c8137183740..b097da22a6d0 100644
--- a/docs/learn/learn-parachains-faq.md
+++ b/docs/learn/learn-parachains-faq.md
@@ -152,10 +152,10 @@ that are locked up to another buyer. This would allow the seller to get liquid t
for the parachain slot and the buyer to acquire the slot as well as the deposited tokens.
A number of system or common-good parachains may be granted slots by the
-[governing bodies](learn-governance.md) of the Relay Chain. System parachains can be recognized by a
-parachain ID lower than 1_000, and common-good parachains by a parachain ID between 1_000 and 1_999.
-Other parachains will have IDs 2_000 or higher. Such parachains would not have to bid for or renew
-their slots as they would be considered essential to the ecosystem's future.
+[governance](./learn-polkadot-opengov.md) of the Relay Chain. System parachains can be recognized by
+a parachain ID lower than 1_000, and common-good parachains by a parachain ID between 1_000 and
+1_999. Other parachains will have IDs 2_000 or higher. Such parachains would not have to bid for or
+renew their slots as they would be considered essential to the ecosystem's future.
### How are auctions scheduled?
diff --git a/docs/learn/learn-parachains.md b/docs/learn/learn-parachains.md
index 4240fefdb67f..aa9c721f08ea 100644
--- a/docs/learn/learn-parachains.md
+++ b/docs/learn/learn-parachains.md
@@ -191,9 +191,9 @@ There are several ways to allocate parachain slots on
[System parachains](#system-parachains) are allocated by
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}'s on-chain
-[governance](learn-governance.md) and are part of the network's protocol, such as bridges to other
-networks or chains. These typically do not have an economic model and help remove transactions from
-the Relay Chain, allowing for more efficient parachain processing.
+[governance](./learn-polkadot-opengov.md) and are part of the network's protocol, such as bridges to
+other networks or chains. These typically do not have an economic model and help remove transactions
+from the Relay Chain, allowing for more efficient parachain processing.
[Auction granted parachains](learn-auction.md) are granted in a permissionless auction. Parachain
teams can either bid with their own {{ polkadot: DOT :polkadot }}{{ kusama: KSM :kusama }} tokens,
diff --git a/docs/learn/learn-phragmen.md b/docs/learn/learn-phragmen.md
index d51194d71d98..ada437e8d56a 100644
--- a/docs/learn/learn-phragmen.md
+++ b/docs/learn/learn-phragmen.md
@@ -70,7 +70,7 @@ The process of computing the optimal solution for NPoS election can be delegated
:::info Deprecated in Polkadot OpenGov
-Phragmen was used for Council elections in [Governance v1](./learn-governance.md).
+Phragmen was used for Council elections in [Governance v1](./archive/learn-governance.md).
:::
diff --git a/docs/learn/learn-polkadot-opengov.md b/docs/learn/learn-polkadot-opengov.md
index b28db4ffd72b..c4734ba93923 100644
--- a/docs/learn/learn-polkadot-opengov.md
+++ b/docs/learn/learn-polkadot-opengov.md
@@ -16,8 +16,8 @@ import Fellowship from "./../../components/Fellowship";
:::caution The content in this document is subject to change
The governance protocol has already undergone iterations (see
-[Governance V1](./learn-governance.md)). Governance is a constantly evolving protocol at this stage
-in its lifecycle.
+[Governance V1](./archive/learn-governance.md)). Governance is a constantly evolving protocol at
+this stage in its lifecycle.
For technical information about Polkadot OpenGov and how to interact with it, please refer to this
[dedicated Wiki page](./learn-guides-polkadot-opengov.md).
@@ -63,12 +63,12 @@ agreed upon by stake-weighted referenda.
## Premise
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}'s first governance system
-([Governance V1](./learn-governance.md)) included three main components.
+([Governance V1](./archive/learn-governance.md)) included three main components.
-- The [Technical Committee](./learn-governance.md#technical-committee): A technocratic committee to
- manage upgrade timelines.
-- The [Council](./learn-governance.md#council): An approval-voted, elected executive "government" to
- manage parameters, admin, and spending proposals.
+- The [Technical Committee](./archive/learn-governance.md#technical-committee): A technocratic
+ committee to manage upgrade timelines.
+- The [Council](./archive/learn-governance.md#council): An approval-voted, elected executive
+ "government" to manage parameters, admin, and spending proposals.
- The Public: All token holders.
Over the first few years of operation, Governance V1 ensured the appropriate usage of treasury funds
@@ -76,8 +76,8 @@ and enabled timely upgrades and fixes. Like most early technologies, protocols m
mature to improve their shortcomings and keep up with modern advancements. In Governance V1, all
referenda carried the same weight as only one referendum could be voted on at a time (except for
emergency proposals), and the voting period could last multiple weeks. Also, an
-[alternating voting timetable](./learn-governance.md#alternating-voting-timetable) allowed to vote
-either for a public referendum or a council motion every
+[alternating voting timetable](./archive/learn-governance.md#alternating-voting-timetable) allowed
+to vote either for a public referendum or a council motion every
{{ polkadot: 28 days :polkadot }}{{ kusama: 7 days :kusama }}. This resulted in the system favoring
careful consideration of very few proposals instead of broad consideration of many.
@@ -87,8 +87,9 @@ the system can make at any given time.
The following content is focused on what the new Polkadot OpenGov version brings to the governance
on {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}, and on the main differences with
-previous governance versions. We recommend learning about [Governance v1](./learn-governance.md) to
-better understand the need for and the direction of Polkadot OpenGov.
+previous governance versions. We recommend learning about
+[Governance v1](./archive/learn-governance.md) to better understand the need for and the direction
+of Polkadot OpenGov.
## Summary
@@ -103,16 +104,17 @@ initiator of legislation, but it was often seen as a centralized entity. To furt
following main changes:
- Migrating all responsibilities of the Council to the public via a direct democracy voting system.
-- Dissolving the current [Council](./learn-governance.md#council) collective
+- Dissolving the current [Council](./archive/learn-governance.md#council) collective
- Allowing users to delegate voting power in more ways to community members
-- Dissolving the [Technical Committee](./learn-governance.md#technical-committee) and establishing
- the broader [Polkadot Technical Fellowship](./learn-polkadot-technical-fellowship.md)
+- Dissolving the [Technical Committee](./archive/learn-governance.md#technical-committee) and
+ establishing the broader [Polkadot Technical Fellowship](./learn-polkadot-technical-fellowship.md)
The figure below shows an overview of Polkadot OpenGov's structure.
:::info
-See [this page](./learn-governance.md#summary) for a comparison with the structure of Governance V1.
+See [this page](./archive/learn-governance.md#summary) for a comparison with the structure of
+Governance V1.
:::
@@ -160,25 +162,25 @@ and learn how to use it.
## Gov1 vs. Polkadot OpenGov
-| Governance V1 | Polkadot OpenGov | Polkadot OpenGov Benefit |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Includes the [Council](./learn-governance.md#council), the [Technical Committee](./learn-governance.md#technical-committee), and the Public (i.e. token holders). | Includes the Public and the [Technical Fellowship](./learn-polkadot-technical-fellowship.md). | Simpler and more decentralized structure. |
-| Referenda executed only from one origin (Root). Referenda in this origin must be carefully scrutinized. Therefore, there is only one track (i.e. only one referendum at a time can be executed). | Referenda executed from [multiple origins](./learn-polkadot-opengov-origins.md#origins-and-tracks-info), each with a different track that shapes proposals’ timelines. Depending on the origin, multiple referenda within the same track are possible. | Possibility to categorize proposals (based on importance and urgency) and execute them simultaneously within and between origin tracks. |
-| Proposals can be submitted by either the Council or the Public. | The public submits proposals. | More democratic. |
-| Uses [Adaptive Quorum Biasing](./learn-governance.md#adaptive-quorum-biasing) to define the approval threshold based on turnout. Given the same turnout, council-initiated referenda require fewer Aye votes to pass compared to public referenda. | Uses origin-specific approval and support curves defining the amount of approval and support (i.e. turnout) needed as a function of time. The same curves are applied to all referenda within the same origin track. | Referenda timeline depends on the origin and not on who submitted the proposal (i.e. Council or Public). This is a more democratic and equalitarian system. |
-| Uses [alternating voting timetable](./learn-governance.md#alternating-voting-timetable) allowing voters to cast votes for either council or public referenda every 28 eras. | Multiple referenda can be voted at the same time. | More flexible and agile governance system. |
-| Except for emergency proposals, all referenda have fixed voting and enactment periods of 28 eras. | Periods' length is customizable and has pre-defined limits for each origin. The same limits apply to all tracks with the same origin. For example, the track in the origin Root will be longer than the track within the Small Tipper origin. | Referenda’s timeline is tailored to their importance and urgency. Flexible enactment period based on origin. |
-| Emergency proposals turned referenda can be simultaneously voted on and executed with other referenda and have shorter enactment periods. They must be proposed by the Technical Committee and approved by the Council. | No emergency proposals. The Technical Fellowship can whitelist proposals that will have their origin with shorter lead-in, confirmation, and enactment periods. | The Technical Fellowship is a more decentralized entity when compared to the Technical Committee. Whitelisting a proposal requires a majority of approval from the fellowship. |
-| Only the [most-endorsed proposal](./learn-governance.md#endorsing-proposals) is able to transit from Launch to Voting period. The time for the transition is indeterminate, and (with no possibility of canceling endorsements) proposers and endorsers might wait a long time before a referendum is tabled, and getting their deposits back. | All proposals will eventually be voted on (given track capacity and deposit are met and the Lead-in period has ended). | It allows all proposals to get a chance to be voted on in a timely predictive manner. |
-| Only _aye_ or _nay_ votes possible. | Voters can have the additional voting options of abstaining or splitting votes. | More ways to engage in voting and increase turnout. |
-| Voters can decide to delegate votes to another account. | Voters can use [multirole delegations](#multirole-delegation) and delegate votes to different accounts depending on origins. | More agile delegations tailored by expertise. |
+| Governance V1 | Polkadot OpenGov | Polkadot OpenGov Benefit |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Includes the [Council](./archive/learn-governance.md#council), the [Technical Committee](./archive/learn-governance.md#technical-committee), and the Public (i.e. token holders). | Includes the Public and the [Technical Fellowship](./learn-polkadot-technical-fellowship.md). | Simpler and more decentralized structure. |
+| Referenda executed only from one origin (Root). Referenda in this origin must be carefully scrutinized. Therefore, there is only one track (i.e. only one referendum at a time can be executed). | Referenda executed from [multiple origins](./learn-polkadot-opengov-origins.md#origins-and-tracks-info), each with a different track that shapes proposals’ timelines. Depending on the origin, multiple referenda within the same track are possible. | Possibility to categorize proposals (based on importance and urgency) and execute them simultaneously within and between origin tracks. |
+| Proposals can be submitted by either the Council or the Public. | The public submits proposals. | More democratic. |
+| Uses [Adaptive Quorum Biasing](./archive/learn-governance.md#adaptive-quorum-biasing) to define the approval threshold based on turnout. Given the same turnout, council-initiated referenda require fewer Aye votes to pass compared to public referenda. | Uses origin-specific approval and support curves defining the amount of approval and support (i.e. turnout) needed as a function of time. The same curves are applied to all referenda within the same origin track. | Referenda timeline depends on the origin and not on who submitted the proposal (i.e. Council or Public). This is a more democratic and equalitarian system. |
+| Uses [alternating voting timetable](./archive/learn-governance.md#alternating-voting-timetable) allowing voters to cast votes for either council or public referenda every 28 eras. | Multiple referenda can be voted at the same time. | More flexible and agile governance system. |
+| Except for emergency proposals, all referenda have fixed voting and enactment periods of 28 eras. | Periods' length is customizable and has pre-defined limits for each origin. The same limits apply to all tracks with the same origin. For example, the track in the origin Root will be longer than the track within the Small Tipper origin. | Referenda’s timeline is tailored to their importance and urgency. Flexible enactment period based on origin. |
+| Emergency proposals turned referenda can be simultaneously voted on and executed with other referenda and have shorter enactment periods. They must be proposed by the Technical Committee and approved by the Council. | No emergency proposals. The Technical Fellowship can whitelist proposals that will have their origin with shorter lead-in, confirmation, and enactment periods. | The Technical Fellowship is a more decentralized entity when compared to the Technical Committee. Whitelisting a proposal requires a majority of approval from the fellowship. |
+| Only the [most-endorsed proposal](./archive/learn-governance.md#endorsing-proposals) is able to transit from Launch to Voting period. The time for the transition is indeterminate, and (with no possibility of canceling endorsements) proposers and endorsers might wait a long time before a referendum is tabled, and getting their deposits back. | All proposals will eventually be voted on (given track capacity and deposit are met and the Lead-in period has ended). | It allows all proposals to get a chance to be voted on in a timely predictive manner. |
+| Only _aye_ or _nay_ votes possible. | Voters can have the additional voting options of abstaining or splitting votes. | More ways to engage in voting and increase turnout. |
+| Voters can decide to delegate votes to another account. | Voters can use [multirole delegations](#multirole-delegation) and delegate votes to different accounts depending on origins. | More agile delegations tailored by expertise. |
## Proposals
:::info Starting a proposal in Governance v1
-See [this page](./learn-governance.md#proposals) for more information about starting referenda in
-Governance v1.
+See [this page](./archive/learn-governance.md#proposals) for more information about starting
+referenda in Governance v1.
:::
@@ -191,8 +193,8 @@ referenda.
:::info Cancelling Referenda in Governance v1
-See [this page](./learn-governance.md#cancelling-proposals) for more information about cancelling
-referenda in Governance v1.
+See [this page](./archive/learn-governance.md#cancelling-proposals) for more information about
+cancelling referenda in Governance v1.
:::
@@ -212,7 +214,7 @@ For more information about how to cancel a referendum see the
:::info Blacklisting
Blacklisting referenda in Polkadot OpenGov is
-[the same as in Governance v1](./learn-governance.md#blacklisting-proposals).
+[the same as in Governance v1](./archive/learn-governance.md#blacklisting-proposals).
:::
@@ -220,11 +222,11 @@ Blacklisting referenda in Polkadot OpenGov is
:::info Public and Council Referenda in Governance v1
-With the Council's dissolution, [council referenda](./learn-governance.md#council-referenda) are no
-longer present in Polkadot OpenGov.
+With the Council's dissolution, [council referenda](./archive/learn-governance.md#council-referenda)
+are no longer present in Polkadot OpenGov.
-See [this page](./learn-governance.md#public-referenda) for more information about public referenda
-in Governance v1.
+See [this page](./archive/learn-governance.md#public-referenda) for more information about public
+referenda in Governance v1.
:::
@@ -237,8 +239,8 @@ in Governance v1.
:::info Voting timetable in Governance v1
-See [this page](./learn-governance.md#referenda-timeline) for more information about the voting
-timetable in Governance v1.
+See [this page](./archive/learn-governance.md#referenda-timeline) for more information about the
+voting timetable in Governance v1.
:::
@@ -418,8 +420,9 @@ Delegations under Governance v1 will need to be re-issued under OpenGov.
:::info Adaptive Quorum Biasing is deprecated
-In Polkadot OpenGov, [Adaptive quorum biasing](./learn-governance.md#adaptive-quorum-biasing) used
-in Governance V1 has been replaced with the **Approval and Support system**.
+In Polkadot OpenGov,
+[Adaptive quorum biasing](./archive/learn-governance.md#adaptive-quorum-biasing) used in Governance
+V1 has been replaced with the **Approval and Support system**.
:::
@@ -511,8 +514,8 @@ amount earlier than those which use highly privileged classes such as `Root`.
:::info Enactment in Governance v1
-See [this page](./learn-governance.md#enactment) for more information about enactment in Governance
-v1.
+See [this page](./archive/learn-governance.md#enactment) for more information about enactment in
+Governance v1.
:::
@@ -583,8 +586,8 @@ information.
### Multirole Delegation
Polkadot OpenGov builds on the
-[vote delegation feature from Governance v1](./learn-governance.md#delegations) where a voter can
-delegate their voting power to another voter. It does so by introducing a feature known as
+[vote delegation feature from Governance v1](./archive/learn-governance.md#delegations) where a
+voter can delegate their voting power to another voter. It does so by introducing a feature known as
**multirole delegation**, where voters can specify a different delegate for every class of
referendum in the system. Delegation can be done per track, and accounts can choose to select
different delegates (or no delegation) for each track.
diff --git a/docs/learn/learn-polkadot-technical-fellowship.md b/docs/learn/learn-polkadot-technical-fellowship.md
index 003f500c9e45..657645c14c66 100644
--- a/docs/learn/learn-polkadot-technical-fellowship.md
+++ b/docs/learn/learn-polkadot-technical-fellowship.md
@@ -19,11 +19,11 @@ repository.
The Polkadot Technical Fellowship was established in 2022 and plays an important role in the
Polkadot OpenGov. This fellowship replaced the
-[Technical Committee](./learn-governance.md#technical-committee) from Polkadot's first iteration of
-governance, and will be serving both the Polkadot and Kusama networks. This Fellowship is designed
-to be far broader in membership (i.e. to work well with even tens of thousands of members) and with
-far lower barriers to entry both in terms of administrative process flow and levels of expertise.
-For more information, read through the
+[Technical Committee](./archive/learn-governance.md#technical-committee) from Polkadot's first
+iteration of governance, and will be serving both the Polkadot and Kusama networks. This Fellowship
+is designed to be far broader in membership (i.e. to work well with even tens of thousands of
+members) and with far lower barriers to entry both in terms of administrative process flow and
+levels of expertise. For more information, read through the
[Fellowship Manifesto](https://github.com/polkadot-fellows/manifesto/blob/0c3df46d76625980b8b48742cb86f4d8fa6dda8d/manifesto.pdf).
:::
diff --git a/docs/learn/learn-runtime-upgrades.md b/docs/learn/learn-runtime-upgrades.md
index 6a1548fdf2f9..2c36095bb159 100644
--- a/docs/learn/learn-runtime-upgrades.md
+++ b/docs/learn/learn-runtime-upgrades.md
@@ -35,8 +35,8 @@ The {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} runtime is st
{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} can upgrade its runtime by upgrading
the logic stored on-chain and removes the coordination challenge of requiring thousands of node
operators to upgrade in advance of a given block number. Polkadot stakeholders propose and approve
-upgrades through the [on-chain governance](learn-governance.md) system, which also enacts them
-autonomously.
+upgrades through the [on-chain governance](./learn-polkadot-opengov.md) system, which also enacts
+them autonomously.
As a result of storing the Runtime as part of the state, the Runtime code itself becomes state
sensitive, and calls to Runtime can change the Runtime code itself. Therefore, the Polkadot Host
@@ -123,9 +123,13 @@ on how the nodes on the network are reacting to a new upgrade.
## Monitoring Runtime Changes
You can monitor the chain for upcoming upgrades. The client release notes include the hashes of any
-proposals related to any on-chain upgrades for easy matching. We recommend keeping track of the Polkadot Fellowship's [runtime upgrades](https://github.com/polkadot-fellows/runtimes/releases/latest) to be aware of changes in the runtime logic.
+proposals related to any on-chain upgrades for easy matching. We recommend keeping track of the
+Polkadot Fellowship's
+[runtime upgrades](https://github.com/polkadot-fellows/runtimes/releases/latest) to be aware of
+changes in the runtime logic.
### Governance V1
+
Monitor the chain for:
1. `democracy(Started)` events and log `index` and `blockNumber`. This event indicates that a
@@ -147,14 +151,28 @@ proposals and referenda.
\* E.g. via `pallets/democracy/storage/ReferendumInfoOf?key1=index&at=blockNumber` on Sidecar.
### Polkadot OpenGov
-Runtime upgrades are voted on and executed via [Polkadot OpenGov](./learn-polkadot-opengov.md). You should monitor the Relay chain as follows to know when the next runtime upgrade will be enacted:
-
-1. Check each block for `referenda (Submitted)` events and check if `track` is `1`, which means it's `whitelistedCaller` - this is the only track that can enact runtime upgrdes - and log its `index` and `proposal`, this will help you keep track of the proposal's evolution. With the index you can lookup the details of the proposal in [Polkassembly.io](https://polkadot.polkassembly.io/whitelisted-caller?trackStatus=all&page=1) to see if it corresponds with a runtime upgrade.
-2. In the same block, look for the extrinsic `referenda.submit`, which has the `enactment_moment` for the proposal in blocks.
-3. Check also for `referenda (DecisionDepositPlaced)` events where `index` matches the one previously found. This means that the required deposit has been placed.
-4. `referenda (DecisionStarted)` indicates that the decision period has started for the referenda of that `index`.
-5. `referenda (ConfirmStarted)` indicates that `index`'s referenda has entered the confirmation period.
- 1. `referenda (Confirmed)` indicates that `index`'s referenda has been confirmed and will enter the enactment period. With this and `enactment_moment`, you can estimate when the proposal will be enacted.
- 2. `referenda (Rejected)` indicates that `index`'s referenda has been rejected and will not be enacted.
-6. Once the enactment period is over, there will be a `system(CodeUpdated)` event confirming the execution of the runtime upgrade.
+Runtime upgrades are voted on and executed via [Polkadot OpenGov](./learn-polkadot-opengov.md). You
+should monitor the Relay chain as follows to know when the next runtime upgrade will be enacted:
+
+1. Check each block for `referenda (Submitted)` events and check if `track` is `1`, which means it's
+ `whitelistedCaller` - this is the only track that can enact runtime upgrdes - and log its `index`
+ and `proposal`, this will help you keep track of the proposal's evolution. With the index you can
+ lookup the details of the proposal in
+ [Polkassembly.io](https://polkadot.polkassembly.io/whitelisted-caller?trackStatus=all&page=1) to
+ see if it corresponds with a runtime upgrade.
+2. In the same block, look for the extrinsic `referenda.submit`, which has the `enactment_moment`
+ for the proposal in blocks.
+3. Check also for `referenda (DecisionDepositPlaced)` events where `index` matches the one
+ previously found. This means that the required deposit has been placed.
+4. `referenda (DecisionStarted)` indicates that the decision period has started for the referenda of
+ that `index`.
+5. `referenda (ConfirmStarted)` indicates that `index`'s referenda has entered the confirmation
+ period.
+ 1. `referenda (Confirmed)` indicates that `index`'s referenda has been confirmed and will enter
+ the enactment period. With this and `enactment_moment`, you can estimate when the proposal
+ will be enacted.
+ 2. `referenda (Rejected)` indicates that `index`'s referenda has been rejected and will not be
+ enacted.
+6. Once the enactment period is over, there will be a `system(CodeUpdated)` event confirming the
+ execution of the runtime upgrade.
diff --git a/docs/learn/learn-staking.md b/docs/learn/learn-staking.md
index 1c8cca9e796b..e22483f6853e 100644
--- a/docs/learn/learn-staking.md
+++ b/docs/learn/learn-staking.md
@@ -451,11 +451,11 @@ Slashing will happen if a validator misbehaves (e.g. goes offline, attacks the n
modified software) in the network. They and their nominators will get slashed by losing a percentage
of their bonded/staked DOT.
-Any slashed DOT will be added to the [Treasury](learn-treasury.md). The rationale for this (rather
-than burning or distributing them as rewards) is that slashes may then be reverted by the Council by
-simply paying out from the Treasury. This would be useful in situations such as faulty slashes. In
-the case of legitimate slashing, it moves tokens away from malicious validators to those building
-the ecosystem through the normal Treasury process.
+Any slashed DOT will be added to the [Treasury](./archive/learn-treasury.md). The rationale for this
+(rather than burning or distributing them as rewards) is that slashes may then be reverted by the
+Council by simply paying out from the Treasury. This would be useful in situations such as faulty
+slashes. In the case of legitimate slashing, it moves tokens away from malicious validators to those
+building the ecosystem through the normal Treasury process.
Validators with a larger total stake backing them will get slashed more harshly than less popular
ones, so we encourage nominators to shift their nominations to less popular validators to reduce
diff --git a/docs/learn/learn-system-chains.md b/docs/learn/learn-system-chains.md
index 5628fd45f964..a795db8023f7 100644
--- a/docs/learn/learn-system-chains.md
+++ b/docs/learn/learn-system-chains.md
@@ -13,7 +13,7 @@ import RPC from "./../../components/RPC-Connection";
System parachains are those that contain core Polkadot protocol features, but in parachains rather
than the Relay Chain. Rather than leasing an execution core by economic means (e.g., auction),
-execution cores are allocated by network [governance](learn-governance.md).
+execution cores are allocated by network [governance](./learn-guides-polkadot-opengov.md).
By hosting core protocol logic in parachains instead of the Relay Chain, Polkadot uses its own
scaling technology -- namely, parallel execution -- to host _itself_. System parachains remove
diff --git a/docs/learn/learn-transaction-fees.md b/docs/learn/learn-transaction-fees.md
index c772275f8176..d69a8e76dcec 100644
--- a/docs/learn/learn-transaction-fees.md
+++ b/docs/learn/learn-transaction-fees.md
@@ -70,8 +70,8 @@ Together, these fees constitute the inclusion fee. The inclusion fee is the base
fee plus the adjusted weight fee.
The inclusion fee is deducted from the sender's account before transaction execution. A portion of
-the fee will go to the block author, and the remainder will go to the [Treasury](learn-treasury.md).
-This is 20% and 80%, respectively.
+the fee will go to the block author, and the remainder will go to the
+[Treasury](./archive/learn-treasury.md). This is 20% and 80%, respectively.
Tips are an optional transaction fee that users can add. Tips are not part of the inclusion fee and
are an incentive to block authors for prioritizing a transaction, and the entire tip goes directly
diff --git a/docs/maintain/archive/maintain-guides-democracy.md b/docs/maintain/archive/maintain-guides-democracy.md
index 0c9fe4afc35d..0844ed77ce7e 100644
--- a/docs/maintain/archive/maintain-guides-democracy.md
+++ b/docs/maintain/archive/maintain-guides-democracy.md
@@ -18,14 +18,14 @@ The content on this page is archived. For up-to-date information about governanc
The public referenda chamber is one of the three bodies of on-chain governance as it's instantiated
in Polkadot and Kusama. The other two bodies are the
[council](./maintain-guides-how-to-join-council.md) and the
-[technical committee](../../learn/learn-governance.md#technical-committee).
+[technical committee](../../learn/archive/learn-governance.md#technical-committee).
Public referenda can be proposed and voted on by any token holder in the system as long as they
provide a bond. After a proposal is made, others can agree with it by _endorsing_ it and putting up
tokens equal to the original bond. During every launch period, the most endorsed proposal will be
moved to the public referenda table where it can be voted upon. Voters who are willing to lock up
their tokens for a greater duration of time can do so and get their votes amplified. For more
-details on the governance system please see [here](../../learn/learn-governance.md).
+details on the governance system please see [here](../../learn/archive/learn-governance.md).
This guide will instruct token holders how to propose and vote on public referenda using the
Democracy module. Below are a few links to stay informed and directly engage with the community.
diff --git a/docs/maintain/archive/maintain-guides-how-to-join-council.md b/docs/maintain/archive/maintain-guides-how-to-join-council.md
index f7b3184970bc..a5f8a873d6dd 100644
--- a/docs/maintain/archive/maintain-guides-how-to-join-council.md
+++ b/docs/maintain/archive/maintain-guides-how-to-join-council.md
@@ -18,7 +18,7 @@ The content on this page is archived. For up-to-date information about governanc
The council is an elected body of on-chain accounts that are intended to represent the passive
stakeholders of Polkadot and/or Kusama. The council has two major tasks in governance: proposing
referenda and vetoing dangerous or malicious referenda. For more information on the council, see the
-[governance page](../../learn/learn-governance.md#council). This guide will walk you through
+[governance page](../../learn/archive/learn-governance.md#council). This guide will walk you through
entering your candidacy to the council.
## Submit Candidacy
diff --git a/docs/maintain/archive/maintain-guides-how-to-vote-councillor.md b/docs/maintain/archive/maintain-guides-how-to-vote-councillor.md
index 2ace684c4d45..8f948230ff00 100644
--- a/docs/maintain/archive/maintain-guides-how-to-vote-councillor.md
+++ b/docs/maintain/archive/maintain-guides-how-to-vote-councillor.md
@@ -18,8 +18,8 @@ The content on this page is archived. For up-to-date information about governanc
The council is an elected body of on-chain accounts that are intended to represent the passive
stakeholders of Polkadot and/or Kusama. The council has two major tasks in governance: proposing
referenda and vetoing dangerous or malicious referenda. For more information on the council, see the
-[governance page](../../learn/learn-governance.md#council). This guide will walk you through voting
-for councillors in the elections.
+[governance page](../../learn/archive/learn-governance.md#council). This guide will walk you through
+voting for councillors in the elections.
## Voting for Councillors
diff --git a/docs/maintain/maintain-archive.md b/docs/maintain/maintain-archive.md
index a39dd4fb4e13..18fed1fc6f2f 100644
--- a/docs/maintain/maintain-archive.md
+++ b/docs/maintain/maintain-archive.md
@@ -2,8 +2,8 @@
id: maintain-archive
title: Maintain Archive
sidebar_label: Archive
-description: Steps on setting up a boot node.
-keywords: [bootnode, web socket, remote, connection, secure websocket]
+description: Archive for the Maintain Section.
+keywords: [Democracy, Council, Gov1, Councillor]
slug: ../maintain-archive
---
diff --git a/docs/maintain/maintain-guides-validator-payout.md b/docs/maintain/maintain-guides-validator-payout.md
index 1a9c55d89477..13ad0f8daac3 100644
--- a/docs/maintain/maintain-guides-validator-payout.md
+++ b/docs/maintain/maintain-guides-validator-payout.md
@@ -78,7 +78,7 @@ Then, `v` ↑ if `w` ↑, as this reduces `p` : `w`, with respect to `e`
Increased `v` is expected, and initially keeping `p` ↓ using the same para-validator set for
all parachains ensures
[availability](../learn/learn-parachains-protocol.md#availability-and-unavailability-phase) and
-[approval voting](../learn/learn-governance.md). In addition, despite `v` ↑ on an `e` to `e`
+[voting](../learn/learn-polkadot-opengov.md). In addition, despite `v` ↑ on an `e` to `e`
basis, over time, the amount of rewards each validator receives will equal out based on the
continuous selection of para-validators.
diff --git a/docs/maintain/maintain-polkadot-parameters.md b/docs/maintain/maintain-polkadot-parameters.md
index e914e668d5e3..8e3cda678dc5 100644
--- a/docs/maintain/maintain-polkadot-parameters.md
+++ b/docs/maintain/maintain-polkadot-parameters.md
@@ -107,4 +107,5 @@ DOT have 10 decimals of precision. In other words, 10 \*\* 10 (10_000_000_000 or
Plancks make up a DOT.
The denomination of DOT was changed from 12 decimals of precision at block #1,248,328 in an event
-known as _Denomination Day_. See [Redenomination](../learn/learn-redenomination.md) for details.
+known as _Denomination Day_. See [Redenomination](../learn/archive/learn-redenomination.md) for
+details.
diff --git a/kusama-guide/sidebars.js b/kusama-guide/sidebars.js
index 4d992794da7c..f19de873d29d 100644
--- a/kusama-guide/sidebars.js
+++ b/kusama-guide/sidebars.js
@@ -608,17 +608,15 @@ module.exports = {
label: "Archive",
description: "Implementations no longer live on Kusama.",
link: {
- type: 'generated-index',
- title: "Archive",
- description: "Implementations no longer live on Kusama.",
- slug: '/learn-archive-index',
+ type: 'doc',
+ id: 'learn/learn-archive',
},
items: [
- "learn/learn-governance",
- "learn/learn-treasury",
- "learn/learn-launch",
- "learn/learn-redenomination",
- "learn/learn-controller",
+ "learn/archive/learn-governance",
+ "learn/archive/learn-treasury",
+ "learn/archive/learn-launch",
+ "learn/archive/learn-redenomination",
+ "learn/archive/learn-controller",
],
},
],
diff --git a/kusama-guide/static/css/custom.css b/kusama-guide/static/css/custom.css
index a9e0da469a98..a7f7076c099b 100755
--- a/kusama-guide/static/css/custom.css
+++ b/kusama-guide/static/css/custom.css
@@ -730,7 +730,15 @@ div[role=banner] .close {
color: #fff;
}
-
+div.sticky {
+ position: -webkit-sticky;
+ position: sticky;
+ top: 0;
+ background-color: yellow;
+ padding: 30px;
+ font-size: 20px;
+ font-family: 'Unbounded';
+}
/* ==========================================================================
Typing Style for Main Page
diff --git a/polkadot-wiki/sidebars.js b/polkadot-wiki/sidebars.js
index 220573f52465..e4ff01a819db 100644
--- a/polkadot-wiki/sidebars.js
+++ b/polkadot-wiki/sidebars.js
@@ -626,17 +626,15 @@ module.exports = {
label: "Archive",
description: "Implementations no longer live on Polkadot.",
link: {
- type: 'generated-index',
- title: "Archive",
- description: "Implementations no longer live on Polkadot.",
- slug: '/learn-archive-index',
+ type: 'doc',
+ id: "learn/learn-archive",
},
items: [
- "learn/learn-governance",
- "learn/learn-treasury",
- "learn/learn-launch",
- "learn/learn-redenomination",
- "learn/learn-controller",
+ "learn/archive/learn-governance",
+ "learn/archive/learn-treasury",
+ "learn/archive/learn-launch",
+ "learn/archive/learn-redenomination",
+ "learn/archive/learn-controller",
],
},
],