forked from OffchainLabs/nitro
-
Notifications
You must be signed in to change notification settings - Fork 7
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
L2msgs in single tx #178
Closed
Closed
L2msgs in single tx #178
Conversation
This file contains 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
…ersion Require program.version == params.Version when caching
update minInitGas for stylus v2
…_split_l1gas [NIT-2558] Consensus/Execution split: simplifies ConsensusSequencer and ExecutionEngine interfaces
Add sequencer info logs
…uch behind transaction streamer
…sig-checking Remove sig from DAS writer iface, sign in client
pin espresso-sequencer-go to new release v0.0.20
build arbitrator.h on test-go-deps
The logic for fetching keysets and batches was originally all done using GetByHash on the the DASReader interface. Nitro nodes, batch posters, and daservers would all include the ChainFetchReader at the beginning of their chain of DASReaders in order to intercept GetByHash calls and do the lookup of the keyset on L1. It was confusing, however, because it also forwarded GetByHash requests to an inner DASReader, since it had no way of telling if the GetByHash requests were for keysets or batch data. This commit renames the ChainFetchReader to KeysetFetcher and removes the inner DASReader and chaining logic so that it only tries to fetch keysets from L1 or its own internal cache. The orchestration of normal nodes and batch posters is changed to set up the KeysetFetcher separately rather than part of the chain of DASReaders. The replay binary preimage reader still needs to be updated.
…-espresso-integration into forward-l2-message
|
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.
No description provided.