Settlement is not issuance
An ordinary blockchain is a settlement rail. It moves a token from one address to another and asks no questions: it does not know who issued the token, what stands behind it, or whether the transfer ought to be permitted at all. On such a chain a "currency" is nothing more than a smart contract -- a lone program that anyone may deploy and that carries no inherent standing as money.
The Digital Currency Platform (DCP) begins from the opposite premise. Where a chain settles value, DCP defines the currency. A unit issued through DCP is not a stray contract but a Currency Object: a managed financial instrument that carries, on-chain, everything a regulator would ask of a real currency.
A blockchain settles value. The Digital Currency Platform defines the currency -- and binds its law to every unit that moves.
The Currency Object
Each Currency Object is authored, not merely deployed. Its record names, in consensus, the terms of its own existence:
- Issuer and issuing authority -- the licensed institution that stands behind the instrument, bound to specific keys.
- Reserve model -- what backs a unit, and the on-chain relation that must hold between reserves and outstanding supply.
- Mint and burn authority -- the precise keys permitted to create or destroy units. No one else may, and the platform operator cannot.
- Settlement rules, identity requirements, and jurisdiction -- who may hold the instrument, at what level of verified identity, and under which nation's rulebook.
- Audit requirements and proof-of-reserve configuration -- how solvency is attested and where its root is anchored.
- A live policy profile -- the compliance law the instrument obeys, adjustable by governance without redeploying the currency.
Because these terms live in the object itself, the currency is legible: any party can read what the instrument is and what governs it, and every validator agrees on the answer.
The life of a unit
A unit of a DCP currency has a lifecycle rather than a mere balance. It is minted by the licensed issuer against a reserve deposit, signed by the issuer's own mint key. It circulates holder to holder. It is redeemed by an issuer-signed burn when a holder returns it for value. Each of these three acts produces an immutable audit receipt -- a tamper-evident record of what happened and why it was allowed -- committed into the chain's state. The audit trail is not reconstructed after the fact; it is a by-product of the currency operating as designed.
Solvency as an on-chain relation
Because the circulating currency is a native denomination and its outstanding amount is the real total supply, the relation reserve ≥ outstanding is checkable on-chain rather than self-reported. Reserves are held in cash, Treasury bills, and government bonds; they are independently audited; and the attestation root is pinned on-chain and published as a signed, tamper-evident verify link. Live proof-of-reserve vendor feeds are on the production roadmap -- today the platform pins and anchors the attestation root; automated third-party reserve feeds are still being wired.
ATCE: whether an action may occur at all
The rule that makes a Currency Object more than a token is the ATCE -- the Adaptive Trust, Compliance and Execution Engine. Every transfer of a DCP currency passes through it before value moves. ATCE weighs the identity level presented, the jurisdiction of sender and recipient, the amount against a per-transaction ceiling, a live risk score, and sanctions status, and returns a single verdict: allow, deny, or require approval. It fails closed -- if a required fact is missing or a policy is malformed, the transfer is refused -- and every verdict carries an explicit reason code and a tamper-evident record hash.
For a monetary authority this changes the nature of control. Adjusting the law of a currency is not a code deployment or a hard fork; it is a setting. A central bank can raise a required identity tier, tighten a per-transaction limit, or add a jurisdiction to the allow-list the way one adjusts a threshold on a dashboard, and the change governs the very next transfer.
Reserves, banking, and the CBDC stance
A DCP currency is meant to live inside the existing financial system, not beside it. Reserves sit in conventional instruments -- cash, Treasury bills, government bonds -- and the platform is designed to connect to the rails institutions already use: SWIFT, ACH, SEPA, RTP, and FedNow. A sovereign can issue an instrument such as JUSD, JEUR, JN1, or JN2 whose backing is auditable, whose movement is compliant by construction, and whose settlement reaches the accounts a treasury already holds.
This is also why JIL does not compete with a central bank digital currency. A CBDC is a policy and a liability of the issuing state; DCP is the rail that such a currency can run on -- the issuance, reserve, compliance, and audit machinery a monetary authority would otherwise have to build. JIL is not a rival to the sovereign's money. It is the infrastructure beneath it, and the sovereign keeps the keys, the reserves, and the rules.