AllowPostingBatchWithOnlyBatchPostingReport config #2657
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
cla-bot
bot
added
the
s
diegoximenes
force-pushed
the
allow_only_posting_batch_posting_report
branch
from
b3b8501
to
df0da33
Compare
diegoximenes
requested review from
ganeshvanahalli,
Tristan-Wilson and
amsanghi
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.
Resolves NIT-2720.
AllowPostingBatchWithOnlyBatchPostingReport config.
SequencerInbox contract adds a batch posting report to the delayed inbox after a batch is posted to the non delayed inbox.
When AllowPostingBatchWithOnlyBatchPostingReport is set to true, considering that no L2 transactions were created since the last posted batch, the sequencer will read the batch posting report from the delayed inbox and will post a batch only containing the report.
So setting AllowPostingBatchWithOnlyBatchPostingReport to true guarantees that a batch will be posted at least as frequently as batch the batch poster tries to create a batch.
This is going to be useful to avoid allowing validation being permissionless if there have been no assertions created within a 2 week period, behavior which is controlled by Nitro's contracts.