全部经验 · CCC (TypeScript SDK) · 从这里开始 · 术语表
Clamp the node's get_fee_rate_statistics median before using it as a fee rate实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 2026-11-19
Do not pass the node's get_fee_rate_statistics median straight to a transaction builder: a high or untrusted endpoint can set the fee rate for every transaction you build. Clamp it between the minimum relay rate (1,000 shannons/KB) and an app-chosen ceiling, and fall back to the minimum if the call fails, accepting that a ceiling below the real market rate can make confirmation slow. openswap used 1,000 to 5,000 shannons/KB (testnet nodes suggested 33,000 to 47,000) plus a 0.01 CKB per-transaction cap.
为什么重要: Without the clamp, order-book transactions paid whatever median the node reported, which on testnet was 33,000 to 47,000 shannons/KB, many times the 1,000 minimum, with no upper bound.
代码模式
const rate=suggested<ORDER_FEE_POLICY.minRate?ORDER_FEE_POLICY.minRate:suggested>ORDER_FEE_POLICY.maxRate?ORDER_FEE_POLICY.maxRate:suggested;摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- toastmanAu/openswap:
frontend/test/fixtures.ts,frontend/test/pools.spec.ts,sdk/test/frontend-fees.test.ts
- 概念
- Transaction building and fees, Network and RPC reliability
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-10-29
- 最近改动
- 2026-10-29
- 最近核对
- 2026-11-19
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-10-29 · toastmanAu/openswap · 这个项目的更多经验
更多关于CCC (TypeScript SDK)
- CCC client cache can keep dropped transactions; check status without cache
- Classifying sendTransaction failures before dropping a pending CKB transaction
- Persist the transaction hash before broadcasting it
引用这条经验
LusoCryptoLabs, "Clamp the node's get_fee_rate_statistics median before using it as a fee rate", CKB lessons, https://pulse.lusocryptolabs.com/learned/ccc/clamp-the-node-s-get-fee-rate-statistics-median-before-using, CC BY 4.0, last changed 2026-10-29.