CB

EXECUTION EVIDENCE FILE

Coinbase

A documented split between simple brokerage and order-book execution, with regional entity and incident boundaries that matter to any cost or reliability claim.

REVIEW DATE
EVIDENCE STATUS
partially verified
CONFIDENCE
medium

Written by Beacon Ratio Editorial TeamIndependently reviewed by Beacon Ratio Review TeamPublished by Beacon Ratio Team

EDITORIAL ASSESSMENT

Coinbase presents two materially different execution paths: convenience-led Simple transactions and Coinbase Advanced order-book trading. The documents are strong enough to map the route, but not to award an execution score without matched live orders, funding and withdrawal tests.

SUITABLE FOR
Readers who want a clearly documented custodial platform and can choose deliberately between a quoted retail transaction and an order-book interface.
PRIMARY TRADE-OFF
The simpler route reduces interface work but can combine a displayed Coinbase fee with spread; Advanced exposes maker/taker mechanics but asks more of the trader.
DOCUMENTED STRENGTHS
  • Clear public distinction between simple and Advanced fee mechanics
  • Public-company filings add incident and financial-risk context
  • Hosted custody and self-custody Wallet are explicitly separable
LIMITS / OPEN TESTS
  • Exact Advanced tiers can require account context and change with volume
  • No Beacon Ratio fill, spread, latency or withdrawal benchmark has been run
  • Licensing and cash protection cannot be generalised across markets
ANALYSIS / 5

From interface claim to executable test.

01

Execution surface

Simple Buy, Sell and Convert use a quoted transaction path; Advanced uses an order book. Those are different test subjects, so a single headline fee would conceal the choice a user actually makes.

02

Cost path

Coinbase says a Simple transaction can include a Coinbase fee and spread, while Advanced applies maker/taker pricing without an embedded spread. Total cost still needs funding, slippage and withdrawal added to the trade fee.

04

Operational evidence

The May 2025 filing describes data obtained through paid overseas support personnel and says passwords and private keys were not compromised. It is material evidence about the support chain, not a measurement of present order-engine availability.

DECISION FILE / 04

Where this product fits—and where it does not.

BEST FIT

Readers who want a clearly documented custodial platform and can choose deliberately between a quoted retail transaction and an order-book interface.

NOT A FIT

Readers who need anonymous access, deterministic low-latency execution, a universal fee promise, or one conclusion that applies to every Coinbase entity and product.

STRONGEST DOCUMENTED CASE

Clear public distinction between simple and Advanced fee mechanics

CLOSEST ALTERNATIVE

Kraken Pro is the closest documented alternative for a user prioritising a visible order-book path and withdrawal-hold disclosure; a self-custody wallet is an exit tool, not a substitute venue.

REVIEW SCOPE
Coinbase retail hosted account and Coinbase Advanced, with the US agreement as the legal reference. Coinbase Wallet, institutional Prime, derivatives and non-US entities are outside this file unless explicitly named.
ENTITY / CONTROL BOUNDARY
The reviewed US agreement names Coinbase, Inc. Hosted crypto remains under Coinbase-controlled keys, while the separate unhosted Wallet changes the control model entirely.
SCENARIOS / 4

Concrete routes, not generic personas.

01

Primary decision route

A US retail user funds USD, compares a Simple quote with an Advanced marketable order, then withdraws the acquired asset to a self-controlled address.

02

Convenience route

Bank funding → Simple quote → hosted balance → external withdrawal. Open question: Effective spread versus a contemporaneous market, settlement hold, slippage after quote acceptance and final withdrawal charge.

03

Order-book route

USD balance → Advanced marketable order → external withdrawal. Open question: Queue position, realised slippage, rejected quantity, API overhead and exit cost at the test timestamp.

04

Alternative route

Kraken Pro is the closest documented alternative for a user prioritising a visible order-book path and withdrawal-hold disclosure; a self-custody wallet is an exit tool, not a substitute venue.

EXPERT LEDGER / 8

Decision factors with evidence state and the next test attached.

Coinbase execution, control and evidence ledger
Decision factorCurrent finding and adjacent evidenceEvidence stateVerification protocol
Scope and entity

Simple transactions and Advanced order-book trading are different execution products. The US agreement cannot be exported to another jurisdiction without its local terms.

Documented

Capture the agreement and entity shown to the funded test account.

Custody and keys

Coinbase controls hosted-wallet keys and records customer balances; Coinbase Wallet is separately unhosted. Title language does not remove outage, legal-order or operational access constraints.

