Add registry-data subcommand "bytecode" that generates a single bytecode file from hex #7488
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.
Description
This PR adds a new
bytecode
subcommand of theop-chain-ops/cmd/registry-data
command that takes in a single hex-encoded bytecode argument, and saves it to the bytecode directory in the superchain-registry.Example:
Tests
Tested by generating a file. Also tested using an existing bytecode from a genesis.json file to ensure the logic is the same.
Additional context
One of the comments in ethereum-optimism/op-geth/pull/126 was to store the bytecode for the predeploy in the superchain registry repo.