全部经验 · CKB node, RPC and indexer · 从这里开始 · 术语表
Verify a self indexed tip against the node's canonical block hash before serving it实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
A locally maintained index of CKB blocks can lag the node or still hold an orphaned block after a reorg, so before serving its tip as an anchor, fetch the node's tip number, wait briefly for the index to reach it, then ask the node for the canonical block hash at the indexed height and refuse (503 with NOT_SYNCED or REORGANIZING) unless it equals the indexed hash. The check narrows the window but is not atomic, so a client that signs over the anchor should also compare it with an independent source.
为什么重要: Without the check, a server whose index lags the node or still holds an orphaned block after a reorg hands clients an anchor that is not the node's current canonical tip. Signatures made over that anchor are then rejected as ANCHOR_INVALID or refer to a block that left the chain.
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- poshboytl/omavote:
web/test/tipcheck.test.ts
- 概念
- Network and RPC reliability, Indexer queries and cell collection
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-08
- 最近改动
- 2026-10-08
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-10-08 · poshboytl/omavote · 这个项目的更多经验
更多关于CKB node, RPC and indexer
- get_live_cell may return "unknown" rather than "dead" for a spent output
- Wait for get_indexer_tip to reach the commit block before re-reading cells
- Check indexer lag with get_indexer_tip before signing
引用这条经验
LusoCryptoLabs, "Verify a self indexed tip against the node's canonical block hash before serving it", CKB lessons, https://pulse.lusocryptolabs.com/learned/node/verify-a-self-indexed-tip-against-the-node-s-canonical-block, CC BY 4.0, last changed 2026-10-08.