How a country gets a cell

What shows up before a country has a cell

The request arrives as a meeting, not as a chain. Someone asks whether the country can issue on its own rules. The materials on the table are a license question, a list of who may operate a node, and a slide that already assumes a public chain. A demonstration unit is treated as the currency. A fork of an existing network is treated as sovereignty. Issuance is discussed before anyone has approved the rulebook.

Those are the signs.

A country does not get a sovereign cell by deploying a contract on a public chain, and it does not get one by opening the worked example. The path written on this host is a license, an input sheet, a demonstration, and five gates. The cell is provisioned from the shared engine. It is not built from scratch for each nation, and it is not a tenant row on someone else's ledger. The chain it is provisioned onto is not EVM-compatible. Ethereum, if it is reached at all, is a bridge. The original Layer-1 reading is that fact. This page is the procedure around it.

The license comes first. A sovereign root is Class A or Class B. The licensing model and license classes readings state the prices. Class A is $2,500,000 to join and $400,000 a year. The paper names that class for global commodities and tier 1 nations. The corridor credential stays on the root sovereign. Class B is $1,500,000 to join and $250,000 a year, named in the paper for regional hubs and philanthropic desks. Up to 10 hubs are included. A further hub is $25,000 a year billed to the sovereign. That seat is not a second license. The hub's own license stays $0. An annex license is $0. An annex contains nothing under it. A new hub under a hub is rejected. Depth is sovereign, hub, annex. The public UAE desk is the Class A worked example. The public India desk is the Class B worked example. Neither page is a purchase claim. The prices are the commercial framework. Specific terms are negotiated, and this page is not an offer.

Before anything is provisioned, the deployment runbook collects an input sheet. The fields are decisions the licensee owns. Identity: the cell's name, its public hostname, and the chain-id validators will report from block one. Currency: code, display name, the fiat peg it represents, and the maximum supply, enforced in the on-chain currency object rather than in a brochure. Issuance state: disabled at the start. Mint and burn are bound to the issuer's own keys, and issuance is switched on only when regulatory approval exists. Regulatory framing: a design target, never a claim of approval. Federation posture: isolated, or connected by a governed corridor, and to whom. The face: the site, the language, the line a citizen sees. With that sheet, a demonstration cell, its own chain and its own currency object with issuance off, is the runbook's hours step, not a weeks-long build. The demonstration disclaimer stays until the cell is a licensed, contracted deployment. A prospect is shown a running demonstration, not told that a country has already joined.

Five gates separate that demonstration from a go-live, and the runbook assigns each a test. Re-skin, measured in hours, puts the customer's names, language, and domain on the same engine. Nothing about the engine changes. Validators, written as days one to three, is the gate at which the state's own set would be stood up on its own infrastructure, with a genesis ceremony. The runbook says that from this gate on, the nation, not JIL, operates the machines that finalize that cell's blocks. Read that beside the live record, not instead of it. The fleet running today is 10 validators, all operated by JIL, permissioned. The showcase is 10 in the set, 9 signing, same operator. The named validators page is the record. A country reading this page has not passed that gate by reading it. Agreement on the live set is 100% of responding validators, with a halt on divergence. That is not Byzantine fault tolerance.

Policy and banking, written as days three to five, binds the jurisdiction's identity requirements, limits, and sanctions posture, and connects reserve accounts so the proof-of-reserve relation is fed by the banking system rather than by hand. The Digital Currency Platform is the instrument those reserves back. Stablecoin issuance stays approval-gated. Enabling it is a licensing and regulatory event, not an engineering switch thrown because the software can mint. The rest of the demonstration economy can run while issuance stays dark. Certification and cutover, written as about a week, walks the cell against its manifest. The offering gate stays closed until legal, KYC, and banking workstreams have cleared. Then DNS cuts over to the national domain. The runbook's own timing note is that a cell converted from a running demonstration completes this path in about a week, and a brand-new sovereign cell from scratch remains roughly two weeks, for a prepared licensee. Those are delivery figures under the runbook. They are not a promise that a specific country is on the clock.

The prerequisites are the part the runbook refuses to improvise. The licensee brings the license, a mandate to run the deployment, and a live path to the approval that issuance waits on. It brings hosts and participants for a genesis ceremony, and a custody policy for the operator's keys. JIL does not custody the cell's banking. It brings reserve accounts, a chosen reserve model, and an auditor or attestation provider to feed the proof-of-reserve anchor. It brings an identity provider, sanctions sources, and the policy parameters someone with authority has actually decided. ATCE will enforce that published profile. It will not invent it. The licensee brings a staffed operating function for monitoring, upgrades, and incidents once the chain is theirs to run. If the cell will settle across borders, it brings corridor agreements. A corridor is opened on purpose. It is not ambient connectivity.

The corridor settlement rules travel with that corridor, and they are not optional. KYB and KYC come before corridor keys. Identity checks plug into the sovereign's national ID scheme or its approved provider. Hubs and annexes cannot send on the corridor and cannot bypass their sovereign. The oil annex on the demo cannot open one. Movement inside a hub is 0 basis points. A settled hop is 5 basis points of settled gross, paid by the initiating sovereign. The fee is escrowed with the gross. A denied trade releases the escrow and settles no fee. The sovereign operator sets the rate. JIL records the hop and the proof.

What the country does not receive, even after a careful reading, is a claim that its regulator has approved a currency, that the public holds a retail Digital Dirham, or that Saudi Arabia is a live mBridge settler. UAE-S is not the Digital Dirham and is not legal tender. AE Coin and DDSC are not the Digital Dirham and are not legal tender. Qatar and Oman are not described on this host as having issued a CBDC. INR-S is not a Reserve Bank of India purchase. The October 2026 white paper is the architecture document. It is not a signed national treaty with a named state. The JIL.ai reading does not substitute for a Statement of Authority. Nubara and Tirmore are fictional demonstration cells. They are not a way in, and this page does not link to them.

Local entities carry regulated activity when an engagement exists. This company's role on the license is the core, the provisioning, and, on the fleet that exists now, operation of the recorded validators. Holdings licenses the IP and does not operate the cell. The federation reading shows the constellation the runbook is aimed at. The cell demos are the sales artifact, carrying the disclaimer they keep until a deployment is licensed and contracted. A briefing at /connect/ is how a prepared licensee starts the input sheet. It is not itself a gate that has been passed.

Questions

Read with this

The deployment runbook, The licensing model, License classes, The federation, What is a corridor, Corridor settlement, Named validators, What is a sovereign cell.