← All signal reportsBitGo hub →
Signal report

BitGo

Publication date June 23, 2026

Live SoT
Settlement pressure
Φ_S 0.0200
Field coherence
κ 0.0123
M1 ledger obs
1
M1 coverage (field)
193 / 199

Hero numbers overlay the live dossier SoT (compiled 2026-08-30T05:00:04Z). This is current engine state, not the prose below.

Publication snapshot · 2026-06-23
Φ_S at publish
0.0200
κ at publish
0.0098
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 (1 obs for BITGO; field coverage 193 / 199). Do not read vault@publish = 0 as "no measurements exist" when M1 ledger obs is non-zero.

BitGo: Field Position Report

Eigenstate Research, June 23, 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.2361 below equilibrium coherence. Each entity with measured vault activity raises the global PT toward 0.618. BitGo does not yet have a complete observation record on the M1 topology (199 entities).

What it is

BitGo is an institutional digital asset custody and wallet infrastructure provider serving exchanges, banks, and tokenized asset issuers. For the tokenized settlement layer, BitGo sits alongside Fireblocks, Coinbase Custody, and Anchorage as a qualified custodian node, wiring TradFi institutions into on-chain mint, redeem, and treasury token workflows.

Verified claims

Field Confidence: ? LOW, No external sources mapped for this entity, engine-internal data only

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 BitGo:

BitGo, institutional digital asset custody [✓ ATTESTED-PRIMARY] BitGo's primary site identifies the firm as an institutional digital asset custody and security provider, the custody counterparty anchor. Source-checked: ATTESTED-PRIMARY · custody sha256 b3ecfd3d9927…, found in primary source

BitGo custody infrastructure [✓ ATTESTED-PRIMARY] BitGo's home page documents qualified custody and wallet infrastructure for institutions, the verifiable lane for settlement backing claims. Source-checked: ATTESTED-PRIMARY · custody sha256 b3ecfd3d9927…, found in primary source

BitGo institutional platform [✓ ATTESTED-PRIMARY] BitGo's site describes institutional-grade digital asset infrastructure, the technical anchor for qualified custodian settlement workflows. Source-checked: ATTESTED-PRIMARY · custody sha256 b3ecfd3d9927…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0200)

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

BitGo settlement pressure is elevated because institutional tokenization and stablecoin reserve custody route through qualified custodians whose policy architecture determines whether on-chain settlement is bank-grade or contingent counterparty risk. Incomplete vault attestation of custody transfer events versus BitGo's topology weight drives unrealized Φ_S.

Coherence (κ = 0.0098)

κ = 0.0098 reflects the engine's current measurement coverage, not BitGo'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.0098, BitGo is 0.6082 below equilibrium. Vault observations of BitGo'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 BitGo. This is a gap in the field coverage. The engine recommends observation as the first action (see below).


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 BitGo 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
Eigenstate Pages & federation surfaces
Canonical report · this page
Entity hub · publish history + measurement evolution
Entity dossier (HTML) · live SoT card for BitGo
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 11.392Tether (USDT)Φ_S 6.556CoinbaseΦ_S 6.511Tokenized Treasury PoolΦ_S 6.506BaseΦ_S 6.503Uniswap DEXΦ_S 6.492
For agents
APIs · Vercel apps · federation traverse · Node 34539544 (collapsed)

Cold-agent entry for Node 34539544 / BITGO. 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
Entity feed (BitGo)· report_feed
Live dossier API· /api/dossier
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
entity:BITGO · report_id:BITGO_20260623
Build fingerprint: 041e5dd870ae8493… (match builds[].chain_hash for BITGO 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.