Repository navigation
Milestone
Description
When my validator went to build a block, it failed as it was too far into the slot for INITIALIZING_PROPOSAL. See:
[08:37:39.671] INFO: archiver Downloaded L2 block 9571 {"blockHash":{},"blockNumber":9571,"txCount":0,"globalVariables":{"chainId":11155111,"version":3538330213,"blockNumber":9571,"slotNumber":14234,"timestamp":1744619844,"coinbase":"0xf692ec3e193dbf9159ffd5a73a043f1bd3f61b1a","feeRecipient":"0x0000000000000000000000000000000000000000000000000000000000000000","feePerDaGas":0,"feePerL2Gas":0}}
[08:38:03.454] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 3.453s greater than 3s allowance)
[08:38:04.736] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 4.736s greater than 3s allowance)
[08:38:06.005] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 6.005s greater than 3s allowance)
[08:38:07.293] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 7.293s greater than 3s allowance)
[08:38:08.562] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 8.562s greater than 3s allowance)
[08:38:09.869] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 9.869s greater than 3s allowance)
[08:38:11.083] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 11.083s greater than 3s allowance)
[08:38:12.327] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 12.327s greater than 3s allowance)
[08:38:13.716] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 13.716s greater than 3s allowance)
[08:38:14.918] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 14.918s greater than 3s allowance)
[08:38:16.156] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 16.156s greater than 3s allowance)
[08:38:17.426] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 17.426s greater than 3s allowance)
[08:38:18.665] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 18.664s greater than 3s allowance)
[08:38:19.876] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 19.876s greater than 3s allowance)
[08:38:21.089] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 21.089s greater than 3s allowance)
[08:38:22.319] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 22.319s greater than 3s allowance)
[08:38:23.544] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 23.544s greater than 3s allowance)
[08:38:24.829] WARN: sequencer Too far into slot for INITIALIZING_PROPOSAL (time into slot 24.829s greater than 3s allowance)
I don't think we need to be as stringent regarding the timetable at this point of block building. e.g. if our timetable says that we must sync the previous block by 3s and execute by 10s, we could loosen this to say we must sync the block by 8s. We probably still want to give the committee the full 7s to re-execute so we can't reduce any of the following time slots. But me receiving the block a little bit late shouldn't prevent me from building anything.
Metadata
Metadata
Assignees
Labels
No labels
Activity
chore: Less strict block proposal init deadline (#13522)
chore(master): release 0.85.0 (#13297)