fix: wrong l2 chain owner and nonce issues #41
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
Ferret-san
pushed a commit
to celestiaorg/nitro-testnode
that referenced
this pull request
Aug 27, 2024
* Fix the L3 node * Add comments for l3node with espresso mode * Fix smoke test * Add l3 node test in smoke test * Separate the l3 test bash * Add flake.nix --------- Co-authored-by: sveitser <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
fixes an issue where the incorrect chain owner is set in the chain config file, leading to unexpected l2 chain owner
the new l2owner private key can be obtained by
also moving to use the token bridge deployer for l1l2 bridge to reduce chance of nonce race
also added l1user, l2user and l3user as nonce race free accounts