Jason @0xbbbb_eth
Account Abstraction Developer
MEV Researcher
Core Contributor of Panta Rhei
Account Abstraction
gas pricing questions
how to approach revocations
There was a bit of pushback on the call by wallet developers, saying this would make certain use cases more complex, or impossible.
Blob
This tool allows users to monitor the state of the blob mempool through their execution client.
Some things it does
Tracking of Viable Blobs in the mempool
Tracking of fees and tips
Tracking inclusion rates of blob transactions by the rollup along with the builder.
Improve blob fee mechanism
Blob Inversion: An Investigation Into the June 20th 2024 Blob Spike
Adding a maxPriorityFeePerBlobGas or similar so that L2s can more effectively price on a per blob basis instead of using maxPriorityFeePerGas.
Changing the replacement/speedup policies for type 3 transactions. Right now protocols must double their priority fee to do a speedup transaction. Perhaps we need a different penalty here or allow users to update the gas parameters only of a type 3 transaction without needing to repropagate the blob itself.
Changes to the mempool policy for blobs. As Bert Kellerman points out, the mempool policies might be too restrictive and cause unnecessary delays in blob confirmation time.
Increasing the supply side by accepting more than 6 blobs per block. This is already under active consideration.
Changing the max amount of blobs per type 3 transaction. Perhaps allowing 5-6 blobs per type 3 transaction makes the knapsack problem for block builders too restrictive and actually hurts L2s chances of getting on-chain.
Some threads
EIP-7706: Create a separate basefee and gaslimit for calldata
The current tip is per execution gas, so for type 0/2 you know the rate the tx is paying *before* executing.
But, when using the current priority fee to tip for blobs, miners won't know the tip per blob until *after* executing.
Blob fee market is broken
First Broken (Arbitrum LayerZero Airdrop | June 20, 2024)
Blob Inversion: An Investigation Into the June 20th 2024 Blob Spike
The Blob Base Fee spiked to 8,000 GWEI, making blobdata (type 3 transactions) more expensive than calldata (type 2 transactions) for the second time since the Dencun upgrade.
During the inversion event, L2s incurred an estimated overpayment of ~166 ETH (approximately $550,000 USD) by including data in batches sent to Ethereum as blobdata instead of calldata.
Arbitrum (automatically switch)
Arbitrum LayerZero airdrop → Arbitrum posted more batches (priority fee: 1-4 GWEI, high block pending time)
Zksync (automatically switch)
OP Mainnet (manually switch)
Op posted more batches as well (priority fee: 4-8 GWEI → 256 GWEI,replacing batch transactions by double priority fee, low block pending time)
Base (minimal signs of changing their batch posting behavior)
Scroll (stop posting)
Taiko (must keep posting in order to keep the chain moving, slowed down their batch transactions by 30-50%)
Second Broken (Blast Airdrop | June 27, 2024)
Preconfs
Enabling preconfirmations ~certainly removes the pure "based" property of based rollups.
Pre-confirmation Liveness Slashing Penalties from the Proposer's Perspective
Parallel Execution
MEV
Censorship Resistance
Others
A deep dive into how The Burn© affects the network ownership of stakers & non-stakers!
ZK Coprocessor and Lagrange State Commitment
If you need to bridge from an optimistic rollup and do not want to wait for the challenge window, you can use the Lagrange State Committee (LSC) to bypass this.
LSC: restaked committee to attest to state root for Optimistic Rollup, provide fast mode for OR
If you need to query data onchain but want to do it more efficiently, you can use the ZK Coprocessor.