Revert "Merge branch 'master' of https://github.com/djhatrang/polkado…

…t-wiki"

This reverts commit b1feee8, reversing
changes made to 35a67af.

components/Referenda-Tracks.jsx

@@ -57,7 +57,7 @@ async function GetTracks(network, wsUrl, setReturnValue) {
     tableData.push(
       <tr key={trackData[0]}>
         <td><b>{trackData[0]}</b></td>
-        <td><a href={`#${origin.toLowerCase().replace(" ", "-")}`}><b>{origin}</b></a></td>
+        <td><b>{origin}</b></td>
         <td>{trackData[1].maxDeciding}</td>
         <td>{HumanReadable(trackData[1].decisionDeposit, network)}</td>
         <td style={hover} title={`${trackData[1].preparePeriod} Blocks`}>{BlocksToTime(trackData[1].preparePeriod)}</td>

components/utilities/data/PolkadotAuctions.json

@@ -688,16 +688,16 @@
     "startBlock": 14065600,
     "startHash": "0x9e266086e86d910bec6dab22ba4c5e0c27a06c2e82aeed1a612230865f26e6dc",
     "endPeriodBlock": 14092600,
-    "endPeriodHash": "0xcc0f604ba2e80b3e22d96d5d355772510e542a2b1bd61fc875db2d04bbaaee0d",
+    "endPeriodHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
     "biddingEndsBlock": 14164600,
-    "biddingEndsHash": "0x327540ef3573c646661bd229d5a584f6f10f7d36e040e970c766baac9338ad8f",
+    "biddingEndsHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
     "onboardStartBlock": 14227200,
     "onboardStartHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
     "onboardEndBlock": 23904000,
     "onboardEndHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
     "startDate": 1675305504009,
-    "endPeriodDate": 1675467570000,
-    "biddingEndsDate": 1675899888000,
+    "endPeriodDate": null,
+    "biddingEndsDate": null,
     "onboardStartDate": null,
     "onboardEndDate": null
   },

docs/build/build-parachains.md

@@ -271,7 +271,7 @@ connected to {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}. Thi
 - An embedded full client of the Relay Chain
 - Block authorship compatibility
 
-Are you interested in building a PDK? See the [future PDKs](#future-pdks) section for details.
+Are you interested in building a PDK? See the [future PDKs](##future-pdks) section for details.
 
 ### How to set up your parachain
 

docs/general/claims.md

@@ -0,0 +1,16 @@
+---
+id: claims
+title: Polkadot Claims
+sidebar_label: Claims
+description: Step-by-step guide on how to claim your DOT tokens.
+keywords: [claim, DOT, token sale]
+slug: ../claims
+---
+
+For the most update-to-date information on DOT claims, checkout the following claiming resources and
+tutorials:
+
+- [Why do I need to claim my DOT tokens and is there a deadline?](https://support.polkadot.network/support/solutions/articles/65000063553-why-do-i-need-to-claim-my-dot-tokens-and-is-there-a-deadline-)
+- [I claimed my DOT before Polkadot went live, but still see zero balance!](https://support.polkadot.network/support/solutions/articles/65000063667-i-claimed-my-dot-before-polkadot-went-live-but-still-see-zero-balance-)
+- [How to claim your DOT - Tutorial](https://support.polkadot.network/support/solutions/articles/65000138217-how-to-claim-your-dot-tutorial)
+- [How do I know my claim worked?](https://support.polkadot.network/support/solutions/articles/65000103605-how-do-i-know-my-claim-worked-)

docs/general/community.md

@@ -114,15 +114,12 @@ you face any issues, join the rooms individually.
 
 ## Ecosystem
 
-- [Polkadot & Kusama Ecosystem Map](https://dotinsights.subwallet.app/) - Comprehensive list of
-  projects building in the ecosystem made by SubWallet with support from Parity Technologies.
-- [Polkadot Deep Dive Quarterly Report](https://dotinsights.subwallet.app/polkadot-report-q4-2022-en/) -
-  A quarterly report series that dives deep into the growth of the whole ecosystem. Made by
-  SubWallet with sections focused on Ecosystem Overview, DeFi, NFT & Web3.
+- [Polkadot & Kusama Ecosystem Map](https://dotinsights.subwallet.app/) - Comprehensive list of projects building in the ecosystem 
+  made by SubWallet with support from Parity Technologies.
+- [Polkadot Deep Dive Quarterly Report](https://dotinsights.subwallet.app/polkadot-report-q4-2022-en/) - A quarterly report series that 
+  dives deep into the growth of the whole ecosystem. Made by SubWallet with sections focused on Ecosystem Overview, DeFi, NFT & Web3.
 - [Polkadot Stack](../build/build-open-source.md) - if you're interested in seeing what's under
   development and where there's room for your contributions.
 - [Teams Building on Polkadot](https://polkaproject.com/) - Community maintained list of teams
   building on Polkadot and/or Substrate. (Note that this may contain inaccuracies, as it's
-  unofficial)
-- [Polkadot Stack](../build/build-open-source.md) - if you're interested in seeing what's under
-  development and where there's room for your contributions.
+  unofficial).

docs/general/ens.md

@@ -0,0 +1,81 @@
+---
+id: ens
+title: Adding accounts to an ENS domain
+sidebar_label: Using ENS with DOT/KSM accounts
+description: Steps on how to use an ENS with Substrate-based accounts.
+keywords: [ENS, domain, eth]
+slug: ../ens
+---
+
+ENS (Ethereum Name Service) is a distributed and open system of smart contracts on the Ethereum
+blockchain which allows users to claim domain names like `bruno.eth`.
+
+The ENS is a domain that is equivalent to a DNS (Domain Name System) domain. Instead, it offers a
+decentralized and secure way to translate text via smart contracts. Supporting wallets can then
+allow senders to input ENS domains instead of long and unwieldy addresses. This prevents phishing,
+fraud, typos, and adds a layer of usability on top of the regular wallet user experience.
+
+:::note
+
+You will need an ENS name and an Ethereum account with some ether in it to follow along with this
+guide. To register an ENS name, visit the [ENS App](https://app.ens.domains) or any number of
+subdomain registrars like [Nameth](https://nameth.io). Note that if you're using an older ENS name,
+you should make sure you're using the
+[new resolver](https://medium.com/the-ethereum-name-service/ens-registry-migration-is-over-now-what-a-few-things-to-know-fb05f921872a).
+Visiting the ENS App will warn you about this if not. You will also need some way to use your
+Ethereum address - following this guide on a personal computer is recommended. Wallets like
+[Frame](https://frame.sh/) and [Metamask](https://metamask.io) are safe and will make interacting
+with the Ethereum blockchain through your browser very easy.
+
+:::
+
+Despite living on the Ethereum blockchain, the ENS system has multi-chain support. In this guide,
+you'll go through the process of adding a KSM and DOT address to ENS. We cover both KSM and DOT to
+show two different approaches.
+
+:::note
+
+DOT can currently only be added using the Resolver method. KSM can be added through both methods are
+described below.
+
+:::
+
+This guide is also available in video format [on YouTube](https://youtu.be/XKjZk-5_mQc).
+
+## Adding via the UI
+
+The [ENS App](https://app.ens.domains) allows an ENS domain owner to inspect all records bound to
+the domain, and to add new ones.
+
+![bruno.eth domain name in the ENS application](../assets/ens/01-min.png)
+
+In the example above, the domain `bruno.eth` has an Ethereum and a Bitcoin address attached. Let's
+attach a KSM account. First, click the `[+]` icon in the Records tab.
+
+![The plus icon in the records tab](../assets/ens/02-min.png)
+
+Then, pick "Other Addresses", "KSM", and input the Kusama address:
+
+![Inputs needed to register a KSM address](../assets/ens/03-min.png)
+
+After clicking Save, your Ethereum wallet will ask you to confirm a transaction. Once processed, the
+record will show up on the domain's page:
+
+![KSM address now visible in bruno.eth records](../assets/ens/04-min.png)
+
+The same process applies to adding your DOT address.
+
+Once the transaction is confirmed, your address will be bound to your ENS domain.
+
+### Wallet Support
+
+There is no wallet support for ENS names for either KSM or DOT at this time, but the crypto
+accounting and portfolio application [Rotki](https://rotki.com/) does support KSM ENS resolution.
+
+### Relevant links
+
+- [ENS docs](https://docs.ens.domains/)
+- [ENS Multi-chain announcement](https://medium.com/the-ethereum-name-service/ens-launches-multi-coin-support-15-wallets-to-integrate-92518ab20599)
+- [Address encoder](https://github.com/ensdomains/address-encoder)
+- [Namehash calculator](https://swolfeyes.github.io/ethereum-namehash-calculator/)
+- [Address to pubkey converter](https://www.shawntabrizi.com/substrate-js-utilities/)

docs/general/faq.md

@@ -168,7 +168,7 @@ there will be bridges between Polkadot and most of the other major chains.
 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](redenomination.md), the new DOT is called DOT.
 
 ### What is the inflation rate of the DOT?
 

docs/learn/learn-redenomination.md → docs/general/redenomination.md

@@ -1,15 +1,12 @@
 ---
-id: learn-redenomination
+id: redenomination
 title: Redenomination of DOT
 sidebar_label: Redenomination of DOT
 description: Learn about the DOT token Redenomination.
 keywords: [DOT, redenomination]
-slug: ../learn-redenomination
+slug: ../redenomination
 ---
 
-On August 21, 2020, the redenomination of DOT, the native token on Polkadot, occurred. From this
-date, one DOT (old) equals 100 new DOT.
-
 :::info Denomination Day
 
 The DOT redenomination took place on 21 August 2020, known as Denomination Day, at block number
@@ -18,12 +15,13 @@ 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
-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,
-as in, ten decimal places. DOT denominated to twelve decimal places is referred to as "DOT (old)"
-and DOT denominated to ten decimal places is generally referred to as "DOT". When the difference
-must be made explicit, the current ten-decimal-denominated DOT is referred to as "_New DOT_".
+interacting with the system, the smallest unit of account is called 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, as in, ten decimal places. DOT denominated to twelve decimal places is referred to as "DOT
+(old)" and DOT denominated to ten decimal places is generally referred to as "DOT". When the
+difference must be made explicit, the current ten-decimal-denominated DOT is referred to as "_New
+DOT_".
 
 :::note Redenomination Explainer
 
@@ -39,10 +37,10 @@ denomination by a factor of one hundred.
 
 The overall effect of this change was that the number of Polkadot's smallest unit, the Planck,
 remained constant, while the DOT balance for all holders was increased by a factor of one hundred.
-As one can see from the example below, the number of Plancks a user has does not change, only the
-number of Plancks that constitute a single DOT. A user with 1_000_000_000_000 Plancks still has the
-same number of Plancks but will have 100 DOT under the new denomination, as opposed to one DOT under
-the old denomination.
+As one can see from the example below, the number of Plancks that a user has does not change, only
+the number of Plancks that constitute a single DOT. A user with 1_000_000_000_000 Plancks still has
+the same number of Plancks, but will have 100 DOT under the new denomination, as opposed to one DOT
+under the old denomination.
 
 ```
    Before the change the decimal was here
@@ -79,10 +77,10 @@ was summarized as having four effects if approved by KSM holders.
 
 :::
 
-The initial referendum was proposed before the Polkadot genesis block, assuming that making a
-redenomination would be simpler before the Polkadot chain was live. However, many in the community
-pointed out the disconnect between the two networks and how it was unfair for holders of DOT to be
-impacted by a vote by a different token holder set. For this reason, Web3 Foundation
+The initial referendum was proposed prior to the Polkadot genesis block under the assumption that
+making a redenomination would be simpler before the Polkadot chain was live. However, many in the
+community pointed out the disconnect of the two networks and how it was unfair for holders of DOT to
+be impacted by a vote by a different token holder set. For this reason, Web3 Foundation
 [decided to make a new vote on Polkadot](https://polkadot.network/results-of-dot-redenomination-referendum/)
 when it went live, although the Kusama vote ended with a majority in favor of the redenomination
 change.
@@ -101,25 +99,26 @@ redenomination.**
 
 After the genesis block of Polkadot was created and the network was running with a decentralized
 community of validators securing the network, Web3 Foundation decided to put the redenomination
-topic up for a vote again. This time, the vote was explicitly binding — meaning that it would
-be executed if voted through. In comparison, the vote on Kusama was non-binding to capture a signal
-without a direct way to affect the Polkadot chain.
+topic up to a vote again. This time, the vote was explicitly binding — meaning that it would
+be executed if voted through. In comparison, the vote on Kusama was of course non-binding, being at
+best a way to capture a signal without a direct way to affect the Polkadot chain.
 
 Based on the feedback received during the Kusama referendum, the
 [Polkadot vote](https://polkadot.network/the-first-polkadot-vote/) was held as an approval vote,
 with four available options. DOT holders could issue votes for any configuration of the four
-options: no change, a change of 10x, a change of 100x, or a change of 1000x. The voting logic was
-contained in a specially-built Substrate pallet included in Polkadot's runtime for this poll.
+options: no change, a change of 10x, a change of 100x, or a change of 1000x. The vote logic was
+contained in a specially-built Substrate pallet that was included in Polkadot's runtime for this
+poll.
 
 :::info Summary of the Vote
 
-- Any combination of the four options may have been approved by the voter. There was no need to
-  select only one option.
-- Approving all or none of the options was equivalent and did not affect the outcome.
-- All voters could alter their votes any number of times before the close of the poll.
+- Any combination of the four options may have been approved of by the voter. There was no need to
+  only select one option.
+- Approving of all or none of the options was equivalent and did not affect the outcome.
+- All voters were able to alter their votes any number of times prior to the close of the poll.
 - No discretionary lock-voting was in place; all DOT used to vote counts the same.
-- Voting was made on a per-account basis; a single account must have voted the same way and could
-  not split its vote.
+- Voting was made on a per-account basis; a single account must have voted the same way and was
+  unable to split its vote.
 - This vote did not affect any economics of the Polkadot platform. As in, staking rewards,
   inflation, effective market capitalization, and the underlying balances of every account remained
   completely unchanged. It was “merely” about what units the network uses to denominate the balances
@@ -135,8 +134,8 @@ community for a final, binding decision.
 ![redenomination](../assets/redenomination.png)
 
 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
-the vote. The redenomination proposal passed with 86% of the voters favoring a 100x factor increase
+redenomination vote were tallied. About one third of the total DOT in the network participated in
+the vote. The redenominaton proposal passed with 86% of the voters favoring a 100x factor increase
 (or two decimal places of precision loss).
 
 Polkadot's redenomination then took place on 21 August, now known as Denomination Day, at block
@@ -153,8 +152,8 @@ every account.
 
 If you are the builder of a tool that consumes the
 [`@polkadot/api`](https://yarnpkg.com/package/@polkadot/api) package — then there should be no
-real changes to be made in your application. The denomination is technically a cosmetic change, and
-every value remains a constant amount of Plancks.
+real changes that need to be made in your application. The denomination is technically a cosmetic
+change and every value is still a constant amount of Plancks.
 
 However — if you are a builder of a tool that displays DOT balances to users (e.g. a wallet)
 or handles DOT balances in an off-chain or custodial way, then you will need to ensure that you