Kaynak doğrulamalı araştırma: Binance / OKX

Verified source facts

1. Binance describes a Merkle-tree and zk-SNARK workflow that lets a user verify inclusion of a dated account snapshot. 2. Binance's current self-verification guide says the snapshot is taken monthly and must be checked with the verifier version mapped to that report cycle; the report is not a real-time asset display. 3. Binance's own explainer says proof of reserves has point-in-time and off-chain-liability limitations. 4. OKX describes zk-STARK proofs, published wallet addresses, downloadable reserve and liability files, and comparison of account assets with wallet assets. 5. OKX says its monthly report separates exchange and third-party-custody balances and that snapshot data can include debts or negative equity from borrowing. 6. Neither venue's disclosure proves every off-chain obligation, future withdrawal condition, or asset state after the snapshot.

Comparison at a glance

1. Control test: Snapshot time

A trading-control disclosure is meaningful only when converted into a testable rule. For snapshot time, inspect the exact point represented. Use a sandbox, non-production context, or the smallest reversible test available, then record the timestamp beside every ratio. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, conditions after the snapshot is therefore an explicit audit gap.

The snapshot time row should end with a concrete monitoring rule tied to the exact point represented. Make the operator record the timestamp beside every ratio, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; conditions after the snapshot remains a separate production risk until observed.

2. Control test: Asset scope

For asset scope, inspect which coins and account products are included. Use a sandbox, non-production context, or the smallest reversible test available, then match personal holdings to the coverage list.

In this dimension, uncovered asset backing is therefore an explicit audit gap.

The asset scope row should end with a concrete monitoring rule tied to which coins and account products are included. Make the operator match personal holdings to the coverage list, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; uncovered asset backing remains a separate production risk until observed.

3. Control test: Liability scope

For liability scope, inspect gross balances, debt and negative equity. Use a sandbox, non-production context, or the smallest reversible test available, then read the calculation rules before interpreting ratios.

In this dimension, off-chain obligations outside the proof is therefore an explicit audit gap.

The liability scope row should end with a concrete monitoring rule tied to gross balances, debt and negative equity. Make the operator read the calculation rules before interpreting ratios, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; off-chain obligations outside the proof remains a separate production risk until observed.

4. Control test: User inclusion

For user inclusion, inspect Merkle or zero-knowledge membership proof. Use a sandbox, non-production context, or the smallest reversible test available, then download and independently verify the personal record.

In this dimension, incorrect operator execution is therefore an explicit audit gap.

The user inclusion row should end with a concrete monitoring rule tied to Merkle or zero-knowledge membership proof. Make the operator download and independently verify the personal record, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; incorrect operator execution remains a separate production risk until observed.

5. Control test: Wallet ownership

For wallet ownership, inspect signed messages and public addresses. Use a sandbox, non-production context, or the smallest reversible test available, then verify signatures with published tools.

In this dimension, undisclosed custody arrangements is therefore an explicit audit gap.

The wallet ownership row should end with a concrete monitoring rule tied to signed messages and public addresses. Make the operator verify signatures with published tools, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; undisclosed custody arrangements remains a separate production risk until observed.

6. Control test: Balance check

For balance check, inspect on-chain holdings at the named block height. Use a sandbox, non-production context, or the smallest reversible test available, then recompute the visible balance.

In this dimension, assets moved after capture is therefore an explicit audit gap.

The balance check row should end with a concrete monitoring rule tied to on-chain holdings at the named block height. Make the operator recompute the visible balance, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; assets moved after capture remains a separate production risk until observed.

7. Control test: Proof software

For proof software, inspect open-source validator and file integrity. Use a sandbox, non-production context, or the smallest reversible test available, then pin versions and verify checksums.

In this dimension, supply-chain risk in downloaded tools is therefore an explicit audit gap.

The proof software row should end with a concrete monitoring rule tied to open-source validator and file integrity. Make the operator pin versions and verify checksums, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; supply-chain risk in downloaded tools remains a separate production risk until observed.

8. Control test: Custody split

For custody split, inspect exchange wallets and third-party custodians. Use a sandbox, non-production context, or the smallest reversible test available, then identify which balances depend on another custodian.

In this dimension, third-party liabilities is therefore an explicit audit gap.

The custody split row should end with a concrete monitoring rule tied to exchange wallets and third-party custodians. Make the operator identify which balances depend on another custodian, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; third-party liabilities remains a separate production risk until observed.

9. Control test: Audit boundary

For audit boundary, inspect cryptographic proof versus financial-statement assurance. Use a sandbox, non-production context, or the smallest reversible test available, then avoid calling the snapshot a complete audit.

In this dimension, full solvency between reports is therefore an explicit audit gap.

The audit boundary row should end with a concrete monitoring rule tied to cryptographic proof versus financial-statement assurance. Make the operator avoid calling the snapshot a complete audit, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; full solvency between reports remains a separate production risk until observed.

10. Control test: Publication cadence

For publication cadence, inspect how quickly old evidence becomes stale. Use a sandbox, non-production context, or the smallest reversible test available, then schedule a recurring recheck.

In this dimension, future report delays is therefore an explicit audit gap.

The publication cadence row should end with a concrete monitoring rule tied to how quickly old evidence becomes stale. Make the operator schedule a recurring recheck, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; future report delays remains a separate production risk until observed.

Decision scenarios

Scenario 1: when snapshot time becomes decisive

Consider a reader whose main constraint is the exact point represented. The correct response is not to infer a universal platform or product winner. It is to record the timestamp beside every ratio, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when asset scope becomes decisive

Consider a reader whose main constraint is which coins and account products are included. It is to match personal holdings to the coverage list, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when liability scope becomes decisive

Consider a reader whose main constraint is gross balances, debt and negative equity. It is to read the calculation rules before interpreting ratios, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when user inclusion becomes decisive

Consider a reader whose main constraint is Merkle or zero-knowledge membership proof. It is to download and independently verify the personal record, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when wallet ownership becomes decisive

Consider a reader whose main constraint is signed messages and public addresses. It is to verify signatures with published tools, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when balance check becomes decisive

Consider a reader whose main constraint is on-chain holdings at the named block height. It is to recompute the visible balance, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

Product availability, fees, controls, and legal terms can vary by entity, region, account tier, and time. Verify the live official page and the exact account screen before acting.