Why isn’t Blob Gaz Ethereum’s future?

Connection table

Summary and 1st Introduction

2. Background

   2.1 Collection

   2.2 EIP-4844

   2.3 (vector authority)

3. Data

   3.1 Consensus Safety Data

   3.2 Ethereum usage data

   3.3 Collection Data

   3.4 BLOB Gas Fee Data

4. Empirical Results

   4.1 Consensus Safety

   4.2 Use of Ethereum

   4.3 Collection Transactions

   4.4 BLOB Gas Fee Market

5. Results and references

A. Consensus Safety Data

B. Data Collection Collection

C. BLOB GAS BASE FEE AND GAS FEE DETAILED MODEL RESULTS

D. BLOB Gas Printing Fee and Blob Gas Priority Fee Detailed Var Model Results

E. Rollup Processing Dynamics

3.3 Collection Data

In order to assess the effect of EIP-4844 on the collection process dynamics, we conducted a comprehensive analysis that focuses on the changes in the collection process volumes and the delays between the collection and ethereum blocks. The analysis time covers 100,000 blocks before and after the application of EIP-4844.

Our data has been obtained from transactions sent with well -known collection addresses in Ethereum Network. Among the various types of transactions initiated by the Tops, we have collected collective processing processes, which squeeze all individual collection. These operations are very important to ensure user security by reducing the risk of operator and protecting user funds. Collective processing usually reflects the basic roles in collecting income and user interactions before other types of processing such as proofing and finalizing operations. We see it as the solution of the time stamp of the party transaction sent to Ethereum and calculate the delay by taking the difference from the time stamp of the collection block.

The following joint process has been used to obtain data about collection and user delays:

(1) Filter the filter collection process from Ethereum Mainnet using the known recovery sending addresses.

(2) Solve the data obtained from public collective processes.

(3) Integrate with this data (2) to receive collection block data from external sources and to analyze user delays and process metrics.

Figure 4 shows an example of our data collection process and pre -processing for arbitration blocks.

Each collection uses unique coding mechanisms that are often replaced by updates such as span-yalı mechanisms.[37]It has demonstrated important code -solving difficulties. In addition, fast block times and large data volumes such as arbitration (0.26 seconds) and optimism (2 seconds) required the use of special tools and methods for data collection and analysis, as full nodes could not be maintained for all the recovery.

We used various collection explorers and collective code -solving tools designed for each collection special needs. The details of certain tools and data resources used are given in Additional Table 9. Our analysis has focused on six collection (arbitrum one, optimism, base, starknet, zksync period and linea) where we can obtain code -solved party transaction data.

3.4 BLOB Gas Fee Data

In order to conduct a comprehensive analysis of the BLOB Gas Fee Mechanism, we collected data on the use of gas and BLOB gas for each transaction in the selected blocks as well as basic fees for BLOB gas from our Erigon Archive node. In order to explore the new BLOB gas market, we especially analyzed data from 19.518,097 to 19.587.588 blocks, while the BLOB gas base fee exceeded 0.1 GWEI.

BLOB GAS MARKET PERIOD The Blob Gas Base Fee Update Rule Sets the base fee up when the average usage exceeds three mixtures per block. Considering the gradual purchase of the Blobs with recovery and limited use by DAPPS, BLOB Gas Base fee was usually around 1 Wei for a significant period.

Our analysis focuses on the period that corresponds to the increasing BLOB activity, where basic wages are above 0.1 GWEI. This period began in the 19,518,097 block, which was triggered by the activation of BLOB reference services, which briefly increased the BLOB base fee. Although the demand is withdrawn and the basic fee returns to 1 WeI with a block of 19.587,588, fluctuations in this range are very important to understand the potential reactions of the BLOB Gas Fee Market to the increasing PAPP participation. Focusing on this period allows detailed examination of the behavior of the BLOB gas fee market under the conditions of active stain use.

BLOB gas priority fee. Unlike the gas fee update update rule, where users can set maximum priority fee per gas unit, the BLOB gas fee mechanism lacks this function. In the Blob gas market, there is a basic fee that is automatically set according to network blockage. Users, as shown in Figure 5, indirectly determine a BLOB gas priority fee.

In order to effectively evaluate the BLOB gas printing fee updating rule, it is very important to measure the excessive demand for the BLOB gas. In the traditional gas market, the priority fee of a transaction is an indication of how well the base fee reflects the real user demand. As a result, we have developed a new metric to represent the BLOB gas priority fee using the following formula:

We define the following parameters for each block that contains multiple operations:

BLOB can be expressed before gas for each process as follows:

In order to find implicit priority fees for BLOB GAS, we used the median priority fee of the other transactions in the same block for the gas priority fee and we have removed from the total fee paid.