← All signal reportsArbitrum hub →
Signal report

Arbitrum

Publication date July 02, 2026

Live SoT
Settlement pressure
Φ_S 1.6381
Field coherence
κ 0.0010
M1 ledger obs
40
M1 coverage (field)
193 / 199

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

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

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

What it is

Arbitrum is an Ethereum Layer 2 rollup network built by Offchain Labs, a primary settlement layer for DeFi, tokenized assets, and stablecoin flows seeking lower costs than Ethereum L1. For spread-capture topology, Arbitrum is the L2 infrastructure waist where tokenized treasury and RWA deployment must align with attested on-chain throughput and bridge evidence.

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

Arbitrum, gentle introduction [✓ ATTESTED-PRIMARY] Arbitrum documentation introduces the Layer 2 rollup network, primary technical anchor for Arbitrum settlement-topology claims. Source-checked: ATTESTED-PRIMARY · custody sha256 66027803d41a…, found in primary source

DeFiLlama, Arbitrum chain page [✓ ATTESTED-PRIMARY] DeFiLlama's Arbitrum chain page documents on-chain TVL and protocol activity, cross-check for Arbitrum settlement throughput claims. Source-checked: ATTESTED-PRIMARY · custody sha256 69f1699436d1…, found in primary source

Ethereum.org, Layer 2 overview [✓ ATTESTED-PRIMARY] Ethereum.org's Layer 2 overview documents rollup networks scaling Ethereum, structural context for Arbitrum as an L2 settlement layer. Source-checked: ATTESTED-PRIMARY · custody sha256 be4b72661dc7…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0200)

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

Arbitrum settlement pressure is elevated because tokenized fund and stablecoin issuers deploy on Arbitrum faster than VERIFY catalogs L2 settlement attestation relative to Ethereum L1 finality. The engine reads unrealized Φ_S when Arbitrum centrality exceeds vault evidence of L2 chain TVL and protocol deployment feedback loops.

Coherence (κ = 0.1296)

κ = 0.1296 reflects the engine's current measurement coverage, not Arbitrum'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.1296, Arbitrum is 0.4884 below equilibrium. Vault observations of Arbitrum'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 Arbitrum. 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 Arbitrum 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
Other cited pages
Arbitrum, gentle introduction
DeFiLlama, Arbitrum chain page
Ethereum.org, Layer 2 overview
Eigenstate Pages & federation surfaces
Canonical report · this page
Entity hub · publish history + measurement evolution
Entity dossier (HTML) · live SoT card for Arbitrum
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 / ARBITRUM. 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)· ARBITRUM.json
Live dossier API· /api/dossier
Machine claims (Pages)· ARBITRUM.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:ARBITRUM · report_id:ARBITRUM_20260702
Build fingerprint: 8c85e69f774bc428… (match builds[].chain_hash for ARBITRUM 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.