全部经验 · Developer tooling · 从这里开始 · 术语表
Reset devnets instead of skewing the chain clock实践来自一次修复
来自一次修复 · 核对结果:部分正确 · 核对于 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.
为什么重要: 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.
代码模式
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- 概念
- Testing and devnet, Since and time locks
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-15
- 最近改动
- 2026-11-15
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 部分正确:核心属实,但有一部分表述松散或范围过宽
来源(1)
- 2026-11-15 · psawyerberlin/ckb-revocable-timelock · 这个项目的更多经验
更多关于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
引用这条经验
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.