-
Notifications
You must be signed in to change notification settings - Fork 81
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(batcher): send batcher transaction right before KromaMPTTime #393
base: feat/separate-deposit-tx
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (2)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
bd07942
to
62f7667
Compare
ab1e59a
to
7716f5c
Compare
0ec3c25
to
89ee103
Compare
e87e3bc
to
b08a314
Compare
I have read the rules in .gitmessage and tried various settings for PR titles and commit messages, but the semantic PR check still fails. |
@@ -260,6 +260,10 @@ func (s *channelManager) processBlocks() error { | |||
if s.currentChannel.IsFull() { | |||
break | |||
} | |||
if s.rollupCfg.KromaMPTTime != nil && block.Time() == *s.rollupCfg.KromaMPTTime-s.rollupCfg.BlockTime { | |||
s.currentChannel.channelBuilder.setFullErr(errors.New("reached the block just before KromaMPTTime")) |
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.
It would be nice to declare it in the channel builder file along with the other errors.
if s.rollupCfg.KromaMPTTime != nil && block.Time() == *s.rollupCfg.KromaMPTTime-s.rollupCfg.BlockTime { | ||
s.currentChannel.channelBuilder.setFullErr(errors.New("reached the block just before KromaMPTTime")) |
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.
Since setFullErr is a managed function of the channelBuilder, why not handle this logic in the AddBlock of the channelBuilder?
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.
How about changing the commit name to feat(batcher): send batcher transaction right before KromaMPTTime ?
dcc04fe
to
83a7b05
Compare
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
4b9f74f
to
1737b2b
Compare
3473ad1
to
dd9255c
Compare
Description
To create the block at the point where a geth reaches KromaMPTTime, the migration must be completed up to the block immediately before the KromaMPTTime block. Since migrations are performed based on the SafeBlock, the batcher needs to be modified to immediately generate and send a batcher transaction covering all blocks up to the block just before KromaMPTTime when it encounters this block.
This PR is related to kroma-network/go-ethereum #121.