← All signal reportsTether Omnichain USDT hub →
Signal report

Tether Omnichain USDT

Publication date July 02, 2026

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

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

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

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

What it is

Tether Omnichain USDT is Tether's cross-chain USDT deployment using LayerZero OFT standards, a unified stablecoin rail that moves native USDT liquidity across supported chains without wrapped bridge intermediaries. For the tokenized settlement layer, omnichain USDT is a cross-chain dollar primitive wiring Tether's reserve-backed USDT into DeFi and RWA collateral paths alongside USDC and CCTP-native flows.

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 Tether Omnichain USDT:

Developer documentation, omnichain stablecoin [✓ ATTESTED-PRIMARY] Tether's developer documentation describes the omnichain USDT deployment and OFT standard integration, the primary-source lane for cross-chain dollar settlement topology. Source-checked: ATTESTED-PRIMARY · custody sha256 207876a22cee…, found in primary source

LayerZero omnichain deployment [✓ ATTESTED-PRIMARY] The product site documents LayerZero-powered omnichain USDT, the verifiable bridge rail connecting Tether liquidity across supported settlement chains. Source-checked: ATTESTED-PRIMARY · custody sha256 2a5a976a6b92…, found in primary source

DeFiLlama, omnichain USDT protocol listing [✓ ATTESTED-PRIMARY] DeFiLlama's protocol page indexes omnichain stablecoin metrics, the third-party listing anchor for cross-chain USDT settlement weight in topology graphs. Source-checked: ATTESTED-PRIMARY · custody sha256 f06b7e264765…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0200)

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

Omnichain USDT carries elevated settlement pressure because cross-chain mint-burn authority, LayerZero pathway attestations, and per-chain liquidity depth directly affect whether bridged USDT counts as same-instrument settlement or fragmented counterparty exposure. The engine tracks the gap between omnichain composability and incomplete vault attestation of OFT pathway integrity as unrealized Φ_S.

Coherence (κ = 0.0092)

κ = 0.0092 reflects the engine's current measurement coverage, not Tether Omnichain USDT'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.0092, Tether Omnichain USDT is 0.6088 below equilibrium. Vault observations of Tether Omnichain USDT'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 Tether Omnichain USDT. 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 Tether Omnichain USDT 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
Developer documentation, omnichain stablecoin
DeFiLlama, omnichain USDT protocol listing
LayerZero omnichain deployment
Eigenstate Pages & federation surfaces
Canonical report · this page
Entity hub · publish history + measurement evolution
Entity dossier (HTML) · live SoT card for Tether Omnichain USDT
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 / USDT0. 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
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:USDT0 · report_id:USDT0_20260702
Build fingerprint: 50b55531384a7040… (match builds[].chain_hash for USDT0 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.