EIP-7928 for Glamsterdam
This post represent the official proposal of EIP-7928: Block-level Access Lists for the Glamsterdam hardfork.
Read More →Unlock parallel transaction execution on Ethereum
See how EIP-7928 transforms transaction processing
Execute multiple transactions simultaneously by knowing state dependencies upfront
Track state changes (incl. ETH balances) without executing transactions
Reconstruct state without executing transactions using post-execution values
Mandatory access lists ensure complete and accurate state dependency information
Every block includes a complete record of all state interactions:
Key benefits for validators:
Cheatsheets for Validators:
BlockAccessList(
account_changes=[
# Alice's account after sending 1 ETH
AccountChanges(
address=0xaaaa...,
balance_changes=[
BalanceChange(tx_index=0, post_balance=50 ETH)
],
nonce_changes=[
NonceChange(tx_index=0, new_nonce=10)
]
),
# Bob's account after receiving 1 ETH
AccountChanges(
address=0xbbbb...,
balance_changes=[
BalanceChange(tx_index=0, post_balance=11 ETH)
]
),
# Coinbase gets transaction fees
AccountChanges(
address=0xeeee...,
balance_changes=[
BalanceChange(tx_index=0, post_balance=100.01 ETH)
]
)
]
)
Latest insights on Block-Level Access Lists
This post represent the official proposal of EIP-7928: Block-level Access Lists for the Glamsterdam hardfork.
Read More →Exploring how BALs enable parallel transaction execution by providing comprehensive state access information at the block level.
Read More →Analyzing worst-case BAL sizes and how to generate them. This includes a detailed analysis of the worst-case BAL size for different scenarios, bloating different parts of the BAL.
Read More →Deep dive into transaction dependencies and how understanding them unlocks efficient parallel processing capabilities.
Read More →Analyzing a different, more lightweight BAL design that achieves perfect parallelization for most average blocks, but not for worst-cases.
Read More →Dive deeper into "where we are today?". The pages provide a tracker to follow progress on the EIP, from specs to production-ready implementation..
Read More →Read the full technical specification
Join the community discussion
Technical implementation details
Technical implementation details
Reference implementation and analysis
Raw up-to-date block-level access lists for research and testing.