Template permissions and notice periods

Registering a template#

Only governance can register a template. Registration starts a fourteen-day public notice; until it has run, the factory refuses to create from the template. The launch templates, registered at deployment, carry no notice.

A template that is registered cannot be edited. Its content — every bound, its class, its outcome count, its lane — is hashed to a fingerprint, and the factory checks at registration that:

• its id is new;
• its resolver is on the allowlist fixed when the factory was deployed;
• its settlement timer names a known lane (60 seconds, 15 minutes, 24 hours or 48 hours);
• its risk class is one the fee model knows;
• its masks name only sources, metrics and comparators the catalogue has; its thresholds and windows are ordered; a template that can express a band has a non-zero grid.

Retiring a template#

A dedicated template administrator can disable a template. That sets it off and records its fingerprint as retired, so the same content can never be registered again under a new id. There is no re-enable.

Pausing a template#

Pausing stops new positions and new markets on a template without retiring it.

• Governance can pause a template until any time it chooses.
• A guardian can pause a template for at most 72 hours, may extend but may never shorten a pause, and cannot unpause. The guardian may be absent.

An ordinary template pause affects entry only. Permanent emergency retirement is different: it freezes all mutations, including settlement, claims, refunds and voids, before backing is evacuated.

Restricted templates and curators#

A template can be registered as restricted, meaning only a curator may create from it. The flag is set only at registration and can be cleared by governance exactly once, permanently; nothing can set it again. So a restricted template is the most restricted the venue will ever be, and every later change makes it freer. Governance seats and unseats curators individually. See Categories and curation.

Subjects#

The one template class that takes a subject — any listed token — requires the subject to be seated in the registry, which takes a public petition and a seven-day notice. See Token-listing petitions.

What governance cannot do#

• Raise a fee rate above 7%, or a tier discount above 40%: both ceilings are compile-time constants with no setter.
• Change where fees go: the fee router address is immutable.
• Add a resolver: the resolver allowlist is fixed at deployment, and the router's four lanes are immutable.
• Move locked RINO, or any USDG in escrow: no function exists for it.
• Overturn a resolved answer: the only override anywhere is a timelocked void, and it can only refund.

Governance-settable parameters#

Governance transfers in two steps — a nomination and an acceptance — so a mistyped address cannot take the role.