全部经验 · Apps and UI · 从这里开始 · 术语表
Resolving cell deps per cell after redeploying a data-hashed script实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
After a data/data1 type script is redeployed with a new code hash, old cells still run against the old code. Keep a list of retired deployments and query the indexer for every one. Pick each cell's cell dep by matching the codeHash and hashType of that cell's own type script, not a single 'current' manifest entry.
为什么重要: Indexer scans and holdings filters keyed only to the newest code hash miss every cell made under the replaced contract. A transaction built with the newest contract's cell dep for such a cell is built against the wrong code, and the app's checker refuses it.
代码模式
manifest.scripts[name] used for every cell → resolve per cell: deployments.find(d => d.codeHash===cell.type.codeHash && d.hashType===cell.type.hashType)同一提交中改动了测试
它与修复在一起,我们没有运行它。
- toastmanAu/daowow:
apps/web/test/app-shell.test.js,apps/web/test/helpers/fake-chain.js,apps/web/test/manifest.test.js,apps/web/test/model-claim-guard.test.js,apps/web/test/round-cells.test.js
- 概念
- Cell deps and script lookup, Type ID and upgrades, Indexer queries and cell collection
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-17
- 最近改动
- 2026-11-17
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-17 · toastmanAu/daowow · 这个项目的更多经验
更多关于Apps and UI
- Lock-based fallback when a stored out point goes stale
- Exact CKB-to-shannon conversion with BigInt
- Nervos DAO hold time with term-locked withdrawals
引用这条经验
LusoCryptoLabs, "Resolving cell deps per cell after redeploying a data-hashed script", CKB lessons, https://pulse.lusocryptolabs.com/learned/apps/resolving-cell-deps-per-cell-after-redeploying-a-data-hashed, CC BY 4.0, last changed 2026-11-17.