You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix: sequencer should handle claims correctly when there are empty epochs #8855
See createProofClaimForPreviousEpoch in sequencer.ts. We should not compute epochToProve as the block's slot minus 1, but should ask the rollup (or compute from the rollup's data) what the epoch that needs proving is, and also read the rollup's value of proofClaim to see if a claim exists.
This is also an issue in the prover node: it submits quotes with the wrong epoch to prove when there are empty epochs.
changed the title [-]fix: sequencer should get epoch to prove from rollup[/-][+]fix: sequencer should handle claims correctly when there are empty epochs[/+]on Sep 27, 2024
Activity
[-]fix: sequencer should get epoch to prove from rollup[/-][+]fix: sequencer should handle claims correctly when there are empty epochs[/+]chore: test 4epochs in native-network (#9309)