fix: configure the correct batcher address #188
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
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.
The batcher component uses a private key which does not match the configuration files
intent.toml,rollup.jsonandstate.json.This causes some complications in the the op node operations. Once the sequencer window is passed (3600 seconds), op node will reorg to build virtual L2 blocks from the L1 origin, effectively wiping all L2 state until then.
The reason is that the expected batcher's address does not match to the private key passed to the component.
Additionally, the batcher's account is not prefunded, therefore it cannot post data on L1.
This PR configures the batcher address for op node to be the one which is passed to the batcher and also prefunds this address on L1.
With this change the builder playground stays operational even after the sequencer window of 1 hour passes.
Note
At phylax systems, we used the builder-playground to generate our demo environment for OP-Talos.
During our work we made a small set of changes which are worth suggesting as upstream contributions.
I tried to split the work in several PRs, to let the maintainers decide what is worth to be included.