Coinbase · Coinbase Fee Schedule · View original document ↗

Batch Network Fee Excess Retention

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time Coinbase changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Coinbase recorded 2 documented changes in the last 30 days.
Get same-day alerts →
Monitor governance changes for Coinbase Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

Get the weekly research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.

Document Record

What it is

This provision discloses that when Coinbase batches multiple users' transactions together for network submission, the total estimated network fees charged to those users may collectively exceed the actual network fee that Coinbase pays, with Coinbase retaining the difference.

This analysis describes what Coinbase's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes that the network fee charged to an individual user is based on an estimate of standalone transaction costs, and that efficiency gains realized by batching are not passed through to users. The resulting difference between aggregate user charges and Coinbase's actual cost is retained by Coinbase.

Recent Activity

This document changed recently

Medium Jun 16, 2026

The updated fee schedule removes the pre-published 1% fee for instant unstaking and instead discloses the fee only at the moment a user requests to unstake. This means users can no longer review the exact cost before initiating a transaction through the published schedule. The revision also explicitly includes converting a pending standard unstake to an instant unstake as a fee-triggering action. No fee continues to apply if a user waits for the full unbonding period.

View change record →

Clause Stability Stable

0
Changes
4
Months Monitored
Jul 9, 2026
First Seen
Jul 9, 2026
Last Seen

Consumer impact (what this means for users)

Under this provision, a user paying an estimated network fee for a batched transaction may pay more than the proportional share of Coinbase's actual network cost for that batch. The document states all fees are disclosed at the time of the transaction, but the disclosure reflects an estimate rather than the final cost.

Cross-platform context

See how other platforms handle Batch Network Fee Excess Retention and similar clauses.

Compare across platforms →

Monitoring

Coinbase has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
Due to potential efficiency gains from batching transactions, the aggregate amount of estimated network fees paid by users within a given batch may exceed the final network fee paid by Coinbase.

Excerpt from Coinbase's Fee Schedule

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

REGULATORY LANDSCAPE: This practice may require evaluation under the FTC Act regarding whether the disclosure that estimated fees may exceed actual costs is sufficiently prominent and specific to satisfy consumer protection standards. State money transmission regulators may view the retention of the difference between estimated and actual network fees as a fee that requires separate disclosure or regulatory treatment. GOVERNANCE EXPOSURE: Medium. The document discloses the practice but does not quantify the magnitude of potential excess or commit to any cap on the retained amount. The absence of a maximum retention threshold creates ongoing disclosure and fairness exposure. JURISDICTION FLAGS: New York and California money transmission frameworks may treat the retained network fee differential as a separate charge subject to disclosure requirements. EU MiCA regulations impose transparency obligations on crypto-asset service providers that may require more explicit disclosure of this practice. CONTRACT AND VENDOR IMPLICATIONS: Institutional users and developers building on Coinbase infrastructure should account for the fact that quoted network fees are estimates and may not reflect actual costs, creating variability in transaction cost modeling for compliance and accounting purposes. COMPLIANCE CONSIDERATIONS: Compliance teams should assess whether the disclosure of batch fee estimation and excess retention meets applicable state and federal fee disclosure requirements. An analysis of whether this practice constitutes a separate fee category requiring independent regulatory treatment under applicable money transmission licenses may be warranted.

Full institutional analysis

Regulatory citations, enforcement risk, and due diligence action items.

Get same-day alerts when this changes → Get Analyst

Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.

Applicable agencies

  • FTC
    The FTC has authority over unfair or deceptive practices in consumer transactions, which may be relevant to the adequacy of network fee estimation and excess retention disclosures.
    File a complaint →
  • CFPB
    The CFPB oversees fee transparency in consumer financial products, which may apply to network fee practices depending on the regulatory classification of Coinbase's services.
    File a complaint →

Provision details

Document information
Document
Coinbase Fee Schedule
Entity
Coinbase
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-016369
Document ID
CA-D-00049
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
89ca126094c98e1370eb4e2ea79e673081dcd220d7d329a21d3d6bb58d52c3ec
Analysis generated
July 9, 2026 14:24 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Coinbase
Document: Coinbase Fee Schedule
Record ID: CA-P-016369
Captured: 2026-07-09 14:24:03 UTC
SHA-256: 89ca126094c98e13…
URL: https://conductatlas.com/platform/coinbase/coinbase-fee-schedule/provision/CA-P-016369/batch-network-fee-excess-retention/
Accessed: July 23, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Coinbase's Batch Network Fee Excess Retention clause do?

This provision establishes that the network fee charged to an individual user is based on an estimate of standalone transaction costs, and that efficiency gains realized by batching are not passed through to users. The resulting difference between aggregate user charges and Coinbase's actual cost is retained by Coinbase.

How does this clause affect you?

Under this provision, a user paying an estimated network fee for a batched transaction may pay more than the proportional share of Coinbase's actual network cost for that batch. The document states all fees are disclosed at the time of the transaction, but the disclosure reflects an estimate rather than the final cost.

Is ConductAtlas affiliated with Coinbase?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Coinbase.