-
Notifications
You must be signed in to change notification settings - Fork 142
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
feat(block): add lazy block time as additional block production trigger in lazy aggregator mode #1643
Conversation
WalkthroughThe recent updates introduce a new configuration option Changes
Recent Review DetailsConfiguration used: CodeRabbit UI Files selected for processing (1)
Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Overview
One problem that chains in lazy aggregator mode have is that there is no way externally to see if the chain is still live without sending new transactions.
The lazy block time adds an additional trigger that can produce a block during long periods of inactivity.
Summary by CodeRabbit
New Features
LazyBlockTime
to customize the time interval for block production in lazy mode when no transactions are present.Enhancements
Testing