From 16f3fdc8186df71c749972e4268b8f42c43b4547 Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Sat, 9 Mar 2024 08:50:03 -0800 Subject: [PATCH 01/12] feat: add /roadmap/dencun/ page --- public/_redirects | 4 + public/content/roadmap/dencun/index.md | 121 +++++++++++++++++++++++++ src/lib/utils/md.ts | 1 + 3 files changed, 126 insertions(+) create mode 100644 public/content/roadmap/dencun/index.md diff --git a/public/_redirects b/public/_redirects index ad4df6dd796..8e61fef288b 100644 --- a/public/_redirects +++ b/public/_redirects @@ -171,3 +171,7 @@ /*/staking/withdraws /:splat/staking/withdrawals/ 301! /*/guides/how-to-register-an-ethereum-account /:splat/guides/how-to-create-an-ethereum-account/ 301! + +/*/roadmap/deneb /:splat/roadmap/dencun/ 301! + +/*/roadmap/cancun /:splat/roadmap/dencun/ 301! diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md new file mode 100644 index 00000000000..bece60d1d6f --- /dev/null +++ b/public/content/roadmap/dencun/index.md @@ -0,0 +1,121 @@ +--- +title: Cancun-Deneb (Dencun) FAQ +description: Frequently asked questions regarding the Cancun-Deneb (Dencun) network upgrade +lang: en +--- + +# Cancun-Deneb (Dencun) {#dencun} + +Cancun-Deneb (Dencun) is an upgrade to the Ethereum network which activates **Proto-Danksharding (EIP-4844)**, introducing data **blobs** for cheaper layer 2 (L2) rollup storage. + +A new transaction type enables rollup providers to store data in a more cost-effective manner, in what are known as "blobs", which are guaranteed to be made available to the network, but can be discarded after a couple weeks. + +This significantly reduces the cost of using rollups, limits chain growth, and helps to support more users while maintaining security and a decentralized set of node operators. + +## When do we expect that rollups will reflect lower fees as a result of Proto-Danksharding? {#when} + +- This upgrade is set for activation at start of [epoch](/glossary/#epoch) 269568, occurring on **13-Mar-2024 (UTC)** +- All major rollup providers, such as Arbitrum or Optimism, have signaled that blobs will be supported immediately following the upgrade +- Individual rollup support may vary as each rollup must upgrade to take advantage of the new blob space + +## How can ETH be converted after the hard fork? {#scam-alert} + +- **There is NO need to convert your ETH**. Your account balances will not change, and the ETH you hold will continue to be available in the same form after the upgrade (hard fork). +-  Anyone telling you to upgrade your ETH is attempting to scam you! Users do not need to do anything for this upgrade, and your assets will remain unaffected. + +[More on recognizing and avoiding scams](/security/) + +## What problem is the Dencun network upgrade solving? {#network-impact} + +Dencun primarily addresses **scalability** (handling more users and more transactions) with **affordable fees**, while **maintaining decentralization** of the network. + +The Ethereum community has been taking a "rollup-centric" approach to its growth, which places layer 2 rollups as the primary means to safely support more users. + +Rollup networks handle the _processing_ (or "execution") of transactions separate from Mainnet, and then publish a cryptographic proof of the results back to Mainnet for record keeping. Storing these proofs carries an expense (in the form of [gas](/glossary/#gas)), which prior to Proto-Danksharding had to be stored permanently by all network node operators, making it an expensive task. + +The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data storage for these proofs by only requiring node operators to store this data for about 18 days, after which is can safely be removed to prevent expansion of hardware requirements. + +[More on scaling Ethereum](/roadmap/scaling/) + +## How does this upgrade contribute to the broader Ethereum roadmap? {#roadmap-impact} + +Proto-Danksharding sets the stage for the full implementation of [Danksharding](/roadmap/danksharding/), which splits up the burden of storing rollup data amongst node operators, so each only has to handle a small portion of the total. This will enable significantly more data blobs per block, and help Ethereum grow by another order of magnitude. + +This is critical to [scale Ethereum to support billions of users](/roadmap/scaling/) with affordable fees and more advanced applications, while maintaining a decentralized network of participants. Without this, hardware requirements for node operators would continue to climb over time, requiring more-and-more expensive machinery to operate, pricing out users who would [otherwise participate](/run-a-node/). This would consolidate node operators to a select few who could afford the hardware, hindering decentralization. + +## Does this upgrade affect all Ethereum consensus and validator clients? {#client-impact} + +Yes. Proto-Danksharding (EIP-4844) involves changes to both the execution clients _and_ consensus clients. All production Ethereum clients have released updates to support the upgrade. Node operators must upgrade to a supported version to stay in sync with the chain after the upgrade. [See details on supported client releases](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement#client-releases) + +_Validator_ software is handled by the consensus clients, which have all been updated to accommodate the upgrade. + +## How does Cancun-Deneb (Dencun) affect Goerli or other Ethereum testnets? {#testnet-impact} + +- Devnets, Goerli, Sepolia and Holesky have all undergone the Dencun upgrade and have Proto-Danksharding fully functioning +- Rollup developers can use these networks for EIP-4844 testing +- Most users will be completely unaffected by this change to each testnet + +## What is the economic impact for the included Ethereum Improvement Proposals (EIPs)? {#economic-impact} + +### Cancun (Execution) {#economic-impact-cancun} + +[EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) - *Shard blob transactions (Proto-Danksharding)* + +- Introduction and utilization of blob-space reduces L1 gas demand in the near-term, making all transactions less expensive on average +- Lower L1 gas costs means the amount of ETH burned from transaction fees is also reduced, making ETH less deflationary +- Lower gas costs make the network more accessible to new users and new use cases, reflexively increasing demand for block space over time + +[EIP-7516](https://eips.ethereum.org/EIPS/eip-7516) - *Blob base fee opcode* + +- Introduces a new fee market, similar to the EIP-1559 mechanism, dedicated to pricing blob space +- This offloads demand for traditional L1 block space, reducing fees and reducing the amount of ETH burned on average + +### Deneb (Consensus) {#economic-impact-deneb} + +[EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) - [See above](#economic-impact-cancun) + +[EIP-7044](https://eips.ethereum.org/EIPS/eip-7044) - *Perpetually valid signed voluntary exits* + +- This reduces the trust assumptions for users of pooled staking or staking-as-a-service platforms by providing a self-sovereign means of exiting validator funds without any permission from a third-party node operator +- In the event this encourages more users to stake, the increase in total ETH staked will increase the issuance of new ETH +- In the event users are more likely to exit staking, this will decrease the total ETH staked, reducing the issuance of new ETH + +[EIP-7514](https://eips.ethereum.org/EIPS/eip-7514) - *Add max epoch churn limit* + +- This caps the rate at which new ETH can be staked +- ETH issuance is proportional to the total amount of ETH staked, thus this limitation will slow the potential issuance of new ETH +- This does NOT mean that new validators cannot join, but removes the exponential climb in how many are allowed to join at a time + +## Would this reduce layer 1 (L1) gas fees in any way? {#l1-fee-impact} + +Yes, but significantly less than on layer 2 rollups. A new gas market is introduced exclusively for blob space, for use by rollup providers. This reduces the demand from these rollups for L1 block space, pushing gas prices downward. + +_Although fees on L1 may be reduced by off-loading rollup data to blobs, this upgrade primarily focuses on the reduction of L2 fees. Reduction of fees on L1 (Mainnet) may occur as a second-order effect._ + +- L1 gas reduction will be proportional to adoption/usage of blob data by rollup providers +- L1 gas is likely to remain competitive from non-rollup related activity +- Rollups that adopt the use of blob space will demand less L1 gas, helping push L1 gas fees downward in the near-term +- Blob space is still limited, so if blobs in a block are saturated/full, then rollups may be required to post their data as permanent data again, which will drive L1 and L2 gas prices up + +## Will this reduce fees on other EVM layer 1 blockchains? {#alt-l1-fee-impact} + +No. The benefits of Proto-Danksharding are specific to Ethereum layer 2 rollups that store their proofs on layer 1 (Mainnet). + +Simply being compatible with the Ethereum Virtual Machine (EVM) does not mean that a network will see any benefit from this upgrade. Networks that operate independently of Ethereum (whether EVM compatible or not), such as Polygon PoS, Binance Smart Chain, Solana, Avalanche, or Gnosis Chain, do not store their data on Ethereum and will not see any benefit from this upgrade. + +[More about layer 2 rollups](/layer-2/) + +## More of a visual learner? {#visual-learner} + + + +_Bankless: Blobspace 101 with Domothy_ + +## Further reading {#further-reading} + +- [EIP4844.com](https://www.eip4844.com/) +- [EIP-4844: Shard blob transactions (Proto-Danksharding)](https://eips.ethereum.org/EIPS/eip-4844) +- [Dencun Mainnet Announcement](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement) - _Ethereum Foundation blog_ +- [The Hitchhiker's Guide to Ethereum: Proto-Danksharding](https://members.delphidigital.io/reports/the-hitchhikers-guide-to-ethereum/#proto-danksharding-eip-4844) - _Jon Charbonneau_ +- [Proto-Danksharding FAQ](https://notes.ethereum.org/@vbuterin/proto_danksharding_faq) - _Vitalik Buterin_ +- [An In-depth Explanation of EIP-4844: The Core of the Cancun Upgrade](https://medium.com/@ebunker.io/an-in-depth-explanation-of-eip-4844-the-core-of-the-cancun-upgrade-de7b13761d2c) - _Ebunker_ \ No newline at end of file diff --git a/src/lib/utils/md.ts b/src/lib/utils/md.ts index d4577b25132..2fe35e9c3eb 100644 --- a/src/lib/utils/md.ts +++ b/src/lib/utils/md.ts @@ -252,6 +252,7 @@ const getPostSlugs = (dir: string, files: string[] = []) => { "/privacy-policy", "/roadmap/account-abstraction", "/roadmap/danksharding", + "/roadmap/dencun", "/roadmap/merge/issuance", "/roadmap/pbs", "/roadmap/secret-leader-election", From d6f68e52b19ae6f762560142c8b9e750ffb95e5c Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Mon, 11 Mar 2024 11:19:39 -0700 Subject: [PATCH 02/12] feat: embed Finematics EIP-4844 explainer --- public/content/roadmap/dencun/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index bece60d1d6f..a4920dcff00 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -107,6 +107,10 @@ Simply being compatible with the Ethereum Virtual Machine (EVM) does not mean th ## More of a visual learner? {#visual-learner} + + +_Finematics: Unlocking Ethereum's Scaling, EIP-4844_ + _Bankless: Blobspace 101 with Domothy_ From 79707e33c6c1e767c930a8d70372f385b20e6c8e Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Mon, 11 Mar 2024 13:56:09 -0700 Subject: [PATCH 03/12] feat: add FAQ questions to Dencun page --- public/content/roadmap/dencun/index.md | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index a4920dcff00..c7699eade21 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -37,6 +37,21 @@ The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data s [More on scaling Ethereum](/roadmap/scaling/) +## How is old blob data accessed? {#historical-access} + +While regular Ethereum nodes will always hold the _current state_ of the network, historical blob data can be discarded after ~18 days. Before it can be discarded, Ethereum guarantees that this data has been made available to allows time for all rollup challenge periods to be completed, interested parties to download the data, and the L2 data to be considered finalized. + +Historical blob data my be desired for a variety of reasons, and can be stored and accessed using several decentralized protocols: + +- **Rollup providers** are incentivized to store this data to improve the user experience of their rollup +- **Block explorers** typically run archival nodes that will index and store all of this information for easy historical reference +- **Third-party indexing protocols** such as The Graph can store this data using a decentralized set of node operators using crypto-economic incentives +- **Bittorrent** is a decentralized protocol consisting of volunteers who can hold and serve this data +- **[Ethereum portal network](/developers/docs/networking-layer/portal-network/)** aims to provide access to all Ethereum data through a decentralized network of node operators, by means of splitting up data amongst participants, similar to Bittorrent +- **Individual users** are always free to store their own copy of any data they would like for historical reference + +It is important to note, that recovering historical state of a **1-of-N trust modal**, meaning that you only need _a single honest actor_ to provide the data, and then anyone can verify it to be correct using the current state of the network. + ## How does this upgrade contribute to the broader Ethereum roadmap? {#roadmap-impact} Proto-Danksharding sets the stage for the full implementation of [Danksharding](/roadmap/danksharding/), which splits up the burden of storing rollup data amongst node operators, so each only has to handle a small portion of the total. This will enable significantly more data blobs per block, and help Ethereum grow by another order of magnitude. @@ -86,11 +101,17 @@ _Validator_ software is handled by the consensus clients, which have all been up - ETH issuance is proportional to the total amount of ETH staked, thus this limitation will slow the potential issuance of new ETH - This does NOT mean that new validators cannot join, but removes the exponential climb in how many are allowed to join at a time +## Will all transactions on L2s now use temporary blob space, or will you be able to choose? {#calldata-vs-blobs} + +Rollup transactions are not required to use blob space for their data (though they are economically incentivized to do so). Each can optionally write their data to blobs (guaranteed available for all challenge periods, very cheap) or to smart contract "calldata" (permanent storage, more expensive). Rollup providers will decide which to use based on the current demand for blob space. If blobs are in high demand, the rollup may decide to use calldata to ensure the data is posted in a timely manner. + +Although this decision is likely to be performed behind-the-scenes by rollup providers, it is theoretically possible for a user to choose which storage type to use. This would require the rollup provider to expose this option to the user, which introduces additional complexities when bundling transactions in a cost-effective manner. See individual rollup provider documentation for more details. + ## Would this reduce layer 1 (L1) gas fees in any way? {#l1-fee-impact} Yes, but significantly less than on layer 2 rollups. A new gas market is introduced exclusively for blob space, for use by rollup providers. This reduces the demand from these rollups for L1 block space, pushing gas prices downward. -_Although fees on L1 may be reduced by off-loading rollup data to blobs, this upgrade primarily focuses on the reduction of L2 fees. Reduction of fees on L1 (Mainnet) may occur as a second-order effect._ +_Although fees on L1 may be reduced by off-loading rollup data to blobs, this upgrade primarily focuses on the reduction of L2 fees. Reduction of fees on L1 (Mainnet) may occur as a second-order effect to a lesser extent._ - L1 gas reduction will be proportional to adoption/usage of blob data by rollup providers - L1 gas is likely to remain competitive from non-rollup related activity @@ -122,4 +143,4 @@ _Bankless: Blobspace 101 with Domothy_ - [Dencun Mainnet Announcement](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement) - _Ethereum Foundation blog_ - [The Hitchhiker's Guide to Ethereum: Proto-Danksharding](https://members.delphidigital.io/reports/the-hitchhikers-guide-to-ethereum/#proto-danksharding-eip-4844) - _Jon Charbonneau_ - [Proto-Danksharding FAQ](https://notes.ethereum.org/@vbuterin/proto_danksharding_faq) - _Vitalik Buterin_ -- [An In-depth Explanation of EIP-4844: The Core of the Cancun Upgrade](https://medium.com/@ebunker.io/an-in-depth-explanation-of-eip-4844-the-core-of-the-cancun-upgrade-de7b13761d2c) - _Ebunker_ \ No newline at end of file +- [An In-depth Explanation of EIP-4844: The Core of the Cancun Upgrade](https://medium.com/@ebunker.io/an-in-depth-explanation-of-eip-4844-the-core-of-the-cancun-upgrade-de7b13761d2c) - _Ebunker_ From ffcfb33e1bf84ca1d912b1069bbe483163879ec4 Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Mon, 11 Mar 2024 14:24:09 -0700 Subject: [PATCH 04/12] chore: copy adjustments and typo fixes --- public/content/roadmap/dencun/index.md | 29 +++++++++++++++----------- 1 file changed, 17 insertions(+), 12 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index c7699eade21..2bf2046cdbb 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -14,7 +14,7 @@ This significantly reduces the cost of using rollups, limits chain growth, and h ## When do we expect that rollups will reflect lower fees as a result of Proto-Danksharding? {#when} -- This upgrade is set for activation at start of [epoch](/glossary/#epoch) 269568, occurring on **13-Mar-2024 (UTC)** +- This upgrade is set for activation at the start of [epoch](/glossary/#epoch) 269568, occurring on **13-Mar-2024 (UTC)** - All major rollup providers, such as Arbitrum or Optimism, have signaled that blobs will be supported immediately following the upgrade - Individual rollup support may vary as each rollup must upgrade to take advantage of the new blob space @@ -39,18 +39,22 @@ The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data s ## How is old blob data accessed? {#historical-access} -While regular Ethereum nodes will always hold the _current state_ of the network, historical blob data can be discarded after ~18 days. Before it can be discarded, Ethereum guarantees that this data has been made available to allows time for all rollup challenge periods to be completed, interested parties to download the data, and the L2 data to be considered finalized. +While regular Ethereum nodes will always hold the _current state_ of the network, historical blob data can be discarded after ~18 days. Before it can be discarded, Ethereum guarantees that this data has been made available to all network participants, to allow time for: -Historical blob data my be desired for a variety of reasons, and can be stored and accessed using several decentralized protocols: +- interested parties to download and store the data +- all rollup challenge periods to be completed +- and the rollup transactions to be considered finalized. -- **Rollup providers** are incentivized to store this data to improve the user experience of their rollup -- **Block explorers** typically run archival nodes that will index and store all of this information for easy historical reference -- **Third-party indexing protocols** such as The Graph can store this data using a decentralized set of node operators using crypto-economic incentives -- **Bittorrent** is a decentralized protocol consisting of volunteers who can hold and serve this data +_Historical_ blob data may be desired for a variety of reasons, and can be stored and accessed using several decentralized protocols: + +- **Third-party indexing protocols**, such as The Graph, can store this data using a decentralized set of node operators using crypto-economic incentives +- **Bittorrent** is a decentralized protocol consisting of volunteers who can hold and serve this data for others - **[Ethereum portal network](/developers/docs/networking-layer/portal-network/)** aims to provide access to all Ethereum data through a decentralized network of node operators, by means of splitting up data amongst participants, similar to Bittorrent - **Individual users** are always free to store their own copy of any data they would like for historical reference +- **Rollup providers** are incentivized to store this data to improve the user experience of their rollup +- **Block explorers** typically run archival nodes that will index and store all of this information for easy historical reference, made available to users through a web interface -It is important to note, that recovering historical state of a **1-of-N trust modal**, meaning that you only need _a single honest actor_ to provide the data, and then anyone can verify it to be correct using the current state of the network. +It is important to note, that recovering historical state is a **1-of-N trust modal**, meaning that you only need _a single honest actor_ to provide the data, and then _anyone can verify it_ to be correct using the current state of the network. ## How does this upgrade contribute to the broader Ethereum roadmap? {#roadmap-impact} @@ -76,14 +80,15 @@ _Validator_ software is handled by the consensus clients, which have all been up [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) - *Shard blob transactions (Proto-Danksharding)* -- Introduction and utilization of blob-space reduces L1 gas demand in the near-term, making all transactions less expensive on average +- Introduction and utilization of blob-space reduces L1 gas demand in the near-term, making all transactions less expensive on average ([see L1 fee impact below](#l1-fee-impact)) +- This upgrade primarily affects L2 rollup fees, making them significantly cheaper, but also helps offload some demand for L1 block space - Lower L1 gas costs means the amount of ETH burned from transaction fees is also reduced, making ETH less deflationary -- Lower gas costs make the network more accessible to new users and new use cases, reflexively increasing demand for block space over time +- Lower gas costs make the network more accessible to new users and new use cases, which may reflexively increase demand for block space over time [EIP-7516](https://eips.ethereum.org/EIPS/eip-7516) - *Blob base fee opcode* - Introduces a new fee market, similar to the EIP-1559 mechanism, dedicated to pricing blob space -- This offloads demand for traditional L1 block space, reducing fees and reducing the amount of ETH burned on average +- This helps offload demand for traditional L1 block space, reducing fees and reducing the amount of ETH burned on average ### Deneb (Consensus) {#economic-impact-deneb} @@ -116,7 +121,7 @@ _Although fees on L1 may be reduced by off-loading rollup data to blobs, this up - L1 gas reduction will be proportional to adoption/usage of blob data by rollup providers - L1 gas is likely to remain competitive from non-rollup related activity - Rollups that adopt the use of blob space will demand less L1 gas, helping push L1 gas fees downward in the near-term -- Blob space is still limited, so if blobs in a block are saturated/full, then rollups may be required to post their data as permanent data again, which will drive L1 and L2 gas prices up +- Blob space is still limited, so if blobs within a block are saturated/full, then rollups may be required to post their data as permanent data in the meantime, which would drive L1 and L2 gas prices up ## Will this reduce fees on other EVM layer 1 blockchains? {#alt-l1-fee-impact} From e58f1611203c6c08d768aa5e2b96be685e634d8c Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Tue, 12 Mar 2024 13:31:28 -0700 Subject: [PATCH 05/12] chore: copy updates from code review Co-Authored-By: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Co-Authored-By: Jakub <100724231+konopkja@users.noreply.github.com> --- public/content/roadmap/dencun/index.md | 47 +++++--------------------- 1 file changed, 8 insertions(+), 39 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index 2bf2046cdbb..75f96f1520f 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -6,15 +6,15 @@ lang: en # Cancun-Deneb (Dencun) {#dencun} -Cancun-Deneb (Dencun) is an upgrade to the Ethereum network which activates **Proto-Danksharding (EIP-4844)**, introducing data **blobs** for cheaper layer 2 (L2) rollup storage. +Cancun-Deneb (Dencun) is an upgrade to the Ethereum network which activates **Proto-Danksharding (EIP-4844)**, introducing temporary data **blobs** for cheaper layer 2 (L2) rollup storage. -A new transaction type enables rollup providers to store data in a more cost-effective manner, in what are known as "blobs", which are guaranteed to be made available to the network, but can be discarded after a couple weeks. +A new transaction type enables rollup providers to store data in a more cost-effective manner, in what are known as "blobs". These are guaranteed to be made available to the network for a few weeks, or more precisely, 4096 [epochs](/glossary/#epoch). After this period, blobs are pruned from the network but applications can still verify the validity of their data using proofs. This significantly reduces the cost of using rollups, limits chain growth, and helps to support more users while maintaining security and a decentralized set of node operators. ## When do we expect that rollups will reflect lower fees as a result of Proto-Danksharding? {#when} -- This upgrade is set for activation at the start of [epoch](/glossary/#epoch) 269568, occurring on **13-Mar-2024 (UTC)** +- This upgrade is set for activation at the start of epoch 269568, occurring on **13-Mar-2024 (UTC)** - All major rollup providers, such as Arbitrum or Optimism, have signaled that blobs will be supported immediately following the upgrade - Individual rollup support may vary as each rollup must upgrade to take advantage of the new blob space @@ -31,9 +31,9 @@ Dencun primarily addresses **scalability** (handling more users and more transac The Ethereum community has been taking a "rollup-centric" approach to its growth, which places layer 2 rollups as the primary means to safely support more users. -Rollup networks handle the _processing_ (or "execution") of transactions separate from Mainnet, and then publish a cryptographic proof of the results back to Mainnet for record keeping. Storing these proofs carries an expense (in the form of [gas](/glossary/#gas)), which prior to Proto-Danksharding had to be stored permanently by all network node operators, making it an expensive task. +Rollup networks handle the _processing_ (or "execution") of transactions separate from Mainnet, and then publish a cryptographic proof and/or compressed transaction data of the results back to Mainnet for record keeping. Storing these proofs carries an expense (in the form of [gas](/glossary/#gas)), which prior to Proto-Danksharding had to be stored permanently by all network node operators, making it an expensive task. -The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data storage for these proofs by only requiring node operators to store this data for about 18 days, after which is can safely be removed to prevent expansion of hardware requirements. +The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data storage for these proofs by only requiring node operators to store this data for about 18 days, after which data can be safely removed to prevent expansion of hardware requirements. Because rollups typically have a withdrawal period of 7 days, their security model is unchanged as long as blobs are available on L1 for this duration. The 18 day pruning window provides a significant buffer to this period. [More on scaling Ethereum](/roadmap/scaling/) @@ -64,7 +64,7 @@ This is critical to [scale Ethereum to support billions of users](/roadmap/scali ## Does this upgrade affect all Ethereum consensus and validator clients? {#client-impact} -Yes. Proto-Danksharding (EIP-4844) involves changes to both the execution clients _and_ consensus clients. All production Ethereum clients have released updates to support the upgrade. Node operators must upgrade to a supported version to stay in sync with the chain after the upgrade. [See details on supported client releases](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement#client-releases) +Yes. Proto-Danksharding (EIP-4844) involves changes to both the execution clients and consensus clients. All production Ethereum clients have released updates to support the upgrade. Node operators must upgrade to a supported version to stay in sync with the chain after the upgrade. [See details on supported client releases](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement#client-releases) _Validator_ software is handled by the consensus clients, which have all been updated to accommodate the upgrade. @@ -74,38 +74,6 @@ _Validator_ software is handled by the consensus clients, which have all been up - Rollup developers can use these networks for EIP-4844 testing - Most users will be completely unaffected by this change to each testnet -## What is the economic impact for the included Ethereum Improvement Proposals (EIPs)? {#economic-impact} - -### Cancun (Execution) {#economic-impact-cancun} - -[EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) - *Shard blob transactions (Proto-Danksharding)* - -- Introduction and utilization of blob-space reduces L1 gas demand in the near-term, making all transactions less expensive on average ([see L1 fee impact below](#l1-fee-impact)) -- This upgrade primarily affects L2 rollup fees, making them significantly cheaper, but also helps offload some demand for L1 block space -- Lower L1 gas costs means the amount of ETH burned from transaction fees is also reduced, making ETH less deflationary -- Lower gas costs make the network more accessible to new users and new use cases, which may reflexively increase demand for block space over time - -[EIP-7516](https://eips.ethereum.org/EIPS/eip-7516) - *Blob base fee opcode* - -- Introduces a new fee market, similar to the EIP-1559 mechanism, dedicated to pricing blob space -- This helps offload demand for traditional L1 block space, reducing fees and reducing the amount of ETH burned on average - -### Deneb (Consensus) {#economic-impact-deneb} - -[EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) - [See above](#economic-impact-cancun) - -[EIP-7044](https://eips.ethereum.org/EIPS/eip-7044) - *Perpetually valid signed voluntary exits* - -- This reduces the trust assumptions for users of pooled staking or staking-as-a-service platforms by providing a self-sovereign means of exiting validator funds without any permission from a third-party node operator -- In the event this encourages more users to stake, the increase in total ETH staked will increase the issuance of new ETH -- In the event users are more likely to exit staking, this will decrease the total ETH staked, reducing the issuance of new ETH - -[EIP-7514](https://eips.ethereum.org/EIPS/eip-7514) - *Add max epoch churn limit* - -- This caps the rate at which new ETH can be staked -- ETH issuance is proportional to the total amount of ETH staked, thus this limitation will slow the potential issuance of new ETH -- This does NOT mean that new validators cannot join, but removes the exponential climb in how many are allowed to join at a time - ## Will all transactions on L2s now use temporary blob space, or will you be able to choose? {#calldata-vs-blobs} Rollup transactions are not required to use blob space for their data (though they are economically incentivized to do so). Each can optionally write their data to blobs (guaranteed available for all challenge periods, very cheap) or to smart contract "calldata" (permanent storage, more expensive). Rollup providers will decide which to use based on the current demand for blob space. If blobs are in high demand, the rollup may decide to use calldata to ensure the data is posted in a timely manner. @@ -127,7 +95,7 @@ _Although fees on L1 may be reduced by off-loading rollup data to blobs, this up No. The benefits of Proto-Danksharding are specific to Ethereum layer 2 rollups that store their proofs on layer 1 (Mainnet). -Simply being compatible with the Ethereum Virtual Machine (EVM) does not mean that a network will see any benefit from this upgrade. Networks that operate independently of Ethereum (whether EVM compatible or not), such as Polygon PoS, Binance Smart Chain, Solana, Avalanche, or Gnosis Chain, do not store their data on Ethereum and will not see any benefit from this upgrade. +Simply being compatible with the Ethereum Virtual Machine (EVM) does not mean that a network will see any benefit from this upgrade. Networks that operate independently of Ethereum (whether EVM compatible or not) do not store their data on Ethereum and will not see any benefit from this upgrade. [More about layer 2 rollups](/layer-2/) @@ -149,3 +117,4 @@ _Bankless: Blobspace 101 with Domothy_ - [The Hitchhiker's Guide to Ethereum: Proto-Danksharding](https://members.delphidigital.io/reports/the-hitchhikers-guide-to-ethereum/#proto-danksharding-eip-4844) - _Jon Charbonneau_ - [Proto-Danksharding FAQ](https://notes.ethereum.org/@vbuterin/proto_danksharding_faq) - _Vitalik Buterin_ - [An In-depth Explanation of EIP-4844: The Core of the Cancun Upgrade](https://medium.com/@ebunker.io/an-in-depth-explanation-of-eip-4844-the-core-of-the-cancun-upgrade-de7b13761d2c) - _Ebunker_ +- [AllCoreDevs Update 016](https://tim.mirror.xyz/HzH5MpK1dnw7qhBSmzCfdCIxpwpD6DpwlfxtaAwEFro) - _Tim Beiko_ From 6f5cbd21d3f462f322a687f8f571eb12f9d001f4 Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Tue, 12 Mar 2024 13:37:05 -0700 Subject: [PATCH 06/12] chore: apply suggestions from code review --- public/_redirects | 4 ---- public/content/roadmap/dencun/index.md | 6 +++--- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/public/_redirects b/public/_redirects index 8e61fef288b..ad4df6dd796 100644 --- a/public/_redirects +++ b/public/_redirects @@ -171,7 +171,3 @@ /*/staking/withdraws /:splat/staking/withdrawals/ 301! /*/guides/how-to-register-an-ethereum-account /:splat/guides/how-to-create-an-ethereum-account/ 301! - -/*/roadmap/deneb /:splat/roadmap/dencun/ 301! - -/*/roadmap/cancun /:splat/roadmap/dencun/ 301! diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index 75f96f1520f..02b2df2fddf 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -41,8 +41,8 @@ The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data s While regular Ethereum nodes will always hold the _current state_ of the network, historical blob data can be discarded after ~18 days. Before it can be discarded, Ethereum guarantees that this data has been made available to all network participants, to allow time for: -- interested parties to download and store the data -- all rollup challenge periods to be completed +- interested parties to download and store the data. +- all rollup challenge periods to be completed. - and the rollup transactions to be considered finalized. _Historical_ blob data may be desired for a variety of reasons, and can be stored and accessed using several decentralized protocols: @@ -80,7 +80,7 @@ Rollup transactions are not required to use blob space for their data (though th Although this decision is likely to be performed behind-the-scenes by rollup providers, it is theoretically possible for a user to choose which storage type to use. This would require the rollup provider to expose this option to the user, which introduces additional complexities when bundling transactions in a cost-effective manner. See individual rollup provider documentation for more details. -## Would this reduce layer 1 (L1) gas fees in any way? {#l1-fee-impact} +## Will 4844 reduce L1 gas? {#l1-fee-impact} Yes, but significantly less than on layer 2 rollups. A new gas market is introduced exclusively for blob space, for use by rollup providers. This reduces the demand from these rollups for L1 block space, pushing gas prices downward. From 83525b9a24cba532de89a4d7f601db344479bb5f Mon Sep 17 00:00:00 2001 From: Joshua <62268199+minimalsm@users.noreply.github.com> Date: Wed, 13 Mar 2024 12:44:46 +0000 Subject: [PATCH 07/12] Apply suggestions from code review --- public/content/roadmap/dencun/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index 02b2df2fddf..feb7b5320f2 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -14,13 +14,13 @@ This significantly reduces the cost of using rollups, limits chain growth, and h ## When do we expect that rollups will reflect lower fees as a result of Proto-Danksharding? {#when} -- This upgrade is set for activation at the start of epoch 269568, occurring on **13-Mar-2024 (UTC)** +- This upgrade actives at epoch 269568, on **13-Mar-2024 (UTC)** - All major rollup providers, such as Arbitrum or Optimism, have signaled that blobs will be supported immediately following the upgrade - Individual rollup support may vary as each rollup must upgrade to take advantage of the new blob space ## How can ETH be converted after the hard fork? {#scam-alert} -- **There is NO need to convert your ETH**. Your account balances will not change, and the ETH you hold will continue to be available in the same form after the upgrade (hard fork). +- **There is NO need to convert your ETH** after Ethereum's Dencun upgrade. Your account balances will not change, and the ETH you hold will continue to be available in the same form after the upgrade (hard fork). -  Anyone telling you to upgrade your ETH is attempting to scam you! Users do not need to do anything for this upgrade, and your assets will remain unaffected. [More on recognizing and avoiding scams](/security/) @@ -103,11 +103,11 @@ Simply being compatible with the Ethereum Virtual Machine (EVM) does not mean th -_Finematics: Unlocking Ethereum's Scaling, EIP-4844_ +_Unlocking Ethereum's Scaling, EIP-4844 — Finematics _ -_Bankless: Blobspace 101 with Domothy_ +_Blobspace 101 with Domothy — Bankless_ ## Further reading {#further-reading} From 4edb07e955c12e2cdb8a7898b6ded4c0194c07db Mon Sep 17 00:00:00 2001 From: Joshua <62268199+minimalsm@users.noreply.github.com> Date: Wed, 13 Mar 2024 15:20:24 +0000 Subject: [PATCH 08/12] Copyedits --- public/content/roadmap/dencun/index.md | 62 ++++++++++++++------------ 1 file changed, 33 insertions(+), 29 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index feb7b5320f2..cc89223a912 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -6,22 +6,22 @@ lang: en # Cancun-Deneb (Dencun) {#dencun} -Cancun-Deneb (Dencun) is an upgrade to the Ethereum network which activates **Proto-Danksharding (EIP-4844)**, introducing temporary data **blobs** for cheaper layer 2 (L2) rollup storage. +Cancun-Deneb (Dencun) is an upgrade to the Ethereum network, which activates **Proto-Danksharding (EIP-4844)**, introducing temporary data **blobs** for cheaper layer 2 (L2) rollup storage. -A new transaction type enables rollup providers to store data in a more cost-effective manner, in what are known as "blobs". These are guaranteed to be made available to the network for a few weeks, or more precisely, 4096 [epochs](/glossary/#epoch). After this period, blobs are pruned from the network but applications can still verify the validity of their data using proofs. +A new transaction type enables rollup providers to store data more cost-effectively in what are known as "blobs." Blobs are guaranteed to be available to the network for around 18 days (more precisely, 4096 [epochs](/glossary/#epoch)). After this period, blobs are pruned from the network, but applications can still verify the validity of their data using proofs. -This significantly reduces the cost of using rollups, limits chain growth, and helps to support more users while maintaining security and a decentralized set of node operators. +This significantly reduces the cost of rollups, limits chain growth, and helps to support more users while maintaining security and a decentralized set of node operators. -## When do we expect that rollups will reflect lower fees as a result of Proto-Danksharding? {#when} +## When do we expect rollups to reflect lower fees due to Proto-Danksharding? {#when} -- This upgrade actives at epoch 269568, on **13-Mar-2024 (UTC)** -- All major rollup providers, such as Arbitrum or Optimism, have signaled that blobs will be supported immediately following the upgrade -- Individual rollup support may vary as each rollup must upgrade to take advantage of the new blob space +- This upgrade activates at epoch 269568, on **13-Mar-2024 at 13:55PM (UTC)** +- All major rollup providers, such as Arbitrum or Optimism, have signalled that blobs will be supported immediately following the upgrade +- The timeline for individual rollup support may vary, as each provider must update their systems to take advantage of the new blob space ## How can ETH be converted after the hard fork? {#scam-alert} -- **There is NO need to convert your ETH** after Ethereum's Dencun upgrade. Your account balances will not change, and the ETH you hold will continue to be available in the same form after the upgrade (hard fork). --  Anyone telling you to upgrade your ETH is attempting to scam you! Users do not need to do anything for this upgrade, and your assets will remain unaffected. +- **No Action Required for Your ETH**: Following the Ethereum Dencun upgrade, there is no need to convert or upgrade your ETH. Your account balances will remain the same, and the ETH you currently hold will remain accessible in its existing form after the hard fork. +- **Beware of Scams!**  **anyone instructing you to "upgrade" your ETH is trying to scam you.** There is nothing you need to do in relation to this upgrade. Your assets will stay completely unaffected. Remember, staying informed is the best defense against scams. [More on recognizing and avoiding scams](/security/) @@ -31,42 +31,42 @@ Dencun primarily addresses **scalability** (handling more users and more transac The Ethereum community has been taking a "rollup-centric" approach to its growth, which places layer 2 rollups as the primary means to safely support more users. -Rollup networks handle the _processing_ (or "execution") of transactions separate from Mainnet, and then publish a cryptographic proof and/or compressed transaction data of the results back to Mainnet for record keeping. Storing these proofs carries an expense (in the form of [gas](/glossary/#gas)), which prior to Proto-Danksharding had to be stored permanently by all network node operators, making it an expensive task. +Rollup networks handle the _processing_ (or "execution") of transactions separate from Mainnet and then publish a cryptographic proof and/or compressed transaction data of the results back to Mainnet for record keeping. Storing these proofs carries an expense (in the form of [gas](/glossary/#gas)), which, before Proto-Danksharding, had to be stored permanently by all network node operators, making it an expensive task. -The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data storage for these proofs by only requiring node operators to store this data for about 18 days, after which data can be safely removed to prevent expansion of hardware requirements. Because rollups typically have a withdrawal period of 7 days, their security model is unchanged as long as blobs are available on L1 for this duration. The 18 day pruning window provides a significant buffer to this period. +The introduction of Proto-Danksharding in the Dencun upgrade adds cheaper data storage for these proofs by only requiring node operators to store this data for about 18 days, after which data can be safely removed to prevent expansion of hardware requirements. Because rollups typically have a withdrawal period of 7 days, their security model is unchanged as long as blobs are available on L1 for this duration. The 18-day pruning window provides a significant buffer for this period. [More on scaling Ethereum](/roadmap/scaling/) ## How is old blob data accessed? {#historical-access} -While regular Ethereum nodes will always hold the _current state_ of the network, historical blob data can be discarded after ~18 days. Before it can be discarded, Ethereum guarantees that this data has been made available to all network participants, to allow time for: +While regular Ethereum nodes will always hold the _current state_ of the network, historical blob data can be discarded approximately 18 days after its introduction. Before discarding this data, Ethereum ensures that it has been made available to all network participants, allowing time for: -- interested parties to download and store the data. -- all rollup challenge periods to be completed. -- and the rollup transactions to be considered finalized. +- Interested parties to download and store the data. +- Completion of all rollup challenge periods. +- Finalization of the rollup transactions. -_Historical_ blob data may be desired for a variety of reasons, and can be stored and accessed using several decentralized protocols: +_Historical_ blob data may be desired for a variety of reasons and can be stored and accessed using several decentralized protocols: -- **Third-party indexing protocols**, such as The Graph, can store this data using a decentralized set of node operators using crypto-economic incentives -- **Bittorrent** is a decentralized protocol consisting of volunteers who can hold and serve this data for others -- **[Ethereum portal network](/developers/docs/networking-layer/portal-network/)** aims to provide access to all Ethereum data through a decentralized network of node operators, by means of splitting up data amongst participants, similar to Bittorrent -- **Individual users** are always free to store their own copy of any data they would like for historical reference -- **Rollup providers** are incentivized to store this data to improve the user experience of their rollup -- **Block explorers** typically run archival nodes that will index and store all of this information for easy historical reference, made available to users through a web interface +- **Third-party indexing protocols**, such as The Graph, store this data through a decentralized network of node operators incentivized by crypto-economic mechanisms. +- **BitTorrent** is a decentralized protocol where volunteers can hold and distribute this data to others. +- **[Ethereum portal network](/developers/docs/networking-layer/portal-network/)** aims to provide access to all Ethereum data through a decentralized network of node operators by distributing data among participants akin to BitTorrent. +- **Individual users** are always free to store their own copies of any data they wish for historical reference. +- **Rollup providers** are incentivized to store this data to enhance the user experience of their rollup. +- **Block explorers** typically run archival nodes that index and store all this information for easy historical reference, accessible to users via a web interface. -It is important to note, that recovering historical state is a **1-of-N trust modal**, meaning that you only need _a single honest actor_ to provide the data, and then _anyone can verify it_ to be correct using the current state of the network. +It is important to note that recovering historical state operates on a **1-of-N trust model**. This means that you only need data from _a single trustworthy source_ to verify its correctness using the current state of the network. ## How does this upgrade contribute to the broader Ethereum roadmap? {#roadmap-impact} -Proto-Danksharding sets the stage for the full implementation of [Danksharding](/roadmap/danksharding/), which splits up the burden of storing rollup data amongst node operators, so each only has to handle a small portion of the total. This will enable significantly more data blobs per block, and help Ethereum grow by another order of magnitude. +Proto-Danksharding sets the stage for the full implementation of [Danksharding](/roadmap/danksharding/). Danksharding is designed to distribute the storage of rollup data across node operators, so each operator only needs to handle a small part of the total data. This distribution will increase the number of data blobs per block, which is essential for scaling Ethereum to handle more users and transactions. -This is critical to [scale Ethereum to support billions of users](/roadmap/scaling/) with affordable fees and more advanced applications, while maintaining a decentralized network of participants. Without this, hardware requirements for node operators would continue to climb over time, requiring more-and-more expensive machinery to operate, pricing out users who would [otherwise participate](/run-a-node/). This would consolidate node operators to a select few who could afford the hardware, hindering decentralization. +This scalability is crucial to [supporting billions of users on Ethereum](/roadmap/scaling/) with affordable fees and more advanced applications, while maintaining a decentralized network. Without these changes, the hardware demands for node operators would escalate, leading to the need for increasingly expensive equipment. This could price out smaller operators, resulting in a concentration of network control among a few large operators, which would go against the principle of decentralization. ## Does this upgrade affect all Ethereum consensus and validator clients? {#client-impact} -Yes. Proto-Danksharding (EIP-4844) involves changes to both the execution clients and consensus clients. All production Ethereum clients have released updates to support the upgrade. Node operators must upgrade to a supported version to stay in sync with the chain after the upgrade. [See details on supported client releases](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement#client-releases) +Yes, Proto-Danksharding (EIP-4844) requires updates to both execution clients and consensus clients. All main Ethereum clients have released versions supporting the upgrade. To maintain synchronization with the Ethereum network post-upgrade, node operators must ensure they are running a supported client version. Note that the information about client releases is time-sensitive, and users should refer to the latest updates for the most current details. [See details on supported client releases](https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement#client-releases). -_Validator_ software is handled by the consensus clients, which have all been updated to accommodate the upgrade. +The consensus clients handle the _Validator_ software, which has all been updated to accommodate the upgrade. ## How does Cancun-Deneb (Dencun) affect Goerli or other Ethereum testnets? {#testnet-impact} @@ -76,9 +76,13 @@ _Validator_ software is handled by the consensus clients, which have all been up ## Will all transactions on L2s now use temporary blob space, or will you be able to choose? {#calldata-vs-blobs} -Rollup transactions are not required to use blob space for their data (though they are economically incentivized to do so). Each can optionally write their data to blobs (guaranteed available for all challenge periods, very cheap) or to smart contract "calldata" (permanent storage, more expensive). Rollup providers will decide which to use based on the current demand for blob space. If blobs are in high demand, the rollup may decide to use calldata to ensure the data is posted in a timely manner. +## Will all transactions on L2s now use temporary blob space, or will you be able to choose? {#calldata-vs-blobs} + +Rollup transactions on Layer 2 (L2) of Ethereum have the option of using two types of data storage: temporary blob space or permanent smart contract calldata. Blob space is an economical choice, providing temporary storage at a lower cost. It guarantees data availability for all necessary challenge periods. On the other hand, smart contract calldata offers permanent storage but is more expensive. + +The decision between using blob space or calldata is primarily made by rollup providers. They base this decision on the current demand for blob space. If blob space is in high demand, rollups may opt for calldata to ensure the data is posted in a timely manner. -Although this decision is likely to be performed behind-the-scenes by rollup providers, it is theoretically possible for a user to choose which storage type to use. This would require the rollup provider to expose this option to the user, which introduces additional complexities when bundling transactions in a cost-effective manner. See individual rollup provider documentation for more details. +While it's theoretically possible for users to choose their preferred storage type, rollup providers typically manage this choice. Offering this option to users would add complexity, particularly in cost-effective bundling transactions. For specific details on this choice, users should refer to the documentation provided by individual rollup providers. ## Will 4844 reduce L1 gas? {#l1-fee-impact} From 5500dacbebd1ecd7aa8e1b1189373605c1564244 Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Wed, 13 Mar 2024 10:05:39 -0700 Subject: [PATCH 09/12] chore: copy update --- public/content/roadmap/dencun/index.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index cc89223a912..86591f6aa21 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -86,9 +86,7 @@ While it's theoretically possible for users to choose their preferred storage ty ## Will 4844 reduce L1 gas? {#l1-fee-impact} -Yes, but significantly less than on layer 2 rollups. A new gas market is introduced exclusively for blob space, for use by rollup providers. This reduces the demand from these rollups for L1 block space, pushing gas prices downward. - -_Although fees on L1 may be reduced by off-loading rollup data to blobs, this upgrade primarily focuses on the reduction of L2 fees. Reduction of fees on L1 (Mainnet) may occur as a second-order effect to a lesser extent._ +Not significantly. A new gas market is introduced exclusively for blob space, for use by rollup providers. _Although fees on L1 may be reduced by off-loading rollup data to blobs, this upgrade primarily focuses on the reduction of L2 fees. Reduction of fees on L1 (Mainnet) may occur as a second-order effect to a lesser extent._ - L1 gas reduction will be proportional to adoption/usage of blob data by rollup providers - L1 gas is likely to remain competitive from non-rollup related activity From 0ac08017fa34c36aced238b2866b3bfbaa53119b Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Wed, 13 Mar 2024 10:21:01 -0700 Subject: [PATCH 10/12] chore: add layer 2 glossary tooltip --- public/content/roadmap/dencun/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index 86591f6aa21..c28465ec23b 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -6,7 +6,7 @@ lang: en # Cancun-Deneb (Dencun) {#dencun} -Cancun-Deneb (Dencun) is an upgrade to the Ethereum network, which activates **Proto-Danksharding (EIP-4844)**, introducing temporary data **blobs** for cheaper layer 2 (L2) rollup storage. +Cancun-Deneb (Dencun) is an upgrade to the Ethereum network, which activates **Proto-Danksharding (EIP-4844)**, introducing temporary data **blobs** for cheaper [layer 2 (L2)](/glossary/#layer-2) rollup storage. A new transaction type enables rollup providers to store data more cost-effectively in what are known as "blobs." Blobs are guaranteed to be available to the network for around 18 days (more precisely, 4096 [epochs](/glossary/#epoch)). After this period, blobs are pruned from the network, but applications can still verify the validity of their data using proofs. From 95e08bd7b35583dc867f6bfbe1fc48696e2bcad1 Mon Sep 17 00:00:00 2001 From: Corwin Smith Date: Wed, 13 Mar 2024 16:33:34 -0600 Subject: [PATCH 11/12] remove duplicate heading --- public/content/roadmap/dencun/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index c28465ec23b..3e08f550d8c 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -76,8 +76,6 @@ The consensus clients handle the _Validator_ software, which has all been update ## Will all transactions on L2s now use temporary blob space, or will you be able to choose? {#calldata-vs-blobs} -## Will all transactions on L2s now use temporary blob space, or will you be able to choose? {#calldata-vs-blobs} - Rollup transactions on Layer 2 (L2) of Ethereum have the option of using two types of data storage: temporary blob space or permanent smart contract calldata. Blob space is an economical choice, providing temporary storage at a lower cost. It guarantees data availability for all necessary challenge periods. On the other hand, smart contract calldata offers permanent storage but is more expensive. The decision between using blob space or calldata is primarily made by rollup providers. They base this decision on the current demand for blob space. If blob space is in high demand, rollups may opt for calldata to ensure the data is posted in a timely manner. From d2b1348ca20db9ac74a8705bd9891607db773bf6 Mon Sep 17 00:00:00 2001 From: Corwin Smith Date: Wed, 13 Mar 2024 22:40:34 -0600 Subject: [PATCH 12/12] Fix tense --- public/content/roadmap/dencun/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/content/roadmap/dencun/index.md b/public/content/roadmap/dencun/index.md index 3e08f550d8c..1a45f40b3af 100644 --- a/public/content/roadmap/dencun/index.md +++ b/public/content/roadmap/dencun/index.md @@ -14,7 +14,7 @@ This significantly reduces the cost of rollups, limits chain growth, and helps t ## When do we expect rollups to reflect lower fees due to Proto-Danksharding? {#when} -- This upgrade activates at epoch 269568, on **13-Mar-2024 at 13:55PM (UTC)** +- This upgrade activated at epoch 269568, on **13-Mar-2024 at 13:55PM (UTC)** - All major rollup providers, such as Arbitrum or Optimism, have signalled that blobs will be supported immediately following the upgrade - The timeline for individual rollup support may vary, as each provider must update their systems to take advantage of the new blob space