Skip to content
Fiat-on-Chain

Your ledger entry, made portable.

A bank deposit that moves at 02:00 on a Sunday — and never leaves the bank.

Fiat-on-Chain binds regulated money to the ledger that already holds it, as tokenized deposits, and settles any asset against it in central bank money. Nothing leaves your balance sheet. Nothing needs a reserve, a data feed or a bridge.

Release candidate v1.0.0-rc.1 – Independent audit not yet complete – Sandbox entry in Georgia sought

Regulator's view · one bank's tokens · one bar per minute

minute 1,042 · tokens = ledger · difference 0

Your regulator reads this from a computer it runs. Every cycle, one minute on the reference network, the tokens in existence are proven equal to your ledger — and if they ever were not, token creation would stop by itself.

Better where a bank is judged, built to settle in seconds, and the deposit stays yours.

See the comparison

Built by someone who has done this with central banks and major banks before.

  • National Bank of Georgia
  • SoftBank
  • JPMorgan
  • Morgan Stanley
  • ING
  • Lehman Brothers Inc.
  • Bank of England sandbox

Institutions the founder has built with, worked in or delivered for. Shown as a record of past work. No endorsement of Fiat-on-Chain is implied.

The full record
  • reserve pools

    No reserve pool behind the token. It is the issuer’s own liability, bound to your own ledger. Settlement is prefunded at the central bank.

  • reserve data feeds

    You write the fact yourself, as the posting. Only outside prices — an FX rate, say — need a signed source.

  • token bridges

    Cross-currency and cross-asset settle both sides at once, on the rail. No substitute token, ever.

Who it is for

Enter under the license you already hold.

One protocol, four roles. Each keeps its regulator, its balance sheet and its customer. Issuers are few and licensed; participants are many. Most institutions — and most of a bank's clients — are participants.

Who fits where: issuers, participants, asset legs, money legs and supervisors
  • Issuers

    Banks, payment and e-money institutions, credit unions and cooperative banks, broker-dealers holding client money where the regime allows. They hold money under a license and issue tokens of their own liabilities.

  • Participants

    Asset managers and funds, broker-dealers and venues, insurers and pension funds, FX dealers, trade-finance and remittance companies, fintech lenders, exchanges, marketplaces, corporate treasuries. They hold and move tokens through an issuer’s account.

  • Asset legs

    Central securities depositories, transfer agents, fund registrars, tokenization platforms, custodians acting as registers, central counterparties. They keep the register and settle delivery-versus-payment.

  • Money legs and supervisors

    Central banks as settlement authority and supervisor; designated settlement banks where direct access is unavailable; financial intelligence units reading the policy-decision stream.

Two limits by design: only licensed holders of money can issue, so every token is a claim on a supervised balance sheet; and each institution's regulatory obligations stay its own — identity attestation speeds onboarding under its rules; it does not replace them.

How it works

The mint is the posting.

Three mechanisms replace the reserve, the monthly audit and the bridge.

How a payment settles on FoC-PThe payer's bank lowers the payer's deposit by 100 and destroys the matching token. The central bank moves 100 from the payer's bank's settlement account to the payee's bank's. The payee's bank creates a token and raises the payee's deposit by 100. The three steps are one transaction on the shared ledger: all happen or none does. A read-only supervisor node checks every cycle that tokens equal each bank's ledger. BANK ABANK LEDGER−100ATOKEN−100One entry, two recordsPAYERpays 100 SHARED LEDGER One transaction. All of it, or none. 1BURN Token A is destroyed A 2SETTLE CENTRAL BANK BANK A −100 BANK B +100 3MINT Token B is created B BANK BBANK LEDGER+100BTOKEN+100One entry, two recordsPAYEEreceives 100 SUPERVISOR NODE read-only, at the central bank Tokens = ledgers, every cycle Release candidate, on the reference network. The central bank's role is proposed.

One atomic event

Your core posts a credit and the token is created in the same event; the posting stays pending until the network confirms, and is reversed through ordinary core mechanics if it does not. Two separately administered key groups, held in your own hardware security modules as certification requires, must both sign — a single broken system cannot create money.

How it works

Evidence

Built, not proposed.

The reference implementation is at release candidate and runs the whole protocol on a four-validator permissioned network — with the central bank's roles simulated.

  • Two issuers on two licenses — a bank's deposit tokens and a payment institution's safeguarded funds, settling with committed confirmations on every receipt.
  • Two currencies — lari and pounds, settled against each other with escrows that provably never outlive their deadlines.
  • A bank failure, rehearsed — frozen, customers moved to another bank, both banks proving valid, the record acknowledged by the supervisor.
Release candidate. An internal review is complete; third-party audit and formal verification start from the second release candidate.
v1.0.0-rc.1Release candidate. An internal review is complete; third-party audit and formal verification start from the second release candidate.
Conformance cases; harnesses in TypeScript, Solidity, Go, Rust, Python and Java
1,083Conformance cases; harnesses in TypeScript, Solidity, Go, Rust, Python and Java
Validators confirm every settlement — in a production network the central bank is designed to run one of the four
3 of 4Validators confirm every settlement — in a production network the central bank is designed to run one of the four
Planned: contract to first token, over ISO 20022, the message family your core already speaks
90 daysPlanned: contract to first token, over ISO 20022, the message family your core already speaks

The regulator's screen

What your supervisor sees — continuously.

One screen for three audiences: the central bank sees its own tool, a bank sees what its regulator will see, an investor sees the moat.

The supervisor console: tokens against bank ledgers per minute, breaker state, exposure by issuer, live event stream
How it is secured

Georgia first

Georgia first, then the region.

The first network is proposed for Georgia. Entry to the National Bank of Georgia’s tokenized-instrument sandbox is sought: a bank issuer under letter of intent, a payment-institution issuer and a participant platform to be confirmed, and a supervisor node designed for the central bank, with its settlement-leg role proposed and subject to sandbox design and approval. Then the South Caucasus and Central Asia.

“The two ledgers were never allowed to be two.”

Every design decision follows from that sentence. Customers keep their bank. Banks keep their deposits, their systems and their regulator. The central bank keeps the final word.

Keep the deposit. Add the capability.

Request a briefing