Documented

Complete a small withdrawal and record every approval, hold and status transition.

Security and reliability

The 2025 filing is evidence of a support-chain data incident, not proof about current matching-engine resilience. The agreement also declines to guarantee uninterrupted access or order acceptance.

Mixed

Measure login, acknowledgement, cancel and support escalation across normal and volatile windows.

Regulatory evidence

A public-company filing and a named US contracting entity improve traceability, but they do not establish the permissions or protections of every regional service.

Documented

Bind every regulatory claim to the account entity and product used.

Depth, slippage and API

Advanced exposes order-book mechanics; Simple presents an executable quote. Neither public help page establishes depth at the chosen notional, queue position, reject rates or API tail latency.

Planned verification

Run matched notionals and retain book snapshots, client/server timestamps and raw order events.

Identity and data

The US agreement permits identity, bank, device and fraud-prevention inquiries. This is a regulated hosted-account data path, not a privacy-minimised wallet flow.

Documented

Map actual onboarding fields, vendors and retention disclosures without submitting unnecessary data.

Support and disputes

The agreement contains complaint and arbitration routes; the 2025 incident makes support-vendor access a material operational dependency.

Mixed

Open a harmless support case and record routing, authentication and resolution time.

Incidents and change control

Terms, pricing and supported assets can change. A dated source snapshot is therefore part of the result, not administrative decoration.

Documented

Diff terms and fee pages before publication and after any material product change.

TOTAL COST / 2

Fee schedules are inputs, not outcomes.

Scenario total-cost model; documented inputs applied
ScenarioRouteDocumented inputsOpen question
Convenience routeBank funding → Simple quote → hosted balance → external withdrawal

Displayed Coinbase fee and any quoted spread; bank and network charges disclosed at authorisation.

Effective spread versus a contemporaneous market, settlement hold, slippage after quote acceptance and final withdrawal charge.
Order-book routeUSD balance → Advanced marketable order → external withdrawal

Maker/taker framework and account-volume tier logic.

Queue position, realised slippage, rejected quantity, API overhead and exit cost at the test timestamp.
REPRODUCIBLE METHOD

How this file becomes a measured result

Freeze legal entity, account tier, asset pair, notional, funding rail and observation window; archive the quote, best bid/ask, order events, fill, explicit fees, settlement hold and withdrawal receipt. Run Simple and Advanced as separate products.

EVIDENCE CONFIDENCE

What the documents can support

Medium for the documented US product split, custody wording and 2025 incident record; insufficient for live spread, depth, latency, uptime, support resolution and present withdrawal performance.

Conclusion-change gates

  • A region-matched live route materially contradicts the documented fee or hold model.
  • Coinbase changes the applicable entity, custody terms or Advanced fee construction.
  • Repeated order or withdrawal tests establish reproducible tail-latency or support findings.
CHANGE LOG / 03

Evolution stays visible.

  1. Rechecked US terms, Simple pricing, Advanced fees and the SEC incident filing; added execution scenario and total-cost gates.

  2. Opened the first multi-source public-evidence file without a numeric rating.

  3. A region-matched live route materially contradicts the documented fee or hold model. Coinbase changes the applicable entity, custody terms or Advanced fee construction. Repeated order or withdrawal tests establish reproducible tail-latency or support findings.

FAQ / 4

Questions that change the decision.

Is Coinbase Simple cheaper than Advanced?

The documents do not support a universal answer. Simple and Advanced use different price construction, so a same-time, same-notional fill comparison is required.

Does hosted custody mean Coinbase owns the assets?

The reviewed US terms describe customer title and Coinbase-controlled keys. That is still custodial access and must be read with the full terms and jurisdiction.

Has Beacon Ratio tested Coinbase execution?

No. The live funding, order, API, support and withdrawal protocol is planned.

What would change this conclusion?

A region-matched live route materially contradicts the documented fee or hold model.

PRIMARY SOURCE REGISTER

5 records reviewed

Provider pages establish provider statements. Terms, filings and regulator records retain their narrower legal or historical scope. Dynamic sources were retrieved on 16 August 2026.

  1. termsRetrieved 2026-08-16Coinbase User Agreement — United States
  2. productRetrieved 2026-08-16Coinbase pricing and fees disclosures
  3. productRetrieved 2026-08-16Coinbase Advanced fees
  4. productRetrieved 2026-08-16What Coinbase does with digital assets
  5. filingRetrieved 2026-08-16Coinbase Form 8-K — May 2025 support-chain incident