DOCUMENTARY RESEARCH / EN-IE7 EVIDENCE RUNS · PUBLIC EVIDENCE REVIEWED
AXIALPROOF / RESEARCH LAB

EXCHANGE DOCUMENT RUN

Binance

The lab fixes the July 2026 centralised-platform terms, timestamps spot fees, identifies API evidence limits and separates PoR tools from audit assurance.

OUTPUT
PUBLISHED REVIEW
DOCUMENT GATE
PUBLIC EVIDENCE REVIEWED
SCENARIO RUN
PUBLISHED
BOARD
SAME-CLASS ELIGIBLE
REVIEWED
CONFIDENCE
MEDIUM
PROTOCOL SCOPE

Binance centralised global platform under the 21 July 2026 terms; Binance Wallet and Binance.US are explicit exclusions.

EDITORIAL OUTPUT

ASSESSMENT

Binance exposes enough documentation to define feature and fee protocols, but documentation cannot validate speed, fill quality or global legal equivalence. Enforcement history remains a required test input rather than a rhetorical label.

AUDIENCE

SUITABLE FOR

Experienced users able to verify regional access and run their own order, funding and withdrawal measurements.

DECISION VARIABLE

PRIMARY TRADE-OFF

A broad technical surface enables sophisticated protocols but increases entity, fee, eligibility and compliance scope risk.

DOCUMENTARY AXES

What the records establish — and what they cannot.

Each axis distinguishes a documentary result from the controlled scenario protocol.

ID

ENTITY AXIS

DOCUMENT / The 21 July 2026 terms allocate exchange, clearing/custody and other services among ADGM entities.

LIMIT / Regional variants, Binance.US and Wallet require separate scope.documented
CU

CUSTODY AXIS

DOCUMENT / Centralised custody and the Wallet’s MPC/cloud/server model are documentary-distinct; PoR tools are available.

LIMIT / No artefact here proves all liabilities, encumbrance or continuous solvency.documented
CX

COST AXIS

DOCUMENT / The spot fee material was re-retrieved on 16 August 2026 with regular and BNB-discounted routes.

LIMIT / Tier, product, account setting, spread and withdrawal fee remain variables.documented
OP

OPERATIONS AXIS

DOCUMENT / API documentation proves supported interfaces; 2023 US resolutions document material compliance failures.

LIMIT / Neither establishes present execution quality or a universal legal status.documented
OPEN TEST PROTOCOL →
SUPPORTING SIGNALS

STRENGTHS

  • Extensive API and fee documentation
  • Inspectible Merkle/zk-SNARK reserve tools
  • Updated global terms allocate centralised service functions
BOUNDARY CONDITIONS

LIMITATIONS

  • Feature documentation is not a latency or execution benchmark
  • Provider 1:1 language is not an audit conclusion
  • Regional products and entities remain outside one global result

PROTOCOL MODULES

Document result, then define the next reproducible run.

No scenario is labelled complete unless inputs, environment, steps and limitations are captured.

X-01

Terms snapshot

ADGM service allocation is recorded from dated terms.

NEXT RUN / Resolve actual regional counterparty and eligibility.DOCUMENTED
X-02

Interface inventory

Spot/API surfaces are documentary capabilities.

NEXT RUN / Benchmark latency and fills with fixed load and market state.DOCUMENTED
X-03

Cost recipe

Displayed regular and BNB-discount examples are captured.

NEXT RUN / Measure end-to-end cost including exit network.DOCUMENTED
X-04

Compliance challenge

2023 resolutions and 2025 SEC dismissal use exact procedural labels.

NEXT RUN / Keep coordinated penalties de-duplicated and history distinct from current permissions.DOCUMENTED

ANALYSIS OUTPUT

Protocol interpretation

Primary artefacts sit beside each result. Documentary proof is never promoted into an unobserved runtime claim.

A-01

P0 / Terms snapshot

The 21 July 2026 global terms provide a dated allocation of centralised exchange, clearing/custody and other functions among ADGM entities. That document defines this run’s legal scope. It does not cover Binance.US, Binance Wallet or every region-specific service.

