Checking Rollup data: How Blobs work with Ethereum

Ethereum’s Rollup Protocol has recently gained popularity and offers a scalable and safe way to process transactions. One of the most important functions that distinguishes rollups from conventional proof-of-work-based architectures is the use of compressed transactions stored in Calldata (Calldata is a kind of data on Ethereum in which each value can be a primitive type, such as Boolean). In this article, we will deal with the review of the Rollup data using Blobs and understand the effects of this process.

Historical context

Before EIP-4844, which was included in the Dencun upgrade, the L1 layer from Ethereum stored all transactions in Calldata. This enabled efficient storage and accessing transaction data without the need for complex storage solutions outside the chain. In the course of the Rollup Protocol, however, it became clear that compressed transaction stacks were more than just a convenient way to save them.

EIP-4844: The new standard

In 2021, EIP-4844 was implemented in Dencun, which introduced a new approach to checking the rollup data. Under this standard, each transaction stack is divided into smaller parts that are referred to as “blobs”, and each blob contains the required call data for this transaction. To check the integrity of these blobs, Ethereum uses a combination of cryptographic techniques.

Use of blobs

If a roll-up node receives a new block from the L1 level, it checks whether the block has been successfully compressed into a stack of transactions using the EIP-4844 standard. Once verified, the node creates a new blob from this transactions and stores it in its on-chain storage.

To check the integrity of the blob, Ethereum uses cryptographic technology called “Hash-based news authentication” (HMAC). This process includes the Hashing of the Calldata of each block with a unique secret key, which is then combined with the blob. The resulting hash is an unchangeable proof that the blob has not been manipulated during the transmission.

How Blobs can be checked

How does Ethereum check the blobs? Here is a step-by-step coating of the process:

• Blob -Creation : Each transaction stack is divided into smaller parts that are referred to as “blobs”.

• Check

  

  : The block receives a review from the L1 layer.

• Blob Hashing : Every blob call data is lashed with a unique secret key.

• Hash combination : The resulting hash is combined with the data of the Blob to create an HMAC.

• Blessed evidence : The final HMAC serves as an unchangeable proof that the blob has not been manipulated.

Diploma

The Ethereum Rollup Protocol is strongly based on compressed transaction stacks, which are then verified using blobs and a combination of cryptographic techniques. This approach offers several advantages over conventional proof-of-work-based architectures, including improved scalability and reduced latency. While the ecosystem is developing, the understanding of how rollups work with blobs is becoming increasingly important for developers, researchers and users who are interested in examining the possibilities of the future upgrades from Ethereum.

Ethereum Private