FATF Travel Rule: Field Position Report

Eigenstate Research · August 19, 2026

Publication snapshot (dated). Live SoT Φ_S / κ / M1 ledger overlay on the Pages report. Methodology · Numbers glossary. E = ΔI/A, G = ∮E·dl, Protocol Truth → 1/φ

Publication field context

Global field state unavailable; run parkash to refresh.

What it is

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.

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 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 · status_at_publish=ATTESTED-PRIMARY · custody sha256 bbc04d908506…. found near location anchor 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 · status_at_publish=ATTESTED-PRIMARY · custody sha256 9933285c2252…. found near location anchor 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 · status_at_publish=ATTESTED-PRIMARY · custody sha256 911e256b5310…. found near location anchor in primary source

Field read

Settlement Pressure (Φ_S = 1.6421)

High settlement pressure; this entity is pulling field energy without reciprocal observation.

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.

Coherence (κ = 0.3320)

Moderate coherence; partial integration into the measurement field.

The equilibrium attractor is κ = 1/φ ≈ 0.618. At publish κ = 0.3320, FATF Travel Rule is 0.2860 below equilibrium. Attested observations of FATF Travel Rule's rule outputs (rulemaking notices, enforcement actions, guidance documents) would raise κ toward the living zone [0.618, 0.678].

Vault coverage @ publish

vault@publish = 0 for FATF Travel Rule in this dated snapshot (no trimmed cycle-vault rows at publish). This is not a claim that the live M1 ledger is empty. Re-check the Pages hero M1 ledger obs and the entity dossier.

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.

Human pages:

• Methodology
• Numbers glossary
• Entity dossier (HTML)
• Verify walkthrough
• Related reports

Core equations:

• E = ΔI/A: efficiency, information gained per unit action (Kirandeep's Law)
• G = ∮E·dl: accumulated field circulation along topology paths
• PT → 1/φ: Protocol Truth converges to golden-ratio equilibrium (1/φ ≈ 0.618)
• Φ_S: settlement pain, unrealized settlement pressure per entity
• κ: field coherence, integration of settlement activity across the topology

Published implementation: helixhash v0.1.1 (Zenodo DOI 10.5281/zenodo.18413995)

vault@publish: 0 for FATF Travel Rule in this dated snapshot. Publish-time κ and Φ_S may be topology-derived in the prose; live M1 ledger obs on Pages can differ. See numbers glossary.

Note: Internal topology codenames are not used in public reports. All entity names in this report are public names.