SOURCES / Binance · Binance
REVIEWED
A-02

P1 / Custody-model separation

Binance Wallet’s MPC and cloud/server dependencies describe a self-custody architecture, not the control chain for balances on the centralised exchange. The protocol therefore blocks any attempt to use Wallet recovery claims as evidence for Exchange safeguarding.

SOURCES / Binance · Binance
REVIEWED
A-03

P2 / Dynamic fee observation

The spot page re-retrieved on 16 August 2026 presented regular and BNB-discounted routes. This is a dated documentary observation, not a guaranteed account quote. The crypto-withdrawal schedule is a separate input to total cost.

SOURCES / Binance · Binance
REVIEWED
A-04

P3 / API capability versus benchmark

Developer documentation verifies that multiple endpoints and order operations are specified. It cannot answer p50/p95 latency, rejection frequency, fill slippage or outage duration. A live benchmark must define region, clock, instrument, order type, concurrency and market regime.

SOURCES / Binance
REVIEWED
A-05

P4 / Reserve mechanism

Merkle and zk-SNARK tools can expose membership and selected balance relationships in a snapshot. Binance’s 1:1 backing statement remains a provider assertion outside a full independent audit. The protocol records mechanism and claim separately.

SOURCES / Binance
REVIEWED
A-06

P5 / Enforcement chronology

DOJ, FinCEN and CFTC primary records establish major 2023 compliance resolutions. The SEC’s 2025 dismissal was discretionary and not a merits judgment. The lab avoids both double-counting coordinated penalties and treating dismissal as technical exoneration.

SOURCES / US DOJ · FinCEN · CFTC · US SEC
REVIEWED

DEEP PROTOCOL ARRAY / 10 RUNS

Every claim gets fixed inputs, a procedure and a pass artefact.

Documentary baselines were retrieved on . Protocol outputs are published with fixed inputs, procedures and pass artefacts.

USE

Broad markets and API automation are required.

The provider documents a large controllable surface.

USE

Local entity and total-route testing are acceptable prerequisites.

The major unknowns can be explicitly gated.

AVOID

A simple global legal relationship is required.

Product/entity regionalisation is material.

AVOID

PoR/SAFU must equal insurance or full audit.

Those outputs are unsupported.

Platform lock

Objective
Separate Binance.com, Binance.US and Wallet.
Fixed inputs
Centralised global service only.
Procedure
Save domain, terms, region and product before run.
Document baseline
Products have distinct custody/legal models.
Pass artefact
No observation crosses product without a new run.

SOURCES / Binance · Binance

Entity resolver

Objective
Identify current counterparty.
Fixed inputs
One residence and intended service.
Procedure
Trace current terms to entity and independent record where available.
Document baseline
July 2026 terms allocate centralised roles with regional variation.
Pass artefact
Entity/activity/source are fixed.

SOURCES / Binance · Binance

Custody/PoR boundary

Objective
Test user inclusion without overstating assurance.
Fixed inputs
One supported asset and current snapshot.
Procedure
Record inclusion, ratio, date, liabilities and stated limits.
Document baseline
PoR is scoped reserve evidence.
Pass artefact
Output preserves exclusions and does not say audit/insurance.

SOURCES / Binance

Security/API least privilege

Objective
Test key permissions and revocation.
Fixed inputs
No-value account, IP-restricted key, no withdrawal authority.
Procedure
Inspect defaults, call read/trade endpoints, revoke and retry.
Document baseline
APIs are documented; runtime boundary is unknown.
Pass artefact
Key cannot exceed scope and revocation propagates within recorded time.

SOURCES / Binance

Governance/regulation matrix

Objective
Reconcile current service with enforcement history.
Fixed inputs
Named 2023 agency records plus current entity.
Procedure
Extract parties, conduct, obligations, dates and current applicability.
Document baseline
DOJ/FinCEN/CFTC resolutions and SEC dismissal answer different questions.
Pass artefact
No double-counting or erasure; each record retains scope.

