Skip to content
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

Handle noTxPool correctly #15

Merged
merged 2 commits into from
Aug 16, 2024
Merged

Handle noTxPool correctly #15

merged 2 commits into from
Aug 16, 2024

Conversation

jinmel
Copy link

@jinmel jinmel commented Aug 14, 2024

  • noTxPool is handled by the caller, of which there are two: CLSync and Driver.
  • noTxPool should be handled in case when there is a specific request from sequencer where there needs to be a upgrade tx that sets noTxPool to perform chain upgrade.

- noTxPool is handled by the caller, of which there are two: CLSync and
  Driver.
- noTxPool should be handled in case when there is a specific request
  from sequencer where there needs to be a upgrade tx that sets noTxPool
  to perform chain upgrade.
attrs.NoTxPool = uint64(attrs.Timestamp) > l1Origin.Time+eq.spec.MaxSequencerDrift(l1Origin.Time)

// For the Ecotone activation block we shouldn't include any sequencer transactions.
if eq.cfg.IsEcotoneActivationBlock(uint64(attrs.Timestamp)) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

so do we not add transactions for the activation block of every fork?

Copy link
Author

Choose a reason for hiding this comment

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

yes it seems so. here is where this snippet comes from.

attrs.NoTxPool = uint64(attrs.Timestamp) > l1Origin.Time+d.spec.MaxSequencerDrift(l1Origin.Time)

@jinmel jinmel merged commit 292bdee into pbs Aug 16, 2024
2 checks passed
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