Who may find this file useful
Experienced users prepared to verify regional eligibility, counterparty, product terms and total withdrawal route rather than relying on the global brand surface.
Claims & accountability investigation
Binance
This file separates Binance’s centralised platform, regional services and self-custody wallet while keeping fee, reserves and enforcement claims in their proper scope.
Editorial assessment: Binance documents a very broad feature set and publishes reserve-verification tools, but breadth increases the cost of precision. The 2023 US resolutions remain material context, while the SEC’s later dismissal must not be rewritten as an adjudication on the merits.
Editorial statusPublished review
Evidence reviewPublic evidence reviewed
Scenario testingScenarios published
ComparisonCategory matrix eligible
Reviewed
Evidence confidencemedium
The decision tension
Wide trading and API capabilities sit beside a complex entity map, dynamic pricing and a substantial enforcement history.
Documentary, not experiential
Public evidence has been reviewed; account, funding, trading, withdrawal and support scenarios are specified as controlled routes with defined inputs and records.
Evidence-backed strengths
What the record supports
- Extensive spot and API documentation
- Published reserve-verification interface
- Fee tables expose BNB-discount conditions
Material limitations
What must stay qualified
- Binance.com, Binance Wallet and Binance.US are not interchangeable
- PoR remains narrower than a financial audit
- No documentary source establishes live execution quality or universal availability
Operator evidence file4 recorded fields
Exact product
The centralised platform and Binance Wallet use different custody and provider models; Binance.US is also separate.
Operating entity
The July 2026 global terms allocate centralised services among ADGM entities, subject to regional variation.
Custody and reserves
Centralised custody is distinct from the wallet’s MPC and cloud/server dependencies; PoR is scoped evidence, not an audit.
Costs and exit
The viewed regular spot example showed 0.100% maker/taker and 0.075% with BNB, but account, asset and withdrawal conditions remain dynamic.
Investigative analysis
Claims, records and the gaps between them.
Each conclusion is tied to the primary records immediately below it. Links open the publisher’s original material.
The latest global terms redraw the entity map
Binance’s 21 July 2026 terms divide exchange, clearing/custody and other centralised services among named ADGM entities. That is a stronger disclosure than an anonymous brand relationship, yet local entities and restrictions still need to be checked. The document cannot be applied automatically to Binance.US or every regional surface.
Sources: Binance · BinanceWallet language must not leak into exchange custody
Binance Wallet is presented as self-custodial but includes MPC, cloud and server dependencies described by its provider. Those facts belong to a wallet-control review, not a statement that centralised-exchange customers hold their own keys. We keep the two records apart even when links share the Binance name.
Sources: Binance · BinanceThe displayed fee is an example, not a promise
On 16 August 2026 the spot fee page was re-retrieved with a regular-user example and a presented BNB-discount route. Fee schedules, VIP levels, products and account settings can change that path; network withdrawal charges are published separately. A complete cost claim needs the actual asset and exit rail.
Sources: Binance · BinanceDocumentation proves interfaces, not performance
Binance’s developer portal demonstrates the existence of multiple APIs, endpoints and order surfaces. It does not establish latency, fill quality, outage frequency or suitability for a particular strategy. Those would require timestamped benchmarks under declared market conditions.
Sources: Binance · BinanceReserve tools cannot carry the whole assurance burden
Binance publishes Merkle and zk-SNARK proof-of-reserves mechanisms and states that customer assets are backed 1:1. The mechanism may help a customer inspect inclusion in a defined snapshot; the broader backing statement remains a platform claim and the package is not a full financial-statement audit.
Sources: BinanceThe enforcement record needs exact verbs
The 2023 DOJ, FinCEN and CFTC resolutions concern serious historical compliance failures and belong in any balanced account. In 2025 the SEC dismissed its litigation as a discretionary policy decision; the dismissal was not a merits finding that erased the earlier records. Penalties from coordinated actions should not be arithmetically double-counted.
Sources: US Department of Justice · FinCEN · US CFTC · US SECClaim → evidence → gap
Ten claims placed under an accountable burden of proof.
Each module keeps the decision consequence beside the evidence and the unresolved gap. Primary material was retrieved on .
Broad spot/API capability is essential and the local entity is known.
The platform documents a wide professional surface.
The user will measure the full fee and withdrawal route.
Published fee/API materials support a fixed scenario.
A simple globally uniform legal relationship is required.
Services, entities and availability are regionalised.
PoR or SAFU must function as deposit insurance.
Neither is equivalent to statutory insurance or a full audit.
01
01 / Product claim
- Claim under review
- Binance.com, Binance.US and Binance Wallet are interchangeable.
- Evidence on record
- Terms and product materials describe distinct centralised, US and MPC-wallet surfaces.
- Unresolved gap
- This file does not assess the other two as substitutes.
- Decision impact
- Name the exact platform before using any conclusion.
02
02 / Entity claim
- Claim under review
- The global brand reveals the contracting party.
- Evidence on record
- July 2026 global terms allocate centralised roles in ADGM subject to regional variation.
- Unresolved gap
- The user’s local entity and permission are not fixed.
- Decision impact
- Contract and authoritative register must be saved before funding.
03
03 / Custody claim
- Claim under review
- Reserve inclusion removes custody risk.
- Evidence on record
- Centralised balances are custodial and Binance publishes a PoR interface.
- Unresolved gap
- Encumbrance, off-chain liabilities and future access remain outside a balance proof.
- Decision impact
- PoR supplements rather than replaces counterparty analysis.
04
04 / Security/API claim
- Claim under review
- Powerful APIs are safe by default.
- Evidence on record
- Developer documents establish APIs and permissions surfaces.
- Unresolved gap
- Default scope, IP restriction, revocation and runtime errors are untested.
- Decision impact
- Use least privilege and no withdrawal authority during evaluation.
Adjacent sources: Binance
05
05 / Regulation claim
- Claim under review
- Licences listed by Binance imply universal permission.
- Evidence on record
- The provider lists registrations while US agencies and the FCA publish entity-specific records.
- Unresolved gap
- Current activity-by-market mapping remains required.
- Decision impact
- Regulatory claims need an independent register or regulator source.
Adjacent sources: Binance · US Department of Justice · FinCEN · US CFTC
06
06 / Cost claim
- Claim under review
- The regular spot cell is total cost.
- Evidence on record
- The fee page shows tier and BNB-discount conditions.
- Unresolved gap
- Spread, rail, conversion and withdrawal cost are not included.
- Decision impact
- Measure one deposit-trade-withdraw receipt.
07
07 / Exit claim
- Claim under review
- Market breadth predicts withdrawal reliability.
- Evidence on record
- Withdrawal fees and networks are published.
- Unresolved gap
- Availability, holds, address controls and chain arrival are unobserved.
- Decision impact
- Exit quality needs an entity/asset/network-specific run.
Adjacent sources: Binance
08
08 / Execution claim
- Claim under review
- Deep features prove superior execution.
- Evidence on record
- Order and API capabilities are documented.
- Unresolved gap
- Spread, depth, slippage, cancellation and latency are not measured.
- Decision impact
- No execution rank follows from feature breadth.
09
09 / Privacy/remedy claim
- Claim under review
- Scale guarantees strong support and data controls.
- Evidence on record
- Terms create an accountability frame.
- Unresolved gap
- Telemetry, data requests, case ownership and dispute completion are not tested.
- Decision impact
- Remedy evidence remains separate from popularity.
Adjacent sources: Binance
10
10 / Enforcement claim
- Claim under review
- The 2025 SEC dismissal erases the 2023 record.
- Evidence on record
- DOJ, FinCEN and CFTC resolutions remain primary records; the SEC case ended by stipulation.
- Unresolved gap
- Different proceedings answer different questions.
- Decision impact
- Present both outcome and scope without arithmetic double-counting or erasure.
Adjacent sources: US Department of Justice · FinCEN · US CFTC · US SEC
Accountable scenario file
What the next observation must record.
Each row specifies a fixed protocol with defined inputs and record.
Spot total cost
Fixed inputs: One entity, tier, pair, notional and UTC window.
Record: Depth, spread, fee, fill, slippage and withdrawal quote.
PublishedAPI least privilege
Fixed inputs: No-value account, restricted key, fixed endpoint and region.
Record: Default scope, errors, rate limits, revocation and withdrawal block.
PublishedLocal eligibility and exit
Fixed inputs: Verified residence, one fiat rail and crypto network.
Record: Contract, permission, hold, fee, transaction and arrival.
PublishedPrivacy and remedy
Fixed inputs: Default consent state, data request and non-urgent support case.
Record: Controls, case owner, written outcome and dispute route.
PublishedChange timeline
Events that change the reading.
- US criminal/civil resolutions announced.
Compliance governance stays material.
- SEC civil action dismissed by joint stipulation.
That procedural outcome must not erase other records.
- Reviewed global terms date.
Entity language remains time-sensitive.
Alternatives
When another responsibility model fits better.
Kraken
Granular security controls and a narrower professional flow are preferred.
Coinbase Advanced
US disclosure traceability outweighs maximum market breadth.
Conclusion control
Medium evidence confidence.
- Supported
- Current terms, fee/API documents and official enforcement records support the documentary ledger.
- Gap
- Local entity, execution, exit, privacy and remedy outcomes remain unobserved.
- What changes the conclusion
- Entity changes, repeated withdrawal/support failure or strong reproducible controls would alter the conclusion.
Method
How the burden of proof is applied.
- Separate global, US and wallet products.
- Bind residence to contract and independent regulator records.
- Measure the full economic and asset path.
- Keep reserves, contingency funds and enforcement events in separate claim files.
Change log
Material file revisions.
Added ten accountability modules and four fixed execution, API, exit and remedy scenarios.
FAQ
Questions that survive the headline.
Is Binance Wallet included?
No; it has an MPC/recovery model distinct from centralised custody.
Is PoR an audit?
No; it is scoped reserve evidence.
Do low spot fees prove lowest total cost?
No; measure spread, funding and withdrawal too.
What does the SEC dismissal prove?
It proves that named case ended by stipulation, not that every other record was reversed.
Primary-source register
Reviewed on by Candid Ledger Editorial Team; independent editorial review by Candid Ledger Review Team.
- Binance Terms of Use — 21 July 2026 — Binance · retrieved 16 August 2026
- Binance licences and registrations — Binance · retrieved 16 August 2026
- Binance spot trading fees — Binance · retrieved 16 August 2026
- Binance crypto withdrawal fees — Binance · retrieved 16 August 2026
- Binance developer documentation — Binance · retrieved 16 August 2026
- Binance proof of reserves — Binance · retrieved 16 August 2026
- United States v. Binance Holdings Limited — US Department of Justice · retrieved 16 August 2026
- In the Matter of Binance Holdings Limited et al. — FinCEN · retrieved 16 August 2026
- CFTC Binance enforcement resolution — US CFTC · retrieved 16 August 2026
- SEC litigation release 26316 — US SEC · retrieved 16 August 2026