A Zone is a context governed by a Regime: the rules and typed parameters that shape how it operates. This checklist covers 50 minutes of active work for a first Zone with a Telegram use case. Time for funding, external authorization, or any qualification period required by a Regime is not included.
Start from a connected standard account that has no Zone yet. The 50-minute estimate assumes the required source material is ready; it does not guarantee that the official creation flow is available or that external prerequisites are granted.
Use a connected standard account with no existing Zone. The official product must provide an account-scoped way to confirm that starting state.
Define the act the Zone should govern and prepare a public URL or anonymized evidence reference. Do not include private Telegram data.
Identify its published URI or reference, version, hash, and typed slots. The Regime Templates library can help find a model, but does not make it Telegram-specific.
Confirm in the current official flow whether the account, signing wallet, network, fees, funding, or another authorization are required. An empty account cannot be assumed to be able to submit a transaction.
The linked official documentation is a technical reference and currently does not document a standard-account Zone-creation procedure. Do not infer interface controls, wallet requirements, fees, or available funding from this guide. If the current official product does not document the required flow, stop before signing and record what is missing.
Each checkbox is local to this page and is not saved. Complete a step only when its check passes; if a documented requirement or permission is missing, stop at that step.
Expected result: A connected standard account with no existing Zone is ready for the first creation.
Check: In the current official product, inspect the account-scoped Zone list and confirm it contains no Zone. If no such view is documented or available, record that the starting state cannot be verified and stop.
Expected result: One model is selected with its published URI or reference, version, hash, and typed slots recorded.
Check: Compare all four items with the model’s publication source. Regime Templates is a discovery page; do not describe a generic model as Telegram-specific unless its source does.
Expected result: Each proposed Telegram parameter has a cited rule in the selected source, and the public or anonymized evidence reference is kept with it.
Check: Match every value to the same model URI, version, hash, and rule. This repository does not publish a Telegram Regime or Telegram-specific stake threshold, qualification duration, grace period, or release condition. Do not invent these values or reuse the synthetic dates formerly shown here; if the source has no Telegram rule, record that limitation.
Expected result: The Zone-creation transaction is submitted using the signing method and network confirmed by the current official flow.
Check: Before signing, verify the transaction details, network, fee, and any required funds or external authorization against current official instructions. If those instructions do not document creation for a standard account, or funding/authorization is unavailable, do not sign; note the blocker. These waits are outside the estimate.
Expected result: The created Zone shows the selected model, its hash, the intended typed-slot values, and the confirmed network.
Check: Compare the Zone details shown by the official product field by field with the publication source and submitted values; confirm the network identifier there. Do not mark fields verified when the interface does not expose them.
Expected result: The Zone-creation transaction is findable in the explorer; any available Axone decision is explained from the same published rule and evidence.
Check: Search the exact transaction hash in the Axone explorer. For a decision record, compare its cited rule, model version, and evidence reference; if no Telegram rule supports a decision, state that no Telegram-specific conclusion can be drawn. Finding a transaction alone does not verify every configuration field.