Merge branch 'dev' into 13199-node-clients

Author: m4sterbunny

.all-contributorsrc

@@ -7193,7 +7193,8 @@
       "contributions": [
         "doc",
         "ideas",
-        "bug"
+        "bug",
+        "tool"
       ]
     },
     {
@@ -12204,6 +12205,51 @@
       "contributions": [
         "ideas"
       ]
+    },
+    {
+      "login": "Khemmie-Ray",
+      "name": "Atoyebi Oluwakemi",
+      "avatar_url": "https://avatars.githubusercontent.com/u/89976006?v=4",
+      "profile": "https://github.com/Khemmie-Ray",
+      "contributions": [
+        "maintenance"
+      ]
+    },
+    {
+      "login": "pglekshmi",
+      "name": "pglekshmi",
+      "avatar_url": "https://avatars.githubusercontent.com/u/107828565?v=4",
+      "profile": "https://github.com/pglekshmi",
+      "contributions": [
+        "maintenance"
+      ]
+    },
+    {
+      "login": "abonnaudet-ledger",
+      "name": "abonnaudet-ledger",
+      "avatar_url": "https://avatars.githubusercontent.com/u/71646516?v=4",
+      "profile": "https://github.com/abonnaudet-ledger",
+      "contributions": [
+        "bug"
+      ]
+    },
+    {
+      "login": "JacobSharples",
+      "name": "Jacob Sharples",
+      "avatar_url": "https://avatars.githubusercontent.com/u/45126111?v=4",
+      "profile": "https://github.com/JacobSharples",
+      "contributions": [
+        "content"
+      ]
+    },
+    {
+      "login": "omahs",
+      "name": "omahs",
+      "avatar_url": "https://avatars.githubusercontent.com/u/73983677?v=4",
+      "profile": "https://github.com/omahs",
+      "contributions": [
+        "translation"
+      ]
     }
   ],
   "contributorsPerLine": 7,

.storybook/i18next.ts

@@ -19,6 +19,7 @@ export const ns = [
   "page-learn",
   "page-upgrades",
   "page-developers-index",
+  "page-what-is-ethereum",
 ] as const
 const supportedLngs = Object.keys(baseLocales)
 

README.md

@@ -1166,7 +1166,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/Nottommy11"><img src="https://avatars.githubusercontent.com/u/91304333?v=4?s=100" width="100px;" alt="Thomas"/><br /><sub><b>Thomas</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/commits?author=Nottommy11" title="Documentation">📖</a></td>
     </tr>
     <tr>
-      <td align="center" valign="top" width="14.28%"><a href="https://github.com/plamarque"><img src="https://avatars.githubusercontent.com/u/227828?v=4?s=100" width="100px;" alt="Patrice Lamarque"/><br /><sub><b>Patrice Lamarque</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/commits?author=plamarque" title="Documentation">📖</a> <a href="#ideas-plamarque" title="Ideas, Planning, & Feedback">🤔</a> <a href="https://github.com/ethereum/ethereum-org-website/issues?q=author%3Aplamarque" title="Bug reports">🐛</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/plamarque"><img src="https://avatars.githubusercontent.com/u/227828?v=4?s=100" width="100px;" alt="Patrice Lamarque"/><br /><sub><b>Patrice Lamarque</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/commits?author=plamarque" title="Documentation">📖</a> <a href="#ideas-plamarque" title="Ideas, Planning, & Feedback">🤔</a> <a href="https://github.com/ethereum/ethereum-org-website/issues?q=author%3Aplamarque" title="Bug reports">🐛</a> <a href="#tool-plamarque" title="Tools">🔧</a></td>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/sell50"><img src="https://avatars.githubusercontent.com/u/34224830?v=4?s=100" width="100px;" alt="sell50"/><br /><sub><b>sell50</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/commits?author=sell50" title="Documentation">📖</a></td>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/manuperalta"><img src="https://avatars.githubusercontent.com/u/90803647?v=4?s=100" width="100px;" alt="Manuel Peralta"/><br /><sub><b>Manuel Peralta</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/commits?author=manuperalta" title="Documentation">📖</a></td>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/Riely007"><img src="https://avatars.githubusercontent.com/u/80497350?v=4?s=100" width="100px;" alt="Riely"/><br /><sub><b>Riely</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/commits?author=Riely007" title="Documentation">📖</a> <a href="#translation-Riely007" title="Translation">🌍</a></td>
@@ -1867,6 +1867,13 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/cd-sigma"><img src="https://avatars.githubusercontent.com/u/119534349?v=4?s=100" width="100px;" alt="ciphernova"/><br /><sub><b>ciphernova</b></sub></a><br /><a href="#content-cd-sigma" title="Content">🖋</a></td>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/CodeMongerrr"><img src="https://avatars.githubusercontent.com/u/99281767?v=4?s=100" width="100px;" alt="Aditya Joshi"/><br /><sub><b>Aditya Joshi</b></sub></a><br /><a href="#ideas-CodeMongerrr" title="Ideas, Planning, & Feedback">🤔</a></td>
     </tr>