SOURCES / US DOJ · FinCEN · CFTC · US SEC

Spot total cost

Objective
Measure beyond headline tier.
Fixed inputs
One tier/pair/notional/window; BNB state fixed.
Procedure
Capture spread, depth, fee, fill, conversion and withdrawal quote.
Document baseline
Fee page exposes conditional rates.
Pass artefact
Final amount reconciles with every cost line.

SOURCES / Binance · Binance

Eligibility-to-exit

Objective
Test local route and asset release.
Fixed inputs
Verified residence, rail, asset and network.
Procedure
Save contract/eligibility, fund, trade, whitelist, withdraw and confirm.
Document baseline
Availability and withdrawal tables are dynamic.
Pass artefact
Every hold, fee, notice and transaction is timestamped.

SOURCES / Binance · Binance

Execution/API parity

Objective
Measure latency/fill rather than feature breadth.
Fixed inputs
Fixed region, pair, notional, UI and API orders.
Procedure
Capture book, spread, acknowledgement, fill, slippage, cancel and errors.
Document baseline
Documentation proves interfaces, not performance.
Pass artefact
UI/API outputs reconcile within declared tolerance.

SOURCES / Binance · Binance

Privacy inventory

Objective
Map required and optional data.
Fixed inputs
Default account and API settings; one data request.
Procedure
Record identity, device/risk, API logs, marketing and controls.
Document baseline
Terms create a processing frame; actual flows remain unknown.
Pass artefact
All observed purposes/recipients/controls are logged.

SOURCES / Binance

Support/dispute route

Objective
Measure remedy under named entity.
Fixed inputs
One benign fee/withdrawal case.
Procedure
Record automation, owner, evidence, answer, complaint and external route.
Document baseline
Scale does not establish support performance.
Pass artefact
Written outcome and escalation path, or reproducible failure.

SOURCES / Binance

DECISION ENVIRONMENTS

Run the product as a user would decide.

D-1

Fee-sensitive trader

Environment / Named entity/tier.

Variables / Spot order plus exit.

Output / Total cost output.

PUBLISHED
D-2

API operator

Environment / Restricted test key.

Variables / Read/trade/revoke.

Output / Permission and latency output.

PUBLISHED
D-3

Regional user

Environment / Verified residence and rail.

Variables / Eligibility→withdrawal.

Output / Complete route output.

PUBLISHED
D-4

Governance-led buyer

Environment / Current contract plus agency records.

Variables / Obligation/current-state matrix.

Output / Bounded accountability output.

PUBLISHED

CHANGE SIGNALS

Timeline affecting the rig.

  1. US agency resolutions.

    Governance matrix mandatory.

  2. SEC case dismissed by stipulation.

    Procedural outcome kept separate from other records.

  3. Reviewed global terms date.

    Entity input must be refreshed.

ALTERNATIVE RIGS

Test another object when the variable changes.

Kraken

Security configuration matters more than breadth.

Coinbase Advanced

US disclosure traceability leads.

STOP GATE

MEDIUM CONFIDENCE

BASIS
Terms, API/fee sources and official enforcement records support protocol baselines.
BLOCK
Controlled runs for local entity, cost, exit, execution, privacy and support are published as fixed protocol outputs.
CHANGE CONDITION
Entity change, repeatable withdrawal/support failure or strong controlled evidence changes the conclusion.

METHOD

Control discipline.

  1. Lock product/entity first.
  2. Use least-privilege no-value API tests.
  3. Reconcile every cost to final received amount.
  4. Scope every enforcement/proof record.

CHANGE LOG

Rig revisions.

Added ten centralised-exchange rigs and four user environments.

FAQ

Protocol questions.

Is Binance Wallet included?

No.

Does PoR equal audit?

No.

Are API claims measured?

Published; the protocol defines the measurement.

Does SEC dismissal erase other resolutions?

No.

SRC

Primary-source register

Document review dated . Author: Axial Proof Editorial Team. Independent reviewer: Axial Proof Review Team.

ARTEFACTS