How this page is written, and why
There is a version of this argument that says central banks intend to devalue currencies deliberately in order to force adoption of digital ones. This page does not make that argument. Not because the concern about programmability is unserious — it is serious, and central banks discuss it in their own design papers — but because a claim about motive cannot be evidenced, and stating one would give any regulator reading this a reason to dismiss everything else.
What follows compares design features that are documented. A currency either can be programmed to expire or it cannot. That is checkable. It is also the whole argument, and it does not need help.
Four kinds of money, side by side
| Physical cash | Bank deposit | CBDC, as designed | ASC / Meridian | |
|---|---|---|---|---|
| What backs it | Central bank promise | Bank balance sheet, plus deposit insurance to a limit | Central bank promise | A fixed weight of gold. 0.047424g per Noble, unchanged by anyone |
| Can the issuer change its value? | Yes — by issuing more | Yes, indirectly | Yes — by issuing more | No. The weight is the unit. Issuing more Nobles requires more gold |
| Can it be made to expire? | No | No | Technically possible in most designs; proposed in some | No. There is no expiry mechanism to invoke |
| Can spending be restricted by category? | No | Only by the holder, on their own card | Technically possible where programmability is included | Only by the holder. Card controls exist, and only the holder can set them |
| Who can freeze it, and on what basis? | Nobody, once held | The bank, or an authority, under law | The issuer, directly | Only under a verified court order, capped at 7 days extendable once to 14, actioned through the hub in that jurisdiction. Inbound still lands |
| Is the record auditable by the holder? | No record exists | A statement the bank produces | Depends on design | Hash-chained. The holder can verify a payment happened and prove a refused collection was attempted |
| Works without a network? | Yes | No | Offline modes are proposed, mostly unproven | No — but physical cash can be ordered and delivered against a holding |
Why a weight, and not a promise
That gap is the argument. If official inflation fully captured what happened to the currency, gold would trade near three hundred dollars. It does not. The difference between what was measured and what the market actually charges for an unchanging quantity of metal is what a holder of currency absorbed without ever seeing it on a statement.
The mechanism is not mysterious. Bretton Woods ended in August 1971 when convertibility was suspended; from that point the constraint on issuance was policy rather than metal. Gold has risen in every decade since, not because the metal changed, but because the yardstick did.
Competition, or infrastructure?
| Where Meridian genuinely competes |
|---|
| As a store of value. A holder choosing between a currency whose supply is a policy decision and a unit fixed to a weight is making a real choice, and we expect to win some of it. That competition is with the currency, not with the institution issuing it. |
| As settlement infrastructure. This is squarely aimed at what correspondent banking does today, and the case is made on speed, cost and the order in which compliance runs. See the institutional settlement demonstration. |
| Where it does not compete at all |
|---|
| Monetary policy. Meridian has no view on interest rates and no mechanism to affect them. It is not attempting to replace a central bank's function. |
| Legal tender. Taxes are payable in national currency and nothing here changes that. ASC converts to and from fiat precisely because people live in fiat economies. |
| Supervision. We are pursuing authorisation rather than avoiding it, and every control on this system is built to be operable by a regulator: court-ordered freezing, full audit trail, compliance before settlement rather than after. A network that helps a fraud investigation conclude is not a network a supervisor should want to prevent. |
What this page is, and isn't
What's real here
The comparison rows describe documented design properties, not predictions of behaviour. The 1970 gold average, the Bretton Woods parity, the CPI-adjusted equivalent and the 1976 and 2011–13 declines are all published third-party figures. The Meridian column describes mechanisms that exist and can be exercised elsewhere on this site: the court-order freezing with its seven-day cap, the holder-set card controls, the hash-chained record, and physical cash delivery are all demonstrable rather than asserted.
What this is not
Not a claim about any central bank's intentions, and deliberately so. CBDC designs vary widely by jurisdiction, several explicitly rule out programmable restrictions, and some are at consultation stage rather than built — describing them as a single monolithic thing would be inaccurate. “Technically possible” means the capability exists in a published design, not that anyone has committed to using it. Meridian is not authorised in any jurisdiction, has no customers, and this page is not an offer, solicitation or political statement.