+    <tr>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/Khemmie-Ray"><img src="https://avatars.githubusercontent.com/u/89976006?v=4?s=100" width="100px;" alt="Atoyebi Oluwakemi"/><br /><sub><b>Atoyebi Oluwakemi</b></sub></a><br /><a href="#maintenance-Khemmie-Ray" title="Maintenance">🚧</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/pglekshmi"><img src="https://avatars.githubusercontent.com/u/107828565?v=4?s=100" width="100px;" alt="pglekshmi"/><br /><sub><b>pglekshmi</b></sub></a><br /><a href="#maintenance-pglekshmi" title="Maintenance">🚧</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/abonnaudet-ledger"><img src="https://avatars.githubusercontent.com/u/71646516?v=4?s=100" width="100px;" alt="abonnaudet-ledger"/><br /><sub><b>abonnaudet-ledger</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/issues?q=author%3Aabonnaudet-ledger" title="Bug reports">🐛</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/JacobSharples"><img src="https://avatars.githubusercontent.com/u/45126111?v=4?s=100" width="100px;" alt="Jacob Sharples"/><br /><sub><b>Jacob Sharples</b></sub></a><br /><a href="#content-JacobSharples" title="Content">🖋</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/omahs"><img src="https://avatars.githubusercontent.com/u/73983677?v=4?s=100" width="100px;" alt="omahs"/><br /><sub><b>omahs</b></sub></a><br /><a href="#translation-omahs" title="Translation">🌍</a></td>
+    </tr>
   </tbody>
 </table>
 

package.json

@@ -34,6 +34,8 @@
     "@emotion/styled": "^11.11.0",
     "@radix-ui/react-navigation-menu": "^1.1.4",
     "@socialgouv/matomo-next": "^1.8.0",
+    "chart.js": "^4.4.2",
+    "chartjs-plugin-datalabels": "^2.2.0",
     "embla-carousel-react": "^7.0.0",
     "ethereum-blockies-base64": "^1.0.2",
     "framer-motion": "^10.13.0",
@@ -50,14 +52,14 @@
     "prism-react-renderer": "1.1.0",
     "prismjs": "^1.27.0",
     "react": "^18.2.0",
+    "react-chartjs-2": "^5.2.0",
     "react-dom": "^18.2.0",
     "react-emoji-render": "^2.0.1",
     "react-i18next": "^13.3.1",
     "react-icons": "^4.10.1",
     "react-lite-youtube-embed": "^2.4.0",
     "react-select": "5.8.0",
     "reading-time": "^1.5.0",
-    "recharts": "^2.7.3",
     "remark-gfm": "^3.0.1",
     "yaml-loader": "^0.8.0"
   },

public/content/developers/docs/apis/javascript/index.md

