Skip to content

sequencer: Use higher sequencer drift for Celo#251

Merged
piersy merged 1 commit intocelo9from
karlb/seq-drift
Oct 7, 2024
Merged

sequencer: Use higher sequencer drift for Celo#251
piersy merged 1 commit intocelo9from
karlb/seq-drift

Conversation

@karlb
Copy link
Copy Markdown

@karlb karlb commented Oct 7, 2024

@karlb karlb marked this pull request as ready for review October 7, 2024 11:14
Comment on lines +30 to +34
// Normal OP chains wait for five confirmations while Celo waits for finalization, which can take
// up to 3 * 32 blocks. So we should allow for more drift to compensate.
// 3 * 32 - 5 = 91 blocks
// 91 * 12s block time = 1092
const maxSequencerDriftCelo = maxSequencerDriftFjord + 1092
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im a bit confused about the logic here.

The op calculation seems like it took the 5 block times = 60s and then multiplied by a factor of 30 to reach 1800. So for us that would be 33212*30 = 34560.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The question is, "do you really want the buffer to be a multiple of the minimum required drift?". I don't think so, but it really depends on unprovable assumptions. See also https://github.com/celo-org/celo-blockchain-planning/issues/629#issuecomment-2396351090 .

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok makes sense, I guess we just don't know how it was calculated, but yes almost 10 hours (34560s) does seem like an excessive time.

@piersy piersy merged commit d3e06af into celo9 Oct 7, 2024
@piersy piersy deleted the karlb/seq-drift branch October 7, 2024 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants