储备证明、负债证明与披露范围雷达

已核验事实

• Binance publishes a public Proof of Reserves page.（来源：binance-por）
• OKX publishes a public Proof of Reserves page.（来源：okx-por）
• Kraken publishes a public Proof of Reserves page.（来源：kraken-por）
• FSB maintains policy work on crypto-assets and global stablecoins that keeps governance and risk controls in scope.（来源：fsb-crypto-stablecoins）
• A POR page alone does not prove a specific user account state, future withdrawals, legal entity coverage or future solvency.（来源：binance-por、okx-por、kraken-por、fsb-crypto-stablecoins）
• The practical comparison should ask about covered assets, liabilities, method, update frequency, verification path and exclusions.（来源：binance-por、okx-por、kraken-por）

来源地图

• Binance：《Proof of Reserves》 https://www.binance.com/en/proof-of-reserves（binance-por，primary=true）
• OKX：《Proof of Reserves》 https://www.okx.com/proof-of-reserves（okx-por，primary=true）
• Kraken：《Proof of Reserves》 https://www.kraken.com/proof-of-reserves（kraken-por，primary=true）
• Financial Stability Board：《Crypto-assets and Global Stablecoins》 https://www.fsb.org/work-of-the-fsb/financial-innovation-and-structural-change/crypto-assets-and-global-stablecoins/（fsb-crypto-stablecoins，primary=false）

决策表

如何阅读这些证据

Covered assets

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：POR scope differs by venue and asset list。这个边界重要，因为公开来源只能证明某个交易所、监管机构或基础设施方发布了控制、方法或政策表面，不能证明私人账户状态、风控引擎未来行为，也不能证明真实事故中的支持可用性。因此用户动作必须具体：record exactly which assets appear in the current disclosure。

NexuAlpha 读者行动前应记录来源 URL、访问时间、产品表面、司法辖区、账户类型和受影响资产。仍未解决的未知项是：assets outside the public page。这个未知项应保留在清单中，而不是被改写成营销式确定结论。实际操作中，应把 Binance、OKX、Kraken、Financial Stability Board 仅作为公开文档证据；只有账户本地日志、交易 ID、平台公告或官方支持答复能支持进一步移动余额、授予权限、更改托管或信任自动化。

Liability side

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：reserves are incomplete without liability context。因此用户动作必须具体：check whether and how customer liabilities are represented。

仍未解决的未知项是：private liability records。

User verification

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：Merkle or user-verification tooling changes the evidence value。因此用户动作必须具体：test verification only without exposing balances or identifiers。

仍未解决的未知项是：account inclusion for all products。

Snapshot timing

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：old snapshots cannot prove current reserves。因此用户动作必须具体：record access time and update cadence。

仍未解决的未知项是：intraday reserve movement。

Entity scope

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：global brands can include multiple legal entities or products。因此用户动作必须具体：identify which entity and product the page covers。

仍未解决的未知项是：jurisdiction-specific exclusions。

Withdrawal readiness

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：POR does not replace operational withdrawal controls。因此用户动作必须具体：combine POR review with address, network and support-state checks。

仍未解决的未知项是：future withdrawal pauses。

Stop rule

关于 crypto exchange proof of reserves liability attestation disclosure radar，已核验边界很窄：stop when scope, liability or verification path is unclear。因此用户动作必须具体：do not convert disclosure into a guarantee。

仍未解决的未知项是：audit methodology changes。

仍需明确的未知项

• assets outside the public page
• private liability records
• account inclusion for all products
• intraday reserve movement
• jurisdiction-specific exclusions
• future withdrawal pauses
• audit methodology changes

实用结论

储备证明页面应被阅读为披露证据，而不是一揽子偿付能力保证。Binance、OKX 与 Kraken 都发布公开 proof-of-reserves 材料，但真正有决策价值的是细节：覆盖哪些资产、是否表示负债、用户能否验证自身纳入、快照更新频率、是否说明审计方或方法、哪些实体或产品不在范围内。本轮 radar 结论是：把 POR 当作托管、负债、治理和提现准备清单中的一个控制，而不是单独结论。 保守做法是把公开证据当作地图，而不是当作许可。下一步永远是更窄的核验任务：证明路由、证明范围、证明账户本地状态，并把所有无证据主张留在决策之外。