@@ -29,9 +29,9 @@ Using providers, these libraries allow you to connect to Ethereum and read its d
 **Ethers example**
 
 ```js
-// A Web3Provider wraps a standard Web3 provider, which is
+// A BrowserProvider wraps a standard Web3 provider, which is
 // what MetaMask injects as window.ethereum into each page
-const provider = new ethers.providers.Web3Provider(window.ethereum)
+const provider = new ethers.BrowserProvider(window.ethereum)
 
 // The MetaMask plugin also allows signing transactions to
 // send ether and pay to change state within the blockchain.
@@ -80,7 +80,7 @@ Here's an examples from Ethers
 // Create a wallet instance from a mnemonic...
 mnemonic =
   "announce room limb pattern dry unit scale effort smooth jazz weasel alcohol"
-walletMnemonic = Wallet.fromMnemonic(mnemonic)
+walletMnemonic = Wallet.fromPhrase(mnemonic)
 
 // ...or from a private key
 walletPrivateKey = new Wallet(walletMnemonic.privateKey)

public/content/developers/docs/blocks/index.md

@@ -140,7 +140,7 @@ This implementation differs from proof-of-work based systems where block times a
 
 ## Block size {#block-size}
 
-A final important note is that blocks themselves are bounded in size. Each block has a target size of 15 million gas but the size of blocks will increase or decrease in accordance with network demands, up until the block limit of 30 million gas (2x target block size). The total amount of gas expended by all transactions in the block must be less than the block gas limit. This is important because it ensures that blocks can’t be arbitrarily large. If blocks could be arbitrarily large, then less performant full nodes would gradually stop being able to keep up with the network due to space and speed requirements. The larger the block, the greater the computing power required to process them in time for the next slot. This is a centralizing force, which is resisted by capping block sizes.
+A final important note is that blocks themselves are bounded in size. Each block has a target size of 15 million gas but the size of blocks will increase or decrease in accordance with network demands, up until the block limit of 30 million gas (2x target block size). The block gas limit can be adjusted upwards or downwards by a factor of 1/1024 from the previous block's gas limit. As a result, validators can change the block gas limit through consensus. The total amount of gas expended by all transactions in the block must be less than the block gas limit. This is important because it ensures that blocks can’t be arbitrarily large. If blocks could be arbitrarily large, then less performant full nodes would gradually stop being able to keep up with the network due to space and speed requirements. The larger the block, the greater the computing power required to process them in time for the next slot. This is a centralizing force, which is resisted by capping block sizes.
 
 ## Further reading {#further-reading}
 

public/content/developers/docs/intro-to-ethereum/index.md

@@ -36,7 +36,7 @@ Cryptographic mechanisms ensure that once transactions are verified as valid and
 
 **Ether (ETH)** is the native cryptocurrency of Ethereum. The purpose of ETH is to allow for a market for computation. Such a market provides an economic incentive for participants to verify and execute transaction requests and provide computational resources to the network.
 
-Any participant who broadcasts a transaction request must also offer some amount of ETH to the network as a bounty. The network will award this bounty to whoever eventually does the work of verifying the transaction, executing it, committing it to the blockchain, and broadcasting it to the network.
+Any participant who broadcasts a transaction request must also offer some amount of ETH to the network as a bounty. The network will burn part of the bounty and award the rest to whoever eventually does the work of verifying the transaction, executing it, committing it to the blockchain, and broadcasting it to the network.
 
 The amount of ETH paid corresponds to the resources required to do the computation. These bounties also prevent malicious participants from intentionally clogging the network by requesting the execution of infinite computation or other resource-intensive scripts, as these participants must pay for computation resources.
 

public/content/developers/docs/nodes-and-clients/node-architecture/index.md

@@ -10,13 +10,11 @@ When Ethereum was using [proof-of-work](/developers/docs/consensus-mechanisms/po
 
 The diagram below shows the relationship between the two Ethereum clients. The two clients connect to their own respective peer-to-peer (P2P) networks. Separate P2P networks are needed as the execution clients gossip transactions over their P2P network, enabling them to manage their local transaction pool, whilst the consensus clients gossip blocks over their P2P network, enabling consensus and chain growth.
 
-![](node-architecture2.png)
+![](node-architecture.png)
 
-_This image is borrowed from geth.ethereum.org and uses the Geth logo to represent execution clients - there are other options for the execution client including Erigon, Nethermind, and Besu_.
+_This image is borrowed from besu.hyperledger.org. There are several options for the execution client including Besu, Erigon, Nethermind, and Besu_.
 
-For this two-client structure to work, consensus clients must pass bundles of transactions to the execution client.
-
-The execution client executes the transactions locally to validate that the transactions do not violate any Ethereum rules and that the proposed update to Ethereum’s state is correct. When a node is selected to be a block producer its consensus client instance requests bundles of transactions from the execution client to include in the new block and execute them to update the global state.The consensus client drives the execution client via a local RPC connection using the [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md). 
+For this two-client structure to work, consensus clients must pass bundles of transactions to the execution client. The execution client executes the transactions locally to validate that the transactions do not violate any Ethereum rules and that the proposed update to Ethereum’s state is correct. When a node is selected to be a block producer its consensus client instance requests bundles of transactions from the execution client to include in the new block and execute them to update the global state.The consensus client drives the execution client via a local RPC connection using the [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md). 
 
 ## What does the execution client do? {#execution-client}
 

public/content/translations/fr/developers/docs/scaling/zk-rollups/index.md

@@ -12,7 +12,7 @@ Vous devez avoir lu et compris notre page sur [la mise à l'échelle d'Ethereum]
 
 ## Qu'est-ce que les rollups zero-knowledge ? {#what-are-zk-rollups}
 
-**Les rollups à connaissance nulle (ZK-rollups)**regroupent (« roll up ») les transactions dans des lots qui sont exécutés hors chaîne. Le calcul hors chaîne réduit la quantité de données qui doivent être publiées dans la blockchain. Les opérateurs ZK-rollup soumettent un résumé des modifications requises pour représenter toutes les transactions dans un lot plutôt que d'envoyer chaque transaction individuellement. Ils produisent également [des preuves de validité](/glossary/#validity-proof) pour prouver la justesse de leurs modifications.
+**Les rollups à connaissance nulle (ZK-rollups)** regroupent (« roll up ») les transactions dans des lots qui sont exécutés hors chaîne. Le calcul hors chaîne réduit la quantité de données qui doivent être publiées dans la blockchain. Les opérateurs ZK-rollup soumettent un résumé des modifications requises pour représenter toutes les transactions dans un lot plutôt que d'envoyer chaque transaction individuellement. Ils produisent également [des preuves de validité](/glossary/#validity-proof) pour prouver la justesse de leurs modifications.
 
 L'état du ZK-rollup est maintenu par un contrat intelligent déployé sur le réseau Ethereum. Pour mettre à jour cet état, les nœuds ZK-rollup doivent soumettre une preuve de validité pour vérification. Comme mentionné ci-dessus, la preuve de validité est l'assurance cryptographique que le changement d'état proposé par le rollup correspond au résultat de l'exécution du lot de transactions donné. Cela signifie que les ZK-rollups n'ont besoin que de fournir des preuves de validité pour finaliser les transactions sur Ethereum au lieu de poster toutes les données de transaction sur la chaîne comme les [rollups optimistes](/developers/docs/scaling/optimistic-rollups/).
 

public/content/translations/fr/refi/index.md

@@ -47,7 +47,7 @@ La transition du VCM vers le nouveau **marché numérique du carbone (DCM)** bas
 Les projets ReFi utilisent la technologie de la blockchain pour atténuer de nombreux problèmes du marché traditionnel :
 
 - **La liquidité est concentrée sur un petit nombre de pools** où chacun peut commercer. Les grandes organisations comme les individus peuvent utiliser ces pools sans devoir rechercher manuellement des acheteurs/vendeurs, sans frais de participation ou sans enregistrement préalable.
-- **Toutes les transactions sont enregistrées sur des blockchains publiques**. Le chemin que chaque crédit carbone prend en raison de l'activité de trading est retraçable à jamais dès qu'il est est rendu disponible dans le DCM.
+- **Toutes les transactions sont enregistrées sur des blockchains publiques**. Le chemin que chaque crédit carbone prend en raison de l'activité de trading est retraçable à jamais dès qu'il est rendu disponible dans le DCM.
 - **La rapidité des transactions est quasiment instantanée**. Sécuriser de vastes quantités de crédits carbone via les marchés traditionnels peut prendre des jours ou des semaines, alors que ceci peut être réalisé en quelques secondes dans le DCM.
 - **Les activités de trading ont lieu sans intermédiaires**, qui facturent des fortes commissions. Les crédits carbones numériques représentent une réduction de coût conséquente comparé aux crédits traditionnels.
 - **Le DCM peut passer à l'échelle** et répondre aussi bien aux attentes des individus que des entreprises multinationales.
@@ -60,7 +60,7 @@ Quatre éléments majeurs composent le paysage actuel du DCM :
 
 Une nouvelle vague de projets innovants est en train d'être développée sur des blockchains dans le but de bouleverser les acteurs établis de ce secteur.
 
-2. Ponts carbone, aussi appelées tokeniseurs, fournissent la technologie pour représenter ou transférer les crédits carbones depuis les registres traditionnels vers les DCM. [Toucan Protocol](https://toucan.earth/), [C3](https://c3.app/), and [Moss.Earth](https://moss.earth/) font partie des exemples remarquables.
+2. Ponts carbone, aussi appelés tokeniseurs, fournissent la technologie pour représenter ou transférer les crédits carbones depuis les registres traditionnels vers les DCM. [Toucan Protocol](https://toucan.earth/), [C3](https://c3.app/), and [Moss.Earth](https://moss.earth/) font partie des exemples remarquables.
 3. Les services intégrés offrent des crédits d'évitement ou de suppression de carbone aux utilisateurs finaux afin qu'ils obtiennent le bénéfice environnemental de leur crédit et partagent leur soutien à l'action climatique avec le monde.
 
 Certains, comme [Klima Infinity](https://www.klimadao.finance/infinity) et [Senken](https://senken.io/), proposent une grande variété de projets développés par des tiers et émis conformément à des normes établies telles que Verra ; d'autres, comme [Nori](https://nori.com/), ne proposent que des projets spécifiques développés selon leur propre norme de crédit carbone, qu'ils émettent et pour laquelle ils ont leur propre marché dédié.