MERIDIAN GLOBAL FINANCE

ESTC — the settlement layer between institutions, replacing SWIFT's job.

Every citizen-level demo on this site moves money between two people. This one moves it between two institutions — the scale SWIFT actually operates at, and the scale this is built to compete with directly. Most correspondent banking pushes send first and screens after, sometimes holding a transfer mid-flight for days. Here it's reversed: KYC and AML confirm first, as their own step, and Send stays disabled until that's cleared — nothing moves unverified, and once it's cleared, execution is fast enough to measure in milliseconds, not days. Open any past transfer and the full compliance record is still there, exactly as it was committed. See the real numbers below, not just the claim.

Real SHA-256 hash chain Real minted-and-burned ASC settlement tokens Illustrative KYC/AML — not real screening Not the production network

Initiate an institutional transfer

Bank-to-bank, not citizen-to-citizen. Large value, cross-border, fully documented.
Real banks push send first and screen after — ours confirms KYC/AML before Send is even enabled, so nothing moves unverified.
Chain verified — all blocks intact
Rūnstæf self-check: pending first block…

Look up a settlement token

The token is burned at settlement, but its record is not. This is the same code that appears on both parties' account statements — enter it here to pull the full permanent record: who sent it, who received it, when, and whether KYC/AML actually cleared before it moved. A restricted, internal lookup, not a public one — the whole point is that only the receiving institution can confirm a transfer actually happened this way.

Apply a freezing order

Requires a genuine court order reference — no order, no freeze. The 13 Spire hubs are each their own clearing house, staffed by Meridian's own people, each one adhering to that country's local banking law and the same shared network-wide bylaws. An order actions through the hub the institution falls under — a UK order actions via London, a US order via Texas, and so on — which is what makes enforcement legally coherent: each hub is genuinely subject to its own jurisdiction, not reaching into someone else's. Inbound payments still land; only outbound is blocked. A hold is 7 days by default, with one possible extension to a hard 14-day maximum — after that it lifts automatically unless converted into formal proceedings. Recognised national authorities (PRA-equivalent bodies, designated fraud agencies) may operate under separately-defined access outside this specific workflow.

Settled transfers

Click any transfer to open its full KYC/AML compliance token.

Raw ledger

Why the order matters, not just the speed

Correspondent banking checks compliance after the money moves; ESTC checks it before. That's not a marketing line — it's the actual sequence difference, and it shows up directly in how long transfers take today.
Process (today, elsewhere)Typical durationWhy
Domestic wire transferSame business dayFedwire/CHIPS-class networks, minimal cross-border complexity
International wire transfer1–5 business daysIntermediary bank reviews, AML/sanctions screening — run after the payment is sent
Regular stock trade settlementT+1 to T+2Standard secondary-market settlement cycle in most developed markets today
IPO / primary-market share allotmentHistorically up to 15–20 days in some marketsManual subscription processing, allotment, and refund cycles — a genuinely separate, slower process from ordinary trading
ESTC transfer, once compliance clearsMeasured live, this sessionCompliance already confirmed in Step 1 — Send only ever executes the already-cleared transfer
The 1–5 day international wire figure and the 15–20 day primary-market figure are both drawn from public industry sources, not invented for this page — the point isn't picking the most dramatic number, it's that both are real, current, and driven by processes ESTC restructures rather than merely speeds up. The historical T+14 settlement convention itself dates back to 18th-century Amsterdam-London trades, when settlement genuinely took as long as a horse-and-ship courier — some of what's "standard" in finance today is still catching up to that era, not the 21st century.

What this demo is, and isn't

What's real here

The hashing is genuine SHA-256, computed by your browser as you interact — nothing precomputed. The token mechanic is genuinely computed too: sending currency converts into freshly-minted ASC settlement tokens at the live gold price, those tokens are what actually transmits, and they're burned the instant they arrive, crediting the receiving currency — you can see both legs in the conversion preview before you confirm. These settlement tokens are a genuinely different thing from the ASC/Aurum balance a citizen holds elsewhere on this site: they're never spendable, they exist only for a single transfer's transit, and because they're minted on send and burned on arrival rather than drawn from a shared pool, there's no supply limit tied to this mechanism specifically — the constraint is real gold backing the unit of account, not a finite token stockpile. The 0.05% network fee, matching the rate documented in the ESTC Codex, is genuinely calculated and declared before either compliance step runs, not added silently afterward — it's charged to the sender on top of the amount sent and never reduces what the receiver gets. The sequencing is real too, not cosmetic: Step 1 generates and confirms the KYC/AML token without touching the ledger at all; Send stays genuinely disabled until that's done, and changing any transfer detail after confirming invalidates it and disables Send again, forcing a fresh confirmation. Each transfer's compliance token is permanently attached to its block; opening a past transfer shows exactly what was recorded at the moment it settled, unchanged. The millisecond execution time shown after Send is a real, measured browser timing of the hashing and commit — not a claim about cross-border network settlement, which is the separate, clearly-labelled target figure discussed below.

What's simulated

The KYC/AML screening itself is illustrative — this page doesn't check a real passport, run a real sanctions-list match, or perform real Travel Rule compliance; it always returns "clear" so the mechanic is visible. ESTC's real 238+ settlement codes and same-jurisdiction/cross-regional timing are represented here as a single simplified pair (~15 sec same-region, ~1–4hr cross-region, matching Echelon Chain's own target figures) rather than the full code set. FX rates for USD and EUR are simple fixed illustrative constants, not a live market feed — only the gold leg is genuinely live. The 0.05% fee is calculated and charged to the sender, but this page doesn't model where that revenue actually goes afterward — no ledger of accumulated fee income, no revenue-recognition system, just the charge itself, declared and logged. The token lookup and freezing-order log only search this browser tab's session, since there's no real backend here — in production both would query the permanent, access-controlled Echelon record, not client-side memory that clears on refresh. The freezing order itself accepts any text as a "court order reference" — there's no real judicial verification here, no real institution registry, and no real law-enforcement integration; it demonstrates the mechanic (outbound blocked, inbound unaffected, capped at 7 days with one extension to a 14-day maximum, gated on an order reference, permanently logged), not a functioning legal process. The 7-day countdown is genuinely computed against real elapsed time — the "Fast-forward 7 days" button exists purely so the auto-expiry can be demonstrated in one sitting rather than an actual week.