From 9b0c689063d6642f16fedcd33eb39d87df66c032 Mon Sep 17 00:00:00 2001
From: fennar01 <42185291+fennar01@users.noreply.github.com>
Date: Wed, 1 Jun 2022 23:12:50 +1200
Subject: [PATCH 001/244] Fixed broken link
The link to "The Merge" was broken so I updated the path to the best link I could find. Needs verification.
---
.../docs/consensus-mechanisms/pow/mining-algorithms/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md b/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md
index 38c5a127ca7..0ad03ab6df9 100644
--- a/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md
+++ b/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md
@@ -5,7 +5,7 @@ lang: en
sidebar: true
---
-Ethereum mining has used two mining algorithms, Dagger Hashimoto and Ethash. Dagger Hashimoto was never used to mine Ethereum, being superseded by Ethash before mainet launched. It was a R&D mining algorithm that paved the way for Ethash. However, it has historical significance as an important innovation in Ethereum's development. Proof-of-work mining itself will be deprecated in favor of proof-of-stake during [The Merge](/merge/), which is forecast to happen in Q3-Q4 2022.
+Ethereum mining has used two mining algorithms, Dagger Hashimoto and Ethash. Dagger Hashimoto was never used to mine Ethereum, being superseded by Ethash before mainet launched. It was a R&D mining algorithm that paved the way for Ethash. However, it has historical significance as an important innovation in Ethereum's development. Proof-of-work mining itself will be deprecated in favor of proof-of-stake during [The Merge](/en/upgrades/merge/), which is forecast to happen in Q3-Q4 2022.
The fundamental idea of both mining algorithms is that a miner tries to find a nonce input using brute force computation so that the result is below a certain difficulty threshold. This difficulty threshold can be dynamically adjusted, allowing block production to happen at a regular interval.
From d43b17d409dc107c8c84c0a7ce94bf3bb7c41198 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?M=C3=A1rio=20Havel?=
<61149543+taxmeifyoucan@users.noreply.github.com>
Date: Fri, 3 Jun 2022 12:41:51 +0100
Subject: [PATCH 002/244] Pieces of software
---
src/content/developers/docs/consensus-mechanisms/pos/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/consensus-mechanisms/pos/index.md b/src/content/developers/docs/consensus-mechanisms/pos/index.md
index b9bd6026629..bd61d40fa74 100644
--- a/src/content/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/developers/docs/consensus-mechanisms/pos/index.md
@@ -56,7 +56,7 @@ Overall, proof-of-stake, as it is implemented on Ethereum, has been demonstrated
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Staking makes it easier for individuals to participate in securing the network, promoting decentralization. validator node can be run on a normal laptop. Staking pools allow users to stake without having 32 ETH. | Proof-of-stake is younger and less battle-tested compared to proof-of-work |
| Staking is more decentralized. Economies of scale do not apply in the same way that they do for PoW mining. | Proof-of-stake is more complex to implement than proof-of-work |
-| Proof-of-stake offers greater crypto-economic security than proof-of-work | Users need to run three pieces of software to participate in Ethereum's proof-of-stake compared to one for proof-of-work. |
+| Proof-of-stake offers greater crypto-economic security than proof-of-work | Users need to run three pieces of software to participate in Ethereum's proof-of-stake. |
| Less issuance of new ether is required to incentivize network participants | |
## Further reading {#further-reading}
From 2391c780b2e68e9029f257f8dc1187eadcbb3907 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Mon, 6 Jun 2022 20:41:17 -0700
Subject: [PATCH 003/244] Update /upgrade/merge
first round of edits
---
src/content/upgrades/merge/index.md | 30 ++++++++++++++++-------------
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index e93a62e90b3..b7b0d212cb3 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -5,14 +5,16 @@ lang: en
template: upgrade
sidebar: true
image: ../../../assets/upgrades/merge.png
-summaryPoint1: Eventually the current Ethereum Mainnet will "merge" with the beacon chain proof-of-stake system.
+summaryPoint1: Soon the current Ethereum Mainnet will merge with the Beacon Chain proof-of-stake system.
summaryPoint2: This will mark the end of proof-of-work for Ethereum, and the full transition to proof-of-stake.
-summaryPoint3: This is planned to precede the roll out of shard chains.
-summaryPoint4: We formerly referred to this as "the docking."
+summaryPoint3: This sets the stage for future scaling upgrades including data sharding.
+summaryPoint4: With The Merge, Ethereum's eneregy consumption drops by 99.95%. Welcome a new greener Ethereum.
---
- This upgrade represents the official switch to proof-of-stake consensus. This eliminates the need for energy-intensive mining, and instead secures the network using staked ether. A truly exciting step in realizing the Ethereum vision – more scalability, security, and sustainability.
+The Merge is one of the most significant and high-stakes upgrades in the history of Ethereum. Extensive testing and bug bounties have been underway for years to make sure it’s done right, maximizing chances of a successful transition.
+
+This process is in its final stages, with plans to undergo The Merge on a few public testnets before finally moving forward with Mainnet. If you’re as excited about The Merge as we are, follow the EF Blog or the client communication channels for the latest official word on When Merge?
## What is The Merge? {#what-is-the-docking}
@@ -39,28 +41,30 @@ It is important to note that an implementation goal of The Merge is simplicity i
The Ethereum upgrades are all somewhat interrelated. So let’s recap how The Merge relates to the other upgrades.
-### The Merge and the Beacon Chain {#docking-and-beacon-chain}
+### The Merge and the Beacon Chain {#merge-and-beacon-chain}
+
+The Merge represents the formal adoption of the Beacon Chain as the new consensus layer to the current Mainnet execution layer. Once The Merge happens, validators will be assigned to secure Ethereum Mainnet and mining [proof-of-work](/developers/docs/consensus-mechanisms/pow/) will no longer be a valid means of block production.
-Once The Merge happens, stakers will be assigned to validate the Ethereum Mainnet. [Mining](/developers/docs/consensus-mechanisms/pow/mining/) will no longer be required so miners will likely invest their earnings into staking in the new proof-of-stake system.
+Blocks will instead be proposed by validating nodes that have ether staked for the right to participate in consensus. These upgrades set the stage for future scalability upgrades including data sharding.
The Beacon Chain
-### The Merge and the post-merge cleanup {#merge-and-post-merge-cleanup}
+### The Merge and the Shanghai upgrade {#merge-and-post-merge-cleanup}
-Immediately after The Merge, some features such as withdrawing staked ETH, will not yet be supported. These are planned for a separate upgrade to follow shortly after The Merge.
+In order to simplify and maximize focus on a successful transition to proof-of-stake, The Merge upgrade will not include certain anticipated features such as the ability to withdraw staked ETH. The Shanghai upgrade is planned to follow The Merge, in which the ability to withdraw is slotted as a top priority.
-Stay up-to-date with the [EF Research and Development Blog](https://blog.ethereum.org/category/research-and-development/). For those curious, learn more about [What Happens After The Merge](https://youtu.be/7ggwLccuN5s?t=101), presented by Vitalik at the April 2021 ETHGlobal event.
+Stay up-to-date with the [Shanghai Planning issue on GitHub](https://github.com/ethereum/pm/issues/450), or the [EF Research and Development Blog](https://blog.ethereum.org/category/research-and-development/). For those curious, learn more about [What Happens After The Merge](https://youtu.be/7ggwLccuN5s?t=101), presented by Vitalik at the April 2021 ETHGlobal event.
-### The Merge and shard chains {#docking-and-shard-chains}
+### The Merge and data sharding {#merge-and-data-sharding}
-Originally, the plan was to work on shard chains before The Merge – to address scalability. However, with the boom of [layer 2 scaling solutions](/developers/docs/scaling/#layer-2-scaling), the priority has shifted to swapping proof-of-work to proof-of-stake via The Merge.
+Originally, the plan was to work on shard chains before The Merge—to address scalability. However, with the boom of [layer 2 scaling solutions](/layer-2/), the priority has shifted to swapping proof-of-work to proof-of-stake via The Merge.
-This will be an ongoing assessment from the community as to the need for potentially multiple rounds of shard chains to allow for endless scalability.
+Plans for sharding are rapidly evolving, but given the rise and success of layer 2 technologies to scale transaction execution, sharding plans have shifted to finding the most optimal way to distribute the burden of storing compressed calldata from rollup contracts, allowing for exponential growth in network capacity. This would not be possible without first transitioning to proof-of-stake.
- Shard chains
+ Data sharding
## Read more {#read-more}
From 5e3be9d744120d593bb801f277d2500476295ce9 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Mon, 6 Jun 2022 23:21:27 -0700
Subject: [PATCH 004/244] Update MergeArticleList.js
---
src/components/MergeArticleList.js | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/src/components/MergeArticleList.js b/src/components/MergeArticleList.js
index f29b791eef5..e61f3dca6bf 100644
--- a/src/components/MergeArticleList.js
+++ b/src/components/MergeArticleList.js
@@ -19,9 +19,24 @@ const reads = [
link: "https://consensys.net/blog/news/the-state-of-the-merge-an-update-on-ethereums-merge-to-proof-of-stake-in-2022/",
},
{
- title: "Announcing the Kintsugi Merge Testnet",
+ title: "Announcing the Ropsten Merge Testnet",
description: "Ethereum Foundation",
- link: "https://blog.ethereum.org/2021/12/20/kintsugi-merge-testnet/",
+ link: "https://blog.ethereum.org/2022/05/30/ropsten-merge-announcement/",
+ },
+ {
+ title: "Execution layer specs",
+ description: "Ethereum Foundation",
+ link: "https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/merge.md",
+ },
+ {
+ title: "Consensus layer specs",
+ description: "Ethereum Foundation",
+ link: "https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix",
+ },
+ {
+ title: "Engine API specs",
+ description: "Ethereum Foundation",
+ link: "https://github.com/ethereum/execution-apis/tree/main/src/engine",
},
]
From 0d20fa9482e7db56c8fc18848d909c0660e75acd Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Mon, 6 Jun 2022 23:22:38 -0700
Subject: [PATCH 005/244] Update index.md
---
src/content/upgrades/merge/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index b7b0d212cb3..9e5a999ddf1 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -8,11 +8,11 @@ image: ../../../assets/upgrades/merge.png
summaryPoint1: Soon the current Ethereum Mainnet will merge with the Beacon Chain proof-of-stake system.
summaryPoint2: This will mark the end of proof-of-work for Ethereum, and the full transition to proof-of-stake.
summaryPoint3: This sets the stage for future scaling upgrades including data sharding.
-summaryPoint4: With The Merge, Ethereum's eneregy consumption drops by 99.95%. Welcome a new greener Ethereum.
+summaryPoint4: With The Merge, Ethereum's eneregy consumption drops by 99.95%. Welcome to a new greener Ethereum.
---
-The Merge is one of the most significant and high-stakes upgrades in the history of Ethereum. Extensive testing and bug bounties have been underway for years to make sure it’s done right, maximizing chances of a successful transition.
+The Merge is one of the most significant and high-stakes upgrades in the history of Ethereum. Extensive testing and bug bounties have been underway for years to ensure a safe transition to proof-of-stake.
This process is in its final stages, with plans to undergo The Merge on a few public testnets before finally moving forward with Mainnet. If you’re as excited about The Merge as we are, follow the EF Blog or the client communication channels for the latest official word on When Merge?
From cbc7b2e5970c1f3f0dfaaab821ba1d3f09e2b747 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Mon, 6 Jun 2022 23:28:07 -0700
Subject: [PATCH 006/244] Add persona breakdown
---
src/content/upgrades/merge/index.md | 64 +++++++++++++++++++++++++++++
1 file changed, 64 insertions(+)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 9e5a999ddf1..3389efd7c81 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -37,6 +37,70 @@ It is important to note that an implementation goal of The Merge is simplicity i
**This means a few features, such as the ability to withdraw staked ETH, will have to wait a little longer after The Merge is complete.** Plans include a post-merge "cleanup" upgrade to address these features, which is expected to happen very soon after The Merge is completed.
+## Who does this upgrade affect?
+
+The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term there are a few things the following groups of people should be aware of that we'll discuss below:
+
+- Node-operating solo stakers
+- Non-validating none operators
+- Dapp and smart contract developers
+
+For everyday users and holders there is nothing you need to do, but a few things you should be on alert for. [More on this below](#users-holders).
+
+## What to I need to do to get ready?
+
+### Node-operating solo stakers
+
+If you are a solo staker running your own node setup, there are a few things you need to be aware to be prepared for The Merge. Key action items include:
+
+- [ ] Running _both_ a consensus client as well as an execution client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
+- [ ] Authenticated your execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
+
+Not completing the above items will result in your node being seen as "offline" after The Merge until both layers are synced and authenticated.
+
+- [ ] Setting a `fee recipient` address to direct your earned transaction fee tips/MEV to.
+
+Not setting a `fee recipient` will still allow your validator to behave as usual, but you will miss out on unburnt fee tips and any MEV you would have otherwise earned in blocks your validator proposes.
+
+For more detailed information and summary of links to client resources, stakers are encouraged to check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) over on the Staking Launchpad to make sure you're fully prepared for The Merge.
+
+### Non-validating node operators
+
+If you're operating a non-validating Ethereum node, the most significant change that comes with The Merge is the requirement to run clients for _both_ the execution layer (EL) and the consensus layer (CL).
+
+You probably are already running an EL client, such as Geth, Erigon, Besu or Nethermind. Up until The Merge, an execution layer client was enough to receive, properly validate, and propagate blocks being gossiped by the network. _After The Merge_, the validity of transactions contained within an execution payload will also depend on the validity of the "consensus block" it is contained within.
+
+This means that a full Ethereum node after The Merge requires both an EL client as well as a CL client. These two clients work tightly together using a new Engine API to properly determine the latest state of the network. The Engine API requires authentication using a JWT secret, which is provided to both clients allowing secure communication.
+
+- [ ] I have installed a consensus layer client in addition to my execution layer client
+- [ ] I have authenticated me execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
+
+Not completing the above items in time for The Merge will result in your node appearing to be "offline" until both layers are synced and authenticated.
+Node operators can also check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) on the Staking Launchpad for more information, as much of the details apply to all node operators.
+
+### Dapp/smart contract developers
+
+The Merge has been designed to have minimal impact on smart contract and dapp developers, but there are a few small things devs may want to be aware of heading into The Merge. These changes relate to
+
+- block structure
+- slot/block timing
+- opcode changes
+- sources of on-chain randomness
+- concept of _safe head_ and _finalized blocks_
+
+For more information, check out this blog post by Tim Beiko on [How The Merge Impacts Ethereum’s Application Layer](https://blog.ethereum.org/2021/11/29/how-the-merge-impacts-app-layer/).
+
+### Users & hodlers {#users-holders}
+
+You do not need to anything to protect your funds entering The Merge.
+
+_This bears repeating_: As a user or holder of ETH or any other digital asset on Ethereum, **you do not need to do anything with your funds or wallet before The Merge.**
+
+Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds being protected by your own wallet before The Merge will still be accessible in the same manner after The Merge.
+
+As we approach The Merge of Ethereum Mainnet, **users should be on high alert for scams trying to take advantage of users during this transition.** Do not send your ETH anywhere in attempt to "upgrade to ETH2." There is no "ETH2" token, and there is nothing more you need to do for your funds to remain safe.
+
+[More on Ethereum security](/security/)
## Relationship between upgrades {#relationship-between-upgrades}
The Ethereum upgrades are all somewhat interrelated. So let’s recap how The Merge relates to the other upgrades.
From 784f40ab979e868ccb6fdc0279d68a8ac71e8e64 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Tue, 7 Jun 2022 13:02:38 -0700
Subject: [PATCH 007/244] Add misconceptions about The Merge
---
src/content/upgrades/merge/index.md | 67 ++++++++++++++++++++++++++++-
src/templates/upgrade.tsx | 2 +
2 files changed, 67 insertions(+), 2 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 3389efd7c81..2898fd5feac 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -96,11 +96,74 @@ You do not need to anything to protect your funds entering The Merge.
_This bears repeating_: As a user or holder of ETH or any other digital asset on Ethereum, **you do not need to do anything with your funds or wallet before The Merge.**
-Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds being protected by your own wallet before The Merge will still be accessible in the same manner after The Merge.
+Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds being protected by your own wallet before The Merge will still be accessible in the same manner after The Merge. No action is required to "upgrade" on your part.
-As we approach The Merge of Ethereum Mainnet, **users should be on high alert for scams trying to take advantage of users during this transition.** Do not send your ETH anywhere in attempt to "upgrade to ETH2." There is no "ETH2" token, and there is nothing more you need to do for your funds to remain safe.
+As we approach The Merge of Ethereum Mainnet, **you should be on high alert for scams trying to take advantage of users during this transition.** Do not send your ETH anywhere in attempt to "upgrade to ETH2." There is no "ETH2" token, and there is nothing more you need to do for your funds to remain safe.
[More on Ethereum security](/security/)
+
+## Misconceptions about The Merge {#misconceptions}
+
+
+Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
+
+With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698), efforts are being focused on scaling user activity at layer 2, while enabling layer 1 Mainnet as a secure decentralized settlement layer optimized for rollup data storage to help make rollup transactions exponentially cheaper. The transition to proof-of-stake is a critical precursor to realizing this.
+
+
+
+The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to finalization.
+
+
+
+Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
+
+Withdrawal functionality is planned for the Shanghai upgrade to follow The Merge. This means that newly issued ETH, though accumulating on the Beacon Chain, will remain locked and illiquid for at least 6-12 months following The Merge.
+
+
+
+After the _Shanghai_ update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, and depending on the APR and total ETH staked, they may also be incentivized to exit their validator(s) to reclaim their entire balance.
+
+An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH stake, and acts as a bottle neck to prevent a mass exodus of funds, or a potential attacker from committing a slashable offense and exiting all funds in the same epoch before the slashing penalty could be issued.
+
+The APR is intentionally dynamic, allowing a market of stakers to find a balance of how much they're willing to be paid to help secure the network. When withdrawals are enabled, if the rate is too low, then validators will exit, at a rate limited by the protocol. Gradually this will raise the rate of return for everyone who remains, slowly attracting new or returning stakers yet again.
+
+
+
+This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
+
+ETH is issued by the protocol as a reward to validators for contributing to consensus. This ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
+
+ETH on the execution layer, Mainnet as we know it, is accounted for separately from the consensus layer. When users execute transactions that involve Mainnet, ETH must be paid to cover the gas which includes a tip to the validator. This ETH is already on the execution layer, is NOT being issued by the protocol, and is available to the validator immediately (given a proper `eth1` address is provided to the client software).
+
+
+
+There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
+
+Nodes that can propose blocks are only a _subset_ of the total nodes on the network. This category includes mining nodes under proof-of-work (PoW), and validator nodes under proof-of-stake (PoS). This category requires committing economic resources (such as GPU hash power in PoW, or staked ETH in PoS), in exchange for the ability to occasionally propose the next block and earn protocol rewards.
+
+The _rest_ of the nodes on the network are not required to commit _any_ economic resources, beyond simply needing a consumer grade computer with 1-2 TB free storage and an internet connection. These nodes do not propose blocks, but still serve a _critical_ role in securing the network, by holding all block proposers accountable. These nodes listen for new blocks, and verify their validity on arrival according to the chosen rules of network consensus. If the block is valid, the node will continue propagating it through the network, but importantly, if the block is _invalid_ for whatever reason, the node software will simply disregard it as invalid.
+
+Running a non-block-producing node is not only _possible_ for anyone under either consensus mechanism (PoW _or_ PoS), it is _strongly encouraged_ for users to run their own node if possible. This is _immensely valuable_ for the network, and also gives added benefits to any individual running their own software, such as improved privacy and censorship resistance.
+
+The ability for anyone to run their own node is _absolutely essential_ to maintaining the decentralization of the Ethereum network.
+
+[More on running your own node](/run-a-node/)
+
+
+
## Relationship between upgrades {#relationship-between-upgrades}
The Ethereum upgrades are all somewhat interrelated. So let’s recap how The Merge relates to the other upgrades.
diff --git a/src/templates/upgrade.tsx b/src/templates/upgrade.tsx
index 2ec66190f45..0521b33edda 100644
--- a/src/templates/upgrade.tsx
+++ b/src/templates/upgrade.tsx
@@ -30,6 +30,7 @@ import UpgradeTableOfContents from "../components/UpgradeTableOfContents"
import Translation from "../components/Translation"
import TranslationsInProgress from "../components/TranslationsInProgress"
import SectionNav from "../components/SectionNav"
+import ExpandableCard from "../components/ExpandableCard"
import {
Divider,
Paragraph,
@@ -176,6 +177,7 @@ const components = {
ShardChainsList,
MergeArticleList,
YouTube,
+ ExpandableCard,
}
const Title = styled.h1`
From f8555c80e8c720777caffdf5bc160210016dab92 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Tue, 7 Jun 2022 19:21:27 -0700
Subject: [PATCH 008/244] copy tweaks
---
src/content/upgrades/merge/index.md | 24 +++++++++++++-----------
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 2898fd5feac..18f6f79f799 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -8,7 +8,7 @@ image: ../../../assets/upgrades/merge.png
summaryPoint1: Soon the current Ethereum Mainnet will merge with the Beacon Chain proof-of-stake system.
summaryPoint2: This will mark the end of proof-of-work for Ethereum, and the full transition to proof-of-stake.
summaryPoint3: This sets the stage for future scaling upgrades including data sharding.
-summaryPoint4: With The Merge, Ethereum's eneregy consumption drops by 99.95%. Welcome to a new greener Ethereum.
+summaryPoint4: With The Merge, Ethereum's energy consumption drops by 99.95%. Welcome to a new greener Ethereum.
---
@@ -49,22 +49,22 @@ For everyday users and holders there is nothing you need to do, but a few things
## What to I need to do to get ready?
-### Node-operating solo stakers
+### Node-operating stakers and staking providers
If you are a solo staker running your own node setup, there are a few things you need to be aware to be prepared for The Merge. Key action items include:
-- [ ] Running _both_ a consensus client as well as an execution client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
-- [ ] Authenticated your execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
+- Running _both_ a consensus client as well as an execution client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
+- Authenticated your execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
Not completing the above items will result in your node being seen as "offline" after The Merge until both layers are synced and authenticated.
-- [ ] Setting a `fee recipient` address to direct your earned transaction fee tips/MEV to.
+- Setting a `fee recipient` address to direct your earned transaction fee tips/MEV to.
Not setting a `fee recipient` will still allow your validator to behave as usual, but you will miss out on unburnt fee tips and any MEV you would have otherwise earned in blocks your validator proposes.
For more detailed information and summary of links to client resources, stakers are encouraged to check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) over on the Staking Launchpad to make sure you're fully prepared for The Merge.
-### Non-validating node operators
+### Non-validating node operators and infrastructure providers
If you're operating a non-validating Ethereum node, the most significant change that comes with The Merge is the requirement to run clients for _both_ the execution layer (EL) and the consensus layer (CL).
@@ -72,10 +72,11 @@ You probably are already running an EL client, such as Geth, Erigon, Besu or Net
This means that a full Ethereum node after The Merge requires both an EL client as well as a CL client. These two clients work tightly together using a new Engine API to properly determine the latest state of the network. The Engine API requires authentication using a JWT secret, which is provided to both clients allowing secure communication.
-- [ ] I have installed a consensus layer client in addition to my execution layer client
-- [ ] I have authenticated me execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
+- I have installed a consensus layer client in addition to my execution layer client
+- I have authenticated my execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
Not completing the above items in time for The Merge will result in your node appearing to be "offline" until both layers are synced and authenticated.
+
Node operators can also check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) on the Staking Launchpad for more information, as much of the details apply to all node operators.
### Dapp/smart contract developers
@@ -130,11 +131,12 @@ Withdrawal functionality is planned for the Shanghai upgrade to follow The Merge
-After the _Shanghai_ update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, and depending on the APR and total ETH staked, they may also be incentivized to exit their validator(s) to reclaim their entire balance.
-An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH stake, and acts as a bottle neck to prevent a mass exodus of funds, or a potential attacker from committing a slashable offense and exiting all funds in the same epoch before the slashing penalty could be issued.
+After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
+
+An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, or a potential attacker from committing a slashable offense and exiting all funds in the same epoch before the slashing penalty could be issued.
-The APR is intentionally dynamic, allowing a market of stakers to find a balance of how much they're willing to be paid to help secure the network. When withdrawals are enabled, if the rate is too low, then validators will exit, at a rate limited by the protocol. Gradually this will raise the rate of return for everyone who remains, slowly attracting new or returning stakers yet again.
+The APR is intentionally dynamic, allowing a market of stakers to find a balance of how much they're willing to be paid to help secure the network. When withdrawals are enabled, if the rate is too low, then validators will exit, at a rate limited by the protocol. Gradually this will raise the APR for everyone who remains, slowly attracting new or returning stakers yet again.
Date: Tue, 7 Jun 2022 19:57:48 -0700
Subject: [PATCH 009/244] Adds misconception copy
---
src/content/upgrades/merge/index.md | 25 ++++++++++++++++++++-----
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 18f6f79f799..a619b6e72fb 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -115,9 +115,14 @@ With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centri
-The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to finalization.
+contentPreview="Mostly false... Though some slight changes exist, transaction speed will mostly remain the same on layer 1">
+The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization."
+
+Historically with proof-of-work (PoW) block times target ~13.3 seconds. On the Beacon Chain, slots occur every 12 seconds exactly, each of which is an opportunity for a validator to publish a block. Most slots have blocks, but not all (ie. a validator is offline). In most cases, blocks will be produced ~10% more frequently under PoS than under PoW, but this is a fairly insignificant change in the scaling game, and unlikely to be a noticeable difference for the end user.
+
+PoS does introduce the concept of transaction "finality." Under PoW, the ability to reverse a block gets exponentially more difficult with every passing block that is mined on top of your transaction, but it never quite reaches zero. Under PoS, blocks are bundled into epochs (6.4 minute spans of time containing 32 chances for blocks) which are voted on by validators. After an epoch ends, it can be voted on as "justified," and then one more epoch later results in a "finalized" state. To undo these transactions would require obtaining and burning over 1/3 the total ETH staked.
+
+Many dapps require a number of PoW block confirmations that take a period of time on par with how long PoS finality takes. Finality can offer additional security guarantees, but will not significantly speed up transactions.
This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
@@ -150,7 +155,17 @@ ETH on the execution layer, Mainnet as we know it, is accounted for separately f
+The APR for stakers is expected to increase post-merge. It is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
+
+This will be a new separate source of revenue for validators when they propose blocks. As you can imagine, the amount of fees a validator receives is proportional to network activity at the time of their proposed block. The more fees being paid by users, the more fees validators will receive.
+
+Looking at recent blockchain activity, approximately 10% of all gas fees being paid are currently going to miners in the form of a tip, while the rest is burnt. Outdated predictions estimated this percentage to be much higher, and was calculated when network usage was at all time highs. Extrapolating the 10% number to average recent network activity, it is estimated that the APR for staking will increase to ~7%, approximately 50% higher than the base issuance APR at time of writing.
+
+
+
There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
From ad3fa69e8523db78e8878c8c1daba3875f3a2dc7 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Tue, 7 Jun 2022 20:43:19 -0700
Subject: [PATCH 010/244] update core copy of merge page
---
src/content/upgrades/merge/index.md | 32 +++++++++++++++++++++--------
1 file changed, 23 insertions(+), 9 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index a619b6e72fb..271dad8244e 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -19,23 +19,23 @@ This process is in its final stages, with plans to undergo The Merge on a few pu
## What is The Merge? {#what-is-the-docking}
-It's important to remember that initially, the [Beacon Chain](/upgrades/beacon-chain/) shipped separately from [Mainnet](/glossary/#mainnet) - the chain we use today. Ethereum Mainnet continues to be secured by [proof-of-work](/developers/docs/consensus-mechanisms/pow/), even while the Beacon Chain runs in parallel using [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). The Merge is when these two systems finally come together.
+The Merge represents the merger of the existing execution layer of Ethereum (the Mainnet we use today) with its new proof-of-stake consensus layer, the Beacon Chain.
-Imagine Ethereum is a space ship that isn’t quite ready for an interstellar voyage. With the Beacon Chain the community has built a new engine and a hardened hull. When it’s time, the current ship will dock with this new system, merging into one ship, ready to put in some serious lightyears and take on the universe.
+It's important to remember that initially, the [Beacon Chain](/upgrades/beacon-chain/) (the new "consensus layer") shipped separately from [Mainnet](/glossary/#mainnet). Ethereum Mainnet (the "execution layer") continues to be secured by [proof-of-work](/developers/docs/consensus-mechanisms/pow/), even while the Beacon Chain runs in parallel using [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). The approaching Merge is when these two systems finally come together, and proof-of-work is replaced permanently by proof-of-stake.
-## Merging with Mainnet {#docking-mainnet}
+Imagine Ethereum is a space ship that isn’t quite ready for an interstellar voyage. With the Beacon Chain the community has built a new engine and a hardened hull. After significant testing, it's almost time to hot-swap in the new engine for the old mid-flight. This will merge the new more efficient engine into the existing ship, ready to put in some serious lightyears and take on the universe.
-When ready, Ethereum Mainnet will "merge" with the Beacon Chain, becoming its own shard which uses proof-of-stake instead of [proof-of-work](/developers/docs/consensus-mechanisms/pow/).
+## Merging with Mainnet {#merging-with-mainnet}
-Mainnet will bring the ability to run smart contracts into the proof-of-stake system, plus the full history and current state of Ethereum, to ensure that the transition is smooth for all ETH holders and users.
+Since genesis, Mainnet has been secured by proof-of-work. This is the main Ethereum blockchain that we're all used to—it contains every transaction, every smart contract, and every balance since it began in July 2015.
-## After The Merge {#after-the-merge}
+During this growing history, developers have been hard at work preparing for an eventual transition away from proof-of-work, to proof-of-stake instead. On December 1, 2020 the Beacon Chain was born, which has since lived as a separate blockchain to Mainnet, running in parallel.
-This will signal the end of proof-of-work for Ethereum and start the era of a more sustainable, eco-friendly Ethereum. At this point Ethereum will be one step closer to achieving the full scale, security and sustainability outlined in its [Ethereum vision](/upgrades/vision/).
+The Beacon Chain has not been processing Mainnet transactions, and for all intents and purposed has simply been coming to consensus on the state of itself... which is great and all, but after extensive testing, the time for it to come to consensus on more than just itself is rapidly approaching.
-It is important to note that an implementation goal of The Merge is simplicity in order to expedite the transition from proof-of-work to proof-of-stake. Developers are focusing their efforts on this transition, and minimizing additional features that could delay this goal.
+The Merge itself represents the official switch to using the Beacon Chain as the official means of block production. Mining will no longer be the means of producing valid blocks, and instead this role will land with the validators who will then be responsible for processing the validity of all transactions.
-**This means a few features, such as the ability to withdraw staked ETH, will have to wait a little longer after The Merge is complete.** Plans include a post-merge "cleanup" upgrade to address these features, which is expected to happen very soon after The Merge is completed.
+No history is lost. As Mainnet is merged with the Beacon Chain, the entire transactional history of Ethereum comes with it. You don't need to do anything. Your funds are safe.
## Who does this upgrade affect?
@@ -181,6 +181,20 @@ The ability for anyone to run their own node is _absolutely essential_ to mainta
+
+An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
+
+The Merge is akin to changing an engine on a rocketship mid-flight, and is designed to be performed without any need to pause anything during the switch. The Merge will be triggered by what is known as a TTD, or [terminal total difficulty](/glossary/#terminal-total-difficult), which is a cumulative measure of the total mining power that has gone into building the chain. When the time comes, and this criteria is met, blocks will go from being produced using proof-of-work in one block, to being produced by proof-of-stake in the next.
+
+Ethereum does not go down.
+
+
+## After The Merge {#after-the-merge}
+
+This will signal the end of proof-of-work for Ethereum and start the era of a more sustainable, eco-friendly Ethereum. This will also set the stage for further scalability upgrades not possible under proof-of-work, bringing Ethereum one step closer to achieving the full scale, security and sustainability outlined in its [Ethereum vision](/upgrades/vision/).
+
## Relationship between upgrades {#relationship-between-upgrades}
The Ethereum upgrades are all somewhat interrelated. So let’s recap how The Merge relates to the other upgrades.
From f126fc38a0091ffbc45c287c157c0fd676511a6a Mon Sep 17 00:00:00 2001
From: Joseph Cook <33655003+jmcook1186@users.noreply.github.com>
Date: Wed, 8 Jun 2022 10:03:26 +0100
Subject: [PATCH 011/244] initial commit for pre-merge energy-consumption pg
---
src/content/energy-consumption/index.md | 64 +++++++------------------
1 file changed, 18 insertions(+), 46 deletions(-)
diff --git a/src/content/energy-consumption/index.md b/src/content/energy-consumption/index.md
index bc6f095d924..6734b0a8bca 100644
--- a/src/content/energy-consumption/index.md
+++ b/src/content/energy-consumption/index.md
@@ -7,61 +7,44 @@ sidebar: true
# Ethereum energy consumption {#introduction}
-Ethereum's current energy expenditure with [proof-of-work](/developers/docs/consensus-mechanisms/#proof-of-work) is too high and unsustainable. Resolving energy expenditure concerns without sacrificing security and decentralization is a significant technical challenge and has been a focus of research and development for years. Let's explore why building Ethereum has had a high environmental impact and how the upcoming network upgrade to [proof-of-stake](/developers/docs/consensus-mechanisms/pos) will dramatically change this.
+[The Merge](/upgrades/merge/index.md) from [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/#proof-of-work) to [proof-of-stake (PoS)](/developers/docs/consensus-mechanisms/pos) will reduce Ethereum's energy consumption by [~99.5%](https://blog.ethereum.org/2021/05/18/country-power-no-more/). After the Merge Ethereum will use dramatically less Carbon to be more secure.
-## Energy secures the network {#energy-secures-the-network}
-
-Transactions on the Ethereum blockchain are validated by [miners](/developers/docs/consensus-mechanisms/pow/mining). Miners bundle together transactions into ordered blocks and add them to the Ethereum blockchain. The new blocks get broadcast to all the other node operators who run the transactions independently and verify that they are valid. Any dishonesty shows up as an inconsistency between different nodes. Honest blocks are added to the blockchain and become an immutable part of history.
-
-The ability for any miner to add new blocks only works if there is a cost associated with mining and unpredictability about which specific node submits the next block. These conditions are met by imposing proof-of-work (PoW). To be eligible to submit a block of transactions, a miner must solve an arbitrary computational puzzle faster than any other miner. Solving this puzzle creates competition between miners and costs in the form of energy expenditure. To successfully defraud the blockchain, a dishonest miner would have to consistently win the proof-of-work race, which is very unlikely and prohibitively expensive.
-
-Ethereum has used proof-of-work since genesis. Migrating off of proof-of-work and onto proof-of-stake has always been a fundamental goal of Ethereum. However, developing a proof-of-stake system that adheres to Ethereum's core principles of security and decentralization is not trivial. It has required a lot of research and breakthroughs in cryptography, cryptoeconomics, and mechanism design to get to a point where the transition is possible.
-
-## Proof-of-work energy expenditure {#proof-of-work}
-
-Proof-of-work is a robust way to secure the network and enforce honest changes to the blockchain, but it is problematic for several reasons. Since the right to mine a block requires solving an arbitrary computational puzzle, miners can increase their odds of success by investing in more powerful hardware. These incentives cause an arms race with miners acquiring increasingly power-hungry mining equipment. Ethereum's proof-of-work protocol currently has a total annualized power consumption approximately equal to that of Finland [^1] and carbon footprint similar to Switzerland[^1].
-
-## Proof-of-stake {#proof-of-stake}
-
-A greener future for Ethereum is already being built in the form of a [**proof-of-stake (PoS)** chain](/upgrades/beacon-chain/). Under [proof-of-stake](/developers/docs/consensus-mechanisms/pos/), arbitrary puzzle-solving is unnecessary. Removing puzzle-solving drastically reduces the energy expenditure required to secure the network. Miners get replaced by validators who perform the same function except that instead of expending their assets up-front in the form of computational work, they stake ETH as collateral against dishonest behavior. If the validator is lazy (offline when they are supposed to fulfill some validator duty) their staked ETH can slowly leak away, while provably dishonest behavior results in the staked assets being "slashed". This strongly incentivizes active and honest participation in securing the network.
-
-Similarly to proof-of-work, a malicious entity would require at least 51% of the total ETH staked in the network to execute a [51% attack](/glossary/#51-attack). However, unlike on proof-of-work, where the potential loss of a failed attack is only the cost of generating the hash power needed to mine, on proof-of-stake, the possible loss of an attack is the entire amount of ETH used as collateral. This disincentive structure allows for network security with proof-of-stake while eliminating the need to expend energy on arbitrary computations. Detailed explanations of the network security under proof-of-stake can be found [here](/developers/docs/consensus-mechanisms/pos/) and [here](https://vitalik.ca/general/2017/12/31/pos_faq.html).
+Since inception, Ethereum has aimed to implement a PoS consensus mechanism, but doing this without sacrificing security and decentralization has taken years of focused research and development. Therefore, the network started by using PoW consensus. PoW consensus requires miners to use their computing hardware to solve puzzles. The solutions to these puzzles act as proof that some energy has been expended by the miner which in turn demonstrates that they have invested some real-world value for the right to add to the blockchain. Swapping this mechanism for PoS, where that real world value comes from ether staked directly in a smart contract, removes the need for miners to burn energy to add to the blockchain. Therefore, the environmental cost of securing the network is drastically reduced.
## The Merge {#the-merge}
-There is a functional proof-of-stake chain called the [Beacon Chain](/upgrades/beacon-chain/) that has been running since December 2020 that is demonstrating the viability of the proof-of-stake protocol. The Merge refers to the point in time when Ethereum leaves proof-of-work behind and fully adopts proof-of-stake. The Merge is expected to happen ~Q3/Q4 2022. [More on The Merge](/upgrades/merge/).
+A PoS blockchain known as the "Beacon Chain" has been running since November 2020 alongside the PoW Ethereum Mainnet. In 2022 several custom devnets have been merged with their own Beacon Chains to aid in debugging Ethereum clients in advance of the real merge. More recently, Ethereum developers have started merging public testnets (Kiln, Kintsugi, Ropsten) and shadow-forks (forks of Ethereum Mainnet) as the final stage of testing. Merging Ethereum Mainnet with the Beacon Chain is expected to happen in the second half of 2022. At the moment of the merge, Ethereum's PoW mining will be switched off, PoS consensus will take over, and the energy consumed by the network will drop to <0.05% of its pre-merge amount.
-## Proof-of-stake energy expenditure {#proof-of-stake-energy}
+## Why proof-of-stake is greener than proof-of-work {why-pos-is-greener-than-pow}
-As well as building confidence in the proof-of-stake mechanism, the Beacon Chain also enables estimates of Ethereum's post-merge energy usage. A [recent estimate](https://blog.ethereum.org/2021/05/18/country-power-no-more/) suggested that The Merge to proof-of-stake could result in a 99.95% reduction in total energy use, with proof-of-stake being ~2000x more energy-efficient than proof-of-work. The energy expenditure of Ethereum will be roughly equal to the cost of running a home computer for each node on the network.
+PoW is a robust way to secure the network. Transactions on the Ethereum blockchain are validated by [miners](/developers/docs/consensus-mechanisms/pow/mining). Miners bundle together transactions into ordered blocks and add them to the Ethereum blockchain. The new blocks get broadcast to all the other node operators who run the transactions independently and verify that they are valid. Any dishonesty shows up as an inconsistency between different nodes. Honest blocks are added to the blockchain and become an immutable part of history.
+The ability for any miner to add new blocks only works if there is a cost associated with mining and unpredictability about which specific node submits the next block. These conditions are met by imposing PoW. To be eligible to submit a block of transactions, a miner must be the first to submit the solution to a computationally expensive puzzle. To successfully take control of the blockchain, a dishonest miner would have to consistently win the PoW race by investing in sufficient hardware and energy to outperform the majority of other miners.
-![image](energy_use_per_transaction.png)
+This mechanism of securing the network is problematic for several reasons. Miners can increase their odds of success by investing in more and more powerful hardware, creatign conditions for an arms race with miners acquiring increasingly power-hungry mining equipment. This increases the network's energy consumption and generates hardware waste. Ethereum's PoW protocol currently has a total annualized power consumption approximately equal to that of Finland [^1] and carbon footprint similar to Switzerland[^1].
-
Estimate of PoW energy consumption per tx used in figure based on May 2021 data, at time of writing the same source suggested up to 175.56 Kwh
+PoS uses validators instead of miners. Validators perform the same function as miners except that instead of expending their assets up-front in the form of energy expenditure, they stake ETH as collateral against dishonest behavior. This staked ether cna be destroyed if the validator misbehaves, with more severe penalties for more nefarious actions. This strongly incentivizes active and honest participation in securing the network without requiring large energy expenditure. Since almost all of the energy expended securing the PoW network comes from the mining algorithm, switching to PoS reduces the energy expenditure dramatically. There is also no benefit to be had by investing in mroe powerful hardware under PoS, so there is no arms-race condition and less electronic waste. Ethereum validators can run on normal laptops or even low-power devices such as [Raspberry Pi](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/user-guide/ethereum2.0.html).
-Let's compare these numbers to a service such as Visa. 100,000 Visa transactions uses 149kWh of energy[^2]. Assuming sharding has been implemented, Ethereum's current transaction rate (15 transactions per second) will be increased by at least 64x (the number of shards), not accounting for additional optimization from rollups. A realistic estimate for post-merge, sharded Ethereum with rollups is [25,000 - 100,000](https://twitter.com/VitalikButerin/status/1312905884549300224?s=20) transactions per second. We can use this information to estimate maximum and minimum energy expenditure per 100,000 transactions.
+Read more detailed information about [how PoS is implemented in Ethereum](/developers/docs/consensus-mechanisms/pos) and how it compares to PoW.
-- 25,000 transactions per second.
-- `100,000 / 25,000 = 4` seconds to process 100,000 transactions.
+## Proof-of-stake energy expenditure {#proof-of-stake-energy}
-We can also estimate Ethereum's energy expenditure per second, making a conservative estimate that 10,000 active validators are securing the network (there are over [250,000 validators on the Beacon Chain](https://beaconscan.com/) at the moment, but many validators can operate on a single node. Currently, there are estimated to be 3,000-4,000 individual nodes, so 10,000 is a conservative estimate for post-merge):
+Estimates based on the current Beacon Chain suggest that the merge to PoS could result in a 99.95% reduction in total energy use, with PoS being ~2000x more energy-efficient than PoW. The energy expenditure of Ethereum will be roughly equal to the cost of running a modest laptop for each node on the network.
-`1.44kWh daily usage * 10,000 network nodes = 14,400kWh` per day.
-There are 86,400 seconds in a day, so `14,400 / 86,400 = 0.1667 kWh` per second.
+Many articles estimate "per-transaction" energy expenditure to compare blockchains to other industries. The benefit of this is that it is easy to understand, but the energy required to mine a block is independent of the number of transactions within it. A per transaction unit of energy expenditure implies that fewer transactions would lead to smaller energy expenditure, and vice-versa, which is not the case. A per-transaction estimate is highly dependent upon how a blockchain's transaction throughput is defined, and tweaking this definition can be gamed to make the value seem larger or smaller.
-If we multiply that by the amount of time it takes to process 100,000 transaction: `0.1667 * 4 = 0.667 kWh`.
+For example, for Ethereum the transaction throughput is not only that of the base layer - it is also the sum of the transaction throughput of all of its “layer 2” rollups, which are not generally included in calculations and would drastically reduce them. This is why tools that compare energy consumption per transaction across platforms are misleading.
-This is ~0.4% of the energy used by Visa for the same number of transactions, or a reduction in energy expenditure by a factor of ~225 compared to Ethereum's current proof-of-work network.
+More relevant is the overall energy consumption and carbon footprint of the network as a whole. From those values one can examine what that network offers to its users and to society at large and make a more holistic evaluation of whether that energy expenditure is justified or not. Per transaction measurements, on the other hand, imply the value of the network only comes from its role in transferring crypto between accounts and prohibit an honest cost-benefit analysis.
-Repeating the calculation with the maximum transactions-per-second yields 0.1667 kWh per second which is about 0.1% of the energy expenditure of Visa, or a reduction of ~894x.
+Whole-network energy consumption and carbon footprints for Bitcoin and Ethereum are estimated at [Digiconomist](https://digiconomist.net/ethereum-energy-consumption). At the time of writing this article Ethereum’s total energy consumption is ~112 TWh/yr, equivalent to that of the Netherlands, with a Carbon emission equivalent to that of Singapore (53 MT/yr). For comparison, Bitcoin currently expends about 200 TWh/yr energy and emits about 100 MT/yr C, while also generating about 32,000 T of electrical waste from obsolete hardware per year. Switching off Ethereum’s PoW in favor of PoS will reduce this energy expenditure by more than 99.95%, implying that the total energy expenditure for securing Ethereum is expected to be closer to **0.01 TW/yr**.
-_Note: it's not entirely accurate to compare based on number of transactions as Ethereum's energy usage is time-based. The energy usage of Ethereum is the same in 1 minute regardless if it does 1 or 1,000 transactions._
+To put this in context we can compare to annualized estimates for other industries. If we take Ethereum to be a platform for securely holding digital assets as investments we can compare to mining gold, which has been estimated to expend about [240 TWh/yr](https://www.kitco.com/news/2021-05-17/Gold-s-energy-consumption-doubles-that-of-bitcoin-Galaxy-Digital.html). As a digital payments platform we could perhaps compare to PayPal (about [0.26 TWh/yr](https://app.impaakt.com/analyses/paypal-consumed-264100-mwh-of-energy-in-2020-24-from-non-renewable-sources-27261)). As an entertainment platform we could perhaps compare it to the gaming industry which has been estimated to expend about [34 TW/yr](https://www.researchgate.net/publication/336909520_Toward_Greener_Gaming_Estimating_National_Energy_Use_and_Energy_Efficiency_Potential), or Netflix which expends about [94 TWh/yr](https://www.carbonbrief.org/factcheck-what-is-the-carbon-footprint-of-streaming-video-on-netflix), or Youtube which has been estimated to expend about [244 TWh/yr](https://thefactsource.com/how-much-electricity-does-youtube-use/). Estimates of Youtube’s energy expenditure have even been broken down by channel and even further by individual videos. [Those estimates](https://thefactsource.com/how-much-electricity-does-youtube-use/) imply that at least 400x more energy was expended watching Gangnam Style in 2019 than will be expended in a year of securing PoS Ethereum.
-_We must also consider that Ethereum isn't limited to simple financial transactions but is also a complete platform built for smart contracts and decentralized applications._
## A greener Ethereum {#green-ethereum}
-While Ethereum's energy consumption has historically been substantial, there has been a major investment of developer time and intellect into transitioning from energy-hungry to energy-efficient block validation. To quote [Bankless](http://podcast.banklesshq.com/), the best way to reduce the energy consumed by proof-of-work is simply to "turn it off", which is the approach Ethereum has committed to take.
+While Ethereum's energy consumption has historically been substantial, there has been a major investment of developer time and intellect into transitioning from energy-hungry to energy-efficient block production. To quote [Bankless](http://podcast.banklesshq.com/), the best way to reduce the energy consumed by PoW is simply to "turn it off", which is the approach Ethereum has committed to take. At the same time, there is a substantial, growing and highly active "ReFi" (Regenerative Finance) community building on Ethereum. ReFi refers to applications that use DeFi components to build financial applicatiosn that have positive externalities benfiting the environment. This is part of a wider "Solarpunk" movement that is closely aligned with Ethereum and aims to couple technological advancement and environmental stewardship. The decentralized, permissionless, composable nature of Ethereum makes it the ideal base layer for the ReFi and solarpunk communities. After the merge, the technology and philosophy of Ethereum will finally reconcile and Ethereum should become an overall environmentally-positive technology.
+
If you think these stats are incorrect or can be made more accurate, please raise an issue or PR. These are estimates by the ethereum.org team made using publicly accessible information and the current Ethereum roadmap. These statements don't represent an official promise from the Ethereum Foundation.
@@ -82,14 +65,3 @@ While Ethereum's energy consumption has historically been substantial, there has
- [The Merge](/upgrades/merge/)
- [Sharding](/upgrades/beacon-chain/)
-### Footnotes and sources {#footnotes-and-sources}
-
-#### 1. Ethereum proof-of-work energy consumption {#fn-1}
-
-[Energy Consumption by Country inc. Ethereum (Annualized TWh)](https://digiconomist.net/ethereum-energy-consumption)
-
-#### 2. Visa energy consumption {#fn-2}
-
-[Bitcoin network average energy consumption per transaction compared to VISA network as of 2020, Statista](https://www.statista.com/statistics/881541/bitcoin-energy-consumption-transaction-comparison-visa/)
-
-[Visa financials report Q4 2020](https://s1.q4cdn.com/050606653/files/doc_financials/2020/q4/Visa-Inc.-Q4-2020-Operational-Performance-Data.pdf)
From b382cbe0ffdb6e1aec4f73f093a4590a5307d392 Mon Sep 17 00:00:00 2001
From: Joe
Date: Wed, 8 Jun 2022 13:16:01 +0100
Subject: [PATCH 012/244] apply suggestions from review
---
src/content/energy-consumption/index.md | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/src/content/energy-consumption/index.md b/src/content/energy-consumption/index.md
index 6734b0a8bca..a4b802bc6b1 100644
--- a/src/content/energy-consumption/index.md
+++ b/src/content/energy-consumption/index.md
@@ -7,9 +7,9 @@ sidebar: true
# Ethereum energy consumption {#introduction}
-[The Merge](/upgrades/merge/index.md) from [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/#proof-of-work) to [proof-of-stake (PoS)](/developers/docs/consensus-mechanisms/pos) will reduce Ethereum's energy consumption by [~99.5%](https://blog.ethereum.org/2021/05/18/country-power-no-more/). After the Merge Ethereum will use dramatically less Carbon to be more secure.
+[The Merge](/upgrades/merge/index.md) from [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/#proof-of-work) to [proof-of-stake (PoS)](/developers/docs/consensus-mechanisms/pos) will reduce Ethereum's energy consumption by [~99.95%](https://blog.ethereum.org/2021/05/18/country-power-no-more/). After the Merge Ethereum will use dramatically less carbon to be more secure.
-Since inception, Ethereum has aimed to implement a PoS consensus mechanism, but doing this without sacrificing security and decentralization has taken years of focused research and development. Therefore, the network started by using PoW consensus. PoW consensus requires miners to use their computing hardware to solve puzzles. The solutions to these puzzles act as proof that some energy has been expended by the miner which in turn demonstrates that they have invested some real-world value for the right to add to the blockchain. Swapping this mechanism for PoS, where that real world value comes from ether staked directly in a smart contract, removes the need for miners to burn energy to add to the blockchain. Therefore, the environmental cost of securing the network is drastically reduced.
+Since inception, Ethereum has aimed to implement a PoS consensus mechanism, but doing this without sacrificing security and decentralization has taken years of focused research and development. Therefore, the network started by using PoW consensus. PoW consensus requires miners to use their computing hardware to solve a puzzle. The solution to this puzzle acts as proof that some energy has been expended by the miner which in turn demonstrates that they have invested some real-world value for the right to add to the blockchain. PoW is just a mechanism to decide who gets to add the next block, as is PoS. Swapping PoW for PoS, where the real world value invested comes from ether staked directly in a smart contract, removes the need for miners to burn energy to add to the blockchain. Therefore, the environmental cost of securing the network is drastically reduced.
## The Merge {#the-merge}
@@ -17,7 +17,7 @@ A PoS blockchain known as the "Beacon Chain" has been running since November 202
## Why proof-of-stake is greener than proof-of-work {why-pos-is-greener-than-pow}
-PoW is a robust way to secure the network. Transactions on the Ethereum blockchain are validated by [miners](/developers/docs/consensus-mechanisms/pow/mining). Miners bundle together transactions into ordered blocks and add them to the Ethereum blockchain. The new blocks get broadcast to all the other node operators who run the transactions independently and verify that they are valid. Any dishonesty shows up as an inconsistency between different nodes. Honest blocks are added to the blockchain and become an immutable part of history.
+PoW is a robust way to secure the network. Transactions on the Ethereum blockchain are validated by [miners](/developers/docs/consensus-mechanisms/pow/mining). Miners bundle together transactions into ordered blocks and add them to the Ethereum blockchain. The new blocks get broadcast to all the other node operators who run the transactions independently and verify that they are valid. Any dishonesty shows up as an inconsistency between different nodes. Honest blocks are added to the blockchain and become an immutable part of history.
The ability for any miner to add new blocks only works if there is a cost associated with mining and unpredictability about which specific node submits the next block. These conditions are met by imposing PoW. To be eligible to submit a block of transactions, a miner must be the first to submit the solution to a computationally expensive puzzle. To successfully take control of the blockchain, a dishonest miner would have to consistently win the PoW race by investing in sufficient hardware and energy to outperform the majority of other miners.
This mechanism of securing the network is problematic for several reasons. Miners can increase their odds of success by investing in more and more powerful hardware, creatign conditions for an arms race with miners acquiring increasingly power-hungry mining equipment. This increases the network's energy consumption and generates hardware waste. Ethereum's PoW protocol currently has a total annualized power consumption approximately equal to that of Finland [^1] and carbon footprint similar to Switzerland[^1].
@@ -36,16 +36,14 @@ For example, for Ethereum the transaction throughput is not only that of the bas
More relevant is the overall energy consumption and carbon footprint of the network as a whole. From those values one can examine what that network offers to its users and to society at large and make a more holistic evaluation of whether that energy expenditure is justified or not. Per transaction measurements, on the other hand, imply the value of the network only comes from its role in transferring crypto between accounts and prohibit an honest cost-benefit analysis.
-Whole-network energy consumption and carbon footprints for Bitcoin and Ethereum are estimated at [Digiconomist](https://digiconomist.net/ethereum-energy-consumption). At the time of writing this article Ethereum’s total energy consumption is ~112 TWh/yr, equivalent to that of the Netherlands, with a Carbon emission equivalent to that of Singapore (53 MT/yr). For comparison, Bitcoin currently expends about 200 TWh/yr energy and emits about 100 MT/yr C, while also generating about 32,000 T of electrical waste from obsolete hardware per year. Switching off Ethereum’s PoW in favor of PoS will reduce this energy expenditure by more than 99.95%, implying that the total energy expenditure for securing Ethereum is expected to be closer to **0.01 TW/yr**.
-
-To put this in context we can compare to annualized estimates for other industries. If we take Ethereum to be a platform for securely holding digital assets as investments we can compare to mining gold, which has been estimated to expend about [240 TWh/yr](https://www.kitco.com/news/2021-05-17/Gold-s-energy-consumption-doubles-that-of-bitcoin-Galaxy-Digital.html). As a digital payments platform we could perhaps compare to PayPal (about [0.26 TWh/yr](https://app.impaakt.com/analyses/paypal-consumed-264100-mwh-of-energy-in-2020-24-from-non-renewable-sources-27261)). As an entertainment platform we could perhaps compare it to the gaming industry which has been estimated to expend about [34 TW/yr](https://www.researchgate.net/publication/336909520_Toward_Greener_Gaming_Estimating_National_Energy_Use_and_Energy_Efficiency_Potential), or Netflix which expends about [94 TWh/yr](https://www.carbonbrief.org/factcheck-what-is-the-carbon-footprint-of-streaming-video-on-netflix), or Youtube which has been estimated to expend about [244 TWh/yr](https://thefactsource.com/how-much-electricity-does-youtube-use/). Estimates of Youtube’s energy expenditure have even been broken down by channel and even further by individual videos. [Those estimates](https://thefactsource.com/how-much-electricity-does-youtube-use/) imply that at least 400x more energy was expended watching Gangnam Style in 2019 than will be expended in a year of securing PoS Ethereum.
+Whole-network energy consumption and carbon footprints for Bitcoin and Ethereum are estimated at [Digiconomist](https://digiconomist.net/ethereum-energy-consumption). At the time of writing this article Ethereum’s total energy consumption is ~112 TWh/yr, equivalent to that of the Netherlands, with a Carbon emission equivalent to that of Singapore (53 MT/yr). For comparison, Bitcoin currently expends about 200 TWh/yr energy and emits about 100 MT/yr C, while also generating about 32,000 T of electrical waste from obsolete hardware per year. Switching off Ethereum’s PoW in favor of PoS will reduce this energy expenditure by more than 99.95%, implying that the total energy expenditure for securing Ethereum is expected to be closer to **0.01 TWh/yr**.
+To put this in context we can compare to annualized estimates for other industries. If we take Ethereum to be a platform for securely holding digital assets as investments, perhaps we can compare to mining gold, which has been estimated to expend about [240 TWh/yr](https://www.kitco.com/news/2021-05-17/Gold-s-energy-consumption-doubles-that-of-bitcoin-Galaxy-Digital.html). As a digital payments platform we could perhaps compare to PayPal (about [0.26 TWh/yr](https://app.impaakt.com/analyses/paypal-consumed-264100-mwh-of-energy-in-2020-24-from-non-renewable-sources-27261)). As an entertainment platform we could perhaps compare to the gaming industry which has been estimated to expend about [34 TW/yr](https://www.researchgate.net/publication/336909520_Toward_Greener_Gaming_Estimating_National_Energy_Use_and_Energy_Efficiency_Potential), or Netflix which expends about [94 TWh/yr](https://www.carbonbrief.org/factcheck-what-is-the-carbon-footprint-of-streaming-video-on-netflix), or Youtube which has been estimated to expend about [244 TWh/yr](https://thefactsource.com/how-much-electricity-does-youtube-use/). Estimates of Youtube’s energy expenditure have even been broken down by channel and even further by individual videos. [Those estimates](https://thefactsource.com/how-much-electricity-does-youtube-use/) imply that at least 45x more energy was expended watching Gangnam Style in 2019 than will be expended in a year of securing PoS Ethereum.
## A greener Ethereum {#green-ethereum}
While Ethereum's energy consumption has historically been substantial, there has been a major investment of developer time and intellect into transitioning from energy-hungry to energy-efficient block production. To quote [Bankless](http://podcast.banklesshq.com/), the best way to reduce the energy consumed by PoW is simply to "turn it off", which is the approach Ethereum has committed to take. At the same time, there is a substantial, growing and highly active "ReFi" (Regenerative Finance) community building on Ethereum. ReFi refers to applications that use DeFi components to build financial applicatiosn that have positive externalities benfiting the environment. This is part of a wider "Solarpunk" movement that is closely aligned with Ethereum and aims to couple technological advancement and environmental stewardship. The decentralized, permissionless, composable nature of Ethereum makes it the ideal base layer for the ReFi and solarpunk communities. After the merge, the technology and philosophy of Ethereum will finally reconcile and Ethereum should become an overall environmentally-positive technology.
-
If you think these stats are incorrect or can be made more accurate, please raise an issue or PR. These are estimates by the ethereum.org team made using publicly accessible information and the current Ethereum roadmap. These statements don't represent an official promise from the Ethereum Foundation.
@@ -64,4 +62,3 @@ While Ethereum's energy consumption has historically been substantial, there has
- [The Beacon Chain](/upgrades/beacon-chain)
- [The Merge](/upgrades/merge/)
- [Sharding](/upgrades/beacon-chain/)
-
From 2511d25a5d2428578c64370b42b008726d3043e6 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Wed, 8 Jun 2022 11:52:25 -0700
Subject: [PATCH 013/244] copy adjustments
---
src/content/upgrades/merge/index.md | 46 +++++++++++++++++------------
1 file changed, 27 insertions(+), 19 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 271dad8244e..2d688915a27 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -33,7 +33,7 @@ During this growing history, developers have been hard at work preparing for an
The Beacon Chain has not been processing Mainnet transactions, and for all intents and purposed has simply been coming to consensus on the state of itself... which is great and all, but after extensive testing, the time for it to come to consensus on more than just itself is rapidly approaching.
-The Merge itself represents the official switch to using the Beacon Chain as the official means of block production. Mining will no longer be the means of producing valid blocks, and instead this role will land with the validators who will then be responsible for processing the validity of all transactions.
+The Merge itself represents the official switch to using the Beacon Chain as the official means of block production. Mining will no longer be the means of producing valid blocks, and instead this role will land with the proof-of-stake validators who will then be responsible for processing the validity of all transactions, and proposing blocks.
No history is lost. As Mainnet is merged with the Beacon Chain, the entire transactional history of Ethereum comes with it. You don't need to do anything. Your funds are safe.
@@ -41,20 +41,22 @@ No history is lost. As Mainnet is merged with the Beacon Chain, the entire trans
The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term there are a few things the following groups of people should be aware of that we'll discuss below:
-- Node-operating solo stakers
-- Non-validating none operators
+- Node-operating stakers and staking providers
+- Non-validating node operators and infrastructure providers
- Dapp and smart contract developers
-For everyday users and holders there is nothing you need to do, but a few things you should be on alert for. [More on this below](#users-holders).
+For everyday users, holders, or non-node-operating stakers there is nothing you need to do, but a few things you should be on alert for. [More on this below](#users-holders).
## What to I need to do to get ready?
### Node-operating stakers and staking providers
-If you are a solo staker running your own node setup, there are a few things you need to be aware to be prepared for The Merge. Key action items include:
+If you are a staker running your own node setup, or a node infrastructure provider, there are a few things you need to be aware of to be prepared for The Merge.
-- Running _both_ a consensus client as well as an execution client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
-- Authenticated your execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
+Key action items include:
+
+- Running _both_ a consensus layer (CL) client as well as an execution layer (EL) client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
+- Authenticating both EL and CL clients with a shared JWT secret so they can securely communicate with one another.
Not completing the above items will result in your node being seen as "offline" after The Merge until both layers are synced and authenticated.
@@ -64,16 +66,20 @@ Not setting a `fee recipient` will still allow your validator to behave as usual
For more detailed information and summary of links to client resources, stakers are encouraged to check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) over on the Staking Launchpad to make sure you're fully prepared for The Merge.
+Note for stakers using [SaaS](/staking/saas/) or [staking pools](/staking/pools/): There is nothing you need to do to prepare for The Merge. [More below on staying safe](#users-holders).
+
### Non-validating node operators and infrastructure providers
-If you're operating a non-validating Ethereum node, the most significant change that comes with The Merge is the requirement to run clients for _both_ the execution layer (EL) and the consensus layer (CL).
+If you're operating a non-validating Ethereum node, the most significant change that comes with The Merge is the requirement to run clients for _both_ the execution layer (EL) _and_ the consensus layer (CL).
-You probably are already running an EL client, such as Geth, Erigon, Besu or Nethermind. Up until The Merge, an execution layer client was enough to receive, properly validate, and propagate blocks being gossiped by the network. _After The Merge_, the validity of transactions contained within an execution payload will also depend on the validity of the "consensus block" it is contained within.
+You probably are already running an EL client, such as Geth, Erigon, Besu or Nethermind. Up until The Merge, an EL client was enough to receive, properly validate, and propagate blocks being gossiped by the network. _After The Merge_, the validity of transactions contained within an execution payload will also depend on the validity of the "consensus block" it is contained within.
This means that a full Ethereum node after The Merge requires both an EL client as well as a CL client. These two clients work tightly together using a new Engine API to properly determine the latest state of the network. The Engine API requires authentication using a JWT secret, which is provided to both clients allowing secure communication.
-- I have installed a consensus layer client in addition to my execution layer client
-- I have authenticated my execution and consensus layer clients with a shared JWT secret so they can securely communicate with one another.
+Key action items include:
+
+- Installing a CL client in addition to an EL client
+- Authenticating both EL and CL clients with a shared JWT secret so they can securely communicate with one another.
Not completing the above items in time for The Merge will result in your node appearing to be "offline" until both layers are synced and authenticated.
@@ -115,12 +121,14 @@ With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centri
+contentPreview="Mostly false... Though some slight changes exist, transaction speed will mostly remain the same on layer 1.">
The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization."
+tl;dr: Both change slightly, but not in a way that will be felt significantly by the end user.
+
Historically with proof-of-work (PoW) block times target ~13.3 seconds. On the Beacon Chain, slots occur every 12 seconds exactly, each of which is an opportunity for a validator to publish a block. Most slots have blocks, but not all (ie. a validator is offline). In most cases, blocks will be produced ~10% more frequently under PoS than under PoW, but this is a fairly insignificant change in the scaling game, and unlikely to be a noticeable difference for the end user.
-PoS does introduce the concept of transaction "finality." Under PoW, the ability to reverse a block gets exponentially more difficult with every passing block that is mined on top of your transaction, but it never quite reaches zero. Under PoS, blocks are bundled into epochs (6.4 minute spans of time containing 32 chances for blocks) which are voted on by validators. After an epoch ends, it can be voted on as "justified," and then one more epoch later results in a "finalized" state. To undo these transactions would require obtaining and burning over 1/3 the total ETH staked.
+PoS does introduce the concept of transaction "finality" which did not previously exist. Under PoW, the ability to reverse a block gets exponentially more difficult with every passing block that is mined on top of your transaction, but it never quite reaches zero. Under PoS, blocks are bundled into epochs (6.4 minute spans of time containing 32 chances for blocks) which are voted on by validators. After an epoch ends, it can be voted on as "justified," and then one more epoch later results in a "finalized" state. To undo these transactions would require obtaining and burning over 1/3 the total ETH staked.
Many dapps require a number of PoW block confirmations that take a period of time on par with how long PoS finality takes. Finality can offer additional security guarantees, but will not significantly speed up transactions.
@@ -139,7 +147,7 @@ contentPreview="❌ False. Validator exits are rate limited for security reasons
After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
-An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, or a potential attacker from committing a slashable offense and exiting all funds in the same epoch before the slashing penalty could be issued.
+An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, and also prevents a potential attacker from using their stake to commit a slashable offense and then exiting their entire staking balance in the same epoch before the slashing penalty can be enforced.
The APR is intentionally dynamic, allowing a market of stakers to find a balance of how much they're willing to be paid to help secure the network. When withdrawals are enabled, if the rate is too low, then validators will exit, at a rate limited by the protocol. Gradually this will raise the APR for everyone who remains, slowly attracting new or returning stakers yet again.
@@ -149,15 +157,15 @@ title="'Validators will not receive any liquid ETH rewards until Shanghai when w
contentPreview="❌ False. Fee tips/MEV will be credited to a Mainnet account controlled by the validator, available immediately.">
This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
-ETH is issued by the protocol as a reward to validators for contributing to consensus. This ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
+ETH is issued by the protocol as a reward to validators for contributing to consensus. This _newly issued_ ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
-ETH on the execution layer, Mainnet as we know it, is accounted for separately from the consensus layer. When users execute transactions that involve Mainnet, ETH must be paid to cover the gas which includes a tip to the validator. This ETH is already on the execution layer, is NOT being issued by the protocol, and is available to the validator immediately (given a proper `eth1` address is provided to the client software).
+ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately from the consensus layer. When users execute transactions that involve Mainnet, ETH must be paid to cover the gas which includes a tip to the validator. This ETH is already on the execution layer, is NOT being newly issued by the protocol, and is available to the validator immediately (given a proper `fee recipient` address is provided to the client software).
-The APR for stakers is expected to increase post-merge. It is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
+The APR for stakers is expected to increase post-merge. To understand by how much, it is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
This will be a new separate source of revenue for validators when they propose blocks. As you can imagine, the amount of fees a validator receives is proportional to network activity at the time of their proposed block. The more fees being paid by users, the more fees validators will receive.
@@ -171,9 +179,9 @@ There are two general types of Ethereum nodes: nodes that can propose blocks, an
Nodes that can propose blocks are only a _subset_ of the total nodes on the network. This category includes mining nodes under proof-of-work (PoW), and validator nodes under proof-of-stake (PoS). This category requires committing economic resources (such as GPU hash power in PoW, or staked ETH in PoS), in exchange for the ability to occasionally propose the next block and earn protocol rewards.
-The _rest_ of the nodes on the network are not required to commit _any_ economic resources, beyond simply needing a consumer grade computer with 1-2 TB free storage and an internet connection. These nodes do not propose blocks, but still serve a _critical_ role in securing the network, by holding all block proposers accountable. These nodes listen for new blocks, and verify their validity on arrival according to the chosen rules of network consensus. If the block is valid, the node will continue propagating it through the network, but importantly, if the block is _invalid_ for whatever reason, the node software will simply disregard it as invalid.
+The _rest_ of the nodes on the network are not required to commit _any_ economic resources, beyond simply needing a consumer grade computer with 1-2 TB free storage and an internet connection. These nodes do not propose blocks, but still serve a _critical_ role in securing the network, by holding all block proposers accountable. These nodes listen for new blocks, and verify their validity on arrival according to the chosen rules of network consensus. If the block is valid, the node will continue propagating it through the network, but importantly, if the block is _invalid_ for whatever reason, the node software will simply disregard it as invalid, and stop its propagation.
-Running a non-block-producing node is not only _possible_ for anyone under either consensus mechanism (PoW _or_ PoS), it is _strongly encouraged_ for users to run their own node if possible. This is _immensely valuable_ for the network, and also gives added benefits to any individual running their own software, such as improved privacy and censorship resistance.
+Running a "non block-producing" node is not only _possible_ for anyone under either consensus mechanism (PoW _or_ PoS), it is _strongly encouraged_ for all users to run their own node if possible. This is _immensely valuable_ for the network, and also gives added benefits to any individual running their own software, such as improved security, privacy and censorship resistance.
The ability for anyone to run their own node is _absolutely essential_ to maintaining the decentralization of the Ethereum network.
From 49ba9930588c7f5927ac5d95f4cf3dd31ddec381 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Wed, 8 Jun 2022 12:24:21 -0700
Subject: [PATCH 014/244] header linking
---
src/content/upgrades/merge/index.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 2d688915a27..7257d864830 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -37,19 +37,19 @@ The Merge itself represents the official switch to using the Beacon Chain as the
No history is lost. As Mainnet is merged with the Beacon Chain, the entire transactional history of Ethereum comes with it. You don't need to do anything. Your funds are safe.
-## Who does this upgrade affect?
+## Who does this upgrade affect? {#who-does-the-merge-affect}
The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term there are a few things the following groups of people should be aware of that we'll discuss below:
-- Node-operating stakers and staking providers
-- Non-validating node operators and infrastructure providers
-- Dapp and smart contract developers
+- [Node-operating stakers and staking providers](#node-operating-stakers)
+- [Non-validating node operators and infrastructure providers](#node-operators)
+- [Dapp and smart contract developers](#developers)
For everyday users, holders, or non-node-operating stakers there is nothing you need to do, but a few things you should be on alert for. [More on this below](#users-holders).
-## What to I need to do to get ready?
+## What to I need to do to get ready? {#preparing-for-the-merge}
-### Node-operating stakers and staking providers
+### Node-operating stakers and staking providers {#node-operating-stakers}
If you are a staker running your own node setup, or a node infrastructure provider, there are a few things you need to be aware of to be prepared for The Merge.
@@ -68,7 +68,7 @@ For more detailed information and summary of links to client resources, stakers
Note for stakers using [SaaS](/staking/saas/) or [staking pools](/staking/pools/): There is nothing you need to do to prepare for The Merge. [More below on staying safe](#users-holders).
-### Non-validating node operators and infrastructure providers
+### Non-validating node operators and infrastructure providers {#node-operators}
If you're operating a non-validating Ethereum node, the most significant change that comes with The Merge is the requirement to run clients for _both_ the execution layer (EL) _and_ the consensus layer (CL).
@@ -85,7 +85,7 @@ Not completing the above items in time for The Merge will result in your node ap
Node operators can also check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) on the Staking Launchpad for more information, as much of the details apply to all node operators.
-### Dapp/smart contract developers
+### Dapp/smart contract developers {#developers}
The Merge has been designed to have minimal impact on smart contract and dapp developers, but there are a few small things devs may want to be aware of heading into The Merge. These changes relate to
@@ -196,7 +196,7 @@ An immense amount of work has been put into making sure the transition to proof-
The Merge is akin to changing an engine on a rocketship mid-flight, and is designed to be performed without any need to pause anything during the switch. The Merge will be triggered by what is known as a TTD, or [terminal total difficulty](/glossary/#terminal-total-difficult), which is a cumulative measure of the total mining power that has gone into building the chain. When the time comes, and this criteria is met, blocks will go from being produced using proof-of-work in one block, to being produced by proof-of-stake in the next.
-Ethereum does not go down.
+Ethereum does not have downtime.
## After The Merge {#after-the-merge}
@@ -217,7 +217,7 @@ Blocks will instead be proposed by validating nodes that have ether staked for t
The Beacon Chain
-### The Merge and the Shanghai upgrade {#merge-and-post-merge-cleanup}
+### The Merge and the Shanghai upgrade {#merge-and-shanghai}
In order to simplify and maximize focus on a successful transition to proof-of-stake, The Merge upgrade will not include certain anticipated features such as the ability to withdraw staked ETH. The Shanghai upgrade is planned to follow The Merge, in which the ability to withdraw is slotted as a top priority.
From 1b14b63d30577661c833d6649391f52a83fb0875 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Wed, 8 Jun 2022 21:11:34 -0700
Subject: [PATCH 015/244] copy updates
---
src/content/upgrades/merge/index.md | 101 +++++++++++++++-------------
1 file changed, 56 insertions(+), 45 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 7257d864830..9b5d3672e41 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -41,19 +41,20 @@ No history is lost. As Mainnet is merged with the Beacon Chain, the entire trans
The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term there are a few things the following groups of people should be aware of that we'll discuss below:
-- [Node-operating stakers and staking providers](#node-operating-stakers)
-- [Non-validating node operators and infrastructure providers](#node-operators)
+- [Staking node operators and providers](#staking-node-operators)
+- [Non-staking node operators and infrastructure providers](#node-operators)
- [Dapp and smart contract developers](#developers)
-For everyday users, holders, or non-node-operating stakers there is nothing you need to do, but a few things you should be on alert for. [More on this below](#users-holders).
+For everyday users, holders, or non-node-operating stakers there is nothing you need to do, but a few things you should be on alert for. [More on this below.](#users-holders)
## What to I need to do to get ready? {#preparing-for-the-merge}
-### Node-operating stakers and staking providers {#node-operating-stakers}
-
-If you are a staker running your own node setup, or a node infrastructure provider, there are a few things you need to be aware of to be prepared for The Merge.
+ Key action items include:
- Running _both_ a consensus layer (CL) client as well as an execution layer (EL) client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
- Authenticating both EL and CL clients with a shared JWT secret so they can securely communicate with one another.
@@ -66,12 +67,13 @@ Not setting a `fee recipient` will still allow your validator to behave as usual
For more detailed information and summary of links to client resources, stakers are encouraged to check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) over on the Staking Launchpad to make sure you're fully prepared for The Merge.
-Note for stakers using [SaaS](/staking/saas/) or [staking pools](/staking/pools/): There is nothing you need to do to prepare for The Merge. [More below on staying safe](#users-holders).
-
-### Non-validating node operators and infrastructure providers {#node-operators}
-
-If you're operating a non-validating Ethereum node, the most significant change that comes with The Merge is the requirement to run clients for _both_ the execution layer (EL) _and_ the consensus layer (CL).
+Note for stakers using [SaaS](/staking/saas/) or [staking pools](/staking/pools/): There is nothing you need to do to prepare for The Merge. [More below on staying safe.](#users-holders)
+
+
You probably are already running an EL client, such as Geth, Erigon, Besu or Nethermind. Up until The Merge, an EL client was enough to receive, properly validate, and propagate blocks being gossiped by the network. _After The Merge_, the validity of transactions contained within an execution payload will also depend on the validity of the "consensus block" it is contained within.
This means that a full Ethereum node after The Merge requires both an EL client as well as a CL client. These two clients work tightly together using a new Engine API to properly determine the latest state of the network. The Engine API requires authentication using a JWT secret, which is provided to both clients allowing secure communication.
@@ -84,10 +86,13 @@ Key action items include:
Not completing the above items in time for The Merge will result in your node appearing to be "offline" until both layers are synced and authenticated.
Node operators can also check out the [Merge Readiness Checklist](https://launchpad.ethereum.org/en/merge-readiness/) on the Staking Launchpad for more information, as much of the details apply to all node operators.
+
-### Dapp/smart contract developers {#developers}
-
-The Merge has been designed to have minimal impact on smart contract and dapp developers, but there are a few small things devs may want to be aware of heading into The Merge. These changes relate to
+
+These changes relate to
- block structure
- slot/block timing
@@ -96,37 +101,40 @@ The Merge has been designed to have minimal impact on smart contract and dapp de
- concept of _safe head_ and _finalized blocks_
For more information, check out this blog post by Tim Beiko on [How The Merge Impacts Ethereum’s Application Layer](https://blog.ethereum.org/2021/11/29/how-the-merge-impacts-app-layer/).
+
-### Users & hodlers {#users-holders}
-
-You do not need to anything to protect your funds entering The Merge.
+This bears repeating: As a user or holder of ETH or any other digital asset on Ethereum, you do not need to do anything with your funds or wallet before The Merge.
Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds being protected by your own wallet before The Merge will still be accessible in the same manner after The Merge. No action is required to "upgrade" on your part.
As we approach The Merge of Ethereum Mainnet, **you should be on high alert for scams trying to take advantage of users during this transition.** Do not send your ETH anywhere in attempt to "upgrade to ETH2." There is no "ETH2" token, and there is nothing more you need to do for your funds to remain safe.
[More on Ethereum security](/security/)
+
## Misconceptions about The Merge {#misconceptions}
-Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
+title=""The Merge will reduce gas fees.""
+contentPreview="False. The Merge is a change of consensus mechanism, not an expansion of network capacity, and will not result in lower gas fees."
+
+> Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698), efforts are being focused on scaling user activity at layer 2, while enabling layer 1 Mainnet as a secure decentralized settlement layer optimized for rollup data storage to help make rollup transactions exponentially cheaper. The transition to proof-of-stake is a critical precursor to realizing this.
-The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization."
+title=""Transactions will be noticably faster after The Merge""
+contentPreview="False. Though some slight changes exist, transaction speed will mostly remain the same on layer 1."
-tl;dr: Both change slightly, but not in a way that will be felt significantly by the end user.
+> The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization." Both of these change slightly, but not in a way that will be felt significantly by users.
-Historically with proof-of-work (PoW) block times target ~13.3 seconds. On the Beacon Chain, slots occur every 12 seconds exactly, each of which is an opportunity for a validator to publish a block. Most slots have blocks, but not all (ie. a validator is offline). In most cases, blocks will be produced ~10% more frequently under PoS than under PoW, but this is a fairly insignificant change in the scaling game, and unlikely to be a noticeable difference for the end user.
+Historically with proof-of-work (PoW) block times target ~13.3 seconds. On the Beacon Chain, slots occur every 12 seconds exactly, each of which is an opportunity for a validator to publish a block. Most slots have blocks, but not necessarily all (ie. a validator is offline). In most cases, blocks will be produced ~10% more frequently under PoS than under PoW, but this is a fairly insignificant change in the scaling game, and unlikely to be noticed by users.
PoS does introduce the concept of transaction "finality" which did not previously exist. Under PoW, the ability to reverse a block gets exponentially more difficult with every passing block that is mined on top of your transaction, but it never quite reaches zero. Under PoS, blocks are bundled into epochs (6.4 minute spans of time containing 32 chances for blocks) which are voted on by validators. After an epoch ends, it can be voted on as "justified," and then one more epoch later results in a "finalized" state. To undo these transactions would require obtaining and burning over 1/3 the total ETH staked.
@@ -134,18 +142,19 @@ Many dapps require a number of PoW block confirmations that take a period of tim
-Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
+title=""You can withdraw staked ETH once The Merge occurs.""
+contentPreview="False. Staking withdrawals are not yet enabled with The Merge."
+
+> Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
Withdrawal functionality is planned for the Shanghai upgrade to follow The Merge. This means that newly issued ETH, though accumulating on the Beacon Chain, will remain locked and illiquid for at least 6-12 months following The Merge.
+title=""When withdrawals are enabled, stakers will all exit at once.""
+contentPreview="False. Validator exits are rate limited for security reasons."
-After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
+> After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, and also prevents a potential attacker from using their stake to commit a slashable offense and then exiting their entire staking balance in the same epoch before the slashing penalty can be enforced.
@@ -153,9 +162,10 @@ The APR is intentionally dynamic, allowing a market of stakers to find a balance
-This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
+title=""Validators will not receive any liquid ETH rewards until Shanghai when withdrawals are enabled.""
+contentPreview="False. Fee tips/MEV will be credited to a Mainnet account controlled by the validator, available immediately."
+
+> This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
ETH is issued by the protocol as a reward to validators for contributing to consensus. This _newly issued_ ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
@@ -163,8 +173,8 @@ ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately
+title=""Staking APR is expected to triple after The Merge. ""
+contentPreview="False. More up-to-date estimations predict closer to a 50% increase in APR post-merge, not a 200% increase.">
The APR for stakers is expected to increase post-merge. To understand by how much, it is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
This will be a new separate source of revenue for validators when they propose blocks. As you can imagine, the amount of fees a validator receives is proportional to network activity at the time of their proposed block. The more fees being paid by users, the more fees validators will receive.
@@ -173,9 +183,10 @@ Looking at recent blockchain activity, approximately 10% of all gas fees being p
-There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
+title=""Running a node requires staking 32 ETH.""
+contentPreview="False. Anyone is free to sync their own self-verified copy of Ethereum, aka run a node. No ETH required—not before The Merge, not after The Merge, not ever."
+
+> There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
Nodes that can propose blocks are only a _subset_ of the total nodes on the network. This category includes mining nodes under proof-of-work (PoW), and validator nodes under proof-of-stake (PoS). This category requires committing economic resources (such as GPU hash power in PoW, or staked ETH in PoS), in exchange for the ability to occasionally propose the next block and earn protocol rewards.
@@ -186,13 +197,13 @@ Running a "non block-producing" node is not only _possible_ for anyone under eit
The ability for anyone to run their own node is _absolutely essential_ to maintaining the decentralization of the Ethereum network.
[More on running your own node](/run-a-node/)
-
-An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
+title=""The Merge will result in downtime of the chain.""
+contentPreview="False. The Merge upgrade is designed to transition to proof-of-stake with zero downtime."
+
+> An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
The Merge is akin to changing an engine on a rocketship mid-flight, and is designed to be performed without any need to pause anything during the switch. The Merge will be triggered by what is known as a TTD, or [terminal total difficulty](/glossary/#terminal-total-difficult), which is a cumulative measure of the total mining power that has gone into building the chain. When the time comes, and this criteria is met, blocks will go from being produced using proof-of-work in one block, to being produced by proof-of-stake in the next.
From 6d6a886a1acddbf1c215edc22c153177df2e66b8 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Wed, 8 Jun 2022 21:18:48 -0700
Subject: [PATCH 016/244] linting
---
src/content/upgrades/merge/index.md | 45 ++++++++++++-----------------
1 file changed, 18 insertions(+), 27 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 9b5d3672e41..00f634b24df 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -52,9 +52,8 @@ For everyday users, holders, or non-node-operating stakers there is nothing you
Key action items include:
+id="staking-node-operators">
+Key action items include:
- Running _both_ a consensus layer (CL) client as well as an execution layer (EL) client. Third-party endpoints to obtain execution data will be unavailable after The Merge.
- Authenticating both EL and CL clients with a shared JWT secret so they can securely communicate with one another.
@@ -106,9 +105,8 @@ For more information, check out this blog post by Tim Beiko on [How The Merge Im
This bears repeating: As a user or holder of ETH or any other digital asset on Ethereum, you do not need to do anything with your funds or wallet before The Merge.
+id="users-holders">
+This bears repeating: As a user or holder of ETH or any other digital asset on Ethereum, you do not need to do anything with your funds or wallet before The Merge.
Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds being protected by your own wallet before The Merge will still be accessible in the same manner after The Merge. No action is required to "upgrade" on your part.
@@ -121,18 +119,16 @@ As we approach The Merge of Ethereum Mainnet, **you should be on high alert for
Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
+contentPreview="False. The Merge is a change of consensus mechanism, not an expansion of network capacity, and will not result in lower gas fees.">
+Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698), efforts are being focused on scaling user activity at layer 2, while enabling layer 1 Mainnet as a secure decentralized settlement layer optimized for rollup data storage to help make rollup transactions exponentially cheaper. The transition to proof-of-stake is a critical precursor to realizing this.
The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization." Both of these change slightly, but not in a way that will be felt significantly by users.
+contentPreview="False. Though some slight changes exist, transaction speed will mostly remain the same on layer 1.">
+The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization." Both of these change slightly, but not in a way that will be felt significantly by users.
Historically with proof-of-work (PoW) block times target ~13.3 seconds. On the Beacon Chain, slots occur every 12 seconds exactly, each of which is an opportunity for a validator to publish a block. Most slots have blocks, but not necessarily all (ie. a validator is offline). In most cases, blocks will be produced ~10% more frequently under PoS than under PoW, but this is a fairly insignificant change in the scaling game, and unlikely to be noticed by users.
@@ -143,18 +139,16 @@ Many dapps require a number of PoW block confirmations that take a period of tim
Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
+contentPreview="False. Staking withdrawals are not yet enabled with The Merge.">
+Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
Withdrawal functionality is planned for the Shanghai upgrade to follow The Merge. This means that newly issued ETH, though accumulating on the Beacon Chain, will remain locked and illiquid for at least 6-12 months following The Merge.
After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
+contentPreview="False. Validator exits are rate limited for security reasons.">
+After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, and also prevents a potential attacker from using their stake to commit a slashable offense and then exiting their entire staking balance in the same epoch before the slashing penalty can be enforced.
@@ -163,9 +157,8 @@ The APR is intentionally dynamic, allowing a market of stakers to find a balance
This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
+contentPreview="False. Fee tips/MEV will be credited to a Mainnet account controlled by the validator, available immediately.">
+This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
ETH is issued by the protocol as a reward to validators for contributing to consensus. This _newly issued_ ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
@@ -184,9 +177,8 @@ Looking at recent blockchain activity, approximately 10% of all gas fees being p
There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
+contentPreview="False. Anyone is free to sync their own self-verified copy of Ethereum, aka run a node. No ETH required—not before The Merge, not after The Merge, not ever.">
+There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
Nodes that can propose blocks are only a _subset_ of the total nodes on the network. This category includes mining nodes under proof-of-work (PoW), and validator nodes under proof-of-stake (PoS). This category requires committing economic resources (such as GPU hash power in PoW, or staked ETH in PoS), in exchange for the ability to occasionally propose the next block and earn protocol rewards.
@@ -201,9 +193,8 @@ The ability for anyone to run their own node is _absolutely essential_ to mainta
An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
+contentPreview="False. The Merge upgrade is designed to transition to proof-of-stake with zero downtime.">
+An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
The Merge is akin to changing an engine on a rocketship mid-flight, and is designed to be performed without any need to pause anything during the switch. The Merge will be triggered by what is known as a TTD, or [terminal total difficulty](/glossary/#terminal-total-difficult), which is a cumulative measure of the total mining power that has gone into building the chain. When the time comes, and this criteria is met, blocks will go from being produced using proof-of-work in one block, to being produced by proof-of-stake in the next.
From 3156d8367626e64064d69950f77a468b2303df69 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 10:08:54 -0700
Subject: [PATCH 017/244] design/layout updates
---
src/content/upgrades/merge/index.md | 81 +++++++++++++----------------
1 file changed, 37 insertions(+), 44 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 00f634b24df..734fb33e313 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -37,17 +37,11 @@ The Merge itself represents the official switch to using the Beacon Chain as the
No history is lost. As Mainnet is merged with the Beacon Chain, the entire transactional history of Ethereum comes with it. You don't need to do anything. Your funds are safe.
-## Who does this upgrade affect? {#who-does-the-merge-affect}
-
-The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term there are a few things the following groups of people should be aware of that we'll discuss below:
-
-- [Staking node operators and providers](#staking-node-operators)
-- [Non-staking node operators and infrastructure providers](#node-operators)
-- [Dapp and smart contract developers](#developers)
+## What to I need to do to get ready? {#preparing-for-the-merge}
-For everyday users, holders, or non-node-operating stakers there is nothing you need to do, but a few things you should be on alert for. [More on this below.](#users-holders)
+The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term some folks will need to take action to be fully prepared.
-## What to I need to do to get ready? {#preparing-for-the-merge}
+For everyday users, holders, or non-node-operating stakers there is **nothing you need to do**, but a few things you should be aware of heading into The Merge. [More on this below.](#users-holders)
For more information, check out this blog post by Tim Beiko on [How The Merge Impacts Ethereum’s Application Layer](https://blog.ethereum.org/2021/11/29/how-the-merge-impacts-app-layer/).
-
+### Users and holders {#users-holders}
+
+You do not need to anything to protect your funds entering The Merge.
+
This bears repeating: As a user or holder of ETH or any other digital asset on Ethereum, you do not need to do anything with your funds or wallet before The Merge.
Despite swapping out proof-of-work, the entire history of Ethereum since genesis remains intact and unaltered after the transition to proof-of-stake. Any funds being protected by your own wallet before The Merge will still be accessible in the same manner after The Merge. No action is required to "upgrade" on your part.
As we approach The Merge of Ethereum Mainnet, **you should be on high alert for scams trying to take advantage of users during this transition.** Do not send your ETH anywhere in attempt to "upgrade to ETH2." There is no "ETH2" token, and there is nothing more you need to do for your funds to remain safe.
-[More on Ethereum security](/security/)
-
+[More on Ethereum security](/security/#eth2-token-scam)
+
+## After The Merge {#after-the-merge}
+
+This will signal the end of proof-of-work for Ethereum and start the era of a more sustainable, eco-friendly Ethereum. This will also set the stage for further scalability upgrades not possible under proof-of-work, bringing Ethereum one step closer to achieving the full scale, security and sustainability outlined in its [Ethereum vision](/upgrades/vision/).
## Misconceptions about The Merge {#misconceptions}
+There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
+
+Nodes that can propose blocks are only a _subset_ of the total nodes on the network. This category includes mining nodes under proof-of-work (PoW), and validator nodes under proof-of-stake (PoS). This category requires committing economic resources (such as GPU hash power in PoW, or staked ETH in PoS), in exchange for the ability to occasionally propose the next block and earn protocol rewards.
+
+The _rest_ of the nodes on the network are not required to commit _any_ economic resources, beyond simply needing a consumer grade computer with 1-2 TB free storage and an internet connection. These nodes do not propose blocks, but still serve a _critical_ role in securing the network, by holding all block proposers accountable. These nodes listen for new blocks, and verify their validity on arrival according to the chosen rules of network consensus. If the block is valid, the node will continue propagating it through the network, but importantly, if the block is _invalid_ for whatever reason, the node software will simply disregard it as invalid, and stop its propagation.
+
+Running a "non block-producing" node is not only _possible_ for anyone under either consensus mechanism (PoW _or_ PoS), it is _strongly encouraged_ for all users to run their own node if possible. This is _immensely valuable_ for the network, and also gives added benefits to any individual running their own software, such as improved security, privacy and censorship resistance.
+
+The ability for anyone to run their own node is _absolutely essential_ to maintaining the decentralization of the Ethereum network.
+
+[More on running your own node](/run-a-node/)
+
+
+
Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
@@ -126,7 +139,7 @@ With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centri
The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization." Both of these change slightly, but not in a way that will be felt significantly by users.
@@ -138,7 +151,7 @@ Many dapps require a number of PoW block confirmations that take a period of tim
Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
@@ -146,9 +159,9 @@ Withdrawal functionality is planned for the Shanghai upgrade to follow The Merge
-After the Shanghai update enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
+After the Shanghai upgrade enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, and also prevents a potential attacker from using their stake to commit a slashable offense and then exiting their entire staking balance in the same epoch before the slashing penalty can be enforced.
@@ -156,7 +169,7 @@ The APR is intentionally dynamic, allowing a market of stakers to find a balance
This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
@@ -166,7 +179,7 @@ ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately
The APR for stakers is expected to increase post-merge. To understand by how much, it is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
@@ -176,23 +189,7 @@ Looking at recent blockchain activity, approximately 10% of all gas fees being p
-There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
-
-Nodes that can propose blocks are only a _subset_ of the total nodes on the network. This category includes mining nodes under proof-of-work (PoW), and validator nodes under proof-of-stake (PoS). This category requires committing economic resources (such as GPU hash power in PoW, or staked ETH in PoS), in exchange for the ability to occasionally propose the next block and earn protocol rewards.
-
-The _rest_ of the nodes on the network are not required to commit _any_ economic resources, beyond simply needing a consumer grade computer with 1-2 TB free storage and an internet connection. These nodes do not propose blocks, but still serve a _critical_ role in securing the network, by holding all block proposers accountable. These nodes listen for new blocks, and verify their validity on arrival according to the chosen rules of network consensus. If the block is valid, the node will continue propagating it through the network, but importantly, if the block is _invalid_ for whatever reason, the node software will simply disregard it as invalid, and stop its propagation.
-
-Running a "non block-producing" node is not only _possible_ for anyone under either consensus mechanism (PoW _or_ PoS), it is _strongly encouraged_ for all users to run their own node if possible. This is _immensely valuable_ for the network, and also gives added benefits to any individual running their own software, such as improved security, privacy and censorship resistance.
-
-The ability for anyone to run their own node is _absolutely essential_ to maintaining the decentralization of the Ethereum network.
-
-[More on running your own node](/run-a-node/)
-
-
-
An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
@@ -201,10 +198,6 @@ The Merge is akin to changing an engine on a rocketship mid-flight, and is desig
Ethereum does not have downtime.
-## After The Merge {#after-the-merge}
-
-This will signal the end of proof-of-work for Ethereum and start the era of a more sustainable, eco-friendly Ethereum. This will also set the stage for further scalability upgrades not possible under proof-of-work, bringing Ethereum one step closer to achieving the full scale, security and sustainability outlined in its [Ethereum vision](/upgrades/vision/).
-
## Relationship between upgrades {#relationship-between-upgrades}
The Ethereum upgrades are all somewhat interrelated. So let’s recap how The Merge relates to the other upgrades.
@@ -223,7 +216,7 @@ Blocks will instead be proposed by validating nodes that have ether staked for t
In order to simplify and maximize focus on a successful transition to proof-of-stake, The Merge upgrade will not include certain anticipated features such as the ability to withdraw staked ETH. The Shanghai upgrade is planned to follow The Merge, in which the ability to withdraw is slotted as a top priority.
-Stay up-to-date with the [Shanghai Planning issue on GitHub](https://github.com/ethereum/pm/issues/450), or the [EF Research and Development Blog](https://blog.ethereum.org/category/research-and-development/). For those curious, learn more about [What Happens After The Merge](https://youtu.be/7ggwLccuN5s?t=101), presented by Vitalik at the April 2021 ETHGlobal event.
+Stay up-to-date with the [Shanghai upgrade planning issue on GitHub](https://github.com/ethereum/pm/issues/450), or the [EF Research and Development Blog](https://blog.ethereum.org/category/research-and-development/). For those curious, learn more about [What Happens After The Merge](https://youtu.be/7ggwLccuN5s?t=101), presented by Vitalik at the April 2021 ETHGlobal event.
### The Merge and data sharding {#merge-and-data-sharding}
From 2a8edec0be125653218d0c8e5217146234c2d3c9 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Thu, 9 Jun 2022 12:16:03 -0600
Subject: [PATCH 018/244] wallet listing policy
---
.../contributing/adding-wallet/index.md | 72 +++++++++++++++++++
src/content/contributing/index.md | 1 +
2 files changed, 73 insertions(+)
create mode 100644 src/content/contributing/adding-wallet/index.md
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
new file mode 100644
index 00000000000..afc8de81617
--- /dev/null
+++ b/src/content/contributing/adding-wallet/index.md
@@ -0,0 +1,72 @@
+---
+title: Adding wallets
+description: The policy we use when adding a wallet to ethereum.org
+lang: en
+sidebar: true
+---
+
+# Adding wallets {#adding-wallets}
+
+We want to make sure we show a variety of wallets covering the feature rich landscape of wallets so that users can navigate Ethereum in a confident manner.
+
+Anyone is free to suggest adding a wallet on ethereum.org. If there's a wallet that we have missed, please suggest it!
+
+Anyone is free to suggest a new wallet. Wallets are currently listed on:
+
+- [ethereum.org/wallets/find-wallet](/wallets/find-wallet/)
+
+Wallets are rapidly changing in Ethereum. We've tried to create a fair framework for consideration on ethereum.org but the listing criteria will change and evolve over time.
+
+## The decision framework {#the-decision-framework}
+
+### Criteria for inclusion: the must-haves {#the-must-haves}
+
+- **A security-tested product** - whether through audit, an internal security team, open sourced coded, or some other method, your wallets security must be reliable. This reduces the risk to our users and shows us that you take security seriously.
+- **A wallet that has been “live” for over 6 months OR released by a group with a reputable track record** - this is another indication of security. 6 months is a good time frame for critical bugs and exploitations to have been found. We ask 6 months to help filter our forks that are quickly abandoned as projects.
+- **Worked on by an active team** - this helps to ensure quality and that a user will get support for their queries.
+- **Honest and accurate listing information** - it is expected that any suggesting listings from projects come with honest and accurate information. Products that falsify listing information, such as declaring your product is “open source” when it is not, will be removed.
+- **Point of contact** - A point of contact for the wallet will greatly help us get accurate information when changes are made. This will keep updating ethereum.org manageable when gathering future information.
+
+### Other criteria: the nice-to-haves {#the-nice-to-haves}
+
+- **Globally accessible** - your wallet doesn’t have geographic limitations or KYC requirements that exclude certain people from accessing your service.
+- **Available in multiple languages** - your wallet is translated into multiple languages allowing users around the world to access it.
+- **Open source** - your whole project’s codebase (not just modules) should be accessible and you should accept PR’s from the wider community.
+- **Non-custodial** - users control their funds. If your product disappears, users can still access and move their funds.
+- **Hardware wallet support** - users can connect their hardware wallet to sign transactions.
+- **WalletConnect** - users can connect to dapps using WalletConnect.
+- **Importing Ethereum RPC endpoints** - users can import node RPC data, allowing them to connect to a node of their choice, or other EVM compatible networks.
+- **NFTs** - users are able to view and interact with their NFT’s in the wallet.
+- **Connect to Ethereum applications** - users are able to connect to and use Ethereum applications.
+- **Staking** - users are able to stake directly through the wallet.
+- **Swaps** - users are able to swap tokens through the wallet.
+- **Multichain networks** - your wallet supports users accessing multiple blockchain networks by default.
+- **Customize gas fees** - your wallet allows users to customize their transaction gas fees (base fee, priority fee, max fee)
+- **ENS support** - your wallet allows users to send transactions to ENS names.
+- **ERC-20 support** - your wallet allows users to import ERC-20 token contracts, or automatically queries and displays ERC-20 tokens.
+- **EIP-1559 (type 2) transactions** - your wallet supports EIP-1559 (type 2) transactions.
+- **Buy crypto** - your wallet supports users directly purchasing and onboarding to crypto.
+- **Withdraw crypto** - your wallet supports users withdrawing directly to card or a bank account.
+- **Multisig** - your wallet supports multiple signatures to sign a transaction.
+- **Social recovery** - your wallet supports guardians and a user can recover their wallet if they lose their seed phrase using these guardians.
+- **Dedicated support team** - your wallet has a dedicated support team where users can go to when experiencing issues.
+- **Educational resources/documentation** - your product should have a well-designed onboarding experience to help and educate users. Or evidence of how-to content like articles or videos.
+
+## Adding a wallet {#adding-a-wallet}
+
+If you want to add a wallet to ethereum.org, create an issue on GitHub.
+
+
+ Create an issue
+
+
+## Maintenance {#maintenance}
+
+As is the fluid nature of Ethereum, teams and products come and go and innovation happens daily, so we'll undertake routine checks of our content to:
+
+- ensure that all wallets and dapps listed still fulfil our criteria
+- verify there aren't products that have been suggested that meet more of our criteria than the ones currently listed
+
+## Terms of use {#terms-of-use}
+
+Please also refer to our [terms of use](/terms-of-use/). Information on ethereum.org is provided solely for general information purposes.
diff --git a/src/content/contributing/index.md b/src/content/contributing/index.md
index ad483c20eb8..21d8c999e05 100644
--- a/src/content/contributing/index.md
+++ b/src/content/contributing/index.md
@@ -39,6 +39,7 @@ The ethereum.org website, like Ethereum more broadly, is an open-source project.
- [Add a layer 2](/contributing/adding-layer-2)
_- Add a layer 2 to a relevant page_
- [Add a staking product or service](/contributing/adding-staking-product/) - _Add a project that helps facilitate solo staking, pooled staking, or staking as a service_
+- [Add a wallet](/contributing/adding-wallet/) _- Add a wallet for the [find wallets page](/wallets/find-wallet/)._
_Any questions?_ 🤔 Reach out on our [Discord server](https://discord.gg/CetY6Y4)
From 6de89fad886cdae4673c0fb945ca08d411747825 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 12:22:03 -0700
Subject: [PATCH 019/244] Add /eth-issuance page
---
.../upgrades/merge/eth-issuance/index.md | 102 ++++++++++++++++++
1 file changed, 102 insertions(+)
create mode 100644 src/content/upgrades/merge/eth-issuance/index.md
diff --git a/src/content/upgrades/merge/eth-issuance/index.md b/src/content/upgrades/merge/eth-issuance/index.md
new file mode 100644
index 00000000000..9abc3737bb0
--- /dev/null
+++ b/src/content/upgrades/merge/eth-issuance/index.md
@@ -0,0 +1,102 @@
+---
+title: How will The Merge impact ether supply?
+description: Discussion on how The Merge will impact ether supply
+lang: en
+sidebar: true
+---
+
+# How The Merge impacts ether supply
+
+
+
+- Mining rewards ~13,000 ETH/day pre-merge
+- Staking rewards ~1,600 ETH/day pre-merge
+- **After The Merge, only the ~1,600 ETH per day will remain, dropping total new ETH issuance by ~90%**
+- The burn: At an average gas price of at least 16 gwei, at least 1,600 ETH is burned every day, which effectively brings net ETH inflation to zero or less post-merge.
+
+
+
+We can break the supply of ETH into two primary forces: issuance, and burn.
+
+The **issuance** of ETH is the process of creating ETH that did not previously exist on the balance sheet, while the **burning** of ETH refers to when existing ETH is permanently removed from circulation. The rate of each of these fluctuates based on a number of parameters, and the balance between them determines the resulting inflation/deflation rate of ether.
+
+The way ETH is issued will undergo some changes at time of The Merge. Currently, new ETH is issued from two main sources: the execution layer (EL, i.e. Mainnet) and the consensus layer (CL, i.e. Beacon Chain). After The Merge, issuance from the execution layer will go to zero. Let's break this down.
+
+## Pre-merge:
+
+### EL Issuance
+
+Under proof-of-work, miners only interact with the EL, and are rewarded in the form of block rewards being the first to solve blocks. Since the [Constantinople upgrade](/history/#constantinople) on Feb-28-2019 this reward has been 2 ETH per block. Miners are also rewarded for publishing [ommer](/glossary/#ommer) blocks, which are valid blocks that don't end up in the longest/canonical chain. These rewards max out at 1.75 ETH per ommer, and are _in addition to_ the reward issued from the canonical block. Mining is an economically intensive activity, which requires high levels of ETH issuance to sustain.
+
+### CL Issuance
+
+The [Beacon Chain](/history/#beacon-chain-genesis) has been live since Dec-01-2020, which is secured by proof-of-stake validators, not miners. This chain was bootstrapped by Ethereum users depositing ETH one-way into a smart contract on Mainnet, which the Beacon Chain listens to, crediting the user with an equal amount on the new chain. Right now these validators are not processing transactions, and are essentially coming to consensus on the state of the validator pool itself.
+
+Issuance of new ETH on this chain is rewarded to validators for properly attesting to the state of the chain, and is also rewarded when a validator proposes a block. Rewards (or penalties) are calculated and distributed every epoch (6.4 minutes) based on validator performance for that time period. These rewards are _significantly_ lower than the 2 ETH being issued under proof-of-work today every ~13.5 seconds, as operating a validating node is not an economically intense activity, thus does not require or warrant as high a reward.
+
+### Pre-merge issuance breakdown
+
+Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
+
+
+
+**EL issuance:**
+
+- Estimating at 2.08 ETH per 13.3 seconds\*: **~4,930,000** ETH issued in a year
+- Currently inflating at **~4.13%** (4.93M per year / 119.3M total)
+- \*This includes the 2 ETH per canonical block, plus an average of 0.08 ETH over time from ommer blocks. Also uses 13.3 second, the baseline block time target without any influence from a [difficulty bomb](/glossary/#difficulty-bomb). ([See source](https://bitinfocharts.com/ethereum/))
+
+**CL issuance:**
+
+- Using 13,000,000 total ETH staked, the rate of ETH issuance is ~1600 ETH/day ([SeeSource](https://ultrasound.money/))
+- Results in **~584,000** ETH issued in a year
+- Currently inflating at **~0.49%** (584K per year / 119.3M total)
+
+
+Total annual issuance rate: ~4.62% (4.13% + 0.49%)
+
+**~89.4%** of the issuance is going to miners on the EL (4.13 / 4.62 \* 100)
+
+**~10.6%** is being issued to stakers on the CL (0.49 / 4.62 \* 100)
+
+
+## Post-merge
+
+### EL Issuance
+
+Will be zero. Proof-of-work will no longer be valid under the rules of consensus, and all EL activity will be included in "beacon blocks" which are published and attested to by proof-of-stake validators.
+
+### CL Issuance
+
+Will continue as it was, with small rewards for attesting-to and proposing blocks. These rewards will continue to accrue to _validator balances_ that are managed within the consensus layer. These are separate Ethereum accounts to the accounts we're used to on Mainnet, and until the Shanghai upgrade funds from validator accounts will not be withdrawable/transferrable. This means that although new ETH is still being issued, 100% of it will be locked from the market until this upgrade occurs. When the Shanghai upgrade is rolled out, this ETH will become available.
+
+When validator withdrawals are enabled, stakers will be incentivized to remove their _earnings/rewards (balance over 32)_ as these funds are otherwise not contributing to their stake weight (which maxes as 32).
+
+Stakers may also choose to exit and withdrawal their entire validator balance, but it is important to remember that full validator exits are rate limited. Depending on the total ETH staked at the time, only 6 validators may exit in a given epoch (6.4 minute period). This decreases to as low as 4 as more validators leave, to intentionally prevent the ability for large amounts of staked ETH to leave at once.
+
+### Post-merge inflation breakdown
+
+- Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
+- EL issuance: **0**
+- CL issuance: Same as above, **~0.49%** annual issuance rate (with 13 million ETH staked)
+- Total annual issuance rate: **~0.49%**
+
+
+Total annual issuance rate: ~0.49%
+Net reduction in annual ETH issuance: ~89.4% (0.49% / 4.62% * 100)
+
+
+## The burn
+
+This flip side of ETH issuance is the rate at which ETH is burned. To execute a transaction on Ethereum, a minimum fee (known as a `base fee`) must be paid, which fluctuates depending on network activity in the moment. This fee is paid in ETH, is _required_ for the transaction to be considered valid, and is _burned_ in the process, removing it from circulation.
+
+
+This went live with the London upgrade Aug-4-2021, and will not change after the Merge.
+
+
+On top of the fee burn implemented by the London upgrade, validators can also incur penalties for being offline, or worse they can be slashed for breaking specific rules that threaten network security. These penalties result in a reduction of ETH from that validators balance, which is not directly rewarded to any other account, effectively burning it from circulation.
+
+## Further reading {#further-reading}
+
+- [Ultrasound.money](https://ultrasound.money/) - Dashboards available to visualize ETH issuance and burn in real time
From 465303b7fd60fef28bed0aee2433a7bd814990ce Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 12:22:20 -0700
Subject: [PATCH 020/244] Update /upgrades/merge
---
src/content/upgrades/merge/index.md | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index 734fb33e313..c27e121b45a 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -14,7 +14,7 @@ summaryPoint4: With The Merge, Ethereum's energy consumption drops by 99.95%. We
The Merge is one of the most significant and high-stakes upgrades in the history of Ethereum. Extensive testing and bug bounties have been underway for years to ensure a safe transition to proof-of-stake.
-This process is in its final stages, with plans to undergo The Merge on a few public testnets before finally moving forward with Mainnet. If you’re as excited about The Merge as we are, follow the EF Blog or the client communication channels for the latest official word on When Merge?
+This process is in its final stages, with plans to undergo The Merge on a few public testnets before finally moving forward with Mainnet. If you’re as excited about The Merge as we are, follow the [EF Blog](https://blog.ethereum.org) or the client communication channels for the latest official word on _When Merge?_
## What is The Merge? {#what-is-the-docking}
@@ -37,6 +37,10 @@ The Merge itself represents the official switch to using the Beacon Chain as the
No history is lost. As Mainnet is merged with the Beacon Chain, the entire transactional history of Ethereum comes with it. You don't need to do anything. Your funds are safe.
+
+This transition to proof-of-stake will come with some changes to the way ether is supplied. Learn more about ether issuance before and after The Merge.
+
+
## What to I need to do to get ready? {#preparing-for-the-merge}
The Merge is one of the most significant and anticipated upgrades in the history of Ethereum, and although in the long-term its impact will be felt by everyone, in the near-term some folks will need to take action to be fully prepared.
@@ -110,7 +114,9 @@ As we approach The Merge of Ethereum Mainnet, **you should be on high alert for
## After The Merge {#after-the-merge}
-This will signal the end of proof-of-work for Ethereum and start the era of a more sustainable, eco-friendly Ethereum. This will also set the stage for further scalability upgrades not possible under proof-of-work, bringing Ethereum one step closer to achieving the full scale, security and sustainability outlined in its [Ethereum vision](/upgrades/vision/).
+This will signal the end of proof-of-work for Ethereum and start the era of a more sustainable, eco-friendly Ethereum. Learn more about [Ethereum energy consumption](/energy-consumption/).
+
+This will also set the stage for further scalability upgrades not possible under proof-of-work, bringing Ethereum one step closer to achieving the full scale, security and sustainability outlined in its [Ethereum vision](/upgrades/vision/).
## Misconceptions about The Merge {#misconceptions}
@@ -128,6 +134,7 @@ Running a "non block-producing" node is not only _possible_ for anyone under eit
The ability for anyone to run their own node is _absolutely essential_ to maintaining the decentralization of the Ethereum network.
[More on running your own node](/run-a-node/)
+
-## Read more {#read-more}
+## Further reading {#further-reading}
From 00f66aaeb77ce16169226bc0bca1105bd1b695c0 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 12:33:00 -0700
Subject: [PATCH 021/244] metadata/header link fixes
---
.../upgrades/merge/eth-issuance/index.md | 24 +++++++++----------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/content/upgrades/merge/eth-issuance/index.md b/src/content/upgrades/merge/eth-issuance/index.md
index 9abc3737bb0..8d4ff9e9d89 100644
--- a/src/content/upgrades/merge/eth-issuance/index.md
+++ b/src/content/upgrades/merge/eth-issuance/index.md
@@ -1,11 +1,11 @@
---
-title: How will The Merge impact ether supply?
-description: Discussion on how The Merge will impact ether supply
+title: How The Merge impacts ether supply
+description: Breakdown on how The Merge will impact ether supply
lang: en
sidebar: true
---
-# How The Merge impacts ether supply
+# How The Merge impacts ether supply {#how-the-merge-impacts-ether-supply}
@@ -23,19 +23,19 @@ The **issuance** of ETH is the process of creating ETH that did not previously e
The way ETH is issued will undergo some changes at time of The Merge. Currently, new ETH is issued from two main sources: the execution layer (EL, i.e. Mainnet) and the consensus layer (CL, i.e. Beacon Chain). After The Merge, issuance from the execution layer will go to zero. Let's break this down.
-## Pre-merge:
+## Pre-merge {#pre-merge}
-### EL Issuance
+### EL Issuance {#el-issuance-pre-merge}
Under proof-of-work, miners only interact with the EL, and are rewarded in the form of block rewards being the first to solve blocks. Since the [Constantinople upgrade](/history/#constantinople) on Feb-28-2019 this reward has been 2 ETH per block. Miners are also rewarded for publishing [ommer](/glossary/#ommer) blocks, which are valid blocks that don't end up in the longest/canonical chain. These rewards max out at 1.75 ETH per ommer, and are _in addition to_ the reward issued from the canonical block. Mining is an economically intensive activity, which requires high levels of ETH issuance to sustain.
-### CL Issuance
+### CL Issuance {#cl-issuance-pre-merge}
The [Beacon Chain](/history/#beacon-chain-genesis) has been live since Dec-01-2020, which is secured by proof-of-stake validators, not miners. This chain was bootstrapped by Ethereum users depositing ETH one-way into a smart contract on Mainnet, which the Beacon Chain listens to, crediting the user with an equal amount on the new chain. Right now these validators are not processing transactions, and are essentially coming to consensus on the state of the validator pool itself.
Issuance of new ETH on this chain is rewarded to validators for properly attesting to the state of the chain, and is also rewarded when a validator proposes a block. Rewards (or penalties) are calculated and distributed every epoch (6.4 minutes) based on validator performance for that time period. These rewards are _significantly_ lower than the 2 ETH being issued under proof-of-work today every ~13.5 seconds, as operating a validating node is not an economically intense activity, thus does not require or warrant as high a reward.
-### Pre-merge issuance breakdown
+### Pre-merge issuance breakdown {#pre-merge-issuance-breakdown}
Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
@@ -61,13 +61,13 @@ Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
**~10.6%** is being issued to stakers on the CL (0.49 / 4.62 \* 100)
-## Post-merge
+## Post-merge {#post-merge}
-### EL Issuance
+### EL Issuance {#el-issuance-post-merge}
Will be zero. Proof-of-work will no longer be valid under the rules of consensus, and all EL activity will be included in "beacon blocks" which are published and attested to by proof-of-stake validators.
-### CL Issuance
+### CL Issuance {#cl-issuance-post-merge}
Will continue as it was, with small rewards for attesting-to and proposing blocks. These rewards will continue to accrue to _validator balances_ that are managed within the consensus layer. These are separate Ethereum accounts to the accounts we're used to on Mainnet, and until the Shanghai upgrade funds from validator accounts will not be withdrawable/transferrable. This means that although new ETH is still being issued, 100% of it will be locked from the market until this upgrade occurs. When the Shanghai upgrade is rolled out, this ETH will become available.
@@ -75,7 +75,7 @@ When validator withdrawals are enabled, stakers will be incentivized to remove t
Stakers may also choose to exit and withdrawal their entire validator balance, but it is important to remember that full validator exits are rate limited. Depending on the total ETH staked at the time, only 6 validators may exit in a given epoch (6.4 minute period). This decreases to as low as 4 as more validators leave, to intentionally prevent the ability for large amounts of staked ETH to leave at once.
-### Post-merge inflation breakdown
+### Post-merge inflation breakdown {#post-merge-inflation-breakdown}
- Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
- EL issuance: **0**
@@ -87,7 +87,7 @@ Total annual issuance rate: ~0.49%
Net reduction in annual ETH issuance: ~89.4% (0.49% / 4.62% * 100)
-## The burn
+## The burn {#the-burn}
This flip side of ETH issuance is the rate at which ETH is burned. To execute a transaction on Ethereum, a minimum fee (known as a `base fee`) must be paid, which fluctuates depending on network activity in the moment. This fee is paid in ETH, is _required_ for the transaction to be considered valid, and is _burned_ in the process, removing it from circulation.
From 513087a08bdeef3da1a261d9efbaefa5f5af353e Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 13:59:05 -0700
Subject: [PATCH 022/244] link to /eth-issuance
---
src/content/upgrades/merge/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index c27e121b45a..d3aef9b4811 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -188,7 +188,7 @@ ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately
-The APR for stakers is expected to increase post-merge. To understand by how much, it is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
+The APR for stakers is expected to increase post-merge. To understand by how much, it is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
This will be a new separate source of revenue for validators when they propose blocks. As you can imagine, the amount of fees a validator receives is proportional to network activity at the time of their proposed block. The more fees being paid by users, the more fees validators will receive.
From 523291fd9f743cac6acba1f12793209883428a9a Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 14:13:02 -0700
Subject: [PATCH 023/244] Apply suggestions from code review
Co-authored-by: Corwin Smith
---
src/content/energy-consumption/index.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/content/energy-consumption/index.md b/src/content/energy-consumption/index.md
index a4b802bc6b1..f39dbdf73fd 100644
--- a/src/content/energy-consumption/index.md
+++ b/src/content/energy-consumption/index.md
@@ -15,14 +15,14 @@ Since inception, Ethereum has aimed to implement a PoS consensus mechanism, but
A PoS blockchain known as the "Beacon Chain" has been running since November 2020 alongside the PoW Ethereum Mainnet. In 2022 several custom devnets have been merged with their own Beacon Chains to aid in debugging Ethereum clients in advance of the real merge. More recently, Ethereum developers have started merging public testnets (Kiln, Kintsugi, Ropsten) and shadow-forks (forks of Ethereum Mainnet) as the final stage of testing. Merging Ethereum Mainnet with the Beacon Chain is expected to happen in the second half of 2022. At the moment of the merge, Ethereum's PoW mining will be switched off, PoS consensus will take over, and the energy consumed by the network will drop to <0.05% of its pre-merge amount.
-## Why proof-of-stake is greener than proof-of-work {why-pos-is-greener-than-pow}
+## Why proof-of-stake is greener than proof-of-work {#why-pos-is-greener-than-pow}
PoW is a robust way to secure the network. Transactions on the Ethereum blockchain are validated by [miners](/developers/docs/consensus-mechanisms/pow/mining). Miners bundle together transactions into ordered blocks and add them to the Ethereum blockchain. The new blocks get broadcast to all the other node operators who run the transactions independently and verify that they are valid. Any dishonesty shows up as an inconsistency between different nodes. Honest blocks are added to the blockchain and become an immutable part of history.
The ability for any miner to add new blocks only works if there is a cost associated with mining and unpredictability about which specific node submits the next block. These conditions are met by imposing PoW. To be eligible to submit a block of transactions, a miner must be the first to submit the solution to a computationally expensive puzzle. To successfully take control of the blockchain, a dishonest miner would have to consistently win the PoW race by investing in sufficient hardware and energy to outperform the majority of other miners.
-This mechanism of securing the network is problematic for several reasons. Miners can increase their odds of success by investing in more and more powerful hardware, creatign conditions for an arms race with miners acquiring increasingly power-hungry mining equipment. This increases the network's energy consumption and generates hardware waste. Ethereum's PoW protocol currently has a total annualized power consumption approximately equal to that of Finland [^1] and carbon footprint similar to Switzerland[^1].
+This mechanism of securing the network is problematic for several reasons. Miners can increase their odds of success by investing in more and more powerful hardware, creating conditions for an arms race with miners acquiring increasingly power-hungry mining equipment. This increases the network's energy consumption and generates hardware waste. Ethereum's PoW protocol currently has a total annualized power consumption approximately equal to that of Finland [^1] and carbon footprint similar to Switzerland[^1].
-PoS uses validators instead of miners. Validators perform the same function as miners except that instead of expending their assets up-front in the form of energy expenditure, they stake ETH as collateral against dishonest behavior. This staked ether cna be destroyed if the validator misbehaves, with more severe penalties for more nefarious actions. This strongly incentivizes active and honest participation in securing the network without requiring large energy expenditure. Since almost all of the energy expended securing the PoW network comes from the mining algorithm, switching to PoS reduces the energy expenditure dramatically. There is also no benefit to be had by investing in mroe powerful hardware under PoS, so there is no arms-race condition and less electronic waste. Ethereum validators can run on normal laptops or even low-power devices such as [Raspberry Pi](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/user-guide/ethereum2.0.html).
+PoS uses validators instead of miners. Validators perform the same function as miners except that instead of expending their assets up-front in the form of energy expenditure, they stake ETH as collateral against dishonest behavior. This staked ether can be destroyed if the validator misbehaves, with more severe penalties for more nefarious actions. This strongly incentivizes active and honest participation in securing the network without requiring large energy expenditure. Since almost all of the energy expended securing the PoW network comes from the mining algorithm, switching to PoS reduces the energy expenditure dramatically. There is also no benefit to be had by investing in more powerful hardware under PoS, so there is no arms-race condition and less electronic waste. Ethereum validators can run on normal laptops or even low-power devices such as [Raspberry Pi](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/user-guide/ethereum2.0.html).
Read more detailed information about [how PoS is implemented in Ethereum](/developers/docs/consensus-mechanisms/pos) and how it compares to PoW.
@@ -32,7 +32,7 @@ Estimates based on the current Beacon Chain suggest that the merge to PoS could
Many articles estimate "per-transaction" energy expenditure to compare blockchains to other industries. The benefit of this is that it is easy to understand, but the energy required to mine a block is independent of the number of transactions within it. A per transaction unit of energy expenditure implies that fewer transactions would lead to smaller energy expenditure, and vice-versa, which is not the case. A per-transaction estimate is highly dependent upon how a blockchain's transaction throughput is defined, and tweaking this definition can be gamed to make the value seem larger or smaller.
-For example, for Ethereum the transaction throughput is not only that of the base layer - it is also the sum of the transaction throughput of all of its “layer 2” rollups, which are not generally included in calculations and would drastically reduce them. This is why tools that compare energy consumption per transaction across platforms are misleading.
+For example, for Ethereum the transaction throughput is not only that of the base layer - it is also the sum of the transaction throughput of all of its “[layer 2](/layer-2/)” rollups, which are not generally included in calculations and would drastically reduce them. This is why tools that compare energy consumption per transaction across platforms are misleading.
More relevant is the overall energy consumption and carbon footprint of the network as a whole. From those values one can examine what that network offers to its users and to society at large and make a more holistic evaluation of whether that energy expenditure is justified or not. Per transaction measurements, on the other hand, imply the value of the network only comes from its role in transferring crypto between accounts and prohibit an honest cost-benefit analysis.
From afc98cd7e023be78a460a4048ac776419b1281e0 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 14:14:12 -0700
Subject: [PATCH 024/244] remove comment
---
src/content/upgrades/merge/eth-issuance/index.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/content/upgrades/merge/eth-issuance/index.md b/src/content/upgrades/merge/eth-issuance/index.md
index 8d4ff9e9d89..f31ae150d8f 100644
--- a/src/content/upgrades/merge/eth-issuance/index.md
+++ b/src/content/upgrades/merge/eth-issuance/index.md
@@ -39,8 +39,6 @@ Issuance of new ETH on this chain is rewarded to validators for properly attesti
Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
-
-
**EL issuance:**
- Estimating at 2.08 ETH per 13.3 seconds\*: **~4,930,000** ETH issued in a year
From f4c90c9f5843b4c3aa8989c97b4030fcd5c68241 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Thu, 9 Jun 2022 17:10:48 -0600
Subject: [PATCH 025/244] add note about wallet addresses to layer 2 page
---
src/pages/layer-2.js | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index 36504dcd83b..958a4e83f31 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -679,6 +679,15 @@ const Layer2Page = ({ data }) => {
+
+ NOTE: When bridging over and using layer 2, it is important to note
+ that you will control the address for you EOA account just like on
+ Ethereum Mainnet. However, if you are using a smart contract wallet,
+ you will not have control over this address on a layer 2 by default
+ unless deployed using `CREATE2`. If you are bridging or sending funds
+ to a smart contract wallet, test this out first to make sure you
+ control that address on the layer 2 you are using.
+
From 20a533f73e98e3e42d1435b19d4936976241b0ed Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Thu, 9 Jun 2022 16:17:58 -0700
Subject: [PATCH 026/244] rearrange misconceptions for flow
---
src/content/upgrades/merge/index.md | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index d3aef9b4811..baf7c0a9aad 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -159,30 +159,30 @@ Many dapps require a number of PoW block confirmations that take a period of tim
+contentPreview="False. Staking withdrawals are not yet enabled with The Merge. These will have to wait until the Shanghai upgrade to follow.">
Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
-Withdrawal functionality is planned for the Shanghai upgrade to follow The Merge. This means that newly issued ETH, though accumulating on the Beacon Chain, will remain locked and illiquid for at least 6-12 months following The Merge.
+Withdrawal functionality is planned for the **Shanghai upgrade** to follow The Merge. This means that newly issued ETH, though accumulating on the Beacon Chain, will remain locked and illiquid for at least 6-12 months following The Merge.
-After the Shanghai upgrade enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
+title="Misconception 5: "Validators will not receive any liquid ETH rewards til the Shanghai upgrade when withdrawals are enabled.""
+contentPreview="False. Fee tips/MEV will be credited to a Mainnet account controlled by the validator, available immediately.">
+This may seem counterintuitive to the above note that withdrawals are not enabled til the Shanghai upgrade, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
-An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, and also prevents a potential attacker from using their stake to commit a slashable offense and then exiting their entire staking balance in the same epoch before the slashing penalty can be enforced.
+ETH is issued by the protocol as a reward to validators for contributing to consensus. This _newly issued_ ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
-The APR is intentionally dynamic, allowing a market of stakers to find a balance of how much they're willing to be paid to help secure the network. When withdrawals are enabled, if the rate is too low, then validators will exit, at a rate limited by the protocol. Gradually this will raise the APR for everyone who remains, slowly attracting new or returning stakers yet again.
+ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately from the consensus layer. When users execute transactions that involve Mainnet, ETH must be paid to cover the gas which includes a tip to the validator. This ETH is already on the execution layer, is NOT being newly issued by the protocol, and is available to the validator immediately (given a proper `fee recipient` address is provided to the client software).
-This may seem counterintuitive to the above note that withdrawals are not enabled til Shanghai, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
+title="Misconception 6: "When withdrawals are enabled, stakers will all exit at once.""
+contentPreview="False. Validator exits are rate limited for security reasons.">
+After the Shanghai upgrade enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
-ETH is issued by the protocol as a reward to validators for contributing to consensus. This _newly issued_ ETH is accounted for on the Beacon Chain (consensus layer), where a validator has a unique address that holds its staked ETH and protocol rewards. This ETH is locked until Shanghai.
+An important caveat here, full validator exits are rate limited by the protocol, so only 6 validators may exit per epoch (every 6.4 minutes, so 1350/day, or only ~43,200 ETH/day, out of >10 million ETH staked). This rate limit adjusts depending on total ETH staked, and acts as a bottle neck to prevent a mass exodus of funds, and also prevents a potential attacker from using their stake to commit a slashable offense and then exiting their entire staking balance in the same epoch before the slashing penalty can be enforced.
-ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately from the consensus layer. When users execute transactions that involve Mainnet, ETH must be paid to cover the gas which includes a tip to the validator. This ETH is already on the execution layer, is NOT being newly issued by the protocol, and is available to the validator immediately (given a proper `fee recipient` address is provided to the client software).
+The APR is intentionally dynamic, allowing a market of stakers to find a balance of how much they're willing to be paid to help secure the network. When withdrawals are enabled, if the rate is too low, then validators will exit, at a rate limited by the protocol. Gradually this will raise the APR for everyone who remains, slowly attracting new or returning stakers yet again.
Date: Thu, 9 Jun 2022 21:06:17 -0700
Subject: [PATCH 027/244] Adds PreMergeBanner
to pages flagged during audit
---
src/components/PreMergeBanner.tsx | 27 ++++++++
.../pow/mining-algorithms/index.md | 1 +
.../consensus-mechanisms/pow/mining/index.md | 1 +
.../docs/development-networks/index.md | 1 +
.../developers/docs/intro-to-ether/index.md | 1 +
src/content/developers/docs/mev/index.md | 1 +
.../developers/docs/networking-layer/index.md | 1 +
src/content/developers/docs/networks/index.md | 1 +
.../client-diversity/index.md | 1 +
.../docs/nodes-and-clients/index.md | 1 +
.../nodes-as-a-service/index.md | 1 +
.../nodes-and-clients/run-a-node/index.md | 1 +
.../tutorials/run-light-node-geth/index.md | 1 +
.../tutorials/run-node-raspberry-pi/index.md | 1 +
src/content/governance/index.md | 1 +
src/content/nft/index.md | 1 +
src/content/security/index.md | 1 +
src/pages/developers/tutorials.js | 1 +
src/schema/sdls/Frontmatter.ts | 1 +
src/templates/docs.tsx | 14 +++--
src/templates/tutorial.tsx | 63 +++++++++++--------
src/templates/use-cases.tsx | 27 +++++---
22 files changed, 108 insertions(+), 41 deletions(-)
create mode 100644 src/components/PreMergeBanner.tsx
diff --git a/src/components/PreMergeBanner.tsx b/src/components/PreMergeBanner.tsx
new file mode 100644
index 00000000000..e051862f357
--- /dev/null
+++ b/src/components/PreMergeBanner.tsx
@@ -0,0 +1,27 @@
+import React from "react"
+import styled from "styled-components"
+import BannerNotification from "./BannerNotification"
+import Link from "./Link"
+
+const StyledBannerNotification = styled(BannerNotification)`
+ display: block;
+ z-index: 1;
+ a {
+ text-decoration: underline;
+ }
+`
+
+export interface IProps {
+ className?: string
+}
+
+const PreMergeBanner: React.FC = ({ className }) => (
+
+ The Merge is approaching which comes with many changes to Ethereum. Some
+ content on this page may be out-of-date related to these changes, and
+ updates are coming soon.{" "}
+ Learn more about The Merge.
+
+)
+
+export default PreMergeBanner
diff --git a/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md b/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md
index 9b238f93bb1..0defa86d376 100644
--- a/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md
+++ b/src/content/developers/docs/consensus-mechanisms/pow/mining-algorithms/index.md
@@ -3,6 +3,7 @@ title: Mining algorithms
description: A detailed look at the algorithms used for Ethereum mining.
lang: en
sidebar: true
+preMergeBanner: true
---
Ethereum mining has used two mining algorithms, Dagger Hashimoto and Ethash. Dagger Hashimoto was never used to mine Ethereum, being superseded by Ethash before mainet launched. It was a R&D mining algorithm that paved the way for Ethash. However, it has historical significance as an important innovation in Ethereum's development. Proof-of-work mining itself will be deprecated in favor of proof-of-stake during [The Merge](/merge/), which is forecast to happen in Q3-Q4 2022.
diff --git a/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md b/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
index 427f86f6cf7..aa2370710ac 100644
--- a/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
+++ b/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
@@ -3,6 +3,7 @@ title: Mining
description: An explanation of how mining works in Ethereum and how it helps keep Ethereum secure and decentralized.
lang: en
sidebar: true
+preMergeBanner: true
---
## Prerequisites {#prerequisites}
diff --git a/src/content/developers/docs/development-networks/index.md b/src/content/developers/docs/development-networks/index.md
index 3e37e5b1e57..9008ec45f31 100644
--- a/src/content/developers/docs/development-networks/index.md
+++ b/src/content/developers/docs/development-networks/index.md
@@ -3,6 +3,7 @@ title: Development Networks
description: An overview of development networks and the tools available to help build Ethereum applications.
lang: en
sidebar: true
+preMergeBanner: true
---
When building an Ethereum application with smart contracts, you'll want to run it on a local network to see how it works before deploying it.
diff --git a/src/content/developers/docs/intro-to-ether/index.md b/src/content/developers/docs/intro-to-ether/index.md
index d3b4ae52413..b6726657015 100644
--- a/src/content/developers/docs/intro-to-ether/index.md
+++ b/src/content/developers/docs/intro-to-ether/index.md
@@ -3,6 +3,7 @@ title: Intro to ether
description: A developer's introduction to the ether cryptocurrency.
lang: en
sidebar: true
+preMergeBanner: true
---
## Prerequisites {#prerequisites}
diff --git a/src/content/developers/docs/mev/index.md b/src/content/developers/docs/mev/index.md
index d15c62f6897..a7a9af1a414 100644
--- a/src/content/developers/docs/mev/index.md
+++ b/src/content/developers/docs/mev/index.md
@@ -3,6 +3,7 @@ title: Maximal extractable value (MEV)
description: An introduction to maximal extractable value (MEV)
lang: en
sidebar: true
+preMergeBanner: true
---
Maximal extractable value (MEV) refers to the maximum value that can be extracted from block production in excess of the standard block reward and gas fees by including, excluding, and changing the order of transactions in a block.
diff --git a/src/content/developers/docs/networking-layer/index.md b/src/content/developers/docs/networking-layer/index.md
index 425d2119ccc..98a8bae2c76 100644
--- a/src/content/developers/docs/networking-layer/index.md
+++ b/src/content/developers/docs/networking-layer/index.md
@@ -4,6 +4,7 @@ description: An introduction to Ethereum's networking layer.
lang: en
sidebar: true
sidebarDepth: 2
+preMergeBanner: true
---
Ethereum is a peer-to-peer network with thousands of nodes that must be able to communicate with one another using standardized protocols. The "networking layer" is the stack of protocols that allow those nodes to find each other and exchange information. This includes "gossiping" information (one-to-many communication) over the network as well as swapping requests and responses between specific nodes (one-to-one communication). Each node must adhere to specific networking rules to ensure they are sending and receiving the correct information.
diff --git a/src/content/developers/docs/networks/index.md b/src/content/developers/docs/networks/index.md
index 59062963f32..1de9b5d1768 100644
--- a/src/content/developers/docs/networks/index.md
+++ b/src/content/developers/docs/networks/index.md
@@ -3,6 +3,7 @@ title: Networks
description: An overview of Ethereum's networks and where to get testnet ether (ETH) for testing your application.
lang: en
sidebar: true
+preMergeBanner: true
---
Networks are different Ethereum environments you can access for development, testing, or production use cases. Since Ethereum is a protocol, there can be multiple independent "networks" that conform to the protocol without interacting with each other.
diff --git a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
index aebacbef902..2ec6e717790 100644
--- a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
+++ b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
@@ -4,6 +4,7 @@ description: A high level explanation of the importance of Ethereum client diver
lang: en
sidebar: true
sidebarDepth: 2
+preMergeBanner: true
---
The behavior of an Ethereum node is controlled by the client software it runs. There are several production-level Ethereum clients, each one developed and maintained in different languages by separate teams. The clients are built to a common spec that ensures the clients seamlessly communicate with each other and have the same functionality and provide an equivalent user experience. However, at the moment the distribution of clients across nodes is not equal enough to realize this network fortification to its full potential. Ideally, users divide roughly equally across the various clients to bring as much client diversity as possible to the network.
diff --git a/src/content/developers/docs/nodes-and-clients/index.md b/src/content/developers/docs/nodes-and-clients/index.md
index e8d45a51b70..f3db7a88be9 100644
--- a/src/content/developers/docs/nodes-and-clients/index.md
+++ b/src/content/developers/docs/nodes-and-clients/index.md
@@ -4,6 +4,7 @@ description: An overview of Ethereum nodes and client software, plus how to set
lang: en
sidebar: true
sidebarDepth: 2
+preMergeBanner: true
---
Ethereum is a distributed network of computers running software (known as nodes) that can verify blocks and transaction data. You need an application, known as a client, on your computer to "run" a node.
diff --git a/src/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/src/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md
index 4dfdd79e03b..94b0c69afc1 100644
--- a/src/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md
+++ b/src/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md
@@ -4,6 +4,7 @@ description: An entry-level overview of node services, the pros and cons, and po
lang: en
sidebar: true
sidebarDepth: 2
+preMergeBanner: true
---
## Introduction {#Introduction}
diff --git a/src/content/developers/docs/nodes-and-clients/run-a-node/index.md b/src/content/developers/docs/nodes-and-clients/run-a-node/index.md
index 5dc2877a1ad..c769b2eec8f 100644
--- a/src/content/developers/docs/nodes-and-clients/run-a-node/index.md
+++ b/src/content/developers/docs/nodes-and-clients/run-a-node/index.md
@@ -4,6 +4,7 @@ description: General introduction to running your own instance of an Ethereum cl
lang: en
sidebar: true
sidebarDepth: 2
+preMergeBanner: true
---
Running your own node provides you various benefits, opens new possibilities, and helps to support the ecosystem. This page will guide you through spinning up your own node and taking part in validating Ethereum transactions.
diff --git a/src/content/developers/tutorials/run-light-node-geth/index.md b/src/content/developers/tutorials/run-light-node-geth/index.md
index 2281246cb6c..b23641801b1 100644
--- a/src/content/developers/tutorials/run-light-node-geth/index.md
+++ b/src/content/developers/tutorials/run-light-node-geth/index.md
@@ -7,6 +7,7 @@ skill: beginner
lang: en
sidebar: true
published: 2022-03-04
+preMergeBanner: true
---
You may be interested in running an [Ethereum node](/developers/docs/nodes-and-clients/). One of the easiest ways to do so is by downloading, installing, and running Geth. With Geth, we can have a light node up and running in minutes.
diff --git a/src/content/developers/tutorials/run-node-raspberry-pi/index.md b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
index 2223a440d97..5a766685995 100644
--- a/src/content/developers/tutorials/run-node-raspberry-pi/index.md
+++ b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
@@ -9,6 +9,7 @@ skill: intermediate
published: 2020-05-07
source: r/ethereum
sourceUrl: https://www.reddit.com/r/ethereum/comments/gf3nhg/ethereum_on_arm_raspberry_pi_4_images_release/
+preMergeBanner: true
---
**TL;DR**: Flash your Raspberry Pi 4, plug in an ethernet cable, connect the SSD disk and power up the device to turn the Raspberry Pi 4 into a full Ethereum node running the execution layer, or the consensus layer (Beacon Chain / validator)
diff --git a/src/content/governance/index.md b/src/content/governance/index.md
index 7bff3d0e388..1b541cc6a15 100644
--- a/src/content/governance/index.md
+++ b/src/content/governance/index.md
@@ -3,6 +3,7 @@ title: Ethereum Governance
description: An introduction to how decisions about Ethereum are made.
lang: en
sidebar: true
+preMergeBanner: true
---
# Introduction to Ethereum governance {#introduction}
diff --git a/src/content/nft/index.md b/src/content/nft/index.md
index e7da18f0d9d..32366d20b18 100644
--- a/src/content/nft/index.md
+++ b/src/content/nft/index.md
@@ -11,6 +11,7 @@ alt: An Eth logo being displayed via hologram.
summaryPoint1: A way to represent anything unique as an Ethereum-based asset.
summaryPoint2: NFTs are giving more power to content creators than ever before.
summaryPoint3: Powered by smart contracts on the Ethereum blockchain.
+preMergeBanner: true
---
NFTs are currently taking the digital art and collectibles world by storm. Digital artists are seeing their lives change thanks to huge sales to a new crypto-audience. And celebrities are joining in as they spot a new opportunity to connect with fans. But digital art is only one way to use NFTs. Really they can be used to represent ownership of any unique asset, like a deed for an item in the digital or physical realm.
diff --git a/src/content/security/index.md b/src/content/security/index.md
index 05c65c4692f..9562620820c 100644
--- a/src/content/security/index.md
+++ b/src/content/security/index.md
@@ -3,6 +3,7 @@ title: Ethereum security and scam prevention
description: Staying safe on Ethereum
lang: en
sidebar: true
+preMergeBanner: true
---
# Ethereum security and scam prevention {#introduction}
diff --git a/src/pages/developers/tutorials.js b/src/pages/developers/tutorials.js
index 3b5e1db27b5..d3c5b0e6432 100644
--- a/src/pages/developers/tutorials.js
+++ b/src/pages/developers/tutorials.js
@@ -498,6 +498,7 @@ export const query = graphql`
skill
published
lang
+ preMergeBanner
}
}
}
diff --git a/src/schema/sdls/Frontmatter.ts b/src/schema/sdls/Frontmatter.ts
index e1c5ef159b2..92c20c03fa7 100644
--- a/src/schema/sdls/Frontmatter.ts
+++ b/src/schema/sdls/Frontmatter.ts
@@ -24,5 +24,6 @@ export const Frontmatter = `
author: String
tags: [String]
isOutdated: Boolean
+ preMergeBanner: Boolean
}
`
diff --git a/src/templates/docs.tsx b/src/templates/docs.tsx
index c447fb49f46..a78eb12a5b8 100644
--- a/src/templates/docs.tsx
+++ b/src/templates/docs.tsx
@@ -33,6 +33,7 @@ import {
Header4,
ListItem,
} from "../components/SharedStyledComponents"
+import PreMergeBanner from "../components/PreMergeBanner"
import { ZenModeContext } from "../contexts/ZenModeContext.js"
import { isLangRightToLeft } from "../utils/translations"
@@ -179,6 +180,7 @@ const DocsPage = ({
const tocItems = mdx.tableOfContents?.items
const isPageIncomplete = !!mdx.frontmatter.incomplete
+ const showMergeBanner = !!mdx.frontmatter.preMergeBanner
const { editContentUrl } = siteData.siteMetadata || {}
const { relativePath, slug } = pageContext
@@ -190,10 +192,13 @@ const DocsPage = ({
title={mdx.frontmatter.title}
description={mdx.frontmatter.description}
/>
-
- {/* TODO move to common.json */}
-
-
+ {isPageIncomplete && (
+
+ {/* TODO move to common.json */}
+
+
+ )}
+ {showMergeBanner && }
+
+ )}
@@ -438,6 +444,7 @@ export const useCasePageQuery = graphql`
}
}
isOutdated
+ preMergeBanner
}
body
tableOfContents
From d604270bb527bb7b13457a3c46f18385f0410e9a Mon Sep 17 00:00:00 2001
From: Joe
Date: Fri, 10 Jun 2022 13:23:24 +0100
Subject: [PATCH 028/244] rasp-pi tutorial
---
.../tutorials/run-node-raspberry-pi/index.md | 275 ++++++------------
1 file changed, 82 insertions(+), 193 deletions(-)
diff --git a/src/content/developers/tutorials/run-node-raspberry-pi/index.md b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
index 2223a440d97..c7c8971f079 100644
--- a/src/content/developers/tutorials/run-node-raspberry-pi/index.md
+++ b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
@@ -1,264 +1,153 @@
---
title: How to turn your Raspberry Pi 4 into a node just by flashing the MicroSD card
-description: Flash your Raspberry Pi 4, plug in an ethernet cable, connect the SSD disk and power up the device to turn the Raspberry Pi 4 into a full Ethereum node running the execution layer, or consensus layer (Beacon Chain / validator)
+description: Flash your Raspberry Pi 4, plug in an ethernet cable, connect the SSD disk and power up the device to turn the Raspberry Pi 4 into a full Ethereum node + validator
author: "EthereumOnArm"
tags: ["clients", "execution layer", "consensus layer", "nodes"]
lang: en
sidebar: true
skill: intermediate
-published: 2020-05-07
-source: r/ethereum
+published: 2022-06-10
+source: [Ethereum on ARM](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html)
sourceUrl: https://www.reddit.com/r/ethereum/comments/gf3nhg/ethereum_on_arm_raspberry_pi_4_images_release/
---
-**TL;DR**: Flash your Raspberry Pi 4, plug in an ethernet cable, connect the SSD disk and power up the device to turn the Raspberry Pi 4 into a full Ethereum node running the execution layer, or the consensus layer (Beacon Chain / validator)
+**Ethereum on Arm is a custom Linux image that can turn a Raspberry Pi into an Ethereum node.**
-[Learn about Ethereum upgrades](/upgrades/)
+To use Ethereum on Arm to turn a Raspberry Pi into an Ethereum node, the following hardware is recommended:
-Some background first. As you know, we’ve been running into some memory issues [[1]](/developers/tutorials/run-node-raspberry-pi/#references) with the Raspberry Pi 4 image as Raspbian OS is still on 32bits [[2]](/developers/tutorials/run-node-raspberry-pi/#references) (at least the userland). While we prefer to stick with the official OS we came to the conclusion that, in order to solve these issues, we need to migrate to a native 64 bits OS
-
-Besides, [consensus clients](/upgrades/get-involved/#clients) don’t support 32 bits binaries so using Raspbian would exclude the Raspberry Pi 4 from running a consensus layer node (and the possibility of staking).
-
-So, after several tests we are now releasing 2 different images based on Ubuntu 20.04 64bit [[3]](/developers/tutorials/run-node-raspberry-pi/#references): execution layer and consensus layer editions.
-
-Basically, both are the same image and include the same features of the Raspbian based images. But they are setup for running execution layer or consensus layer software by default.
-
-**Images take care of all the necessary steps**, from setting up the environment and formatting the SSD disk to installing and running the Ethereum software as well as starting the blockchain synchronization.
-
-## Main features {#main-features}
-
-- Based on Ubuntu 20.04 64bit
-- Automatic USB disk partitioning and formatting
-- Adds swap memory (ZRAM kernel module + a swap file) based on Armbian work [[7]](/developers/tutorials/run-node-raspberry-pi/#references)
-- Changes the hostname to something like “ethnode-e2a3e6fe” based on MAC hash
-- Runs software as a systemd service and starts syncing the Blockchain
-- Includes an APT repository for installing and upgrading Ethereum software
-- Includes a monitoring dashboard based on Grafana / Prometheus
-
-## Software included {#software-included}
-
-Both images include the same packages, the only difference between them is that the execution version runs Geth by default and the consensus version runs Prysm beacon chain by default.
-
-### Execution clients {#execution-clients}
-
-- Geth [[8]](/developers/tutorials/run-node-raspberry-pi/#references): 1.9.13 (official binary)
-- Parity [[9]](/developers/tutorials/run-node-raspberry-pi/#references): 2.7.2 (cross compiled)
-- Nethermind [[10]](/developers/tutorials/run-node-raspberry-pi/#references): 1.8.28 (cross compiled)
-- Hyperledger Besu [[11]](/developers/tutorials/run-node-raspberry-pi/#references): 1.4.4 (compiled)
-
-### Consensus clients {#consensus-clients}
-
-- Prysm [[12]](/developers/tutorials/run-node-raspberry-pi/#references): 1.0.0-alpha6 (official binary)
-- Lighthouse [[13]](/developers/tutorials/run-node-raspberry-pi/#references): 0.1.1 (compiled)
-
-### Ethereum framework {#ethereum-framework}
-
-- Swarm [[14]](/developers/tutorials/run-node-raspberry-pi/#references): 0.5.7 (official binary)
-- Raiden Network [[15]](/developers/tutorials/run-node-raspberry-pi/#references): 0.200.0~rc1 (official binary)
-- IPFS [[16]](/developers/tutorials/run-node-raspberry-pi/#references): 0.5.0 (official binary)
-- Statusd [[17]](/developers/tutorials/run-node-raspberry-pi/#references): 0.52.3 (compiled)
-- Vipnode [[18]](/developers/tutorials/run-node-raspberry-pi/#references): 2.3.3 (official binary)
-
-## Installation guide and usage {#installation-guide-and-usage}
-
-### Recommended hardware and setup {#recommended-hardware-and-setup}
-
-- Raspberry 4 (model B) - 4GB
+- Raspberry 4 (model B 8GB)
- MicroSD Card (16 GB Class 10 minimum)
-- SSD USB 3.0 disk (see storage section)
+- 1 TB SSD minimum USB 3.0 disk or an SSD with an USB to SATA case (see Storage section).
- Power supply
- Ethernet cable
-- 30303 Port forwarding (execution layer) and 13000 port forwarding (consensus layer) [[4]](/developers/tutorials/run-node-raspberry-pi/#references)
-- A case with heatsink and fan (optional but strongly recommended)
-- USB keyboard, Monitor and HDMI cable (micro-HDMI) (optional)
+- Port forwarding (see clients for further info)
+- A case with heatsink and fan
+- USB keyboard, Monitor and HDMI cable (micro-HDMI) (Optional)
-## Storage {#storage}
+## Why run Ethereum on ARM?
-You will need an SSD to run the Ethereum clients (without an SSD drive there’s absolutely no chance of syncing the Ethereum blockchain). There are 2 options:
+ARM boards are very affordable, flexible, small computers. They are good choices for running Ethereum nodes because they can be bought cheaply, configured so that all their resources focus just on the node, making them efficient, they consume low amounts of power and have are physically small so they can fit unobtrusively in any home. It is also very easy to spin up nodes because the Raspberry Pi's MicroSD can simply be flashed with a prebuilt image, with no downloading or building software required.
-- Use a USB portable SSD disk such as the Samsung T5 Portable SSD.
-- Use a USB 3.0 External Hard Drive Case with a SSD Disk. In our case we used a Inateck 2.5 Hard Drive Enclosure FE2011. Make sure to buy a case with an UAS compliant chip, particularly, one of these: JMicron (JMS567 or JMS578) or ASMedia (ASM1153E).
+## How does it work?
-In both cases, avoid getting low quality SSD disks as it is a key component of your node and it can drastically affect the performance (and sync times).
+The Raspberry Pi's memory card is flashed with a prebuilt image. This image contains everything needed to run an Ethereum node. With a flashed card, all the user needs to do is power-on the Raspberry Pi. All the processes required to run the node are automatically started. This works because the memory card contains a Linux-based operating system (OS) on top of which system-level processes are automatically run that turn the unit into an Ethereum node.
-Keep in mind that you need to plug the disk to an USB 3.0 port (blue)
+Ethereum cannot be run using the popular Raspberry Pi Linux OS "Raspbian" because Raspbian still uses a 32-bit architecture which leads Ethereum users to run into memory issues and consensus clients do not support 32-bit binaries. To overcome this, the Ethereum on Arm team migrated to a native 64-bit OS called "Armbian".
-## Image download and installation {#image-download-and-installation}
+**Images take care of all the necessary steps**, from setting up the environment and formatting the SSD disk to installing and running the Ethereum software as well as starting the blockchain synchronization.
-### 1. Download the execution and consensus layer images {#1-download-execution-or-consensus-images}
+## Note on execution and consensus clients
-
- Download execution layer image
-
+The Ethereum on Arm documentation explains how to set up _either_ an execution client OR a consensus client, except for two Ethereum testnets (Kiln and Ropsten). This optionality is only possible in advance of Ethereum's upcoming transition from proof-of-work (PoW) to proof-of-stake (PoS) known as [The Merge](/upgrades/merge). After The Merge, it will not be possible to run execution and consensus clients separately - they must be run as a pair. Therefore, in this tutorial we will run a pair of execution and consensus clients together on an Ethereum testnet (Kiln).
-sha256 7fa9370d13857dd6abcc8fde637c7a9a7e3a66b307d5c28b0c0d29a09c73c55c
+## The Kiln Raspberry Pi 4 Image
-
- Download consensus layer image
-
+Kiln is a public testnet specifically designed for testing The Merge. Ethereum on Arm developed an image allowing users to rapidly spin up a pair of Ethereum clients on this merge testnet. The Kiln merge has already happened, but the network is still live, so it can be used for this tutorial. Ether on Kiln has no real-world value.
-sha256 74c0c15b708720e5ae5cac324f1afded6316537fb17166109326755232cd316e
+The Kiln Raspberry Pi 4 image is a "plug and play" image that automatically installs and sets up both the execution and consensus clients, configuring them to talk to each other and connect to the Kiln network. All the user needs to do is start their processes using a simple command. The image contains four execution clients (Geth, Nethermind, Besu and Erigon) and four consensus clients (Lighthouse, Prysm, Nimbus, Teku) that the user can choose from.
-### 2. Flash the image {#2-flash-the-image}
+Download the Raspberry Pi image from [Ethereum on Arm](https://ethereumonarm-my.sharepoint.com/:u:/p/dlosada/ES56R_SuvaVFkiMO1Tgnf6kB7lEbBfla5c2c18E3WQRJzA?download=1) and verify the file with the following SH256 hash: `485cf36128ca60a41b5de82b5fee3ee46b7c479d0fc5dfa5b9341764414c4c57`.
-Insert the microSD in your Desktop / Laptop and download the file (execution layer, for instance):
+Note that for users that do not own a Raspberry Pi but do have an AWS account, there are ARM instances available that can run the same image. Instructions and the AWS image are available to download from Ethereum on Arm (https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html).
-```bash
-wget https://ethraspbian.com/downloads/ubuntu-20.04-preinstalled-server-arm64+raspi-eth1.img.zip
-```
+## Flashing the MicroSD
-Note: If you are not comfortable with command line or if you are running Windows, you can use [Etcher](https://etcher.io)
+The MicroSD card that will be used for the Raspberry Pi should first be inserted into a desktop or laptop so it can be flashed. Then, the following terminal commands will flash the downloaded image onto the SD card:
-Open a terminal and check your MicroSD device name running:
+```shell
+# check the MicroSD card name
+sudo fdisk -I
-```bash
-sudo fdisk -l
+>> sdxxx
```
-You should see a device named mmcblk0 or sdd. Unzip and flash the image:
+It is really important to get the name correct because the next command includes `dd` which completely erases the existing content of the card before pushing the image onto it. To continue, navigate to the directory containing the zipped image:
-```bash
-unzip ubuntu-20.04-preinstalled-server-arm64+raspi-eth1.img.zip
-sudo dd bs=1M if=ubuntu-20.04-preinstalled-server-arm64+raspi-eth1.img of=/dev/mmcblk0 && sync
+```shell
+# unzip and flash image
+unzip ethonarm_kiln_22.03.01.img.zip
+sudo dd bs=1M if=ethonarm_kiln_22.03.01.img of=/dev/mmcblk0 conv=fdatasync status=progress
```
-### 3. Insert the MicroSD into the Raspberry Pi 4. Connect an Ethernet cable and attach the USB SSD disk (make sure you are using a blue port). {#3-insert-the-microsd-into-the-raspberry-pi-4-connect-an-ethernet-cable-and-attach-the-usb-ssd-disk-make-sure-you-are-using-a-blue-port}
-
-### 4. Power on the device {#4-power-on-the-device}
-
-The Ubuntu OS will boot up in less than one minute but **you will need to wait approximately 10 minutes** in order to allow the script to perform the necessary tasks to turn the device into an Ethereum node and reboot the Raspberry.
-
-Depending on the image, you will be running:
+The card is now flashed, so it can be inserted into the Raspberry Pi.
-- Execution client: Geth as the default client syncing the blockchain
-- Consensus client: Prysm as default client syncing the beacon chain (Prater testnet)
+## Start the node
-### 5. Log in {#5-log-in}
+With the SD card inserted into the Raspberry Pi, connect the ethernet cable and SSD then switch the power on. The OS will boot up and automatically start performing the preconfigured tasks that turn the Raspberry Pi into an Ethereum node, including installing and building the client software. This will probably take 10-15 minutes.
-You can log in through SSH or using the console (if you have a monitor and keyboard attached)
+Once everything is installed and configured, log in to the device via an ssh connection or using the terminal directly if a monitor and keyboard is attached to the board. Use the `ethereum` account to log in, as this has permissions required to start the node.
-```bash
+```shell
User: ethereum
Password: ethereum
```
-You will be prompted to change the password on first login, so you will need to login twice.
+The user can then choose the execution-consensus client combination they wish to run, and start their systemctl processes as follows (example runs Geth and Lighthouse):
-### 6. Open 30303 port for Geth and 13000 if you are running Prysm beacon chain. If you don’t know how to do this, google “port forwarding” followed by your router model. {#6-open-30303-port-for-geth-and-13000-if-you-are-running-prysm-beacon-chain-if-you-dont-know-how-to-do-this-google-port-forwarding-followed-by-your-router-model}
-
-### 7. Get console output {#7-get-console-output}
-
-You can see what’s happening in the background by typing:
-
-```bash
-sudo tail -f /var/log/syslog
+```shell
+sudo systemctl start geth-lh
+sudo systemctl start lh-geth-beacon
```
-**Congratulations. You are now running a full Ethereum node on your Raspberry Pi 4.**
-
-## Syncing the Blockchain {#syncing-the-blockchain}
-
-Now you need to wait for the blockchain to be synced. In the case of the execution layer this will take a few days depending on several factors but you can expect up to about 5-7 days.
-
-If you are running the consensus layer Prater testnet you can expect 1-2 days of Beacon chain synchronization time. Remember that you will need to setup the validator later in order to start the staking process. [How to run the consensus layer validator](/developers/tutorials/run-node-raspberry-pi/#validator)
+The logs can be checked using
-## Monitoring dashboards {#monitoring-dashboards}
-
-For this first release, we included 3 monitoring dashboards based on Prometheus [[5]](/developers/tutorials/run-node-raspberry-pi/#references) / Grafana [[6]](/developers/tutorials/run-node-raspberry-pi/#references) in order to monitor the node and clients’ data (Geth and Besu). You can access through your web browser:
-
-```bash
-URL: http://your_raspberrypi_IP:3000
-User: admin
-Password: ethereum
+```shell
+# logs for Geth
+sudo journalctl -u geth-lh -f
+#logs for lighthouse
+sudo journalctl -u lh-geth-beacon -f
```
-## Switching clients {#switching-clients}
+The specific service names for every combination of clients are available at the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#id2). Theyu can be used to update the commands provided here for any combination.
-All clients run as a systemd service. This is important because if a problem arises the system will respawn the process automatically.
+## Validators
-Geth and Prysm beacon chain run by default (depending on what you are synchronizing, execution layer or consensus layer) so, if you want to switch to other clients (from Geth to Nethermind, for instance), you need to stop and disable Geth first, and enable and start the other client:
+In order to run a validator it is first necessary to deposit 32 test-ether into the Kiln deposit contract. This means the user must have access to an account containing 32 ETH. This can be done by following the step-by-step guide on the [Kiln Launchpad](https://kiln.launchpad.ethereum.org/en/). Do this on a desktop/laptop, built do not generate keys - this can be done directly on the Raspberry Pi.
-```bash
-sudo systemctl stop geth && sudo systemctl disable geth
-```
-
-Commands to enable and start each execution client:
+Open a terminal on the Raspberry Pi and run the following command to generate the deposit keys:
-```bash
-sudo systemctl enable besu && sudo systemctl start besu
-sudo systemctl enable nethermind && sudo systemctl start nethermind
-sudo systemctl enable parity && sudo systemctl start parity
```
-
-Consensus clients:
-
-```bash
-sudo systemctl stop prysm-beacon && sudo systemctl disable prysm-beacon
-sudo systemctl start lighthouse && sudo systemctl enable lighthouse
+cd && deposit new-mnemonic --num_validators 1 --chain kiln
```
-## Changing parameters {#changing-parameters}
-
-Clients’ config files are located in the /etc/ethereum/ directory. You can edit these files and restart the systemd service in order for the changes to take effect. The only exception is Nethermind which, additionally, has a Mainnet config file located here:
-
-```bash
-/etc/nethermind/configs/mainnet.cfg
-```
+Keep the mnemonic phrase safe! The command above generated two files in the node's keystore: the validator keys and a deposit data file. The deposit data needs to be uploaded into the launchpad, so it must be copied from the Raspberry Pi to the desktop/laptop. This can be done using an ssh connection or any other copy/paste method.
-Blockchain clients’ data is stored on the Ethereum home account as follows (note the dot before the directory name):
+Once the deposit data file is available on the computer running the launchpad, it can be dragged and dropped onto the `+` on the launchpad screen. Follow the instructions on the screen to send a transaction to the deposit contract.
-### Execution layer {#execution-layer}
+Back on the Raspberry Pi, a validator cna be started. This requires importing the validator keys, setting the address to collect rewards, then starting the preconfigured validator process. The example below is for Lighthouse - instructions for other consensus clients are available on the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#lighthouse):
-```bash
-/home/ethereum/.geth
-/home/ethereum/.parity
-/home/ethereum/.besu
-/home/ethereum/.nethermind
-```
+```shell
+# import the validator keys
+lighthouse-kl account validator import --directory=/home/ethereum/validator_keys --datadir=/home/ethereum/.lh-geth/kiln/testnet-lh
-### Consensus layer {#consensus-layer}
+# set the reward address
+sudo sed -i '' /etc/ethereum/kiln/lh-geth-validator.conf
-```bash
-/home/ethereum/.eth2
-/home/ethereum/.eth2validators
-/home/ethereum/.lighthouse
+# start the validator
+sudo systemctl start lh-geth-validator
```
-## Nethermind and Hyperledger Besu {#nethermind-and-hyperledger-besu}
-
-These 2 great execution clients have become a great alternative to Geth and Parity. The more diversity in the network, the better, so you may give them a try and contribute to the network health.
-
-Both need further testing so feel free to play with them and report back your feedback.
-
-## How to run the consensus validator (staking) {#validator}
-
-Once the Prater testnet beacon chain is synchronized you can run a validator in the same device. You will need to follow [these participation steps](https://prylabs.net/participate).
-
-The first time, you need to create manually an account by running the “validator” binary and setup a password. Once you have completed this step you can add the password to `/etc/ethereum/prysm-validator.conf` and start the validator as a systemd service.
+Congratulations, you now have a full Ethereum node and validator running on a Raspberry Pi!
## Feedback appreciated {#feedback-appreciated}
-We put a lot of work trying to setup the Raspberry Pi 4 as a full Ethereum node as we know the massive user base of this device may have a very positive impact in the network.
-
-Please, take into account that this is the first image based on Ubuntu 20.04 so there may be some bugs. If so, open an issue on [GitHub](https://github.com/diglos/ethereumonarm) or reach us on [Twitter](https://twitter.com/EthereumOnARM).
+We know the Raspberry Pi has a massive user base that could have a very positive impact on the health of the Ethereum network.
+Please dig into the details in this tutorial, try running on other testnets or even Ethereum Mainnet, check out the Ethereum on Arm Github, gvie feedback, raise issues and pull requests and help advance the technology and documentation!
## References {#references}
-1. [geth repeatedly crashes with SIGSEGV](https://github.com/ethereum/go-ethereum/issues/20190)
-2. [https://github.com/diglos/ethereumonarm](https://github.com/diglos/ethereumonarm)
-3. https://ubuntu.com/download/raspberry-pi
-4. https://wikipedia.org/wiki/Port_forwarding
-5. https://prometheus.io
-6. https://grafana.com
-7. https://forum.armbian.com/topic/5565-zram-vs-swap/
-8. https://geth.ethereum.org
-9. https://github.com/openethereum/openethereum \* **Note that OpenEthereum [has been deprecated](https://medium.com/openethereum/gnosis-joins-erigon-formerly-turbo-geth-to-release-next-gen-ethereum-client-c6708dd06dd) and is no longer being maintained.** Use it with caution and preferably switch to another client implementation.
-10. https://nethermind.io
-11. https://www.hyperledger.org/projects/besu
-12. https://github.com/prysmaticlabs/prysm
-13. https://lighthouse.sigmaprime.io
-14. https://ethersphere.github.io/swarm-home
-15. https://raiden.network
-16. https://ipfs.io
-17. https://status.im
-18. https://vipnode.org
+1. https://ubuntu.com/download/raspberry-pi
+2. https://wikipedia.org/wiki/Port_forwarding
+3. https://prometheus.io
+4. https://grafana.com
+5. https://forum.armbian.com/topic/5565-zram-vs-swap/
+6. https://geth.ethereum.org
+7. https://nethermind.io
+8. https://www.hyperledger.org/projects/besu
+9. https://github.com/prysmaticlabs/prysm
+10. https://lighthouse.sigmaprime.io
+11. https://ethersphere.github.io/swarm-home
+12. https://raiden.network
+13. https://ipfs.io
+14. https://status.im
+15. https://vipnode.org
From 76568a6a3b2dab089d804d2d20148b9c71585906 Mon Sep 17 00:00:00 2001
From: mempirate
Date: Fri, 10 Jun 2022 17:47:28 +0200
Subject: [PATCH 029/244] rename Turbo-Geth to Erigon and update links
---
.../developers/docs/programming-languages/golang/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/content/developers/docs/programming-languages/golang/index.md b/src/content/developers/docs/programming-languages/golang/index.md
index 697672f1e9f..645788dff34 100644
--- a/src/content/developers/docs/programming-languages/golang/index.md
+++ b/src/content/developers/docs/programming-languages/golang/index.md
@@ -34,7 +34,7 @@ Need a more basic primer first? Check out [ethereum.org/learn](/learn/) or [ethe
## Intermediate articles and docs {#intermediate-articles-and-docs}
- [Go Ethereum Documentation](https://geth.ethereum.org/docs/) - _The documentation for the official Ethereum Golang_
-- [Turbo-Geth Programmer's Guide](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _Illustrated guide including the state tree, multi-proofs, and transaction processing_
+- [Erigon Programmer's Guide](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _Illustrated guide including the state tree, multi-proofs, and transaction processing_
- [Turbo-Geth and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Community Conference (EthCC 3)_
- [Turbo-Geth: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
@@ -55,7 +55,7 @@ Need a more basic primer first? Check out [ethereum.org/learn](/learn/) or [ethe
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _Official Go implementation of the Ethereum protocol_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Review and analysis of Go Ethereum source code_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _Faster derivative of Go Ethereum_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _Faster derivative of Go Ethereum, with a focus on archive nodes_
- [Golem](https://github.com/golemfactory/golem) - _Golem is creating a global market for computing power_
- [Quorum](https://github.com/jpmorganchase/quorum) - _A permissioned implementation of Ethereum supporting data privacy_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Ethereum 'Serenity' 2.0 Go Implementation_
From 75ea8c707bef9667b9922515b40cb03c5bf3eef3 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 11:02:55 -0700
Subject: [PATCH 030/244] revert static page changes
---
src/content/governance/index.md | 1 -
src/content/security/index.md | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/content/governance/index.md b/src/content/governance/index.md
index 1b541cc6a15..7bff3d0e388 100644
--- a/src/content/governance/index.md
+++ b/src/content/governance/index.md
@@ -3,7 +3,6 @@ title: Ethereum Governance
description: An introduction to how decisions about Ethereum are made.
lang: en
sidebar: true
-preMergeBanner: true
---
# Introduction to Ethereum governance {#introduction}
diff --git a/src/content/security/index.md b/src/content/security/index.md
index 9562620820c..05c65c4692f 100644
--- a/src/content/security/index.md
+++ b/src/content/security/index.md
@@ -3,7 +3,6 @@ title: Ethereum security and scam prevention
description: Staying safe on Ethereum
lang: en
sidebar: true
-preMergeBanner: true
---
# Ethereum security and scam prevention {#introduction}
From 57dadb93ef5101560d2feb883c5f6c94394af6d6 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 12:14:28 -0700
Subject: [PATCH 031/244] Update /eth-issuance
---
.../upgrades/merge/eth-issuance/index.md | 30 +++++++++----------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/src/content/upgrades/merge/eth-issuance/index.md b/src/content/upgrades/merge/eth-issuance/index.md
index f31ae150d8f..e8df5456d4a 100644
--- a/src/content/upgrades/merge/eth-issuance/index.md
+++ b/src/content/upgrades/merge/eth-issuance/index.md
@@ -21,17 +21,17 @@ We can break the supply of ETH into two primary forces: issuance, and burn.
The **issuance** of ETH is the process of creating ETH that did not previously exist on the balance sheet, while the **burning** of ETH refers to when existing ETH is permanently removed from circulation. The rate of each of these fluctuates based on a number of parameters, and the balance between them determines the resulting inflation/deflation rate of ether.
-The way ETH is issued will undergo some changes at time of The Merge. Currently, new ETH is issued from two main sources: the execution layer (EL, i.e. Mainnet) and the consensus layer (CL, i.e. Beacon Chain). After The Merge, issuance from the execution layer will go to zero. Let's break this down.
+The way ETH is issued will undergo some changes at time of The Merge. Currently, new ETH is issued from two main sources: the execution layer (i.e. Mainnet) and the consensus layer (i.e. Beacon Chain). After The Merge, issuance from the execution layer will go to zero. Let's break this down.
## Pre-merge {#pre-merge}
-### EL Issuance {#el-issuance-pre-merge}
+### Execution layer issuance {#el-issuance-pre-merge}
-Under proof-of-work, miners only interact with the EL, and are rewarded in the form of block rewards being the first to solve blocks. Since the [Constantinople upgrade](/history/#constantinople) on Feb-28-2019 this reward has been 2 ETH per block. Miners are also rewarded for publishing [ommer](/glossary/#ommer) blocks, which are valid blocks that don't end up in the longest/canonical chain. These rewards max out at 1.75 ETH per ommer, and are _in addition to_ the reward issued from the canonical block. Mining is an economically intensive activity, which requires high levels of ETH issuance to sustain.
+Under proof-of-work, miners only interact with the execution layer, and are rewarded in the form of block rewards being the first to solve blocks. Since the [Constantinople upgrade](/history/#constantinople) in 2019 this reward has been 2 ETH per block. Miners are also rewarded for publishing [ommer](/glossary/#ommer) blocks, which are valid blocks that don't end up in the longest/canonical chain. These rewards max out at 1.75 ETH per ommer, and are _in addition to_ the reward issued from the canonical block. Mining is an economically intensive activity, which requires high levels of ETH issuance to sustain.
-### CL Issuance {#cl-issuance-pre-merge}
+### Consensus layer issuance {#cl-issuance-pre-merge}
-The [Beacon Chain](/history/#beacon-chain-genesis) has been live since Dec-01-2020, which is secured by proof-of-stake validators, not miners. This chain was bootstrapped by Ethereum users depositing ETH one-way into a smart contract on Mainnet, which the Beacon Chain listens to, crediting the user with an equal amount on the new chain. Right now these validators are not processing transactions, and are essentially coming to consensus on the state of the validator pool itself.
+The [Beacon Chain](/history/#beacon-chain-genesis) has been live since 2020, which is secured by proof-of-stake validators, not miners. This chain was bootstrapped by Ethereum users depositing ETH one-way into a smart contract on Mainnet, which the Beacon Chain listens to, crediting the user with an equal amount on the new chain. Right now these validators are not processing transactions, and are essentially coming to consensus on the state of the validator pool itself.
Issuance of new ETH on this chain is rewarded to validators for properly attesting to the state of the chain, and is also rewarded when a validator proposes a block. Rewards (or penalties) are calculated and distributed every epoch (6.4 minutes) based on validator performance for that time period. These rewards are _significantly_ lower than the 2 ETH being issued under proof-of-work today every ~13.5 seconds, as operating a validating node is not an economically intense activity, thus does not require or warrant as high a reward.
@@ -39,33 +39,33 @@ Issuance of new ETH on this chain is rewarded to validators for properly attesti
Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
-**EL issuance:**
+**Execution layer issuance:**
- Estimating at 2.08 ETH per 13.3 seconds\*: **~4,930,000** ETH issued in a year
- Currently inflating at **~4.13%** (4.93M per year / 119.3M total)
- \*This includes the 2 ETH per canonical block, plus an average of 0.08 ETH over time from ommer blocks. Also uses 13.3 second, the baseline block time target without any influence from a [difficulty bomb](/glossary/#difficulty-bomb). ([See source](https://bitinfocharts.com/ethereum/))
-**CL issuance:**
+**Consensus layer issuance:**
-- Using 13,000,000 total ETH staked, the rate of ETH issuance is ~1600 ETH/day ([SeeSource](https://ultrasound.money/))
+- Using 13,000,000 total ETH staked, the rate of ETH issuance is ~1600 ETH/day ([See source](https://ultrasound.money/))
- Results in **~584,000** ETH issued in a year
- Currently inflating at **~0.49%** (584K per year / 119.3M total)
Total annual issuance rate: ~4.62% (4.13% + 0.49%)
-**~89.4%** of the issuance is going to miners on the EL (4.13 / 4.62 \* 100)
+**~89.4%** of the issuance is going to miners on the execution layer (4.13 / 4.62 \* 100)
-**~10.6%** is being issued to stakers on the CL (0.49 / 4.62 \* 100)
+**~10.6%** is being issued to stakers on the consensus layer (0.49 / 4.62 \* 100)
## Post-merge {#post-merge}
-### EL Issuance {#el-issuance-post-merge}
+### Execution layer issuance {#el-issuance-post-merge}
-Will be zero. Proof-of-work will no longer be valid under the rules of consensus, and all EL activity will be included in "beacon blocks" which are published and attested to by proof-of-stake validators.
+Will be zero. Proof-of-work will no longer be valid under the rules of consensus, and all execution layer activity will be included in "beacon blocks" which are published and attested to by proof-of-stake validators.
-### CL Issuance {#cl-issuance-post-merge}
+### Consensus layer issuance {#cl-issuance-post-merge}
Will continue as it was, with small rewards for attesting-to and proposing blocks. These rewards will continue to accrue to _validator balances_ that are managed within the consensus layer. These are separate Ethereum accounts to the accounts we're used to on Mainnet, and until the Shanghai upgrade funds from validator accounts will not be withdrawable/transferrable. This means that although new ETH is still being issued, 100% of it will be locked from the market until this upgrade occurs. When the Shanghai upgrade is rolled out, this ETH will become available.
@@ -76,8 +76,8 @@ Stakers may also choose to exit and withdrawal their entire validator balance, b
### Post-merge inflation breakdown {#post-merge-inflation-breakdown}
- Total ETH supply: **~119,300,000 ETH** (as of Q2 2022)
-- EL issuance: **0**
-- CL issuance: Same as above, **~0.49%** annual issuance rate (with 13 million ETH staked)
+- Execution layer issuance: **0**
+- Consensus layer issuance: Same as above, **~0.49%** annual issuance rate (with 13 million ETH staked)
- Total annual issuance rate: **~0.49%**
From 6e6b5dcf621f26778d7bc6a5ce8f8d5b3af8fff3 Mon Sep 17 00:00:00 2001
From: Joseph Cook <33655003+jmcook1186@users.noreply.github.com>
Date: Fri, 10 Jun 2022 20:50:48 +0100
Subject: [PATCH 032/244] Apply suggestions from code review
update energy-consumption according to @minimalsm review
Co-authored-by: Joshua <62268199+minimalsm@users.noreply.github.com>
---
src/content/energy-consumption/index.md | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/src/content/energy-consumption/index.md b/src/content/energy-consumption/index.md
index f39dbdf73fd..a49a184a0bd 100644
--- a/src/content/energy-consumption/index.md
+++ b/src/content/energy-consumption/index.md
@@ -7,9 +7,9 @@ sidebar: true
# Ethereum energy consumption {#introduction}
-[The Merge](/upgrades/merge/index.md) from [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/#proof-of-work) to [proof-of-stake (PoS)](/developers/docs/consensus-mechanisms/pos) will reduce Ethereum's energy consumption by [~99.95%](https://blog.ethereum.org/2021/05/18/country-power-no-more/). After the Merge Ethereum will use dramatically less carbon to be more secure.
+Ethereum's energy consumption will be reduced by [~99.95%](https://blog.ethereum.org/2021/05/18/country-power-no-more/) following [The Merge](/upgrades/merge/index.md) from [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/#proof-of-work) to [proof-of-stake (PoS)](/developers/docs/consensus-mechanisms/pos). After The Merge Ethereum will use dramatically less carbon to be more secure.
-Since inception, Ethereum has aimed to implement a PoS consensus mechanism, but doing this without sacrificing security and decentralization has taken years of focused research and development. Therefore, the network started by using PoW consensus. PoW consensus requires miners to use their computing hardware to solve a puzzle. The solution to this puzzle acts as proof that some energy has been expended by the miner which in turn demonstrates that they have invested some real-world value for the right to add to the blockchain. PoW is just a mechanism to decide who gets to add the next block, as is PoS. Swapping PoW for PoS, where the real world value invested comes from ether staked directly in a smart contract, removes the need for miners to burn energy to add to the blockchain. Therefore, the environmental cost of securing the network is drastically reduced.
+Since its inception, Ethereum has aimed to implement a proof-of-stake consensus mechanism, but doing this without sacrificing security and decentralization has taken years of focused research and development. Therefore, the network started by using proof-of-work consensus. Proof-of-work consensus requires miners to use their computing hardware to solve a puzzle. The solution to the puzzle proves that some energy has been expended by the miner, demonstrating that they have invested real-world value for the right to add to the blockchain. Proof-of-work is just a mechanism to decide who gets to add the next block, as is proof-of-stake. Swapping proof-of-work for proof-of-stake, where the real world value invested comes from ETH staked directly in a smart contract, removes the need for miners to burn energy to add to the blockchain. Therefore, the environmental cost of securing the network is drastically reduced.
## The Merge {#the-merge}
@@ -38,11 +38,13 @@ More relevant is the overall energy consumption and carbon footprint of the netw
Whole-network energy consumption and carbon footprints for Bitcoin and Ethereum are estimated at [Digiconomist](https://digiconomist.net/ethereum-energy-consumption). At the time of writing this article Ethereum’s total energy consumption is ~112 TWh/yr, equivalent to that of the Netherlands, with a Carbon emission equivalent to that of Singapore (53 MT/yr). For comparison, Bitcoin currently expends about 200 TWh/yr energy and emits about 100 MT/yr C, while also generating about 32,000 T of electrical waste from obsolete hardware per year. Switching off Ethereum’s PoW in favor of PoS will reduce this energy expenditure by more than 99.95%, implying that the total energy expenditure for securing Ethereum is expected to be closer to **0.01 TWh/yr**.
-To put this in context we can compare to annualized estimates for other industries. If we take Ethereum to be a platform for securely holding digital assets as investments, perhaps we can compare to mining gold, which has been estimated to expend about [240 TWh/yr](https://www.kitco.com/news/2021-05-17/Gold-s-energy-consumption-doubles-that-of-bitcoin-Galaxy-Digital.html). As a digital payments platform we could perhaps compare to PayPal (about [0.26 TWh/yr](https://app.impaakt.com/analyses/paypal-consumed-264100-mwh-of-energy-in-2020-24-from-non-renewable-sources-27261)). As an entertainment platform we could perhaps compare to the gaming industry which has been estimated to expend about [34 TW/yr](https://www.researchgate.net/publication/336909520_Toward_Greener_Gaming_Estimating_National_Energy_Use_and_Energy_Efficiency_Potential), or Netflix which expends about [94 TWh/yr](https://www.carbonbrief.org/factcheck-what-is-the-carbon-footprint-of-streaming-video-on-netflix), or Youtube which has been estimated to expend about [244 TWh/yr](https://thefactsource.com/how-much-electricity-does-youtube-use/). Estimates of Youtube’s energy expenditure have even been broken down by channel and even further by individual videos. [Those estimates](https://thefactsource.com/how-much-electricity-does-youtube-use/) imply that at least 45x more energy was expended watching Gangnam Style in 2019 than will be expended in a year of securing PoS Ethereum.
+To put Ethereum's energy consumption in context, we can compare annualized estimates for other industries. If we take Ethereum to be a platform for securely holding digital assets as investments, perhaps we can compare to mining gold, which has been estimated to expend about [240 TWh/yr](https://www.kitco.com/news/2021-05-17/Gold-s-energy-consumption-doubles-that-of-bitcoin-Galaxy-Digital.html). As a digital payments platform we could perhaps compare to PayPal (about [0.26 TWh/yr](https://app.impaakt.com/analyses/paypal-consumed-264100-mwh-of-energy-in-2020-24-from-non-renewable-sources-27261)). As an entertainment platform we could perhaps compare to the gaming industry which has been estimated to expend about [34 TW/yr](https://www.researchgate.net/publication/336909520_Toward_Greener_Gaming_Estimating_National_Energy_Use_and_Energy_Efficiency_Potential), or Netflix which expends about [94 TWh/yr](https://www.carbonbrief.org/factcheck-what-is-the-carbon-footprint-of-streaming-video-on-netflix), or Youtube which has been estimated to expend about [244 TWh/yr](https://thefactsource.com/how-much-electricity-does-youtube-use/). Estimates of Youtube's energy expenditure have been broken down by channel and individual videos. [Those estimates](https://thefactsource.com/how-much-electricity-does-youtube-use/) imply that people consumed 45 times more energy watching Gangnam Style in 2019 than proof-of-stake Ethereum will use in a year.
## A greener Ethereum {#green-ethereum}
-While Ethereum's energy consumption has historically been substantial, there has been a major investment of developer time and intellect into transitioning from energy-hungry to energy-efficient block production. To quote [Bankless](http://podcast.banklesshq.com/), the best way to reduce the energy consumed by PoW is simply to "turn it off", which is the approach Ethereum has committed to take. At the same time, there is a substantial, growing and highly active "ReFi" (Regenerative Finance) community building on Ethereum. ReFi refers to applications that use DeFi components to build financial applicatiosn that have positive externalities benfiting the environment. This is part of a wider "Solarpunk" movement that is closely aligned with Ethereum and aims to couple technological advancement and environmental stewardship. The decentralized, permissionless, composable nature of Ethereum makes it the ideal base layer for the ReFi and solarpunk communities. After the merge, the technology and philosophy of Ethereum will finally reconcile and Ethereum should become an overall environmentally-positive technology.
+While Ethereum's energy consumption has historically been substantial, there has been a significant investment of developer time and intellect into transitioning from energy-hungry to energy-efficient block production. To quote [Bankless](http://podcast.banklesshq.com/), the best way to reduce the energy consumed by proof-of-work is simply to "turn it off", which is the approach Ethereum has committed to taking.
+
+At the same time, there is a substantial, growing, and highly active **regenerative finance (ReFI)** community building on Ethereum. ReFi applications use DeFi components to build financial applications that have positive externalities benefiting the environment. ReFi is part of a wider "Solarpunk" movement that is closely aligned with Ethereum and aims to couple technological advancement and environmental stewardship. The decentralized, permissionless, composable nature of Ethereum makes it the ideal base layer for the ReFi and solarpunk communities. After The Merge, the technology and philosophy of Ethereum will finally reconcile, and Ethereum should become an environmentally-positive technology.
If you think these stats are incorrect or can be made more accurate, please raise an issue or PR. These are estimates by the ethereum.org team made using publicly accessible information and the current Ethereum roadmap. These statements don't represent an official promise from the Ethereum Foundation.
From cb0bdab68084e859d9cc3ce403369121f73bca5e Mon Sep 17 00:00:00 2001
From: Joseph Cook <33655003+jmcook1186@users.noreply.github.com>
Date: Fri, 10 Jun 2022 20:54:47 +0100
Subject: [PATCH 033/244] incorporate TBs suggestionsto energy page
---
src/content/energy-consumption/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/energy-consumption/index.md b/src/content/energy-consumption/index.md
index a49a184a0bd..7e0dc44ae1c 100644
--- a/src/content/energy-consumption/index.md
+++ b/src/content/energy-consumption/index.md
@@ -13,7 +13,7 @@ Since its inception, Ethereum has aimed to implement a proof-of-stake consensus
## The Merge {#the-merge}
-A PoS blockchain known as the "Beacon Chain" has been running since November 2020 alongside the PoW Ethereum Mainnet. In 2022 several custom devnets have been merged with their own Beacon Chains to aid in debugging Ethereum clients in advance of the real merge. More recently, Ethereum developers have started merging public testnets (Kiln, Kintsugi, Ropsten) and shadow-forks (forks of Ethereum Mainnet) as the final stage of testing. Merging Ethereum Mainnet with the Beacon Chain is expected to happen in the second half of 2022. At the moment of the merge, Ethereum's PoW mining will be switched off, PoS consensus will take over, and the energy consumed by the network will drop to <0.05% of its pre-merge amount.
+A blockchain known as the "Beacon Chain" has been running the consensus algorithm since November 2020 alongside the PoW Ethereum Mainnet. In 2022, several proof-of-work devnets were launched and transitioned to proof-of-stake by merging with their own Beacon Chains. These helped client teams test software before moving to longer-lived networks. After these devnets, Ethereum developers launched new testnets for the community to use (Kiln & Kintsugi) and ran multiple shadow forks of existing testnets and mainnet. Now that these have stabilized, teams are moving to the final stages of testing: transitioning long-lived testnets (Ropsten, Goerli, Sepolia) to proof-of-stake. Merging Ethereum Mainnet with the Beacon Chain is expected to happen in the second half of 2022. At the moment of the merge, Ethereum's PoW mining will be switched off, PoS consensus will take over, and the energy consumed by the network will drop to <0.05% of its pre-merge amount.
## Why proof-of-stake is greener than proof-of-work {#why-pos-is-greener-than-pow}
From c8a1962ce7ad488627bce98d4ffd9741d5eb63e2 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 15:38:44 -0700
Subject: [PATCH 034/244] Update index.md
---
src/content/upgrades/merge/eth-issuance/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/upgrades/merge/eth-issuance/index.md b/src/content/upgrades/merge/eth-issuance/index.md
index e8df5456d4a..4f8ce460ce4 100644
--- a/src/content/upgrades/merge/eth-issuance/index.md
+++ b/src/content/upgrades/merge/eth-issuance/index.md
@@ -90,7 +90,7 @@ Net reduction in annual ETH issuance: ~89.4% (0.49% / 4.62% * 1
This flip side of ETH issuance is the rate at which ETH is burned. To execute a transaction on Ethereum, a minimum fee (known as a `base fee`) must be paid, which fluctuates depending on network activity in the moment. This fee is paid in ETH, is _required_ for the transaction to be considered valid, and is _burned_ in the process, removing it from circulation.
-This went live with the London upgrade Aug-4-2021, and will not change after the Merge.
+Fee burning went live with the London upgrade in August 2021, and will not change after the Merge.
On top of the fee burn implemented by the London upgrade, validators can also incur penalties for being offline, or worse they can be slashed for breaking specific rules that threaten network security. These penalties result in a reduction of ETH from that validators balance, which is not directly rewarded to any other account, effectively burning it from circulation.
From b8fd134f4d892c6d37c3e02467344dbf034d0f7e Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Fri, 10 Jun 2022 16:48:53 -0600
Subject: [PATCH 035/244] add example smart contract wallets
---
src/pages/layer-2.js | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index 958a4e83f31..9f999b56659 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -683,10 +683,12 @@ const Layer2Page = ({ data }) => {
NOTE: When bridging over and using layer 2, it is important to note
that you will control the address for you EOA account just like on
Ethereum Mainnet. However, if you are using a smart contract wallet,
- you will not have control over this address on a layer 2 by default
- unless deployed using `CREATE2`. If you are bridging or sending funds
- to a smart contract wallet, test this out first to make sure you
- control that address on the layer 2 you are using.
+ such as Gnosis Safe or{" "}
+ Argent, you will not have
+ control over this address on a layer 2 by default unless deployed
+ using `CREATE2`. If you are bridging or sending funds to a smart
+ contract wallet, test this out first to make sure you control that
+ address on the layer 2 you are using.
From 8033e597f275a2afe058c8b1ef7dd96ee68e15cc Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 15:58:04 -0700
Subject: [PATCH 036/244] Apply suggestions from code review
Co-authored-by: Joshua <62268199+minimalsm@users.noreply.github.com>
---
src/content/upgrades/merge/index.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index baf7c0a9aad..f5f30602a7d 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -12,7 +12,7 @@ summaryPoint4: With The Merge, Ethereum's energy consumption drops by 99.95%. We
---
-The Merge is one of the most significant and high-stakes upgrades in the history of Ethereum. Extensive testing and bug bounties have been underway for years to ensure a safe transition to proof-of-stake.
+The Merge is the most significant and high-stakes upgrade in the history of Ethereum. Extensive testing and bug bounties were undertaken to ensure a safe transition to proof-of-stake.
This process is in its final stages, with plans to undergo The Merge on a few public testnets before finally moving forward with Mainnet. If you’re as excited about The Merge as we are, follow the [EF Blog](https://blog.ethereum.org) or the client communication channels for the latest official word on _When Merge?_
@@ -23,13 +23,13 @@ The Merge represents the merger of the existing execution layer of Ethereum (the
It's important to remember that initially, the [Beacon Chain](/upgrades/beacon-chain/) (the new "consensus layer") shipped separately from [Mainnet](/glossary/#mainnet). Ethereum Mainnet (the "execution layer") continues to be secured by [proof-of-work](/developers/docs/consensus-mechanisms/pow/), even while the Beacon Chain runs in parallel using [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). The approaching Merge is when these two systems finally come together, and proof-of-work is replaced permanently by proof-of-stake.
-Imagine Ethereum is a space ship that isn’t quite ready for an interstellar voyage. With the Beacon Chain the community has built a new engine and a hardened hull. After significant testing, it's almost time to hot-swap in the new engine for the old mid-flight. This will merge the new more efficient engine into the existing ship, ready to put in some serious lightyears and take on the universe.
+Let's consider an example. Imagine Ethereum is a spaceship that isn't quite ready for an interstellar voyage. With the Beacon Chain, the community has built a new engine and a hardened hull. After significant testing, it's almost time to hot-swap the new engine for the old mid-flight. This will merge the new, more efficient engine into the existing ship, ready to put in some serious lightyears and take on the universe.
## Merging with Mainnet {#merging-with-mainnet}
-Since genesis, Mainnet has been secured by proof-of-work. This is the main Ethereum blockchain that we're all used to—it contains every transaction, every smart contract, and every balance since it began in July 2015.
+Since genesis, Mainnet has been secured by proof-of-work. This is the main Ethereum blockchain we're all used to—it contains every transaction, smart contract, and balance since it began in July 2015.
-During this growing history, developers have been hard at work preparing for an eventual transition away from proof-of-work, to proof-of-stake instead. On December 1, 2020 the Beacon Chain was born, which has since lived as a separate blockchain to Mainnet, running in parallel.
+During this growing history, developers have been hard at work preparing for an eventual transition away from proof-of-work to proof-of-stake instead. On December 1, 2020, the Beacon Chain was created, which has since existed as a separate blockchain to Mainnet, running in parallel.
The Beacon Chain has not been processing Mainnet transactions, and for all intents and purposed has simply been coming to consensus on the state of itself... which is great and all, but after extensive testing, the time for it to come to consensus on more than just itself is rapidly approaching.
From d3aaef4b4f059d16ae23c4de62020535beb7f520 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 16:09:37 -0700
Subject: [PATCH 037/244] remove numbering
---
src/content/upgrades/merge/index.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index f5f30602a7d..a1d78201f33 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -121,7 +121,7 @@ This will also set the stage for further scalability upgrades not possible under
## Misconceptions about The Merge {#misconceptions}
There are two general types of Ethereum nodes: nodes that can propose blocks, and nodes that don't.
@@ -138,7 +138,7 @@ The ability for anyone to run their own node is _absolutely essential_ to mainta
Gas fees are a product of network demand relative to the capacity of the network. The Merge deprecates the use of proof-of-work, transitioning to proof-of-stake for consensus, but does not significantly change any parameters that directly influence network capacity or throughput.
@@ -146,7 +146,7 @@ With a [rollup-centric roadmap](https://ethereum-magicians.org/t/a-rollup-centri
The "speed" of a transaction can be measured a few ways, including time to be included in a block, and also time to "finalization." Both of these change slightly, but not in a way that will be felt significantly by users.
@@ -158,7 +158,7 @@ Many dapps require a number of PoW block confirmations that take a period of tim
Staked ETH, staking rewards to date, and newly issued ETH immediately after The Merge will still be locked on the Beacon Chain without the ability to withdraw.
@@ -166,7 +166,7 @@ Withdrawal functionality is planned for the **Shanghai upgrade** to follow The M
This may seem counterintuitive to the above note that withdrawals are not enabled til the Shanghai upgrade, but validators WILL have immediate access to the fee rewards/MEV earned during block proposals.
@@ -176,7 +176,7 @@ ETH on the _execution layer_ (Mainnet as we know it) is accounted for separately
After the Shanghai upgrade enabled withdrawals, all validators will be incentivized to withdraw their staking balance above 32 ETH, as these funds to not add to yield, and are otherwise locked. Depending on the APR (determined by total ETH staked), they may be incentivized to exit their validator(s) to reclaim their entire balance, or potentially to stake even more using their rewards to earn more yield.
@@ -186,7 +186,7 @@ The APR is intentionally dynamic, allowing a market of stakers to find a balance
The APR for stakers is expected to increase post-merge. To understand by how much, it is important to recognize where this increase in APR is coming from. This does not come from an increase in protocol ETH issuance (ETH issuance after The Merge is in fact decreasing by ~90%), but is instead a reallocation of transaction fees that will start going to validators instead of miners.
@@ -196,7 +196,7 @@ Looking at recent blockchain activity, approximately 10% of all gas fees being p
An immense amount of work has been put into making sure the transition to proof-of-stake does not disrupt the network or its users.
From aaab9213ea536d853ed5bba2d11538894b61ccb0 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 16:24:51 -0700
Subject: [PATCH 038/244] Add header ids
---
.../tutorials/run-node-raspberry-pi/index.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/content/developers/tutorials/run-node-raspberry-pi/index.md b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
index c7c8971f079..9cac6e2fe65 100644
--- a/src/content/developers/tutorials/run-node-raspberry-pi/index.md
+++ b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
@@ -24,11 +24,11 @@ To use Ethereum on Arm to turn a Raspberry Pi into an Ethereum node, the followi
- A case with heatsink and fan
- USB keyboard, Monitor and HDMI cable (micro-HDMI) (Optional)
-## Why run Ethereum on ARM?
+## Why run Ethereum on ARM? {#why-run-ethereum-on-arm}
ARM boards are very affordable, flexible, small computers. They are good choices for running Ethereum nodes because they can be bought cheaply, configured so that all their resources focus just on the node, making them efficient, they consume low amounts of power and have are physically small so they can fit unobtrusively in any home. It is also very easy to spin up nodes because the Raspberry Pi's MicroSD can simply be flashed with a prebuilt image, with no downloading or building software required.
-## How does it work?
+## How does it work? {#how-does-it-work}
The Raspberry Pi's memory card is flashed with a prebuilt image. This image contains everything needed to run an Ethereum node. With a flashed card, all the user needs to do is power-on the Raspberry Pi. All the processes required to run the node are automatically started. This works because the memory card contains a Linux-based operating system (OS) on top of which system-level processes are automatically run that turn the unit into an Ethereum node.
@@ -36,11 +36,11 @@ Ethereum cannot be run using the popular Raspberry Pi Linux OS "Raspbian" becaus
**Images take care of all the necessary steps**, from setting up the environment and formatting the SSD disk to installing and running the Ethereum software as well as starting the blockchain synchronization.
-## Note on execution and consensus clients
+## Note on execution and consensus clients {#note-on-execution-and-consensus-clients}
The Ethereum on Arm documentation explains how to set up _either_ an execution client OR a consensus client, except for two Ethereum testnets (Kiln and Ropsten). This optionality is only possible in advance of Ethereum's upcoming transition from proof-of-work (PoW) to proof-of-stake (PoS) known as [The Merge](/upgrades/merge). After The Merge, it will not be possible to run execution and consensus clients separately - they must be run as a pair. Therefore, in this tutorial we will run a pair of execution and consensus clients together on an Ethereum testnet (Kiln).
-## The Kiln Raspberry Pi 4 Image
+## The Kiln Raspberry Pi 4 Image {#the-kiln-raspberry-pi-4-image}
Kiln is a public testnet specifically designed for testing The Merge. Ethereum on Arm developed an image allowing users to rapidly spin up a pair of Ethereum clients on this merge testnet. The Kiln merge has already happened, but the network is still live, so it can be used for this tutorial. Ether on Kiln has no real-world value.
@@ -50,7 +50,7 @@ Download the Raspberry Pi image from [Ethereum on Arm](https://ethereumonarm-my.
Note that for users that do not own a Raspberry Pi but do have an AWS account, there are ARM instances available that can run the same image. Instructions and the AWS image are available to download from Ethereum on Arm (https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html).
-## Flashing the MicroSD
+## Flashing the MicroSD {#flashing-the-microsd}
The MicroSD card that will be used for the Raspberry Pi should first be inserted into a desktop or laptop so it can be flashed. Then, the following terminal commands will flash the downloaded image onto the SD card:
@@ -71,7 +71,7 @@ sudo dd bs=1M if=ethonarm_kiln_22.03.01.img of=/dev/mmcblk0 conv=fdatasync statu
The card is now flashed, so it can be inserted into the Raspberry Pi.
-## Start the node
+## Start the node {#start-the-node}
With the SD card inserted into the Raspberry Pi, connect the ethernet cable and SSD then switch the power on. The OS will boot up and automatically start performing the preconfigured tasks that turn the Raspberry Pi into an Ethereum node, including installing and building the client software. This will probably take 10-15 minutes.
@@ -100,7 +100,7 @@ sudo journalctl -u lh-geth-beacon -f
The specific service names for every combination of clients are available at the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#id2). Theyu can be used to update the commands provided here for any combination.
-## Validators
+## Validators {#validators}
In order to run a validator it is first necessary to deposit 32 test-ether into the Kiln deposit contract. This means the user must have access to an account containing 32 ETH. This can be done by following the step-by-step guide on the [Kiln Launchpad](https://kiln.launchpad.ethereum.org/en/). Do this on a desktop/laptop, built do not generate keys - this can be done directly on the Raspberry Pi.
From 0acd8ecdeef30a1b9655d377df4c50ff772980ce Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 16:58:55 -0700
Subject: [PATCH 039/244] typo fixes
---
.../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/content/developers/tutorials/run-node-raspberry-pi/index.md b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
index 9cac6e2fe65..9a5c12e2f35 100644
--- a/src/content/developers/tutorials/run-node-raspberry-pi/index.md
+++ b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
@@ -98,7 +98,7 @@ sudo journalctl -u geth-lh -f
sudo journalctl -u lh-geth-beacon -f
```
-The specific service names for every combination of clients are available at the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#id2). Theyu can be used to update the commands provided here for any combination.
+The specific service names for every combination of clients are available at the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#id2). They can be used to update the commands provided here for any combination.
## Validators {#validators}
@@ -114,7 +114,7 @@ Keep the mnemonic phrase safe! The command above generated two files in the node
Once the deposit data file is available on the computer running the launchpad, it can be dragged and dropped onto the `+` on the launchpad screen. Follow the instructions on the screen to send a transaction to the deposit contract.
-Back on the Raspberry Pi, a validator cna be started. This requires importing the validator keys, setting the address to collect rewards, then starting the preconfigured validator process. The example below is for Lighthouse - instructions for other consensus clients are available on the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#lighthouse):
+Back on the Raspberry Pi, a validator can be started. This requires importing the validator keys, setting the address to collect rewards, then starting the preconfigured validator process. The example below is for Lighthouse—instructions for other consensus clients are available on the [Ethereum on Arm docs](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html#lighthouse):
```shell
# import the validator keys
@@ -132,7 +132,7 @@ Congratulations, you now have a full Ethereum node and validator running on a Ra
## Feedback appreciated {#feedback-appreciated}
We know the Raspberry Pi has a massive user base that could have a very positive impact on the health of the Ethereum network.
-Please dig into the details in this tutorial, try running on other testnets or even Ethereum Mainnet, check out the Ethereum on Arm Github, gvie feedback, raise issues and pull requests and help advance the technology and documentation!
+Please dig into the details in this tutorial, try running on other testnets or even Ethereum Mainnet, check out the Ethereum on Arm Github, give feedback, raise issues and pull requests and help advance the technology and documentation!
## References {#references}
From 4139b4ae0dd7ea5d94b81a12d053fd2e3f41a88b Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 16:59:11 -0700
Subject: [PATCH 040/244] Add shasum command
---
.../developers/tutorials/run-node-raspberry-pi/index.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/src/content/developers/tutorials/run-node-raspberry-pi/index.md b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
index 9a5c12e2f35..7dfef84494b 100644
--- a/src/content/developers/tutorials/run-node-raspberry-pi/index.md
+++ b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
@@ -46,7 +46,13 @@ Kiln is a public testnet specifically designed for testing The Merge. Ethereum o
The Kiln Raspberry Pi 4 image is a "plug and play" image that automatically installs and sets up both the execution and consensus clients, configuring them to talk to each other and connect to the Kiln network. All the user needs to do is start their processes using a simple command. The image contains four execution clients (Geth, Nethermind, Besu and Erigon) and four consensus clients (Lighthouse, Prysm, Nimbus, Teku) that the user can choose from.
-Download the Raspberry Pi image from [Ethereum on Arm](https://ethereumonarm-my.sharepoint.com/:u:/p/dlosada/ES56R_SuvaVFkiMO1Tgnf6kB7lEbBfla5c2c18E3WQRJzA?download=1) and verify the file with the following SH256 hash: `485cf36128ca60a41b5de82b5fee3ee46b7c479d0fc5dfa5b9341764414c4c57`.
+Download the Raspberry Pi image from [Ethereum on Arm](https://ethereumonarm-my.sharepoint.com/:u:/p/dlosada/ES56R_SuvaVFkiMO1Tgnf6kB7lEbBfla5c2c18E3WQRJzA?download=1) and verify the SHA256 hash:
+
+```sh
+# From directory containing the downloaded image
+shasum -a 256 ethonarm_kiln_22.03.01.img.zip
+# Hash should output: 485cf36128ca60a41b5de82b5fee3ee46b7c479d0fc5dfa5b9341764414c4c57
+```
Note that for users that do not own a Raspberry Pi but do have an AWS account, there are ARM instances available that can run the same image. Instructions and the AWS image are available to download from Ethereum on Arm (https://ethereum-on-arm-documentation.readthedocs.io/en/latest/kiln/kiln-testnet.html).
From fa5bedda9f9c5dc4b43e1c246206f53045fbcda0 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 17:55:52 -0700
Subject: [PATCH 041/244] Updates copy for upgrades
Merge related to start
---
src/intl/en/page-upgrades-index.json | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/src/intl/en/page-upgrades-index.json b/src/intl/en/page-upgrades-index.json
index b618f80070f..a88b7e2ee89 100644
--- a/src/intl/en/page-upgrades-index.json
+++ b/src/intl/en/page-upgrades-index.json
@@ -16,7 +16,7 @@
"page-upgrade-article-title-rollup-roadmap": "A rollup-centric roadmap",
"page-upgrades-beacon-chain-btn": "More on the Beacon Chain",
"page-upgrades-beacon-chain-date": "The Beacon Chain went live on December 1, 2020.",
- "page-upgrades-beacon-chain-desc": "The Beacon Chain brought staking to Ethereum, laid the groundwork for future upgrades, and will eventually coordinate the new system.",
+ "page-upgrades-beacon-chain-desc": "The Beacon Chain brought staking to Ethereum, laid the groundwork for future upgrades, and will soon coordinate the new system.",
"page-upgrades-beacon-chain-estimate": "The Beacon Chain is live",
"page-upgrades-beacon-chain-title": "The Beacon Chain",
"page-upgrades-bug-bounty": "View the bug bounty program",
@@ -47,7 +47,7 @@
"page-upgrades-docking": "The Merge",
"page-upgrades-merge-answer-1": "The Merge is when Mainnet begins using the Beacon Chain for consensus, and proof-of-work is turned off, sometime in 2022.",
"page-upgrades-merge-btn": "More on The Merge",
- "page-upgrades-merge-desc": "Mainnet Ethereum will need to 'merge' with the Beacon Chain at some point. This will enable staking for the entire network and signal the end of energy-intensive mining.",
+ "page-upgrades-merge-desc": "Mainnet Ethereum will soon 'merge' with the proof-of-stake Beacon Chain. This will signal the end of energy-intensive mining.",
"page-upgrades-merge-estimate": "Estimate: 2022",
"page-upgrades-merge-mainnet": "What's Mainnet?",
"page-upgrades-merge-mainnet-eth2": "Merging Mainnet and the Beacon Chain",
@@ -61,7 +61,7 @@
"page-upgrades-index-staking": "Staking is here",
"page-upgrades-index-staking-desc": "Key to the Ethereum upgrades is the introduction of staking. If you want to use your ETH to help secure the Ethereum network, make sure you follow these steps.",
"page-upgrades-index-staking-learn": "Learn about staking",
- "page-upgrades-index-staking-learn-desc": "The Beacon Chain will bring staking to Ethereum. This means if you have ETH, you can do a public good by securing the network and earn more ETH in the process.",
+ "page-upgrades-index-staking-learn-desc": "The Beacon Chain brought staking to Ethereum. This means if you have ETH, you can do a public good by securing the network and earn more ETH in the process.",
"page-upgrades-index-staking-step-1": "1. Set up with the launchpad",
"page-upgrades-index-staking-step-1-btn": "Visit staking launchpad",
"page-upgrades-index-staking-step-1-desc": "To stake on Ethereum you'll need to use the launchpad - this will walk you through the process.",
@@ -91,7 +91,7 @@
"page-upgrades-question-4-answer-3": "After The Merge, validators will secure the entire network via proof-of-stake.",
"page-upgrades-question-4-answer-6": "Anyone can become a validator by staking their ETH.",
"page-upgrades-question-4-answer-7": "More on staking",
- "page-upgrades-question-4-answer-8": "The Beacon Chain and shard chain upgrades will not disrupt the execution layer (Mainnet) as they are being built out separately.",
+ "page-upgrades-question-4-answer-8": "The Beacon Chain and sharding upgrades will not disrupt the execution layer (Mainnet) as they are being built out separately.",
"page-upgrades-question-4-title": "What is the execution layer?",
"page-upgrades-question-4-desc": "The Ethereum Mainnet you transact on today has previously been referred to as 'Eth1.' This term is being phased out in favor of the 'execution layer'.",
"page-upgrades-question-5-answer-1": "To become a full validator on the network, you'll need to stake 32 ETH. If you don't have that much, or aren't willing to stake that much, you can join staking pools. These pools will let you stake less and earn fractions of the total rewards.",
@@ -155,10 +155,10 @@
"page-upgrades-secure-desc": "Ethereum needs to be more secure. As the adoption of Ethereum grows, the protocol needs to become more secure against all forms of attack.",
"page-upgrades-shard-button": "More on the shard chains",
"page-upgrades-shard-date": "Shard chains should follow The Merge, sometime in 2023.",
- "page-upgrades-shard-desc": "Shard chains will expand Ethereum's capacity to process transactions and store data. The shards themselves will gain more features over time, rolled out in multiple phases.",
- "page-upgrades-shard-estimate": "Estimate: 2023",
- "page-upgrades-shard-lower": "More on shard chains",
- "page-upgrades-shard-title": "Shard chains",
+ "page-upgrades-shard-desc": "Data sharding will expand Ethereum's capacity to store data, and work harmoniously with L2s to scale throughput and reduce network fees. Sharding will be rolled out in multiple stages.",
+ "page-upgrades-shard-estimate": "Estimate: 2023-2024",
+ "page-upgrades-shard-lower": "More on data sharding",
+ "page-upgrades-shard-title": "Data sharding",
"page-upgrades-stay-up-to-date": "Stay up to date",
"page-upgrades-stay-up-to-date-desc": "Get the latest from the researchers and developers working on the Ethereum upgrades.",
"page-upgrades-sustainable-desc": "Ethereum needs to be better for the environment. The technology today requires too much computing power and energy.",
@@ -193,9 +193,9 @@
"page-upgrades-why-cant-we-just-use-eth2-mental-models-description": "One major problem with the Eth2 branding is that it creates a broken mental model for new users of Ethereum. They intuitively think that Eth1 comes first and Eth2 comes after. Or that Eth1 ceases to exist once Eth2 exists. Neither of these is true. By removing Eth2 terminology, we save all future users from navigating this confusing mental model.",
"page-upgrades-why-cant-we-just-use-eth2-inclusivity-title": "Inclusivity",
"page-upgrades-why-cant-we-just-use-eth2-inclusivity-description": "As the roadmap for Ethereum has evolved, Ethereum 2.0 has become an inaccurate representation of Ethereum’s roadmap. Being careful and accurate in our word choice allows content on Ethereum to be understood by the broadest audience possible.",
- "page-upgrades-why-cant-we-just-use-eth2-scam-prevention-title": "Scam Prevention",
+ "page-upgrades-why-cant-we-just-use-eth2-scam-prevention-title": "Scam prevention",
"page-upgrades-why-cant-we-just-use-eth2-scam-prevention-description": "Unfortunately, malicious actors have attempted to use the Eth2 misnomer to scam users by telling them to swap their ETH for ‘ETH2’ tokens or that they must somehow migrate their ETH before the Eth2 upgrade. We hope this updated terminology will bring clarity to eliminate this scam vector and help make the ecosystem safer.",
- "page-upgrades-why-cant-we-just-use-eth2-staking-clarity-title": "Staking Clarity",
+ "page-upgrades-why-cant-we-just-use-eth2-staking-clarity-title": "Staking clarity",
"page-upgrades-why-cant-we-just-use-eth2-staking-clarity-description": "Some staking operators have also represented ETH staked on the Beacon Chain with the ‘ETH2’ ticker. This creates potential confusion, given that users of these services are not actually receiving an ‘ETH2’ token. No ‘ETH2’ token exists; it simply represents their share in that specific providers’ stake.",
"page-upgrades-what-to-do": "What do you need to do?",
"page-upgrades-what-to-do-desc": "If you're a dapp user or ETH holder, you don't need to do anything. If you're a developer or want to start staking, there are ways you can get involved today.",
From 6e91edaa59a8a3bf3c86ff77977752b0aa47a4aa Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 17:56:12 -0700
Subject: [PATCH 042/244] remove deprecated/unused strings
---
src/intl/en/common.json | 1 -
...page-upgrades-get-involved-bug-bounty.json | 1 -
src/intl/en/page-upgrades-index.json | 20 -------------------
src/intl/en/page-upgrades-vision.json | 10 ----------
4 files changed, 32 deletions(-)
diff --git a/src/intl/en/common.json b/src/intl/en/common.json
index e8930bec70a..737b95241cd 100644
--- a/src/intl/en/common.json
+++ b/src/intl/en/common.json
@@ -217,7 +217,6 @@
"security": "Security",
"see-contributors": "See contributors",
"set-up-local-env": "Set up local environment",
- "shard-chains": "Shard chains",
"show-all": "Show all",
"show-less": "Show less",
"site-description": "Ethereum is a global, decentralized platform for money and new kinds of applications. On Ethereum, you can write code that controls money, and build applications accessible anywhere in the world.",
diff --git a/src/intl/en/page-upgrades-get-involved-bug-bounty.json b/src/intl/en/page-upgrades-get-involved-bug-bounty.json
index ff4285b50f7..7c04ba72ca8 100644
--- a/src/intl/en/page-upgrades-get-involved-bug-bounty.json
+++ b/src/intl/en/page-upgrades-get-involved-bug-bounty.json
@@ -50,7 +50,6 @@
"page-upgrades-bug-bounty-quality-repro-desc": ": A Proof of Concept (POC) must be included to be eligible for rewards. Please include test code, scripts and detailed instructions. The easier it is for us to reproduce and verify the vulnerability, the higher the reward.",
"page-upgrades-bug-bounty-questions": "Questions?",
"page-upgrades-bug-bounty-rules": "Read rules",
- "page-upgrades-bug-bounty-shard-chains": "shard chains",
"page-upgrades-bug-bounty-slogan": "Bug Bounty Program",
"page-upgrades-bug-bounty-specs": "Consensus Layer Specifications",
"page-upgrades-bug-bounty-execution-specs": "Execution Layer Specifications",
diff --git a/src/intl/en/page-upgrades-index.json b/src/intl/en/page-upgrades-index.json
index a88b7e2ee89..7ca51e9bdf5 100644
--- a/src/intl/en/page-upgrades-index.json
+++ b/src/intl/en/page-upgrades-index.json
@@ -22,26 +22,6 @@
"page-upgrades-bug-bounty": "View the bug bounty program",
"page-upgrades-clients": "Check out the consensus clients (previously known as 'Eth2' clients)",
"page-staking-deposit-contract-title": "Check the deposit contract address",
- "page-upgrades-diagram-ethereum-mainnet": "Ethereum Mainnet",
- "page-upgrades-diagram-h2": "How the upgrades fit together",
- "page-upgrades-diagram-link-1": "More on proof of work",
- "page-upgrades-diagram-link-2": "More on shard chains",
- "page-upgrades-diagram-mainnet": "Mainnet",
- "page-upgrades-diagram-p": "Ethereum Mainnet will continue to exist in its current form for a while. This means the Beacon Chain and shard upgrades won't disrupt the network.",
- "page-upgrades-diagram-p-1": "Mainnet will eventually merge with the new system introduced by the Beacon Chain.",
- "page-upgrades-diagram-p-2": "The Beacon Chain will become the conductor of Ethereum, coordinating validators and setting the pace for block creation.",
- "page-upgrades-diagram-p-3": "At first, it will exist separately from Mainnet and manage validators - it will have nothing to do with smart contracts, transactions, or accounts.",
- "page-upgrades-diagram-p-4": "Shards will provide lots of extra data to help increase the amount of transactions Mainnet can handle. They'll be coordinated by the Beacon Chain.",
- "page-upgrades-diagram-p-5": "But all transactions will still rely on Mainnet, which will continue to exist as we know it today – secured by proof-of-work and miners.",
- "page-upgrades-diagram-p-6": "Mainnet will merge with the proof-of-stake system, coordinated by the Beacon Chain.",
- "page-upgrades-diagram-p-8": "This will turn Mainnet into a shard within the new system. Miners will no longer be needed as all of Ethereum will be secured by validators.",
- "page-upgrades-diagram-p10": "Ethereum scaling is not a migration or a single thing. It describes a set of upgrades being worked on to unlock Ethereum's true potential. This is how they all fit together.",
- "page-upgrades-diagram-scroll": "Scroll to explore – tap for more information.",
- "page-upgrades-diagram-shard": "Shard (1)",
- "page-upgrades-diagram-shard-1": "Shard (...)",
- "page-upgrades-diagram-shard-2": "Shard (2)",
- "page-upgrades-diagram-shard-3": "Shard (...)",
- "page-upgrades-diagram-validators": "More on validators",
"page-upgrades-dive": "Dive into the vision",
"page-upgrades-dive-desc": "How are we going to make Ethereum more scalable, secure, and sustainable? All while keeping Ethereum's core ethos of decentralization.",
"page-upgrades-docking": "The Merge",
diff --git a/src/intl/en/page-upgrades-vision.json b/src/intl/en/page-upgrades-vision.json
index 39a2459413f..a27b8d6c4c8 100644
--- a/src/intl/en/page-upgrades-vision.json
+++ b/src/intl/en/page-upgrades-vision.json
@@ -2,16 +2,9 @@
"page-upgrades-vision-2014": "View a 2014 blog post detailing proof of stake",
"page-upgrades-vision-2021": "View a 2021 blog post on the Ethereum roadmap evolution",
"page-upgrades-vision-2021-updates": "View a 2021 blog post on the Ethereum Protocol Updates",
- "page-upgrades-vision-beacon-chain": "The beacon chain",
- "page-upgrades-vision-beacon-chain-btn": "More on the Beacon Chain",
- "page-upgrades-vision-beacon-chain-date": "The Beacon Chain is live",
- "page-upgrades-vision-beacon-chain-desc": "The Beacon Chain brought staking to Ethereum, laid the groundwork for future upgrades, and will eventually coordinate the new system.",
- "page-upgrades-vision-beacon-chain-upper": "Beacon Chain",
"page-upgrades-vision-desc-1": "Ethereum needs to reduce network congestion and improve speeds to better service a global user base.",
"page-upgrades-vision-desc-2": "Running a node is getting harder as the network grows. This will only get harder with efforts to scale the network.",
"page-upgrades-vision-desc-3": "Ethereum uses too much electricity. The technology that keeps the network secure needs to be more sustainable.",
- "page-upgrades-vision-merge-date": "Estimate: 2022",
- "page-upgrades-vision-merge-desc": "Mainnet Ethereum will need to \"merge\" with the Beacon Chain at some point. This will enable staking for the entire network and signal the end of energy-intensive mining.",
"page-upgrades-vision-ethereum-node": "More on nodes",
"page-upgrades-vision-explore-upgrades": "Explore the upgrades",
"page-upgrades-vision-future": "A digital future on a global scale",
@@ -32,9 +25,6 @@
"page-upgrades-vision-security-desc-10": "Staking also means you don't need to invest in elite hardware to 'run' an Ethereum node. This should encourage more people to become a validator, increasing the network's decentralization and decreasing the attack surface area.",
"page-upgrades-vision-security-staking": "Stake ETH",
"page-upgrades-vision-security-validator": "You can become a validator by staking your ETH.",
- "page-upgrades-vision-shard-chains": "shard chains",
- "page-upgrades-vision-shard-date": "Estimate: 2021",
- "page-upgrades-vision-shard-desc-4": "Shard chains will spread the load of the network into 64 new blockchains. Shards have the potential to drastically improve transaction speed - up to 100,000 per second.",
"page-upgrades-vision-shard-upgrade": "More on shard chains",
"page-upgrades-vision-staking-lower": "More on staking",
"page-upgrades-vision-subtitle": "Grow Ethereum until it's powerful enough to help all of humanity.",
From b1da527d2e4206c6eed10c185269812e52a1ff93 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Fri, 10 Jun 2022 21:40:18 -0600
Subject: [PATCH 043/244] rewording note
---
src/pages/layer-2.js | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index 9f999b56659..ea3564f85c5 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -681,14 +681,17 @@ const Layer2Page = ({ data }) => {
NOTE: When bridging over and using layer 2, it is important to note
- that you will control the address for you EOA account just like on
- Ethereum Mainnet. However, if you are using a smart contract wallet,
- such as Gnosis Safe or{" "}
+ that you will control the address for your{" "}
+ EOA account (an account where only a
+ single private key controls the account) just like on Ethereum
+ Mainnet. However, if you are using a{" "}
+ contract account, such
+ as Gnosis Safe or{" "}
Argent, you will not have
- control over this address on a layer 2 by default unless deployed
- using `CREATE2`. If you are bridging or sending funds to a smart
- contract wallet, test this out first to make sure you control that
- address on the layer 2 you are using.
+ control over this address on a layer 2 until you redeploy your
+ contract account to that address on the layer 2. If you are bridging
+ or sending funds to a contract account, and you do not control this
+ address for the contract account, your funds may be lost.
From a65ff11e67b11295571c642c2c1ad940638df2cb Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 22:18:01 -0700
Subject: [PATCH 044/244] Update /upgrades copy premerge
---
src/intl/en/page-upgrades-index.json | 34 +++++------
src/pages/upgrades/index.js | 86 ++++++++++++++++------------
2 files changed, 67 insertions(+), 53 deletions(-)
diff --git a/src/intl/en/page-upgrades-index.json b/src/intl/en/page-upgrades-index.json
index 7ca51e9bdf5..2386b02283d 100644
--- a/src/intl/en/page-upgrades-index.json
+++ b/src/intl/en/page-upgrades-index.json
@@ -5,8 +5,8 @@
"consensus-client-prysm-logo-alt": "Prysm logo",
"consensus-client-teku-logo-alt": "Teku logo",
"consensus-client-under-review": "Review and audit in progress",
- "page-upgrades-answer-1": "Think of the changes being rolled out as a set of upgrades being added to improve the Ethereum we use today. These upgrades included the creation of a new chain called the Beacon Chain, and will introduce new chains known as 'shards' in the future.",
- "page-upgrades-answer-2": "Some upgrades are separate from the Ethereum Mainnet we use today but won't replace it. Instead Mainnet will 'merge' with this parallel system that's being added over time.",
+ "page-upgrades-answer-1": "Think of the changes being rolled out as a set of upgrades being added to improve the Ethereum we use today. These upgrades included the creation of a new chain called the Beacon Chain, which will soon act as the consensus engine for the entire network.",
+ "page-upgrades-answer-2": "Despite the Beacon Chain starting as a separate chain, soon the existing Mainnet will be 'merged' with this new proof-of-stake consensus layer.",
"page-upgrades-answer-4": "In other words the Ethereum we use today will eventually embody all the features that we're aiming towards in the Ethereum vision.",
"page-upgrade-article-title-two-point-oh": "Two Point Oh: The Beacon Chain",
"page-upgrade-article-title-beacon-chain-explainer": "The Beacon Chain Ethereum 2.0 explainer you need to read first",
@@ -25,7 +25,7 @@
"page-upgrades-dive": "Dive into the vision",
"page-upgrades-dive-desc": "How are we going to make Ethereum more scalable, secure, and sustainable? All while keeping Ethereum's core ethos of decentralization.",
"page-upgrades-docking": "The Merge",
- "page-upgrades-merge-answer-1": "The Merge is when Mainnet begins using the Beacon Chain for consensus, and proof-of-work is turned off, sometime in 2022.",
+ "page-upgrades-merge-answer-1": "The Merge is when Mainnet begins using the Beacon Chain for consensus, and proof-of-work is turned off, coming soon.",
"page-upgrades-merge-btn": "More on The Merge",
"page-upgrades-merge-desc": "Mainnet Ethereum will soon 'merge' with the proof-of-stake Beacon Chain. This will signal the end of energy-intensive mining.",
"page-upgrades-merge-estimate": "Estimate: 2022",
@@ -49,24 +49,24 @@
"page-upgrades-index-staking-step-2-btn": "Confirm deposit contract address",
"page-upgrades-index-staking-step-2-desc": "Before you stake your ETH, be sure to check you've got the right address. You must have gone through the launchpad before doing this.",
"page-upgrades-index-staking-sustainability": "More sustainable",
- "page-upgrades-just-docking": "More on The Merge",
"page-upgrades-meta-desc": "An overview of the Ethereum upgrades and the vision they hope to make a reality.",
"page-upgrades-meta-title": "Ethereum upgrades (formerly 'Eth2')",
- "page-upgrades-miners": "More on miners",
- "page-upgrades-more-on-upgrades": "More on the Ethereum upgrades",
"page-upgrades-proof-of-stake": "proof-of-stake",
"page-upgrades-proof-of-work": "proof-of-work",
"page-upgrades-proof-stake-link": "More on proof of stake",
"page-upgrades-question-1-title": "When will the upgrades ship?",
"page-upgrades-question-1-desc": "Ethereum is being upgraded progressively; the upgrades are distinct with different ship dates.",
"page-upgrades-question-2-title": "Is the Beacon Chain a separate blockchain?",
- "page-upgrades-question-2-desc": "It's not accurate to think of these upgrades as a separate blockchain.",
- "page-upgrades-question-3-answer-2": "The Merge and shard chain upgrades may impact dapp developers. But the specifications have not been finalized yet, so there's no immediate action required.",
+ "page-upgrades-question-2-desc": "It's not accurate to think of this upgrade as a separate blockchain.",
+ "page-upgrades-question-3-answer-2a": "The Merge specifications have been finalized, and is designed to have minimal impact on dapp developers.",
+ "page-upgrades-question-3-answer-2a-link": "The Merge and dapp developers",
+ "page-upgrades-question-3-answer-2b": "Sharding plans are still being developed, but will be designed with layer 2 rollups in mind.",
+ "page-upgrades-layer-2-rollups": "More on layer 2 rollups",
"page-upgrades-question-3-answer-3": "Talk to the Ethereum research and development team over at ethresear.ch.",
"page-upgrades-question-3-answer-3-link": "Visit ethresear.ch",
"page-upgrades-question-3-desc": "You don't have to do anything right now to prepare for the upgrades.",
"page-upgrades-question-3-title": "How do I prepare for the upgrades?",
- "page-upgrades-question-4-answer-1": "Whenever you send a transaction or use a dapp today, you're using the execution layer, or Mainnet. This is the Ethereum that is secured by miners.",
+ "page-upgrades-question-4-answer-1": "Whenever you send a transaction or use a dapp today, you're using the execution layer, also known as Mainnet.",
"page-upgrades-question-4-answer-2": "Mainnet will continue to run as normal until The Merge.",
"page-upgrades-question-4-answer-3": "After The Merge, validators will secure the entire network via proof-of-stake.",
"page-upgrades-question-4-answer-6": "Anyone can become a validator by staking their ETH.",
@@ -77,12 +77,14 @@
"page-upgrades-question-5-answer-1": "To become a full validator on the network, you'll need to stake 32 ETH. If you don't have that much, or aren't willing to stake that much, you can join staking pools. These pools will let you stake less and earn fractions of the total rewards.",
"page-upgrades-question-5-desc": "You'll need to use the staking launchpad or join a staking pool.",
"page-upgrades-question-5-title": "How do I stake?",
- "page-upgrades-question-6-answer-1": "For now, there's no actions to take. But we recommend you stay up to date with developments on The Merge and shard chain upgrades.",
"page-upgrades-question-6-answer-3": "Danny Ryan of the Ethereum foundation regularly updates the community:",
"page-upgrades-question-6-answer-4": "Ben Edgington of ConsenSys has a weekly newsletter about the Ethereum upgrades:",
"page-upgrades-question-6-answer-5": "You can also join the discussion on Ethereum research and development at ethresear.ch.",
- "page-upgrades-question-6-desc": "Your dapp won't be affected by any imminent upgrades. However future upgrades may require some changes.",
"page-upgrades-question-6-title": "What do I need to do with my dapp?",
+ "page-upgrades-question-6-desc": "The Merge has been designed with the goal of minimizing impact on dapp developers, though there are a couple things work noting.",
+ "page-upgrades-question-6-answer-1": "A few changes are coming with The Merge that can impact certain types of applications. This includes block structure and timing, a few opcode changes, sources of on-chain randomness and the concept of epoch finalization.",
+ "page-upgrades-question-6-answer-1-link": "How The Merge Impacts Ethereum's Application Layer",
+ "page-upgrades-question-6-answer-2": "Most applications will be unaffected, but developers are recommended to stay up to date on the latest with The Merge.",
"page-upgrades-question-7-desc": "Many different teams from all over the community are working on the various Ethereum upgrades.",
"page-upgrades-question-7-lighthouse": "Lighthouse",
"page-upgrades-question-7-lighthouse-lang": "(Rust implementation)",
@@ -99,7 +101,7 @@
"page-upgrades-question-7-clients": "Learn more about Ethereum clients",
"page-upgrades-question-8-answer-1": "The Ethereum upgrades will help Ethereum scale in a decentralized way, while maintaining security, and increasing sustainability.",
"page-upgrades-question-8-answer-2": "Perhaps the most obvious problem is that Ethereum needs to be able to handle more than 15-45 transactions per second. But the upgrades also address some other problems with Ethereum today.",
- "page-upgrades-question-8-answer-3": "The network is in such high demand that it's making Ethereum expensive to use. Nodes in the network are struggling under the size of Ethereum and the amount of data their computers are having to process. And the underlying algorithm that keeps Ethereum secure and decentralized is energy intensive and needs to be greener.",
+ "page-upgrades-question-8-answer-3": "The network is in such high demand that it's making Ethereum expensive to use. Nodes in the network are struggling under the size of Ethereum and the amount of data their computers are having to process. The original algorithm that underlies Ethereum security and decentralization is energy intensive and needs to be greener.",
"page-upgrades-question-8-answer-4": "A lot of what's changing has always been on the Ethereum roadmap, even since 2015. But current conditions are making the need for the upgrades even greater.",
"page-upgrades-question-8-answer-6": "Explore the Ethereum vision",
"page-upgrades-question-8-desc": "The Ethereum we use today needs to offer a better experience to end users and network participants.",
@@ -120,8 +122,8 @@
"page-upgrades-question-10-answer-2": "But if you've followed the discussions, here's how the upgrades fit into technical roadmaps, and a bit on how they're changing.",
"page-upgrades-question-10-answer-3": "Phase 0 described the work to get the Beacon Chain live.",
"page-upgrades-question-10-answer-5": "Phase 1 originally focused on implementing the shard chains, but prioritization has shifted to 'The Merge' which is the next planned upgrade.",
- "page-upgrades-question-10-answer-6": "Phase 1.5 was originally planned to follow shard implementations, when Mainnet would be added as the last shard to the Beacon Chain. To expedite the transition away from proof-of-work mining, Mainnet will instead represent the first shard to connect with the Beacon Chain. This is now known as 'The Merge' and will be a significant step towards a greener Ethereum.",
- "page-upgrades-question-10-answer-7": "Though the plans around Phase 2 have been a point of intense research and discussion, with The Merge planned before shard chains, this will allow for continued reassessment as to the needs of Ethereum development moving forward. Given a rollup-centric roadmap, the immediate necessity of shard chains is debatable.",
+ "page-upgrades-question-10-answer-6": "Phase 1.5 was originally planned to follow shard implementations, when Mainnet would be added as the last shard to the Beacon Chain. With rollup technology progressing, the transition away from proof-of-work was expedited. Mainnet will instead be 'merged' into the Beacon Chain and remain as the execution layer of Ethereum. This will be a significant step towards a greener Ethereum.",
+ "page-upgrades-question-10-answer-7": "The plans around Phase 2 have been a point of intense research and discussion. With The Merge planned before sharding, and the advancements in layer 2 solutions, plans have shifted to provide a more simplified form of data sharding to maximize rollup efficiency. Current layer 2s are enabling the ability to scale transaction execution, and data sharding will help make storing the proofs for this data on layer 1 in a cheap and scalable manner. This will continue to undergo reassessment and research as progress is made.",
"page-upgrades-question-10-answer-8": "More on a rollup-centric roadmap",
"page-upgrades-question-11-title": "Can I buy Eth2?",
"page-upgrades-question-11-desc": "No. There is no Eth2 token and your ETH will not change after The Merge.",
@@ -134,7 +136,7 @@
"page-upgrades-secure": "More secure",
"page-upgrades-secure-desc": "Ethereum needs to be more secure. As the adoption of Ethereum grows, the protocol needs to become more secure against all forms of attack.",
"page-upgrades-shard-button": "More on the shard chains",
- "page-upgrades-shard-date": "Shard chains should follow The Merge, sometime in 2023.",
+ "page-upgrades-shard-date": "Data sharding will follow The Merge in multiple phases, sometime in 2023-2024.",
"page-upgrades-shard-desc": "Data sharding will expand Ethereum's capacity to store data, and work harmoniously with L2s to scale throughput and reduce network fees. Sharding will be rolled out in multiple stages.",
"page-upgrades-shard-estimate": "Estimate: 2023-2024",
"page-upgrades-shard-lower": "More on data sharding",
@@ -152,7 +154,7 @@
"page-upgrades-upgrades-aria-label": "Ethereum upgrades menu",
"page-upgrades-upgrades-beacon-chain": "The Beacon Chain",
"page-upgrades-upgrades-docking": "The Merge",
- "page-upgrades-upgrades-guide": "Guide to Ethereum upgrades",
+ "page-upgrades-energy-consumption": "More on Ethereum energy consumption",
"page-upgrades-upgrades-shard-chains": "The shard chains",
"page-upgrades-upgrading": "Upgrading Ethereum to radical new heights",
"page-upgrades-vision": "The vision",
diff --git a/src/pages/upgrades/index.js b/src/pages/upgrades/index.js
index 0c97229345f..486e2b4c82c 100644
--- a/src/pages/upgrades/index.js
+++ b/src/pages/upgrades/index.js
@@ -502,9 +502,6 @@ const Eth2IndexPage = ({ data }) => {
From b24097af263266c88196cd48b35eca150671a95a Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 22:30:06 -0700
Subject: [PATCH 045/244] update sharding path
---
redirects.json | 6 +++++-
src/content/upgrades/{shard-chains => sharding}/index.md | 0
2 files changed, 5 insertions(+), 1 deletion(-)
rename src/content/upgrades/{shard-chains => sharding}/index.md (100%)
diff --git a/redirects.json b/redirects.json
index 8fd75313911..294ffec2098 100644
--- a/redirects.json
+++ b/redirects.json
@@ -289,7 +289,11 @@
},
{
"fromPath": "/*/eth2/shard-chains/",
- "toPath": "/:splat/upgrades/shard-chains/"
+ "toPath": "/:splat/upgrades/sharding/"
+ },
+ {
+ "fromPath": "/*/upgrades/shard-chains/",
+ "toPath": "/:splat/upgrades/sharding/"
},
{
"fromPath": "/*/eth2/staking/",
diff --git a/src/content/upgrades/shard-chains/index.md b/src/content/upgrades/sharding/index.md
similarity index 100%
rename from src/content/upgrades/shard-chains/index.md
rename to src/content/upgrades/sharding/index.md
From 1d01fc9c40c3d2c6b57d06ccfed2092b2492ec1c Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Fri, 10 Jun 2022 22:30:56 -0700
Subject: [PATCH 046/244] updates react /sharding links
---
src/intl/en/page-layer-2.json | 2 +-
src/pages/layer-2.js | 2 +-
src/pages/upgrades/index.js | 11 ++++++-----
src/pages/upgrades/vision.js | 4 ++--
src/templates/upgrade.tsx | 2 +-
5 files changed, 11 insertions(+), 10 deletions(-)
diff --git a/src/intl/en/page-layer-2.json b/src/intl/en/page-layer-2.json
index dd3e9224482..ed32953d1fa 100644
--- a/src/intl/en/page-layer-2.json
+++ b/src/intl/en/page-layer-2.json
@@ -99,7 +99,7 @@
"layer-2-faq-question-2-description-3": "At the moment, most zk-rollups are application specific, in contrast with optimistic rollups which have largely been generalizable.",
"layer-2-faq-question-2-description-4": "More info on optimistic rollups and zero-knowledge rollups.",
"layer-2-faq-question-3-title": "Is scaling at layer 1 possible?",
- "layer-2-faq-question-3-description-1": "Yes. Currently in the Ethereum roadmap there are plans for shard chains. While these are in the roadmap, further scaling through layer 2 networks is still necessary. More info on sharding.",
+ "layer-2-faq-question-3-description-1": "Yes. Currently in the Ethereum roadmap there are plans for shard chains. While these are in the roadmap, further scaling through layer 2 networks is still necessary. More info on sharding.",
"layer-2-faq-question-4-title": "What are the risks with layer 2?",
"layer-2-faq-question-4-description-1": "Layer 2 projects contain additional risks compared to holding funds and transacting directly on Ethereum Mainnet. For instance, sequencers may go down, leading you to have to wait to access funds.",
"layer-2-faq-question-4-description-2": "We encourage you to do your own research before transferring significant funds to a layer 2. For more information on the technology, risks, and trust assumptions of layer 2s, we recommend checking out L2BEAT, which provides a comprehensive risk assessment framework of each project.",
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index 36504dcd83b..fe03248ce86 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -883,7 +883,7 @@ const Layer2Page = ({ data }) => {
- Finematics
diff --git a/src/templates/upgrade.tsx b/src/templates/upgrade.tsx
index 2ec66190f45..eeec05bff71 100644
--- a/src/templates/upgrade.tsx
+++ b/src/templates/upgrade.tsx
@@ -317,7 +317,7 @@ const dropdownLinks = {
},
{
text: "page-upgrades-upgrades-shard-chains",
- to: "/upgrades/shard-chains/",
+ to: "/upgrades/sharding/",
},
],
}
From 1ab9647c819fa8a01574ec86ce254062b187fe29 Mon Sep 17 00:00:00 2001
From: Joseph Cook <33655003+jmcook1186@users.noreply.github.com>
Date: Sat, 11 Jun 2022 09:22:07 +0100
Subject: [PATCH 047/244] Apply suggestions from code review
Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
---
.../tutorials/run-node-raspberry-pi/index.md | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/src/content/developers/tutorials/run-node-raspberry-pi/index.md b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
index 7dfef84494b..32f2e4c2113 100644
--- a/src/content/developers/tutorials/run-node-raspberry-pi/index.md
+++ b/src/content/developers/tutorials/run-node-raspberry-pi/index.md
@@ -17,7 +17,7 @@ To use Ethereum on Arm to turn a Raspberry Pi into an Ethereum node, the followi
- Raspberry 4 (model B 8GB)
- MicroSD Card (16 GB Class 10 minimum)
-- 1 TB SSD minimum USB 3.0 disk or an SSD with an USB to SATA case (see Storage section).
+- 2 TB SSD minimum USB 3.0 disk or an SSD with a USB to SATA case.
- Power supply
- Ethernet cable
- Port forwarding (see clients for further info)
@@ -38,7 +38,11 @@ Ethereum cannot be run using the popular Raspberry Pi Linux OS "Raspbian" becaus
## Note on execution and consensus clients {#note-on-execution-and-consensus-clients}
-The Ethereum on Arm documentation explains how to set up _either_ an execution client OR a consensus client, except for two Ethereum testnets (Kiln and Ropsten). This optionality is only possible in advance of Ethereum's upcoming transition from proof-of-work (PoW) to proof-of-stake (PoS) known as [The Merge](/upgrades/merge). After The Merge, it will not be possible to run execution and consensus clients separately - they must be run as a pair. Therefore, in this tutorial we will run a pair of execution and consensus clients together on an Ethereum testnet (Kiln).
+The Ethereum on Arm documentation explains how to set up _either_ an execution client OR a consensus client, except for two Ethereum testnets (Kiln and Ropsten). This optionality is only possible in advance of Ethereum's upcoming transition from proof-of-work (PoW) to proof-of-stake (PoS) known as [The Merge](/upgrades/merge).
+
+
+After The Merge, it will not be possible to run execution and consensus clients separately—they must be run as a pair. Therefore, in this tutorial we will run a pair of execution and consensus clients together on an Ethereum testnet (Kiln).
+
## The Kiln Raspberry Pi 4 Image {#the-kiln-raspberry-pi-4-image}
@@ -108,7 +112,7 @@ The specific service names for every combination of clients are available at the
## Validators {#validators}
-In order to run a validator it is first necessary to deposit 32 test-ether into the Kiln deposit contract. This means the user must have access to an account containing 32 ETH. This can be done by following the step-by-step guide on the [Kiln Launchpad](https://kiln.launchpad.ethereum.org/en/). Do this on a desktop/laptop, built do not generate keys - this can be done directly on the Raspberry Pi.
+In order to run a validator you must first have access to 32 testnet ETH, which must be deposited into the Kiln deposit contract. This can be done by following the step-by-step guide on the [Kiln Launchpad](https://kiln.launchpad.ethereum.org/en/). Do this on a desktop/laptop, but do not generate keys—this can be done directly on the Raspberry Pi.
Open a terminal on the Raspberry Pi and run the following command to generate the deposit keys:
From cbe002024d12c85abc840c3d63a8d9e464ff5651 Mon Sep 17 00:00:00 2001
From: Akim Benchiha
Date: Sat, 11 Jun 2022 17:43:57 +0200
Subject: [PATCH 048/244] feat(beaconchainaction): migrate component to
typescript
Refs: #6392
---
...ChainActions.js => BeaconChainActions.tsx} | 40 ++++++++++++-------
1 file changed, 25 insertions(+), 15 deletions(-)
rename src/components/{BeaconChainActions.js => BeaconChainActions.tsx} (84%)
diff --git a/src/components/BeaconChainActions.js b/src/components/BeaconChainActions.tsx
similarity index 84%
rename from src/components/BeaconChainActions.js
rename to src/components/BeaconChainActions.tsx
index 408390d7e99..7afce5ae1a4 100644
--- a/src/components/BeaconChainActions.js
+++ b/src/components/BeaconChainActions.tsx
@@ -6,10 +6,11 @@ import { useIntl } from "gatsby-plugin-intl"
import { translateMessageId } from "../utils/translations"
-import CardList from "./CardList"
+import CardList, { CardListItem } from "./CardList"
import Card from "./Card"
import ButtonLink from "./ButtonLink"
-import Translation from "../components/Translation"
+import Translation from "./Translation"
+import { GatsbyImageProps } from "gatsby-plugin-image"
const Container = styled.div`
margin-bottom: 4rem;
@@ -69,36 +70,45 @@ export const DataLogo = graphql`
}
`
-const BeaconChainActions = () => {
- const intl = useIntl()
- const data = useStaticQuery(graphql`
- query {
- beaconscan: file(relativePath: { eq: "upgrades/etherscan.png" }) {
- ...DataLogo
- }
- beaconchain: file(relativePath: { eq: "upgrades/beaconchainemoji.png" }) {
- ...DataLogo
- }
+const BeaconStaticQuery = graphql`
+ query {
+ beaconscan: file(relativePath: { eq: "upgrades/etherscan.png" }) {
+ ...DataLogo
+ }
+ beaconchain: file(relativePath: { eq: "upgrades/beaconchainemoji.png" }) {
+ ...DataLogo
}
- `)
+ }
+`
+
+type BeaconQueryTypes = {
+ beaconscan: string
+ beaconchain: string
+}
+
+const BeaconChainActions: React.FC = () => {
+ const intl = useIntl()
+ const data = useStaticQuery(BeaconStaticQuery)
- const datapoints = [
+ const datapoints: CardListItem[] = [
{
title: "beaconscan",
image: getImage(data.beaconscan),
+ alt: "test beaconscan",
link: "https://beaconscan.com",
description: translateMessageId("consensus-beaconscan-desc", intl),
},
{
title: "beaconcha.in",
image: getImage(data.beaconchain),
+ alt: "beaconcha test",
link: "https://beaconcha.in",
description: translateMessageId("consensus-beaconcha-in-desc", intl),
},
]
//TODO: we should refactor the naming here instead of using authors into the description field
- const reads = [
+ const reads: CardListItem[] = [
{
title: translateMessageId(
"page-upgrade-article-title-two-point-oh",
From f83045834dd09149abc0aab4e9a5f9369ca48e48 Mon Sep 17 00:00:00 2001
From: Akim Benchiha
Date: Sat, 11 Jun 2022 18:01:16 +0200
Subject: [PATCH 049/244] feat(boxgrid): migrate component to typescript
Refs: #6392
---
src/components/{BoxGrid.js => BoxGrid.tsx} | 45 ++++++++++++++++++----
1 file changed, 37 insertions(+), 8 deletions(-)
rename src/components/{BoxGrid.js => BoxGrid.tsx} (80%)
diff --git a/src/components/BoxGrid.js b/src/components/BoxGrid.tsx
similarity index 80%
rename from src/components/BoxGrid.js
rename to src/components/BoxGrid.tsx
index 77be65631cd..bb6605f11dc 100644
--- a/src/components/BoxGrid.js
+++ b/src/components/BoxGrid.tsx
@@ -3,6 +3,35 @@ import styled from "styled-components"
import Emoji from "./Emoji"
+export interface IOpener {
+ isOpen: boolean
+}
+
+export interface IGridStyle {
+ columnNumber: number
+}
+
+export interface IColor {
+ color: string
+}
+
+export interface IBaseItem {
+ emoji: string
+ title: string
+ description: string
+}
+
+export interface IBoxStyle extends IOpener, IGridStyle, IColor {}
+
+export interface IGridItemProps extends IBaseItem, IBoxStyle {
+ index: number
+ callback: (idx: number) => void
+}
+
+export interface IBoxProps {
+ items: Array
+}
+
const Title = styled.h3`
font-size: 2.5rem;
font-weight: 400;
@@ -35,7 +64,7 @@ const StyledEmoji = styled(Emoji)`
}
`
-const Box = styled.div`
+const Box = styled.div`
grid-row-start: ${(props) => (props.isOpen ? `1` : `auto`)};
grid-row-end: ${(props) => (props.isOpen ? `span 2` : `auto`)};
grid-column-start: ${(props) => (props.isOpen ? props.columnNumber : `auto`)};
@@ -70,9 +99,9 @@ const Box = styled.div`
`
// Represent string as 32-bit integer
-const hashCode = (string) => {
+const hashCode = (stringPhrase: string) => {
let hash = 0
- for (const char of string) {
+ for (const char of stringPhrase) {
const code = char.charCodeAt(0)
hash = (hash << 5) - hash + code
hash |= 0
@@ -91,7 +120,7 @@ const colors = [
"gridPurple",
]
-const GridItem = ({
+const GridItem: React.FC = ({
description,
columnNumber,
emoji,
@@ -112,9 +141,9 @@ const GridItem = ({
color={color}
>
{isOpen ? (
-
+
) : (
-
+
)}
{title}
@@ -124,12 +153,12 @@ const GridItem = ({
)
}
-const BoxGrid = ({ items }) => {
+const BoxGrid: React.FC = ({ items }) => {
const [indexOpen, setOpenIndex] = useState(0)
return (
- {items.map((item, idx) => {
+ {items.map((item, idx: number) => {
let columnNumber = idx + 1
if (columnNumber > 4) {
columnNumber = columnNumber - 3
From a8f2e1da81c38b7741efdcc0a595105fc249e85f Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Sat, 11 Jun 2022 18:45:10 -0700
Subject: [PATCH 050/244] updates markdown /sharding links
---
src/content/community/research/index.md | 2 +-
.../translation-program/content-buckets/index.md | 2 +-
src/content/developers/docs/scaling/index.md | 2 +-
src/content/developers/docs/scaling/plasma/index.md | 2 +-
src/content/nft/index.md | 2 +-
src/content/translations/ar/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/ar/upgrades/merge/index.md | 2 +-
.../ar/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/bg/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/bg/upgrades/merge/index.md | 2 +-
.../bg/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/ca/nft/index.md | 2 +-
src/content/translations/ca/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/ca/upgrades/merge/index.md | 2 +-
.../ca/upgrades/{shard-chains => sharding}/index.md | 0
.../de/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/de/developers/docs/scaling/index.md | 2 +-
src/content/translations/de/nft/index.md | 2 +-
src/content/translations/de/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/de/upgrades/merge/index.md | 2 +-
.../de/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/el/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/el/upgrades/merge/index.md | 6 +++---
.../el/upgrades/{shard-chains => sharding}/index.md | 0
.../es/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
src/content/translations/es/nft/index.md | 2 +-
src/content/translations/es/upgrades/beacon-chain/index.md | 4 ++--
src/content/translations/es/upgrades/merge/index.md | 2 +-
.../es/upgrades/{shard-chains => sharding}/index.md | 0
.../fa/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
src/content/translations/fa/nft/index.md | 2 +-
src/content/translations/fa/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/fa/upgrades/merge/index.md | 2 +-
.../fa/upgrades/{shard-chains => sharding}/index.md | 0
.../fr/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/fr/developers/docs/scaling/index.md | 2 +-
src/content/translations/fr/nft/index.md | 2 +-
src/content/translations/fr/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/fr/upgrades/merge/index.md | 2 +-
.../fr/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/hi/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/hi/upgrades/merge/index.md | 4 ++--
.../hi/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/hr/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/hr/upgrades/merge/index.md | 4 ++--
.../hr/upgrades/{shard-chains => sharding}/index.md | 0
.../hu/developers/docs/consensus-mechanisms/pos/index.md | 2 +-
src/content/translations/hu/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/hu/upgrades/merge/index.md | 4 ++--
.../hu/upgrades/{shard-chains => sharding}/index.md | 0
.../id/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/id/developers/docs/scaling/index.md | 2 +-
src/content/translations/id/nft/index.md | 2 +-
src/content/translations/id/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/id/upgrades/merge/index.md | 2 +-
.../id/upgrades/{shard-chains => sharding}/index.md | 0
.../it/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/it/developers/docs/scaling/index.md | 2 +-
src/content/translations/it/nft/index.md | 2 +-
src/content/translations/it/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/it/upgrades/merge/index.md | 2 +-
.../it/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/ja/nft/index.md | 2 +-
src/content/translations/ja/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/ja/upgrades/merge/index.md | 2 +-
.../ja/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/ml/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/ml/upgrades/merge/index.md | 4 ++--
.../ml/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/nl/nft/index.md | 2 +-
src/content/translations/nl/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/nl/upgrades/merge/index.md | 2 +-
.../nl/upgrades/{shard-chains => sharding}/index.md | 0
.../pl/developers/docs/consensus-mechanisms/pos/index.md | 2 +-
.../translations/pl/developers/docs/scaling/index.md | 2 +-
src/content/translations/pl/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/pl/upgrades/merge/index.md | 4 ++--
.../pl/upgrades/{shard-chains => sharding}/index.md | 0
.../pt-br/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
src/content/translations/pt-br/nft/index.md | 2 +-
.../translations/pt-br/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/pt-br/upgrades/merge/index.md | 2 +-
.../pt-br/upgrades/{shard-chains => sharding}/index.md | 0
.../ro/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/ro/developers/docs/scaling/index.md | 2 +-
src/content/translations/ro/nft/index.md | 2 +-
src/content/translations/ro/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/ro/upgrades/merge/index.md | 2 +-
.../ro/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/ru/nft/index.md | 2 +-
src/content/translations/ru/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/ru/upgrades/merge/index.md | 2 +-
.../ru/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/sl/nft/index.md | 2 +-
src/content/translations/sl/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/sl/upgrades/merge/index.md | 2 +-
.../sl/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/sw/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/sw/upgrades/merge/index.md | 2 +-
.../sw/upgrades/{shard-chains => sharding}/index.md | 0
.../tr/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/tr/developers/docs/scaling/index.md | 2 +-
src/content/translations/tr/nft/index.md | 2 +-
src/content/translations/tr/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/tr/upgrades/merge/index.md | 2 +-
.../tr/upgrades/{shard-chains => sharding}/index.md | 0
src/content/translations/uk/nft/index.md | 2 +-
src/content/translations/uk/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/uk/upgrades/merge/index.md | 2 +-
.../uk/upgrades/{shard-chains => sharding}/index.md | 0
.../zh/developers/docs/consensus-mechanisms/pos/index.md | 4 ++--
.../translations/zh/developers/docs/scaling/index.md | 2 +-
src/content/translations/zh/nft/index.md | 2 +-
src/content/translations/zh/upgrades/beacon-chain/index.md | 6 +++---
src/content/translations/zh/upgrades/merge/index.md | 2 +-
.../zh/upgrades/{shard-chains => sharding}/index.md | 0
src/content/upgrades/beacon-chain/index.md | 6 +++---
src/content/upgrades/merge/index.md | 2 +-
118 files changed, 161 insertions(+), 161 deletions(-)
rename src/content/translations/ar/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/bg/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/ca/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/de/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/el/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/es/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/fa/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/fr/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/hi/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/hr/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/hu/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/id/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/it/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/ja/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/ml/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/nl/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/pl/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/pt-br/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/ro/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/ru/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/sl/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/sw/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/tr/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/uk/upgrades/{shard-chains => sharding}/index.md (100%)
rename src/content/translations/zh/upgrades/{shard-chains => sharding}/index.md (100%)
diff --git a/src/content/community/research/index.md b/src/content/community/research/index.md
index e83a396b38c..a6f3a91f345 100644
--- a/src/content/community/research/index.md
+++ b/src/content/community/research/index.md
@@ -134,7 +134,7 @@ Sharding Ethereum's blockchain has long been part of the development roadmap. Ho
#### Background reading {#background-reading-4}
-- [Introduction to Ethereum sharding](/upgrades/shard-chains/)
+- [Introduction to Ethereum sharding](/upgrades/sharding/)
- [Proto-Danksharding notes](https://notes.ethereum.org/@vbuterin/proto_danksharding_faq)
- [Bankless Danksharding video](https://www.youtube.com/watch?v=N5p0TB77flM)
- [Ethereum Sharding Research Compendium](https://notes.ethereum.org/@serenity/H1PGqDhpm?type=view)
diff --git a/src/content/contributing/translation-program/content-buckets/index.md b/src/content/contributing/translation-program/content-buckets/index.md
index 62b6f841a50..dcbc9544936 100644
--- a/src/content/contributing/translation-program/content-buckets/index.md
+++ b/src/content/contributing/translation-program/content-buckets/index.md
@@ -49,7 +49,7 @@ Below is a breakdown of the website pages each content bucket contains.
- [Ethereum vision](/upgrades/vision/)
- [The Beacon Chain](/upgrades/beacon-chain/)
- [The Merge](/upgrades/merge/)
-- [Shard chains](/upgrades/shard-chains/)
+- [Shard chains](/upgrades/sharding/)
- [Staking](/staking/)
- [Ethereum upgrades get involved](/upgrades/get-involved/)
- [Consensus layer bug bounty](/upgrades/bug-bounty/)
diff --git a/src/content/developers/docs/scaling/index.md b/src/content/developers/docs/scaling/index.md
index 625611f825d..6378d78320c 100644
--- a/src/content/developers/docs/scaling/index.md
+++ b/src/content/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ This method of scaling requires changes to the Ethereum protocol (layer 1 [Mainn
Sharding is the process of splitting a database horizontally to spread the load. In an Ethereum context, sharding will reduce network congestion and increase transactions per second by creating new chains, known as “shards.” This will also lighten the load for each validator who will no longer be required to process the entirety of all transactions across the network.
-Learn more about [sharding](/upgrades/shard-chains/).
+Learn more about [sharding](/upgrades/sharding/).
## Off-chain scaling {#off-chain-scaling}
diff --git a/src/content/developers/docs/scaling/plasma/index.md b/src/content/developers/docs/scaling/plasma/index.md
index 0adcaadb792..8c879e0b883 100644
--- a/src/content/developers/docs/scaling/plasma/index.md
+++ b/src/content/developers/docs/scaling/plasma/index.md
@@ -36,7 +36,7 @@ Conversely, plasma chains derive their security from Mainnet. This makes them me
### Plasma vs sharding {#plasma-vs-sharding}
-Both plasma chains and [shard chains](/upgrades/shard-chains/) periodically publish cryptographic proofs to Ethereum Mainnet. However, both have different security properties.
+Both plasma chains and [shard chains](/upgrades/sharding/) periodically publish cryptographic proofs to Ethereum Mainnet. However, both have different security properties.
Shard chains commit "collation headers" to Mainnet containing detailed information about each data shard. Nodes on Mainnet verify and enforce the validity of data shards, reducing the possibility of invalid shard transitions and protecting the network against malicious activity.
diff --git a/src/content/nft/index.md b/src/content/nft/index.md
index e7da18f0d9d..c2fc1491b23 100644
--- a/src/content/nft/index.md
+++ b/src/content/nft/index.md
@@ -408,7 +408,7 @@ It's estimated that scalability upgrades will allow the network to process betwe
[Vitalik Buterin on transactions per second potential with sharding](https://twitter.com/VitalikButerin/status/1312905884549300224)
-At the bare minimum, sharding will allow 64 times the amount of transactions as today which sits at around 15 transactions. That's the amount of shard chains (extra data and capacity) being introduced. [More on shard chains](/upgrades/shard-chains/)
+At the bare minimum, sharding will allow 64 times the amount of transactions as today which sits at around 15 transactions. That's the amount of shard chains (extra data and capacity) being introduced. [More on shard chains](/upgrades/sharding/)
That means we can estimate how long it will take to process 100,000 transactions so we can compare it to the Visa example above.
diff --git a/src/content/translations/ar/upgrades/beacon-chain/index.md b/src/content/translations/ar/upgrades/beacon-chain/index.md
index 3861775544b..fc3aa1f3be8 100644
--- a/src/content/translations/ar/upgrades/beacon-chain/index.md
+++ b/src/content/translations/ar/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: قد تعرفون هذا كـ "المرحلة 0" على خرائ
## ما الذي تفعله السلسلة المُنارة ؟ {#what-does-the-beacon-chain-do}
-ستقوم سلسلة المنارة بإدارة أو تنسيق الشبكة الموسعة من [الأجزاء](/upgrades/shard-chains/) و[المراهنين](/staking/). لكن لن تكون مشابهة لـ[شبكة إثيريوم الرئيسية](/glossary/#mainnet) لليوم. لا يمكنها التعامل مع الحسابات أو العقود الذكية.
+ستقوم سلسلة المنارة بإدارة أو تنسيق الشبكة الموسعة من [الأجزاء](/upgrades/sharding/) و[المراهنين](/staking/). لكن لن تكون مشابهة لـ[شبكة إثيريوم الرئيسية](/glossary/#mainnet) لليوم. لا يمكنها التعامل مع الحسابات أو العقود الذكية.
سوف يتغير دور سلسلة المنارة بِمرور الوقت ولكنه عنصر أساسي لـ[ إثيريوم الآمن والمستدام والقابل للتطور الذي نعمل من أجله](/upgrades/vision/).
@@ -33,7 +33,7 @@ summaryPoint4: قد تعرفون هذا كـ "المرحلة 0" على خرائ
إذا كنت مهتمًا بأن تصبح مدققًا وتساعد على تأمين سلسلة المنارة، فتعلم المزيد عن تجميد العملات.
-و هذا ايضًا تغيير مهم لترقية "Eth2" أخرى [سلسلة الأجزاء](/upgrades/shard-chains/).
+و هذا ايضًا تغيير مهم لترقية "Eth2" أخرى [سلسلة الأجزاء](/upgrades/sharding/).
### إعداد سلسلة الأجزاء {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ summaryPoint4: قد تعرفون هذا كـ "المرحلة 0" على خرائ
ولا يمكن لسلاسل الأجزاء أن تدخل إلى منظومة إثيريوم إلا بأمان، مع وجود آلية إجماع لإثبات الحصة. سلسلة المنارة سوف تقدم عملية تجميد عملات، مما يمهد الطريق أمام ترقية سلسلة الأجزاء لتتبعها.
-
+
سلاسل الأجزاء
diff --git a/src/content/translations/ar/upgrades/merge/index.md b/src/content/translations/ar/upgrades/merge/index.md
index 1398d6b7aec..d5b6cde6a34 100644
--- a/src/content/translations/ar/upgrades/merge/index.md
+++ b/src/content/translations/ar/upgrades/merge/index.md
@@ -59,6 +59,6 @@ summaryPoint4: أشرنا إلى هذا سابقًا "بالإرساء".
سيكون هذا تقييمًا متواصلاً من طرف المجتمع بخصوص الحاجة الى عدة حلقات من سلسة الأحزاء لتحقيق قابلية اتساع غير متناهية.
-
+
سلاسل قطع
diff --git a/src/content/translations/ar/upgrades/shard-chains/index.md b/src/content/translations/ar/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/ar/upgrades/shard-chains/index.md
rename to src/content/translations/ar/upgrades/sharding/index.md
diff --git a/src/content/translations/bg/upgrades/beacon-chain/index.md b/src/content/translations/bg/upgrades/beacon-chain/index.md
index fbb95e2a7fc..d5b0b4f9385 100644
--- a/src/content/translations/bg/upgrades/beacon-chain/index.md
+++ b/src/content/translations/bg/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Това може да ви познато като „Фаза 0
## Какво прави Сигналната верига? {#what-does-the-beacon-chain-do}
-Сигналната верига ще ръководи или координира разширената мрежа на [фрагменти](/upgrades/shard-chains/) и [залагащи](/staking/). Но това няма да бъде същото като [основната мрежа на Етереум ](/glossary/#mainnet) към днешна дата. Тя не може да се справя с акаунтите и умните договори.
+Сигналната верига ще ръководи или координира разширената мрежа на [фрагменти](/upgrades/sharding/) и [залагащи](/staking/). Но това няма да бъде същото като [основната мрежа на Етереум ](/glossary/#mainnet) към днешна дата. Тя не може да се справя с акаунтите и умните договори.
Ролята на Сигналната верига ще се променя с времето, но тя е основна част на [сигурния, устойчив и разширяващ се Етереум, върху който работим](/upgrades/vision/).
@@ -33,7 +33,7 @@ summaryPoint4: Това може да ви познато като „Фаза 0
Ако се интересувате как да станете валидатор и да помогнете в осигуряването на Сигналната верига, научете повече за залагането.
-Това е и важна промяна за друга надстройка на Eth2: [вериги от компоненти](/upgrades/shard-chains/).
+Това е и важна промяна за друга надстройка на Eth2: [вериги от компоненти](/upgrades/sharding/).
### Настройки за веригите от компоненти {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ summaryPoint4: Това може да ви познато като „Фаза 0
Веригите от компоненти могат безопасно да влязат в екосистемата на Етереум само чрез съществуващ механизъм на консесус при доказателство-за-залог. Сигналната верига ще активира залагането и така ще проправи пътя за следващата надстройка на веригата от компоненти.
-Вериги от компоненти
+Вериги от компоненти
diff --git a/src/content/translations/bg/upgrades/merge/index.md b/src/content/translations/bg/upgrades/merge/index.md
index e8ab1a90a8c..11a60cfd6cf 100644
--- a/src/content/translations/bg/upgrades/merge/index.md
+++ b/src/content/translations/bg/upgrades/merge/index.md
@@ -57,4 +57,4 @@ summaryPoint4: По-рано наричахме това „прикрепван
Това ще бъде една дълготрайна задача пред общността, имайки предвид нуждата от потенциално многократни повторения на веригите от компоненти с цел едно безкрайно разширяване.
-Вериги от компоненти
+Вериги от компоненти
diff --git a/src/content/translations/bg/upgrades/shard-chains/index.md b/src/content/translations/bg/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/bg/upgrades/shard-chains/index.md
rename to src/content/translations/bg/upgrades/sharding/index.md
diff --git a/src/content/translations/ca/nft/index.md b/src/content/translations/ca/nft/index.md
index 35bf5ccb859..a08976dbf34 100644
--- a/src/content/translations/ca/nft/index.md
+++ b/src/content/translations/ca/nft/index.md
@@ -406,7 +406,7 @@ S'estima que les millores en l'escalabilitat permetran la xarxa processar entre
[Vitalik Buterin parla sobre el potencial de les transaccions per segon amb la fragmentació](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Amb un mínim, la fragmentació permetrà una quantitat de transaccions multiplicada per 64 en comparació amb les que es fan avui en dia que ronden les 15. Aquesta és la quantitat de cadenes fragmentades (capacitat i dades extra) que s'han introduït. [Més informació sobre les cadenes de fragments](/upgrades/shard-chains/)
+Amb un mínim, la fragmentació permetrà una quantitat de transaccions multiplicada per 64 en comparació amb les que es fan avui en dia que ronden les 15. Aquesta és la quantitat de cadenes fragmentades (capacitat i dades extra) que s'han introduït. [Més informació sobre les cadenes de fragments](/upgrades/sharding/)
Això vol dir que podem estimar quant es trigaria a processar 100.000 transaccions per poder comparar-ho amb l'exemple de Visa esmentat.
diff --git a/src/content/translations/ca/upgrades/beacon-chain/index.md b/src/content/translations/ca/upgrades/beacon-chain/index.md
index 974de271baf..4ce01f6c098 100644
--- a/src/content/translations/ca/upgrades/beacon-chain/index.md
+++ b/src/content/translations/ca/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Potser, això, ho coneixeu com la "Fase 0" dels mapes tècnics.
## Què fa la cadena de balisa? {#what-does-the-beacon-chain-do}
-La cadena de balisa dirigirà o coordinarà l'expansió de la xarxa de [fragments](/upgrades/shard-chains/) i [participants](/staking/). Però no serà com [la xarxa principal d'Ethereum](/glossary/#mainnet) d'avui en dia. No pot gestionar comptes o contractes intel·ligents.
+La cadena de balisa dirigirà o coordinarà l'expansió de la xarxa de [fragments](/upgrades/sharding/) i [participants](/staking/). Però no serà com [la xarxa principal d'Ethereum](/glossary/#mainnet) d'avui en dia. No pot gestionar comptes o contractes intel·ligents.
El rol de la cadena de balisa canviarà amb el pas del temps, però és un element fonamental de [l'Ethereum segur, sostenible i escalable per la qual treballem](/upgrades/vision/).
@@ -33,7 +33,7 @@ Apostar i convertir-se en validador és més senzill que [minar](/developers/doc
Si us interessa ser validador i contribuir a protegir la cadena de balisa, aquí podeu aprendre més sobre les apostes.
-Això és un canvi important per una altra millora:[les cadenes de fragments](/upgrades/shard-chains/).
+Això és un canvi important per una altra millora:[les cadenes de fragments](/upgrades/sharding/).
### Configuració de les cadenes de fragments {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ En un principi, la cadena de balisa serà independent de la xarxa principal d'Et
Les cadenes de fragments només poden entrar de forma segura a l'ecosistema Ethereum si existeix un mecanisme de consens de prova de participació. La cadena de balisa introduirà l'aposta i aplanarà el camí a la futura introducció de la cadena de fragments.
-
+
Cadenes de fragments
diff --git a/src/content/translations/ca/upgrades/merge/index.md b/src/content/translations/ca/upgrades/merge/index.md
index 414a798f408..48e531e66c3 100644
--- a/src/content/translations/ca/upgrades/merge/index.md
+++ b/src/content/translations/ca/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Originalment, el pla era treballar en cadenes de fragments abans de La Fusió, p
La comunitat avaluarà de forma contínua la necessitat de múltiples rondes de cadenes de fragments per permetre una escalabilitat infinita.
-
+
Cadenes de fragments
diff --git a/src/content/translations/ca/upgrades/shard-chains/index.md b/src/content/translations/ca/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/ca/upgrades/shard-chains/index.md
rename to src/content/translations/ca/upgrades/sharding/index.md
diff --git a/src/content/translations/de/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/de/developers/docs/consensus-mechanisms/pos/index.md
index ea5bb629253..ed636a72728 100644
--- a/src/content/translations/de/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/de/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ Proof-of-Stake kommt mit einer Anzahl an Verbesserungen zum Proof-of-Work-System
- bessere Energieeffizienz – weniger Energieaufwand für das Minen (Schürfen) von Blöcken
- weniger Hindernisse für den Einstieg, zeduziert Hardwareanforderungen – Du brauchst keine Elite-Hardware, um neue Blöcke zu erstellen
- stärkere Immunität gegen die Zentralisierung – Proof-of-Stake sollte zu mehr Nodes im Netzwerk führen
-- stärkere Unterstützung für [Shard Chains](/upgrades/shard-chains/) – ein wichtiges Upgrade bei der Skalierung des Ethereum-Netzwerks
+- stärkere Unterstützung für [Shard Chains](/upgrades/sharding/) – ein wichtiges Upgrade bei der Skalierung des Ethereum-Netzwerks
## Proof-of-Stake, Staking und Validatoren {#pos-staking-validators}
@@ -37,7 +37,7 @@ Wenn du bösartige Blöcke attestierst, verlierst du deinen Einsatz.
### Die Beacon Chain {#the-beacon-chain}
-Wenn Ethereum den Proof-of-Work durch den Proof-of-Stake ersetzt, wird es zusätzlich die Komplexität von [Shard-Chains](/upgrades/shard-chains/) geben. Das sind separate Blockchains, die Validatoren benötigen, um Transaktionen zu verarbeiten und neue Blöcke zu erstellen. Der Plan sind 64 Scherben-Ketten, die alle ein geteiltes Verständnis vom Status des Netzwerks haben. Daher ist eine zusätzliche Koordination notwendig, die von [der Beacon Chain](/upgrades/beacon-chain/) übernommen wird.
+Wenn Ethereum den Proof-of-Work durch den Proof-of-Stake ersetzt, wird es zusätzlich die Komplexität von [Shard-Chains](/upgrades/sharding/) geben. Das sind separate Blockchains, die Validatoren benötigen, um Transaktionen zu verarbeiten und neue Blöcke zu erstellen. Der Plan sind 64 Scherben-Ketten, die alle ein geteiltes Verständnis vom Status des Netzwerks haben. Daher ist eine zusätzliche Koordination notwendig, die von [der Beacon Chain](/upgrades/beacon-chain/) übernommen wird.
Die Beacon Chain erhält Statusinformationen von den Fragmenten und stellt sie für die anderen Fragmente zur Verfügung, so dass das Netzwerken synchronisiert bleiben kann. Die Beacon Chain verwaltet auch die Validatoren, von der Registrierung ihrer Einlagen bis hin zur Verteilung ihrer Belohnungen und Strafen.
diff --git a/src/content/translations/de/developers/docs/scaling/index.md b/src/content/translations/de/developers/docs/scaling/index.md
index b53a5defdde..3f1a550016f 100644
--- a/src/content/translations/de/developers/docs/scaling/index.md
+++ b/src/content/translations/de/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ Diese Methode der Skalierung erfordert Änderungen am Ethereum-Protokoll (Layer
Unter Sharding versteht man die horizontale Aufteilung einer Datenbank, um die Last zu verteilen. Im Ethereum-Kontext wird das Sharding die Netzwerküberlastung reduzieren und die Transaktionen pro Sekunde erhöhen, indem neue Ketten, die sogenannten „Shards", geschaffen werden. Dies entlastet auch die einzelnen Prüfer, die nicht mehr die Gesamtheit aller Transaktionen im Netz bearbeiten müssen.
-Erfahren Sie mehr über [Sharding](/upgrades/shard-chains/).
+Erfahren Sie mehr über [Sharding](/upgrades/sharding/).
## Off-Chain-Skalierung {#off-chain-scaling}
diff --git a/src/content/translations/de/nft/index.md b/src/content/translations/de/nft/index.md
index bf876176d9d..cd14e97be66 100644
--- a/src/content/translations/de/nft/index.md
+++ b/src/content/translations/de/nft/index.md
@@ -406,7 +406,7 @@ Schätzungen zufolge ermöglichen Upgrades an der Skalierbarkeit dem Netzwerk, z
[Vitalik Buterin über das Potenzial für Transaktionen pro Sekunde mit Sharding](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Sharding wird mindestens 64-fache Beschleunigung der derzeitigen Transkationszahlen pro Sekunde ermöglichen, die aktuell bei 15 liegt. Das ist die Menge der Shard Chains (zusätzliche Daten und Kapazität), die eingeführt werden. [Mehr zu Shard-Chains](/upgrades/shard-chains/)
+Sharding wird mindestens 64-fache Beschleunigung der derzeitigen Transkationszahlen pro Sekunde ermöglichen, die aktuell bei 15 liegt. Das ist die Menge der Shard Chains (zusätzliche Daten und Kapazität), die eingeführt werden. [Mehr zu Shard-Chains](/upgrades/sharding/)
Damit können wir abschätzen, wie lange die Verarbeitung von 100.000 Transaktionen dauert, und das ermöglicht den Vergleich mit dem Visa-Beispiel oben.
diff --git a/src/content/translations/de/upgrades/beacon-chain/index.md b/src/content/translations/de/upgrades/beacon-chain/index.md
index d2ba5fc7e39..d08aa634af2 100644
--- a/src/content/translations/de/upgrades/beacon-chain/index.md
+++ b/src/content/translations/de/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Sie kennen das möglicherweise als „Phase 0“ in technischen D
## Welche Funktion hat die Beacon Chain? {#what-does-the-beacon-chain-do}
-Die Beacon Chain übernimmt die Koordination und Verknüpfung des Netzwerks der [Shards](/upgrades/shard-chains/) und [Staker](/staking/). Aber sie ist nicht mit dem [Ethereum-Mainnet](/glossary/#mainnet) von heute vergleichbar, da sie keine Konten oder Smart Contracts verarbeitet.
+Die Beacon Chain übernimmt die Koordination und Verknüpfung des Netzwerks der [Shards](/upgrades/sharding/) und [Staker](/staking/). Aber sie ist nicht mit dem [Ethereum-Mainnet](/glossary/#mainnet) von heute vergleichbar, da sie keine Konten oder Smart Contracts verarbeitet.
Mit der Zeit können sich Aufgabe und Rolle der Beacon Chain zwar verändern, sie ist jedoch ein fundamentaler Baustein für das [sichere, nachhaltige und skalierbare Ethereum der Zukunft](/upgrades/vision/).
@@ -33,7 +33,7 @@ Das Staking als Validator ist einfacher, als das [Mining](/developers/docs/minin
Wenn Sie Interesse haben, die Beacon Chain als Validator sicherer zu machen, können Sie hier mehr über das Staking lernen.
-Das ist auch eine wichtige Änderung für ein anderes Upgrade: [Shard Chains](/upgrades/shard-chains/).
+Das ist auch eine wichtige Änderung für ein anderes Upgrade: [Shard Chains](/upgrades/sharding/).
### Vorbereitung für Shard Chains {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ Die Beacon Chain wird zunächst getrennt vom Ethereum-Mainnet existieren, welche
Shard Chains können nur dann sicher ins Ethereum-Netzwerk eingeführt werden, wenn ein funktionierender Proof-of-Stake-Konsensmechanismus bereits etabliert ist. Mit der Beacon Chain wird Staking eingeführt, wodurch der Weg für das Shard Chains-Upgrade geebnet wird.
-
+
Shard Chains
diff --git a/src/content/translations/de/upgrades/merge/index.md b/src/content/translations/de/upgrades/merge/index.md
index 051d127a1b3..aace633e797 100644
--- a/src/content/translations/de/upgrades/merge/index.md
+++ b/src/content/translations/de/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Ursprünglich war geplant, vor der Zusammenführung an Shard Chains zu arbeiten,
Hier wird eine fortlaufende Bewertung der Gemeinschaft geben, ob ggf. mehrere Runden von Shard Chains erforderlich werden, um eine unbegrenzte Skalierbarkeit zu ermöglichen.
-
+
Shard Chains
diff --git a/src/content/translations/de/upgrades/shard-chains/index.md b/src/content/translations/de/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/de/upgrades/shard-chains/index.md
rename to src/content/translations/de/upgrades/sharding/index.md
diff --git a/src/content/translations/el/upgrades/beacon-chain/index.md b/src/content/translations/el/upgrades/beacon-chain/index.md
index 5f9d47a32cf..bbad6a1e5b6 100644
--- a/src/content/translations/el/upgrades/beacon-chain/index.md
+++ b/src/content/translations/el/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Μπορεί να το γνωρίζετε αυτό ως "Φάση
## Τι ακριβώς κάνει η κύρια αλυσίδα; {#what-does-the-beacon-chain-do}
-Η κύρια αλυσίδα θα διεξάγει ή θα συντονίζει το διευρυμένο δίκτυο των [shards](/upgrades/shard-chains/) και των [stakers](/staking/). Αλλά δεν θα είναι όπως το σημερινό [κεντρικό δίκτυο του Ethereum](/glossary/#mainnet). Δεν μπορεί να χειριστεί λογαριασμούς ή έξυπνα συμβόλαια.
+Η κύρια αλυσίδα θα διεξάγει ή θα συντονίζει το διευρυμένο δίκτυο των [shards](/upgrades/sharding/) και των [stakers](/staking/). Αλλά δεν θα είναι όπως το σημερινό [κεντρικό δίκτυο του Ethereum](/glossary/#mainnet). Δεν μπορεί να χειριστεί λογαριασμούς ή έξυπνα συμβόλαια.
Ο ρόλος της κύρια αλυσίδας θα αλλάξει με την πάροδο του χρόνου, αλλά είναι ένα θεμελιώδες συστατικό για [ένα ασφαλές, βιώσιμο και κλιμακούμενο Ethereum προς το οποίο εργαζόμαστε](/upgrades/vision/).
@@ -33,7 +33,7 @@ summaryPoint4: Μπορεί να το γνωρίζετε αυτό ως "Φάση
Αν ενδιαφέρεστε να γίνετε επικυρωτής και να βοηθήσετε στην ασφάλιση του Beacon Chain, μάθετε περισσότερα για το staking.
-Αυτή είναι επίσης μια σημαντική αλλαγή για τη δεύτερη αναβάθμιση Eth2: [shard chains](/upgrades/shard-chains/).
+Αυτή είναι επίσης μια σημαντική αλλαγή για τη δεύτερη αναβάθμιση Eth2: [shard chains](/upgrades/sharding/).
### Ρύθμιση για τις shard chains {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ summaryPoint4: Μπορεί να το γνωρίζετε αυτό ως "Φάση
Οι Shard chains μπορούν να εισέλθουν με ασφάλεια στο οικοσύστημα του Ethereum μόνο με έναν μηχανισμό επαλήθευσης (proof-of-stake). Η κύρια αλυσίδα θα εισαγάγει το staking, ανοίγοντας το δρόμο για την αναβάθμιση της shard chain.
-Shard chains
+Shard chains
diff --git a/src/content/translations/el/upgrades/merge/index.md b/src/content/translations/el/upgrades/merge/index.md
index 1c570640ec1..928905b060d 100644
--- a/src/content/translations/el/upgrades/merge/index.md
+++ b/src/content/translations/el/upgrades/merge/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Μπορεί να το γνωρίζετε αυτό ως "Φάση
## Ποια είναι η ενσωμάτωση; {#what-is-the-docking}
-Είναι σημαντικό να θυμόμαστε ότι αρχικά, οι υπόλοιπες αναβαθμίσεις του Eth2 αποστέλλονται ξεχωριστά από το [κεντρικό δίκτυο](/glossary/#mainnet) - την αλυσίδα (chain) που χρησιμοποιούμε σήμερα. Το κεντρικό δίκτυο του Ethereum θα συνεχίσει να ασφαλίζεται με το λεγόμενο [proof-of-work](/developers/docs/consensus-mechanisms/pow/), ακόμη και όταν [η Beacon Chain](/upgrades/beacon-chain/) και οι [shard chains](/upgrades/shard-chains/) θα εκτελούνται παράλληλα χρησιμοποιώντας το [proof of stake](/developers/docs/consensus-mechanisms/pos/). Η ενσωμάτωση θα πραγματοποιηθεί όταν αυτά τα δύο συστήματα θα συγχωνευτούν.
+Είναι σημαντικό να θυμόμαστε ότι αρχικά, οι υπόλοιπες αναβαθμίσεις του Eth2 αποστέλλονται ξεχωριστά από το [κεντρικό δίκτυο](/glossary/#mainnet) - την αλυσίδα (chain) που χρησιμοποιούμε σήμερα. Το κεντρικό δίκτυο του Ethereum θα συνεχίσει να ασφαλίζεται με το λεγόμενο [proof-of-work](/developers/docs/consensus-mechanisms/pow/), ακόμη και όταν [η Beacon Chain](/upgrades/beacon-chain/) και οι [shard chains](/upgrades/sharding/) θα εκτελούνται παράλληλα χρησιμοποιώντας το [proof of stake](/developers/docs/consensus-mechanisms/pos/). Η ενσωμάτωση θα πραγματοποιηθεί όταν αυτά τα δύο συστήματα θα συγχωνευτούν.
Φανταστείτε το Ethereum να είναι ένα διαστημόπλοιο που δεν είναι αρκετά έτοιμο για ένα διαστρικό ταξίδι του. Με την Beacon Chain και τις shard chains η κοινότητα έχει χτίσει ένα νέο κινητήρα και ένα ποιο ανθεκτικό κύτος. Όταν έρθει η ώρα, το διαστημόπλοιο θα προσγειωθεί με αυτό το νέο σύστημα, έτσι ώστε να μπορεί να καταστεί έτοιμο να τεθεί σε σοβαρά έτη φωτός και να επικρατήσει στο σύμπαν.
@@ -43,6 +43,6 @@ summaryPoint4: Μπορεί να το γνωρίζετε αυτό ως "Φάση
### Η ενσωμάτωση και οι shard chains {#docking-and-shard-chains}
-Με το κεντρικό δίκτυο να γίνεται ένα shard, η επιτυχής εφαρμογή των shard chains είναι κρίσιμη για αυτή την αναβάθμιση. Είναι πιθανό η μετάβαση να διαδραματίσει σημαντικό ρόλο βοηθώντας την κοινότητα να αποφασίσει αν θα ξεκινήσει μια δεύτερη αναβάθμιση για το sharding. Αυτή η αναβάθμιση θα κάνει τα άλλα shards όπως το Mainnet: θα είναι σε θέση να χειριστεί συναλλαγές και Smart Contract και όχι μόνο να παρέχει περισσότερα δεδομένα.Shard chains
+Με το κεντρικό δίκτυο να γίνεται ένα shard, η επιτυχής εφαρμογή των shard chains είναι κρίσιμη για αυτή την αναβάθμιση. Είναι πιθανό η μετάβαση να διαδραματίσει σημαντικό ρόλο βοηθώντας την κοινότητα να αποφασίσει αν θα ξεκινήσει μια δεύτερη αναβάθμιση για το sharding. Αυτή η αναβάθμιση θα κάνει τα άλλα shards όπως το Mainnet: θα είναι σε θέση να χειριστεί συναλλαγές και Smart Contract και όχι μόνο να παρέχει περισσότερα δεδομένα.Shard chains
-Shard chains
+Shard chains
diff --git a/src/content/translations/el/upgrades/shard-chains/index.md b/src/content/translations/el/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/el/upgrades/shard-chains/index.md
rename to src/content/translations/el/upgrades/sharding/index.md
diff --git a/src/content/translations/es/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/es/developers/docs/consensus-mechanisms/pos/index.md
index 4c35e88f46d..c90f061b8a0 100644
--- a/src/content/translations/es/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/es/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ La Prueba de participación incluye una serie de mejoras para el sistema de Prue
- Mejor eficiencia energética: no necesitas usar mucha energía para minar los bloques
- Barreras de entrada más bajas, requisitos de hardware reducidos: no necesitas hardware de primer nivel para tener una oportunidad de crear nuevos bloques
- Mayor inmunidad a la centralización: la Prueba de participación debería conducir a la existencia de más nodos en la red
-- mayor soporte para la [cadena de fragmentos](/upgrades/shard-chains/) – una mejora clave en la escala de la red Ethereum
+- mayor soporte para la [cadena de fragmentos](/upgrades/sharding/) – una mejora clave en la escala de la red Ethereum
## Prueba de participación, staking (apuestas) y validadores {#pos-staking-validators}
@@ -37,7 +37,7 @@ Si certificas bloques maliciosos, perderás tu apuesta.
### La cadena de baliza (blockchain) {#the-beacon-chain}
-Cuando en Ethereum se reemplaza la prueba de trabajo por la prueba de participación, se añade la complejidad de las [cadenas de fragmentos](/upgrades/shard-chains/). Se trata de cadenas de valores independientes que necesitarán validadores para procesar las transacciones y crear nuevos bloques. El plan es disponer de 64 cadenas fragmentadas y todos necesitan comprender cuál es el estado de la red. Como consecuencia, se necesita una coordinación adicional, la cual se realizará mediante [la cadena de baliza](/upgrades/beacon-chain/).
+Cuando en Ethereum se reemplaza la prueba de trabajo por la prueba de participación, se añade la complejidad de las [cadenas de fragmentos](/upgrades/sharding/). Se trata de cadenas de valores independientes que necesitarán validadores para procesar las transacciones y crear nuevos bloques. El plan es disponer de 64 cadenas fragmentadas y todos necesitan comprender cuál es el estado de la red. Como consecuencia, se necesita una coordinación adicional, la cual se realizará mediante [la cadena de baliza](/upgrades/beacon-chain/).
La cadena de baliza recibe la información del estado de los fragmentos y la hace disponible para otros fragmentos para que, de este modo, la red pueda permanecer sincronizada. La cadena de baliza también gestionará a los validadores, desde el registro de los depósitos de sus apuestas hasta la emisión de sus recompensas y penalizaciones.
diff --git a/src/content/translations/es/nft/index.md b/src/content/translations/es/nft/index.md
index e993061e8f5..a15f496e453 100644
--- a/src/content/translations/es/nft/index.md
+++ b/src/content/translations/es/nft/index.md
@@ -406,7 +406,7 @@ Se calcula que las actualizaciones de escalabilidad podrán permitir que la red
[Vitalik Buterin sobre el potencial de las transacciones por segundo con la fragmentación](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Como mínimo, fraccionar permitirá aumentar 64 veces la cantidad de transacciones, que en la actualidad se sitúa en alrededor de 15 transacciones. Esa es la cantidad de cadenas de fragmentación (datos y capacidad adicionales) que se están introduciendo. [Más información sobre las cadenas de fragmentación](/upgrades/shard-chains/)
+Como mínimo, fraccionar permitirá aumentar 64 veces la cantidad de transacciones, que en la actualidad se sitúa en alrededor de 15 transacciones. Esa es la cantidad de cadenas de fragmentación (datos y capacidad adicionales) que se están introduciendo. [Más información sobre las cadenas de fragmentación](/upgrades/sharding/)
Eso significa que podemos estimar cuánto tiempo llevará procesar 100.000 transacciones para poder compararlo con el ejemplo anterior de Visa.
diff --git a/src/content/translations/es/upgrades/beacon-chain/index.md b/src/content/translations/es/upgrades/beacon-chain/index.md
index 61d2d11225b..61699e679f9 100644
--- a/src/content/translations/es/upgrades/beacon-chain/index.md
+++ b/src/content/translations/es/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Puede que se describa como «Fase 0» en las hojas de ruta técni
## ¿Qué hace la cadena de baliza? {#what-does-the-beacon-chain-do}
-La cadena de baliza conducirá o coordinará la expansión de la red de [fragmentos](/upgrades/shard-chains/) y [participantes](/staking/). Pero no será como la [red principal de Ethereum](/glossary/#mainnet) de hoy en día: no puede manejar cuentas o contratos inteligentes.
+La cadena de baliza conducirá o coordinará la expansión de la red de [fragmentos](/upgrades/sharding/) y [participantes](/staking/). Pero no será como la [red principal de Ethereum](/glossary/#mainnet) de hoy en día: no puede manejar cuentas o contratos inteligentes.
La función de la cadena de baliza cambiará con el tiempo, pero es un componente fundamental para lograr el [ Ethereum seguro, sostenible y escalable en el que estamos trabajando](/upgrades/vision/).
@@ -57,7 +57,7 @@ La cadena de baliza al principio existirá con independencia de la red principal
Las cadenas de fragmentos solo pueden introducirse en el ecosistema Ethereum de manera segura con un mecanismo de consenso de la prueba de participación establecido. La cadena de baliza introducirá la apuesta y allanará el camino a la cadena de fragmentos actualizada que se implementará posteriormente.
-
+
Cadenas de fragmentos
diff --git a/src/content/translations/es/upgrades/merge/index.md b/src/content/translations/es/upgrades/merge/index.md
index 33eb1c5db1e..e98d6cf6090 100644
--- a/src/content/translations/es/upgrades/merge/index.md
+++ b/src/content/translations/es/upgrades/merge/index.md
@@ -59,7 +59,7 @@ El plan inicial consistía en trabajar en cadenas de fragmentos antes de la fusi
La necesidad de múltiples rondas de cadenas de fragmentos para permitir una escalabilidad infinita será objeto de evaluación continua por parte de la comunidad.
-
+
Cadenas de fragmentos
diff --git a/src/content/translations/es/upgrades/shard-chains/index.md b/src/content/translations/es/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/es/upgrades/shard-chains/index.md
rename to src/content/translations/es/upgrades/sharding/index.md
diff --git a/src/content/translations/fa/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/fa/developers/docs/consensus-mechanisms/pos/index.md
index b6c214704ab..92910e56ced 100644
--- a/src/content/translations/fa/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/fa/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ incomplete: true
- کارایی انرژی بهتر – نیازی به استفاده از انرژی زیاد برای استخراج بلوکها ندارید
- موانع کمتر برای ورود، سختافزار موردنیاز کمتر – برای برخورداری از شانس ساختن بلوکهای جدید، نیاز به سختافزار عجیب و خاص ندارید
- مصونیت بیشتر در برابر متمرکز شدن – اثبات سهام به گرههای بیشتری در شبکه منجر میشود
-- پشتیبانی بیشتر برای [خردهزنجیرهها](/upgrades/shard-chains/) – یک ارتقای مهم در مقیاسپذیری شبکهی اتریوم
+- پشتیبانی بیشتر برای [خردهزنجیرهها](/upgrades/sharding/) – یک ارتقای مهم در مقیاسپذیری شبکهی اتریوم
## اثبات سهام، سهامگذاری و اعتبارسنجها {#pos-staking-validators}
@@ -37,7 +37,7 @@ incomplete: true
### زنجیرهی بیکن {#the-beacon-chain}
-زمانی که اتریوم اثبات سهام را جایگزین اثبات کار کند، پیچیدگی بیشتری به [خردهزنجیرهها](/upgrades/shard-chains/) اضافه میشود. اینها زنجیرههای بلوکی مجزایی هستنند که به اعتبارسنجها برای بررسی تراکنشها و ساختن بلوکهای جدید نیاز دارند. برنامه این است که 64 خردهزنجیره وجود داشته باشد که هر کدام فهم مشترکی از وضعیت شبکه داشته باشند. در نتیجه هماهنگی بیشتری لازم است و این کار توسط [زنجیرهی بیکن](/upgrades/beacon-chain/) انجام خواهد شد.
+زمانی که اتریوم اثبات سهام را جایگزین اثبات کار کند، پیچیدگی بیشتری به [خردهزنجیرهها](/upgrades/sharding/) اضافه میشود. اینها زنجیرههای بلوکی مجزایی هستنند که به اعتبارسنجها برای بررسی تراکنشها و ساختن بلوکهای جدید نیاز دارند. برنامه این است که 64 خردهزنجیره وجود داشته باشد که هر کدام فهم مشترکی از وضعیت شبکه داشته باشند. در نتیجه هماهنگی بیشتری لازم است و این کار توسط [زنجیرهی بیکن](/upgrades/beacon-chain/) انجام خواهد شد.
زنجیرهی بیکن اطلاعات وضعیت را از خردهزنجیرهها دریافت کرده و برای بقیه قابل دسترسی میکند و به شبکه اجازهی هماهنگی میدهد. زنجیرهی بیکن همچنین اعتبارسنجها را از سهامگذاری سپرده گرفته تا صدور پاداش و جریمهی آنها مدیریت میکند.
diff --git a/src/content/translations/fa/nft/index.md b/src/content/translations/fa/nft/index.md
index 61e46b8106e..6372506316c 100644
--- a/src/content/translations/fa/nft/index.md
+++ b/src/content/translations/fa/nft/index.md
@@ -406,7 +406,7 @@ _نباید فراموش کرد که اتریوم کاری بیش از تراک
[ویتالیک بوترین دربارهی پتانسیل تراکنش بر ثانیه با زنجیرهایسازی](https://twitter.com/VitalikButerin/status/1312905884549300224)
-در کمترین حالت، زنجیرهایسازی حدود 64 برابر مقدار تراکنشهای امروزی را که حدوداً 15 تراکنش است، ممکن میسازد. این مقدارِ زنجیرههای خردشده (دادهها و ظرفیت اضافی) معرفیشده است. [اطلاعات بیشتر دربارهی زنجیرههای خردشده](/upgrades/shard-chains/)
+در کمترین حالت، زنجیرهایسازی حدود 64 برابر مقدار تراکنشهای امروزی را که حدوداً 15 تراکنش است، ممکن میسازد. این مقدارِ زنجیرههای خردشده (دادهها و ظرفیت اضافی) معرفیشده است. [اطلاعات بیشتر دربارهی زنجیرههای خردشده](/upgrades/sharding/)
این یعنی ما میتوانیم تخمین بزنیم پردازش 100,000 تراکنش چقدر طول خواهد کشید تا بتوانیم آن را با مثال Visa که در بالا ارائه شد، مقایسه کنیم.
diff --git a/src/content/translations/fa/upgrades/beacon-chain/index.md b/src/content/translations/fa/upgrades/beacon-chain/index.md
index 09d200281e2..6b1239d7632 100644
--- a/src/content/translations/fa/upgrades/beacon-chain/index.md
+++ b/src/content/translations/fa/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: احتمالاً شما آن را در نقشه راه فنی ت
## زنجیره بیکن چه میکند؟ {#what-does-the-beacon-chain-do}
-زنجیرهی بیکن شبکهی بسطیافته [خردهزنجیرهها](/upgrades/shard-chains/) و [سهامگذارها](/staking/) را هدایت یا هماهنگ میکند. اما نظیر[شبکه اصلی اتریوم ](/glossary/#mainnet) امروز نخواهد بود. قابلیت استفاده از حساب های کاربری و قرارداد های هوشمند را ندارد.
+زنجیرهی بیکن شبکهی بسطیافته [خردهزنجیرهها](/upgrades/sharding/) و [سهامگذارها](/staking/) را هدایت یا هماهنگ میکند. اما نظیر[شبکه اصلی اتریوم ](/glossary/#mainnet) امروز نخواهد بود. قابلیت استفاده از حساب های کاربری و قرارداد های هوشمند را ندارد.
نقش زنجیرهی بیکن در طی زمان تغییر میکند اما همچنان عنصری بنیادین برای [ اتریوم امن، پایدار و مقیاس پذیری که اکنون داریم به سویش پیش میرویم](/upgrades/vision/) باقی میماند.
@@ -33,7 +33,7 @@ summaryPoint4: احتمالاً شما آن را در نقشه راه فنی ت
اگر به اعتبارسنج شدن و کمک به ایمنسازی شبکهی بیکن علاقمند دارید، درباره سهامگذاری بیشتر بدانید.
-این موضوع همچنین تغییری مهم برای ارتقای دیگری است: [خردهزنجیرهها](/upgrades/shard-chains/).
+این موضوع همچنین تغییری مهم برای ارتقای دیگری است: [خردهزنجیرهها](/upgrades/sharding/).
### راه اندازی زنجیره های شارد {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ summaryPoint4: احتمالاً شما آن را در نقشه راه فنی ت
زنجیره های شارد تنها میتوانند با داشتن یک مکانیسم توافق مجموعه اثبات مالکیت سهام به شکل ایمن وارد اکوسیستم اتریوم شوند. زنجیره بیکن سهام گذاری را معرفی خواهد کرد، که راه را برای ارتقای رنجیره های شارد هموار خواهد کرد.
-
+
زنجیره های شارد
diff --git a/src/content/translations/fa/upgrades/merge/index.md b/src/content/translations/fa/upgrades/merge/index.md
index 7d8f88fa97c..9d09c6ab84d 100644
--- a/src/content/translations/fa/upgrades/merge/index.md
+++ b/src/content/translations/fa/upgrades/merge/index.md
@@ -59,7 +59,7 @@ summaryPoint4: ما پیش تر به این کار "داکینیگ" می گف
این یک ارزیابی مداوم از جامعه برای پاسخ به چندین دوره احتمالی از خده زنجیره های شارد برای امکان پذیر کردن مقیاس پذیری بی نهایت است.
-
+
خرده زنجیرها
diff --git a/src/content/translations/fa/upgrades/shard-chains/index.md b/src/content/translations/fa/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/fa/upgrades/shard-chains/index.md
rename to src/content/translations/fa/upgrades/sharding/index.md
diff --git a/src/content/translations/fr/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/fr/developers/docs/consensus-mechanisms/pos/index.md
index 40bf7ebf5e4..18d02b16457 100644
--- a/src/content/translations/fr/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/fr/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ La preuve d'enjeu apporte un certain nombre d'améliorations au système de preu
- Meilleure efficacité énergétique : vous n'avez pas besoin d'utiliser beaucoup d'énergie en minant des blocs.
- Réduction des barrières à l'entrée et des exigences matérielles : vous n'avez pas besoin de matériel haut de gamme pour avoir une chance de créer de nouveaux blocs.
- Plus grande immunité à la centralisation : la preuve d'enjeu devrait conduire à plus de nœuds sur le réseau.
-- meilleur support des [chaînes fragmentées](/upgrades/shard-chains/) - un point clé dans le passage à l'échelle du réseau Ethereum
+- meilleur support des [chaînes fragmentées](/upgrades/sharding/) - un point clé dans le passage à l'échelle du réseau Ethereum
## Preuve d'enjeu, mise et validateurs {#pos-staking-validators}
@@ -37,7 +37,7 @@ Si vous attestez la conformité de blocs malveillants, vous perdez votre mise.
### La chaîne phare {#the-beacon-chain}
-Quand Ethereum remplacera la preuve de travail par une preuve d'enjeu, cela entraînera la complexité supplémentaire des [chaînes de fragments](/upgrades/shard-chains/). Ce sont des blockchains séparées qui nécessitent des validateurs pour traiter les transactions et créer de nouveaux blocs. Le projet est de disposer de 64 chaînes de fragments, qui exigent toutes une compréhension partagée de l'état du réseau. Cela implique qu'une coordination suplémentaire est nécéssaire et celle ci sera réalisée par [la chaine phare](/upgrades/beacon-chain/).
+Quand Ethereum remplacera la preuve de travail par une preuve d'enjeu, cela entraînera la complexité supplémentaire des [chaînes de fragments](/upgrades/sharding/). Ce sont des blockchains séparées qui nécessitent des validateurs pour traiter les transactions et créer de nouveaux blocs. Le projet est de disposer de 64 chaînes de fragments, qui exigent toutes une compréhension partagée de l'état du réseau. Cela implique qu'une coordination suplémentaire est nécéssaire et celle ci sera réalisée par [la chaine phare](/upgrades/beacon-chain/).
La chaîne phare reçoit des informations d'état provenant de fragments et les met à la disposition d'autres fragments afin que le réseau puisse rester synchronisé. La chaîne phare gère également les validateurs, de l'enregistrement de leur mise jusqu'à l'émission de leurs récompenses et pénalités.
diff --git a/src/content/translations/fr/developers/docs/scaling/index.md b/src/content/translations/fr/developers/docs/scaling/index.md
index 9e92026825f..d7b87a9c65d 100644
--- a/src/content/translations/fr/developers/docs/scaling/index.md
+++ b/src/content/translations/fr/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ Cette méthode de mise à l’échelle nécessite des modifications du protocole
La fragmentation est le processus de fractionnement horizontal d'une base de données pour répartir la charge. Dans le cadre d'Ethereum, cette fragmentation permettra de réduire l'encombrement du réseau en augmentant le nombre de transactions par seconde grâce à la création de nouvelles chaînes, appelées « fragments ». Cela allègera également la charge pour chaque validateur qui ne sera plus tenu de traiter l’intégralité de toutes les transactions sur le réseau.
-En savoir plus sur [la fragmentation](/upgrades/shard-chains/).
+En savoir plus sur [la fragmentation](/upgrades/sharding/).
## Mise à l'echelle hors de la chaîne {#off-chain-scaling}
diff --git a/src/content/translations/fr/nft/index.md b/src/content/translations/fr/nft/index.md
index 6430b8406b3..38e7ccdf695 100644
--- a/src/content/translations/fr/nft/index.md
+++ b/src/content/translations/fr/nft/index.md
@@ -406,7 +406,7 @@ On estime que les mises à niveau d'évolutivité vont permettre au réseau de t
[Vitalik Buterin sur le potentiel de transactions par seconde avec la fragmentation](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Au strict minimum, la fragmentation va permettre 64 fois plus de transactions à la seconde qu'à l'heure actuelle, avec environ 15 transactions à la seconde. C'est la quantité de chaînes de fragments (données et capacité supplémentaires) qui est introduite. [En savoir plus sur les chaînes de fragments](/upgrades/shard-chains/)
+Au strict minimum, la fragmentation va permettre 64 fois plus de transactions à la seconde qu'à l'heure actuelle, avec environ 15 transactions à la seconde. C'est la quantité de chaînes de fragments (données et capacité supplémentaires) qui est introduite. [En savoir plus sur les chaînes de fragments](/upgrades/sharding/)
Cela signifie que nous pouvons estimer le temps qu'il faudra pour traiter 100 000 transactions et le comparer à l'exemple Visa ci-dessus.
diff --git a/src/content/translations/fr/upgrades/beacon-chain/index.md b/src/content/translations/fr/upgrades/beacon-chain/index.md
index f2e6c29c6f2..f2e527afc0b 100644
--- a/src/content/translations/fr/upgrades/beacon-chain/index.md
+++ b/src/content/translations/fr/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Vous pouvez le connaître sous le nom de « Phase 0 » sur les fe
## Que fait la chaîne phare ? {#what-does-the-beacon-chain-do}
-La chaîne phare dirigera ou coordonnera le réseau étendu de [fragments](/upgrades/shard-chains/) et de [validateurs](/staking/). Mais ce ne sera pas comme le [réseau principal Ethereum](/glossary/#mainnet) d'aujourd'hui. Elle ne peut gérer ni les comptes ni les contrats intelligents.
+La chaîne phare dirigera ou coordonnera le réseau étendu de [fragments](/upgrades/sharding/) et de [validateurs](/staking/). Mais ce ne sera pas comme le [réseau principal Ethereum](/glossary/#mainnet) d'aujourd'hui. Elle ne peut gérer ni les comptes ni les contrats intelligents.
Le rôle de la chaîne phare évoluera au fil du temps, mais restera un élément fondamental de l'[Ethereum sécurisé, durable et évolutif auquel nous travaillons](/upgrades/vision/).
@@ -33,7 +33,7 @@ Miser des ETH et devenir validateur est plus simple que de [miner](/developers/d
Si vous souhaitez devenir validateur et aider à sécuriser la chaîne phare, familiarisez-vous avec le concept de mise en jeu.
-Il s'agit également d'un changement important pour une autre mise à jour : [les chaînes de fragments](/upgrades/shard-chains/).
+Il s'agit également d'un changement important pour une autre mise à jour : [les chaînes de fragments](/upgrades/sharding/).
### Mise en place des chaînes de fragments {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ La chaîne phare existera d'abord séparément du réseau principal Ethereum que
Les chaînes de fragments ne peuvent s'ajouter en toute sécurité dans l'écosystème Ethereum que s'il existe un mécanisme de consensus sur la preuve de mise à enjeu. La chaîne phare introduira la mise en jeu, ouvrant la voie à la mise à niveau suivante : la chaîne de fragments.
-
+
Chaînes de fragments
diff --git a/src/content/translations/fr/upgrades/merge/index.md b/src/content/translations/fr/upgrades/merge/index.md
index 527623f5e74..23b1f1298f8 100644
--- a/src/content/translations/fr/upgrades/merge/index.md
+++ b/src/content/translations/fr/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Restez à jour avec le [Blog de Recherche et Développement EF](https://blog.eth
Il s'agira d'une évaluation continue de la part de la communauté quant à la potentielle nécessité de plusieurs séries de chaînes fragmentées afin de permettre une évolutivité sans fin.
-
+
Chaines de fragments
diff --git a/src/content/translations/fr/upgrades/shard-chains/index.md b/src/content/translations/fr/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/fr/upgrades/shard-chains/index.md
rename to src/content/translations/fr/upgrades/sharding/index.md
diff --git a/src/content/translations/hi/upgrades/beacon-chain/index.md b/src/content/translations/hi/upgrades/beacon-chain/index.md
index 9e27fd7cfa0..85247f0f0c1 100644
--- a/src/content/translations/hi/upgrades/beacon-chain/index.md
+++ b/src/content/translations/hi/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: आप इसे तकनीकी रोडमैप पर "
## बीकन चेन क्या करती है? {#what-does-the-beacon-chain-do}
-बीकन चेन [शार्ड](/upgrades/shard-chains/) और [स्टेकर](/staking/) के विस्तारित नेटवर्क का संचालन या समन्वय करेगी। लेकिन यह आज के [इथेरियम मेननेट](/glossary/#mainnet) की तरह नहीं होगा। यह खातों या स्मार्ट अनुबंधों को संभाल नहीं सकता है।
+बीकन चेन [शार्ड](/upgrades/sharding/) और [स्टेकर](/staking/) के विस्तारित नेटवर्क का संचालन या समन्वय करेगी। लेकिन यह आज के [इथेरियम मेननेट](/glossary/#mainnet) की तरह नहीं होगा। यह खातों या स्मार्ट अनुबंधों को संभाल नहीं सकता है।
बीकन चेन की भूमिका समय के साथ बदल जाएगी, लेकिन यह [ सुरक्षित, टिकाऊ और स्केलेबल इथेरियम के लिए एक मूलभूत घटक है, जिसके लिए हम काम कर रहे हैं ](/upgrades/vision/)।
@@ -33,7 +33,7 @@ summaryPoint4: आप इसे तकनीकी रोडमैप पर "
यदि आप एक सत्यापनकर्ता बनने में रुचि रखते हैं और बीकन चेन को सुरक्षित करने में मदद करते हैं, तो स्टेकिंग के बारे में और जानें।
-यह दूसरे Eth2 अपग्रेड के लिए एक महत्वपूर्ण बदलाव भी है: [शार्ड चेन](/upgrades/shard-chains/)।
+यह दूसरे Eth2 अपग्रेड के लिए एक महत्वपूर्ण बदलाव भी है: [शार्ड चेन](/upgrades/sharding/)।
### शार्ड चेन के लिए सेटिंग {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ Eth2 अपग्रेड कुछ हद तक परस्पर जुड
शार्ड चेन केवल इथेरियम इकोसिस्टम में सुरक्षित रूप से हिस्सेदारी के लिए सर्वसम्मति के साथ हिस्सेदारी कर सकती है। बीकन चेन स्टेकिंग को पेश करेगा, शार्ड चेन अपग्रेड का अनुसरण करने का मार्ग प्रशस्त करेगा।
-शार्ड चेन
+शार्ड चेन
diff --git a/src/content/translations/hi/upgrades/merge/index.md b/src/content/translations/hi/upgrades/merge/index.md
index aed563b5e50..74fd687f226 100644
--- a/src/content/translations/hi/upgrades/merge/index.md
+++ b/src/content/translations/hi/upgrades/merge/index.md
@@ -17,7 +17,7 @@ summaryPoint4: आप इसे तकनीकी रोडमैप पर"
## डॉकिंग क्या है? {#what-is-the-docking}
-यह याद रखना महत्वपूर्ण है कि शुरू में, अन्य Eth2 अपग्रेड को [मेननेट](/glossary/#mainnet) - आज हम जिस चेन का उपयोग करते हैं, से अलग-अलग शिप किया जा रहा है। इथेरियम मेननेट को [कार्य-के-प्रमाण](/developers/docs/consensus-mechanisms/pow/) द्वारा सुरक्षित किया जाता रहेगा, जबकि [बीकन चेन](/upgrades/beacon-chain/) और इसके [शार्ड चेन](/upgrades/shard-chains/) [स्टेक-के-प्रमाण](/developers/docs/consensus-mechanisms/pos/) के समानांतर में चलते हैं। डॉकिंग तब होता है जब इन दोनों प्रणालियों को एक साथ मिला दिया जाता है।
+यह याद रखना महत्वपूर्ण है कि शुरू में, अन्य Eth2 अपग्रेड को [मेननेट](/glossary/#mainnet) - आज हम जिस चेन का उपयोग करते हैं, से अलग-अलग शिप किया जा रहा है। इथेरियम मेननेट को [कार्य-के-प्रमाण](/developers/docs/consensus-mechanisms/pow/) द्वारा सुरक्षित किया जाता रहेगा, जबकि [बीकन चेन](/upgrades/beacon-chain/) और इसके [शार्ड चेन](/upgrades/sharding/) [स्टेक-के-प्रमाण](/developers/docs/consensus-mechanisms/pos/) के समानांतर में चलते हैं। डॉकिंग तब होता है जब इन दोनों प्रणालियों को एक साथ मिला दिया जाता है।
कल्पना कीजिए कि इथेरियम एक अंतरिक्ष जहाज है, जो तारों के बीच यात्रा के लिए बिल्कुल तैयार नहीं है। बीकन चेन और शार्ड चेन के साथ समुदाय ने एक नया इंजन और एक कठोर पतवार बनाया है। जब यह समय होता है, तो वर्तमान जहाज इस नई प्रणाली के साथ डॉक करेगा, ताकि यह एक जहाज बन सके, कुछ गंभीर प्रकाश वर्ष के लिए डाला जा सके और ब्रह्मांड पर ले जाने के लिए तैयार हो सके।
@@ -45,4 +45,4 @@ Eth2 अपग्रेड कुछ हद तक परस्पर जुड
मेननेट शार्ड बनने के साथ, शार्ड चेन का सफल क्रियान्वयन इस अपग्रेड के लिए महत्वपूर्ण है। यह संभावना है कि संक्रमण समुदाय को यह निर्णय लेने में मदद करने में महत्वपूर्ण भूमिका निभाएगा कि क्या एक दूसरे अपग्रेड को शार्डिंग में रोल आउट किया जाए। इस अपग्रेड से अन्य शार्ड जैसे मेननेट: वे लेन-देन और स्मार्ट अनुबंध को संभालने में सक्षम होंगे और न केवल अधिक डेटा प्रदान करेंगे।
-शार्ड चेन
+शार्ड चेन
diff --git a/src/content/translations/hi/upgrades/shard-chains/index.md b/src/content/translations/hi/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/hi/upgrades/shard-chains/index.md
rename to src/content/translations/hi/upgrades/sharding/index.md
diff --git a/src/content/translations/hr/upgrades/beacon-chain/index.md b/src/content/translations/hr/upgrades/beacon-chain/index.md
index 96b049f280c..d2d30640496 100644
--- a/src/content/translations/hr/upgrades/beacon-chain/index.md
+++ b/src/content/translations/hr/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: To možete prepoznati kao „Fazu 0” na tehničkom planu.
## Što radi Beacon Chain? {#what-does-the-beacon-chain-do}
-Beacon Chain će dirigirati ili uskladiti proširenu mrežu [ djelića](/upgrades/shard-chains/) i [učesnika](/staking/). Ali neće biti kao današnja [glavna mreža Ethereum](/glossary/#mainnet). Ne podržava račune ili pametne ugovore.
+Beacon Chain će dirigirati ili uskladiti proširenu mrežu [ djelića](/upgrades/sharding/) i [učesnika](/staking/). Ali neće biti kao današnja [glavna mreža Ethereum](/glossary/#mainnet). Ne podržava račune ili pametne ugovore.
Beacon Chain će tijekom vremena mijenjati ulogu, međutim to je temeljna komponenta za [siguran, održiv i nadogradiv Ethereum na kojem radimo](/upgrades/vision/).
@@ -33,7 +33,7 @@ Ulagati i postati validator, jednostavnije je od [ rudarenja ](/developers/docs/
Ako ste zainteresirani za validiranje i pomoć u osiguranju za Beacon Chain, saznajte više o sudjelovanju.
-Ovo je također važna promjena za drugu nadogradnju Eth2: [lanci djelića](/upgrades/shard-chains/).
+Ovo je također važna promjena za drugu nadogradnju Eth2: [lanci djelića](/upgrades/sharding/).
### Postavljanje lanaca djelića {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ Beacon Chain će u početku postojati odvojeno od glavne mreže Ethereum mreže
Lanci djelića mogu sigurno ući u Ethereumov ekosustav samo ako je uspostavljen mehanizam konsenzusa proof-of-stake. Beacon Chain predstavit će ulaganje, radeći put za nadogradnju lanca djelića.
-Lanci djelića
+Lanci djelića
diff --git a/src/content/translations/hr/upgrades/merge/index.md b/src/content/translations/hr/upgrades/merge/index.md
index b38371508bf..1b981601ade 100644
--- a/src/content/translations/hr/upgrades/merge/index.md
+++ b/src/content/translations/hr/upgrades/merge/index.md
@@ -17,7 +17,7 @@ summaryPoint4: To vam može biti poznato kao „faza 1.5” na tehničkim planov
## Što je spajanje? {#what-is-the-docking}
-Važno je imati na umu da se u početku ostale nadogradnje Eth2 isporučuju odvojeno od [ glavne mreže ](/glossary/#mainnet) – lanca kojim se koristimo danas. Glavna mreža Ethereum i dalje biti osigurana pomoću mehanizma [proof-of-work](/developers/docs/consensus-mechanisms/pow/), čak i dok [Beacon Chain](/upgrades/beacon-chain/) i njegovi [lanci djelića](/upgrades/shard-chains/) rade paralelno pomoću mehanizma [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). Spajanje je kad se ova dva sustava sjedine.
+Važno je imati na umu da se u početku ostale nadogradnje Eth2 isporučuju odvojeno od [ glavne mreže ](/glossary/#mainnet) – lanca kojim se koristimo danas. Glavna mreža Ethereum i dalje biti osigurana pomoću mehanizma [proof-of-work](/developers/docs/consensus-mechanisms/pow/), čak i dok [Beacon Chain](/upgrades/beacon-chain/) i njegovi [lanci djelića](/upgrades/sharding/) rade paralelno pomoću mehanizma [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). Spajanje je kad se ova dva sustava sjedine.
Zamislite da je Ethereum svemirski brod koji nije baš spreman za međuzvjezdano putovanje. Zajednica je s nadogradnjom Beacon chain i lancima djelića izgradila novi motor i očvrsnuti trup. Kad dođe vrijeme, trenutačni brod pristat će uz novi sustav i oni će postati jedno, spremni za ozbiljne svjetlosne godine i zauzimanje svemira.
@@ -45,4 +45,4 @@ Nakon spajanja, bit će dodijeljeni učesnici koji će provjeriti valjanost mre
Kad glavna mreža postane djelić, uspješna implementacija lanaca djelića bit će presudna za ovu nadogradnju. Vjerojatno će tranzicija igrati važnu ulogu u pomaganju zajednici da odluči hoće li pokrenuti drugu nadogradnju na metodu razdjeljivanja. Ova će nadogradnja kreirati druge djeliće poput glavne mreže: oni će moći obrađivati transakcije i pametne ugovore, a ne samo pružati više podataka.
-Lanci djelića
+Lanci djelića
diff --git a/src/content/translations/hr/upgrades/shard-chains/index.md b/src/content/translations/hr/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/hr/upgrades/shard-chains/index.md
rename to src/content/translations/hr/upgrades/sharding/index.md
diff --git a/src/content/translations/hu/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/hu/developers/docs/consensus-mechanisms/pos/index.md
index 35e4ddc8b25..b6d3bfce457 100644
--- a/src/content/translations/hu/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/hu/developers/docs/consensus-mechanisms/pos/index.md
@@ -37,7 +37,7 @@ Ha tanúsítasz egy rosszindulatú blokkot, akkor elveszted a letéted.
### A Beacon Chain {#the-beacon-chain}
-Amikor az Ethereum leváltja a proof-of-work-öt a proof-of-stake-kel, hozzáadott komplexitás fog életbe lépni a [shard láncok](/upgrades/shard-chains/) által. Ezek különálló blokkláncok, melynek szükségük van validátorokra, hogy tranzakciókat dolgozzanak fel és új blokkokat hozzanak létre. A terv az, hogy 64 shard láncot fogunk létrehozni, melyeknek megosztottan egyet kell érteniük a hálózat állapotára vonatkozóan. Így további koordináció szükségeltetik, ezt pedig [a beacon chain](/upgrades/beacon-chain/) fogja biztosítani.
+Amikor az Ethereum leváltja a proof-of-work-öt a proof-of-stake-kel, hozzáadott komplexitás fog életbe lépni a [shard láncok](/upgrades/sharding/) által. Ezek különálló blokkláncok, melynek szükségük van validátorokra, hogy tranzakciókat dolgozzanak fel és új blokkokat hozzanak létre. A terv az, hogy 64 shard láncot fogunk létrehozni, melyeknek megosztottan egyet kell érteniük a hálózat állapotára vonatkozóan. Így további koordináció szükségeltetik, ezt pedig [a beacon chain](/upgrades/beacon-chain/) fogja biztosítani.
A Beacon Chain állapot információkat kap a shardoktól, melyet elérhetővé tesz a többi shard számára, hogy azok szinkronban tudjanak maradni. A Beacon Chain fogja kezelni a validátorokat is a letétbetételtől egészen a jutalmak és büntetések kiosztásáig.
diff --git a/src/content/translations/hu/upgrades/beacon-chain/index.md b/src/content/translations/hu/upgrades/beacon-chain/index.md
index c75257f0496..9088adf07b8 100644
--- a/src/content/translations/hu/upgrades/beacon-chain/index.md
+++ b/src/content/translations/hu/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: A technikai ütemtervekben "Fázis 0"-ként is ismerheted.
## Mit csinál a Beacon Chain? {#what-does-the-beacon-chain-do}
-A Beacon Chain fogja koordinálni vagy vezetni a [shardokból](/upgrades/shard-chains/) és [stakerekből](/staking/) álló kiterjesztett hálózatot. De nem olyan lesz, mint jelenleg az [Ethereum főhálózat](/glossary/#mainnet). Nem fog tudni számlákat vagy okosszerződéseket kezelni.
+A Beacon Chain fogja koordinálni vagy vezetni a [shardokból](/upgrades/sharding/) és [stakerekből](/staking/) álló kiterjesztett hálózatot. De nem olyan lesz, mint jelenleg az [Ethereum főhálózat](/glossary/#mainnet). Nem fog tudni számlákat vagy okosszerződéseket kezelni.
A Beacon Chain szerepe meg fog változni idővel, de egy olyan alapvető összetevője [ a biztonságos, fenntartható és skálázható Ethereumnak, amiért dolgozunk](/upgrades/vision/).
@@ -33,7 +33,7 @@ A letétbe helyezés és a validátorrá válás egyszerűbb, mint a [bányásza
Ha érdekel a letétbe helyezés és szeretnél segíteni a Beacon Chain biztosításában, akkor tudj meg többet a letétbe helyezésről.
-Ez a második Eth2 fejlesztésnél is fontos változás: [a shard láncoknál](/upgrades/shard-chains/).
+Ez a második Eth2 fejlesztésnél is fontos változás: [a shard láncoknál](/upgrades/sharding/).
### Shard láncok előkészítése {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ A Beacon Chain eleinte különállóan fog létezni az Ethereum főhálózattól
A shard láncokat csak a proof-of-stake konszenzus mechnanizmussal lehet biztonságosan bevezetni az Ethereum ökoszisztémába. A Beacon Chain bevezeti a letétbe helyezést (staking) ezzel lekövezve a shard láncok bevezetéséhez szükséges utat.
-Shard láncok
+Shard láncok
diff --git a/src/content/translations/hu/upgrades/merge/index.md b/src/content/translations/hu/upgrades/merge/index.md
index cd807d6702a..444aefbd46e 100644
--- a/src/content/translations/hu/upgrades/merge/index.md
+++ b/src/content/translations/hu/upgrades/merge/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Úgy is ismerheted, mint a Fázis 1.5 a technikai ütemtervek sze
## Mi az a dokkolás? {#what-is-the-docking}
-Fontos megjegyezni, hogy eredetileg a többi Eth2 fejlesztés a [főhálózattól](/glossary/#mainnet) - azaz a lánctól, amit ma is használunk - külön kerül bevezetésre. Az Ethereum főhálózat biztonságát továbbra is a [proof-of-work](/developers/docs/consensus-mechanisms/pow/) szolgáltatja majd, még akkor is amikor [a Beacon Chain](/upgrades/beacon-chain/) és a [shard láncok](/upgrades/shard-chains/) párhuzamosan futnak majd a [proof-of-stake](/developers/docs/consensus-mechanisms/pos/) használatával. A dokkolás az, amikor ez a két rendszer egybeolvad.
+Fontos megjegyezni, hogy eredetileg a többi Eth2 fejlesztés a [főhálózattól](/glossary/#mainnet) - azaz a lánctól, amit ma is használunk - külön kerül bevezetésre. Az Ethereum főhálózat biztonságát továbbra is a [proof-of-work](/developers/docs/consensus-mechanisms/pow/) szolgáltatja majd, még akkor is amikor [a Beacon Chain](/upgrades/beacon-chain/) és a [shard láncok](/upgrades/sharding/) párhuzamosan futnak majd a [proof-of-stake](/developers/docs/consensus-mechanisms/pos/) használatával. A dokkolás az, amikor ez a két rendszer egybeolvad.
Képzeld el, hogy az Ethereum egy űrhajó, ami még nem teljesen áll készen egy csillagközi utazásra. A Beacon Chainnel és a shard láncokkal a közösség egy új hajtóművet és egy erősebb hajótestet épített. Ha eljön az idő, a meglévő hajó dokkol ezzel az új rendszerrel, eggyé válik vele és készen áll arra, hogy néhány fényév alatt meghódítsa az univerzumot.
@@ -45,4 +45,4 @@ Amint megtörtént a dokkolás, a letétbe helyezőket kijelölik az Ethereum f
Mivel a főhálózat egy sharddá válik, a shard láncok sikeres implementációja kritikus ezen fejlesztési lépés szempontjából. Valószínű, hogy az átmenet egy fontos szerepet fog játszani, hogy a közösség eldöntse szeretne-e egy második sharding fejlesztést. Ez a fejlesztés a többi shardot is a főhálózathoz hasonlóvá teszi: képesek lesznek tranzakciókat és okosszerződéseket feldolgozni, nem csak több adatot biztosítani.
-Shard láncok
+Shard láncok
diff --git a/src/content/translations/hu/upgrades/shard-chains/index.md b/src/content/translations/hu/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/hu/upgrades/shard-chains/index.md
rename to src/content/translations/hu/upgrades/sharding/index.md
diff --git a/src/content/translations/id/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/id/developers/docs/consensus-mechanisms/pos/index.md
index 08b1f796885..baae36b6084 100644
--- a/src/content/translations/id/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/id/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ Bukti taruhan hadir dengan sejumlah peningkatan pada sistem bukti kerja:
- efisiensi energi yang lebih baik - Anda tidak perlu menggunakan banyak blok penambangan energi
- hambatan masuk yang lebih rendah, persyaratan perangkat keras yang berkurang – Anda tidak memerlukan perangkat keras elit untuk mendapat peluang membuat blok baru
- kekebalan yang lebih kuat terhadap sentralisasi - bukti taruhan harus mengarah ke lebih banyak node di jaringan
-- dukungan yang lebih kuat untuk [rantai shard](/upgrades/shard-chains/) – sebuah peningkatan kunci dalam perluasan jaringan Ethereum
+- dukungan yang lebih kuat untuk [rantai shard](/upgrades/sharding/) – sebuah peningkatan kunci dalam perluasan jaringan Ethereum
## Bukti taruhan, penaruhan, dan validator {#pos-staking-validators}
@@ -37,7 +37,7 @@ Jika Anda melakukan pengesahan terhadap blok jahat, Anda akan kehilangan taruhan
### Rantai suar {#the-beacon-chain}
-Ketika Ethereum menggantikan bukti kerja dengan bukti taruhan, akan ada kompleksitas tambahan dari [rantai shard](/upgrades/shard-chains/). Ini adalah blockchain terpisah yang membutuhkan validator untuk memproses transaksi dan membuat blok baru. Rencananya adalah memiliki 64 rantai shard dan mereka semua membutuhkan pemahaman bersama tentang keadaan jaringan. Akibatnya, diperlukan koordinasi ekstra dan akan dilakukan oleh [rantai suar](/upgrades/beacon-chain/).
+Ketika Ethereum menggantikan bukti kerja dengan bukti taruhan, akan ada kompleksitas tambahan dari [rantai shard](/upgrades/sharding/). Ini adalah blockchain terpisah yang membutuhkan validator untuk memproses transaksi dan membuat blok baru. Rencananya adalah memiliki 64 rantai shard dan mereka semua membutuhkan pemahaman bersama tentang keadaan jaringan. Akibatnya, diperlukan koordinasi ekstra dan akan dilakukan oleh [rantai suar](/upgrades/beacon-chain/).
Rantai suar menerima informasi state dari shard dan membuatnya tersedia untuk shard lainnya, sehingga jaringan dapat terus disinkronkan. Rantai suar juga akan mengatur validator mulai dari mendaftarkan deposito taruhan mereka hingga menerbitkan imbalan dan penalti mereka.
diff --git a/src/content/translations/id/developers/docs/scaling/index.md b/src/content/translations/id/developers/docs/scaling/index.md
index 3899ec68a15..df04c681e50 100644
--- a/src/content/translations/id/developers/docs/scaling/index.md
+++ b/src/content/translations/id/developers/docs/scaling/index.md
@@ -27,7 +27,7 @@ Metode penskalaan ini memerlukan perubahan pada protokol Ethereum (lapisan 1 [Ja
Sharding adalah proses pemisahan basis data secara horizontal untuk menyebarkan muatan. Dalam konteks Ethereum, sharding akan mengurangi kemacetan jaringan dan meningkatkan transaksi per detik dengan membuat rantai baru, yang dikenal sebagai “shard.” Ini juga akan meringankan beban setiap validator yang tidak lagi diharuskan untuk memroses keseluruhan transaksi di seluruh jaringan.
-Pelajari lebih lanjut tentang [sharding](/upgrades/shard-chains/).
+Pelajari lebih lanjut tentang [sharding](/upgrades/sharding/).
## Penskalaan off-chain {#off-chain-scaling}
diff --git a/src/content/translations/id/nft/index.md b/src/content/translations/id/nft/index.md
index e2f53df66e4..f11814efb6f 100644
--- a/src/content/translations/id/nft/index.md
+++ b/src/content/translations/id/nft/index.md
@@ -406,7 +406,7 @@ Diperkirakan bahwa peningkatan skalabilitas akan memungkinkan jaringan untuk mem
[Vitalik Buterik membahas transaksi per detik yang potensial dengan sharding](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Pada tingkat terendah, sharding akan memungkinkan 64 kali jumlah transaksi dari jumlah saat ini yang berada sekitar 15 transaksi. Itulah jumlah rantai shard (data dan kapasitas tambahan) yang akan dimasukkan. [Selengkapnya tentang rantai shard](/upgrades/shard-chains/)
+Pada tingkat terendah, sharding akan memungkinkan 64 kali jumlah transaksi dari jumlah saat ini yang berada sekitar 15 transaksi. Itulah jumlah rantai shard (data dan kapasitas tambahan) yang akan dimasukkan. [Selengkapnya tentang rantai shard](/upgrades/sharding/)
Itu berarti kita dapat memperkirakan berapa lama waktu yang diperlukan untuk memroses 100.000 transaksi, sehingga kita dapat membandingkannya dengan contoh Visa di atas.
diff --git a/src/content/translations/id/upgrades/beacon-chain/index.md b/src/content/translations/id/upgrades/beacon-chain/index.md
index 107a4c5745a..7266ebd6e17 100644
--- a/src/content/translations/id/upgrades/beacon-chain/index.md
+++ b/src/content/translations/id/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Anda mungkin mengenalnya sebagai "Fase 0" pada roadmap teknis.
## Apa yang dilakukan oleh Rantai Suar? {#what-does-the-beacon-chain-do}
-Rantai Suar akan mengadakan atau mengoordinasi jaringan yang sudah diperluas dari [shard](/upgrades/shard-chains/) dan [penaruh](/staking/). Tapi itu tidak akan sama seperti [Jaringan Utama Ethereum](/glossary/#mainnet) saat ini. Rantai suar tidak bisa menangani akun ataupun kontrak pintar.
+Rantai Suar akan mengadakan atau mengoordinasi jaringan yang sudah diperluas dari [shard](/upgrades/sharding/) dan [penaruh](/staking/). Tapi itu tidak akan sama seperti [Jaringan Utama Ethereum](/glossary/#mainnet) saat ini. Rantai suar tidak bisa menangani akun ataupun kontrak pintar.
Peran Rantai Suar akan berubah seiring berjalannya waktu, namun rantai ini merupakan komponen dasar untuk [jaringan Ethereum yang aman, berkelanjutan, dan terukur yang sedang kami kerjakan](/upgrades/vision/).
@@ -33,7 +33,7 @@ Penaruhan dan menjadi validator lebih mudah daripada [menambang](/developers/doc
Jika Anda tertarik untuk menjadi validator dan membantu mengamankan Rantai Suar, pelajari selengkapnya tentang penaruhan.
-Ini juga merupakan perubahan penting untuk peningkatan lainnya: [rantai shard](/upgrades/shard-chains/).
+Ini juga merupakan perubahan penting untuk peningkatan lainnya: [rantai shard](/upgrades/sharding/).
### Menyiapkan rantai shard {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ Rantai Suar, pada awalnya, akan hadir terpisah dari Jaringan Utama Ethereum yang
Rantai shard hanya dapat masuk dalam ekosistem Ethereum dengan mekanisme konsesus bukti taruhan. Rantai Suar akan memperkenalkan penaruhan, menyiapkan jalan bagi peningkatan rantai shard berikutnya.
-
+
Rantai shard
diff --git a/src/content/translations/id/upgrades/merge/index.md b/src/content/translations/id/upgrades/merge/index.md
index 15a4f2b4590..6581fd6bc27 100644
--- a/src/content/translations/id/upgrades/merge/index.md
+++ b/src/content/translations/id/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Pada awalnya, rencananya adalah melanjutkan pengembangan rantai shard sebelum Pe
Ini akan menjadi penilaian berkelanjutan dari komunitas seiring dengan kebutuhan akan potensi beberapa putaran rantai shard untuk memungkinkan skalabilitas yang tak terbatas.
-
+
Pecahan rantai jaringan
diff --git a/src/content/translations/id/upgrades/shard-chains/index.md b/src/content/translations/id/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/id/upgrades/shard-chains/index.md
rename to src/content/translations/id/upgrades/sharding/index.md
diff --git a/src/content/translations/it/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/it/developers/docs/consensus-mechanisms/pos/index.md
index 04ea3358c35..d0e440cfc8f 100644
--- a/src/content/translations/it/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/it/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ La proof-of-stake porta con sé una serie di miglioramenti rispetto al sistema P
- migliore efficienza energetica: non occorre molta energia per il mining dei blocchi
- minori barriere all'ingresso, requisiti hardware ridotti: non serve hardware d'èlite per avere la possibilità di creare nuovi blocchi
- maggiore immunità alla centralizzazione: la proof-of-stake dovrebbe portare un maggior numero di nodi alla rete
-- Migliore supporto per le [catene di shard](/upgrades/shard-chains/): un aggiornamento importante per scalare la rete Ethereum
+- Migliore supporto per le [catene di shard](/upgrades/sharding/): un aggiornamento importante per scalare la rete Ethereum
## Proof-of-stake, staking e validatori {#pos-staking-validators}
@@ -37,7 +37,7 @@ Se attesti un blocco dannoso, perdi il tuo stake.
### La beacon chain {#the-beacon-chain}
-Dal momento in cui Ethereum sostituirà il Proof of Work con il proof-of-stake, verrà aggiunta la complessità delle [catene di shard](/upgrades/shard-chains/). Si tratta di blockchain separate, in cui i validatori dovranno elaborare transazioni e creare nuovi blocchi. Si prevede di avere 64 shard chain e tutte dovranno avere una comprensione condivisa dello stato della rete. Ne risulta che è necessaria una maggiore coordinazione, che sarà garantita [dalla Beacon Chain](/upgrades/beacon-chain/).
+Dal momento in cui Ethereum sostituirà il Proof of Work con il proof-of-stake, verrà aggiunta la complessità delle [catene di shard](/upgrades/sharding/). Si tratta di blockchain separate, in cui i validatori dovranno elaborare transazioni e creare nuovi blocchi. Si prevede di avere 64 shard chain e tutte dovranno avere una comprensione condivisa dello stato della rete. Ne risulta che è necessaria una maggiore coordinazione, che sarà garantita [dalla Beacon Chain](/upgrades/beacon-chain/).
La beacon chain riceve informazioni sullo stato dagli shard e le rende disponibili ad altri shard, in modo che la rete possa rimanere sincronizzata. La beacon chain gestirà anche i validatori, dalla registrazione dei depositi di stake fino all'emissione delle ricompense o delle penalità.
diff --git a/src/content/translations/it/developers/docs/scaling/index.md b/src/content/translations/it/developers/docs/scaling/index.md
index c23aa5fcac4..4aba9861710 100644
--- a/src/content/translations/it/developers/docs/scaling/index.md
+++ b/src/content/translations/it/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ Questo metodo di scalabilità richiede modifiche al protocollo Ethereum ([rete p
Sharding è il processo di suddivisione orizzontale di un database per distribuire il carico. In un contesto Ethereum, lo sharding ridurrà la congestione della rete e aumenterà le transazioni al secondo creando nuove catene, note come "shard". Questo alleggerirà anche il carico per ogni validatore, che non dovrà più elaborare la totalità di tutte le transazioni sulla rete.
-Ulteriori informazioni sullo [sharding](/upgrades/shard-chains/).
+Ulteriori informazioni sullo [sharding](/upgrades/sharding/).
## Scalabilità off-chain {#off-chain-scaling}
diff --git a/src/content/translations/it/nft/index.md b/src/content/translations/it/nft/index.md
index d5401148a2b..89cedebd331 100644
--- a/src/content/translations/it/nft/index.md
+++ b/src/content/translations/it/nft/index.md
@@ -406,7 +406,7 @@ Si stima che gli aggiornamenti di scalabilità consentiranno alla rete di elabor
[Vitalik Buterin sulle transazioni per secondo potenziali con lo sharding](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Come minimo, lo sharding consentirà 64 volte la quantità di transazioni di oggi, che si attesta a circa 15 transazioni. È la quantità di shard chain (dati e capacità supplementari) che vengono introdotte. [Maggiori informazioni sulle shard chain](/upgrades/shard-chains/)
+Come minimo, lo sharding consentirà 64 volte la quantità di transazioni di oggi, che si attesta a circa 15 transazioni. È la quantità di shard chain (dati e capacità supplementari) che vengono introdotte. [Maggiori informazioni sulle shard chain](/upgrades/sharding/)
Ciò significa che possiamo stimare quanto tempo ci vorrà per elaborare 100.000 transazioni in modo da poterlo confrontare con l'esempio di Visa sopra riportato.
diff --git a/src/content/translations/it/upgrades/beacon-chain/index.md b/src/content/translations/it/upgrades/beacon-chain/index.md
index 1034f071993..76c3fff7c9e 100644
--- a/src/content/translations/it/upgrades/beacon-chain/index.md
+++ b/src/content/translations/it/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Potresti conoscere questa come "Fase 0" sulle roadmap tecniche.
## Cosa fa la beacon chain? {#what-does-the-beacon-chain-do}
-La Beacon Chain condurrà o coordinerà la rete ampliata di [shard](/upgrades/shard-chains/) e [staker](/staking/). Ma non sarà come l'attuale [Rete principale di Ethereum](/glossary/#mainnet). Non è in grado di gestire gli account o gli Smart Contracts.
+La Beacon Chain condurrà o coordinerà la rete ampliata di [shard](/upgrades/sharding/) e [staker](/staking/). Ma non sarà come l'attuale [Rete principale di Ethereum](/glossary/#mainnet). Non è in grado di gestire gli account o gli Smart Contracts.
Il ruolo della beacon chain cambierà con il passare del tempo ma è una componente fondamentale per [la sicurezza, la sostenibilità e la scalabilità di Ethereum che stiamo cercando di raggiungere](/upgrades/vision/).
@@ -33,7 +33,7 @@ Fare staking e diventare validatore è più facile che [fare mining](/developers
Se sei interessato a diventare un validatore e ad contribuire a proteggere la beacon chain, scopri di più sullo staking.
-È anche un importante cambiamento per un altro aggiornamento: [shard chains](/upgrades/shard-chains/).
+È anche un importante cambiamento per un altro aggiornamento: [shard chains](/upgrades/sharding/).
### Prepararsi alle shard chain {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ In un primo momento la beacon chain godrà di vita separata rispetto all'attuale
Le shard chain potranno entrare in modo sicuro nell'ecosistema Ethereum solo quando sarà presente un meccanismo di consenso proof of stake. La beacon chain introdurrà lo staking, aprendo la strada al successivo upgrade basato sulla shard chain.
-
+
Shard chain
diff --git a/src/content/translations/it/upgrades/merge/index.md b/src/content/translations/it/upgrades/merge/index.md
index 900daa32a12..49bbb3a58a4 100644
--- a/src/content/translations/it/upgrades/merge/index.md
+++ b/src/content/translations/it/upgrades/merge/index.md
@@ -59,7 +59,7 @@ In origine, il piano era quello di operare sulle shard chain prima della Fusione
Si tratterà di una valutazione continua da parte della community circa la necessità di cicli potenzialmente multipli di shard chain per consentire una scalabilità senza fine.
-
+
Shard chain
diff --git a/src/content/translations/it/upgrades/shard-chains/index.md b/src/content/translations/it/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/it/upgrades/shard-chains/index.md
rename to src/content/translations/it/upgrades/sharding/index.md
diff --git a/src/content/translations/ja/nft/index.md b/src/content/translations/ja/nft/index.md
index 0344925fbe4..7c0245bb6fe 100644
--- a/src/content/translations/ja/nft/index.md
+++ b/src/content/translations/ja/nft/index.md
@@ -406,7 +406,7 @@ _また、イーサリアムは金融取引だけでなく、アプリケーシ
[Vitalik Buterin によるシャーディングでの 1 秒当たりのトランザクション件数見込みについて](https://twitter.com/VitalikButerin/status/1312905884549300224)
-最低でも、シャーディングは現在の約 15 件のトランザクション件数の 64 倍のトランザクションが可能になります。 それは、シャードチェーン(データや容量の追加)が導入されている分です。 [シャードチェーンの詳細](/upgrades/shard-chains/)
+最低でも、シャーディングは現在の約 15 件のトランザクション件数の 64 倍のトランザクションが可能になります。 それは、シャードチェーン(データや容量の追加)が導入されている分です。 [シャードチェーンの詳細](/upgrades/sharding/)
上記の Visa の例と比較できるよう、100,000 件のトランザクションを処理するのにかかる時間を見積もることができます。
diff --git a/src/content/translations/ja/upgrades/beacon-chain/index.md b/src/content/translations/ja/upgrades/beacon-chain/index.md
index fa243277656..c2c9cf2e0ed 100644
--- a/src/content/translations/ja/upgrades/beacon-chain/index.md
+++ b/src/content/translations/ja/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: 技術的なロードマップでは、「フェーズ0」と呼
## ビーコンチェーンとは {#what-does-the-beacon-chain-do}
-ビーコンチェーンは、[シャード](/upgrades/shard-chains/)と[ステーカー](/staking/)の拡張ネットワークを管理・調整します。 しかし、それは今日の [イーサリアムメインネット](/glossary/#mainnet) のようなものではなく、 アカウントやスマートコントラクトを処理しません。
+ビーコンチェーンは、[シャード](/upgrades/sharding/)と[ステーカー](/staking/)の拡張ネットワークを管理・調整します。 しかし、それは今日の [イーサリアムメインネット](/glossary/#mainnet) のようなものではなく、 アカウントやスマートコントラクトを処理しません。
ビーコンチェーンの役割は時間の経過とともに変わりますが、これは、私たちが取り組んでいる、[安全で持続可能、そしてスケーラブルなイーサリアム](/upgrades/vision/)の基本的な構成要素となります。
@@ -33,7 +33,7 @@ summaryPoint4: 技術的なロードマップでは、「フェーズ0」と呼
バリデータになり、ビーコンチェーンの安全性の確保にご興味がある場合は、ステーキングの詳細をご参照ください。
-これは、[シャードチェーン](/upgrades/shard-chains/)という別のアップグレードにとっても重要な変更です。
+これは、[シャードチェーン](/upgrades/sharding/)という別のアップグレードにとっても重要な変更です。
### シャードチェーンの設定 {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ summaryPoint4: 技術的なロードマップでは、「フェーズ0」と呼
シャードチェーンは、プルーフ・オブ・ステークのコンセンサスメカニズムがあることにより、イーサリアムのエコシステムに安全に参加することができます。 ビーコンチェーンはステーキングを導入し、シャードチェーンのアップグレードへの道を開きます。
-
+
シャードチェーン
diff --git a/src/content/translations/ja/upgrades/merge/index.md b/src/content/translations/ja/upgrades/merge/index.md
index 782668cb8d4..ab3691107b8 100644
--- a/src/content/translations/ja/upgrades/merge/index.md
+++ b/src/content/translations/ja/upgrades/merge/index.md
@@ -59,7 +59,7 @@ summaryPoint4: 旧称は「ドッキング」です。
ただし、無限のスケーラビリティを可能にするために、複数のシャードチェーンの潜在的な必要性について、継続的な評価検証がコミュニティにより行われています。
-
+
シャードチェーン
diff --git a/src/content/translations/ja/upgrades/shard-chains/index.md b/src/content/translations/ja/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/ja/upgrades/shard-chains/index.md
rename to src/content/translations/ja/upgrades/sharding/index.md
diff --git a/src/content/translations/ml/upgrades/beacon-chain/index.md b/src/content/translations/ml/upgrades/beacon-chain/index.md
index 653be6a047d..22a596cca79 100644
--- a/src/content/translations/ml/upgrades/beacon-chain/index.md
+++ b/src/content/translations/ml/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: സാങ്കേതിക റോഡ്മാപ്പിൽ "
## ബീക്കൺ ചെയിൻ എന്താണ് ചെയ്യുന്നത്? {#what-does-the-beacon-chain-do}
-ബീക്കൺ ചെയിൻ [ഷാർഡുകളുടെയും](/upgrades/shard-chains/) [സ്റ്റേക്കറുകളുടെയും](/staking/) വിപുലീകരിച്ച ശൃംഖല നടത്തുകയോ ഏകോപിപ്പിക്കുകയോ ചെയ്യും. പക്ഷെ ഇത് ഇന്നത്തെ [Ethereum mainnet](/glossary/#mainnet) പോലെ ആയിരിക്കില്ല. ഇതിന് അക്കൗണ്ടുകളോ സ്മാർട്ട് കരാറുകളോ കൈകാര്യം ചെയ്യാൻ കഴിയില്ല.
+ബീക്കൺ ചെയിൻ [ഷാർഡുകളുടെയും](/upgrades/sharding/) [സ്റ്റേക്കറുകളുടെയും](/staking/) വിപുലീകരിച്ച ശൃംഖല നടത്തുകയോ ഏകോപിപ്പിക്കുകയോ ചെയ്യും. പക്ഷെ ഇത് ഇന്നത്തെ [Ethereum mainnet](/glossary/#mainnet) പോലെ ആയിരിക്കില്ല. ഇതിന് അക്കൗണ്ടുകളോ സ്മാർട്ട് കരാറുകളോ കൈകാര്യം ചെയ്യാൻ കഴിയില്ല.
ബീക്കൺ ചെയിനിന്റെ പങ്ക് കാലക്രമേണ മാറും, പക്ഷേ ഇത് [സുരക്ഷിതവും സുസ്ഥിരവും വിപുലീകരിക്കാവുന്നതുമായ Ethereumനുള്ള അടിസ്ഥാന ഘടകമാണ്](/upgrades/vision/).
@@ -33,7 +33,7 @@ summaryPoint4: സാങ്കേതിക റോഡ്മാപ്പിൽ "
ഒരു വാലിഡേറ്ററാകാനും ബീക്കൺ ചെയിൻ സുരക്ഷിതമാക്കാൻ സഹായിക്കാനും നിങ്ങൾക്ക് താൽപ്പര്യമുണ്ടെങ്കിൽ, സ്റ്റേക്കിംഗിനെക്കുറിച്ച് കൂടുതലറിയുക .
-രണ്ടാമത്തെ Eth2 അപ്ഗേഡിനായുള്ള ഒരു പ്രധാന മാറ്റവും ഇതാണ്: [ ഷാർഡ് ചെയിനുകൾ ](/upgrades/shard-chains/).
+രണ്ടാമത്തെ Eth2 അപ്ഗേഡിനായുള്ള ഒരു പ്രധാന മാറ്റവും ഇതാണ്: [ ഷാർഡ് ചെയിനുകൾ ](/upgrades/sharding/).
### ഷാർഡ് ചെയ്നുകൾക്കായി സജ്ജമാക്കുന്നു {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ Eth2 അപ്ഗ്രേഡുകളെല്ലാം പരസ്പര
ഒരു പ്രൂഫ് ഓഫ് സ്റ്റേക്ക് കന്സെന്സസ് മെക്കാനിസം ഉണ്ടെങ്കില് മാത്രമേ ഷാർഡ് ചെയിനുകൾക്ക് സുരക്ഷിതമായി Ethereum ഇക്കോസിസ്റ്റത്തിലേക്ക് പ്രവേശിക്കാൻ കഴിയൂ. ഷാർഡ് ചെയിൻ അപ്ഗ്രേഡ് പിന്തുടരാൻ വഴിയൊരുക്കിക്കൊണ്ട് ബീക്കൺ ചെയിൻ സ്റ്റേക്കിംഗ് അവതരിപ്പിക്കും.
-ഷാർഡ് ചെയിനുകള്
+ഷാർഡ് ചെയിനുകള്
diff --git a/src/content/translations/ml/upgrades/merge/index.md b/src/content/translations/ml/upgrades/merge/index.md
index 9f518d6b370..cf43fe705ac 100644
--- a/src/content/translations/ml/upgrades/merge/index.md
+++ b/src/content/translations/ml/upgrades/merge/index.md
@@ -17,7 +17,7 @@ summaryPoint4: ഇത് സാങ്കേതിക റോഡ്മാപ്പ
## ഡോക്കിംഗ് എന്താണ്? {#what-is-the-docking}
-തുടക്കത്തിൽ, മറ്റ് Eth2 അപ്ഗ്രേഡുകൾ [ മെയിൻനെറ്റ് ](/glossary/#mainnet) ൽ നിന്ന് വെവ്വേറെ ഷിപ്പുചെയ്യുന്നുവെന്നത് ഓർത്തിരിക്കേണ്ടത് പ്രധാനമാണ് - ഇന്ന് നമ്മൾ ഉപയോഗിക്കുന്ന ശൃംഖല. [ബീക്കൺ ചെയിനും](/upgrades/beacon-chain/) അതിന്റെ [ഷാർഡ് ചെയിനുകളും](/upgrades/shard-chains/) സമാന്തരമായി [പ്രൂഫ് ഓഫ് സ്റ്റേക്ക് സിസ്റ്റത്തിൽ](/developers/docs/consensus-mechanisms/pos/) പ്രവർത്തിക്കുമ്പോൾ തന്നെ [പ്രൂഫ് ഓഫ് വർക്ക്](/developers/docs/consensus-mechanisms/pow/) ഉപയോഗിച്ച് Ethereum മെയിൻനെറ്റ് സമാന്തരമായി പ്രവർത്തിക്കും. ഈ രണ്ട് സിസ്റ്റങ്ങളും ഒന്നിച്ച് ലയിപ്പിക്കുന്നതാണ് ഡോക്കിംഗ്.
+തുടക്കത്തിൽ, മറ്റ് Eth2 അപ്ഗ്രേഡുകൾ [ മെയിൻനെറ്റ് ](/glossary/#mainnet) ൽ നിന്ന് വെവ്വേറെ ഷിപ്പുചെയ്യുന്നുവെന്നത് ഓർത്തിരിക്കേണ്ടത് പ്രധാനമാണ് - ഇന്ന് നമ്മൾ ഉപയോഗിക്കുന്ന ശൃംഖല. [ബീക്കൺ ചെയിനും](/upgrades/beacon-chain/) അതിന്റെ [ഷാർഡ് ചെയിനുകളും](/upgrades/sharding/) സമാന്തരമായി [പ്രൂഫ് ഓഫ് സ്റ്റേക്ക് സിസ്റ്റത്തിൽ](/developers/docs/consensus-mechanisms/pos/) പ്രവർത്തിക്കുമ്പോൾ തന്നെ [പ്രൂഫ് ഓഫ് വർക്ക്](/developers/docs/consensus-mechanisms/pow/) ഉപയോഗിച്ച് Ethereum മെയിൻനെറ്റ് സമാന്തരമായി പ്രവർത്തിക്കും. ഈ രണ്ട് സിസ്റ്റങ്ങളും ഒന്നിച്ച് ലയിപ്പിക്കുന്നതാണ് ഡോക്കിംഗ്.
ഒരു ഇന്റർസ്റ്റെല്ലാർ യാത്രയ്ക്ക് തികച്ചും തയ്യാറാകാത്ത ഒരു ബഹിരാകാശ കപ്പലാണ് Ethereum എന്ന് സങ്കൽപ്പിക്കുക. ബീക്കൺ ചെയിനും ഷാർഡ് ചെയിനുകളും ഉപയോഗിച്ച് കമ്മ്യൂണിറ്റി ഒരു പുതിയ എഞ്ചിനും കഠിനമാക്കിയ ഹലും നിർമ്മിച്ചു. സമയമാകുമ്പോൾ, ഒരൊറ്റ കപ്പൽ ആയി മാറാന് പാകത്തില് നിലവിലെ കപ്പൽ ഈ പുതിയ സിസ്റ്റത്തിൽ ഡോക്ക് ചെയ്യുന്നതിനാൽ, കുറച്ചധികം ലൈറ്റ്ഇയറുകൾ പിന്നിട്ട് പ്രപഞ്ചത്തെ വെല്ലുവിളിക്കാന് തയ്യാറാവും.
@@ -45,4 +45,4 @@ Eth2 അപ്ഗ്രേഡുകളെല്ലാം ഏതാണ്ട
മെയിൻനെറ്റ് ഒരു ഷാർഡായി മാറുന്നതോടെ, ഷാർഡ് ചെയിനുകൾ വിജയകരമായി നടപ്പിലാക്കുന്നത് ഈ നവീകരണത്തിന് നിർണ്ണായകമാണ്. ഷാർഡിംഗിലേക്ക് രണ്ടാമത്തെ നവീകരണം നടത്തണോ എന്ന് തീരുമാനിക്കാൻ കമ്മ്യൂണിറ്റിയെ സഹായിക്കുന്നതിൽ ഈ മാറ്റം ഒരു പ്രധാന പങ്ക് വഹിക്കാൻ സാധ്യതയുണ്ട്. ഈ അപ്ഗ്രേഡ് മറ്റ് ഷാർഡുകളെ മെയിൻനെറ്റ് പോലെയാക്കും: കൂടുതൽ ഡാറ്റ മാത്രമല്ല അവയ്ക്ക് ഇടപാടുകളും സ്മാർട്ട് കരാറുകളും കൈകാര്യം ചെയ്യാനും കഴിയും.
-ഷാർഡ് ചെയിനുകള്
+ഷാർഡ് ചെയിനുകള്
diff --git a/src/content/translations/ml/upgrades/shard-chains/index.md b/src/content/translations/ml/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/ml/upgrades/shard-chains/index.md
rename to src/content/translations/ml/upgrades/sharding/index.md
diff --git a/src/content/translations/nl/nft/index.md b/src/content/translations/nl/nft/index.md
index 3691c92ac31..4e22fcf0d1b 100644
--- a/src/content/translations/nl/nft/index.md
+++ b/src/content/translations/nl/nft/index.md
@@ -406,7 +406,7 @@ Geschat wordt dat upgrades voor schaalbaarheid het netwerk toestaan om tussen de
[Vitalik Buterin over het potentieel voor transacties per seconde met sharding](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Minimaal zal sharding 64 keer de hoeveelheid transacties van vandaag de dag toestaan, die momenteel op ongeveer 15 transacties staat. Dat is de hoeveelheid shardketens (extra gegevens en capaciteit) die wordt geïntroduceerd. [Meer over shardketens](/upgrades/shard-chains/)
+Minimaal zal sharding 64 keer de hoeveelheid transacties van vandaag de dag toestaan, die momenteel op ongeveer 15 transacties staat. Dat is de hoeveelheid shardketens (extra gegevens en capaciteit) die wordt geïntroduceerd. [Meer over shardketens](/upgrades/sharding/)
Dat betekent dat we kunnen inschatten hoelang het zal duren om 100.000 transacties te verwerken zodat we het kunnen vergelijken met het bovenstaande voorbeeld van Visa.
diff --git a/src/content/translations/nl/upgrades/beacon-chain/index.md b/src/content/translations/nl/upgrades/beacon-chain/index.md
index b34ae0dcfc1..98d1467b381 100644
--- a/src/content/translations/nl/upgrades/beacon-chain/index.md
+++ b/src/content/translations/nl/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: U kent dit wellicht als "Fase 0" op technische routekaarten.
## Wat doet de Beacon Chain? {#what-does-the-beacon-chain-do}
-De Beacon Chain zal het uitgebreide netwerk leiden of coördineren tussen [shards](/upgrades/shard-chains/) en [stakers](/staking/). Maar het zal niet zijn zoals het [Ethereum-hoofdnet](/glossary/#mainnet) dat we nu gebruiken. Het kan geen accounts of slimme contracten aan.
+De Beacon Chain zal het uitgebreide netwerk leiden of coördineren tussen [shards](/upgrades/sharding/) en [stakers](/staking/). Maar het zal niet zijn zoals het [Ethereum-hoofdnet](/glossary/#mainnet) dat we nu gebruiken. Het kan geen accounts of slimme contracten aan.
Het doel van de Beacon Chain zal in de loop van de tijd veranderen, maar het is een fundamenteel onderdeel voor [het veilige, duurzame en haalbare Ethereum waar we naartoe werken.](/upgrades/vision/).
@@ -33,7 +33,7 @@ Sstaken en een validator worden is makkelijker dan [mining](/developers/docs/min
Als u geïnteresseerd bent om een validator te worden en de Beacon Chain te beveiligen, hier vindt u meer informatie over staken.
-Dit is ook een belangrijke verandering voor een andere upgrade: [shardketens](/upgrades/shard-chains/).
+Dit is ook een belangrijke verandering voor een andere upgrade: [shardketens](/upgrades/sharding/).
### Opzetten van shardketens {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ In het begin zal de Beacon Chain apart bestaan van het Ethereum-hoofdnet dat we
Shardketens kunnen alleen op een veilige manier in het Ethereum-netwerk komen als er een proof-of-stake consensusmechanisme geïmplementeerd is. De Beacon Chain zal het staken introduceren en de weg vrijmaken voor de upgrade van de shardketen die zal volgen.
-
+
Shardketens
diff --git a/src/content/translations/nl/upgrades/merge/index.md b/src/content/translations/nl/upgrades/merge/index.md
index 3f2af5a5895..9ecded259c5 100644
--- a/src/content/translations/nl/upgrades/merge/index.md
+++ b/src/content/translations/nl/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Oorspronkelijk was het plan om aan shardketens te werken voor de merge, om de sc
Dit zal een voortdurende beoordeling zijn van de gemeenschap over de noodzaak van mogelijk meerdere rondes van shardketens om eindeloze schaalbaarheid mogelijk te maken.
-
+
Shardketens
diff --git a/src/content/translations/nl/upgrades/shard-chains/index.md b/src/content/translations/nl/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/nl/upgrades/shard-chains/index.md
rename to src/content/translations/nl/upgrades/sharding/index.md
diff --git a/src/content/translations/pl/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/pl/developers/docs/consensus-mechanisms/pos/index.md
index f1657256a94..5ef6e9f999e 100644
--- a/src/content/translations/pl/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/pl/developers/docs/consensus-mechanisms/pos/index.md
@@ -37,7 +37,7 @@ Jeżeli poświadczasz szkodliwe bloki, tracisz zastaw.
### Łańcuch śledzący {#the-beacon-chain}
-Gdy Ethereum zastąpi proof-of-work przez proof-of-stake, zostanie dodana złożoność [łańcuchów odłamkowych](/upgrades/shard-chains/). Są to oddzielne blockchainy, które będą potrzebowały walidatorów do przetwarzania transakcji i tworzenia nowych bloków. Planowane są 64 łańcuchy odłamkowe, a wszystkie one wymagają współdzielonego porozumienia w kwestii stanu sieci. Potrzebna jest więc dodatkowa koordynacja, która zostanie zrealizowana z użyciem [łańcucha nawigacyjnego](/upgrades/beacon-chain/).
+Gdy Ethereum zastąpi proof-of-work przez proof-of-stake, zostanie dodana złożoność [łańcuchów odłamkowych](/upgrades/sharding/). Są to oddzielne blockchainy, które będą potrzebowały walidatorów do przetwarzania transakcji i tworzenia nowych bloków. Planowane są 64 łańcuchy odłamkowe, a wszystkie one wymagają współdzielonego porozumienia w kwestii stanu sieci. Potrzebna jest więc dodatkowa koordynacja, która zostanie zrealizowana z użyciem [łańcucha nawigacyjnego](/upgrades/beacon-chain/).
Łańcuch śledzący odbiera informację o stanie z odłamków (fragmentów) i udostępnia ją innym odłamkom, aby sieć mogła pozostać zsynchronizowana. Łańcuch śledzący zarządza również walidatorami, od rejestrowania ich depozytów zastawnych po wydawanie im nagród i kar.
diff --git a/src/content/translations/pl/developers/docs/scaling/index.md b/src/content/translations/pl/developers/docs/scaling/index.md
index 9e7231c298d..422639581ab 100644
--- a/src/content/translations/pl/developers/docs/scaling/index.md
+++ b/src/content/translations/pl/developers/docs/scaling/index.md
@@ -27,7 +27,7 @@ Ta metoda skalowania wymaga zmian w protokole Ethereum ([sieć główna](/glossa
Sharding jest procesem poziomego dzielenia bazy danych w celu rozłożenia obciążenia. W kontekście Ethereum sharding zmniejszy zatłoczenie sieci i zwiększy liczbę transakcji na sekundę dzięki tworzeniu nowych łańcuchów — „odłamków”. Odciąży to również każdego walidatora, który nie będzie już musiał przetwarzać wszystkich transakcji w całej sieci.
-Dowiedz się więcej o shardingu.
+Dowiedz się więcej o shardingu.
## Skalowanie off-chain {#off-chain-scaling}
diff --git a/src/content/translations/pl/upgrades/beacon-chain/index.md b/src/content/translations/pl/upgrades/beacon-chain/index.md
index 98969da9602..8754aa8a912 100644
--- a/src/content/translations/pl/upgrades/beacon-chain/index.md
+++ b/src/content/translations/pl/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Być może znasz to jako "etap 0" w hamonogramie technicznym
## Co robi łańcuch śledzący? {#what-does-the-beacon-chain-do}
-Łańcuch śledzący będzie prowadził lub koordynował rozszerzoną sieć [fragmentów](/upgrades/shard-chains/) i [zastawiających](/staking/). Ale nie będzie jak sieć główna [Ethereum](/glossary/#mainnet) dzisiaj. Nie może on obsługiwać kont ani inteligentnych kontraktów.
+Łańcuch śledzący będzie prowadził lub koordynował rozszerzoną sieć [fragmentów](/upgrades/sharding/) i [zastawiających](/staking/). Ale nie będzie jak sieć główna [Ethereum](/glossary/#mainnet) dzisiaj. Nie może on obsługiwać kont ani inteligentnych kontraktów.
Rola łańcucha śledzącego z czasem się zmieni, ale jest to podstawowy komponent [bezpiecznego, zrównoważonego i skalowalnego Ethereum, nad którym pracujemy](/upgrades/vision/).
@@ -33,7 +33,7 @@ Zastawianie i stawanie się walidatorem jest łatwiejsze niż [wydobywanie](/dev
Jeżeli jesteś zainteresowany staniem się walidatorem i pomocą w zabezpieczaniu łańcucha śledzącego, dowiedz się więcej o zastawianiu.
-Jest to również ważna zmiana w stosunku do drugiej aktualizacji Eth2: [łańcuchów szczątkowych](/upgrades/shard-chains/).
+Jest to również ważna zmiana w stosunku do drugiej aktualizacji Eth2: [łańcuchów szczątkowych](/upgrades/sharding/).
### Ustawianie łańcuchów szczątkowych {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ Wszystkie ulepszenia Eth2 są poniekąd wzajemnie powiązane. Więc podsumujmy,
Łańcuch śledzący będzie początkowo odrębny od głównej sieci Ethereum, której używamy dziś. Jednak ostatecznie zostaną one połączone.
-Dokowanie
+Dokowanie
diff --git a/src/content/translations/pl/upgrades/merge/index.md b/src/content/translations/pl/upgrades/merge/index.md
index 15ba381773f..0d3daa97d87 100644
--- a/src/content/translations/pl/upgrades/merge/index.md
+++ b/src/content/translations/pl/upgrades/merge/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Być może znasz ten etap jako „Faza 1.5” z technicznego harm
## Czym jest dokowanie? {#what-is-the-docking}
-Ważne jest, by pamiętać, że początkowo inne ulepszenia Eth2 zostaną przetransportowane oddzielnie z [sieci głównej](/glossary/#mainnet) — sieci, której używamy dzisiaj. Sieć główna Ethereum będzie nadal zabezpieczona za pomocą [proof-of-work](/developers/docs/consensus-mechanisms/pow/), nawet gdy [łańcuch śledzący](/upgrades/beacon-chain/) i jego [łańcuch odłamków](/upgrades/shard-chains/) działają równolegle przy użyciu [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). Dokowanie jest łączeniem tych dwóch systemów.
+Ważne jest, by pamiętać, że początkowo inne ulepszenia Eth2 zostaną przetransportowane oddzielnie z [sieci głównej](/glossary/#mainnet) — sieci, której używamy dzisiaj. Sieć główna Ethereum będzie nadal zabezpieczona za pomocą [proof-of-work](/developers/docs/consensus-mechanisms/pow/), nawet gdy [łańcuch śledzący](/upgrades/beacon-chain/) i jego [łańcuch odłamków](/upgrades/sharding/) działają równolegle przy użyciu [proof-of-stake](/developers/docs/consensus-mechanisms/pos/). Dokowanie jest łączeniem tych dwóch systemów.
Wyobraź sobie że Ethereum jest statkiem kosmicznym, który nie jest gotowy na międzygalaktyczną podróż. Dzięki łańcuchowi śledzącemu i łańcuchom odłamkowym społeczność zbuduje nowy silnik i utwardzony kadłub. Kiedy przyjdzie czas, statek zostanie zadokowany z tymi nowymi systemami, więc będzie mógł być jedną całością, gotową do podróży na odległość wielu lat świetlnych i odkrywania wszechświata.
@@ -45,4 +45,4 @@ Kiedy nastąpi dokowanie, stakerzy zostaną przydzieleni do walidacji sieci gł
W momencie, gdy sieć główna staje się odłamkiem, udana implementacja łańcuchów odłamkowych jest kluczowa dla tej aktualizacji. Najprawdopodobniej ta sytuacja odegra kluczową rolę w pomaganiu społeczności w decydowaniu o dalszym rozwoju drugiego ulepszenia shardingu. To ulepszenie sprawi że pojawią się inne odłamki podobne do sieci głównej: będą gotowe do obsługi transakcji, inteligentnych kontraktów, a nie tylko dostarczania większej ilości danych.
-Łańcuchy odłamkowe
+Łańcuchy odłamkowe
diff --git a/src/content/translations/pl/upgrades/shard-chains/index.md b/src/content/translations/pl/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/pl/upgrades/shard-chains/index.md
rename to src/content/translations/pl/upgrades/sharding/index.md
diff --git a/src/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/index.md
index 2e013fe5d09..49d86d7fd7d 100644
--- a/src/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ A prova de participação vem com várias melhorias referente ao sistema de prov
- melhor eficiência energética: você não precisa usar muita energia minerando blocos
- menores barreiras à entrada, redução dos requisitos de hardware — você não precisa de um hardware potente para ter a chance de criar novos blocos
- maior imunidade à centralização: a prova de participação deve gerar mais nós na rede
-- suporte mais forte para as [cadeias de fragmentos](/upgrades/shard-chains/) – uma atualização chave para dimensionamento da rede Ethereum
+- suporte mais forte para as [cadeias de fragmentos](/upgrades/sharding/) – uma atualização chave para dimensionamento da rede Ethereum
## Prova de participação, participação (staking) e validadores {#pos-staking-validators}
@@ -37,7 +37,7 @@ Se você atesta/certifica blocos maliciosos, perde sua participação (stake).
### A Beacon Chain {#the-beacon-chain}
-Quando o Ethereum substituir a prova de trabalho para a prova de participação, existirá uma complexidade adicional devido às [cadeias de fragmentos](/upgrades/shard-chains/). Estas são blockchains separadas que vão precisar de validadores para processar transações e criar novos blocos. O plano é ter 64 cadeias de fragmentos e todas elas precisam de uma compreensão compartilhada do estado da rede. Como resultado, uma coordenação extra é necessária, e será feita pela chamada cadeia de referência ou [Beacon Chain](/upgrades/beacon-chain/).
+Quando o Ethereum substituir a prova de trabalho para a prova de participação, existirá uma complexidade adicional devido às [cadeias de fragmentos](/upgrades/sharding/). Estas são blockchains separadas que vão precisar de validadores para processar transações e criar novos blocos. O plano é ter 64 cadeias de fragmentos e todas elas precisam de uma compreensão compartilhada do estado da rede. Como resultado, uma coordenação extra é necessária, e será feita pela chamada cadeia de referência ou [Beacon Chain](/upgrades/beacon-chain/).
A Beacon Chain recebe informações de estado de fragmentos (shards) e as disponibiliza para outros fragmentos para que a rede possa permanecer em sincronia. A Beacon Chain também gerenciará os validadores, do registro de depósito de suas participações (stakes) até a emissão de suas recompensas e penalidades.
diff --git a/src/content/translations/pt-br/nft/index.md b/src/content/translations/pt-br/nft/index.md
index 7979f07d2e4..345dc7172da 100644
--- a/src/content/translations/pt-br/nft/index.md
+++ b/src/content/translations/pt-br/nft/index.md
@@ -406,7 +406,7 @@ Estima-se que a melhoria de dimensionamento permitirá que a rede processe entre
[Vitalik Buterin sobre transações potenciais por segundo com a fragmentação](https://twitter.com/VitalikButerin/status/1312905884549300224)
-No mínimo, a fragmentação permitirá 64 vezes mais transações, que hoje está em torno de 15 transações. Essa é a quantidade de cadeias de fragmentos (dados extras e capacidade) sendo introduzida. [Mais sobre cadeias de fragmentação](/upgrades/shard-chains/)
+No mínimo, a fragmentação permitirá 64 vezes mais transações, que hoje está em torno de 15 transações. Essa é a quantidade de cadeias de fragmentos (dados extras e capacidade) sendo introduzida. [Mais sobre cadeias de fragmentação](/upgrades/sharding/)
Isso significa que podemos estimar quanto tempo levará para processar 100.000 transações, para que possamos comparar com o exemplo da Visa acima.
diff --git a/src/content/translations/pt-br/upgrades/beacon-chain/index.md b/src/content/translations/pt-br/upgrades/beacon-chain/index.md
index c3e9907710d..9262178770c 100644
--- a/src/content/translations/pt-br/upgrades/beacon-chain/index.md
+++ b/src/content/translations/pt-br/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Talvez você tenha visto isso sendo mencionado como "Fase 0" nos
## O que a Beacon Chain faz? {#what-does-the-beacon-chain-do}
-A Beacon Chain conduzirá ou coordenará a rede estendida de [shards](/upgrades/shard-chains/) ("fragmentos") e [stakers](/staking/) ("participantes"). Mas não será como a [rede principal da Ethereum](/glossary/#mainnet) de hoje. Ela não será capaz de gerenciar contas ou contratos inteligentes.
+A Beacon Chain conduzirá ou coordenará a rede estendida de [shards](/upgrades/sharding/) ("fragmentos") e [stakers](/staking/) ("participantes"). Mas não será como a [rede principal da Ethereum](/glossary/#mainnet) de hoje. Ela não será capaz de gerenciar contas ou contratos inteligentes.
O papel da Beacon Chain mudará com o tempo, mas é um componente fundamental para [o Ethereum seguro, sustentável e dimensionável rumo ao qual estamos trabalhando](/upgrades/vision/).
@@ -33,7 +33,7 @@ Participar e se tornar um validador é mais fácil do que [minerar](/developers/
Se você estiver interessado em se tornar um validador e ajudar a manter a Beacon Chain segura, veja mais informações sobre como participar.
-Essa também é uma mudança importante para outra melhoria do Ethereum: [as cadeias de fragmentos (shard chains)](/upgrades/shard-chains/).
+Essa também é uma mudança importante para outra melhoria do Ethereum: [as cadeias de fragmentos (shard chains)](/upgrades/sharding/).
### Preparação para as cadeias de fragmentos {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ A Beacon Chain existirá, a princípio, separada da rede principal Ethereum que
As cadeias de fragmentos (shard chains) somente podem ser introduzidas ao ecossistema Ethereum com um mecanismo de consenso de prova de participação em vigor. A Beacon Chain introduzirá a participação (staking), preparando assim o caminho para a implementação das cadeias de fragmentos na próxima atualização.
-
+
Cadeias de fragmentos
diff --git a/src/content/translations/pt-br/upgrades/merge/index.md b/src/content/translations/pt-br/upgrades/merge/index.md
index c9d50532b3c..788000b1329 100644
--- a/src/content/translations/pt-br/upgrades/merge/index.md
+++ b/src/content/translations/pt-br/upgrades/merge/index.md
@@ -59,7 +59,7 @@ No início, o plano era trabalhar em cadeias de fragmentos antes da fusão – p
Essa será uma avaliação contínua da comunidade quanto à necessidade de rodadas potencialmente múltiplas de cadeias de fragmentos para permitir dimensionamento sem limites.
-
+
Cadeias de fragmentos
diff --git a/src/content/translations/pt-br/upgrades/shard-chains/index.md b/src/content/translations/pt-br/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/pt-br/upgrades/shard-chains/index.md
rename to src/content/translations/pt-br/upgrades/sharding/index.md
diff --git a/src/content/translations/ro/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/ro/developers/docs/consensus-mechanisms/pos/index.md
index b71a78fd2be..3174bbae1d0 100644
--- a/src/content/translations/ro/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/ro/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ Dovada-mizei aduce o serie de îmbunătățiri ale sistemului dovezii-muncii:
- eficiență energetică mai bună – nu trebuie utilizată multă energie pentru minarea blocurilor
- bariere mai mici la intrare, cerințe hardware reduse – nu aveți nevoie de hardware super performant pentru a avea o șansă de a crea blocuri noi
- imunitate mai puternică la centralizare – dovada-mizei ar trebui să conducă la mai multe noduri în rețea
-- o compatibilitate mai mare pentru [lanțurile de fragmente](/upgrades/shard-chains/) – o actualizare esențială în scalarea rețelei Ethereum
+- o compatibilitate mai mare pentru [lanțurile de fragmente](/upgrades/sharding/) – o actualizare esențială în scalarea rețelei Ethereum
## Dovada-mizei, mizarea și validatorii {#pos-staking-validators}
@@ -37,7 +37,7 @@ Dacă atestați blocuri rău intenționate, veți pierde miza.
### Lanțul Beacon {#the-beacon-chain}
-Când Ethereum va înlocui dovada-muncii (PoW) cu dovada-mizei (PoS), se va adăuga o complexitate numită [lanțuri de fragmente](/upgrades/shard-chains/). Acestea sunt blockchain-uri separate care vor avea nevoie de validatori pentru a procesa tranzacțiile și a crea noi blocuri. Se prevede să avem 64 de lanțuri de fragmente și toate au nevoie de o înțelegere comună a stării rețelei. Din acest motiv este necesară o coordonare suplimentară și va fi realizată de [lanțul beacon](/upgrades/beacon-chain/).
+Când Ethereum va înlocui dovada-muncii (PoW) cu dovada-mizei (PoS), se va adăuga o complexitate numită [lanțuri de fragmente](/upgrades/sharding/). Acestea sunt blockchain-uri separate care vor avea nevoie de validatori pentru a procesa tranzacțiile și a crea noi blocuri. Se prevede să avem 64 de lanțuri de fragmente și toate au nevoie de o înțelegere comună a stării rețelei. Din acest motiv este necesară o coordonare suplimentară și va fi realizată de [lanțul beacon](/upgrades/beacon-chain/).
Lanțul beacon primește informații de stare de la fragmente și le face disponibile altor fragmente, astfel încât rețeaua să poată rămâne sincronizată. Lanțul beacon va gestiona și validatorii, de la înregistrarea depozitelor de miză ale acestora până la emiterea recompenselor și a penalităților.
diff --git a/src/content/translations/ro/developers/docs/scaling/index.md b/src/content/translations/ro/developers/docs/scaling/index.md
index 7365e937fe9..86f75243708 100644
--- a/src/content/translations/ro/developers/docs/scaling/index.md
+++ b/src/content/translations/ro/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ Această metodă de scalare necesită modificări ale protocolului Ethereum (niv
Fragmentarea este procesul de divizare orizontală a unei baze de date pentru a distribui sarcina. În contextul Ethereum, fragmentarea va reduce congestionarea rețelei și va crește numărul de tranzacții pe secundă prin crearea de noi lanțuri, cunoscute sub numele de „fragmente.” Acest lucru va ușura de asemenea sarcina fiecărui validator, care nu va mai fi nevoit să proceseze integral toate tranzacțiile din întreaga rețea.
-Aflați mai multe despre [fragmentare](/upgrades/shard-chains/).
+Aflați mai multe despre [fragmentare](/upgrades/sharding/).
## Scalarea off-chain {#off-chain-scaling}
diff --git a/src/content/translations/ro/nft/index.md b/src/content/translations/ro/nft/index.md
index ccab24c77f4..4d84537c057 100644
--- a/src/content/translations/ro/nft/index.md
+++ b/src/content/translations/ro/nft/index.md
@@ -406,7 +406,7 @@ Se estimează că actualizările de scalabilitate vor permite rețelei să proce
[Vitalik Buterin despre potențialul tranzacțiilor pe secundă cu sistemul de fragmentare](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Fragmentarea va permite cel puțin un număr de tranzacții de 64 de ori mai mare decât numărul actual, care este de aproximativ 15 tranzacții. Este cantitatea de lanțuri de fragmente (date și capacitate în plus) care va fi introdusă. [Mai multe informații despre lanțurile de fragmente](/upgrades/shard-chains/)
+Fragmentarea va permite cel puțin un număr de tranzacții de 64 de ori mai mare decât numărul actual, care este de aproximativ 15 tranzacții. Este cantitatea de lanțuri de fragmente (date și capacitate în plus) care va fi introdusă. [Mai multe informații despre lanțurile de fragmente](/upgrades/sharding/)
Asta înseamnă că putem estima cât timp va dura procesarea a 100.000 de tranzacții, astfel încât să putem compara cu exemplul Visa de mai sus.
diff --git a/src/content/translations/ro/upgrades/beacon-chain/index.md b/src/content/translations/ro/upgrades/beacon-chain/index.md
index 8b09c0f18c3..1f1ffeec5b0 100644
--- a/src/content/translations/ro/upgrades/beacon-chain/index.md
+++ b/src/content/translations/ro/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: S-ar putea să-l cunoști sub numele de „Faza 0” pe foile de
## Ce face Lanțul Beacon? {#what-does-the-beacon-chain-do}
-Lanțul Beacon va conduce sau va coordona rețeaua extinsă de [fragmente](/upgrades/shard-chains/) și [stakeri](/staking/). Dar nu va fi ca [Rețeaua principală Ethereum](/glossary/#mainnet) de astăzi. Nu poate gestiona conturi sau contracte inteligente.
+Lanțul Beacon va conduce sau va coordona rețeaua extinsă de [fragmente](/upgrades/sharding/) și [stakeri](/staking/). Dar nu va fi ca [Rețeaua principală Ethereum](/glossary/#mainnet) de astăzi. Nu poate gestiona conturi sau contracte inteligente.
Rolul rețelei Beacon se va schimba în timp, dar este o componentă fundamentală pentru [Ethereum-ul sigur, durabil și scalabil la care lucrăm](/upgrades/vision/).
@@ -33,7 +33,7 @@ Mizarea și transformarea în validator este mai ușoară decât [minatul](/deve
Dacă dorești să devii validator și să ajuți la securizarea rețelei Beacon, află mai multe despre mizare.
-Aceasta este o altă schimbare importantă pentru următorul upgrade Eth2: [lanțurile de fragmente](/upgrades/shard-chains/).
+Aceasta este o altă schimbare importantă pentru următorul upgrade Eth2: [lanțurile de fragmente](/upgrades/sharding/).
### Configurarea lanțurilor de fragmente {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ La început, Rețeaua Beacon va exista separat de Rețeaua principală Ethereum
Lanțurile de fragmente nu pot intra în siguranță în ecosistemul Ethereum decât cu un mecanism de consens bazat pe Dovada de Minare(proof-of-stake). Rețeaua Beacon va introduce mizarea, pregătind astfel terenul pentru ca actualizarea lanțului de fragmente să aibă loc.
-Lanțuri de fragmente
+Lanțuri de fragmente
diff --git a/src/content/translations/ro/upgrades/merge/index.md b/src/content/translations/ro/upgrades/merge/index.md
index 74085beccd1..eb69a6549b6 100644
--- a/src/content/translations/ro/upgrades/merge/index.md
+++ b/src/content/translations/ro/upgrades/merge/index.md
@@ -57,4 +57,4 @@ Inițial, planul era ca lanțurile de fragmente să fie folosite înainte de uni
Acest lucru va fi evaluat în continuu de către comunitate în ceea ce privește necesitatea unor potențiale runde multiple de lanțuri de fragmente pentru a permite o scalabilitate infinită.
-Lanțuri de fragmente
+Lanțuri de fragmente
diff --git a/src/content/translations/ro/upgrades/shard-chains/index.md b/src/content/translations/ro/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/ro/upgrades/shard-chains/index.md
rename to src/content/translations/ro/upgrades/sharding/index.md
diff --git a/src/content/translations/ru/nft/index.md b/src/content/translations/ru/nft/index.md
index 048c7575fbf..e7ed18f401a 100644
--- a/src/content/translations/ru/nft/index.md
+++ b/src/content/translations/ru/nft/index.md
@@ -406,7 +406,7 @@ _Также важно помнить, что Ethereum делает больше
[Виталик Бутерин о потенциале транзакций в секунду при использовании шардинга](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Как минимум, шардинг позволит в 64 раза увеличить количество транзакций по сравнению с сегодняшним уровнем, который составляет около 15 транзакций. Это количество вводимых цепочек-осколков (дополнительные данные и емкость). [Подробнее о цепочках-осколках](/upgrades/shard-chains/)
+Как минимум, шардинг позволит в 64 раза увеличить количество транзакций по сравнению с сегодняшним уровнем, который составляет около 15 транзакций. Это количество вводимых цепочек-осколков (дополнительные данные и емкость). [Подробнее о цепочках-осколках](/upgrades/sharding/)
Это означает, что мы можем оценить, сколько времени потребуется для обработки 100 000 транзакций, чтобы сравнить это с примером Visa выше.
diff --git a/src/content/translations/ru/upgrades/beacon-chain/index.md b/src/content/translations/ru/upgrades/beacon-chain/index.md
index 55073dfa14e..cac911207e9 100644
--- a/src/content/translations/ru/upgrades/beacon-chain/index.md
+++ b/src/content/translations/ru/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: В технических дорожных картах вы мо
## Что делает Beacon Chain? {#what-does-the-beacon-chain-do}
-Beacon Chain будет осуществлять или координировать расширенную сеть [осколков](/upgrades/shard-chains/) и [стейкеров](/staking/). Но это не будет похоже на сегодняшнюю [основную сеть Ethereum](/glossary/#mainnet). Она не может работать с аккаунтами или смарт-контрактами.
+Beacon Chain будет осуществлять или координировать расширенную сеть [осколков](/upgrades/sharding/) и [стейкеров](/staking/). Но это не будет похоже на сегодняшнюю [основную сеть Ethereum](/glossary/#mainnet). Она не может работать с аккаунтами или смарт-контрактами.
Роль Beacon Chain со временем изменится, но это основополагающий компонент для [безопасного, устойчивого и масштабируемого Ethereum, над которым мы работаем](/upgrades/vision/).
@@ -33,7 +33,7 @@ Beacon Chain вводит [доказательство владения](/devel
Если вы хотите стать валидатором и принять участие в защите Beacon Chain, узнайте больше о стейкинге.
-Это также важное изменение для другого обновления: [цепочек осколков](/upgrades/shard-chains/).
+Это также важное изменение для другого обновления: [цепочек осколков](/upgrades/sharding/).
### Настройка цепей-осколков {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ Beacon Chain вводит [доказательство владения](/devel
Цепочки-осколки способны только на безопасный вход в экосистему Ethereum с механизмом консенсуса на основе доказательства владения. Beacon Chain вводит ставки, прокладывая путь к последующему обновлению с цепочками-осколками.
-
+
Цепочки-осколки
diff --git a/src/content/translations/ru/upgrades/merge/index.md b/src/content/translations/ru/upgrades/merge/index.md
index cb94a283ba5..5d6f8684898 100644
--- a/src/content/translations/ru/upgrades/merge/index.md
+++ b/src/content/translations/ru/upgrades/merge/index.md
@@ -59,7 +59,7 @@ summaryPoint4: Раньше мы называли это «стыковкой».
Это будет постоянная оценка сообщества относительно необходимости потенциально нескольких раундов цепочек осколков, чтобы обеспечить бесконечную масштабируемость.
-
+
Цепочки-осколки
diff --git a/src/content/translations/ru/upgrades/shard-chains/index.md b/src/content/translations/ru/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/ru/upgrades/shard-chains/index.md
rename to src/content/translations/ru/upgrades/sharding/index.md
diff --git a/src/content/translations/sl/nft/index.md b/src/content/translations/sl/nft/index.md
index dc849e44f45..82673490a0d 100644
--- a/src/content/translations/sl/nft/index.md
+++ b/src/content/translations/sl/nft/index.md
@@ -400,7 +400,7 @@ Ocenjuje se, da bo Eth2 omrežju omogočal, da bo procesiralo med 25.000 in 100.
[Vitalik Buterin o potencialu transakcij na sekundo na Eth2](https://twitter.com/VitalikButerin/status/1312905884549300224?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1312905886327664640%7Ctwgr%5E%7Ctwcon%5Es2_&ref_url=https%3A%2F%2Fwww.coinspeaker.com%2Fvitalik-buterin-ethereum-layer-2%2F)
-Eth2 bo omogočal vsaj 64-krat večjo količino transakcij kot danes, ko ta številka stoji okoli 15 transakcij. To je število razdrobljenih verig (dodatnih podatkov in kapacitet), ki se jih uvaja. [Več o razdrobljenih verigah](/upgrades/shard-chains/)
+Eth2 bo omogočal vsaj 64-krat večjo količino transakcij kot danes, ko ta številka stoji okoli 15 transakcij. To je število razdrobljenih verig (dodatnih podatkov in kapacitet), ki se jih uvaja. [Več o razdrobljenih verigah](/upgrades/sharding/)
To pomeni, da lahko ocenimo, kako dolgo bo trajalo, da se obdela 100.000 transakcij in tako to primerjamo z zgornjim primerom Vise.
diff --git a/src/content/translations/sl/upgrades/beacon-chain/index.md b/src/content/translations/sl/upgrades/beacon-chain/index.md
index ad6263605c1..87ad08aaebe 100644
--- a/src/content/translations/sl/upgrades/beacon-chain/index.md
+++ b/src/content/translations/sl/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Oddajniško verigo morda poznate pod imenom "faza 0", ki se upora
## Kakšen je namen oddajniške verige? {#what-does-the-beacon-chain-do}
-Oddajniška veriga bo izvajala in usklajevala razširjeno omrežje [drobcev](/upgrades/shard-chains/) in [zastavljavcev](/staking/). Vendar ne bo enaka kot [glavno Ethereum omrežje](/glossary/#mainnet) danes. Ne more obdelovati računov ali pametnih pogodb.
+Oddajniška veriga bo izvajala in usklajevala razširjeno omrežje [drobcev](/upgrades/sharding/) in [zastavljavcev](/staking/). Vendar ne bo enaka kot [glavno Ethereum omrežje](/glossary/#mainnet) danes. Ne more obdelovati računov ali pametnih pogodb.
Vloga oddajniške verige se bo sčasoma spremenila, vendar je temeljni sestavni del [varnega, trajnostnega in nadgradljivega Ethereuma, ki ga želimo razviti](/upgrades/vision/).
@@ -33,7 +33,7 @@ Zastavljanje in delovanje kot validator sta lažja kot [rudarjenje](/developers/
Če vas zanima, da bi postali validator in pomagali zaščititi oddajniško verigo, preberite več o zastavljanju.
-To je prav tako pomembna sprememba za drugo Eth2 nadgradnjo: [razdrobljene verige](/upgrades/shard-chains/).
+To je prav tako pomembna sprememba za drugo Eth2 nadgradnjo: [razdrobljene verige](/upgrades/sharding/).
### Priprava na razdrobljene verige {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ Oddajniška veriga bo sprva obstajala ločeno od glavnega omrežja, ki ga uporab
Razdrobljene verige lahko v ekosistem Ethereum varno vstopijo samo, ko je vključen mehanizem za doseganje soglasja z dokazom o deležu. Oddajniška veriga bo uvedla zastavljanje in tlakovala pot za nadgradnjo razdrobljenih verig, ki prihaja.
-Razdrobljene verige
+Razdrobljene verige
diff --git a/src/content/translations/sl/upgrades/merge/index.md b/src/content/translations/sl/upgrades/merge/index.md
index a8bdde1738f..5f469b41b62 100644
--- a/src/content/translations/sl/upgrades/merge/index.md
+++ b/src/content/translations/sl/upgrades/merge/index.md
@@ -57,4 +57,4 @@ Začetni načrt je delo na razdrobljenih verigah predvideval pred spojitvijo –
Skupnost bo sprotno ocenjevala potencialno potrebo po več krogih razdrobljenih verig, da bi lahko omogočili neskončno nadgradljivost.
-Razdrobljene verige
+Razdrobljene verige
diff --git a/src/content/translations/sl/upgrades/shard-chains/index.md b/src/content/translations/sl/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/sl/upgrades/shard-chains/index.md
rename to src/content/translations/sl/upgrades/sharding/index.md
diff --git a/src/content/translations/sw/upgrades/beacon-chain/index.md b/src/content/translations/sw/upgrades/beacon-chain/index.md
index 5e19bfe212a..da491d286fa 100644
--- a/src/content/translations/sw/upgrades/beacon-chain/index.md
+++ b/src/content/translations/sw/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Unaweza kua unaitambua hii kama "Awamu 0" kwenye mipango ya kitaa
## Myororo wa Kioleza ni nini? {#what-does-the-beacon-chain-do}
-Mnyororo wa Beacon utaendeleza mwenendo wa kutanua mtandao wake wa [shards](/upgrades/shard-chains/) na [wanahisa](/staking/). Lakini haitakua kama [mtandao mkuu wa Ethereum](/glossary/#mainnet) wa leo. Inaweza kuhimili akaunti au mikataba mahiri.
+Mnyororo wa Beacon utaendeleza mwenendo wa kutanua mtandao wake wa [shards](/upgrades/sharding/) na [wanahisa](/staking/). Lakini haitakua kama [mtandao mkuu wa Ethereum](/glossary/#mainnet) wa leo. Inaweza kuhimili akaunti au mikataba mahiri.
Jukumu ya mnyororo wa Kioleza litabadilika baada ya mda ila sehemu ya msingi ya [usalama, kuendeleza na ubadilikaji wa Ethereum tunayoijenga](/upgrades/vision/).
@@ -33,7 +33,7 @@ Kuweka hisa na kua mt hibitishaji ni rahisi kuliko [kuchimba](/developers/docs/m
Kama ungependa kua mthibitishaji na kusaidia kulinda mnyororo wa Kioleza, jifunze zaidi jinsi ya kuweka hisa.
-Hili pia ni badiliko muhumu kwa ajili ya uboreshaji wa Eth2:[minyororo ya vigae](/upgrades/shard-chains/).
+Hili pia ni badiliko muhumu kwa ajili ya uboreshaji wa Eth2:[minyororo ya vigae](/upgrades/sharding/).
### Maandalizi ya minyororo ya shards {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ Mnyororo Kioleza, mwanzoni, itakuwa imetengana na Mtandao mkuu wa Ethereum tunao
Minyororo ya Vigae itakua salama kuingia katika ikolojia ya Ethereum pale tu utaratibu wa makubaliano kwenye uthibitisho-wa-hisa utakapochukua nafasi. Mnyororo Kioleza utaanzisha hisa, ikitengeneza njia ili uboreshwaji wa mnyororo-kigae ufuate.
-
+
Minyororo ya Kigae
diff --git a/src/content/translations/sw/upgrades/merge/index.md b/src/content/translations/sw/upgrades/merge/index.md
index b189f270d6c..a8f7e8ccda7 100644
--- a/src/content/translations/sw/upgrades/merge/index.md
+++ b/src/content/translations/sw/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Hapo awali, mpango huo ulikuwa ukifanya kazi kwenye minyororo iliyokatwa kabla y
Hii itakuwa tathmini inayoendelea kutoka kwa jamii juu ya hitaji la raundi nyingi za vipande vya minyororo ili kuruhusu uendelevu usio na mwisho.
-
+
Vipande vya minyororo
diff --git a/src/content/translations/sw/upgrades/shard-chains/index.md b/src/content/translations/sw/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/sw/upgrades/shard-chains/index.md
rename to src/content/translations/sw/upgrades/sharding/index.md
diff --git a/src/content/translations/tr/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/tr/developers/docs/consensus-mechanisms/pos/index.md
index 108aabdf24a..298ef6f1c8b 100644
--- a/src/content/translations/tr/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/tr/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ Hisse ispatı, bir dizi iyileştirme ile iş ispatının (PoW) yerini alacak:
- daha iyi enerji verimliliği - blok madenciliği için yüksek enerji kullanmanıza gerek yok
- daha düşük giriş bedeli ve donanım gereksinimleri - yeni bloklar oluşturma kabiliyeti için elit donanıma ihtiyacınız yok
- merkezileştirmeye karşı daha güçlü bağışıklık - hisse ispatı ağdaki düğüm sayısını artıracaktır
-- [parça zincirleri](/upgrades/shard-chains/) için daha güçlü destek - Ethereum ağını ölçeklendirme için önemli bir yükseltme
+- [parça zincirleri](/upgrades/sharding/) için daha güçlü destek - Ethereum ağını ölçeklendirme için önemli bir yükseltme
## Hisse ispatı, stake etme ve doğrulayıcılar {#pos-staking-validators}
@@ -37,7 +37,7 @@ Kötü niyetli blokları tasdiklerseniz, stake ettiğiniz miktarı kaybedersiniz
### İşaret zinciri {#the-beacon-chain}
-Ethereum, iş ispatını hisse ispatı ile değiştirdiğinde, [parça zincirlerinin (shard chain)](/upgrades/shard-chains/) karmaşıklığı artacaktır. Bunlar, işlemleri gerçekleştirmek ve yeni bloklar oluşturmak için doğrulayıcılara ihtiyaç duyacak ayrı blok zincirleridir. 64 parça zincirinin bulunması ve hepsinin ağın durumu hakkında ortak bir anlayışa sahip olması planlanır. Sonuç olarak, ekstra koordinasyon gereklidir ve bu koordinasyon [işaret zinciri](/upgrades/beacon-chain/) tarafından sağlanacaktır.
+Ethereum, iş ispatını hisse ispatı ile değiştirdiğinde, [parça zincirlerinin (shard chain)](/upgrades/sharding/) karmaşıklığı artacaktır. Bunlar, işlemleri gerçekleştirmek ve yeni bloklar oluşturmak için doğrulayıcılara ihtiyaç duyacak ayrı blok zincirleridir. 64 parça zincirinin bulunması ve hepsinin ağın durumu hakkında ortak bir anlayışa sahip olması planlanır. Sonuç olarak, ekstra koordinasyon gereklidir ve bu koordinasyon [işaret zinciri](/upgrades/beacon-chain/) tarafından sağlanacaktır.
İşaret zinciri, parçalardan durum bilgilerini alır ve ağın senkronize kalabilmesi için diğer parçalar için kullanılabilir hâle getirir. Aynı zamanda işaret zinciri, stake yatırımlarını kaydetmekten ödüllerini ve cezalarını vermeye kadar doğrulayıcıları yönetecektir.
diff --git a/src/content/translations/tr/developers/docs/scaling/index.md b/src/content/translations/tr/developers/docs/scaling/index.md
index 866766471d8..9cf6054b13b 100644
--- a/src/content/translations/tr/developers/docs/scaling/index.md
+++ b/src/content/translations/tr/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ Bu ölçeklendirme yöntemi, Ethereum protokolünde değişiklik yapılmasını
Parçalama, yükü yaymak için bir veri tabanını yatay olarak bölme işlemidir. Ethereum bağlamında parçalama, "parça" olarak bilinen yeni zincirler oluşturarak ağ tıkanıklığını azaltır ve saniye başına işlem kapasitesini artırır. Bu, aynı zamanda doğrulayıcıların ağdaki işlemlerin tamamını işleme zorunluluğunu ortadan kaldırarak tüm doğrulayıcıların yükünü azaltır.
-[Parçalama](/upgrades/shard-chains/) hakkında daha fazla bilgi.
+[Parçalama](/upgrades/sharding/) hakkında daha fazla bilgi.
## Zincir dışında ölçeklendirme {#off-chain-scaling}
diff --git a/src/content/translations/tr/nft/index.md b/src/content/translations/tr/nft/index.md
index 6b930404979..0b1897cbeed 100644
--- a/src/content/translations/tr/nft/index.md
+++ b/src/content/translations/tr/nft/index.md
@@ -406,7 +406,7 @@ Eylül 2020 yıl sonunda 140.839.000.000 işlem gerçekleştirdiler – [Visa ma
[Vitalik Buterin'in parçalama ile saniye başına işlem potansiyeli hakkında düşünceleri](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Parçalama, bugün yaklaşık 15 işlem olan işlem miktarının en az 64 katını mümkün kılacaktır. Bu, kullanıma giren parça zincirlerinin (ekstra veri ve kapasite) miktarıdır. [Parça zincirleri hakkında daha fazla bilgi](/upgrades/shard-chains/)
+Parçalama, bugün yaklaşık 15 işlem olan işlem miktarının en az 64 katını mümkün kılacaktır. Bu, kullanıma giren parça zincirlerinin (ekstra veri ve kapasite) miktarıdır. [Parça zincirleri hakkında daha fazla bilgi](/upgrades/sharding/)
Bu, yukarıdaki Visa örneğiyle karşılaştırabilmemiz için 100.000 işlemin ne kadar süreceğini tahmin edebileceğimiz anlamına gelir.
diff --git a/src/content/translations/tr/upgrades/beacon-chain/index.md b/src/content/translations/tr/upgrades/beacon-chain/index.md
index a0eb42c3c76..e9bc4e04f06 100644
--- a/src/content/translations/tr/upgrades/beacon-chain/index.md
+++ b/src/content/translations/tr/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Bunu teknik yol haritalarından "Aşama 0" olarak biliyor olabili
## İşaret (Beacon) Zinciri Ne Yapar? {#what-does-the-beacon-chain-do}
-İşaret Zinciri, [parçalardan](/upgrades/shard-chains/) ve [stake edenlerden](/staking/) oluşan genişletilmiş ağı yönetir veya koordine eder. Ancak günümüzün [Ethereum ana ağı](/glossary/#mainnet) gibi olmayacaktır. Hesapları veya akıllı sözleşmeleri ele alamaz.
+İşaret Zinciri, [parçalardan](/upgrades/sharding/) ve [stake edenlerden](/staking/) oluşan genişletilmiş ağı yönetir veya koordine eder. Ancak günümüzün [Ethereum ana ağı](/glossary/#mainnet) gibi olmayacaktır. Hesapları veya akıllı sözleşmeleri ele alamaz.
İşaret Zincirinin rolü zamanla değişecek ancak [geliştirmeye çalıştığımız güvenli, sürdürülebilir ve ölçeklenebilir Ethereum](/upgrades/vision/) için temel bir bileşendir.
@@ -33,7 +33,7 @@ Paydaşlık ve doğrulayıcı oluşturmak [madencilik](/developers/docs/mining/)
Bir doğrulayıcı olarak İşaret Zincirinin güvenliğine yardımcı olmak istiyorsanız stake etme konusunda daha fazla bilgi alın.
-Bu ayrıca başka bir yükseltme için de önemli bir değişikliktir: [parça zincirleri](/upgrades/shard-chains/).
+Bu ayrıca başka bir yükseltme için de önemli bir değişikliktir: [parça zincirleri](/upgrades/sharding/).
### Shard zincirleri kurulumu {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ Ethereum yükseltmelerinin tamamı bir şekilde ilişkilidir. İşaret (Beacon)
Parça zincirleri, Ethereum ekosistemine yalnızca hisse ispatı mutabakat mekanizması ile güvenli bir şekilde girebilir. İşaret Zinciri, staking sistemini başlatarak gelecekte parça zinciri yükseltmesine olanak verir.
-
+
Parça zincirleri
diff --git a/src/content/translations/tr/upgrades/merge/index.md b/src/content/translations/tr/upgrades/merge/index.md
index 041452db052..98251bebd3c 100644
--- a/src/content/translations/tr/upgrades/merge/index.md
+++ b/src/content/translations/tr/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Başlangıçta plan, ölçeklenebilirliği ele almak için Birleştirmeden önce
Bu, sonsuz ölçeklenebilirliğe izin vermek için potansiyel olarak birden fazla parça zinciri turuna duyulan ihtiyaç konusunda topluluk tarafından, devam eden bir değerlendirme olacaktır.
-
+
Shard zincirleri
diff --git a/src/content/translations/tr/upgrades/shard-chains/index.md b/src/content/translations/tr/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/tr/upgrades/shard-chains/index.md
rename to src/content/translations/tr/upgrades/sharding/index.md
diff --git a/src/content/translations/uk/nft/index.md b/src/content/translations/uk/nft/index.md
index 87d396849d3..46a87aef5b6 100644
--- a/src/content/translations/uk/nft/index.md
+++ b/src/content/translations/uk/nft/index.md
@@ -406,7 +406,7 @@ _Важливо також пам’ятати, що Ethereum виконує н
[Розповідь Віталіка Бутеріна про потенціал транзакцій за секунду за використання шардингу](https://twitter.com/VitalikButerin/status/1312905884549300224)
-Як мінімум, шардинг дасть змогу здійснювати в 64 рази більше транзакцій у порівнянні з поточним рівнем (близько 15 транзакцій). Це кількість ланцюгів шардів (додаткові дані та потужність), які впроваджуються. [Докладніше про ланцюги шардів](/upgrades/shard-chains/)
+Як мінімум, шардинг дасть змогу здійснювати в 64 рази більше транзакцій у порівнянні з поточним рівнем (близько 15 транзакцій). Це кількість ланцюгів шардів (додаткові дані та потужність), які впроваджуються. [Докладніше про ланцюги шардів](/upgrades/sharding/)
Це означає, що ми можемо оцінити, скільки часу потрібно для процесу обробки 100 000 транзакцій, щоб порівняти дані з прикладом Visa вище.
diff --git a/src/content/translations/uk/upgrades/beacon-chain/index.md b/src/content/translations/uk/upgrades/beacon-chain/index.md
index 285aa73bfba..bb90f693275 100644
--- a/src/content/translations/uk/upgrades/beacon-chain/index.md
+++ b/src/content/translations/uk/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: Дізнатися більше про це оновлення м
## Про оновлення Beacon Chain {#what-does-the-beacon-chain-do}
-Оновлення Beacon Chain керуватиме розширеною мережею [сегментів даних](/upgrades/shard-chains/) і [часток](/staking/). Але це нововведення не буде схожим на [основну мережу Ethereum](/glossary/#mainnet), що функціонує сьогодні. Воно не стосуватиметься акаунтів і розумних контрактів.
+Оновлення Beacon Chain керуватиме розширеною мережею [сегментів даних](/upgrades/sharding/) і [часток](/staking/). Але це нововведення не буде схожим на [основну мережу Ethereum](/glossary/#mainnet), що функціонує сьогодні. Воно не стосуватиметься акаунтів і розумних контрактів.
Роль оновлення Beacon Chain із часом змінюватиметься, однак воно й надалі залишатиметься базовою умовою для [безпечної та надійної мережі Ethereum, яку можна масштабувати](/upgrades/vision/).
@@ -33,7 +33,7 @@ summaryPoint4: Дізнатися більше про це оновлення м
Якщо ви хочете стати валідатором і допомогти захистити Beacon Chain, дізнайтеся більше про стейкінг.
-Це також важлива зміна для іншого оновлення Eth2, що стосується [ланцюгів сегментів даних](/upgrades/shard-chains/).
+Це також важлива зміна для іншого оновлення Eth2, що стосується [ланцюгів сегментів даних](/upgrades/sharding/).
### Налаштування ланцюгів сегментів даних {#setting-up-for-shard-chains}
@@ -55,7 +55,7 @@ Beacon Chain також відповідатиме за випадкове пр
Ланцюги сегментів даних зможуть безпечно входити в екосистему Ethereum лише за наявності механізму консенсусу, що перевірятиме докази частки володіння. Завдяки Beacon Chain ми впровадимо стейкінг, а згодом — оновлення стосовно ланцюгів сегментів даних.
-Ланцюги сегментів даних
+Ланцюги сегментів даних
diff --git a/src/content/translations/uk/upgrades/merge/index.md b/src/content/translations/uk/upgrades/merge/index.md
index c60607c7890..0abc89fcd5c 100644
--- a/src/content/translations/uk/upgrades/merge/index.md
+++ b/src/content/translations/uk/upgrades/merge/index.md
@@ -57,4 +57,4 @@ summaryPoint4: Раніше ми називали це злиттям.
Спільнотою постійно оцінюватиметься необхідність потенційного проведення кількох раундів ланцюгів сегментів даних, щоб забезпечити нескінченну масштабованість.
-Ланцюги сегментів даних
+Ланцюги сегментів даних
diff --git a/src/content/translations/uk/upgrades/shard-chains/index.md b/src/content/translations/uk/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/uk/upgrades/shard-chains/index.md
rename to src/content/translations/uk/upgrades/sharding/index.md
diff --git a/src/content/translations/zh/developers/docs/consensus-mechanisms/pos/index.md b/src/content/translations/zh/developers/docs/consensus-mechanisms/pos/index.md
index cab4f1ed234..d378d574caa 100644
--- a/src/content/translations/zh/developers/docs/consensus-mechanisms/pos/index.md
+++ b/src/content/translations/zh/developers/docs/consensus-mechanisms/pos/index.md
@@ -23,7 +23,7 @@ incomplete: true
- 提高能效——您不需要大量能源去挖掘区块
- 门槛降低,硬件要求减少——您不需要优秀的硬件从而获得建立新区块的机会
- 更强的去中心化——权益证明可以在网络中提供更多的节点。
-- 更有力地支持[分片链](/upgrades/shard-chains/),这是以太坊网络扩展的关键升级
+- 更有力地支持[分片链](/upgrades/sharding/),这是以太坊网络扩展的关键升级
## 权益证明、权益质押和验证者 {#pos-staking-validators}
@@ -37,7 +37,7 @@ incomplete: true
### 信标链 {#the-beacon-chain}
-以太坊用权益证明取代工作量证明时,[分片链](/upgrades/shard-chains/)的复杂性会增加。 这是需要验证者来处理交易和创建新区块的独立区块链。 计划中将有 64 个分片链,并且它们都需要对网络的当下状态有一个共同的理解。 所以这需要额外的协调工作,这将由[信标链](/upgrades/beacon-chain/)来完成。
+以太坊用权益证明取代工作量证明时,[分片链](/upgrades/sharding/)的复杂性会增加。 这是需要验证者来处理交易和创建新区块的独立区块链。 计划中将有 64 个分片链,并且它们都需要对网络的当下状态有一个共同的理解。 所以这需要额外的协调工作,这将由[信标链](/upgrades/beacon-chain/)来完成。
信标链从碎片接收状态信息,并可供其他碎片使用,以便网络能够一直保持同步。 信标链也会管理验证者,从注册其股份存储到发布奖励和惩罚。
diff --git a/src/content/translations/zh/developers/docs/scaling/index.md b/src/content/translations/zh/developers/docs/scaling/index.md
index 813840a447e..e8ca4803375 100644
--- a/src/content/translations/zh/developers/docs/scaling/index.md
+++ b/src/content/translations/zh/developers/docs/scaling/index.md
@@ -28,7 +28,7 @@ sidebarDepth: 3
区块分片是一个横向分割数据库以扩展网络承载能力的过程。 在以太坊中,区块分片将通过创建新链(称为“分片”)来减少网络拥塞和增加每秒交易量。 这还可以减轻每位验证者的负担,因为他们不再需要处理整个网络的所有交易。
-详细了解[区块分片](/upgrades/shard-chains/)。
+详细了解[区块分片](/upgrades/sharding/)。
## 链下扩容 {#off-chain-scaling}
diff --git a/src/content/translations/zh/nft/index.md b/src/content/translations/zh/nft/index.md
index 1c4c7bfd246..d94a6eedd25 100644
--- a/src/content/translations/zh/nft/index.md
+++ b/src/content/translations/zh/nft/index.md
@@ -406,7 +406,7 @@ Digiconomist 预估以太坊矿工当前每年消耗 44.94 太瓦时的总能耗
[Vitalik Buterin 谈论在分片上每秒可行的交易量](https://twitter.com/VitalikButerin/status/1312905884549300224)
-最起码,分片允许的交易量是现在的 64 倍,当前交易量大约为 15 笔交易。 这是正在引入分片链(额外数据和容量)的数量。 [关于分片链的更多信息](/upgrades/shard-chains/)
+最起码,分片允许的交易量是现在的 64 倍,当前交易量大约为 15 笔交易。 这是正在引入分片链(额外数据和容量)的数量。 [关于分片链的更多信息](/upgrades/sharding/)
这意味着我们可以估算处理 100,000 笔交易需要的时间,以便我们能够将其与上述 Visa 例子对比。
diff --git a/src/content/translations/zh/upgrades/beacon-chain/index.md b/src/content/translations/zh/upgrades/beacon-chain/index.md
index 1bd5f0bc1d0..054c96e92c7 100644
--- a/src/content/translations/zh/upgrades/beacon-chain/index.md
+++ b/src/content/translations/zh/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: 您可能知道,它在技术路线图上属于“阶段 0”。
## 信标链有什么作用? {#what-does-the-beacon-chain-do}
-信标链将处理或协调[分片](/upgrades/shard-chains/)和[质押人](/staking/)的扩展网络。 但它会与今天的[以太坊主网](/glossary/#mainnet)不同。 它无法处理帐户或智能合约。
+信标链将处理或协调[分片](/upgrades/sharding/)和[质押人](/staking/)的扩展网络。 但它会与今天的[以太坊主网](/glossary/#mainnet)不同。 它无法处理帐户或智能合约。
信标链的角色将随着时间的推移而改变,但它是[我们正在努力实现的安全、可持续和可扩展以太坊的](/upgrades/vision/)基础组件。
@@ -33,7 +33,7 @@ summaryPoint4: 您可能知道,它在技术路线图上属于“阶段 0”。
如果您有兴趣成为验证者并帮助保护信标链,请点击了解关于质押的更多信息。
-引入该机制这一重要变化也有助于实现另一个升级:[分片链](/upgrades/shard-chains/)。
+引入该机制这一重要变化也有助于实现另一个升级:[分片链](/upgrades/sharding/)。
### 设置分片链 {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ summaryPoint4: 您可能知道,它在技术路线图上属于“阶段 0”。
分片链只有在已建立权益证明共识机制的情况下才能安全进入以太坊生态系统。 信标链将引入权益质押,为后续的分片链升级奠定基础。
-
+
分片链
diff --git a/src/content/translations/zh/upgrades/merge/index.md b/src/content/translations/zh/upgrades/merge/index.md
index eb41d87e4ee..7a0b55446d9 100644
--- a/src/content/translations/zh/upgrades/merge/index.md
+++ b/src/content/translations/zh/upgrades/merge/index.md
@@ -59,7 +59,7 @@ summaryPoint4: 我们以前将此称为“对接”。
这需要社区进行持续评估,以确定是否可能需要多轮分片链来实现无限的可扩展性。
-
+
分片链
diff --git a/src/content/translations/zh/upgrades/shard-chains/index.md b/src/content/translations/zh/upgrades/sharding/index.md
similarity index 100%
rename from src/content/translations/zh/upgrades/shard-chains/index.md
rename to src/content/translations/zh/upgrades/sharding/index.md
diff --git a/src/content/upgrades/beacon-chain/index.md b/src/content/upgrades/beacon-chain/index.md
index 41f6ce5a831..e0f02946a90 100644
--- a/src/content/upgrades/beacon-chain/index.md
+++ b/src/content/upgrades/beacon-chain/index.md
@@ -17,7 +17,7 @@ summaryPoint4: You might know this as "Phase 0" on technical roadmaps.
## What does the Beacon Chain do? {#what-does-the-beacon-chain-do}
-The Beacon Chain will conduct or coordinate the expanded network of [shards](/upgrades/shard-chains/) and [stakers](/staking/). But it won't be like the [Ethereum Mainnet](/glossary/#mainnet) of today. It can't handle accounts or smart contracts.
+The Beacon Chain will conduct or coordinate the expanded network of [shards](/upgrades/sharding/) and [stakers](/staking/). But it won't be like the [Ethereum Mainnet](/glossary/#mainnet) of today. It can't handle accounts or smart contracts.
The Beacon Chain’s role will change over time but it’s a foundational component for [the secure, sustainable and scalable Ethereum we’re working towards](/upgrades/vision/).
@@ -33,7 +33,7 @@ Staking and becoming a validator is easier than [mining](/developers/docs/mining
If you're interested in becoming a validator and helping secure the Beacon Chain, learn more about staking.
-This is also an important change for another upgrade: [shard chains](/upgrades/shard-chains/).
+This is also an important change for another upgrade: [shard chains](/upgrades/sharding/).
### Setting up for shard chains {#setting-up-for-shard-chains}
@@ -57,7 +57,7 @@ The Beacon Chain, at first, will exist separately to the Ethereum Mainnet we use
Shard chains can only safely enter the Ethereum ecosystem with a proof-of-stake consensus mechanism in place. The Beacon Chain will introduce staking, paving the way for the shard chain upgrade to follow.
-
+
Shard chains
diff --git a/src/content/upgrades/merge/index.md b/src/content/upgrades/merge/index.md
index e93a62e90b3..5499eef221c 100644
--- a/src/content/upgrades/merge/index.md
+++ b/src/content/upgrades/merge/index.md
@@ -59,7 +59,7 @@ Originally, the plan was to work on shard chains before The Merge – to address
This will be an ongoing assessment from the community as to the need for potentially multiple rounds of shard chains to allow for endless scalability.
-
+
Shard chains
From 7ddf3904194a2af78d80b60feb3d42ca275fcb64 Mon Sep 17 00:00:00 2001
From: Joe
Date: Mon, 13 Jun 2022 15:44:26 +0100
Subject: [PATCH 051/244] add p2p/merge warning, rm ropsten
---
.../tutorials/run-light-node-geth/index.md | 109 +++++++++++++++++-
1 file changed, 108 insertions(+), 1 deletion(-)
diff --git a/src/content/developers/tutorials/run-light-node-geth/index.md b/src/content/developers/tutorials/run-light-node-geth/index.md
index 2281246cb6c..ed4023d6b62 100644
--- a/src/content/developers/tutorials/run-light-node-geth/index.md
+++ b/src/content/developers/tutorials/run-light-node-geth/index.md
@@ -9,6 +9,66 @@ sidebar: true
published: 2022-03-04
---
+ Please note that Geth light clients can be very slow to find peers. This is because they rely on full-node operators opting-in to be light servers that the light clients can request data from. There are usually only a small number of light servers available.
+
+Also note that after [The Merge]() a Geth node alone will not be sufficient - a consensus client must be connected to it in order to track the head of the chain.
+
+
+You may be interested in running an [Ethereum node](/developers/docs/nodes-and-clients/). One of the easiest ways to do so is by downloading, installing, and running [Geth](https://geth.ethereum.org). With Geth, we can have a light node up and running in minutes.
+
+A light client requires less than 400MB of storage whilst still allowing full interactivity with the Ethereum state. Light clients retrieve data from remote peers, so some queries may take longer to respond in comparison to other sync modes.
+
+For an explanation of the differences between the different sync modes, read our [nodes and clients developer docs](/developers/docs/nodes-and-clients/#node-types).
+
+## Install and run {#install-and-run}
+
+First, [install Geth](https://geth.ethereum.org/docs/install-and-build/installing-geth).
+
+After installing Geth, you can run an Ethereum node in "light" mode by running the following command in a Terminal window:
+
+```bash
+geth --syncmode light
+```
+
+Once launched, Geth will begin connecting to other nodes on Ethereum - known as "peers". The process of connecting to peers may take a while.
+
+When your Geth node has enough peers, it will import headers from new blocks on the chain.
+
+When new block headers no longer have an "age", Geth will be synced to the chain's head.
+
+## Stopping and restarting your node {#stopping-and-restarting-your-node}
+
+You can stop your node at any time by pressing CTRL+C.
+
+When restarting the node, Geth will take a few minutes to download block headers created since the node was last run.
+
+## Enable the HTTP-RPC server {#enable-the-http-rpc-server}
+
+Enabling the HTTP-RPC server lets you connect your Ethereum node to other software like wallets, browser extensions, or custom software libraries.
+
+You can enable the HTTP-RPC server by running the following command when launching Geth:
+
+```bash
+geth --syncmode light --http
+```
+
+Once enabled, run `curl http://127.0.0.1:8545`. This should report no error.
+
+### Allow remote connections {#allow-remote-connections}
+
+## To allow remote hosts to connect to your node, launch Geth with the following command:
+
+title: How to run a light node with Geth
+description: How to download, install and run a lightclient with Geth.
+authors: "Brian Gu"
+tags: ["clients", "geth", "nodes"]
+skill: beginner
+lang: en
+sidebar: true
+published: 2022-03-04
+
+---
+
You may be interested in running an [Ethereum node](/developers/docs/nodes-and-clients/). One of the easiest ways to do so is by downloading, installing, and running Geth. With Geth, we can have a light node up and running in minutes.
A light client requires less than 400MB of storage whilst still allowing full interactivity with the Ethereum state. Light clients retrieve data from remote peers, so some queries may take longer to respond in comparison to other sync modes.
@@ -80,7 +140,54 @@ Geth runs your node on [Ethereum Mainnet](/glossary/#mainnet) by default.
It is also possible to use Geth to run a node on one of the [public test networks](/developers/docs/networks/#ethereum-testnets), by running one of the following commands in Terminal:
```bash
-geth --syncmode light --ropsten
+geth --syncmode light --rinkeby
+geth --syncmode light --goerli
+```
+
+## Where is the blockchain and EVM data stored? {#where-is-the-blockchain-and-evm-data-stored}
+
+The directory which Geth uses to store raw blockchain data depends on your operating system. Upon running Geth, look for a message that looks like this:
+
+```bash
+INFO [11-18|14:04:47] Allocated cache and file handles database=/Users/bgu/Library/Ethereum/testnet/geth/lightchaindata cache=768 handles=128
+```
+
+The path following `“database=”` should tell you where the blockchain data is stored on your machine. If you’re running a full node, this directory will contain all of the data about every block that has ever been committed to the blockchain. Since we’re running a light node, this directory only contains the block headers.
+
+It’s worth emphasizing here that, at the lowest level, this is where the blockchain lives. The full contents of the blockchain and the EVM state are stored on every full node in the Ethereum network, in directories that look very much like the one on your computer.
+
+## Further reading {#further-reading}
+
+- [Learn more about different networks](/developers/docs/networks/).
+- [Run a full node](/run-a-node/)
+
+```
+geth --syncmode light --http --http.addr 0.0.0.0
+```
+
+Note: this assumes that there is no process blocking requests to your localhost, such as a firewall.
+
+## Geth JavaScript console {#geth-javascript-console}
+
+Geth has a built-in JavaScript console and a JavaScript API called [web3js](https://github.com/ethereum/web3.js/) that you can use to interact with your node.
+
+To use the JavaScript console run:
+
+```bash
+geth attach
+```
+
+This console allows direct interaction with Ethereum. For example, running the `eth.blockNumber` command will print the latest known block number.
+
+[Full web3js documentation](http://web3js.readthedocs.io/)
+
+## Mainnet and testnets {#mainnet-and-testnets}
+
+Geth runs your node on [Ethereum Mainnet](/glossary/#mainnet) by default.
+
+It is also possible to use Geth to run a node on one of the [public test networks](/developers/docs/networks/#ethereum-testnets), by running one of the following commands in Terminal:
+
+```bash
geth --syncmode light --rinkeby
geth --syncmode light --goerli
```
From 16f5691fc23291c71e8cc3608eb226442a8daebd Mon Sep 17 00:00:00 2001
From: Seek4samurai
Date: Mon, 13 Jun 2022 20:48:16 +0530
Subject: [PATCH 052/244] description about ERC-20 & ERC-721 and added further
reading topic on EIPs
---
src/content/developers/docs/standards/index.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/content/developers/docs/standards/index.md b/src/content/developers/docs/standards/index.md
index db1aa31b4f2..31a80715ce7 100644
--- a/src/content/developers/docs/standards/index.md
+++ b/src/content/developers/docs/standards/index.md
@@ -29,8 +29,8 @@ Certain EIPs relate to application-level standards (e.g. a standard smart-contra
### Token standards {#token-standards}
-- [ERC-20](/developers/docs/standards/tokens/erc-20/) - A standard interface for fungible (interchangeable) tokens, like voting tokens, staking tokens or virtual currencies.
-- [ERC-721](/developers/docs/standards/tokens/erc-721/) - A standard interface for non-fungible tokens, like a deed for artwork or a song.
+- [ERC-20](/developers/docs/standards/tokens/erc-20/) - A standard interface for fungible (interchangeable) tokens, like voting tokens, staking tokens or virtual currencies. Think of it as a set of rules or functions that a newly created token in the Ethereum network must respect or follow.
+- [ERC-721](/developers/docs/standards/tokens/erc-721/) - A standard interface for non-fungible tokens, like a deed for artwork or a song. Things or assets that use ERC-721 will record and assign the ownership to the account numbers.
- [ERC-777](/developers/docs/standards/tokens/erc-777/) - A token standard improving over ERC-20.
- [ERC-1155](/developers/docs/standards/tokens/erc-1155/) - A token standard which can contain both fungible and non-fungible assets.
- [ERC-4626](/developers/docs/standards/tokens/erc-4626/) - A tokenized vault standard designed to optimize and unify the technical parameters of yield-bearing vaults.
@@ -39,4 +39,6 @@ Learn more about [token standards](/developers/docs/standards/tokens/).
## Further reading {#further-reading}
+- [Ethereum Improvement Proposals (EIPs)](https://ethereum.org/en/eips/)
+
_Know of a community resource that helped you? Edit this page and add it!_
From 66034f78b2095bbabfc7db6f2c3b955ba6f1fa18 Mon Sep 17 00:00:00 2001
From: Joe
Date: Mon, 13 Jun 2022 16:21:52 +0100
Subject: [PATCH 053/244] add local and public beacon chain info
---
.../developers/docs/development-networks/index.md | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/src/content/developers/docs/development-networks/index.md b/src/content/developers/docs/development-networks/index.md
index 3e37e5b1e57..e18419a1a09 100644
--- a/src/content/developers/docs/development-networks/index.md
+++ b/src/content/developers/docs/development-networks/index.md
@@ -48,6 +48,21 @@ Hardhat Network comes built-in with Hardhat, an Ethereum development environment
- [Website](https://hardhat.org/)
- [GitHub](https://github.com/nomiclabs/hardhat)
+### Local Beacon Chains
+
+Some consensus clients have built-in tools for spinning up local Beacon chains for testing purposes. Instructions for Lighthouse, Nimbus and Lodestar are available at:
+
+[Local testnet using Lodestar](https://chainsafe.github.io/lodestar/usage/local/)
+[Local testnet using Lighthouse](https://lighthouse-book.sigmaprime.io/setup.html#local-testnets)
+[Local testnet using Nimbus](https://github.com/status-im/nimbus-eth1/blob/master/fluffy/docs/local_testnet.md)
+
+### Public Beacon Test-chains
+
+There are also public test implementation of the Beacon Chain. The recommended testnet with long term support is Prater (which will eventually merge with the Goerli chain). The Ropsten Chain was rceently merged with its own Beacon Chain and is currently still available for testing consensus client implementations and post-merge application development.
+
+[Prater Staking Launchpad](https://prater.launchpad.ethereum.org/en/)
+[Ropsten Staking Launchpad](https://ropsten.launchpad.ethereum.org/en/)
+
## Further reading {#further-reading}
_Know of a community resource that helped you? Edit this page and add it!_
From 994830d1b75b38ed48becaa802787fb1621a007e Mon Sep 17 00:00:00 2001
From: Joe
Date: Mon, 13 Jun 2022 16:35:37 +0100
Subject: [PATCH 054/244] add execution-layer info
---
.../docs/nodes-and-clients/client-diversity/index.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
index aebacbef902..c67efe0c4b2 100644
--- a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
+++ b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
@@ -51,6 +51,10 @@ The execution layer data were obtained from [Ethernodes](https://ethernodes.org)
Up to date client diversity data for the consensus layer is now available at https://clientdiversity.org/.
+## Execution Layer
+
+Up until now, the conversation around client diversity has focused mainly on the consensus layer. However, the execution client [Geth](https://geth.ethereum.org) currently accounts for around 85% of all nodes. This is problematic for the same reasons as for consensus clients. For example, a bug in Geth affecting transaction-handling or constructing execution payloads could lead to bugged information being finalized by the consensus clients. Therefore, Ethereum would be healthier with a more even distribution of execution clients, ideally with no client representing more than 33% of the network.
+
## Use a minority client {#use-minority-client}
Addressing client diversity requires more than individual users to choose minority clients - it requires mining/validator pools and institutions like the major dapps and exchanges to switch clients too. However, all users can do their part in redressing the current imbalance and normalizing the use of all the available Ethereum software. After The Merge, all node operators will be required to run an execution client and a consensus client. Choosing combinations of the clients suggested below will help increase client diversity.
From 0c11b18e9af30bdb05ce0ec375d5b368a42af4ab Mon Sep 17 00:00:00 2001
From: Akim Benchiha
Date: Mon, 13 Jun 2022 17:36:42 +0200
Subject: [PATCH 055/244] feat(beaconchainaction): add type for gatsbyImage
Refs: #6392
---
src/components/BeaconChainActions.tsx | 23 +++++++++++++++--------
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/src/components/BeaconChainActions.tsx b/src/components/BeaconChainActions.tsx
index 7afce5ae1a4..58028ca4248 100644
--- a/src/components/BeaconChainActions.tsx
+++ b/src/components/BeaconChainActions.tsx
@@ -6,11 +6,12 @@ import { useIntl } from "gatsby-plugin-intl"
import { translateMessageId } from "../utils/translations"
-import CardList, { CardListItem } from "./CardList"
+import CardList from "./CardList"
import Card from "./Card"
import ButtonLink from "./ButtonLink"
import Translation from "./Translation"
-import { GatsbyImageProps } from "gatsby-plugin-image"
+
+import type { CardListItem } from "./CardList"
const Container = styled.div`
margin-bottom: 4rem;
@@ -70,6 +71,12 @@ export const DataLogo = graphql`
}
`
+type ChildImage = {
+ childImageSharp: {
+ gatsbyImageData: Record
+ }
+}
+
const BeaconStaticQuery = graphql`
query {
beaconscan: file(relativePath: { eq: "upgrades/etherscan.png" }) {
@@ -82,33 +89,33 @@ const BeaconStaticQuery = graphql`
`
type BeaconQueryTypes = {
- beaconscan: string
- beaconchain: string
+ beaconscan: ChildImage
+ beaconchain: ChildImage
}
const BeaconChainActions: React.FC = () => {
const intl = useIntl()
const data = useStaticQuery(BeaconStaticQuery)
- const datapoints: CardListItem[] = [
+ const datapoints: Array = [
{
title: "beaconscan",
image: getImage(data.beaconscan),
- alt: "test beaconscan",
+ alt: "",
link: "https://beaconscan.com",
description: translateMessageId("consensus-beaconscan-desc", intl),
},
{
title: "beaconcha.in",
image: getImage(data.beaconchain),
- alt: "beaconcha test",
+ alt: "",
link: "https://beaconcha.in",
description: translateMessageId("consensus-beaconcha-in-desc", intl),
},
]
//TODO: we should refactor the naming here instead of using authors into the description field
- const reads: CardListItem[] = [
+ const reads: Array = [
{
title: translateMessageId(
"page-upgrade-article-title-two-point-oh",
From 175662f008ea98f07a299c8d2424d1a34b57d2e2 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Mon, 13 Jun 2022 16:49:36 +0100
Subject: [PATCH 056/244] Update
src/content/developers/docs/development-networks/index.md
---
src/content/developers/docs/development-networks/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/development-networks/index.md b/src/content/developers/docs/development-networks/index.md
index e18419a1a09..981ba530e2d 100644
--- a/src/content/developers/docs/development-networks/index.md
+++ b/src/content/developers/docs/development-networks/index.md
@@ -48,7 +48,7 @@ Hardhat Network comes built-in with Hardhat, an Ethereum development environment
- [Website](https://hardhat.org/)
- [GitHub](https://github.com/nomiclabs/hardhat)
-### Local Beacon Chains
+### Local Beacon Chains {#local-beacon-chains}
Some consensus clients have built-in tools for spinning up local Beacon chains for testing purposes. Instructions for Lighthouse, Nimbus and Lodestar are available at:
From 2b53a7f981e4340d479e81b9811b16633f60d7cd Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Mon, 13 Jun 2022 16:49:42 +0100
Subject: [PATCH 057/244] Update
src/content/developers/docs/development-networks/index.md
---
src/content/developers/docs/development-networks/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/development-networks/index.md b/src/content/developers/docs/development-networks/index.md
index 981ba530e2d..b4f176e788b 100644
--- a/src/content/developers/docs/development-networks/index.md
+++ b/src/content/developers/docs/development-networks/index.md
@@ -50,7 +50,7 @@ Hardhat Network comes built-in with Hardhat, an Ethereum development environment
### Local Beacon Chains {#local-beacon-chains}
-Some consensus clients have built-in tools for spinning up local Beacon chains for testing purposes. Instructions for Lighthouse, Nimbus and Lodestar are available at:
+Some consensus clients have built-in tools for spinning up local Beacon chains for testing purposes. Instructions for Lighthouse, Nimbus and Lodestar are available:
[Local testnet using Lodestar](https://chainsafe.github.io/lodestar/usage/local/)
[Local testnet using Lighthouse](https://lighthouse-book.sigmaprime.io/setup.html#local-testnets)
From 538422bea724c7ebb16ea3bd91e9ac8066e0e599 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Mon, 13 Jun 2022 16:49:58 +0100
Subject: [PATCH 058/244] Update
src/content/developers/docs/development-networks/index.md
---
src/content/developers/docs/development-networks/index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/content/developers/docs/development-networks/index.md b/src/content/developers/docs/development-networks/index.md
index b4f176e788b..6879df6d711 100644
--- a/src/content/developers/docs/development-networks/index.md
+++ b/src/content/developers/docs/development-networks/index.md
@@ -52,9 +52,9 @@ Hardhat Network comes built-in with Hardhat, an Ethereum development environment
Some consensus clients have built-in tools for spinning up local Beacon chains for testing purposes. Instructions for Lighthouse, Nimbus and Lodestar are available:
-[Local testnet using Lodestar](https://chainsafe.github.io/lodestar/usage/local/)
-[Local testnet using Lighthouse](https://lighthouse-book.sigmaprime.io/setup.html#local-testnets)
-[Local testnet using Nimbus](https://github.com/status-im/nimbus-eth1/blob/master/fluffy/docs/local_testnet.md)
+- [Local testnet using Lodestar](https://chainsafe.github.io/lodestar/usage/local/)
+- [Local testnet using Lighthouse](https://lighthouse-book.sigmaprime.io/setup.html#local-testnets)
+- [Local testnet using Nimbus](https://github.com/status-im/nimbus-eth1/blob/master/fluffy/docs/local_testnet.md)
### Public Beacon Test-chains
From 43f760230b3f6db96c3849e9dd556cd6044bb1d4 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Mon, 13 Jun 2022 16:51:18 +0100
Subject: [PATCH 059/244] Apply suggestions from code review
---
src/content/developers/docs/development-networks/index.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/content/developers/docs/development-networks/index.md b/src/content/developers/docs/development-networks/index.md
index 6879df6d711..17e4890c3c9 100644
--- a/src/content/developers/docs/development-networks/index.md
+++ b/src/content/developers/docs/development-networks/index.md
@@ -56,12 +56,12 @@ Some consensus clients have built-in tools for spinning up local Beacon chains f
- [Local testnet using Lighthouse](https://lighthouse-book.sigmaprime.io/setup.html#local-testnets)
- [Local testnet using Nimbus](https://github.com/status-im/nimbus-eth1/blob/master/fluffy/docs/local_testnet.md)
-### Public Beacon Test-chains
+### Public Beacon Test-chains {#public-beacon-testchains}
-There are also public test implementation of the Beacon Chain. The recommended testnet with long term support is Prater (which will eventually merge with the Goerli chain). The Ropsten Chain was rceently merged with its own Beacon Chain and is currently still available for testing consensus client implementations and post-merge application development.
+There are also public test implementations of the Beacon Chain. The recommended testnet with long-term support is Prater (which will eventually merge with the Goerli chain). The Ropsten Chain was recently merged with its own Beacon Chain and is currently still available for testing consensus client implementations and post-merge application development.
-[Prater Staking Launchpad](https://prater.launchpad.ethereum.org/en/)
-[Ropsten Staking Launchpad](https://ropsten.launchpad.ethereum.org/en/)
+- [Prater Staking Launchpad](https://prater.launchpad.ethereum.org/en/)
+- [Ropsten Staking Launchpad](https://ropsten.launchpad.ethereum.org/en/)
## Further reading {#further-reading}
From 8665663fdd32746b59fe5ae44272bc3a4cd5d346 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Mon, 13 Jun 2022 09:31:15 -0700
Subject: [PATCH 060/244] Update src/components/PreMergeBanner.tsx
Co-authored-by: Joshua <62268199+minimalsm@users.noreply.github.com>
---
src/components/PreMergeBanner.tsx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/components/PreMergeBanner.tsx b/src/components/PreMergeBanner.tsx
index e051862f357..d9c5c45adda 100644
--- a/src/components/PreMergeBanner.tsx
+++ b/src/components/PreMergeBanner.tsx
@@ -17,7 +17,7 @@ export interface IProps {
const PreMergeBanner: React.FC = ({ className }) => (
- The Merge is approaching which comes with many changes to Ethereum. Some
+ The Merge is approaching, and with it comes many changes to Ethereum. Some
content on this page may be out-of-date related to these changes, and
updates are coming soon.{" "}
Learn more about The Merge.
From 473d8ce2ddfc93ef451fdba74440f6a82921301c Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Mon, 13 Jun 2022 10:44:03 -0600
Subject: [PATCH 061/244] Update layer-2.js
---
src/pages/layer-2.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index ea3564f85c5..d53e3b263a1 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -679,8 +679,9 @@ const Layer2Page = ({ data }) => {
+
A note on wallets
- NOTE: When bridging over and using layer 2, it is important to note
+ When bridging over and using layer 2, it is important to note
that you will control the address for your{" "}
EOA account (an account where only a
single private key controls the account) just like on Ethereum
From ac8b575fe0e748266585820701b6593a30ea043b Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Mon, 13 Jun 2022 17:50:08 +0100
Subject: [PATCH 062/244] Add header id
---
.../developers/docs/nodes-and-clients/client-diversity/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
index c67efe0c4b2..7570c9b3a4f 100644
--- a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
+++ b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
@@ -51,7 +51,7 @@ The execution layer data were obtained from [Ethernodes](https://ethernodes.org)
Up to date client diversity data for the consensus layer is now available at https://clientdiversity.org/.
-## Execution Layer
+## Execution layer {#execution-layer}
Up until now, the conversation around client diversity has focused mainly on the consensus layer. However, the execution client [Geth](https://geth.ethereum.org) currently accounts for around 85% of all nodes. This is problematic for the same reasons as for consensus clients. For example, a bug in Geth affecting transaction-handling or constructing execution payloads could lead to bugged information being finalized by the consensus clients. Therefore, Ethereum would be healthier with a more even distribution of execution clients, ideally with no client representing more than 33% of the network.
From a2aa24e46945806e808c348fe4b8e5965c2f187c Mon Sep 17 00:00:00 2001
From: Nuno Loureiro
Date: Mon, 13 Jun 2022 18:02:49 +0100
Subject: [PATCH 063/244] changed back to a
---
src/pages/layer-2.js | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index d53e3b263a1..b554adae75b 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -679,9 +679,8 @@ const Layer2Page = ({ data }) => {
-
A note on wallets
- When bridging over and using layer 2, it is important to note
+ Note: When bridging over and using layer 2, it is important to note
that you will control the address for your{" "}
EOA account (an account where only a
single private key controls the account) just like on Ethereum
From 552358c1aa66cbbf9f99632b0476c393a27dfb05 Mon Sep 17 00:00:00 2001
From: vdusart
Date: Mon, 13 Jun 2022 19:04:05 +0200
Subject: [PATCH 064/244] Convert FeedbackCard to TS
---
src/components/{FeedbackCard.js => FeedbackCard.tsx} | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
rename src/components/{FeedbackCard.js => FeedbackCard.tsx} (95%)
diff --git a/src/components/FeedbackCard.js b/src/components/FeedbackCard.tsx
similarity index 95%
rename from src/components/FeedbackCard.js
rename to src/components/FeedbackCard.tsx
index 655cdf6e48d..2671fdd2446 100644
--- a/src/components/FeedbackCard.js
+++ b/src/components/FeedbackCard.tsx
@@ -39,7 +39,12 @@ const ButtonContainer = styled.div`
}
`
-const FeedbackCard = ({ prompt, className }) => {
+export interface IProps {
+ prompt?: string
+ className?: string
+}
+
+const FeedbackCard: React.FC = ({ prompt, className }) => {
const [feedbackSubmitted, setFeedbackSubmitted] = useState(false)
const [isHelpful, setIsHelpful] = useState(false)
const location = typeof window !== "undefined" ? window.location.href : ""
From 48f070a712c92f956216947d562a7a6b2e3ede67 Mon Sep 17 00:00:00 2001
From: Nuno Loureiro
Date: Mon, 13 Jun 2022 18:06:01 +0100
Subject: [PATCH 065/244] Uppercase the word
---
src/pages/layer-2.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/pages/layer-2.js b/src/pages/layer-2.js
index b554adae75b..0b125aad953 100644
--- a/src/pages/layer-2.js
+++ b/src/pages/layer-2.js
@@ -680,7 +680,7 @@ const Layer2Page = ({ data }) => {
- Note: When bridging over and using layer 2, it is important to note
+ NOTE: When bridging over and using layer 2, it is important to note
that you will control the address for your{" "}
EOA account (an account where only a
single private key controls the account) just like on Ethereum
From 5a5aee4dccb61bc66af3063d0021833696292b1c Mon Sep 17 00:00:00 2001
From: vdusart
Date: Mon, 13 Jun 2022 19:20:02 +0200
Subject: [PATCH 066/244] Convert FeedbackWidget to TS
---
.../{FeedbackWidget.js => FeedbackWidget.tsx} | 20 ++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
rename src/components/{FeedbackWidget.js => FeedbackWidget.tsx} (95%)
diff --git a/src/components/FeedbackWidget.js b/src/components/FeedbackWidget.tsx
similarity index 95%
rename from src/components/FeedbackWidget.js
rename to src/components/FeedbackWidget.tsx
index 1d933bbe6f8..95997f0f142 100644
--- a/src/components/FeedbackWidget.js
+++ b/src/components/FeedbackWidget.tsx
@@ -51,7 +51,9 @@ const ModalBackground = styled.div`
z-index: 1001; /* Above the nav bar */
`
-const Container = styled.div`
+const Container = styled.div<{
+ bottomOffset: number
+}>`
display: flex;
box-sizing: border-box;
width: 300px;
@@ -141,9 +143,13 @@ const IconContainer = styled(NakedButton)`
transition: transform 0.2s ease-in-out;
`
-const FeedbackWidget = ({ className }) => {
+export interface IProps {
+ className?: string
+}
+
+const FeedbackWidget: React.FC = ({ className }) => {
const intl = useIntl()
- const containerRef = useRef()
+ const containerRef = useRef(null)
useOnClickOutside(containerRef, () => handleClose(), [`mousedown`])
const [isOpen, setIsOpen] = useState(false)
const [feedbackSubmitted, setFeedbackSubmitted] = useState(false)
@@ -197,7 +203,7 @@ const FeedbackWidget = ({ className }) => {
trackCustomEvent({
eventCategory: `FeedbackWidget toggled`,
eventAction: `Clicked`,
- label: `Closed feedback widget`,
+ eventName: `Closed feedback widget`,
})
}
const handleOpen = () => {
@@ -205,14 +211,14 @@ const FeedbackWidget = ({ className }) => {
trackCustomEvent({
eventCategory: `FeedbackWidget toggled`,
eventAction: `Clicked`,
- label: `Opened feedback widget`,
+ eventName: `Opened feedback widget`,
})
}
const handleSubmit = (choice) => {
trackCustomEvent({
eventCategory: `Page is helpful feedback`,
eventAction: `Clicked`,
- label: choice,
+ eventName: choice,
})
setIsHelpful(choice)
setFeedbackSubmitted(true)
@@ -221,7 +227,7 @@ const FeedbackWidget = ({ className }) => {
trackCustomEvent({
eventCategory: `Feedback survey opened`,
eventAction: `Clicked`,
- label: "Feedback survey opened",
+ eventName: "Feedback survey opened",
})
window && surveyUrl && window.open(surveyUrl, "_blank")
setIsOpen(false) // Close widget without triggering redundant tracker event
From 74b9c8bdd2ebb2b3c2ae90eb74545999ad49f91c Mon Sep 17 00:00:00 2001
From: vdusart
Date: Mon, 13 Jun 2022 19:20:24 +0200
Subject: [PATCH 067/244] Convert FileContributors to TS
---
...leContributors.js => FileContributors.tsx} | 21 +++++++++++++++----
1 file changed, 17 insertions(+), 4 deletions(-)
rename src/components/{FileContributors.js => FileContributors.tsx} (95%)
diff --git a/src/components/FileContributors.js b/src/components/FileContributors.tsx
similarity index 95%
rename from src/components/FileContributors.js
rename to src/components/FileContributors.tsx
index a94d5758d0a..5d20c35762a 100644
--- a/src/components/FileContributors.js
+++ b/src/components/FileContributors.tsx
@@ -10,6 +10,7 @@ import Modal from "./Modal"
import Translation from "./Translation"
import { ButtonSecondary } from "./SharedStyledComponents"
import { getLocaleTimestamp } from "../utils/time"
+import { Lang } from "../utils/languages"
const loadingStyles = css`
font-size: 0;
@@ -47,9 +48,11 @@ const Container = styled.div`
}
`
-const SkeletonContainer = styled(Container)`
+const SkeletonContainer = styled(Container)<{
+ loading: boolean
+}>`
justify-content: flex-start;
- position: absolute;
+ position: absolute;é
width: 100%;
height: 100%;
left: 0;
@@ -224,7 +227,17 @@ const COMMIT_HISTORY = gql`
}
`
-const FileContributors = ({ relativePath, className, editPath }) => {
+export interface IProps {
+ relativePath: string
+ className?: string
+ editPath?: string
+}
+
+const FileContributors: React.FC = ({
+ relativePath,
+ className,
+ editPath,
+}) => {
const [isModalOpen, setModalOpen] = useState(false)
const intl = useIntl()
@@ -300,7 +313,7 @@ const FileContributors = ({ relativePath, className, editPath }) => {
)}
{!lastContributor.user && {lastContributor.name}},{" "}
- {getLocaleTimestamp(intl.locale, lastCommit.committedDate)}
+ {getLocaleTimestamp(intl.locale as Lang, lastCommit.committedDate)}
From ebeeb9377385d6a5b57fafcdf51cb718e8260f95 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Mon, 13 Jun 2022 18:46:19 +0100
Subject: [PATCH 068/244] Update
src/content/developers/docs/nodes-and-clients/client-diversity/index.md
---
.../developers/docs/nodes-and-clients/client-diversity/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
index 7570c9b3a4f..3a7b39b9c78 100644
--- a/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
+++ b/src/content/developers/docs/nodes-and-clients/client-diversity/index.md
@@ -53,7 +53,7 @@ Up to date client diversity data for the consensus layer is now available at htt
## Execution layer {#execution-layer}
-Up until now, the conversation around client diversity has focused mainly on the consensus layer. However, the execution client [Geth](https://geth.ethereum.org) currently accounts for around 85% of all nodes. This is problematic for the same reasons as for consensus clients. For example, a bug in Geth affecting transaction-handling or constructing execution payloads could lead to bugged information being finalized by the consensus clients. Therefore, Ethereum would be healthier with a more even distribution of execution clients, ideally with no client representing more than 33% of the network.
+Until now, the conversation around client diversity has focused mainly on the consensus layer. However, the execution client [Geth](https://geth.ethereum.org) currently accounts for around 85% of all nodes. This percentage is problematic for the same reasons as for consensus clients. For example, a bug in Geth affecting transaction handling or constructing execution payloads could lead to consensus clients finalizing problematic or bugged transactions. Therefore, Ethereum would be healthier with a more even distribution of execution clients, ideally with no client representing more than 33% of the network.
## Use a minority client {#use-minority-client}
From bf8e26f375e090703b265ebe1b3b6f06dfdef1cb Mon Sep 17 00:00:00 2001
From: vdusart
Date: Mon, 13 Jun 2022 23:24:43 +0200
Subject: [PATCH 069/244] Convert Footer file to TS
---
src/components/{Footer.js => Footer.tsx} | 26 +++++++++++++++++-------
1 file changed, 19 insertions(+), 7 deletions(-)
rename src/components/{Footer.js => Footer.tsx} (93%)
diff --git a/src/components/Footer.js b/src/components/Footer.tsx
similarity index 93%
rename from src/components/Footer.js
rename to src/components/Footer.tsx
index 269f4bea87b..969bb0c78e8 100644
--- a/src/components/Footer.js
+++ b/src/components/Footer.tsx
@@ -7,7 +7,8 @@ import { getLocaleTimestamp } from "../utils/time"
import Translation from "./Translation"
import Link from "./Link"
import Icon from "./Icon"
-import { isLangRightToLeft } from "../utils/translations"
+import { isLangRightToLeft, TranslationKey } from "../utils/translations"
+import { Lang } from "../utils/languages"
const StyledFooter = styled.footer`
padding-top: 3rem;
@@ -121,12 +122,23 @@ const socialLinks = [
},
]
-const Footer = () => {
+export interface LinkSection {
+ title: TranslationKey
+ links: Array<{
+ to: string
+ text: TranslationKey
+ isPartiallyActive?: boolean
+ }>
+}
+
+export interface IProps {}
+
+const Footer: React.FC = () => {
const intl = useIntl()
- const isPageRightToLeft = isLangRightToLeft(intl.locale)
+ const isPageRightToLeft = isLangRightToLeft(intl.locale as Lang)
- const linkSections = [
+ const linkSections: Array = [
{
title: "use-ethereum",
links: [
@@ -355,7 +367,7 @@ const Footer = () => {
:{" "}
{getLocaleTimestamp(
- intl.locale,
+ intl.locale as Lang,
data.allSiteBuildMetadata.edges[0].node.buildTime
)}
@@ -375,7 +387,7 @@ const Footer = () => {
- {linkSections.map((section, idx) => (
+ {linkSections.map((section: LinkSection, idx) => (
@@ -384,7 +396,7 @@ const Footer = () => {
{section.links.map((link, linkIdx) => (
From 01da6672fcd6c89ab289d11be21c4a3ad2c0e1f6 Mon Sep 17 00:00:00 2001
From: vdusart
Date: Mon, 13 Jun 2022 23:33:41 +0200
Subject: [PATCH 070/244] Convert GhostCard file to TS
---
src/components/{GhostCard.js => GhostCard.tsx} | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
rename src/components/{GhostCard.js => GhostCard.tsx} (88%)
diff --git a/src/components/GhostCard.js b/src/components/GhostCard.tsx
similarity index 88%
rename from src/components/GhostCard.js
rename to src/components/GhostCard.tsx
index 79b4f9a2069..ce50aac9461 100644
--- a/src/components/GhostCard.js
+++ b/src/components/GhostCard.tsx
@@ -30,7 +30,11 @@ const Ghost = styled(BaseCard)`
background-color: ${(props) => props.theme.colors.ghostCardGhost};
`
-const GhostCard = ({ children, className }) => (
+export interface IProps {
+ className?: string
+}
+
+const GhostCard: React.FC = ({ children, className }) => (
{children}
From 96c43c84f231b220f1ccbc111b32258c612ce67d Mon Sep 17 00:00:00 2001
From: vdusart
Date: Mon, 13 Jun 2022 23:43:42 +0200
Subject: [PATCH 071/244] Convert GitStars file to TS
---
src/components/{GitStars.js => GitStars.tsx} | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
rename src/components/{GitStars.js => GitStars.tsx} (87%)
diff --git a/src/components/GitStars.js b/src/components/GitStars.tsx
similarity index 87%
rename from src/components/GitStars.js
rename to src/components/GitStars.tsx
index 92ee7d0e09e..5ba41a5a720 100644
--- a/src/components/GitStars.js
+++ b/src/components/GitStars.tsx
@@ -46,8 +46,18 @@ const Text = styled.div`
font-size: 0.8125rem;
background: ${(props) => props.theme.colors.searchBackgroundEmpty};
`
+export interface GitHubRepo {
+ stargazerCount: number
+ url: string
+}
+
+export interface IProps {
+ gitHubRepo: GitHubRepo
+ className?: string
+ hideStars: string
+}
-const GitStars = ({ gitHubRepo, className, hideStars }) => {
+const GitStars: React.FC = ({ gitHubRepo, className, hideStars }) => {
// Stringify with commas
let starsString = gitHubRepo.stargazerCount.toString()
const rgx = /(\d+)(\d{3})/
From c6997633ec01815356b607aaa455b738d6246414 Mon Sep 17 00:00:00 2001
From: Paul Wackerow <54227730+wackerow@users.noreply.github.com>
Date: Mon, 13 Jun 2022 18:19:04 -0700
Subject: [PATCH 072/244] Update /sharding pre-merge copy
Adds "outdated" InfoBanner as a temporary communication measure while content updates are being planned, with link to external resource.
---
src/content/upgrades/sharding/index.md | 27 +++++++++++++++-----------
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/src/content/upgrades/sharding/index.md b/src/content/upgrades/sharding/index.md
index 9cb09c5ad3e..daf4e7a38ab 100644
--- a/src/content/upgrades/sharding/index.md
+++ b/src/content/upgrades/sharding/index.md
@@ -1,23 +1,23 @@
---
-title: Shard chains
-description: Learn about shard chains - partitions of the network that give Ethereum more transaction capacity and make it easier to run.
+title: Sharding
+description: Learn about data sharding - breaking up and distributing the data load needed to give Ethereum more transaction capacity and make it easier to run.
lang: en
template: upgrade
sidebar: true
image: ../../../assets/upgrades/newrings.png
summaryPoint1: Sharding is a multi-phase upgrade to improve Ethereum’s scalability and capacity.
-summaryPoint2: Shard chains provide extra, cheaper, storage layers for applications and rollups to store data.
+summaryPoint2: Sharding provides secure distribution of data storage requirements, enabling rollups to be even cheaper, and making nodes easier to operate.
summaryPoint3: They enable layer 2 solutions to offer low transaction fees while leveraging the security of Ethereum.
summaryPoint4: This upgrade is planned to follow The Merge of Mainnet with the Beacon Chain.
---
- Shard chains should ship sometime in 2023, depending on how quickly work progresses after The Merge. These shards will give Ethereum more capacity to store and access data, but they won’t be used for executing code.
+ Sharding should ship sometime in 2023, depending on how quickly work progresses after The Merge. These shards will give Ethereum more capacity to store and access data, but they won’t be used for executing code.
## What is sharding? {#what-is-sharding}
-Sharding is the process of splitting a database horizontally to spread the load – it’s a common concept in computer science. In an Ethereum context, sharding will reduce network congestion and increase transactions per second by creating new chains, known as “shards”.
+Sharding is the process of splitting a database horizontally to spread the load – it’s a common concept in computer science. In an Ethereum context, sharding will work synergistically with [layer 2 rollups] by splitting up the burden of handling the large amount of data needed by rollups over the entire network. This will continue to reduce network congestion and increase transactions per second.
This is important for reasons other than scalability.
@@ -25,7 +25,7 @@ This is important for reasons other than scalability.
### Everyone can run a node {#everyone-can-run-a-node}
-Sharding is a good way to scale if you want to keep things decentralized as the alternative is to scale by increasing the size of the existing database. This would make Ethereum less accessible for network validators because they'd need powerful and expensive computers. With shard chains, validators only need to store/run data for the shard they're validating, not the entire network (like what happens today). This speeds things up and drastically reduces hardware requirements.
+Sharding is a good way to scale if you want to keep things decentralized as the alternative is to scale by increasing the size of the existing database. This would make Ethereum less accessible for network validators because they'd need powerful and expensive computers. With sharding, validators will no longer be required to store all of this data themselves, but instead can use data techniques to confirm that the data has been made available by the network as a whole. This drastically reduces the cost of storing data on layer 1 by reducing hardware requirements.
### More network participation {#more-network-participation}
@@ -35,18 +35,23 @@ With lower hardware requirements, sharding will make it easier to run [clients](
-
- At first, you'll need to run a Mainnet client at the same time as your Beacon Chain client. The launchpad will walk you through the hardware requirements and process. Alternatively you can use a backend API.
+
+ At first, you'll need to run a Mainnet (execution layer) client at the same time as your Beacon Chain (consensus later) client. The launchpad will walk you through the hardware requirements and process.
## Shard chains version 1: data availability {#data-availability}
+
+ Note: The plans for sharding have been evolving as more efficient paths to scaling have been developed. "Danksharding" is a new approach to sharding, which does not utilize the concept of shard "chains" but instead uses shard "blobs" to split up the data, along with "data availability sampling" to confirm all data has been made available. This change in plan solves the same original problem.
+ Details below may be out of date with the latest development plans. While we update things, check out The Hitchhiker's Guide to the Ethereum for an excellent breakdown of Ethereum plans after The Merge.
+
+
When the first shard chains are shipped they will just provide extra data to the network. They won’t handle transactions or smart contracts. But they’ll still offer incredible improvements to transactions per second when combined with rollups.
Rollups are a "layer 2" technology that exists today. They allow dapps to bundle or “roll up” transactions into a single transaction off-chain, generate a cryptographic proof and then submit it to the chain. This reduces the data needed for a transaction. Combine this with all the extra data availability provided by shards and you get 100,000 transactions per second.
-
- Given recent progress in layer 2 scaling solution research and development, this has prompted the prioritization of The Merge upgrade ahead of shard chains. These will be the focus following Mainnet transition to proof-of-stake.
+
+ Given recent progress in layer 2 scaling solution research and development, this has prompted the prioritization of transitioning to proof-of-stake ahead of sharding. Sharding will be the focus following The Merge.
[More on rollups](/developers/docs/scaling/#rollups)
@@ -69,7 +74,7 @@ This would mean we don’t give shards the capability to handle smart contracts
#### 2. Have some execution shards {#some-execution-shards}
-Perhaps there’s a compromise where we don’t need all shards (64 are planned right now) to be smarter. We could just add this functionality to a few and leave the rest. This could speed the delivery up.
+Perhaps there’s a compromise where we don’t need all shards to be smarter. We could just add this functionality to a few and leave the rest. This could speed the delivery up.
#### 3. Wait until we can do Zero Knowledge (ZK) snarks {#wait-for-zk-snarks}
From 72768cbe227bf08d1c9e54a14dfa54619f4cd2b8 Mon Sep 17 00:00:00 2001
From: gichiba
Date: Tue, 14 Jun 2022 12:10:56 +0700
Subject: [PATCH 073/244] Update Fellowship Program copy.
---
src/content/foundation/index.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/src/content/foundation/index.md b/src/content/foundation/index.md
index b71fab63a3a..870cbee6126 100644
--- a/src/content/foundation/index.md
+++ b/src/content/foundation/index.md
@@ -31,11 +31,9 @@ Learn more at [devcon.org](https://devcon.org/), check out the [Devcon Blog](htt
### Fellowship Program {#fellowship-program}
-The [Ethereum Foundation Fellowship Program](https://fellowship.ethereum.foundation/) is a pilot project that focuses on seeking opportunities in emerging economies. Developing countries today account for over 80% of the world’s population. Amongst about 400,000 babies born every day around the world, more than 360,000 are born in developing countries. People in developing nations represent not only our future as a people, but they may also represent the next billion active users of Ethereum.
+The [Ethereum Foundation Fellowship Program](https://fellowship.ethereum.foundation/) is an initiative to help address gaps in representation across cultures, nationalities, and economic classes. The Fellowship Program is about bridging these gaps by identifying and supporting unique and talented individuals helping to enable Ethereum’s relevance and breaking down barriers to entry for those underrepresented people and communities who will become the future of web3.
-The Fellowship Program provides the EF an opportunity to work with change-makers, whose projects have high potential to create impact in emerging economies by using Ethereum. The program features a unique experience that includes mentorship, expertise and access to leaders in the Ethereum ecosystem.
-
-Learn more at [fellowship.ethereum.foundation](https://fellowship.ethereum.foundation/) or check out the [recent blog post on the Fellowship Program](https://blog.ethereum.org/2021/05/07/ethereum-for-the-next-billion/).
+Learn more at [fellowship.ethereum.foundation](https://fellowship.ethereum.foundation/).
From 23f197d1a16663b79292d5ebac71ec5fbe167119 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Tue, 14 Jun 2022 00:02:03 -0600
Subject: [PATCH 074/244] Update
src/content/contributing/adding-wallet/index.md
Co-authored-by: Luka Kropec <37338979+lukassim@users.noreply.github.com>
---
src/content/contributing/adding-wallet/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
index afc8de81617..86f1aa8f9f3 100644
--- a/src/content/contributing/adding-wallet/index.md
+++ b/src/content/contributing/adding-wallet/index.md
@@ -7,7 +7,7 @@ sidebar: true
# Adding wallets {#adding-wallets}
-We want to make sure we show a variety of wallets covering the feature rich landscape of wallets so that users can navigate Ethereum in a confident manner.
+We want to make sure we show a variety of wallets covering the feature-rich landscape of wallets so that users can navigate Ethereum in a confident manner.
Anyone is free to suggest adding a wallet on ethereum.org. If there's a wallet that we have missed, please suggest it!
From 66b374341ff3d7fc68ee661f8822a87f7cf85a32 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Tue, 14 Jun 2022 00:02:12 -0600
Subject: [PATCH 075/244] Update
src/content/contributing/adding-wallet/index.md
Co-authored-by: Luka Kropec <37338979+lukassim@users.noreply.github.com>
---
src/content/contributing/adding-wallet/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
index 86f1aa8f9f3..352e142f25e 100644
--- a/src/content/contributing/adding-wallet/index.md
+++ b/src/content/contributing/adding-wallet/index.md
@@ -22,7 +22,7 @@ Wallets are rapidly changing in Ethereum. We've tried to create a fair framework
### Criteria for inclusion: the must-haves {#the-must-haves}
- **A security-tested product** - whether through audit, an internal security team, open sourced coded, or some other method, your wallets security must be reliable. This reduces the risk to our users and shows us that you take security seriously.
-- **A wallet that has been “live” for over 6 months OR released by a group with a reputable track record** - this is another indication of security. 6 months is a good time frame for critical bugs and exploitations to have been found. We ask 6 months to help filter our forks that are quickly abandoned as projects.
+- **A wallet that has been “live” for over 6 months OR released by a group with a reputable track record** - this is another indication of security. 6 months is a good time frame for critical bugs and exploitations to have been found. We ask 6 months to help filter out forks that are quickly abandoned as projects.
- **Worked on by an active team** - this helps to ensure quality and that a user will get support for their queries.
- **Honest and accurate listing information** - it is expected that any suggesting listings from projects come with honest and accurate information. Products that falsify listing information, such as declaring your product is “open source” when it is not, will be removed.
- **Point of contact** - A point of contact for the wallet will greatly help us get accurate information when changes are made. This will keep updating ethereum.org manageable when gathering future information.
From ea7912d2117adfedb72451775533b5ed1f022522 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Tue, 14 Jun 2022 00:02:23 -0600
Subject: [PATCH 076/244] Update
src/content/contributing/adding-wallet/index.md
Co-authored-by: Luka Kropec <37338979+lukassim@users.noreply.github.com>
---
src/content/contributing/adding-wallet/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
index 352e142f25e..fdd77cf8beb 100644
--- a/src/content/contributing/adding-wallet/index.md
+++ b/src/content/contributing/adding-wallet/index.md
@@ -24,7 +24,7 @@ Wallets are rapidly changing in Ethereum. We've tried to create a fair framework
- **A security-tested product** - whether through audit, an internal security team, open sourced coded, or some other method, your wallets security must be reliable. This reduces the risk to our users and shows us that you take security seriously.
- **A wallet that has been “live” for over 6 months OR released by a group with a reputable track record** - this is another indication of security. 6 months is a good time frame for critical bugs and exploitations to have been found. We ask 6 months to help filter out forks that are quickly abandoned as projects.
- **Worked on by an active team** - this helps to ensure quality and that a user will get support for their queries.
-- **Honest and accurate listing information** - it is expected that any suggesting listings from projects come with honest and accurate information. Products that falsify listing information, such as declaring your product is “open source” when it is not, will be removed.
+- **Honest and accurate listing information** - it is expected that any suggested listings from projects come with honest and accurate information. Products that falsify listing information, such as declaring your product is “open source” when it is not, will be removed.
- **Point of contact** - A point of contact for the wallet will greatly help us get accurate information when changes are made. This will keep updating ethereum.org manageable when gathering future information.
### Other criteria: the nice-to-haves {#the-nice-to-haves}
From 5989017031691854eec05fbc7cbdb0073dfe31f7 Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Tue, 14 Jun 2022 00:02:28 -0600
Subject: [PATCH 077/244] Update
src/content/contributing/adding-wallet/index.md
Co-authored-by: Luka Kropec <37338979+lukassim@users.noreply.github.com>
---
src/content/contributing/adding-wallet/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
index fdd77cf8beb..8f017d8aba0 100644
--- a/src/content/contributing/adding-wallet/index.md
+++ b/src/content/contributing/adding-wallet/index.md
@@ -36,7 +36,7 @@ Wallets are rapidly changing in Ethereum. We've tried to create a fair framework
- **Hardware wallet support** - users can connect their hardware wallet to sign transactions.
- **WalletConnect** - users can connect to dapps using WalletConnect.
- **Importing Ethereum RPC endpoints** - users can import node RPC data, allowing them to connect to a node of their choice, or other EVM compatible networks.
-- **NFTs** - users are able to view and interact with their NFT’s in the wallet.
+- **NFTs** - users are able to view and interact with their NFTs in the wallet.
- **Connect to Ethereum applications** - users are able to connect to and use Ethereum applications.
- **Staking** - users are able to stake directly through the wallet.
- **Swaps** - users are able to swap tokens through the wallet.
From 4b04938e2acc32c6072ef3b3e258b67def50b57b Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Tue, 14 Jun 2022 00:02:34 -0600
Subject: [PATCH 078/244] Update
src/content/contributing/adding-wallet/index.md
Co-authored-by: Luka Kropec <37338979+lukassim@users.noreply.github.com>
---
src/content/contributing/adding-wallet/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
index 8f017d8aba0..b60af24a255 100644
--- a/src/content/contributing/adding-wallet/index.md
+++ b/src/content/contributing/adding-wallet/index.md
@@ -41,7 +41,7 @@ Wallets are rapidly changing in Ethereum. We've tried to create a fair framework
- **Staking** - users are able to stake directly through the wallet.
- **Swaps** - users are able to swap tokens through the wallet.
- **Multichain networks** - your wallet supports users accessing multiple blockchain networks by default.
-- **Customize gas fees** - your wallet allows users to customize their transaction gas fees (base fee, priority fee, max fee)
+- **Customize gas fees** - your wallet allows users to customize their transaction gas fees (base fee, priority fee, max fee).
- **ENS support** - your wallet allows users to send transactions to ENS names.
- **ERC-20 support** - your wallet allows users to import ERC-20 token contracts, or automatically queries and displays ERC-20 tokens.
- **EIP-1559 (type 2) transactions** - your wallet supports EIP-1559 (type 2) transactions.
From 3e4d71972e2c0641fd68e04239a78a39a160a37f Mon Sep 17 00:00:00 2001
From: Corwin Smith
Date: Tue, 14 Jun 2022 00:02:41 -0600
Subject: [PATCH 079/244] Update
src/content/contributing/adding-wallet/index.md
Co-authored-by: Luka Kropec <37338979+lukassim@users.noreply.github.com>
---
src/content/contributing/adding-wallet/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/contributing/adding-wallet/index.md b/src/content/contributing/adding-wallet/index.md
index b60af24a255..58ab24bdcac 100644
--- a/src/content/contributing/adding-wallet/index.md
+++ b/src/content/contributing/adding-wallet/index.md
@@ -21,7 +21,7 @@ Wallets are rapidly changing in Ethereum. We've tried to create a fair framework
### Criteria for inclusion: the must-haves {#the-must-haves}
-- **A security-tested product** - whether through audit, an internal security team, open sourced coded, or some other method, your wallets security must be reliable. This reduces the risk to our users and shows us that you take security seriously.
+- **A security-tested product** - whether through audit, an internal security team, open sourced coded, or some other method, your wallet's security must be reliable. This reduces the risk to our users and shows us that you take security seriously.
- **A wallet that has been “live” for over 6 months OR released by a group with a reputable track record** - this is another indication of security. 6 months is a good time frame for critical bugs and exploitations to have been found. We ask 6 months to help filter out forks that are quickly abandoned as projects.
- **Worked on by an active team** - this helps to ensure quality and that a user will get support for their queries.
- **Honest and accurate listing information** - it is expected that any suggested listings from projects come with honest and accurate information. Products that falsify listing information, such as declaring your product is “open source” when it is not, will be removed.
From 101d600ba562fe945aa8ac275d4e7aeb9572b374 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Tue, 14 Jun 2022 09:21:37 +0100
Subject: [PATCH 080/244] Apply suggestions from code review
---
src/content/foundation/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/content/foundation/index.md b/src/content/foundation/index.md
index 870cbee6126..b9972bf331c 100644
--- a/src/content/foundation/index.md
+++ b/src/content/foundation/index.md
@@ -31,9 +31,9 @@ Learn more at [devcon.org](https://devcon.org/), check out the [Devcon Blog](htt
### Fellowship Program {#fellowship-program}
-The [Ethereum Foundation Fellowship Program](https://fellowship.ethereum.foundation/) is an initiative to help address gaps in representation across cultures, nationalities, and economic classes. The Fellowship Program is about bridging these gaps by identifying and supporting unique and talented individuals helping to enable Ethereum’s relevance and breaking down barriers to entry for those underrepresented people and communities who will become the future of web3.
+The [Ethereum Foundation Fellowship Program](https://fellowship.ethereum.foundation/) is an initiative to help address gaps in representation across cultures, nationalities, and economic classes. The Fellowship Program is about bridging these gaps by identifying and supporting unique and talented individuals helping to enable Ethereum’s relevance, and breaking down barriers to entry for those underrepresented people and communities who will become the future of Web3.
-Learn more at [fellowship.ethereum.foundation](https://fellowship.ethereum.foundation/).
+[Learn more at fellowship.ethereum.foundation](https://fellowship.ethereum.foundation/).
From 2ca3d0e8219e3ec65a740d5a04be0a6d73219416 Mon Sep 17 00:00:00 2001
From: "allcontributors[bot]"
<46447321+allcontributors[bot]@users.noreply.github.com>
Date: Tue, 14 Jun 2022 08:22:28 +0000
Subject: [PATCH 081/244] docs: update README.md [skip ci]
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 4dc2c6dc7ee..d9f86921dc6 100644
--- a/README.md
+++ b/README.md
@@ -446,7 +446,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
From 536dc1c776acad7bfc4e08b5a1ecbcd128826179 Mon Sep 17 00:00:00 2001
From: "allcontributors[bot]"
<46447321+allcontributors[bot]@users.noreply.github.com>
Date: Tue, 14 Jun 2022 08:25:24 +0000
Subject: [PATCH 085/244] docs: update .all-contributorsrc [skip ci]
---
.all-contributorsrc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/.all-contributorsrc b/.all-contributorsrc
index 36e18be32a8..8f0e41e1989 100644
--- a/.all-contributorsrc
+++ b/.all-contributorsrc
@@ -7811,6 +7811,15 @@
"doc",
"bug"
]
+ },
+ {
+ "login": "ArpitIngle",
+ "name": "Arpit Ingle",
+ "avatar_url": "https://avatars.githubusercontent.com/u/37828045?v=4",
+ "profile": "https://github.com/ArpitIngle",
+ "contributions": [
+ "ideas"
+ ]
}
],
"contributorsPerLine": 7,
From 170bfb45fe2376f73c6a90b8b863c411b34c844c Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Tue, 14 Jun 2022 09:29:19 +0100
Subject: [PATCH 086/244] Apply suggestions from code review
---
src/content/developers/docs/standards/index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/content/developers/docs/standards/index.md b/src/content/developers/docs/standards/index.md
index 31a80715ce7..3c921ed7276 100644
--- a/src/content/developers/docs/standards/index.md
+++ b/src/content/developers/docs/standards/index.md
@@ -29,8 +29,8 @@ Certain EIPs relate to application-level standards (e.g. a standard smart-contra
### Token standards {#token-standards}
-- [ERC-20](/developers/docs/standards/tokens/erc-20/) - A standard interface for fungible (interchangeable) tokens, like voting tokens, staking tokens or virtual currencies. Think of it as a set of rules or functions that a newly created token in the Ethereum network must respect or follow.
-- [ERC-721](/developers/docs/standards/tokens/erc-721/) - A standard interface for non-fungible tokens, like a deed for artwork or a song. Things or assets that use ERC-721 will record and assign the ownership to the account numbers.
+- [ERC-20](/developers/docs/standards/tokens/erc-20/) - A standard interface for fungible (interchangeable) tokens, like voting tokens, staking tokens or virtual currencies.
+- [ERC-721](/developers/docs/standards/tokens/erc-721/) - A standard interface for non-fungible tokens, like a deed for artwork or a song.
- [ERC-777](/developers/docs/standards/tokens/erc-777/) - A token standard improving over ERC-20.
- [ERC-1155](/developers/docs/standards/tokens/erc-1155/) - A token standard which can contain both fungible and non-fungible assets.
- [ERC-4626](/developers/docs/standards/tokens/erc-4626/) - A tokenized vault standard designed to optimize and unify the technical parameters of yield-bearing vaults.
@@ -39,6 +39,6 @@ Learn more about [token standards](/developers/docs/standards/tokens/).
## Further reading {#further-reading}
-- [Ethereum Improvement Proposals (EIPs)](https://ethereum.org/en/eips/)
+- [Ethereum Improvement Proposals (EIPs)](/eips/)
_Know of a community resource that helped you? Edit this page and add it!_
From 84c8bb76ee9e1bb2c61f46f479fd3344909aa43a Mon Sep 17 00:00:00 2001
From: "allcontributors[bot]"
<46447321+allcontributors[bot]@users.noreply.github.com>
Date: Tue, 14 Jun 2022 08:30:08 +0000
Subject: [PATCH 087/244] docs: update README.md [skip ci]
---
README.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/README.md b/README.md
index d7010c4a5aa..5a5d080521c 100644
--- a/README.md
+++ b/README.md
@@ -1260,6 +1260,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
From d9b48a90dbcdcc28198888f140b25d8926a387f9 Mon Sep 17 00:00:00 2001
From: "allcontributors[bot]"
<46447321+allcontributors[bot]@users.noreply.github.com>
Date: Tue, 14 Jun 2022 08:31:54 +0000
Subject: [PATCH 090/244] docs: update .all-contributorsrc [skip ci]
---
.all-contributorsrc | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/.all-contributorsrc b/.all-contributorsrc
index 71d88f72d5f..d07542085e7 100644
--- a/.all-contributorsrc
+++ b/.all-contributorsrc
@@ -7830,6 +7830,16 @@
"doc",
"ideas"
]
+ },
+ {
+ "login": "jonasbostoen",
+ "name": "mempirate",
+ "avatar_url": "https://avatars.githubusercontent.com/u/32879610?v=4",
+ "profile": "https://netbound.io",
+ "contributions": [
+ "doc",
+ "bug"
+ ]
}
],
"contributorsPerLine": 7,
From f89cfedd923830b64ac844b44a329350c28fcad6 Mon Sep 17 00:00:00 2001
From: Joshua <30259508@cityofglacol.ac.uk>
Date: Tue, 14 Jun 2022 09:42:26 +0100
Subject: [PATCH 091/244] Fix TurboGeth links
---
.../developers/docs/programming-languages/golang/index.md | 4 ++--
.../de/developers/docs/nodes-and-clients/index.md | 2 +-
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../fa/developers/docs/nodes-and-clients/index.md | 2 +-
.../fr/developers/docs/nodes-and-clients/index.md | 2 +-
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../id/developers/docs/nodes-and-clients/index.md | 2 +-
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../it/developers/docs/nodes-and-clients/index.md | 2 +-
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../ro/developers/docs/nodes-and-clients/index.md | 2 +-
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../tr/developers/docs/nodes-and-clients/index.md | 2 +-
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
.../developers/docs/programming-languages/golang/index.md | 8 ++++----
18 files changed, 49 insertions(+), 49 deletions(-)
diff --git a/src/content/developers/docs/programming-languages/golang/index.md b/src/content/developers/docs/programming-languages/golang/index.md
index 645788dff34..e4a456d2401 100644
--- a/src/content/developers/docs/programming-languages/golang/index.md
+++ b/src/content/developers/docs/programming-languages/golang/index.md
@@ -35,8 +35,8 @@ Need a more basic primer first? Check out [ethereum.org/learn](/learn/) or [ethe
- [Go Ethereum Documentation](https://geth.ethereum.org/docs/) - _The documentation for the official Ethereum Golang_
- [Erigon Programmer's Guide](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _Illustrated guide including the state tree, multi-proofs, and transaction processing_
-- [Turbo-Geth and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Community Conference (EthCC 3)_
-- [Turbo-Geth: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Erigon and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Community Conference (EthCC 3)_
+- [Erigon: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Creating a Dapp in Go with Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Work with Ethereum Private Network with Golang and Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
diff --git a/src/content/translations/de/developers/docs/nodes-and-clients/index.md b/src/content/translations/de/developers/docs/nodes-and-clients/index.md
index 5e8a1cd0107..064bc692c0e 100644
--- a/src/content/translations/de/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/de/developers/docs/nodes-and-clients/index.md
@@ -162,7 +162,7 @@ Hyperledger Besu ist ein unternehmensorientierter Ethereum-Client für öffentli
#### Erigon {#erigon}
-Erigon, früher bekannt als Turbo-Geth, ist eine Abspaltung von Go Ethereum, die auf Geschwindigkeit und Speicherplatzeffizienz ausgerichtet ist. Erigon ist eine komplett neu entwickelte Implementierung von Ethereum, die derzeit in Go geschrieben ist, aber auch in anderen Sprachen implementiert werden soll. Das Ziel von Erigon ist es, eine schnellere, modularere und optimierte Implementierung von Ethereum anzubieten. Es kann eine vollständige Synchronisierung des Archiv-Nodes mit weniger als 2 Tb Speicherplatz in weniger als 3 Tagen durchführen
+Erigon, früher bekannt als Erigon, ist eine Abspaltung von Go Ethereum, die auf Geschwindigkeit und Speicherplatzeffizienz ausgerichtet ist. Erigon ist eine komplett neu entwickelte Implementierung von Ethereum, die derzeit in Go geschrieben ist, aber auch in anderen Sprachen implementiert werden soll. Das Ziel von Erigon ist es, eine schnellere, modularere und optimierte Implementierung von Ethereum anzubieten. Es kann eine vollständige Synchronisierung des Archiv-Nodes mit weniger als 2 Tb Speicherplatz in weniger als 3 Tagen durchführen
### Synchronisationsmodi {#sync-modes}
diff --git a/src/content/translations/es/developers/docs/programming-languages/golang/index.md b/src/content/translations/es/developers/docs/programming-languages/golang/index.md
index f2dbfdbfae2..8cd37be2d65 100644
--- a/src/content/translations/es/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/es/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Usa Ethereum para crear aplicaciones descentralizadas (o "dapps"). Estas dapps p
## Artículos y documentos de nivel intermedio {#intermediate-articles-and-docs}
- [Documentación Ethereum de Go](https://geth.ethereum.org/docs/): _La documentación oficial para Ethereum Golang_
-- [Guía del Programador Turbo-Geth](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md): _Guía ilustrada que incluye el árbol de estado, multi-pruebas y procesamiento de transacciones_
-- [Turbo-Geth and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394): _Conferencia de la Comunidad Ethereum (EthCC 3)_
-- [Turbo-Geth: Optimizando clientes de Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _Devcon 2018 4_
+- [Guía del Programador Erigon](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md): _Guía ilustrada que incluye el árbol de estado, multi-pruebas y procesamiento de transacciones_
+- [Erigon and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394): _Conferencia de la Comunidad Ethereum (EthCC 3)_
+- [Erigon: Optimizando clientes de Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _Devcon 2018 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Crear una dapp en Go con Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Trabajar con la red privada Ethereum con Golang y Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Usa Ethereum para crear aplicaciones descentralizadas (o "dapps"). Estas dapps p
- [Geth/Go Ethereum](https://github.com/ethereum/go-ethereum): _Implementación oficial en Go del protocolo Ethereum_
- [Análisis de código Go de Ethereum](https://github.com/ZtesoftCS/go-ethereum-code-analysis): _Revisión y análisis del código fuente de Go para Ethereum_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth)_: Derivada más rápida de Go Ethereum_
+- [Erigon](https://github.com/ledgerwatch/erigon)_: Derivada más rápida de Go Ethereum_
- [Golem](https://github.com/golemfactory/golem): _Golem está creando un mercado global orientado al poder de la informática_
- [Quorum](https://github.com/jpmorganchase/quorum): _Una implementación autorizada de Ethereum compatible con la privacidad de datos_
- [Prysm](https://github.com/prysmaticlabs/prysm): _Implementación de Go de Ethereum 'Serenity' 2.0_
diff --git a/src/content/translations/fa/developers/docs/nodes-and-clients/index.md b/src/content/translations/fa/developers/docs/nodes-and-clients/index.md
index d094746089f..f9a302ea1c6 100644
--- a/src/content/translations/fa/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/fa/developers/docs/nodes-and-clients/index.md
@@ -162,7 +162,7 @@ Nethermind همچنین [اسناد با جزییات](https://docs.nethermind.i
#### Erigon {#erigon}
-Erigon که قبلاً به عنوان Turbo-Geth شناخته میشد، یک فورک Go Ethereum است که هدفش سرعت و کارایی فضای دیسک است. Erigon یک پیادهسازی کاملاً بازسازی شده از Ethereum است که در حال حاضر به زبان Go نوشته شده است، اما پیادهسازی آن به زبانهای دیگر برنامهریزی شده است. هدف Erigon ارائهی پیادهسازی سریعتر، ماژولارتر و بهینهتر اتریوم است. این کلاینت میتواند با بکارگیری کمتر از 2 ترابایت فضای دیسک، در کمتر از 3 روز، همگامسازی گرهی آرشیو کامل را انجام دهد
+Erigon که قبلاً به عنوان Erigon شناخته میشد، یک فورک Go Ethereum است که هدفش سرعت و کارایی فضای دیسک است. Erigon یک پیادهسازی کاملاً بازسازی شده از Ethereum است که در حال حاضر به زبان Go نوشته شده است، اما پیادهسازی آن به زبانهای دیگر برنامهریزی شده است. هدف Erigon ارائهی پیادهسازی سریعتر، ماژولارتر و بهینهتر اتریوم است. این کلاینت میتواند با بکارگیری کمتر از 2 ترابایت فضای دیسک، در کمتر از 3 روز، همگامسازی گرهی آرشیو کامل را انجام دهد
### حالات همگامسازی {#sync-modes}
diff --git a/src/content/translations/fr/developers/docs/nodes-and-clients/index.md b/src/content/translations/fr/developers/docs/nodes-and-clients/index.md
index f5218556289..74973b4cc3b 100644
--- a/src/content/translations/fr/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/fr/developers/docs/nodes-and-clients/index.md
@@ -162,7 +162,7 @@ Hyperledger Besu est un client Ethereum de niveau entreprise pour les réseaux p
#### Erigon {#erigon}
-Erigon, anciennement connu sous le nom de Turbo-Geth, est une fourche de Go Ethereum axée sur la vitesse et l'efficacité de l'espace disque. Erigon est une implémentation entièrement repensée d'Ethereum, actuellement écrite en Go mais pour laquelle des implémentations dans d'autres langages sont prévues. L'objectif d'Erigon est de fournir une implémentation plus rapide, plus modulaire et plus optimisée d'Ethereum. Il peut effectuer une synchronisation complète des nœuds d'archive en utilisant moins de 2 To d'espace disque, et ce en moins de 3 jours.
+Erigon, anciennement connu sous le nom de Erigon, est une fourche de Go Ethereum axée sur la vitesse et l'efficacité de l'espace disque. Erigon est une implémentation entièrement repensée d'Ethereum, actuellement écrite en Go mais pour laquelle des implémentations dans d'autres langages sont prévues. L'objectif d'Erigon est de fournir une implémentation plus rapide, plus modulaire et plus optimisée d'Ethereum. Il peut effectuer une synchronisation complète des nœuds d'archive en utilisant moins de 2 To d'espace disque, et ce en moins de 3 jours.
### Modes de synchronisation {#sync-modes}
diff --git a/src/content/translations/fr/developers/docs/programming-languages/golang/index.md b/src/content/translations/fr/developers/docs/programming-languages/golang/index.md
index 3337e1eadd1..d0a2727edf3 100644
--- a/src/content/translations/fr/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/fr/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Besoin d’une approche plus élémentaire ? Consultez [ethereum.org/learn](/le
## Articles et documentation de niveau intermédiaire {#intermediate-articles-and-docs}
- [Documentation Go Ethereum](https://geth.ethereum.org/docs/) - _Documentation Ethereum officielle pour Go_
-- [Guide du programmeur Turbo-Geth](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _Guide illustré incluant l'arborescence d'état, les multipreuves et le traitement des transactions_
-- [Turbo-Geth et Ethereum sans état](https://youtu.be/3-Mn7OckSus?t=394) - _Conférence de la communauté Ethereum 2020 (EthCC 3)_
-- [Turbo-Geth: optimiser les clients Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _Devcon 4 - 2018 _
+- [Guide du programmeur Erigon](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _Guide illustré incluant l'arborescence d'état, les multipreuves et le traitement des transactions_
+- [Erigon et Ethereum sans état](https://youtu.be/3-Mn7OckSus?t=394) - _Conférence de la communauté Ethereum 2020 (EthCC 3)_
+- [Erigon: optimiser les clients Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _Devcon 4 - 2018 _
- [GoDoc Go Ethereum](https://godoc.org/github.com/ethereum/go-ethereum)
- [Créer un dApp avec Geth dans Go](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Travailler avec le réseau privé Ethereum avec Golang et Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Besoin d’une approche plus élémentaire ? Consultez [ethereum.org/learn](/le
- [Geth/Go Ethereum](https://github.com/ethereum/go-ethereum) - _Implémentation officielle du protocole Ethereum_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Revue et analyse du code source Go Ethereum_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _Dérivé plus rapide de Go Thereum_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _Dérivé plus rapide de Go Thereum_
- [Golem](https://github.com/golemfactory/golem) - _Golem crée un marché mondial de distribution de puissance informatique_
- [Quorum](https://github.com/jpmorganchase/quorum) - _Implémentation d'Ethereum soumise à droit d'accès, prenant en charge la confidentialité des données_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Implémentation d'Ethereum « Serenity » 2.0 Go _
diff --git a/src/content/translations/hu/developers/docs/programming-languages/golang/index.md b/src/content/translations/hu/developers/docs/programming-languages/golang/index.md
index f8c279ee5ab..635e615477d 100644
--- a/src/content/translations/hu/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/hu/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Szükséged van egy méginkább kezdőknek szóló alapozóra? Tekintsd meg az [
## Haladó cikkek és dokumentációk {#intermediate-articles-and-docs}
- [Go Ethereum Documentation](https://geth.ethereum.org/docs/) - _A hivatalos Ethereum Golang dokumentáció_
-- [Turbo-Geth Programmer's Guide](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _Illusztrált útmutató, mely bemutatja az állapot fát, többszöri bizonyítékokat és a tranzakció feldolgozást_
-- [Turbo-Geth és az állapot nélküli Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Közösségi Konferenica (EthCC 3)_
-- [Turbo-Geth: Ethereum kliensek optimalizálása](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Erigon Programmer's Guide](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _Illusztrált útmutató, mely bemutatja az állapot fát, többszöri bizonyítékokat és a tranzakció feldolgozást_
+- [Erigon és az állapot nélküli Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Közösségi Konferenica (EthCC 3)_
+- [Erigon: Ethereum kliensek optimalizálása](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Egy dapp készítése Go-ban Geth-tel](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Munka Ethereum Privát Hálózaton Golang-gel és Geth-tel](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Szükséged van egy méginkább kezdőknek szóló alapozóra? Tekintsd meg az [
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _Az Ethereum protokoll hivatalos Go implementációja_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Go Ethereum forráskód áttekintése és elemzése_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _A Go Ethereum gyorsabb származéka_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _A Go Ethereum gyorsabb származéka_
- [Golem](https://github.com/golemfactory/golem) - _A Golem egy globális piacot teremt a számítási teljesítmény számára_
- [Quorum](https://github.com/jpmorganchase/quorum) - _Egy engedélyköteles Ethereum implementáció, mely támogatja az adatvédelmet_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Ethereum 'Serenity' 2.0 Go implementáció_
diff --git a/src/content/translations/id/developers/docs/nodes-and-clients/index.md b/src/content/translations/id/developers/docs/nodes-and-clients/index.md
index e38f8ecefba..d966f896369 100644
--- a/src/content/translations/id/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/id/developers/docs/nodes-and-clients/index.md
@@ -160,7 +160,7 @@ Hyperledger Besu adalah klien Ethereum standar perusahaan untuk jaringan publik
#### Erigon {#erigon}
-Erigon, yang sebelumnya dikenal sebagai Turbo-Geth, adalah sebuah fork Go Ethereum yang diarahkan untuk efisiensi kecepatan dan pemakaian ruangan cakram. Erigon adalah sebuah implementasi yang sepenuhnya di buat kembali di Ethereum, yang saat ini ditulis dalam Go dengan implementasi dalam bahasa pemograman lain yang direncanakan. Tujuan Erigon adalah menyediakan implementasi Ethereum yang lebih cepat, lebih modular, dan lebih teroptimisasi. Ia dapat melakukan sinkronisasi node arsip penuh dengan menggunakan kurang dari 2 TB ruangan cakram, dalam waktu kurang dari 3 hari
+Erigon, yang sebelumnya dikenal sebagai Erigon, adalah sebuah fork Go Ethereum yang diarahkan untuk efisiensi kecepatan dan pemakaian ruangan cakram. Erigon adalah sebuah implementasi yang sepenuhnya di buat kembali di Ethereum, yang saat ini ditulis dalam Go dengan implementasi dalam bahasa pemograman lain yang direncanakan. Tujuan Erigon adalah menyediakan implementasi Ethereum yang lebih cepat, lebih modular, dan lebih teroptimisasi. Ia dapat melakukan sinkronisasi node arsip penuh dengan menggunakan kurang dari 2 TB ruangan cakram, dalam waktu kurang dari 3 hari
### Mode sinkronisasi {#sync-modes}
diff --git a/src/content/translations/id/developers/docs/programming-languages/golang/index.md b/src/content/translations/id/developers/docs/programming-languages/golang/index.md
index 97af2f585b0..e41ee390308 100644
--- a/src/content/translations/id/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/id/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Perlu penjelasan yang lebih mendasar? Kunjungi [ethereum.org/learn](/learn/) ata
## Artikel dan dokumen tingkat menengah {#intermediate-articles-and-docs}
- [Dokumentasi Go Ethereum](https://geth.ethereum.org/docs/) - _Dokumentasi untuk Golang Ethereum resmi_
-- [Panduan Programmer Turbo-Geth](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _Panduan bergambar yang mencakup pohon state, multibukti, dan pemrosesan transaksi_
-- [Turbo-Geth dan Ethereum Tanpa State](https://youtu.be/3-Mn7OckSus?t=394) - _Konferensi Komunitas Ethereum 2020 (EthCC 3)_
-- [Turbo-Geth: mengoptimalkan klien Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _Devcon 4 2018_
+- [Panduan Programmer Erigon](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _Panduan bergambar yang mencakup pohon state, multibukti, dan pemrosesan transaksi_
+- [Erigon dan Ethereum Tanpa State](https://youtu.be/3-Mn7OckSus?t=394) - _Konferensi Komunitas Ethereum 2020 (EthCC 3)_
+- [Erigon: mengoptimalkan klien Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _Devcon 4 2018_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Membuat Dapp dalam Go dengan Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Bekerja dengan Jaringan Privat Ethereum dengan Golang dan Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Perlu penjelasan yang lebih mendasar? Kunjungi [ethereum.org/learn](/learn/) ata
- [Geth/Go Ethereum](https://github.com/ethereum/go-ethereum) - _Implementasi Go resmi untuk protokol Ethereum_
- [Analisis Kode Go Ethereum](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Ulasan dan analisa kode sumber Go Ethereum_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _Turunan Go Ethereum yang lebih cepat_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _Turunan Go Ethereum yang lebih cepat_
- [Golem](https://github.com/golemfactory/golem) - _Golem sedang menciptakan pasar global untuk daya komputasi_
- [Quorum](https://github.com/jpmorganchase/quorum) - _Sebuah implementasi Ethereum berizin yang mendukung privasi data_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Implementasi Go 'Serenity' 2.0 Ethereum_
diff --git a/src/content/translations/it/developers/docs/nodes-and-clients/index.md b/src/content/translations/it/developers/docs/nodes-and-clients/index.md
index 0ee59603b9e..274e7e6f437 100644
--- a/src/content/translations/it/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/it/developers/docs/nodes-and-clients/index.md
@@ -154,7 +154,7 @@ Hyperledger Besu è un client Ethereum di livello enterprise per reti pubbliche
#### Erigon {#erigon}
-Erigon, precedentemente noto come Turbo-Geth, è una diramazione di Go Ethereum orientata alla velocità e all'efficienza dello spazio su disco. Erigon è un'implementazione completamente riprogettata di Ethereum, correntemente scritta in Go ma con implementazioni pianificate in altri linguaggi. L'obiettivo di Erigon è fornire un'implementazione più veloce, modulare e ottimizzata di Ethereum. Può eseguire una sincronizzazione completa del nodo d'archivio usando meno di 2TB di spazio su disco, in meno di 3 giorni.
+Erigon, precedentemente noto come Erigon, è una diramazione di Go Ethereum orientata alla velocità e all'efficienza dello spazio su disco. Erigon è un'implementazione completamente riprogettata di Ethereum, correntemente scritta in Go ma con implementazioni pianificate in altri linguaggi. L'obiettivo di Erigon è fornire un'implementazione più veloce, modulare e ottimizzata di Ethereum. Può eseguire una sincronizzazione completa del nodo d'archivio usando meno di 2TB di spazio su disco, in meno di 3 giorni.
### Modalità di sincronizzazione {#sync-modes}
diff --git a/src/content/translations/it/developers/docs/programming-languages/golang/index.md b/src/content/translations/it/developers/docs/programming-languages/golang/index.md
index 9987373ac0a..5dbee30f13c 100644
--- a/src/content/translations/it/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/it/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Hai prima bisogno di nozioni di base? Dai un'occhiata a [ethereum.org/learn](/le
## Articoli e documentazione di livello intermedio {#intermediate-articles-and-docs}
- [Go Ethereum Documentation](https://geth.ethereum.org/docs/) - _La documentazione per il Golang ufficiale di Ethereum_
-- [Turbo-Geth Programmer's Guide](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _ Guida illustrata che tratta gli alberi di stato, prove multiple ed elaborazioni delle transazioni_
-- [Turbo-Geth and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _Conferenza della Community di Ethereum 2020 (EthCC 3)_
-- [Turbo-Geth: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Erigon Programmer's Guide](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _ Guida illustrata che tratta gli alberi di stato, prove multiple ed elaborazioni delle transazioni_
+- [Erigon and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _Conferenza della Community di Ethereum 2020 (EthCC 3)_
+- [Erigon: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Creating a Dapp in Go with Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Work with Ethereum Private Network with Golang and Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Hai prima bisogno di nozioni di base? Dai un'occhiata a [ethereum.org/learn](/le
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _Implementazione ufficiale di Go del protocollo di Ethereum_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Controllo e analisi del codice sorgente di Go Ethereum_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _Il più veloce derivato di Go Ethereum_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _Il più veloce derivato di Go Ethereum_
- [Golem](https://github.com/golemfactory/golem) - _Golem sta creando un mercato globale per la potenza di calcolo_
- [Quorum](https://github.com/jpmorganchase/quorum) - _Implementazione con permessi di Ethereum a supporto della privacy dei dati_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Implementazione Go di 'Serenity' 2.0 per Ethereum_
diff --git a/src/content/translations/pl/developers/docs/programming-languages/golang/index.md b/src/content/translations/pl/developers/docs/programming-languages/golang/index.md
index ef2bd043160..361a73122f7 100644
--- a/src/content/translations/pl/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/pl/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Potrzebujesz bardziej podstawowych informacji? Sprawdź na stronach [ethereum.or
## Artykuły dla średniozaawansowanych {#intermediate-articles-and-docs}
- [Go Ethereum Documentation](https://geth.ethereum.org/docs/) — dokumentacja oficjalnego Golang Ethereum
-- [Turbo-Geth Programmer's Guide](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) — ilustrowany przewodnik uwzględniający drzewo stanowe, wiele dowodów i przetwarzanie transakcji
-- [TTurbo-Geth and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) — _Konferencja Społeczności Ethereum 2020 (EthCC 3)_
-- [TTurbo-Geth: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) — _2018 Devcon 4_
+- [Erigon Programmer's Guide](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) — ilustrowany przewodnik uwzględniający drzewo stanowe, wiele dowodów i przetwarzanie transakcji
+- [Turbo-Geth and Stateless Ethereum](https://youtu.be/3-Mn7OckSus?t=394) — _Konferencja Społeczności Ethereum 2020 (EthCC 3)_
+- [Turbo-Geth: optimising Ethereum clients](https://www.youtube.com/watch?v=CSpc1vZQW2Q) — _2018 Devcon 4_
- [Go Ethereum — dokumentacja Go](https://godoc.org/github.com/ethereum/go-ethereum)
- [Tworzenie aplikacji zdecentralizowanych w Go z użyciem Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Praca z prywatną siecią Ethereum z Golang i Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Potrzebujesz bardziej podstawowych informacji? Sprawdź na stronach [ethereum.or
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) — oficjalna implementacja protokołu Ethereum
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) — przegląd i analiza kodu źródłowego Go Ethereum
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) — szybsza pochodna Go Ethereum
+- [Erigon](https://github.com/ledgerwatch/erigon) — szybsza pochodna Go Ethereum
- [Golem](https://github.com/golemfactory/golem) — _Golem tworzy globalny rynek mocy obliczeniowej_
- [Quorum](https://github.com/jpmorganchase/quorum) — uprawniona implementacja Ethereum wspierająca prywatność danych
- Prysm — implementacja Ethereum „Serenity” 2.0 przy użyciu Go
diff --git a/src/content/translations/pt-br/developers/docs/programming-languages/golang/index.md b/src/content/translations/pt-br/developers/docs/programming-languages/golang/index.md
index f54e62c2094..718b02cfaf3 100644
--- a/src/content/translations/pt-br/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/pt-br/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Precisa de uma introdução geral? Confira [ethereum.org/learn](/learn/) ou [eth
## Artigos e documentos de nível Intermediário {#intermediate-articles-and-docs}
- [Documentação Ethereum em Go](https://geth.ethereum.org/docs/) - _A documentação da implementação oficial da Ethereum em Go_
-- [Guia do Programador Turbo-Geth](https://github. com/ledgerwatch/turbo-geth/blob/master/docs/programmers*guide/guide. md) - \_Guia ilustrado, incluindo a árvore de estado, múltiplas provas e processamento de transações*
-- [Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _Conferência Comunitária da Ethereum da Turbo-Geth e sem estado, (EthCC 3)_
-- [Turbo-Geth: otimização de clientes Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Guia do Programador Erigon](https://github. com/ledgerwatch/erigon/blob/devel/docs/programmers*guide/guide. md) - \_Guia ilustrado, incluindo a árvore de estado, múltiplas provas e processamento de transações*
+- [Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _Conferência Comunitária da Ethereum da Erigon e sem estado, (EthCC 3)_
+- [Erigon: otimização de clientes Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Criando um Dapp Go com o Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Trabalhe com uma rede privada Ethereum com Golang e Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Precisa de uma introdução geral? Confira [ethereum.org/learn](/learn/) ou [eth
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _Implementação Oficial do protocolo da Ethereum_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Revisão e analise do código-fonte do Go Ethereum_
-- [Turbo-Geth](https://github. com/ledgerwatch/turbo-geth) - _Mais rápido derivado da Go Ethereum_
+- [Erigon](https://github. com/ledgerwatch/turbo-geth) - _Mais rápido derivado da Go Ethereum_
- [Golem](https://github.com/golemfactory/golem) - _Golem está criando um mercado global para computação distribuída_
- [Quorum](https://github.com/jpmorganchase/quorum) - _Uma implementação permissionada da Ethereum com suporte a privacidade de dados_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Implementação em Go da Ethereum 'Serenity' 2.0_
diff --git a/src/content/translations/ro/developers/docs/nodes-and-clients/index.md b/src/content/translations/ro/developers/docs/nodes-and-clients/index.md
index 25cccf6e34b..31a6fceafca 100644
--- a/src/content/translations/ro/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/ro/developers/docs/nodes-and-clients/index.md
@@ -162,7 +162,7 @@ Hyperledger Besu este un client Ethereum de nivel de întreprindere pentru rețe
#### Erigon {#erigon}
-Erigon, cunoscut anterior sub denumirea de Turbo-Geth, este un fork Go Ethereum ce vizează creşterea vitezei şi a eficienţei spaţiului pe disc. Erigon este o implementare complet reproiectată a lui Ethereum, actualmente scrisă în Go, dar care urmează să fie implementată și în alte limbaje. Scopul Erigon este de a oferi o implementare mai rapidă, mai modulară și mai optimizată a lui Ethereum. It can perform a full archive node sync using less than 2TB of disk space, in under 3 days
+Erigon, cunoscut anterior sub denumirea de Erigon, este un fork Go Ethereum ce vizează creşterea vitezei şi a eficienţei spaţiului pe disc. Erigon este o implementare complet reproiectată a lui Ethereum, actualmente scrisă în Go, dar care urmează să fie implementată și în alte limbaje. Scopul Erigon este de a oferi o implementare mai rapidă, mai modulară și mai optimizată a lui Ethereum. It can perform a full archive node sync using less than 2TB of disk space, in under 3 days
### Moduri de sincronizare {#sync-modes}
diff --git a/src/content/translations/ro/developers/docs/programming-languages/golang/index.md b/src/content/translations/ro/developers/docs/programming-languages/golang/index.md
index 5a0d80909d4..d8427434a41 100644
--- a/src/content/translations/ro/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/ro/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Aveţi nevoie de o scurtă introducere? Accesaţi [ethereum.org/learn](/learn/)
## Articole și documentații de nivel intermediar {#intermediate-articles-and-docs}
- [Documentație Go Ethereum](https://geth.ethereum.org/docs/) - _Documentația oficială pentru Ethereum Golang_
-- [Ghidul programatorului Turbo-Geth](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) – _Ghid ilustrat ce cuprinde arborele de stare, dovezile multiple și procesarea tranzacțiilor_
-- [Turbo-Geth și Ethereum fără stare](https://youtu.be/3-Mn7OckSus?t=394) - _Conferința comunitară Ethereum din 2020 (EthCC 3)_
-- [Turbo-Geth: optimizarea clienților Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Ghidul programatorului Erigon](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) – _Ghid ilustrat ce cuprinde arborele de stare, dovezile multiple și procesarea tranzacțiilor_
+- [Erigon și Ethereum fără stare](https://youtu.be/3-Mn7OckSus?t=394) - _Conferința comunitară Ethereum din 2020 (EthCC 3)_
+- [Erigon: optimizarea clienților Ethereum](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Crearea unei aplicații descentralizate în Go cu Geth](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Utilizarea unei rețele private Ethereum cu Golang și Geth](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Aveţi nevoie de o scurtă introducere? Accesaţi [ethereum.org/learn](/learn/)
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _Implementarea oficială Go a protocolului Ethereum_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Evaluarea și analiza codului sursă Go Ethereum_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _Derivat mai rapid al Go Ethereum_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _Derivat mai rapid al Go Ethereum_
- [Golem](https://github.com/golemfactory/golem) - _Golem construiește o piață globală pentru puterea de calcul_
- [Quorum](https://github.com/jpmorganchase/quorum) - _O implementare Ethereum cu sistem de permisiuni și suport pentru confidențialitatea datelor_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _Implementare Go Ethereum „Serenity” 2.0_
diff --git a/src/content/translations/tr/developers/docs/nodes-and-clients/index.md b/src/content/translations/tr/developers/docs/nodes-and-clients/index.md
index acf57a894c4..474e1b93e30 100644
--- a/src/content/translations/tr/developers/docs/nodes-and-clients/index.md
+++ b/src/content/translations/tr/developers/docs/nodes-and-clients/index.md
@@ -162,7 +162,7 @@ Hyperledger Besu, genel ve izin verilen ağlar için kurumsal düzeyde bir Ether
#### Erigon {#erigon}
-Eskiden Turbo-Geth olarak bilinen Erigon, hız ve disk alanı verimliliğine yönelik bir Go Ethereum çatalıdır. Erigon, şu anda Go'da yazılmış, ancak diğer dillerde uygulanması planlanan Ethereum'un tamamen yeniden tasarlanmış bir uygulamasıdır. Erigon'un amacı, Ethereum'un daha hızlı, daha modüler ve daha optimize edilmiş bir uygulamasını sağlamaktır. 3 günden kısa bir sürede 2 Tb'den daha az disk alanı kullanarak tam bir arşiv düğümü senkronizasyonu gerçekleştirebilir
+Eskiden Erigon olarak bilinen Erigon, hız ve disk alanı verimliliğine yönelik bir Go Ethereum çatalıdır. Erigon, şu anda Go'da yazılmış, ancak diğer dillerde uygulanması planlanan Ethereum'un tamamen yeniden tasarlanmış bir uygulamasıdır. Erigon'un amacı, Ethereum'un daha hızlı, daha modüler ve daha optimize edilmiş bir uygulamasını sağlamaktır. 3 günden kısa bir sürede 2 Tb'den daha az disk alanı kullanarak tam bir arşiv düğümü senkronizasyonu gerçekleştirebilir
### Senkronizasyon modları {#sync-modes}
diff --git a/src/content/translations/tr/developers/docs/programming-languages/golang/index.md b/src/content/translations/tr/developers/docs/programming-languages/golang/index.md
index f9b2e588496..b01ac30d38d 100644
--- a/src/content/translations/tr/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/tr/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ Başlamadan önce temel bilgilere mi ihtiyacınız var? [ethereum.org/learn](/le
## Orta Seviye Makaleler ve Belgeler {#intermediate-articles-and-docs}
- [Go Ethereum Belgeleri](https://geth.ethereum.org/docs/) - _Resmi Ethereum Golang belgeleri_
-- [Turbo-Geth Programcı Kılavuzu](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _Durum ağacını, çoklu ispatları ve işlem sürecini içeren resimli bir rehber_
-- [Turbo-Geth ve Durumsuz Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Topluluk Konferansı(EthCC 3)_
-- [Turbo-Geth: Ethereum istemcilerinin optimizasyonu](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Erigon Programcı Kılavuzu](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _Durum ağacını, çoklu ispatları ve işlem sürecini içeren resimli bir rehber_
+- [Erigon ve Durumsuz Ethereum](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Topluluk Konferansı(EthCC 3)_
+- [Erigon: Ethereum istemcilerinin optimizasyonu](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go Ethereum GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [Geth ile Go'da bir Dapp oluşturma](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [Golang ve Geth üzerinden Ethereum Private Network ile çalışın](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ Başlamadan önce temel bilgilere mi ihtiyacınız var? [ethereum.org/learn](/le
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _Ethereum protokolünün resmi Go uygulaması_
- [Go Ethereum Kodu Analizi](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _Go Ethereum kaynak kodunun incelenmesi ve analizi_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _Go Ethereum'un daha hızlı bir türevi_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _Go Ethereum'un daha hızlı bir türevi_
- [Golem](https://github.com/golemfactory/golem) - _Golem, bilgi işlem gücü için küresel bir pazar oluşturuyor_
- [Quorum](https://github.com/jpmorganchase/quorum) - _İzin verilen veri gizliliğini destekleyen Ethereum uygulaması_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _ Ethereum "Serenity" 2.0 Go Uygulaması_
diff --git a/src/content/translations/zh/developers/docs/programming-languages/golang/index.md b/src/content/translations/zh/developers/docs/programming-languages/golang/index.md
index cd340b93371..030b62479c1 100644
--- a/src/content/translations/zh/developers/docs/programming-languages/golang/index.md
+++ b/src/content/translations/zh/developers/docs/programming-languages/golang/index.md
@@ -34,9 +34,9 @@ incomplete: true
## 面向中等程度用户的文章和文档 {#intermediate-articles-and-docs}
- [Go 以太坊相关文档](https://geth.ethereum.org/docs/) - _官方以太坊 Golang 相关文档_
-- [Turbo-Geth 编程者指南](https://github.com/ledgerwatch/turbo-geth/blob/master/docs/programmers_guide/guide.md) - _图文指南,内容涵盖状态树、多重认证和交易处理_
-- [Turbo-Geth 和无状态以太坊](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Community Conference (EthCC 3)_
-- [Turbo-Geth:优化以太坊客户端](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
+- [Erigon 编程者指南](https://github.com/ledgerwatch/erigon/blob/devel/docs/programmers_guide/guide.md) - _图文指南,内容涵盖状态树、多重认证和交易处理_
+- [Erigon 和无状态以太坊](https://youtu.be/3-Mn7OckSus?t=394) - _2020 Ethereum Community Conference (EthCC 3)_
+- [Erigon:优化以太坊客户端](https://www.youtube.com/watch?v=CSpc1vZQW2Q) - _2018 Devcon 4_
- [Go 以太坊 GoDoc](https://godoc.org/github.com/ethereum/go-ethereum)
- [在 Go 上使用 Geth 创建一个去中心化应用程序](https://kauri.io/#collections/A%20Hackathon%20Survival%20Guide/creating-a-dapp-in-go-with-geth/)
- [用 Golang 和 Geth 使用以太坊专用网络](https://myhsts.org/tutorial-learn-how-to-work-with-ethereum-private-network-with-golang-with-geth.php)
@@ -55,7 +55,7 @@ incomplete: true
- [Geth / Go Ethereum](https://github.com/ethereum/go-ethereum) - _以太坊协议的官方 Go 实现_
- [Go Ethereum Code Analysis](https://github.com/ZtesoftCS/go-ethereum-code-analysis) - _审查和分析 Go 以太坊源代码_
-- [Turbo-Geth](https://github.com/ledgerwatch/turbo-geth) - _基于 Go Ethereum 的更快的实现_
+- [Erigon](https://github.com/ledgerwatch/erigon) - _基于 Go Ethereum 的更快的实现_
- [Golem](https://github.com/golemfactory/golem) - _Golem 正在创建一个算力全球市场_
- [Quorum](https://github.com/jpmorganchase/quorum) - _支持数据隐私的许可型以太坊实现_
- [Prysm](https://github.com/prysmaticlabs/prysm) - _以太坊 ‘Serenity’2.0 Go 实现_
From c158c07fe3cb2e66d85e3a294e798a0ba88cb7e7 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Tue, 14 Jun 2022 09:52:12 +0100
Subject: [PATCH 092/244] Apply suggestions from code review
---
.../tutorials/run-light-node-geth/index.md | 18 +++---------------
1 file changed, 3 insertions(+), 15 deletions(-)
diff --git a/src/content/developers/tutorials/run-light-node-geth/index.md b/src/content/developers/tutorials/run-light-node-geth/index.md
index ed4023d6b62..292dbd63db2 100644
--- a/src/content/developers/tutorials/run-light-node-geth/index.md
+++ b/src/content/developers/tutorials/run-light-node-geth/index.md
@@ -9,14 +9,13 @@ sidebar: true
published: 2022-03-04
---
- Please note that Geth light clients can be very slow to find peers. This is because they rely on full-node operators opting-in to be light servers that the light clients can request data from. There are usually only a small number of light servers available.
+**Please note that Geth light clients can be very slow to find peers. This is because they rely on full-node operators volunteering themselves as light servers from which the light clients can request data. There are usually only a small number of light servers available.**
-Also note that after [The Merge]() a Geth node alone will not be sufficient - a consensus client must be connected to it in order to track the head of the chain.
-
+**Also, note that after [The Merge](/upgrades/merge/), a Geth node alone will not be sufficient - a consensus client must be connected to it to track the head of the chain.**
You may be interested in running an [Ethereum node](/developers/docs/nodes-and-clients/). One of the easiest ways to do so is by downloading, installing, and running [Geth](https://geth.ethereum.org). With Geth, we can have a light node up and running in minutes.
-A light client requires less than 400MB of storage whilst still allowing full interactivity with the Ethereum state. Light clients retrieve data from remote peers, so some queries may take longer to respond in comparison to other sync modes.
+A light client requires less than 400MB of storage whilst still allowing full interactivity with the Ethereum state. Light clients retrieve data from remote peers, so some queries may take longer to respond to than other sync modes.
For an explanation of the differences between the different sync modes, read our [nodes and clients developer docs](/developers/docs/nodes-and-clients/#node-types).
@@ -58,17 +57,6 @@ Once enabled, run `curl http://127.0.0.1:8545`. This should report no error.
## To allow remote hosts to connect to your node, launch Geth with the following command:
-title: How to run a light node with Geth
-description: How to download, install and run a lightclient with Geth.
-authors: "Brian Gu"
-tags: ["clients", "geth", "nodes"]
-skill: beginner
-lang: en
-sidebar: true
-published: 2022-03-04
-
----
-
You may be interested in running an [Ethereum node](/developers/docs/nodes-and-clients/). One of the easiest ways to do so is by downloading, installing, and running Geth. With Geth, we can have a light node up and running in minutes.
A light client requires less than 400MB of storage whilst still allowing full interactivity with the Ethereum state. Light clients retrieve data from remote peers, so some queries may take longer to respond in comparison to other sync modes.
From 0f82fe931a28bd950d76f5c54c583acec9c90704 Mon Sep 17 00:00:00 2001
From: Joe
Date: Tue, 14 Jun 2022 09:55:32 +0100
Subject: [PATCH 093/244] add soulbound/QF/PoPP info to DID pg
---
src/content/decentralized-identity/index.md | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/src/content/decentralized-identity/index.md b/src/content/decentralized-identity/index.md
index 63f2021b2c4..2dcaeb77fb5 100644
--- a/src/content/decentralized-identity/index.md
+++ b/src/content/decentralized-identity/index.md
@@ -14,7 +14,7 @@ summaryPoint3: Thanks to crypto, users now have the tools to issue, hold and con
Identity underpins virtually every aspect of your life today. Using online services, opening a bank account, voting in elections, buying property, securing employment—all of these things require proving your identity.
-However, traditional identity management systems have long relied on centralized intermediaries who issue, hold, and control your identifiers and attestations. This means you cannot control your identity-related information, or decide who has access to personally identifiable information (PII) and how much access these parties have.
+However, traditional identity management systems have long relied on centralized intermediaries who issue, hold, and control your identifiers and [attestations](#what-are-attestations). This means you cannot control your identity-related information, or decide who has access to personally identifiable information (PII) and how much access these parties have.
To solve these problems, we have decentralized identity systems built on public blockchains like Ethereum. Decentralized identity allows individuals to manage their identity-related information. With decentralized identity solutions, _you_ can create identifiers and claim and hold your attestations without relying on central authorities, like service providers or governments.
@@ -108,6 +108,10 @@ Here's an example to show how on-chain attestations might work in practice:
3. The smart contract selling shares can check the registry contract for the identities of screened buyers, making it possible for the smart contract to determine who is permitted to buy shares or not.
+### Soulbound tokens and identity
+
+[Soulbound Tokens](https://vitalik.ca/general/2022/01/26/soulbound.html) (non-transferable NFTs) could be used to collect information unique to a specific wallet. This effectively creates a unique on-chain identity bound to a specific Ethereum address that could include tokens representing achievements (e.g. finishing some specific online course or a particular score in a game) or participation in communities.
+
## Benefits of decentralized identity {#benefits-of-decentralized-identity}
1. Decentralized identity increases individual control of identifying information. Decentralized identifiers and attestations can be verified without relying on centralized authorities and third-party services.
@@ -118,6 +122,10 @@ Here's an example to show how on-chain attestations might work in practice:
4. Decentralized identity makes identity data portable. Users store attestations and identifiers in mobile wallet and can share with any party of their choice. Decentralized identifiers and attestations are not locked into the database of the issuing organization.
+5. Decentralized identity should work well with emerging zero-knowledge technologies that will enable individuals to prove they own or have done something without revealing what that thing is. This could become a powerful way to combine trust and privacy for applications such as voting.
+
+6. Decentralized identity enables anti-Sybil mechanisms that can identify when one individual human is pretending to be multiple humans in order to game or spam some system.
+
## Decentralized identity use-cases {#decentralized-identity-use-cases}
Decentralized identity has many potential use-cases:
@@ -140,6 +148,10 @@ Online voting and social media are two novel applications for decentralized iden
Decentralized identity can help create online communities that are free of fake accounts. For example, each user might have to authenticate their identity using an on-chain identity system, like the Ethereum Name Service, reducing the possibility of bots.
+### 4. Anti-Sybil protection
+
+Sybil attacks refer to individual humans tricking a system into thinking they are multiple people in order to increase their influence. [Grant-giving applications](https://gitcoin.co/grants/) that use [quadratic voting](https://www.radicalxchange.org/concepts/plural-voting/) are vulnerable to these Sybil attacks because the value of a grant is increased when more individuals vote for it, incentivizing users to split their contributions across many identities. Decentralized identities help to prevent this by rasing the burden on each participant to prove that they are really human, although often without having to reveal specific private information.
+
## Use decentralized identity {#use-decentralized-identity}
There are many ambitious projects using Ethereum as a foundation for decentralized identity solutions:
@@ -148,6 +160,7 @@ There are many ambitious projects using Ethereum as a foundation for decentraliz
- **[SpruceID](https://www.spruceid.com/)** - _A decentralized identity project which allows users to control digital identity with Ethereum accounts and ENS profiles instead of relying on third-party services._
- **[Proof of Humanity](https://www.proofofhumanity.id)** - _Proof of Humanity (or PoH) is a social identity verification system built on Ethereum._
- **[BrightID](https://www.brightid.org/)** - _A decentralized, open-source social identity network seeking to reform identity verification through the creation and analysis of a social graph._
+- - **[Proof-of-personhood Passport](https://proofofpersonhood.com/)** - _A decentralized digital identity aggregator._
## Further reading {#further-reading}
From b61184fb25e2e69ab2002fd9bbee69d98d8b1f3f Mon Sep 17 00:00:00 2001
From: Joseph Cook <33655003+jmcook1186@users.noreply.github.com>
Date: Tue, 14 Jun 2022 10:15:32 +0100
Subject: [PATCH 094/244] fix accidental ctrl-v
---
.../tutorials/run-light-node-geth/index.md | 92 -------------------
1 file changed, 92 deletions(-)
diff --git a/src/content/developers/tutorials/run-light-node-geth/index.md b/src/content/developers/tutorials/run-light-node-geth/index.md
index 292dbd63db2..93809f4c7e6 100644
--- a/src/content/developers/tutorials/run-light-node-geth/index.md
+++ b/src/content/developers/tutorials/run-light-node-geth/index.md
@@ -55,50 +55,6 @@ Once enabled, run `curl http://127.0.0.1:8545`. This should report no error.
### Allow remote connections {#allow-remote-connections}
-## To allow remote hosts to connect to your node, launch Geth with the following command:
-
-You may be interested in running an [Ethereum node](/developers/docs/nodes-and-clients/). One of the easiest ways to do so is by downloading, installing, and running Geth. With Geth, we can have a light node up and running in minutes.
-
-A light client requires less than 400MB of storage whilst still allowing full interactivity with the Ethereum state. Light clients retrieve data from remote peers, so some queries may take longer to respond in comparison to other sync modes.
-
-For an explanation of the differences between the different sync modes, read our [nodes and clients developer docs](/developers/docs/nodes-and-clients/#node-types).
-
-## Install and run {#install-and-run}
-
-First, [install Geth](https://geth.ethereum.org/docs/install-and-build/installing-geth).
-
-After installing Geth, you can run an Ethereum node in "light" mode by running the following command in a Terminal window:
-
-```bash
-geth --syncmode light
-```
-
-Once launched, Geth will begin connecting to other nodes on Ethereum - known as "peers". The process of connecting to peers may take a while.
-
-When your Geth node has enough peers, it will import headers from new blocks on the chain.
-
-When new block headers no longer have an "age", Geth will be synced to the chain's head.
-
-## Stopping and restarting your node {#stopping-and-restarting-your-node}
-
-You can stop your node at any time by pressing CTRL+C.
-
-When restarting the node, Geth will take a few minutes to download block headers created since the node was last run.
-
-## Enable the HTTP-RPC server {#enable-the-http-rpc-server}
-
-Enabling the HTTP-RPC server lets you connect your Ethereum node to other software like wallets, browser extensions, or custom software libraries.
-
-You can enable the HTTP-RPC server by running the following command when launching Geth:
-
-```bash
-geth --syncmode light --http
-```
-
-Once enabled, run `curl http://127.0.0.1:8545`. This should report no error.
-
-### Allow remote connections {#allow-remote-connections}
-
To allow remote hosts to connect to your node, launch Geth with the following command:
```
@@ -148,51 +104,3 @@ It’s worth emphasizing here that, at the lowest level, this is where the block
- [Learn more about different networks](/developers/docs/networks/).
- [Run a full node](/run-a-node/)
-
-```
-geth --syncmode light --http --http.addr 0.0.0.0
-```
-
-Note: this assumes that there is no process blocking requests to your localhost, such as a firewall.
-
-## Geth JavaScript console {#geth-javascript-console}
-
-Geth has a built-in JavaScript console and a JavaScript API called [web3js](https://github.com/ethereum/web3.js/) that you can use to interact with your node.
-
-To use the JavaScript console run:
-
-```bash
-geth attach
-```
-
-This console allows direct interaction with Ethereum. For example, running the `eth.blockNumber` command will print the latest known block number.
-
-[Full web3js documentation](http://web3js.readthedocs.io/)
-
-## Mainnet and testnets {#mainnet-and-testnets}
-
-Geth runs your node on [Ethereum Mainnet](/glossary/#mainnet) by default.
-
-It is also possible to use Geth to run a node on one of the [public test networks](/developers/docs/networks/#ethereum-testnets), by running one of the following commands in Terminal:
-
-```bash
-geth --syncmode light --rinkeby
-geth --syncmode light --goerli
-```
-
-## Where is the blockchain and EVM data stored? {#where-is-the-blockchain-and-evm-data-stored}
-
-The directory which Geth uses to store raw blockchain data depends on your operating system. Upon running Geth, look for a message that looks like this:
-
-```bash
-INFO [11-18|14:04:47] Allocated cache and file handles database=/Users/bgu/Library/Ethereum/testnet/geth/lightchaindata cache=768 handles=128
-```
-
-The path following `“database=”` should tell you where the blockchain data is stored on your machine. If you’re running a full node, this directory will contain all of the data about every block that has ever been committed to the blockchain. Since we’re running a light node, this directory only contains the block headers.
-
-It’s worth emphasizing here that, at the lowest level, this is where the blockchain lives. The full contents of the blockchain and the EVM state are stored on every full node in the Ethereum network, in directories that look very much like the one on your computer.
-
-## Further reading {#further-reading}
-
-- [Learn more about different networks](/developers/docs/networks/).
-- [Run a full node](/run-a-node/)
From 210cb013a7d593af0ae99f760b3b382ae1eb794e Mon Sep 17 00:00:00 2001
From: Joe
Date: Tue, 14 Jun 2022 11:12:12 +0100
Subject: [PATCH 095/244] additional warning about merge changes to p2p
---
src/content/developers/docs/networking-layer/index.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/content/developers/docs/networking-layer/index.md b/src/content/developers/docs/networking-layer/index.md
index 425d2119ccc..abb3a965457 100644
--- a/src/content/developers/docs/networking-layer/index.md
+++ b/src/content/developers/docs/networking-layer/index.md
@@ -10,6 +10,8 @@ Ethereum is a peer-to-peer network with thousands of nodes that must be able to
After [The Merge](/upgrades/merge/), there will be two parts of client software (execution clients and consensus clients), each with its own distinct networking stack. As well as communicating with other Ethereum nodes, the execution and consensus clients have to communicate with each other. This page gives an introductory explanation of the protocols that enable this communication.
+**Note that after [The Merge](/upgrades/merge) execution clients will no longer be responsible for gossiping blocks, but they will still gossip transactions over the execution-layer peer-to-peer network. Transactions will be passed to consensus clients via a local RPC connection, where they will be packaged into Beacon blocks. Consensus clients will then gossip Beacon blocks across their p2p network.**
+
## Prerequisites {#prerequisites}
Some knowledge of Ethereum [nodes and clients](/src/content/developers/docs/nodes-and-clients/) will be helpful for understanding this page.
From 5710bdfc5bb7536dd0839622a05ec9494a3ac43a Mon Sep 17 00:00:00 2001
From: Joe
Date: Tue, 14 Jun 2022 11:54:35 +0100
Subject: [PATCH 096/244] update banner position and content
---
.../docs/consensus-mechanisms/pow/mining/index.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md b/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
index 427f86f6cf7..cf1c13597c8 100644
--- a/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
+++ b/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
@@ -5,6 +5,10 @@ lang: en
sidebar: true
---
+
+ Proof-of-stake will soon replace proof-of-work as Ethereum's consensus mechanism, meaning mining will be switched off. Instead, Ethereum will be secured by validators who stake Ether. You can start staking your ETH today. Read more on The Merge, proof-of-stake and staking.)
+
+
## Prerequisites {#prerequisites}
To better understand this page, we recommend you first read up on [transactions](/developers/docs/transactions/), [blocks](/developers/docs/blocks/) and [proof-of-work](/developers/docs/consensus-mechanisms/pow/).
@@ -19,10 +23,6 @@ Mining ether = Securing the Network
Ethereum, like Bitcoin, currently uses a [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/pow/) consensus mechanism. Mining is the lifeblood of proof-of-work. Ethereum miners - computers running software - using their time and computation power to process transactions and produce blocks.
-
- Proof-of-stake will replace mining and proof-of-work over the next year. You can start staking your ETH today. More on staking
-
-
## Why do miners exist? {#why-do-miners-exist}
In decentralized systems like Ethereum, we need to ensure that everyone agrees on the order of transactions. Miners help this happen by solving computationally difficult puzzles to produce blocks, securing the network from attacks.
From d007c38bd9526deee6453755038dcb4727c4a202 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Tue, 14 Jun 2022 12:24:33 +0100
Subject: [PATCH 097/244] Update
src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
---
.../developers/docs/consensus-mechanisms/pow/mining/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md b/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
index cf1c13597c8..13a08e81228 100644
--- a/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
+++ b/src/content/developers/docs/consensus-mechanisms/pow/mining/index.md
@@ -6,7 +6,7 @@ sidebar: true
---
- Proof-of-stake will soon replace proof-of-work as Ethereum's consensus mechanism, meaning mining will be switched off. Instead, Ethereum will be secured by validators who stake Ether. You can start staking your ETH today. Read more on The Merge, proof-of-stake and staking.)
+ Proof-of-stake will soon replace proof-of-work as Ethereum's consensus mechanism, meaning mining will be switched off. Instead, Ethereum will be secured by validators who stake ETH. You can start staking your ETH today. Read more on The Merge, proof-of-stake and staking.)
## Prerequisites {#prerequisites}
From 63296b495d44278c73ab86b127953572e2219406 Mon Sep 17 00:00:00 2001
From: Joshua <62268199+minimalsm@users.noreply.github.com>
Date: Tue, 14 Jun 2022 12:29:44 +0100
Subject: [PATCH 098/244] Apply suggestions from code review
---
src/content/decentralized-identity/index.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/content/decentralized-identity/index.md b/src/content/decentralized-identity/index.md
index 2dcaeb77fb5..3524e9723bd 100644
--- a/src/content/decentralized-identity/index.md
+++ b/src/content/decentralized-identity/index.md
@@ -14,7 +14,7 @@ summaryPoint3: Thanks to crypto, users now have the tools to issue, hold and con
Identity underpins virtually every aspect of your life today. Using online services, opening a bank account, voting in elections, buying property, securing employment—all of these things require proving your identity.
-However, traditional identity management systems have long relied on centralized intermediaries who issue, hold, and control your identifiers and [attestations](#what-are-attestations). This means you cannot control your identity-related information, or decide who has access to personally identifiable information (PII) and how much access these parties have.
+However, traditional identity management systems have long relied on centralized intermediaries who issue, hold, and control your identifiers and [attestations](#what-are-attestations). This means you cannot control your identity-related information or decide who has access to personally identifiable information (PII) and how much access these parties have.
To solve these problems, we have decentralized identity systems built on public blockchains like Ethereum. Decentralized identity allows individuals to manage their identity-related information. With decentralized identity solutions, _you_ can create identifiers and claim and hold your attestations without relying on central authorities, like service providers or governments.
@@ -108,9 +108,9 @@ Here's an example to show how on-chain attestations might work in practice:
3. The smart contract selling shares can check the registry contract for the identities of screened buyers, making it possible for the smart contract to determine who is permitted to buy shares or not.
-### Soulbound tokens and identity
+### Soulbound tokens and identity {#soulbound}
-[Soulbound Tokens](https://vitalik.ca/general/2022/01/26/soulbound.html) (non-transferable NFTs) could be used to collect information unique to a specific wallet. This effectively creates a unique on-chain identity bound to a specific Ethereum address that could include tokens representing achievements (e.g. finishing some specific online course or a particular score in a game) or participation in communities.
+[Soulbound tokens](https://vitalik.ca/general/2022/01/26/soulbound.html) (non-transferable NFTs) could be used to collect information unique to a specific wallet. This effectively creates a unique on-chain identity bound to a particular Ethereum address that could include tokens representing achievements (e.g. finishing some specific online course or passing a threshold score in a game) or community participation.
## Benefits of decentralized identity {#benefits-of-decentralized-identity}
@@ -124,7 +124,7 @@ Here's an example to show how on-chain attestations might work in practice:
5. Decentralized identity should work well with emerging zero-knowledge technologies that will enable individuals to prove they own or have done something without revealing what that thing is. This could become a powerful way to combine trust and privacy for applications such as voting.
-6. Decentralized identity enables anti-Sybil mechanisms that can identify when one individual human is pretending to be multiple humans in order to game or spam some system.
+6. Decentralized identity enables anti-Sybil mechanisms to identify when one individual human is pretending to be multiple humans to game or spam some system.
## Decentralized identity use-cases {#decentralized-identity-use-cases}
@@ -148,9 +148,9 @@ Online voting and social media are two novel applications for decentralized iden
Decentralized identity can help create online communities that are free of fake accounts. For example, each user might have to authenticate their identity using an on-chain identity system, like the Ethereum Name Service, reducing the possibility of bots.
-### 4. Anti-Sybil protection
+### 4. Anti-Sybil protection {#sybil-protection}
-Sybil attacks refer to individual humans tricking a system into thinking they are multiple people in order to increase their influence. [Grant-giving applications](https://gitcoin.co/grants/) that use [quadratic voting](https://www.radicalxchange.org/concepts/plural-voting/) are vulnerable to these Sybil attacks because the value of a grant is increased when more individuals vote for it, incentivizing users to split their contributions across many identities. Decentralized identities help to prevent this by rasing the burden on each participant to prove that they are really human, although often without having to reveal specific private information.
+Sybil attacks refer to individual humans tricking a system into thinking they are multiple people to increase their influence. [Grant-giving applications](https://gitcoin.co/grants/) that use [quadratic voting](https://www.radicalxchange.org/concepts/plural-voting/) are vulnerable to these Sybil attacks because the value of a grant is increased when more individuals vote for it, incentivizing users to split their contributions across many identities. Decentralized identities help to prevent this by raising the burden on each participant to prove that they are really human, although often without having to reveal specific private information.
## Use decentralized identity {#use-decentralized-identity}
@@ -160,7 +160,7 @@ There are many ambitious projects using Ethereum as a foundation for decentraliz
- **[SpruceID](https://www.spruceid.com/)** - _A decentralized identity project which allows users to control digital identity with Ethereum accounts and ENS profiles instead of relying on third-party services._
- **[Proof of Humanity](https://www.proofofhumanity.id)** - _Proof of Humanity (or PoH) is a social identity verification system built on Ethereum._
- **[BrightID](https://www.brightid.org/)** - _A decentralized, open-source social identity network seeking to reform identity verification through the creation and analysis of a social graph._
-- - **[Proof-of-personhood Passport](https://proofofpersonhood.com/)** - _A decentralized digital identity aggregator._
+- **[Proof-of-personhood Passport](https://proofofpersonhood.com/)** - _A decentralized digital identity aggregator._
## Further reading {#further-reading}
From 3355358d97acedf8e9ca2b5c736463fdec51d80c Mon Sep 17 00:00:00 2001
From: Joe
Date: Tue, 14 Jun 2022 13:20:18 +0100
Subject: [PATCH 099/244] refine content for pre-merge
---
src/content/developers/docs/intro-to-ether/index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/content/developers/docs/intro-to-ether/index.md b/src/content/developers/docs/intro-to-ether/index.md
index d3b4ae52413..cf05e322549 100644
--- a/src/content/developers/docs/intro-to-ether/index.md
+++ b/src/content/developers/docs/intro-to-ether/index.md
@@ -33,7 +33,7 @@ It is [common](https://www.reuters.com/article/us-crypto-currencies-lending-insi
Minting is the process in which new ether gets created on the Ethereum ledger. The underlying Ethereum protocol creates the new ether, and it is not possible for a user to create ether.
-Ether is minted when a miner creates a block on the Ethereum blockchain. As an incentive to miners, the protocol grants a reward in each block, incrementing the balance of an address set by the block's miner. The block reward has changed over time, and today it is 2 ETH per block.
+Ether is minted when a new block is created on the Ethereum blockchain. As an incentive to build blocks, the protocol grants a reward in each block, incrementing the balance of an address set by the block producer. The block reward has changed over time, and today it is 2 ETH per block. After the merge issuance to each validator depends upon the amount of ether they have staked and their performance.
## Burning ether {#burning-ether}
@@ -41,7 +41,7 @@ As well as creating ether through block rewards, ether can get destroyed by a pr
Ether burn occurs in every transaction on Ethereum. When users pay for their transactions, a base gas fee, set by the network according to transactional demand, gets destroyed. This, coupled with variable block sizes and a maximum gas fee, simplifies transaction fee estimation on Ethereum. When network demand is high, [blocks](https://etherscan.io/block/12965263) can burn more ether than they mint, effectively offsetting ether issuance.
-Burning the base fee prevents various ways the miners could manipulate it otherwise. For example, if miners got the base fee, they could include their own transactions for free and raise the base fee for everyone else. Alternatively, they could refund the base fee to some users off-chain, leading to a more opaque and complex transaction fee market.
+Burning the base fee prevents various ways block producers could manipulate it otherwise. For example, if miners got the base fee, they could include their own transactions for free and raise the base fee for everyone else. Alternatively, they could refund the base fee to some users off-chain, leading to a more opaque and complex transaction fee market.
## Denominations of ether {#denominations}
@@ -68,7 +68,7 @@ When the recipient address is a [smart contract](/developers/docs/smart-contract
Users can query the ether balance of any [account](/developers/docs/accounts/) by inspecting the account's `balance` field, which shows ether holdings denominated in wei.
-[Etherscan](https://etherscan.io) is a popular tool to inspect address balances via a web-based application. For example, [this Etherscan page](https://etherscan.io/address/0xde0b295669a9fd93d5f28d9ec85e40f4cb697bae) shows the balance for the Ethereum Foundation.
+[Etherscan](https://etherscan.io) is a popular tool to inspect address balances via a web-based application. For example, [this Etherscan page](https://etherscan.io/address/0xde0b295669a9fd93d5f28d9ec85e40f4cb697bae) shows the balance for the Ethereum Foundation. Account balances can also be queried using wallets or directly by making requests to nodes.
## Further reading {#further-reading}
From 0ca24094345cfe3264a3ed6c152c5c831e169978 Mon Sep 17 00:00:00 2001
From: Joe
Date: Tue, 14 Jun 2022 13:22:18 +0100
Subject: [PATCH 100/244] rm "miner"
---
src/content/developers/docs/intro-to-ether/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/content/developers/docs/intro-to-ether/index.md b/src/content/developers/docs/intro-to-ether/index.md
index cf05e322549..3a806cba42d 100644
--- a/src/content/developers/docs/intro-to-ether/index.md
+++ b/src/content/developers/docs/intro-to-ether/index.md
@@ -41,7 +41,7 @@ As well as creating ether through block rewards, ether can get destroyed by a pr
Ether burn occurs in every transaction on Ethereum. When users pay for their transactions, a base gas fee, set by the network according to transactional demand, gets destroyed. This, coupled with variable block sizes and a maximum gas fee, simplifies transaction fee estimation on Ethereum. When network demand is high, [blocks](https://etherscan.io/block/12965263) can burn more ether than they mint, effectively offsetting ether issuance.
-Burning the base fee prevents various ways block producers could manipulate it otherwise. For example, if miners got the base fee, they could include their own transactions for free and raise the base fee for everyone else. Alternatively, they could refund the base fee to some users off-chain, leading to a more opaque and complex transaction fee market.
+Burning the base fee prevents various ways block producers could manipulate it otherwise. For example, if block producers received the base fee, they could include their own transactions for free and raise the base fee for everyone else. Alternatively, they could refund the base fee to some users off-chain, leading to a more opaque and complex transaction fee market.
## Denominations of ether {#denominations}
From 233b167b87d71f2aaf64c36b6fd78a183cfa5148 Mon Sep 17 00:00:00 2001
From: barukimang
Date: Tue, 14 Jun 2022 15:57:41 +0300
Subject: [PATCH 101/244] added ethsafari to community events page
---
src/data/community-events.json | 9 +++++++++
yarn.lock | 2 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/src/data/community-events.json b/src/data/community-events.json
index c6a5822d825..72fdba5a56c 100644
--- a/src/data/community-events.json
+++ b/src/data/community-events.json
@@ -430,5 +430,14 @@
"description": "Join Warsaw Web3 community in the first in-person conference and hackathon!",
"startDate": "2022-09-01",
"endDate": "2022-09-04"
+ },
+ {
+ "title": "ETHSafari",
+ "to": "https://ethsafari.xyz/",
+ "sponsor": null,
+ "location": "Nairobi & Kilifi, Kenya",
+ "description": "Welcome to the latest greatest ETH event happening in Africa!",
+ "startDate": "2022-09-18",
+ "endDate": "2022-09-25"
}
]
diff --git a/yarn.lock b/yarn.lock
index 8ffc8f2b3b1..f1e199cf220 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -11592,7 +11592,7 @@ minimatch@^3.1.1, minimatch@^3.1.2:
dependencies:
brace-expansion "^1.1.7"
-minimist@^1.2.0, minimist@^1.2.3, minimist@^1.2.5, minimist@^1.2.6:
+minimist@^1.2.0, minimist@^1.2.3, minimist@^1.2.6:
version "1.2.6"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.6.tgz#8637a5b759ea0d6e98702cfb3a9283323c93af44"
integrity sha512-Jsjnk4bw3YJqYzbdyBiNsPWHPfO++UGG749Cxs6peCu5Xg4nrena6OVxOYxrQTqww0Jmwt+Ref8rggumkTLz9Q==
From 21ecaaa3083e70a36a8793119dc60d89e165e0d0 Mon Sep 17 00:00:00 2001
From: vdusart
Date: Tue, 14 Jun 2022 16:01:23 +0200
Subject: [PATCH 102/244] Fix comments
---
src/components/FeedbackCard.tsx | 12 ++++++++----
src/components/FeedbackWidget.tsx | 16 ++++++++--------
src/components/FileContributors.tsx | 24 +++++++++++++++++++-----
src/components/Footer.tsx | 2 +-
src/components/Link.tsx | 3 +--
5 files changed, 37 insertions(+), 20 deletions(-)
diff --git a/src/components/FeedbackCard.tsx b/src/components/FeedbackCard.tsx
index 2671fdd2446..b47fcd139a9 100644
--- a/src/components/FeedbackCard.tsx
+++ b/src/components/FeedbackCard.tsx
@@ -1,4 +1,4 @@
-import React, { useState } from "react"
+import React, { ReactNode, useState } from "react"
import styled from "styled-components"
import { ButtonSecondary } from "./SharedStyledComponents"
import { trackCustomEvent } from "../utils/matomo"
@@ -50,7 +50,11 @@ const FeedbackCard: React.FC = ({ prompt, className }) => {
const location = typeof window !== "undefined" ? window.location.href : ""
const isStaking = location.includes("staking")
- const getTitle = (feedbackSubmitted, isStaking, isHelpful) => {
+ const getTitle = (
+ feedbackSubmitted: boolean,
+ isStaking: boolean,
+ isHelpful: boolean
+ ): ReactNode => {
if (!feedbackSubmitted)
return prompt ||
if (isStaking)
@@ -77,11 +81,11 @@ const FeedbackCard: React.FC = ({ prompt, className }) => {
)
}
- const handleClick = (isHelpful) => {
+ const handleClick = (isHelpful: boolean): void => {
trackCustomEvent({
eventCategory: `Page is helpful feedback`,
eventAction: `Clicked`,
- eventName: isHelpful,
+ eventName: String(isHelpful),
})
setIsHelpful(isHelpful)
setFeedbackSubmitted(true)
diff --git a/src/components/FeedbackWidget.tsx b/src/components/FeedbackWidget.tsx
index 95997f0f142..678a28811f6 100644
--- a/src/components/FeedbackWidget.tsx
+++ b/src/components/FeedbackWidget.tsx
@@ -151,9 +151,9 @@ const FeedbackWidget: React.FC = ({ className }) => {
const intl = useIntl()
const containerRef = useRef(null)
useOnClickOutside(containerRef, () => handleClose(), [`mousedown`])
- const [isOpen, setIsOpen] = useState(false)
- const [feedbackSubmitted, setFeedbackSubmitted] = useState(false)
- const [isHelpful, setIsHelpful] = useState(null)
+ const [isOpen, setIsOpen] = useState(false)
+ const [feedbackSubmitted, setFeedbackSubmitted] = useState(false)
+ const [isHelpful, setIsHelpful] = useState(null)
const location = typeof window !== "undefined" ? window.location.href : ""
@@ -198,7 +198,7 @@ const FeedbackWidget: React.FC = ({ className }) => {
return offset
}, [location])
- const handleClose = () => {
+ const handleClose = (): void => {
setIsOpen(false)
trackCustomEvent({
eventCategory: `FeedbackWidget toggled`,
@@ -206,7 +206,7 @@ const FeedbackWidget: React.FC = ({ className }) => {
eventName: `Closed feedback widget`,
})
}
- const handleOpen = () => {
+ const handleOpen = (): void => {
setIsOpen(true)
trackCustomEvent({
eventCategory: `FeedbackWidget toggled`,
@@ -214,16 +214,16 @@ const FeedbackWidget: React.FC = ({ className }) => {
eventName: `Opened feedback widget`,
})
}
- const handleSubmit = (choice) => {
+ const handleSubmit = (choice: boolean): void => {
trackCustomEvent({
eventCategory: `Page is helpful feedback`,
eventAction: `Clicked`,
- eventName: choice,
+ eventName: String(choice),
})
setIsHelpful(choice)
setFeedbackSubmitted(true)
}
- const handleSurveyOpen = () => {
+ const handleSurveyOpen = (): void => {
trackCustomEvent({
eventCategory: `Feedback survey opened`,
eventAction: `Clicked`,
diff --git a/src/components/FileContributors.tsx b/src/components/FileContributors.tsx
index 5d20c35762a..4e2cedac073 100644
--- a/src/components/FileContributors.tsx
+++ b/src/components/FileContributors.tsx
@@ -52,7 +52,7 @@ const SkeletonContainer = styled(Container)<{
loading: boolean
}>`
justify-content: flex-start;
- position: absolute;é
+ position: absolute;
width: 100%;
height: 100%;
left: 0;
@@ -227,6 +227,21 @@ const COMMIT_HISTORY = gql`
}
`
+interface Author {
+ name: string
+ email: string
+ avatarUrl: string
+ user: {
+ login: string
+ url: string
+ }
+}
+
+interface Commit {
+ author: Author
+ committedDate: string
+}
+
export interface IProps {
relativePath: string
className?: string
@@ -247,15 +262,14 @@ const FileContributors: React.FC = ({
if (error) return null
- const commits = data?.repository?.ref?.target?.history?.edges?.map(
- (commit) => commit.node
- )
+ const commits: Array =
+ data?.repository?.ref?.target?.history?.edges?.map((commit) => commit.node)
const lastCommit = commits?.[0] || {}
const lastContributor = lastCommit?.author || {}
const uniqueContributors =
commits?.reduce(
- (res, cur) => {
+ (res: Array, cur: Commit) => {
if (cur.author.user === null) {
return res
}
diff --git a/src/components/Footer.tsx b/src/components/Footer.tsx
index 969bb0c78e8..f16d41b9e75 100644
--- a/src/components/Footer.tsx
+++ b/src/components/Footer.tsx
@@ -396,7 +396,7 @@ const Footer: React.FC = () => {
{section.links.map((link, linkIdx) => (
diff --git a/src/components/Link.tsx b/src/components/Link.tsx
index 460619d4e8f..f6f3d68a7bd 100644
--- a/src/components/Link.tsx
+++ b/src/components/Link.tsx
@@ -7,7 +7,6 @@ import Icon from "./Icon"
import { languageMetadata } from "../utils/languages"
import { trackCustomEvent, EventOptions } from "../utils/matomo"
-import { StringValueNode } from "graphql"
const HASH_PATTERN = /^#.*/
// const DOMAIN_PATTERN = /^(?:https?:)?[/]{2,}([^/]+)/
@@ -67,7 +66,7 @@ const GlossaryIcon = styled(Icon)`
export interface IProps {
to?: string
href?: string
- dir?: "ltr" | "rtl"
+ dir?: "ltr" | "rtl" | "auto"
hideArrow?: boolean
className?: string
isPartiallyActive?: boolean
From 9e9e98092ee7b8d87501d3ac3c1cb08f80f6c358 Mon Sep 17 00:00:00 2001
From: Joe
Date: Tue, 14 Jun 2022 15:08:06 +0100
Subject: [PATCH 103/244] update nodes page to include ex/cons client info
---
.../docs/nodes-and-clients/eth1eth2client.png | Bin 0 -> 272874 bytes
.../developers/docs/nodes-and-clients/index.md | 14 ++++++++------
2 files changed, 8 insertions(+), 6 deletions(-)
create mode 100644 src/content/developers/docs/nodes-and-clients/eth1eth2client.png
diff --git a/src/content/developers/docs/nodes-and-clients/eth1eth2client.png b/src/content/developers/docs/nodes-and-clients/eth1eth2client.png
new file mode 100644
index 0000000000000000000000000000000000000000..c84b1edcae051c16c38c17a99f0678ebdd58fcec
GIT binary patch
literal 272874
zcmeEucRZGV`~L0DOtO-_Njn)Kg=|qsrBYF5Mn=kB30YZ%C?kqgR!P}XA&N4yl@^)V
z^LJeOJiqVnyZ-(C^>{t6o<6zn>%Ok{`#g{HIFI9e-@$r^H5k@%ttF923|gA1M@S^9
z6C~1_tF&a|Uxs&1kw^k0E!6`@T`7Kd(;Q`Mo0sXcU+O%gRq{47SSCT0O8fjS=Pl&(
zROwmQPJd<4zEKjNP?`}acqwhP<~WAI~mSiDx79{^(Wu1B6am2t{-<_cviln
z!|LAUt5$ACQsqWcr7BWoMp8OVW+VE>t>yO33{gi`}Eu-@Ui)nt`;m^r6}A&N2Znx8Fxi
zt0TBn9L!o;!
z;iF1(|CQh4t^*XsanmUZgPFQZKgJxFC10HqAo*!gM$*Pp(ik5gP`RR)mBaOqg^7vp
z;&+Xuo$Z}7ZT7+Y_wVoC-#i-Ao#x#nQXYTB**UV;v3B%T^RD*;ZPtVAfAY$I%Iw*5
zWAC5Gyf+e3Gxw(vQ_CTNW8PU_w3oT^z?LB*^t0{4x2Nb4jeeJ?5Z!m!A&Jf
zo=2`KYX1f~Ik|zvJ9qB<{{8#$?x@?hZ{NCgOKwBX1tC+N67QviFm3*jXLMKR_ee`m
zwbW>G?uxDsjgyMHd2@2&Tiwl@Hw|;n-cL_&^py18Ehl%|GfL`$$fixvqA|b3?oK!C
zGA{Gfvim(d#K)(7NPX?mQjKtam&j(R9XoblSw%(7yDq%ty&WALosf_a8#_JN@+gm0
zuT#lLU^pf=Ha02gaI0qL`G;TMv|H%v>Shdcq^}8E(3;vJLEqA?9-cuhwpCBkJCa;L
zA66`tZ=*A*HLUyj^JlXL;e~FINmIoWc4IBofN%coDDy1I0h2Q)nn
z>Uyg@dHC>QcJ`+7sw3rJ*C)SZT;9HG*RE~bgvn&tM$
zy??MYoP6g@`Gp1@Jhlk|@VZ~~;K75Mn%6@kLU}oN@7|r4
zm*=R$%*x8j%e(aDO=xESb)Jyx*RTI*NY+qQRaH|fbsZOykeHbJ^P^vC+}3QL*SwVN
zX5}CuGo8qB-K2eVd?6|QwCTYqDJgw@ePX&vlvGqyl$5iK0lf~hH`o;v6nacw*=*hy
z^s1_=s;;iCt*x!Mw-=6E;^O#A#N!%EoiJ+(MMXs)pOuP=3jIUsTsuucz3NwuLt6428#k&?`|B?y+j8HY
z_*KL4vUlD3fS{llukhc_4MC>AO|C$+`t953SD6h_)xMR2PL$XA
zZ%`&^>ge!%IJh(wlOB|*!*pv>kdEI;@7|}qM>l?-8fp_Ul-M&gZYW`zc{4FFF)mJH
zeFRoAARyq`-1U3+grcK2Z`ra1`Lb=>wq3h&9`n?1IcjJaGf6SWQ&N^u=6y8Z*Nmp4
zv$K|s_U_%gBD<76QPfa1&g`PkT(T7ORjsi6xUQX+VB*F_6%~noBO@b7*!`|!eH{fh
z_*20mj>`6CJpAkT?=NK)JG}0&q-;x{S#<<|8}F_g
z4AmdU&(GGGYDDn0aB_B39Z=`r?|xH9XJguvCr_j=SRH2Ks&X8tVMbos*$t;@L|EI{
zFdoiM-EFeXBV$*dUlM6Lt5-?_jfapDk;94ra-Xh<&cq@Z#d&
zxTD~ez{6V8f0ak{Fe42o&y?I?g|fWnjUC8Qv7m?gG}}6&26ELEYW+T#>BJ`_90{t%
zegR1n0OE;>Mkh`*@+i|VCVp2ra3g;pQhR;*v*gw)$6udBxw*NGj5_P$b{W5P`ZlN+
zS+&^m$S{W?pj+>Bxp%ks=8Ih~94~FY$na*kvyhjEhbQROh0S;F-W}~OX2&}X4QKAJ
zh+Q8Js$dsGgt51owVMzTmYjxkQ?jvn6dGDL(p~)dEq!aSzj=uXAEz0Mg@whY1QYzB
z&ATu>A9dipl+$FgN{o;8rt|nYcTP~+^xV0V<=#t0QF-1=?wdAk$`3FtKT~*-_qK0v
z@P#h>hXML^sYm1E<1_8G{A@pEMx{}&v<}w9#z@~d)14_=UMFxY)N!cTdud)jJ|-o+!SugPy)Fkb(Qe$&+nQjAkxME=jkyKG}?&ox5;{p;3h4JM-_ne3pSs{ejHe+LBFR!HldiLYl
zr{{8fmTa(0<%<(_Is7}lx!2~G7zci7Gxk{;F6{lzNHa`nYN%aC{Ks2wwOGly-)0GT
zr^Na}it_V2*Z(Tu
z&yR+T2Rzy1eY(~nJE#ioQB@s~uWOemC{k0&i#+FWc}2WNf_*)ex$=%nl~<`kH|{vK
zcSBfMn5kIG10Exe?55-oreYk@fwr~x)Iz=a*Q%?()n_f~6?n2QprN87*Q_?W*Js7+
z<2|+Xn6QN3XQ-=(@0p3*_QIub5$(90qBgh9=6xnw?8}$l*3`@{jF#^@Q*<*b%F#B+
zXXsV${d_a7EV>@^*i>FK2Y$|;mduycyY$XDHm^$;-hn3>)c1K*QB(86b^ME{cI@_3
zwPY_pzDI<5n4-Fq1JeF_|rgL*&D>zLkzyw)(C%nqiXz+u{ugvBQVro
zkuieq^5x463=H|%!WuWi=DZy!3$8hq-`^zbIXjjb>|g&VJKGy*O1$D6tFA)7%(G7M
ze$}A$;iv8f2EKjKl5wU()jVrHU8$fdb3EM|7?aLuWo;e3)vx7u+BUz9mn5mzLH$>cd}8ML}Cqh@2Qb6vQb=s8xNsemy-s)6>(R
zJ{?g}srm+}JX>-?LqlxKmSA_^=}hH|7k3UnozE0IrO!D3!0WWJx;pjLzDpAhkM(uc
z#TXlf8k)GKeomG16-l4wn#!E(w_IdcPItR#_-d@GWO<$w9FCt~_d#$(L_{d}l5B-O
zBQ^I_dv2cpM|*nfjT2^->;^o|F%6qO@3fA2yCaMxg}QdlCv~q+=a=vA%UA6b`Wky7
z(f*#qh4Fy_v#g-7!8HSiD64n}8j{oYe#$&B*l(A%7PVc-o`R!AZG|g6NlxyxfLEe>
zJ@+w=sePW-Z5*Das>fSj=$7y=@Vw|}H(0mKQ@~hOXX5RxFtr@&ayzN#LF!qWF^X*p
zY;}vii5kV3i;JEemE}es-oGy>EbJ}1JXF~0U2NZ5mYKP^M1xd*M5#}h9&sC0nYVY9
zZKNuJvD?_#=<9#HEom9M%Xqn(--m;fQ(8(&=jgEsdj2WzU*%_|WG9mj3|?O2Kgz|k
zeo)Q7xj5$`yLnTYu1B*CZKfgP5vmTuvmeVMav#3@mE$AatD{+Z|ITyq5s!}E`Sost
z;iuEqR@uw(jK?HAc>X+gnxfm_C|};lICbXm?M!j~sp}p-C|*J({$0tZ#SkZXU;n>&gD91r5!mFw^gsS=+Qz$
z;bVrGnGvnCEz3WaKlRGYy5C6kY0g$%+x)2G;VV@Sp|>i1F|?8F@7>+pg0ElqTo^6{
zoHH{s59}u=n|b6Op>51SXia_|$&`kK;K#V75$W9Ad^0)O-ozx=_H%yWCUQ@So66mL
zVF%YXCVh%*V>)u-Do94EYNav%vn~F4VuzdMT2uqFN6HVsR=<^LP*8p>!6{ML+lC
zFV_v;^-I<=3oEu%jJ;j#&eFHvuwoQ#f7kV>N9kpUdkSMazgAy);==#O(DH7IYGbvXV#rET?8ge|DqC-^)h0)N^(B6J@!(*DzYb46I>`Fo=p6p=(gu?9S!fs`6pOck!
zP)iHRKRa5!vb?j9x@6(iZc#$Gq4o44i!hI&V&PWAL`2fl($X?AXj}?By%@r|yq*)c
z^ZbxMgFkUQZ)l$t6x@o76Wg?j511uF4hs(#b34(;Zm`>S^Xk=f!b!Ji+e79;
zj9gq~SSSqq!|yAb@IYjKd!Taj>W$ADk-^+WMMcqU?cKWxpPO4-hA+26H2#M
z+C46!JUlq!dyo=*oRX4KN?Q8zl`BHb;(WVq$^qu!s#zHCx
zDja7Z;CLHzW)4Wn{AC9RaV^U2#$`N=^os`*HntFvC@xKY7ED4-MBc^5ZWJLupyt*N
zsF1~;hWTIB|GNf-l!HS4Uz8B8FKCx{(e)@$2MGoVlQD8g=(WRfk)A*h#
zzOvtaGP9(l)%wQH}df*7^6wG$H(AnzP>+RjZDhS0-N>GxN2c4hQK2?hUF@LqIXSzZEf
zSI5q*`@1tmECRv4_GNSG%F16V{b>+CV1n44WBf|yicg5$Y2~*GB6dfb_UN%=Z>p<{
zi;A|QKRor!3dIc@WMgI6O!0p=$kEZ!(6H^^y?f}?fGhvY2H^sxrlx03pWeX6#=hg!
zwQb~{DyFB{BBqpW6i^?K%pgj~b##6&FD;-&otm2Z-|p$?QB@5Md3kyC{aA9L|Fk?-
ztQ0$U?u2XsLZV5jBPtim;KxjCRbK_32y0jpq=erh*8Tnc@7&=*Ri?OplK4eqB9e}Y
zjji<34?xOcJG&i#)m8?*Ufs=TL&RQJXA!mAQO
zdoKK(hlmjk)|5k(==g+1MepCcM-KLl_#VM_fD}xc{2Q#Z8DupzHSl&wax5$?>(;G%
zbo|LHN%Hc;E#Ft8@EEpIB_XHJ}G@99yHlY3cG!V~P9Q}kZ{WrH?xBaimy
zO0V9Cs^6N=r
zJ-(4d6-k@&qgA7Ob)Px>u3jZW<}olZfSQH=Bl}dryXNK%_6)P)FHWq*68YumS5#MP
zoIbr6#P5wOX577d2A98ZVGDx7)FAC}@xL3CF0BT0C{e14!3}g49NnLe!A3s
zD()672S>T<(W79MGVziz&h!S<<$yK}6ifK+a@a>zMyE{;Ir0Zo2+Nt*m
z((Jp=F7_2tJ72jHd-JA+jD`
zMVNEZs6W)Cg!)B8NeSdWpsj5)+Ee<;o}P{EmZar}_Rh|rfPh=Eu~%GN;$maVctRj*
z6G(V{RnBckkJ9Z(a@#S6nht
z#=fJy9YuBE$B($1H@iwb4AFiW8}~xHv@VV?7)6ysz9QQyOO6~re)1$CdO^*tJ}KWy
z_RBej#J24%Tl#cgd)GZ`bS&+QU#6&yQy^eAKv0AiP@-b}=HK%NG5_26oL1(4x2U@zw9
z=dWJ93LG&=pzZtm)#$0k`w+Hm%d=k@A;cn)>{zd1ZNVm>S|}+g>FevGFzM+<=H-ne
z&2giM=lrKnQCuPVEiEp7NZRl5vr!Or64&?eSb&p}lY3WTVQZACFN9PC0M;loGZRnj
z>FMe1y?kq%Arx-hDssmF*TdGfv`jf}ZSL&kW@Eej>(hP2Q&*Xnyp)s_65;vt>93D@
zZTu?Qw)TA+78Mebu
zZ-awbj~*4{)wuP;mxX*|VlLIi?f{O00AMc)#jbnIjLa=8XsD@~TUx@%Ic{i(XdLM&
zH9CCw1IS%fl`!z_%H~MgS)IM7v5!_K@FXu$%kfmGW_YS2M~*-QMWuoCdH2p8w6#Nn
zgQq%ADRwlyL3RT~TAG_hL_{X1rcmF{mbmI4KR$gs<(#CzSisuIAgaTOd+bm?u=*%_
z2tFW9>XYF2%PaugSr#LPPVhOUzCSEA_4Uqsv`89j>Ek{2EWxdEXS^&JJNc@j1VNXYQ;
zFn%*o>GW49!GD6z!oxz!78DfV1^5f%9=-zJJ-`r1y!e+h-V1m|bl`DuFiYQcV_Ta>Y!`f}1YcXllTKP%
zT6h{r7JWCDywY2cY3Mr=5~!ttzv#w6u>tRO@7`H;7Ukzh?^C=7(G$T`QnL8&*0#<<
zd*gEN(y*|4xIX*}o|+f;2r}$;n;PE%lATSm6RN1M$9`Lao`J8~1Vk~#uLVngpv+c>
zeoR2gm<-|BWu)t4b7Omn+aCl7x?43ZtzVPBni%=^VVebh%$X{3b8#gkCZYmO{P|;C
z;@Uqjke->js=l2qi4P6cMpbEVmlYQmhbZ>pt~@n0HC6?fg1HvgM}p;
zL1JLg)Y>`?%)^eNNV?`EF;qpv?9(s37OvRZ+M=X-czA%i
zUc7h_c#1Ca)~yyIvy&CzSL1l|g@#lbK0NPcJ+)H95JCfdQXU>N%H>%|V195|K8ls;`Ml
zy?TY6&+Ncj!|dGeIV%o$NKH*GEG#T9_lX`+fDeXJ0EHnbX?dVFrr2fl)X9@~6};xV
zUS0yHdEq%XfxH7|PR~!-M8DykByCuxaZc^*3X~iq_#`R$P|_?HOQzUfI&;(9Dc!eR904^*&r6*Wi$!l
zjv&VRAJWmWwX*{X0i+&fWrc)>Vnwi9_*jVh-y4z}-n~Oz%gV`F`S~#o6+A0z>pp3R
z=+(YDyLc6G_$k(?5
zYV?EoR$pN7!^})Dhsw6LLRg|MUtmuS4UK9aK77T=37znlZ{L=FWh8sg_6NEB`M$Kg
zFp8+d-j7dDm$^?3A{J0G0Ha_AS4O(F2n#>8Y1?`BY|pVr$MbS?Z6V^!jC3Q8;Cdre
zP=$EFgn$^3NNQ^Z4OOlO2RmN6lyf5Q>aAOs|9pS%o0OcKjO)D#VM8SY
z^nen6`0ydexcs8EwNOUN?UN@#J@FKI`S}vk(xs?22%^jz*iQ~#UL=AQZ~^dVXRekM
zADNVN(cD}V&$w;dql^s8bLSj?Hm35*Um3&CpFj4W^S^;#T)A=umpp#_I09lLJNu9R
z{*z^%a_sDJ*g=#uL@N3oBjfbHj<4bI;~SZnOf0TAqR|DsL&GKvm2KOGZt%)Cx3t*V
z+5+Ve2-Rnq;Sj|}M(XM5nOIsDVsVkcxNLMZ%S4#(jT<)*hUw`d=-mz-djG_z5bKwH
z@@e4h+inZf!*I9p*-$ye;w%ux#|#bOW21(50)$_`ehrJm$Y`O$Z%y%)VW9$3OUvHp
zcAaQsAz|J{g2l(XV($zx4iC5InJzERp_Z;dp+_J54BaLxYm8+>5*Dfdq2EzU6$-MC
zHW7(EC3CL==miA@v45JBi#t?w*7^AmEuiAZsuF_Y35aiwjEd_2`O_7vcqnntjuW{i
zOY>9Mbc4xO5}3~WL>W->T%kMx%NObpcSFnV5pSKbAc5^M>U
z4C;0nzz=l&?%i%JFE2Hrkc2>~s(N~%X%qTotTlK%k_tl|sBIGyP7_JWXU?2~K7^i#
zjxHFXgGIjBU33gFUt9aIsAw2-@JaEeWo}zIoTLy9ZUj!eP$M}^B!~gh|-%ko8N|W1Gw=z{E4ZEYuB#b
z;E{8h8f*b@;p9ZKwwk|h%_vz>-@Gr
z!!kMOmghi-56*(fbnk^}J8U}ma6}|+`wPdk%*>z22srBe``u@4uU?0bTUTcT6!9@B
zcl-0;&YiAkQEh1WaqZVeWuo-MaMq_fMWUK{OBb_1m{@1?Zoha9M!V
zVAq~|?%TUtz*o4s&^Uhm`UQGLM@I+w>$tvt6t)ea0)+!>apT5%w*_C6k=)#|2Zs`2
z+4CuScXf1}LamLAbU<(BwJ^OjUd<1|4E@@E=#F5UU|gsyC?e=j(OHA_$xK}Ag6j!R
z1u_Gp2Od*)R#p)lUtn3yyLWv1TpK$&_M*;|mn#Yi_RmiZVbB1WVW_XaTUt6iEG)g~
z%%MZ!$;rJCB9KQBJaWoAH-rC%1qbUJ8YV0HD1c>1O8$YRY;I;oNQyoy-q2`)jffxo
z2_lT_y&e(*ChyT(<^^(r%1zj+1=cONrPF85#6(A<)Md7WZv|jsq6f_cn%GB~nYrjo
z|NOzz8W|Y;sfiNCd)KaAYxLaqB#t&pdp%JpT`Y?D
z!VC@LA|mYJ2m=NdW=0F2Klffu^!^IABbbM`%6SX;YARP-`_Vb4DbaR7(_
zu@p}Q9E-6cd<%1Pg7i!eccT72#mfC9TRtmGGeB?9^-s06zYwAz&X_sqeBt<2rq}c7
z`8R7JAz|2r(2sz}Z{J#A8&Dy!MSufTH;_yaCk$%=tsta;RD#SYT>4&*^7N4J7rq5GZqp_NMZ#jL
z5pL%7>j8u*7~0P5+b74yWG{UWgEoa22SJCh4)ozu@I)a5)ViUgFgO3kz`X~z{|;0^
z?$X<;Dj;=DW#xgRN1ZX;fZqMcv18Jbk{**k^$|3#t}ik&e%#lN!wq@QePajeu36&`
zuvOR4Q1qA%J4lJKj$K5xJ4b^66HFBZ14SHw<|FVFA;Tcsfeb^q_l+B46A}hTNA1x%
zrltyth&*%p_6|cqkf3Cwr2~S3AOV%R2=!q!c~^J$vry-N?2tOZi4_;e
z)?jiCJQlSgC&wPl813cU>?|Sppmjk>dr@3$X=bL=yZ|2qGy+XuA(9Au9fcnV*@M6a
z%ff>Q3BCIKd9E>41)+g-b#ZnM3kfOln8`*vJP_=QU_`0Cew~(vhGxr_hk)*Eqr$`J
zz|bdSMi9P(gajtQK7tG$KOT!o8dPME2LY{QekdVNN!2wuLN9Q*F
z1<@A(=D8ZVxzW*|(D9+f0+SyfkphLY9_dZlbSM$sCLnv^pY6
zEELGs-e(txu{bbb6s~a93f0pbjDCze!4_%6-jE5Mxbd!%we=wK1o5&5BUldo$`%&i
zw;ZA*?g^R{%0HMpytsj60jP>_6=I{KkF46FC!zoii<%WQ88Pan~^gbXo8>{U_J&))W?sQLw38z*9*iN87Tw5C(7{k
z>%Y-EA@P91;0K^R;CB$7VG`|i8bD(f{OFO5gTokN8!g02tE!UKiJwagGYxm;;TB6_
zdqEZV4HHD|&5Q-YzGH8$OB3d+JmIrn3C~Rg8@l
zB_s&R6-B0~sH3iK=yfn_)uA0;0BP_ZFf|mFwe<8)b8|Ou-3qRQ%VG;-*j1wAWDkq@
zjzdgTB_9>?O-^2cUVu!3ab^}U{@>&m%zPAG8BTyN!pPVF`Q`E1(s^jeC-Ti|!EkDY
zC!gP7C#qawA?BHhqF`f#p;8oabiUty{D33o?Bo;@76$l2U{C$|BkwW&7(Fmt0Wk8Y
zDCS}R8RJs-%RoOAfNfj1MprLD1f`~-K?~!A&IY->frX_AAc6T#=#1mmvY^;-e4oK^
zg?gQpnJK$>uY&7XMMJ|V$|Yn_01g766Qibo=+~miA>3*%O@Lvb=>dU%W>QIpFNIDs
z`rG{n56Uo=ym|9a@C@{VKz<^wF<*k%LEY3jbVy8_($)3nuV3gDOuCHLpdmecN0xb7
zYWt<16tmd%ftT}0b>dwRsMhl<@bL5Z_VgU?8RcbSN_qJ3rD^qg6zLs1o(#3+!2Unn
z+zqHBVrctz(3P!Qwzw_MI)YerY@@}!)+F+R%EG5a4ncbAO`z3;Loz-6JTDK-;>V94
z;EBt~EmY+#kAO@ldzgyB)unA(>l36QJbdWwRot_u6=05lIeXT-^SK=s4A29tdhlFv
z(?nS+#G~tNJhiIf1~!G*aIvu4B)do2ZB2S-xc}*
z(sgQjIyNrO!`&S!CVa;2V8VzF#0Z*-syg{+px&sPAXAXqR>rCrAu-6hO_<@XUdH>}
zQ&mC*1ucZc0{!OZty|R!!oHC08XKW7W}`;{$HH92)~)Zr(!e1Q{Fu~$91K1p>a*ni
z=ldZOlN9JW$W?3(>;(9T%F1MO>8!@qR=83`3x!YC*3w2Z8zV+O5>xP;K|y6V+GcQR
z2(CMJ3kb~e#Ppy@=Xc(JDho~XK=?&;HANGS|{fU|?sp!g}Ps9=1;Q_r`8X2aO@_(oRN
z1&CNsxY3^hd*IqdK_q(xk!%w&JmbXgNxy3G+OunFX(1=xL4|nv;)SMA#ivhBgGtP}
z=5-q(C!^Cr`s4Z?boam&AdDAzFFXk*A)nCVLhHdsnVFmGx4^CtXp6y^upy{`y88F@
zvN9w`LP7`n)s><0<)PxyvP8K{-vMGii{sVFfu`6-F!QCA<#Vi$?
zOh}9bRY9di3yji*-VV2dC50rbaf64MiRlE231HPN
z5CzeJKokc>x^iW@LJzR92>=9b5+>AWG_94LU8(ag79bdUFsGaz)BznzmtPAw*K4
z0wE5GDzo!ue7vk|WuB=frQUv4Dq5W=xG+R#w9D
zJJ|tM68;NX9Pe-M*qTBgK>9CtaLvrjV4CnwONCjNKtMy~0EB~tLQivK
zr2xHxbOsFO-^Yx(2muih9IR3AX@;<8=auC_iED(lEKsP25Lmf($4tE32R^
zWP$)ivjUXIcmSec$)0}V^o+|(Axr^j0oQwayrWf#)CH%UnH@Lf<-JSLfTaCK2M!2s
z-kgcD16%|2AmZ`ts7Rp3Xwz^_Vc~z6^46`^C}(PF0f=zK6Dl@x8%p{^gACvlvI_m!
zDI+5|<28TAKt5~v3;%${$;;zXFf?JpK`z6AqK7#-{Ads~=jRu|EV9p*Zryb1CC&1`
zW&t)mM{^75ExK=dpIJpkMmAy-F#dyZ0L=lQt!juWNFwARSoS!ID!Rn3uG1h3Gn$k{
zV|M!V9gt(BG`O>XfB+WP=ChYRBdsSFMKo>vZc}Oq0}vgHix<$@I;d4-Tv+$`)=px~
ztIk5>{_60Qo*!o1@qxG{aANd$=qfS8_OMtQ?T|6TU0WLkXyoMV(=a+Aj5y(n=(G?*
zu>W9dV+aSG0hlEy77z$whV=50VFq~F+S?~bMM3$%KOVTqfWhNyu%%(NgYx4P4Wv)P
zg+VkUr6;(qLY2maQKo{kX{~H+!9JZ`T+lL^ojW%N*AS)Q+s~h~z)maz;On1bcIcsz
zVK8h_RB`|45`YG(flB7*jZU|r@~^ToSd9zd(NWO#yOc2aiynP?oQbiVAe
z-)FfC2#IjTas~zcz&bPXD{SAn^Fu>J!-o%;b{>aRiNi6^w4K@jyx3vF=drcj=O!eu
zfBzC_I3FJ$1anNPEH?Ojw{6d@1ouVM!sJ7_2O?kw1A_{f??tu4y}~61_o}I@^GH@z
za%n@D!x03^ZP>tu9t(qED545K6|Myw@ExJdRILEYM(`_+eE$wX;;JgCduq+m*(Tx`
z%dg*g7OSI>p(Nno!Gj?&F@Jg
z>e3XPD6R&>`Qwv%YWvbP$cfx9{H-+$Vp6+>JV^`Tq4Q5b2OyYKy;da&TaSz*%rS
z^;cgX6Ekyv|1U>$rRYUro??Bhgh$m;jDR?x2cXu;o0-AjVOVl=a$c~tExFM20LHIf
zchMAlbKK#?*qH0a<$74IU9!1$oqLdv7I0DGN
zfa8r1LCQ2JuGHgrRbAaeB`ZZtxk7G6M$o`63@mLE6)k}FfS!eDlDrq&k%B09NMSua
z2P7g=8l)FMg{>CJVHDXl#y#_d0=hWv9B>H*#RG>eA&o;`2O1zXfo1+zukKqNk^x;4
zKtBU8sjbC>-N8Gc9qAayuC1>Rxc
zu2w;uFnw~W0Q?W~B?jWoIA3iCUqb(c+W`-Su?Qa*y6rT=72_4~L-E4QM~`|-J!GV|
zPoi;#Ct-hx@;7)oG<=x1Ac{Fpo-okU6T$>a8OBIK95DI~fd^a