← All signal reportsSpiko hub →
Signal report

Spiko

Publication date July 02, 2026

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

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

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

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

What it is

Spiko is a European tokenized money-market fund issuer, deploying on-chain tokens backed by regulated fund shares under EU jurisdiction, connected to Western Europe settlement rails alongside Backed and other RWA issuers. For spread-capture topology, Spiko is an EU issuer waist where tokenized product deployment must align with attested disclosure and MiCA jurisdiction evidence on Ethereum and Base.

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

Spiko, tokenized fund issuer homepage [✓ ATTESTED-PRIMARY] Spiko's homepage documents tokenized money-market fund products, primary anchor for Spiko issuer claims in settlement topology. Source-checked: ATTESTED-PRIMARY · custody sha256 cbc960f46197…, found in primary source

Spiko documentation [✓ ATTESTED-PRIMARY] Spiko docs describe tokenized fund mechanics and product structure, cross-check for EU issuer claims in tokenized settlement graphs. Source-checked: ATTESTED-PRIMARY · custody sha256 67db312f58e6…, found in primary source

RWA.xyz, Spiko asset page [✓ ATTESTED-PRIMARY] RWA.xyz's Spiko page documents on-chain tokenized fund activity, verifiable open-data lane for Spiko issuer products in settlement topology. Source-checked: ATTESTED-PRIMARY · custody sha256 b45d92f42edf…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0200)

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

Spiko settlement pressure is elevated because EU tokenized fund issuance scales on public chains faster than VERIFY catalogs per-product attestation of reserve backing and regulatory disclosure. The engine reads unrealized Φ_S when Spiko centrality exceeds vault evidence of issuer deployment and EU jurisdiction compliance events.

Coherence (κ = 0.0185)

κ = 0.0185 reflects the engine's current measurement coverage, not Spiko'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.0185, Spiko is 0.5995 below equilibrium. Vault observations of Spiko'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 Spiko. 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 Spiko 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
Spiko, tokenized fund issuer homepage
Spiko documentation
RWA.xyz, Spiko asset page
Eigenstate Pages & federation surfaces
Canonical report · this page
Entity hub · publish history + measurement evolution
Entity dossier (HTML) · live SoT card for Spiko
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 / SPIKO. 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 (Spiko)· 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:SPIKO · report_id:SPIKO_20260702
Build fingerprint: 50b1b772ea231898… (match builds[].chain_hash for SPIKO 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.