← All signal reportsCoinbase hub →
Signal report

Coinbase

Publication date July 02, 2026

Live SoT
Settlement pressure
Φ_S 6.5107
Field coherence
κ 0.1052
M1 ledger obs
613
M1 coverage (field)
193 / 199

Hero numbers overlay the live dossier SoT (compiled 2026-10-21T05:46:03Z). This is current engine state, not the prose below.

Publication snapshot · 2026-07-02
Φ_S at publish
0.0377
κ at publish
0.1944
vault@publish
0

Dated research snapshot. Prose below describes publication-time observation. vault@publish counts trimmed cycle-vault rows at publish time. It is not the live M1 ledger (613 obs for COINBASE; field coverage 193 / 199). Do not read vault@publish = 0 as "no measurements exist" when M1 ledger obs is non-zero.

Coinbase: Field Position Report

Eigenstate Research, July 02, 2026

Methodology: The Information Field Equations, E = ΔI/A, G = ∮E·dl, Protocol Truth → 1/φ


Publication field context

The Eigenstate engine currently measures the tokenized settlement field at:

The field is 0.1172 below equilibrium coherence. Each entity with measured vault activity raises the global PT toward 0.618. Coinbase does not yet have a complete observation record on the M1 topology (199 entities).

What it is

Coinbase is the largest US-regulated cryptocurrency exchange and custody provider, operating under a BitLicense (New York), money transmitter licenses (49 states), and as a FINRA-registered broker-dealer for securities. For the tokenized settlement layer, Coinbase occupies three structural roles simultaneously: (1) the retail on/off-ramp connecting the crypto-native audience to the field, (2) the institutional custody provider for BUIDL and other tokenized fund shares (Coinbase Custody), and (3) the owner/operator of Base (chain 8453), the settlement layer on which Eigenstate's contracts are deployed.

The engine maps 21 direct connections from Coinbase in the settlement topology, regulatory, custody, funding, and information-flow relationships that determine how rule signals propagate to downstream issuers and custodians.

Verified claims

Field Confidence: ✓ HIGH, Avg source weight 0.82 across 2 source(s): SEC_EDGAR, DEFILLAMA

Verification: 3/3 source-checked (ATTESTED), 3 grounded. Each claim below carries a machine-checked status against its cited source; ungrounded items are editorial assessments, not verified facts.

Active signals the engine is tracking for Coinbase:

Base sequencer decentralization, fault proofs live [✓ ATTESTED-PRIMARY] Coinbase documents Base's path toward a decentralized sequencer, including fault proofs as a stage-1 milestone, the settlement-neutrality signal the engine tracks for Base-as-public-good vs sequencer revenue capture. Source-checked: ATTESTED-PRIMARY · custody sha256 b68d5c28d597…, found in primary source

Coinbase Prime, institutional custody platform [✓ ATTESTED-PRIMARY] Coinbase Prime is Coinbase's institutional trading and custody product, the custody counterparty lane for tokenized securities and fund shares flowing through US-regulated infrastructure. Source-checked: ATTESTED-PRIMARY · custody sha256 889418bfd15b…, found in primary source

Coinbase operates Base as an Ethereum L2 [✓ ATTESTED-PRIMARY] Base documentation identifies Coinbase as the builder of Base, wiring the exchange/custody institution directly into the L2 settlement layer the topology maps at chain ID 8453. Source-checked: ATTESTED-PRIMARY · custody sha256 b68d5c28d597…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0377)

Near-zero settlement pressure, this entity is close to field equilibrium.

Coinbase has elevated settlement pressure because its three roles create structural tension: it simultaneously competes with and provides infrastructure for the tokenized asset ecosystem. As Base grows as a public good settlement layer, Coinbase must balance sequencer revenue (captured) against ecosystem credibility (requires neutrality). The ongoing decentralization of Base's sequencer and the Coinbase Prime custody expansion into tokenized securities are the two primary rule signals the engine is tracking.

Coherence (κ = 0.1944)

