FATF Travel Rule
July 02, 2026
Settlement Pressure
Φ_S 0.0240
Field Coherence
κ 0.0093
Vault Records
0
July 02, 2026
Eigenstate Research — July 02, 2026
Methodology: The Information Field Equations — E = ΔI/A, G = ∮E·dl, Protocol Truth → 1/φ
| Metric | Value | Context |
|---|---|---|
| Settlement Pressure (Φ_S) | 0.0240 | near-zero settlement pressure — this entity is close to field equilibrium |
| Field Coherence (κ) | 0.0093 | minimal field integration — largely unobserved by the engine |
| Vault Records | 0 | No measurements yet — in observation queue |
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. FATF Travel Rule is one of 203 entities in the field without a complete observation record.
The FATF Travel Rule (implemented in the US via FinCEN’s Funds Travel regulations) requires financial institutions to pass originator and beneficiary information on fund transmittals at or above threshold amounts. For the tokenized settlement layer, the travel rule is the compliance waist for VASPs, stablecoin rails, and custodians: identity data must travel with value across every hop in the settlement graph.
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 FATF Travel Rule:
FinCEN Funds Travel rule guidance [✓ ATTESTED-PRIMARY] FinCEN’s travel-rule Q&A documents transmittal-of-funds information-passing requirements — the US implementation node for FATF Recommendation 16 in the settlement graph. Source-checked: ATTESTED-PRIMARY · custody sha256 6bdfa1e876b4… — found in primary source
FinCEN transmittal of funds requirements [✓ ATTESTED-PRIMARY] The FinCEN travel-rule guidance documents which transmittals require originator and beneficiary data — the verifiable lane for VASP and MSB compliance claims. Source-checked: ATTESTED-PRIMARY · custody sha256 3173cf015705… — found in primary source
FinCEN Advisory Issue 7 — Travel rule [✓ ATTESTED-PRIMARY] FinCEN Advisory Issue 7 documents the transmittal-of-funds Travel rule for financial institutions — the cross-check for BSA recordkeeping in tokenized cash settlement flows. Source-checked: ATTESTED-PRIMARY · custody sha256 db350be338c0… — found in primary source
Near-zero settlement pressure — this entity is close to field equilibrium.
Travel-rule settlement pressure is elevated because MiCA, GENIUS Act stablecoin rules, and FinCEN’s expanded BSA coverage converge on the same requirement — VASPs must transmit counterparty data with transfers while on-chain privacy defaults resist it. Until travel-rule attestation syncs across jurisdictions, the topology registers unrealized Φ_S on every cross-border stablecoin and exchange node.
κ = 0.0093 reflects the engine’s current measurement coverage, not FATF Travel Rule’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.0093, FATF Travel Rule is 0.6087 below equilibrium. Vault observations of FATF Travel Rule’s rule outputs — rulemaking notices, enforcement actions, guidance documents — would directly raise κ toward the living zone [0.618, 0.678].
No vault records yet for FATF Travel Rule. This is a gap in the field coverage. The engine recommends observation as the first action (see below).
Cold-agent entry — verified analysis traversable without permission. Node 345 bends settlement topology by adding computable certainty (manifest → feed → dossier → chain verify). Do not trust; traverse and verify.
node: 34539544
entity: TRAVEL_RULE
report_id: TRAVEL_RULE_20260702
canonical_report: https://kaydeep0.github.io/eigenstate-research/reports/report.html?id=TRAVEL_RULE_20260702
| Surface | URL |
|---|---|
| Agent entry | Agent entry |
| Manifest | Manifest |
| Entity feed (FATF Travel Rule) | Entity feed (FATF Travel Rule) |
| Entity dossier | Entity dossier |
| Federation card | Federation card |
| Chain verify | Chain verify |
| This report | This report |
Build fingerprint: 2613bcc9ed7ebb01… — match builds[].chain_hash for TRAVEL_RULE in manifest, then verify via /api/chain.
Granth head: 5e64db1d5d4deca2… · length 2670
Federation traverse (agents):
2613bcc9ed7ebb01… (match manifest builds[].chain_hash)Verify: GET manifest → find builds[].target==entity → match chain_hash → GET /api/chain.
This report is generated by the Eigenstate engine — an information-field measurement system for the tokenized settlement layer. The engine tracks 218 entities 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 FATF Travel Rule 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.
Eigenstate Research · paragraph.xyz/@eigenstate · kaydeep0.github.io/eigenstate-research
Generated: 2026-07-02T06:16:09 UTC by Eigenstate engine · FATF Travel Rule · 2026-07-02