-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eth_createAccessList Support #4081
Comments
Hey @AusIV thanks for the suggestion, we were running into some weird issues with Berlin, but think we've got most of it sorted out. We can definitely look into adding this as an rpc method! |
Realising there is very little documentation surround this call.. looking into it, but not sure if it will be included in the next release |
Tracking Open RPC addition ethereum/execution-specs#196 |
It's probably worth calling out that in my mind this would ideally be something along the lines of:
Not just a simple exposure of:
(I'm also not sure if it's possible to send an access list through |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
I'd hate to see this go stale. Any prospects on this? |
Hey there @AusIV, just wanted to let you know that I'm currently looking into this to gauge the feasibility of implementing what you've requested |
* Init web3.eth.createAccessList * Init e2e test for createAccessList * Add createAccessList method to method wrappers for contracts * Update failing tests to use dynamic address * Add check to not run tests if ENV not Geth * Add createAccessList to docs * Update CHANGELOG.md * Update docs/web3-eth-contract.rst * Update docs/web3-eth-contract.rst * Update docs/web3-eth-contract.rst * Update docs/web3-eth-contract.rst * Update docs/web3-eth-contract.rst * Update docs/web3-eth.rst * Remove duplicate line in CHANGELOG * Move CHANGELOG addition to 1.6.1
Any update on this? it's been a while. |
With the Berlin hard fork, access lists were added to offset some of the gas costs introduced with EIP-2929.
Geth supports eth_createAccessList to generate the input to transactions.
I have a contract that is currently broken by EIP-2929 (which I realize is not a web3.js problem), and while eth_createAccessList would resolve our problem, there's not an easy way to use it in the context of web3.js.
It would be great to have web3.js explicitly support eth_createAccessList, but if somebody has a guide on how to use eth_createAccessList with web3.js without explicit support that would be most welcome.
The text was updated successfully, but these errors were encountered: