Jason @0xbbbb_eth
Account Abstraction Developer
MEV Researcher
Core Contributor of Panta Rhei
Account & Chain Abstraction
ModuleKit - build, test and deploy smart account modules
ModulesSandbox - an open source frontend playground to test a module
OneBalance: chain abstraction stack
Bringing Credible Accounts to Web3 in order to abstract away sprawling fragmentation.
An interface for cross chain trade execution systems | ERC-7683 Cross Chain Intents
Everything About Account Abstraction: Zyfi Raises $2M for zkSync…
Inclusion Lists
Preconfs
Preconfirmations: On splitting the block, mev-boost compatibility and relays
what do people think of Justin's take for cap efficiency on preconf bonds?
PBS
MEV
Cryptoeconomics
Developer
Transient Storage: Transience offers methods for writing and reading transient storage without having to use assembly/Yul.
Reentrancy Awareness: Transience keeps track of the current call depth, preventing a reentrant function call from overwriting its parent's transient storage location.
Blob
Blob Usage Strategies by Rollups and Non-rollup Applications
The main applications using blobs are rollups, accounting for approximately 87%. Non-rollup applications mainly include Blobscriptions and customized type 3 transactions.
Rollup applications choose different blob usage strategies according to their own situations. The strategies will consider the number of blobs carried by type 3 transactions, blob utilization, and blob submission frequency to balance the costs of availability data fees and delay costs.
Non-rollup applications can be characterized and distinguished from rollup applications by the number of blobs carried by type 3 transactions, blob utilization, and blob submission frequency. These features help identify scenarios of blob abuse, allowing for the design of corresponding anti-abuse mechanisms.
In most cases, using blobs as a data availability solution is more cost-effective than calldata. However, there are a few scenarios where calldata is cheaper: blob gas price spikes and blob utilization is extremely low.
Short-term fluctuations in blob gas price is mainly influenced by the demand from non-rollup applications. Rollup applications have a relatively inelastic demand for blobs, so they do not significantly impact short-term fluctuations in blob gas prices.
Currently, rollup applications do not seem to consider blob gas price as a reference factor in their blob usage strategies.
The probability of blocks containing type 3 transactions being reorganized is extremely low. Additionally, carrying more blobs does not increase the probability of block reorganization. However, there is a clustering phenomenon in block height for blocks containing type 3 transactions.
Blob Adoption and Utilization - Insights from the first 85 days - HackMD
77.97% of on-chain Type 3 transaction volume is collectively submitted by 25 different Layer 2 protocols (L2s).
72% of Type 3 transactions carry only 1 blob.
On average, Type 3 transactions with 1 posted blob use 23.3% of available storage, while Type 3 transactions with 6 posted blobs use 99.1%.
Type 3 transactions take 2.1 times longer to confirm on-chain than non-Type 3 transactions
0.12% of total on-chain blob transactions were sent privately. 99% of Lisk on-chain volume was detected to be private.
Median MaxPriorityFeePerGas for Type 3 transactions has hovered around 1 GWEI.
Around June 4, 2024, the median MaxPriorityFeePerGas rose to 4 GWEI. This was the first occurrence of Type 3 tip contention between several L2s.
On average, a MaxPriorityFeePerGas of more than 1 GWEI does not have a faster on-chain time than a MaxPriorityFeePerGas of less than 1 GWEI.
But, even though the zkSync airdrop has passed, we can see that blob activity is still hugging close to the target and will likely cross that boundary again soon.