全部经验 · CCC (TypeScript SDK) · 从这里开始 · 术语表
Verifying an immutable data1 script code cell after deployment实践来自一次修复
来自一次修复 · 核对结果:部分正确 · 核对于 2026-11-19
For a script referenced by hashType 'data1', put the binary in a cell whose lock is the always fail lock (codeHash 32 zero bytes, hashType data1, args 0x, which no code cell can match) and with no type, so the cell can never be spent and the cell dep stays live; the capacity is locked forever. After sending, read the cell with client.getCellLive(outPoint, true) and assert that ccc.hashCkb(outputData) equals the pinned code hash, that the lock equals the always fail lock and that there is no type, ideally on more than one endpoint. The data1 code hash is already pinned by the binary's content; the immutable lock is what keeps the cell available.
为什么重要: If the code cell had a spendable lock, the deployer could consume it, and every transaction using that out point as a cell dep would fail. Without the post-deployment check, a wrong binary, lock or type would be recorded in the manifest unnoticed.
代码模式
assert(code&&ccc.hashCkb(code.outputData)===LOCK_V2.codeHash ...); assert(code.cellOutput.lock.eq(IMMUTABLE_LOCK)&&!code.cellOutput.type,`Code cell is not immutable on ${url}`);摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- toastmanAu/openswap:
frontend/test/fixtures.ts,sdk/test/v2-sdk.test.ts
- 概念
- Cell deps and script lookup, Type ID and upgrades
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-29
- 最近改动
- 2026-10-29
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 部分正确:核心属实,但有一部分表述松散或范围过宽
来源(1)
- 2026-10-29 · toastmanAu/openswap · 这个项目的更多经验
更多关于CCC (TypeScript SDK)
- CCC custom client scripts must include AnyoneCanPay for SignerCkbPrivateKey
- Registering NervosDao on devnet
- Convert Fiber RPC snake_case scripts to CCC camelCase ScriptLike
引用这条经验
LusoCryptoLabs, "Verifying an immutable data1 script code cell after deployment", CKB lessons, https://pulse.lusocryptolabs.com/learned/ccc/verifying-an-immutable-data1-script-code-cell-after-deployme, CC BY 4.0, last changed 2026-10-29.