The input sheet: every deployment starts with decisions, not code
Before anything is provisioned, the engagement collects a short input sheet. Every field is a decision the licensee owns, and with the sheet in hand the stand-up itself is measured in hours:
- Identity. The cell's name, its public hostname, and its chain identity -- the chain ID the validators will report from block one.
- The currency. Code, display name, the fiat peg it represents, and the maximum supply -- the enforced cap lives in the on-chain currency object, not in a brochure.
- Issuance state. Always the same answer at the start: disabled. Mint and burn are bound to the issuer's own keys, and issuance is switched on only when regulatory approval exists.
- Regulatory framing. The national framework the cell is designed to align with. This is a design target, never a claim of approval -- the distinction is kept explicit on every page the deployment renders.
- Federation posture. Isolated, or connected by governed corridor -- and to whom.
- The face. The site, the colors, the language of the hero line -- the parts a citizen sees.
Hours: the demonstration
From a completed input sheet, a demonstration cell -- its own chain, its own currency object with issuance off, its own public site -- comes up in hours, not weeks. That speed is the point: the demonstration is the proof of deployability. A prospect is not shown a slide deck; they are shown their sovereign economy already running, carrying the demonstration disclaimer it will keep until it is a licensed, contracted deployment.
The demonstration is the sales artifact. It shows a sovereign their economy already running -- and everything that must still be true before it can be more than a demonstration.
Demo to go-live: five gates
What separates a demonstration from a national deployment is not more software. It is five gates, each with a clear owner and a clear test:
1. Re-skin -- hours
The same running chain takes on the customer's identity: names, colors, language, domain. Nothing about the engine changes.
2. Validators -- days one to three
The state's own validator set is stood up on its own infrastructure: a genesis ceremony, post-quantum ML-DSA-65 validator identities pinned from block zero, and multi-host BFT consensus closed out inside the engagement. From this gate on, the nation -- not JIL -- operates the machines that finalize its blocks.
3. Policy and banking -- days three to five
The jurisdiction's policy zone is bound -- identity requirements, limits, sanctions posture -- and the reserve side is connected: reserve accounts established and attestation feeds wired so the proof-of-reserve relation is fed by the banking system, not by hand.
4. Stablecoin issuance -- approval-gated
Issuance remains disabled until the regulator's approval is in hand. Because mint and burn are bound to the issuer's own keys, enabling issuance is a licensing event, not an engineering one -- the rest of the economy runs in the meantime.
5. Certification and cutover -- about a week
A certification pass walks the deployed cell against its manifest, and the offering gate stays closed until the legal, KYC, and banking workstreams have cleared. Then DNS cuts over to the national domain. A cell converted from a running demonstration completes this path in about a week; a brand-new sovereign cell from scratch remains roughly two weeks.
Prerequisites for a full deployment
The runbook is fast precisely because it refuses to improvise the slow things. These are the prerequisites a full national deployment requires -- collected early, because no gate below can be engineered around:
What the licensee brings
A license and a tier. Managed, Regulated, or Full Sovereign -- the tier decides who operates what, and it is a governance choice made before provisioning. The Licensing Model describes the three.
Legal authority and regulator engagement. A mandate to run the deployment in the jurisdiction, and a live path to the regulatory approval that issuance waits on. The platform ships with issuance disabled; only the approval opens it.
Validator infrastructure and key custody. Hosts for the validator set (or a Managed-tier election for JIL to operate them), participants for the genesis ceremony, and a custody policy for the keys -- the state's keys are the state's.
Banking and reserves. Reserve accounts, a chosen reserve model -- cash, treasury bills, government bonds, or a mix -- and an independent auditor or attestation provider to feed the proof-of-reserve anchor.
Compliance data. An identity/KYC provider, sanctions list sources, and the jurisdiction's policy parameters -- the rules the chain will enforce in consensus have to be decided by someone with the authority to decide them.
Operations. A staffed operating function -- or the Managed tier -- for monitoring, upgrades, and incident response once the chain is the nation's.
A federation posture. If the cell will settle across borders, corridor agreements with its counterpart cells -- corridors are governed instruments, opened deliberately, never ambient connectivity.
The rules that are not optional
Three disciplines hold on every deployment, demonstration or national, and they are written into the runbook rather than left to judgment. The demonstration disclaimer stays on every generated cell until that cell is a licensed, contracted deployment. Regulatory framings are design targets, never claims of approval. And issuance ships disabled -- no demonstration ever mints anything that could read as a live national currency offer.
A note on standing
This page describes an engineering and delivery procedure. It is not an offer, solicitation, or sale of securities or virtual assets, and it is not legal, tax, or investment advice. Timelines describe the delivery motion for a prepared licensee; specific engagements are governed by their definitive agreements.