#eip7928
eip7928
1,502 views
3 Discussing
Hot
Latest
·
--
Ethereum BALs ExplainedEthereum transactions remain ordered, but many of the accounts and storage slots they need are discovered only while the EVM is already executing.
EIP-7928 addresses that visibility problem with a Block Access List, or BAL, for the complete block.
The list records the accounts and storage locations actually accessed, together with the relevant post-transaction state changes. That gives execution clients a working-set map they can use for parallel disk reads, dependency-aware validation, earlier state-root work and state-reconstruction workflows.
The security boundary matters as much as the performance benefit.
A BAL is not an optional prediction supplied by a user. It is not a replacement for transaction traces, receipts or contract logic. It is also not trusted simply because a builder supplied it.
Clients check the block commitment, validate ordering and structural rules, execute the block, derive the real accesses and require equality with the provided list. Missing or spurious entries can invalidate the block.
BALs therefore make hidden state dependencies visible without changing Ethereum’s canonical transaction order. Independent work can be scheduled together, while conflicting state still respects the correct sequence.
Read the complete TokenToolHub explanation:
https://tokentoolhub.com/eip-7928-block-level-access-lists/
#Ethereum #EIP7928 #blockchain #Web3 #CryptoSecurity
Ethereum BALs Explained
Ethereum transactions remain ordered, but many of the accounts and storage slots they need are discovered only while the EVM is already executing.
EIP-7928 addresses that visibility problem with a Block Access List, or BAL, for the complete block.
The list records the accounts and storage locations actually accessed, together with the relevant post-transaction state changes. That gives execution clients a working-set map they can use for parallel disk reads, dependency-aware validation, earlier state-root work and state-reconstruction workflows.
The security boundary matters as much as the performance benefit.
A BAL is not an optional prediction supplied by a user. It is not a replacement for transaction traces, receipts or contract logic. It is also not trusted simply because a builder supplied it.
Clients check the block commitment, validate ordering and structural rules, execute the block, derive the real accesses and require equality with the provided list. Missing or spurious entries can invalidate the block.
BALs therefore make hidden state dependencies visible without changing Ethereum’s canonical transaction order. Independent work can be scheduled together, while conflicting state still respects the correct sequence.
Read the complete TokenToolHub explanation:
https://tokentoolhub.com/eip-7928-block-level-access-lists/
#Ethereum #EIP7928 #blockchain #Web3 #CryptoSecurity
EIP-7928 addresses that visibility problem with a Block Access List, or BAL, for the complete block.
The list records the accounts and storage locations actually accessed, together with the relevant post-transaction state changes. That gives execution clients a working-set map they can use for parallel disk reads, dependency-aware validation, earlier state-root work and state-reconstruction workflows.
The security boundary matters as much as the performance benefit.
A BAL is not an optional prediction supplied by a user. It is not a replacement for transaction traces, receipts or contract logic. It is also not trusted simply because a builder supplied it.
Clients check the block commitment, validate ordering and structural rules, execute the block, derive the real accesses and require equality with the provided list. Missing or spurious entries can invalidate the block.
BALs therefore make hidden state dependencies visible without changing Ethereum’s canonical transaction order. Independent work can be scheduled together, while conflicting state still respects the correct sequence.
Read the complete TokenToolHub explanation:
https://tokentoolhub.com/eip-7928-block-level-access-lists/
#Ethereum #EIP7928 #blockchain #Web3 #CryptoSecurity
46
·
--
Verified
The Ethereum “Glamsterdam” upgrade is about to go live, the largest protocol change since The Merge
Ethereum’s next batch of feature updates, “Glamsterdam,” is scheduled to be deployed on the mainnet, expected to launch in the second half of 2026. This is the largest-scale protocol change for Ethereum since “The Merge.”
Two core upgrades:
EIP-7732: Embedded Proposer-Builder Separation (ePBS)
Separate the responsibilities of block building and block proposing, directly embedding them into the protocol core. The goal is to eliminate reliance on trust in third-party relays, reduce the space for MEV manipulation, and improve network efficiency.
EIP-7928: Block-level Access Lists (BALs)
Introduce a new data structure that allows validators to declare in advance which accounts and contract data a set of transactions will access. This lays the foundation for parallel transaction processing, enabling the network to handle non-interfering transactions at the same time and significantly increase throughput.
Other improvements:
In terms of developer experience, EIP-7708 makes logs for ETH transfers and burning easier to track, EIP-8024 introduces new opcodes, and EIP-7954 raises the maximum contract size to about 32 KiB. For gas fees, EIP-7778 implements a new gas accounting approach with no refunds, EIP-8037 increases the gas cost for creating states, and EIP-7976 and EIP-7981 respectively increase the costs of calldata and access lists.
Three key goals:
Faster processing (parallelization), greater capacity, and preventing database bloat.
Timeline:
Mainnet launch targeted for the second half of 2026. As of June, the upgrade has entered the final development testnet stage.
Glamsterdam aims to rebuild Ethereum L1’s transaction processing from the ground up, paving the way for the next stage of scaling.
$ETH
{future}(ETHUSDT)
#以太坊 #Glamsterdam #EIP7732 #EIP7928 #ETH
The Ethereum “Glamsterdam” upgrade is about to go live, the largest protocol change since The Merge
Ethereum’s next batch of feature updates, “Glamsterdam,” is scheduled to be deployed on the mainnet, expected to launch in the second half of 2026. This is the largest-scale protocol change for Ethereum since “The Merge.”
Two core upgrades:
EIP-7732: Embedded Proposer-Builder Separation (ePBS)
Separate the responsibilities of block building and block proposing, directly embedding them into the protocol core. The goal is to eliminate reliance on trust in third-party relays, reduce the space for MEV manipulation, and improve network efficiency.
EIP-7928: Block-level Access Lists (BALs)
Introduce a new data structure that allows validators to declare in advance which accounts and contract data a set of transactions will access. This lays the foundation for parallel transaction processing, enabling the network to handle non-interfering transactions at the same time and significantly increase throughput.
Other improvements:
In terms of developer experience, EIP-7708 makes logs for ETH transfers and burning easier to track, EIP-8024 introduces new opcodes, and EIP-7954 raises the maximum contract size to about 32 KiB. For gas fees, EIP-7778 implements a new gas accounting approach with no refunds, EIP-8037 increases the gas cost for creating states, and EIP-7976 and EIP-7981 respectively increase the costs of calldata and access lists.
Three key goals:
Faster processing (parallelization), greater capacity, and preventing database bloat.
Timeline:
Mainnet launch targeted for the second half of 2026. As of June, the upgrade has entered the final development testnet stage.
Glamsterdam aims to rebuild Ethereum L1’s transaction processing from the ground up, paving the way for the next stage of scaling.
$ETH
#以太坊 #Glamsterdam #EIP7732 #EIP7928 #ETH
Ethereum’s next batch of feature updates, “Glamsterdam,” is scheduled to be deployed on the mainnet, expected to launch in the second half of 2026. This is the largest-scale protocol change for Ethereum since “The Merge.”
Two core upgrades:
EIP-7732: Embedded Proposer-Builder Separation (ePBS)
Separate the responsibilities of block building and block proposing, directly embedding them into the protocol core. The goal is to eliminate reliance on trust in third-party relays, reduce the space for MEV manipulation, and improve network efficiency.
EIP-7928: Block-level Access Lists (BALs)
Introduce a new data structure that allows validators to declare in advance which accounts and contract data a set of transactions will access. This lays the foundation for parallel transaction processing, enabling the network to handle non-interfering transactions at the same time and significantly increase throughput.
Other improvements:
In terms of developer experience, EIP-7708 makes logs for ETH transfers and burning easier to track, EIP-8024 introduces new opcodes, and EIP-7954 raises the maximum contract size to about 32 KiB. For gas fees, EIP-7778 implements a new gas accounting approach with no refunds, EIP-8037 increases the gas cost for creating states, and EIP-7976 and EIP-7981 respectively increase the costs of calldata and access lists.
Three key goals:
Faster processing (parallelization), greater capacity, and preventing database bloat.
Timeline:
Mainnet launch targeted for the second half of 2026. As of June, the upgrade has entered the final development testnet stage.
Glamsterdam aims to rebuild Ethereum L1’s transaction processing from the ground up, paving the way for the next stage of scaling.
$ETH
#以太坊 #Glamsterdam #EIP7732 #EIP7928 #ETH
1
1.6k
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number
Trending Topics
1
#BTCBreaks80K
151,785 views
2,413 Discussing
2
#BitcoinMarketCapTopsTesla
594 views
66 Discussing
3
#SOLJumpsAbout10%
7,650 views
238 Discussing
4
#EthereumReclaims$2600
713 views
32 Discussing
5
#SECReceivesAmendedInjectiveETFFiling
6,376 views
241 Discussing
6
#SanDiskToJoinSP100OnSep21
4,786 views
149 Discussing
7
#PolygonToDeployContractBurning100MPOL
3,577 views
124 Discussing
8
#TRMReportsYouTubeScamStole274.6ETH
1,591 views
44 Discussing
9
#YahooFinanceEndsPolymarketPartnership
2,439 views
45 Discussing
10
#BuffettBecomesBerkshireChairmanEmeritus
39,296 views
734 Discussing