CKB Pulse

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

Separate builds for test-only contract constants实践来自一次修复

来自一次修复 · 核对结果:部分正确 · 核对于 2026-11-19

Put test variants that change protocol constants behind a Cargo feature, built as a separate binary with its own code hash and deployment file. Client deployment parsing and deploy scripts should reject that variant on mainnet. Off-chain code should read the constant from the deployment rather than hardcode the default.

为什么重要: If off-chain code assumes the default constant while the deployed script enforces the test value, heartbeat jobs are funded for the wrong term. A test binary could also be wired into a mainnet deployment by mistake.

代码模式

#[cfg(feature="drill")] const GRACE_SECONDS: u64 = 600; build into separate target dir/output path; parseDeployment throws if network_id==0 && (drill || grace_seconds!=86400); heartbeatJob(..., graceSeconds(d))

同一提交中改动了测试

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

概念
Testing and devnet, Cell deps and script lookup, Type ID and upgrades
证据
来自一次修复: 来自一个项目,已对照其提交核对
首次出现
2026-11-16
最近改动
2026-11-16
最近核对
2026-11-19
对照提交的核对结果
部分正确:核心属实,但有一部分表述松散或范围过宽

来源(1)

更多关于Rust scripts and ckb-std

查看此主题的全部 35 条

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

引用这条经验
LusoCryptoLabs, "Separate builds for test-only contract constants", CKB lessons, https://pulse.lusocryptolabs.com/learned/scripts/separate-builds-for-test-only-contract-constants, CC BY 4.0, last changed 2026-11-16.

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