⚪$BLOB is the first blobcoin on Arbitrum! 🤓Here to educate and spread the word regarding EIP4844 and its impact on the Ethereum ecosystem
⚪$BLOB is the first blobcoin on Arbitrum! 🤓Here to educate and spread the word regarding EIP4844 and its impact on the Ethereum ecosystem
Subscribe to BLOB
Subscribe to BLOB
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Welcome back, Blobs!
This is the first article of a series of educational posts regarding all things Dencun, EIP4844 and lower tx fees on Ethereum L2s.
Here, we will discuss the Dencun Upgrade at a high level, explaining all the changes it’ll bring to Ethereum, both on its Execution Layer and its Consensus Layer.
EIP-1 describes it as:
EIP stands for “Ethereum Improvement Proposal“.
EIPs are design documents providing information to the Ethereum community, or describing a new feature for Ethereum or its processes or environment!
Anyone can start a conversation, regarding a change they wish to make on Ethereum, on a forum like Ethereum Magicians or Ethereum Research: once an agreement about the idea has been reached, the author may write the EIP, following the process described in EIP-1.
Ever since Ethereum underwent The Merge (a.k.a. “Paris Upgrade”), Ethereum has been operating with 2 distinct, isolated layers: the “execution layer“ and “consensus layer“.
The layers serve different functions, and together they form the PoS version of the Ethereum blockchain:
Execution Layer (EL): Is responsible for applying changes brought by transactions to the blockchain.
If you’re wondering “wtf does that mean??“, let’s see it with an example!
Take the case in which Alice wants to swap 10 WETH for BLOB: Alice will, of course, have to send a transaction to the Ethereum blockchain, specifying to trade her WETH for BLOB. When Alice’s transaction is included in the blockchain, the Execution Layer is the one responsible for executing all necessary code (the coin swap on the Sushiswap pair) and update Alice’s coin balances and approvals, effectively modifying the blockchain’s database!
💡 Essentially, you must imagine the Execution Layer as Ethereum’s engine, which makes its wheels turn as users do stuff on the blockchain!
Consensus Layer (CL): is responsible for making all blockchain nodes agree with each other. Given that blockchains are supported by a network of distributed participants, such participants (often called “nodes“) must all agree on what the blockchain looks like! In case this wasn’t to happen and the Ethereum nodes were to disagree, then we’d be in a world in which it’d be possible that part of Ethereum believes Alice holds 10 WETH and another part of Etherum belives Alice has no WETH balance!
💡 Imagine the Consensus Layer as Etheruem’s steering wheel, which defines the next road the entire Ethereum blockchain will take!
🗝️ Key takeaway🗝️
Exeuction and Consensus layers are separate and independent, maintained by different teams!
Dencun = Deneb + Cancun
Because of the fact that Ethereum is now composed by 2 independent layers, both layers must undergo their own modifications, in order to support large-scale changes (like EIP4844!).
As a result, large upgrades will now require upgrades to both layers! Because of this, the Ethereum Core developers like to refer to the general Ethereum upgrade with a name which is obtained by merging together the names of each Layer’s upgrade
Shapella = Shanghai (EL) + Capella (CL)
Dencun = Cancun (EL) + Deneb (CL)
🎈 Fun fact 🎈
EL upgrades take names of cities🏙️, while CL upgrades take names of stars ✨
Now that we understand the two major parts of Dencun, lets break into them!
Deneb, the CL upgrade, will include 5 EIPs.
Cancun will include 6 EIPs.
EIP-4788: Beacon block root in the EVM
This EIP will add a “proof“ of the Consensus Layer’s conditions and make it available to smart contracts on Ethereum (which live on the Execution Layer!).
Systems like staking pools, restaking protocols and bridges will benefit from improved trust assumptions when operating.
EIP-4844: Shard Blob Transactions 💖
This EIP introduces a new transaction format for “blob-carrying transactions“. This new transaction format will be employed by L2 networks such as Arbitrum and Optimism to post their own L2 transactions on Ethereum in a compressed format. The improvement will also create a separate fee market for these transactions - this means that Ethereum users and L2 networks will not compete in the Ethereum fee market, but rather each will have its own gas price!
🎯 We will see this EIP more in detail in a future post! 🎯
EIP-7044: Perpetuall Valid Signed Voluntary Exits
This EIP brings a quality-of-life improvement for Ethereum validators operating with split credentials, making it easier to withdraw a validator’s stake in the case in which the validation credentials are held separately from the withdrawal credentials.
🤓 Curious readers may learn more about this EIP here
EIP-7045: Increase Max Attestation Inclusion Slot
This EIP will extend the maximum time in which an attestation may be submitted for a proposed Ethereum block.
💡 Attestations are “votes“ that validators cast in favor of a proposed block: enough votes determine whether the new block will be accepted and added to the blockchain or not!
EIP-7514: Add Max Epoch Churn Limit
This EIP intends to introduce a limit to the “
EIP-1153: Transient Storage Opcodes
This EIP will introduce TLOAD AND TSTORE opcodes to the Ethereum Virtual Machine.
These will be used to specify that some smart contract data is transient: it will return to its original value before the transaction finishes! This means that smart contracts will be able to have storage that will only change within a transaction! At the end of a transaction, such storage will return to its original conditions!
💡 Many contracts and protocols will benefit from these, as the gas cost for variables used in reentrancy guards will decrease! (reentrancy guards are variables set to an initial value, which is modified during a transaction’s execution, and which are reset to the initial value at the end of the transaction)
EIP-4788: Beacon Block Root in the EVM
This EIP interests both the CL and EL. Its been discussed above!
EIP-4844: Shard Blob Transactions💖
Our beloved EIP-4844, has already been discussed in the Deneb section!
EIP-5656: MCOPY - Memory Copying Opcode
This EIP will introduce MCOPY opcode to the Ethereum Virtual Machine, allowing to copy a segment of memory and writing it to a different section of memory, during a smart contract execution.
EIP-6780: SELFDESTRUCT Only in the Same Transaction
This EIP is part of the master plan to deprecate SELFDESTRUCT. It will change the behaviour of this opcode to delete the account only in the case in which it is executed in the same transaction that creates a smart contract!
💡
Congratulations Blob! You made it to the end! 🏁Revising what we learned about today, we:
Introduced EIPs
Learned about the distinction between Ethereum’s Execution and Consensus layers
Understood what Dencun means
Learned about the Consensus Layer changes coming to Ethereum in Dencun
Learned about the Execution Layer changes coming to Ethereum in Dencun
🧠 Not bad, Blob! 🧠
In the next post of the series, we’ll delve into how L2s function in the pre-Dencun era and understand why EIP-4844 was first introduced, what issues it solves for L2 networks and the road it paves for additional future scaling efforts!
As a final note, if you enjoyed this blog post, please consider following our blog and our X account ! Or drop by our telegram community and say “Hi!“, we’d love to see you there!
onwards and upwards, Blobs
PEEPanEIP : an awesome youtube playlist dedicated to EIP, Network Upgrades & Ethereum research sharing! Inside, you’ll find ~130 videos (30m to 1h long) in which authors of EIPs are interviewed and asked to explain the EIP at hand!
eips.ethereum.org : here you’ll find all formal EIPs, which can be fairly complex and tech-heavy!
⚠️ To read about a specific EIP, search the following link https://eips.ethereum.org/EIPS/eip-XXXX , after having changed the XXXX with the EIPs number, like so : https://eips.ethereum.org/EIPS/eip-4844
EIP-7569 : this EIP is a meta EIP (i.e. : an EIP about EIPs) which serves to track all things regarding the Dencun upgrade, monitor this page to know when Dencun will be activated on different Ethereum networks!
Welcome back, Blobs!
This is the first article of a series of educational posts regarding all things Dencun, EIP4844 and lower tx fees on Ethereum L2s.
Here, we will discuss the Dencun Upgrade at a high level, explaining all the changes it’ll bring to Ethereum, both on its Execution Layer and its Consensus Layer.
EIP-1 describes it as:
EIP stands for “Ethereum Improvement Proposal“.
EIPs are design documents providing information to the Ethereum community, or describing a new feature for Ethereum or its processes or environment!
Anyone can start a conversation, regarding a change they wish to make on Ethereum, on a forum like Ethereum Magicians or Ethereum Research: once an agreement about the idea has been reached, the author may write the EIP, following the process described in EIP-1.
Ever since Ethereum underwent The Merge (a.k.a. “Paris Upgrade”), Ethereum has been operating with 2 distinct, isolated layers: the “execution layer“ and “consensus layer“.
The layers serve different functions, and together they form the PoS version of the Ethereum blockchain:
Execution Layer (EL): Is responsible for applying changes brought by transactions to the blockchain.
If you’re wondering “wtf does that mean??“, let’s see it with an example!
Take the case in which Alice wants to swap 10 WETH for BLOB: Alice will, of course, have to send a transaction to the Ethereum blockchain, specifying to trade her WETH for BLOB. When Alice’s transaction is included in the blockchain, the Execution Layer is the one responsible for executing all necessary code (the coin swap on the Sushiswap pair) and update Alice’s coin balances and approvals, effectively modifying the blockchain’s database!
💡 Essentially, you must imagine the Execution Layer as Ethereum’s engine, which makes its wheels turn as users do stuff on the blockchain!
Consensus Layer (CL): is responsible for making all blockchain nodes agree with each other. Given that blockchains are supported by a network of distributed participants, such participants (often called “nodes“) must all agree on what the blockchain looks like! In case this wasn’t to happen and the Ethereum nodes were to disagree, then we’d be in a world in which it’d be possible that part of Ethereum believes Alice holds 10 WETH and another part of Etherum belives Alice has no WETH balance!
💡 Imagine the Consensus Layer as Etheruem’s steering wheel, which defines the next road the entire Ethereum blockchain will take!
🗝️ Key takeaway🗝️
Exeuction and Consensus layers are separate and independent, maintained by different teams!
Dencun = Deneb + Cancun
Because of the fact that Ethereum is now composed by 2 independent layers, both layers must undergo their own modifications, in order to support large-scale changes (like EIP4844!).
As a result, large upgrades will now require upgrades to both layers! Because of this, the Ethereum Core developers like to refer to the general Ethereum upgrade with a name which is obtained by merging together the names of each Layer’s upgrade
Shapella = Shanghai (EL) + Capella (CL)
Dencun = Cancun (EL) + Deneb (CL)
🎈 Fun fact 🎈
EL upgrades take names of cities🏙️, while CL upgrades take names of stars ✨
Now that we understand the two major parts of Dencun, lets break into them!
Deneb, the CL upgrade, will include 5 EIPs.
Cancun will include 6 EIPs.
EIP-4788: Beacon block root in the EVM
This EIP will add a “proof“ of the Consensus Layer’s conditions and make it available to smart contracts on Ethereum (which live on the Execution Layer!).
Systems like staking pools, restaking protocols and bridges will benefit from improved trust assumptions when operating.
EIP-4844: Shard Blob Transactions 💖
This EIP introduces a new transaction format for “blob-carrying transactions“. This new transaction format will be employed by L2 networks such as Arbitrum and Optimism to post their own L2 transactions on Ethereum in a compressed format. The improvement will also create a separate fee market for these transactions - this means that Ethereum users and L2 networks will not compete in the Ethereum fee market, but rather each will have its own gas price!
🎯 We will see this EIP more in detail in a future post! 🎯
EIP-7044: Perpetuall Valid Signed Voluntary Exits
This EIP brings a quality-of-life improvement for Ethereum validators operating with split credentials, making it easier to withdraw a validator’s stake in the case in which the validation credentials are held separately from the withdrawal credentials.
🤓 Curious readers may learn more about this EIP here
EIP-7045: Increase Max Attestation Inclusion Slot
This EIP will extend the maximum time in which an attestation may be submitted for a proposed Ethereum block.
💡 Attestations are “votes“ that validators cast in favor of a proposed block: enough votes determine whether the new block will be accepted and added to the blockchain or not!
EIP-7514: Add Max Epoch Churn Limit
This EIP intends to introduce a limit to the “
EIP-1153: Transient Storage Opcodes
This EIP will introduce TLOAD AND TSTORE opcodes to the Ethereum Virtual Machine.
These will be used to specify that some smart contract data is transient: it will return to its original value before the transaction finishes! This means that smart contracts will be able to have storage that will only change within a transaction! At the end of a transaction, such storage will return to its original conditions!
💡 Many contracts and protocols will benefit from these, as the gas cost for variables used in reentrancy guards will decrease! (reentrancy guards are variables set to an initial value, which is modified during a transaction’s execution, and which are reset to the initial value at the end of the transaction)
EIP-4788: Beacon Block Root in the EVM
This EIP interests both the CL and EL. Its been discussed above!
EIP-4844: Shard Blob Transactions💖
Our beloved EIP-4844, has already been discussed in the Deneb section!
EIP-5656: MCOPY - Memory Copying Opcode
This EIP will introduce MCOPY opcode to the Ethereum Virtual Machine, allowing to copy a segment of memory and writing it to a different section of memory, during a smart contract execution.
EIP-6780: SELFDESTRUCT Only in the Same Transaction
This EIP is part of the master plan to deprecate SELFDESTRUCT. It will change the behaviour of this opcode to delete the account only in the case in which it is executed in the same transaction that creates a smart contract!
💡
Congratulations Blob! You made it to the end! 🏁Revising what we learned about today, we:
Introduced EIPs
Learned about the distinction between Ethereum’s Execution and Consensus layers
Understood what Dencun means
Learned about the Consensus Layer changes coming to Ethereum in Dencun
Learned about the Execution Layer changes coming to Ethereum in Dencun
🧠 Not bad, Blob! 🧠
In the next post of the series, we’ll delve into how L2s function in the pre-Dencun era and understand why EIP-4844 was first introduced, what issues it solves for L2 networks and the road it paves for additional future scaling efforts!
As a final note, if you enjoyed this blog post, please consider following our blog and our X account ! Or drop by our telegram community and say “Hi!“, we’d love to see you there!
onwards and upwards, Blobs
PEEPanEIP : an awesome youtube playlist dedicated to EIP, Network Upgrades & Ethereum research sharing! Inside, you’ll find ~130 videos (30m to 1h long) in which authors of EIPs are interviewed and asked to explain the EIP at hand!
eips.ethereum.org : here you’ll find all formal EIPs, which can be fairly complex and tech-heavy!
⚠️ To read about a specific EIP, search the following link https://eips.ethereum.org/EIPS/eip-XXXX , after having changed the XXXX with the EIPs number, like so : https://eips.ethereum.org/EIPS/eip-4844
EIP-7569 : this EIP is a meta EIP (i.e. : an EIP about EIPs) which serves to track all things regarding the Dencun upgrade, monitor this page to know when Dencun will be activated on different Ethereum networks!
SELFDESTRUCTEIP-7516: BLOBBASEFEE Opcode
This EIP introduces the BLOBBASEFEE opcode, which returns the current data-blob base-fee.Similarly to how transaction fees work on Ethereum today, data-blob transactions will be priced using an elastic base fee mechanism, which will determine the total gas price of sending such transactions!Just like the normal transactions base fee, the blob base fee will progressively increase if the number of blob transactions surpasses a target number of transactions, and progressively decrease if it’s under such target!
SELFDESTRUCTEIP-7516: BLOBBASEFEE Opcode
This EIP introduces the BLOBBASEFEE opcode, which returns the current data-blob base-fee.Similarly to how transaction fees work on Ethereum today, data-blob transactions will be priced using an elastic base fee mechanism, which will determine the total gas price of sending such transactions!Just like the normal transactions base fee, the blob base fee will progressively increase if the number of blob transactions surpasses a target number of transactions, and progressively decrease if it’s under such target!
No activity yet