Can the platform operating the registry mint or redeem a Currency Object's supply?

No. Every mint and redeem operation must be signed by an authority key bound to the currency object's own licensed issuer entity. The platform authors and hosts the object's registry entry, but never holds a key capable of moving its supply.

What is the object's genome?

The governance policy profile pinned to that specific currency object, defining the compliance rules a transfer must pass. Every mint, transfer, and redeem against the object is evaluated against its own genome, using the same policy-evaluation engine that also gates value crossing between federated blockchain cells, rather than a single global rule set applied to every currency alike.

What happens to a currency object if its proof-of-reserves attestation lapses?

Governance can move the object into a Paused lifecycle state, which blocks further minting and transfers while still permitting redemption so existing holders can exit. A Retired object remains redeem-only until its outstanding supply reaches zero.

Currency Object with Pre-Execution Genome Validation

Executive Summary

A Currency Object bundles everything that makes a regulated stablecoin actually regulable — a licensed-issuer binding, jurisdiction, reserve model, mint and burn authority keys, a maximum supply ceiling, a lifecycle state, and a governance genome defining the compliance rules that must pass before value moves — into one on-chain-pinned object, rather than a bare balance mapping with an admin-controlled mint function bolted on separately.

Every mint, transfer, and redeem operation against a Currency Object is evaluated, before execution, against that specific object's own pinned genome, using the same policy-evaluation engine that also gates value crossing between federated blockchain cells — so one shared engine enforces distinct monetary policy per currency, parameterized entirely by each object's own configuration rather than by a code fork. Fail-closed defaults apply throughout: an unpinned or zero lifecycle-state slot reads as Draft, in which nothing may circulate.

Core Innovation: One settlement and policy-evaluation engine, independently parameterized per currency by that currency's own pinned genome, so each regulated instrument can carry distinct monetary policy without forking the underlying engine — and the issuing platform itself never holds the key capable of moving a currency's supply.

Problem Statement

Typical stablecoin contracts place mint and burn authority behind a single admin key with no jurisdiction-scoped policy attached to the token's own on-chain identity. Where compliance exists at all, it usually lives in an off-chain gateway that is not cryptographically bound to the token, and reserve claims are frequently self-attested with no on-chain-checkable relation to outstanding supply.

4

Lifecycle states, each independently gating which operations are permitted

1

Shared evaluation engine used for both currency transfers and federation-border crossings

0

Instances where the platform itself is authorized to mint or redeem a licensed issuer's currency

Why Existing Solutions Are Insufficient

Typical stablecoin contracts: a single admin key controls mint/burn with no jurisdiction-scoped policy bound to the token's own identity.
Wrapped or synthetic tokens: compliance, if present, lives in an off-chain gateway disconnected from the token's on-chain identity.
One-size-fits-all compliance middleware: a single global rule set applied uniformly, unable to give one currency a different reserve model, jurisdiction, or policy profile than another without a code fork.
Self-attested reserve claims: no on-chain-checkable relation between outstanding supply and the reserves a stablecoin claims to hold.

Technical Architecture

Registry Field	Purpose
Header	Code, display name, jurisdiction, decimals, unit par, max supply
Issuer binding	Cryptographic commitment to a specific licensed local entity, part of the app hash
Mint / burn authority	Keys custodied by the licensed issuer, never by the platform
Genome / policy profile	This object's own governance rules, evaluated before every transfer
Lifecycle state	Draft / Active / Paused / Retired
Reserve root	Hash-committed reserve attestation backing the outstanding supply

Every field above is pinned in a domain-separated, SHA-256-addressed storage slot under one reserved system account, so the whole object is part of the same storage merkle and app hash as everything else on the chain — zero new state-plumbing required.

Lifecycle States

State	Permitted Operations
Draft	Authored but nothing circulates
Active	Mint, circulate, and redeem all permitted
Paused	Mint and transfer blocked; redeem-only so holders can exit
Retired	Redeem-only until outstanding supply reaches zero

Issuer Binding, Never the Platform

The object is cryptographically bound to a specific licensed local issuer entity — never to the platform authoring the object. Only that issuer's own mint and burn authority key can move supply, and only when the genome gate allows it; the platform that operates the Currency Object registry cannot itself mint or redeem.

Pre-Execution Genome Gate

Before any mint, transfer, or redeem executes, it is evaluated against the SAME policy-evaluation engine used for the federation-border arrival gate, parameterized by this currency object's own pinned genome rather than a shared global rule set. Fail-closed: an unauthorized, mis-signed, over-ceiling, or genome-denied operation is rejected outright with no partial state change.

Exactly-Once Replay Protection

Mint and redeem operations are each keyed to a dedicated replay slot, so no double-mint or double-redeem is possible even under a retried submission of the same request.

Prior Art Differentiation

Approach	Compliance Binding	Mint/Burn Authority	Reserve Checkability
Typical ERC-20 stablecoin	None built in	Single admin key	Self-attested
Off-chain compliance gateway	Bolted on, not token-bound	Varies	Varies
Generic policy engine over tokens	One global rule set	Varies	Varies
JIL Sovereign	Per-object genome, on-chain pinned	Licensed issuer only, never the platform	Hash-committed, on-chain checkable

Patent Claim

Independent Claim 91: A computer-implemented system for a regulated digital currency, comprising: an on-chain registry that pins, for a currency object identified by a unique code, an issuer-entity binding, a reserve model, a maximum supply ceiling, a lifecycle state selected from at least a draft state in which no supply circulates and an active state in which supply may circulate, and a governance policy profile specific to that currency object; a mint-and-redeem authorization mechanism in which supply-affecting operations are permitted only when signed by an authority key bound to the currency object's licensed issuer entity, never by a key controlled by the platform operating the registry; and a transfer-evaluation mechanism that, prior to executing any mint, transfer, or redeem operation against the currency object, evaluates the operation against the currency object's own pinned governance policy profile using a shared policy-evaluation engine also used to gate value crossing between federated blockchain cells, and rejects the operation without state change upon a policy denial.