← All signal reportsAnchorage Digital hub →
Signal report

Anchorage Digital

Publication date July 02, 2026

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

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

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

Anchorage Digital: 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. Anchorage Digital does not yet have a complete observation record on the M1 topology (199 entities).

What it is

Anchorage Digital is a federally chartered crypto bank and institutional custody platform for digital assets. For the tokenized settlement layer, Anchorage is a regulated custody counterparty, OCC-chartered bank status distinct from trust-company custodians, wiring TradFi institutions into tokenized asset mint, redeem, and staking settlement.

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 Anchorage Digital:

Anchorage Digital, crypto-native bank and custodian [✓ ATTESTED-PRIMARY] Anchorage's primary site identifies the firm as a digital asset platform and federally chartered crypto bank, the regulated custody anchor. Source-checked: ATTESTED-PRIMARY · custody sha256 81cde5ce5715…, found in primary source

Anchorage digital asset custody [✓ ATTESTED-PRIMARY] Anchorage's about page documents digital asset custody and banking services, the verifiable lane for qualified custodian settlement claims. Source-checked: ATTESTED-PRIMARY · custody sha256 2d92dc2f1f0e…, found in primary source

Anchorage regulated bank charter [✓ ATTESTED-PRIMARY] Anchorage's banking page describes OCC bank-charter custody infrastructure, the institutional anchor distinguishing federally chartered custody from trust-company alternatives in the settlement graph. Source-checked: ATTESTED-PRIMARY · custody sha256 01a6a8f26c9f…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0200)

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

Anchorage settlement pressure is elevated because bank-charter custody is the regulatory gold standard for tokenized securities and stablecoin reserves, yet vault coverage of Anchorage-custodied settlement events remains sparse versus the node's weight in institutional RWA topology.

Coherence (κ = 0.0003)

κ = 0.0003 reflects the engine's current measurement coverage, not Anchorage Digital'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.0003, Anchorage Digital is 0.6177 below equilibrium. Vault observations of Anchorage Digital'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 Anchorage Digital. 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 Anchorage Digital 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 Anchorage Digital
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 / ANCHORAGE. 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)· ANCHORAGE.json
Live dossier API· /api/dossier
Machine claims (Pages)· ANCHORAGE.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
entity:ANCHORAGE · report_id:ANCHORAGE_20260702
Build fingerprint: 80c9868b9b29ac8a… (match builds[].chain_hash for ANCHORAGE 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.