Checkpoints
The update that turns completed Squeek blocks into $SQK and funds Staking.
TL;DR
- A checkpoint mints $SQK for settled Squeek blocks completed after the start and funds Staking with all of it.
- Anyone can run a checkpoint and pays its network fee.
- The checkpoint restarts Staking's reward stream immediately.
What does a checkpoint do?
A checkpoint turns completed Squeek blocks into $SQK. It issues the $SQK the issuance schedule sets for those blocks and funds Staking with all of it, picking up where the last checkpoint stopped.
Staking then shares the new $SQK out over the next 20 minutes. Until a checkpoint runs, settled work hasn't reached anyone's rewards.
Who runs checkpoints?
Anyone can submit a checkpoint, and it serves every staker. The caller pays the Ethereum network fee and receives no $SQK; all minted $SQK funds Staking.
Before submitting one, check that a settled round is waiting and weigh it against the estimated fee. Developers can follow the checkpoint procedure.
How much can one checkpoint process?
A large backlog can take several checkpoints, and each continues where the previous one stopped; the checkpoint procedure gives the per-call limit.
Blocks after the schedule ends or the cap is reached advance progress without issuing $SQK.
What happens during a pause or failure?
A checkpoint needs three things: issuance has started, neither the core contract nor Mining is paused, and a new round has settled. Pauses and unavailable services explains who can pause and resume each part.
These pauses leave Staking running: funded $SQK keeps streaming, and you can still claim, withdraw Squeeks and unstake $SQK. A Staking intake pause doesn't block checkpoints either.
A failed checkpoint changes nothing, and the next call starts from the same point. Status fields, errors and transaction checks are in the Build owner actions guide.