All lessons · Developer tooling · Start here · Glossary
Reset devnets instead of skewing the chain clockWorkingFrom one fix
From one fix · Check: partly right · Checked 2026-11-19
Pushing devnet timestamps ahead leaves the chain clock skewed for every later run, which stalls services that compare the tip with wall time. Reset the devnet for each scenario. At the start, assert that |tip timestamp − now| is small, for example under 600 s.
Why it matters: Without a reset and the precondition, a rerun on the same devnet starts with the chain clock hours or days ahead, so the runners idle and the scenario fails with timeouts instead of a clear message.
Pattern
start-up step that advances median time +1h and mines blocks on a long-lived devnet -> reset the devnet and add a precondition asserting chain-clock skew < 600 s- Concepts
- Testing and devnet, Since and time locks
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-15
- Last changed
- 2026-11-15
- Last checked
- 2026-11-19
- Check against the commit
- partly right: a true core, with a part that is loose or too wide
Sources (1)
- 2026-11-15 · psawyerberlin/ckb-revocable-timelock · more from this project
More about Developer tooling
- Mirror on-chain rules off-chain with mutation tests
- Separate submit and commit verification environments
- ckb-vm-js 0.2.0 (npm) checks header hash instead of rejecting the field
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "Reset devnets instead of skewing the chain clock", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/reset-devnets-instead-of-skewing-the-chain-clock, CC BY 4.0, last changed 2026-11-15.