全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Check indexer lag with get_indexer_tip before signing实践来自一次修复
来自一次修复 · 核对结果:部分正确 · 核对于 2026-11-19
The built-in CKB indexer can trail the chain tip, so cells it returns may be stale. Before signing, compare the block_number from get_indexer_tip with the height from get_tip_header, show a notice when the gap is large, and refuse to sign while it is. daowow flags the indexer as lagging when it is more than 8 blocks behind, and its entry, refund and claim guards refuse to proceed in that state.
为什么重要: Without this check, a transaction can be built and signed on stale indexer cells that may already be spent or changed, so the user signs against a picture of the chain that is no longer true.
代码模式
readIndexerTip: async (r) => BigInt((await r.call("get_indexer_tip", [])).block_number),摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- toastmanAu/daowow:
apps/web/test/app-shell.test.js,apps/web/test/dao-yield.test.js,apps/web/test/model-draw-script.test.js,apps/web/test/model-entry-guard.test.js,apps/web/test/model-refund-guard.test.js
- 概念
- Indexer queries and cell collection, Network and RPC reliability, Transaction building and fees
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-10
- 最近改动
- 2026-11-10
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 部分正确:核心属实,但有一部分表述松散或范围过宽
来源(1)
- 2026-11-10 · toastmanAu/daowow · 这个项目的更多经验
更多关于CKB node, RPC and indexer
- Reconcile a lost send_transaction response by pinned hash, not by rebuilding
- get_live_cell may return "unknown" rather than "dead" for a spent output
- send_transaction error -1111 (PoolRejectedRBF) is a conflict, not "already in pool"
引用这条经验
LusoCryptoLabs, "Check indexer lag with get_indexer_tip before signing", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/check-indexer-lag-with-get-indexer-tip-before-signing, CC BY 4.0, last changed 2026-11-10.