◆ FutureChain

FutureChain AB · Sweden

Payments that arrive
already compliant.
Not screened afterwards.

A proof-of-work settlement chain that speaks ISO 20022 natively. Every transaction carries a real PACS.008 message, is screened against sanctions and jurisdiction rules before it can enter a block, and settles with post-quantum signatures.

Get started Browse the live chain ↗
Settled pacs.008.001.13 · block 1,121,699 
<!-- the message the chain actually settles -->
FIToFICstmrCdtTrf
  GrpHdr
    MsgId              MSG-8f3c1a20
    SttlmInf/SttlmMtd  INDA
  CdtTrfTxInf
    PmtId/UETR         8f3c1a20-6b14-4e5d-9a77-2c0e51db4417
    IntrBkSttlmAmt     125.00 FTC
    DbtrAcct/Othr/Id   fc_VHLPNqo7dqq2yU32ot2LWSmDRhp3KZRyar
    CdtrAcct/Othr/Id   fc_VQsvaFW5QGh7FAN1oaNryD6x9Ftwu42c9j

compliance   Heimdall — sanctions, jurisdiction, wallet screening
attestation  Ed25519 + FALCON-512 hybrid signature over the compliance decision
             (hybrid required at consensus since block 810,000)
finality     included in the next block, ~13 s
The chain

Compliance is a consensus rule, not a service you call

On most chains, screening happens off to the side — a service that can be skipped, time out, or be reconciled after the fact. Here a payment that has not been screened is not a valid payment. The gateway is fail-closed: if compliance cannot answer, the transaction does not settle.

ISO 20022 native

Real PACS.008, not a memo field

Structured debtor, creditor, remittance and UETR data travel with the payment and are retrievable for audit — the same message a bank would send.

Post-quantum

Hybrid Ed25519 + FALCON-512

Compliance attestations are hybrid-signed and consensus-enforced. Payment signatures carry the post-quantum material alongside the classical one, so the record stays verifiable once enforcement is switched on — the migration does not need the history re-signed.

Screening

Heimdall, before the block

Jurisdiction, wallet and sanctions-name screening are a precondition of inclusion — a payment that fails them never reaches a block, rather than being flagged after settlement. Further risk-scoring modules run in shadow alongside, scoring and recording without blocking, and graduate individually once calibrated.

Regulatory

Built for MiCA from the start

Swedish issuer, LEI registered, crypto-asset white paper notified to Finansinspektionen on 2 June 2026 and published here as filed. Notification is a disclosure obligation, not a licence — authorisation is in progress, not claimed.

RefusesNon-compliant paymentsat ingest, not after settlement
EmitsA real pacs.008 messagethe same one a bank would send
SettlesIn seconds, with a fixed capno fee auction, no priority lane
DisclosesIssuance and supply integrityincluding what went wrong

Deliberately no live counters here — a number printed on a page is out of date the moment it is printed. The explorer carries the current height, supply and every transaction behind them, and the white paper carries the issuance schedule as filed.

ANTON

The product surface on top of the chain

FutureChain is the rails. ANTON is what people actually use — a phone wallet, merchant tools, and a public API, all settling through the same fail-closed compliance gateway. Nothing reaches the chain without being screened first.

ANTON Pay · Android

Self-custody wallet

A 24-word seed generated on the device and never transmitted. The private key lives in the Android Keystore and signs there — it never re-enters app memory. Every send is gated on biometrics, with an optional passphrase as a second factor.

ANTON Business

Merchant tools

Payment QR with order envelope and expiry, scheduled transfers, budget pools, and reconciliation that exports the underlying PACS.008 rather than a summary line.

ANTON Comm

Contact-bound payments

Messaging with identity attestations, so paying a contact does not mean pasting a 38-character address and hoping.

Public API

rpc.futurechain.eu

TLS 1.3, a fixed endpoint allowlist, per-install bearer tokens and rate limits. Every submission is authenticated at the edge before it reaches a node.

In development

Agent-to-agent settlement

Software agents increasingly transact on someone's behalf — buying compute, settling API usage, paying each other. An ANTON agent holds its own wallet and pays other agents directly, but every payment is still PACS.008-screened, and the agent never has unilateral spending power: a human approval stays in the loop.

That combination — autonomous settlement that is still auditable and still requires consent — is the part of ANTON we think matters most. It is in active development, not shipped.

How ANTON works in detail →

Get started

Two ways in

Whether you are assessing FutureChain as an institution or building on it, start where the detail is written for you.

For institutions

Exchanges, banks, auditors, regulators

  • Crypto-asset white paper and MiCA posture
  • Supply integrity and issuance disclosures
  • Compliance architecture and control coverage
  • Independent verification against the live chain
Request the pack

For developers

Building payments and agents

  • Quickstart against the public relay
  • Build and sign a PACS.008 with the SDK
  • Wallet, balance and UTXO endpoints
  • Read any block or transaction on the explorer
Read the quickstart →