generators: include prestate bloater for 64 KiB max-sized contracts EIP-7954 - #56
Draft
jochem-brouwer wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This includes 150k accounts, this is vibe coded, but the intent of this PR is: the devnet should be started with 150k accounts of 64 KiB size (so 9.375 GiB of code).
This is the theoretical max of accounts we can read in Fusaka. It is good to test this in a live network.
Deploying these contracts on a live network costs an insane amount of gas, and I actually am not even sure that we can deploy these types of account (this size) in Glamsterdam due to the storage gas (code deposit) repricing in EIP-8037 and the transaction gas limit of EIP-7825. This should nevertheless be part of the stress test, and the intent is to do this with ethpandaops/buildoor
There might be some blockers downstream and I'm also not sure if we can deploy non-Fusaka-compatible accounts via clients, plus if they even support ingesting 9.375 GiB of code (at least double of that of the genesis prestate JSON) directly via genesis.
Will otherwise attempt to find another "solution" for this problem. Deploying this live is not really an option due to the insane gas costs of the deployment (we will block other interesting stress test txs like this)