-
Notifications
You must be signed in to change notification settings - Fork 451
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
PeriodToAllowPostingBatchWithOnlyBatchPostingReport config #2657
Conversation
b3b8501
to
df0da33
Compare
52f6a6c
df0da33
to
52f6a6c
Compare
arbnode/batch_poster.go
Outdated
Dangerous BatchPosterDangerousConfig `koanf:"dangerous"` | ||
ReorgResistanceMargin time.Duration `koanf:"reorg-resistance-margin" reload:"hot"` | ||
CheckBatchCorrectness bool `koanf:"check-batch-correctness"` | ||
PeriodToAllowPostingBatchWithOnlyBatchPostingReport time.Duration `koanf:"period-to-allow-posting-batch-with-only-batch-posting-report"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to find a simpler name.
A batch posting report is automatically added (by the inbox smart-contract) every time a batch is posted. Orbit deployers don't usually understand too well what is a "batch-posting-report". They will experience it as maximum delay between batches even if they are empty.
I want something close to "max-deay" that shows the difference.
Maybe "max-empty-batch-delay"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renamed to max-empty-batch-delay
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Seems to be failing CI now due to merge conflicts of firstMsgTime no longer existing. I think substituting |
…batch with only batch posting report
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Resolves NIT-2720.
PeriodToAllowPostingBatchWithOnlyBatchPostingReport config.
SequencerInbox contract adds a batch posting report to the delayed inbox after a batch is posted to the non delayed inbox.
The sequencer will read the batch posting report from the delayed inbox, and the PeriodToAllowPostingBatchWithOnlyBatchPostingReport config allows the batch poster to post batches that only contain batch posting report messages.
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.