caps/eth.md: define block-level access list (BAL)#264
Conversation
|
@nerolation do we need this merged for devnet-2? |
|
No, I don't think so! |
|
Yep I think this should be renamed to eth/71 |
|
One thing that might be worth considering here is adding a |
|
Ah and could you also open a Networking EIP for this like https://eips.ethereum.org/EIPS/eip-7975? |
|
Do we need to paginate the BALs as well? How far away are the worst case BALs from 10MB? The reads should be dependent on gas limit, so the size of the BALs will grow with growing gas limit |
yeah, depends on gas limit and state pricing but right now we're still quite far from the 10 MiB: at 60M gas limit, we may get BALs of 1 MiB and calldata of 5MiB (ignoring that the BAL may become smaller with the glamsterdam repricing for now; same applies for the worst-case calldata block) - so eth/70 is more pressuring for block bodies right now than for the BAL. |
|
Based on ACD deciding to put this on a devnet and flagging it on ACDT to be reviewed, we can proceed with merging it if your final review is positive, @fjl . |
Add
eth/70eth/71 protocol support for EIP-7928 Block-Level Access Lists (BALs).Changes:
block-access-list-hashfield to block headerGetBlockAccessLists(0x12) andBlockAccessLists(0x13) messages