κ = 0.1944 reflects the engine's current measurement coverage, not Coinbase's actual institutional influence. With no vault records yet, the coherence score is derived purely from topology position, connection count and structural weight, without any attested observation data. The low value means the engine has not yet measured this entity's settlement activity, not that the entity lacks field presence.

The equilibrium attractor is κ = 1/φ ≈ 0.618. At current κ = 0.1944, Coinbase is 0.4236 below equilibrium. Vault observations of Coinbase's rule outputs, rulemaking notices, enforcement actions, guidance documents, would directly raise κ toward the living zone [0.618, 0.678].

Vault Coverage

No vault records yet for Coinbase. This is a gap in the field coverage. The engine recommends observation as the first action (see below).

Field read · recommendations

The following actions are ranked by capital-adjusted score from the current photon queue:

1. Publish network analysis of Coinbase and its 21 connections

Field read · concentration

Coinbase ranks #6 in the field's power concentration with a score of 0.05 (field total: 0.88).

The top 5 entities control 81.8% of field power (Gini = 0.89). High concentration with low vault coverage (6.9%) is the primary source of PT = 0.0568 vs target 0.618.


Sources

This report is generated by the Eigenstate engine, an information-field measurement system for the tokenized settlement layer. The engine tracks 199 entities (M1 topology denominator) across the regulatory, infrastructure, issuer, and audience layers.

Core equations:

Published implementation: helixhash v0.1.1, Zenodo DOI 10.5281/zenodo.18413995

Vault: No vault records yet for Coinbase in the current cycle, κ and Φ_S here are topology-derived until observations are attested. The field recommends observation as the first action.

Note: Internal topology codenames are not used in public reports. All entity names in this report are public names.

Sources & human pages
Issuer / primary pages
Coinbase Prime, institutional custody platform
Other cited pages
Base sequencer decentralization, fault proofs live
Coinbase operates Base as an Ethereum L2
Base, Ethereum L2 incubated by Coinbase
Eigenstate Pages & federation surfaces
Canonical report · this page
Entity hub · publish history + measurement evolution
Entity dossier (HTML) · live SoT card for Coinbase
Methodology · field equations and publish honesty
Numbers glossary · Φ_S, κ, vault@publish, M1 ledger
Verify walkthrough · human federation check
Related reports · other tracked entities
Paragraph journal · long-form distribution
Federation network view · RWA map · Node diary
RWA registry · public registry UI
Related entities · by settlement pressure
CircleΦ_S 8.155Uniswap DEXΦ_S 6.492Tether (USDT)Φ_S 4.938BlackRockΦ_S 3.287Regulation DΦ_S 3.284Regulation SΦ_S 3.284
For agents
APIs · Vercel apps · federation traverse · Node 34539544 (collapsed)

Cold-agent entry for Node 34539544 / COINBASE. Prefer human pages above first. Traverse: agent entry → manifest → entity feed → dossier → chain verify → canonical report. Walkthrough: verify-walkthrough.

Machine JSON & federation APIs
Agent entry· Node hub · cold start
Manifest· builds directory
Machine dossier (Pages)· COINBASE.json
Live dossier API· /api/dossier
Machine claims (Pages)· COINBASE.json
Federation card· Node hub agent descriptor (entity feed stubs retired)
Chain verify· /api/chain
Federation base· geniusflow-federation.vercel.app
Federation status· best_effort_vercel
llms.txt· agent adapter index
OpenAPI· machine schema
api/verify· claim verify wire
api/package· claim package wire
api/cite· cite surface
api/return_wire· return wire
Vercel apps
geniusflow-rwa (Vercel)· registry + federation.html
Entity feed (corrected · was stub)· doubled-name *supplyfeed/*tvlfeed hosts retired → federation report_feed
entity:COINBASE · report_id:COINBASE_20260702
Build fingerprint: 38de5171506f9523… (match builds[].chain_hash for COINBASE in api/manifest, then verify via api/chain)
Granth head:917f0e3036931e14… · length 919
Verify: GET api/manifest → find builds[].target==entity → match chain_hash → GET api/chain.