Recherche vérifiée par sources: OKX / Kraken
Le corps de l'article est affiché dans sa version anglaise vérifiée. La traduction sera ajoutée après revue des sources.
Verified Fact Boundary
1. OKX publishes proof-of-reserves information with reserve ratios, supported assets and user-verification material. 2. Kraken publishes proof-of-reserves information that describes cryptographic client-balance inclusion and reserve verification. 3. Binance also publishes a proof-of-reserves page, which makes reserve disclosures a comparable category rather than a single-venue feature. 4. FSB materials frame crypto-asset and stablecoin activity as requiring risk, governance and financial-stability controls beyond a single disclosure page. 5. A proof-of-reserves snapshot does not by itself prove future liquidity, unsupported-asset coverage, complete off-chain liabilities or post-snapshot solvency.
Réduire
Decision Matrix
Tableau de l’article : faites défiler horizontalement ou placez le focus sur le tableau et utilisez les flèches.
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Asset coverage | which assets are inside the published reserve set | match the reader's asset to the disclosed list | unsupported balances |
| Snapshot timing | when balances and wallets were measured | record the timestamp before relying on a ratio | post-snapshot events |
| Liability scope | whether user liabilities are included and how | separate customer-balance inclusion from corporate obligations | off-chain obligations |
| Wallet proof | published wallet ownership or address evidence | check wallet evidence without sharing personal data | wallet changes after publication |
| User verification | whether a user can verify inclusion | run the official self-verification flow if needed | private account eligibility |
| Independent assurance | whether third-party attestations or cryptographic proofs are described | read the method before quoting assurance | auditor scope |
| Limitations | what the venue says the proof does not cover | quote limitations beside ratios | omitted product lines |
| Withdrawal relevance | whether the proof informs a withdrawal decision | combine reserve proof with live withdrawal status | future withdrawal stress |
| Evidence packet | official URL, date, asset, snapshot and method | store non-secret evidence only | private balance exposure |
| Stop rule | when comparison is not decision-quality | stop if asset, snapshot, method or liability scope is unclear | future methodology revisions |
Source Map
- OKX: Proof of Reserves (okx-por)
- Kraken: Proof of Reserves (kraken-por)
- Binance: Proof of Reserves (binance-por)
- Financial Stability Board: Crypto-assets and Global Stablecoins (fsb-crypto-assets)
Control Notes
1. Asset coverage
Asset coverage is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means which assets are inside the published reserve set. The useful action is to match the reader's asset to the disclosed list. The unresolved edge is unsupported balances, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, asset coverage should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.
2. Snapshot timing
Snapshot timing is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when balances and wallets were measured. The useful action is to record the timestamp before relying on a ratio. The unresolved edge is post-snapshot events, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, snapshot timing should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
Vérifiez l’éligibilité régionale et les conditions du compte
Ouvrir →3. Liability scope
Liability scope is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether user liabilities are included and how. The useful action is to separate customer-balance inclusion from corporate obligations. The unresolved edge is off-chain obligations, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, liability scope should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
4. Wallet proof
Wallet proof is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means published wallet ownership or address evidence. The useful action is to check wallet evidence without sharing personal data. The unresolved edge is wallet changes after publication, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, wallet proof should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
5. User verification
User verification is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether a user can verify inclusion. The useful action is to run the official self-verification flow if needed. The unresolved edge is private account eligibility, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, user verification should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
6. Independent assurance
Independent assurance is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether third-party attestations or cryptographic proofs are described. The useful action is to read the method before quoting assurance. The unresolved edge is auditor scope, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, independent assurance should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
7. Limitations
Limitations is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means what the venue says the proof does not cover. The useful action is to quote limitations beside ratios. The unresolved edge is omitted product lines, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, limitations should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
8. Withdrawal relevance
Withdrawal relevance is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether the proof informs a withdrawal decision. The useful action is to combine reserve proof with live withdrawal status. The unresolved edge is future withdrawal stress, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
For an operator, withdrawal relevance should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.
9. Evidence packet
Evidence packet is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means official URL, date, asset, snapshot and method. The useful action is to store non-secret evidence only. The unresolved edge is private balance exposure, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
10. Stop rule
Stop rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when comparison is not decision-quality. The useful action is to stop if asset, snapshot, method or liability scope is unclear. The unresolved edge is future methodology revisions, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.
Known Unknowns
- unsupported balances
- post-snapshot events
- off-chain obligations
- wallet changes after publication
- private account eligibility
- auditor scope
- omitted product lines
- future withdrawal stress
- private balance exposure
- future methodology revisions
Practical Takeaway
The safest version of this article is the one that stays boring and exact. OKX and Kraken both publish proof-of-reserves material, but the decision should focus on disclosure scope rather than a generic trust label. OKX publishes a proof-of-reserves page with reserve ratios, supported assets, wallet evidence and user self-verification material. Kraken publishes a proof-of-reserves page that frames reserves as independently verifiable cryptographic proof and explains client-balance inclusion. Neither page should be treated as a full financial statement audit, a guarantee of future withdrawals or proof that every unsupported asset, off-chain obligation and post-snapshot event is covered. The practical choice is to verify asset coverage, timestamp, liability scope, wallet proof, self-verification path and stated limitations before relying on either disclosure. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route or tokenized asset will work under every future condition.
Thèmes et outils:Comparer deux plateformes
Vérifiez l’éligibilité régionale et les conditions du compte
Ouvrir →Sources
04- Proof of Reserves · okx.com
- Proof of Reserves
- Proof of Reserves
- Crypto-assets and Global Stablecoins