CKB Pulse

全部经验 · Rust scripts and ckb-std · 从这里开始 · 术语表

Median time vs tip timestamp for deadlines实践再次出现

再次出现 · 核对结果:正确 · 核对于 2026-11-19

On-chain since checks use the median time of past blocks, but clients often use the tip header's timestamp, and the two can diverge widely after devnet time travel. Compute deadlines from max(ceil(tipMs/1000), medianSeconds) so minimum-term checks hold on both sides.

为什么重要: If the deadline is computed from the median time alone, a client that measures the minimum term from the tip timestamp rejects the deadline as too short. This happens after devnet time travel, when the tip runs far ahead of the median.

代码模式

deadline = medianSeconds() + term  →  deadline = max(ceil(tipMs/1000), medianSeconds()) + term

同一提交中改动了测试

它与修复在一起,我们没有运行它。

概念
Since and time locks, Testing and devnet
证据
再次出现: 在两个或以上项目中出现
首次出现
2026-11-15
最近改动
2026-11-15
最近核对
2026-11-19
对照提交的核对结果
正确:这条经验出自该提交,并且在今天的代码中仍然成立

来源(3)

更多关于Rust scripts and ckb-std

查看此主题的全部 35 条

你维护这条经验的来源项目吗?请确认或纠正

引用这条经验
LusoCryptoLabs, "Median time vs tip timestamp for deadlines", CKB lessons, https://pulse.lusocryptolabs.com/learned/scripts/median-time-vs-tip-timestamp-for-deadlines, CC BY 4.0, last changed 2026-11-15.

取自公开提交,并对照每条经验的来源提交和项目当前代码做了核对。使用前请先读来源。 文本采用 CC BY 4.0:请署名 LusoCryptoLabs, CKB lessons,并附上经验的链接。 想修改或撤下某条经验?请提交 issue。