Skip to content

Conversation

nerolation
Copy link
Contributor

Add EIP-7928: Block-level Access Lists to the execution-specs.

Copy link
Contributor

@SamWilsn SamWilsn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to self, I haven't reviewed the tests yet.

@nerolation
Copy link
Contributor Author

Thanks a lot Sam! Super helpful comments.
I integrated all your proposed changes.

@SamWilsn SamWilsn force-pushed the forks/osaka branch 2 times, most recently from 301eb89 to 5a49b2f Compare July 25, 2025 19:55
@SamWilsn
Copy link
Contributor

I've rebased forks/osaka to pick up the last straggling commits from master. If you do something like this, should be easy enough to resolve the conflicts:

git checkout forks/osaka
git pull
git checkout bals
git reset --hard forks/osaka
git cherry-pick a24d3837cde502cb3133cbe37a5c8871ca516525^..3d986436ca1d9c406a154e3549d3b415ddf88b3b

@SamWilsn
Copy link
Contributor

Actually, there weren't any conflicts. I took the liberty of rebasing your branch. Please confirm everything looks the way it should!

@nerolation
Copy link
Contributor Author

yeah looks good, what I can tell.

…to RLP

- System contracts (parent hash, beacon root) now use block_access_index 0
- Transactions use block_access_index 1 to len(transactions)
- Post-execution changes use block_access_index len(transactions) + 1
- Migrated from SSZ to RLP encoding as per updated EIP-7928 spec
- Updated all tests to match new API and structure
- Replaced tx_index with block_access_index throughout codebase
@gurukamath
Copy link
Contributor

@nerolation Could we close this and continue the BAL work on #1381 ?

@nerolation nerolation closed this Sep 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants