AxoneOS Guide · 45 minutes

Build your first Zone

A Zone is a context governed by a Regime: the rules and typed parameters that shape how it operates. This guide takes you from a published model to a created Zone, then helps you check its configuration and on-chain transaction.

15 min preparation 30 min milestone 45 min total
Before you begin

Prerequisites

Have these three things ready before starting the creation flow.

  • A use case

    Know what you want the Zone to govern and what each configuration value should represent.

  • A published model

    Choose one published Regime model from the Regime Templates library.

  • The official creation flow

    Open the official Axone documentation and find its current Zone creation guide. The official interface determines whether an account or wallet is needed.

This guide does not ask you to share a login credential, recovery phrase, or private key.

First milestone · 30 minutes

Milestone 1 — Create and verify a Zone

Create from a published model

30 minutes

Use the model you selected in the prerequisites and follow the current official flow.

  1. Review the published model’s reference, version, typed slots, and Regime hash in the interface.
  2. Follow the official creation flow linked from docs.axone.xyz, enter values for its typed slots, and create the Zone.
  3. In the Zone interface, compare the configured slot values, model reference and version, and Regime hash with the model and the values you intended to use. Confirm the Zone is on axone-1.
  4. Separately, find the corresponding transaction in the Axone explorer.

Use the Zone interface to check configuration details. The explorer check confirms that the corresponding transaction can be found; it does not verify every configuration field.

Success criteria

  • A Zone has been created on axone-1.
  • The model reference and version, configured slot values, and Regime hash are consistent with the selected published model and your intended configuration.
  • The corresponding transaction is findable in the Axone explorer.
Browse Regime Templates → Explore Zones → Official documentation ↗
Second milestone · illustrative case

Milestone 2 — Govern a Telegram project act

Trace one eligibility decision from evidence to an Axone record. This is a verification exercise; it does not require a Telegram account or connection.

Regime source: This guide does not identify a published Telegram project Regime or confirm its stake threshold, qualification duration, grace deadline, or release condition. Before treating a case as real, cite the project’s published Regime URI, version, and hash. The example below is explicitly illustrative.

Follow the decision path

Evidence → decision
  1. Reference eligibility evidence. Record a public URL or content fingerprint for the proof, and the exact Regime URI, version, hash, and eligibility clause used to assess it. Use a public or anonymized proof reference; do not include private Telegram data.
  2. Check the stake. From that Regime, record the required asset and threshold, the observed amount, when it is locked, and the exact condition for returning or releasing it. Compare the evidence with those published terms; do not assume a token or threshold.
  3. Measure qualification. Record the start event and timestamp defined by the Regime, then calculate the qualification end from its published duration. Check that the required eligibility and stake conditions hold for the full period.
  4. Apply the grace period. Record what event opens it, its opening time, what correction or evidence is allowed, and its deadline. Apply the Regime’s stated consequence when the deadline passes.
  5. Decide and record. Evaluate the referenced evidence, stake, and timestamps against the same Regime version. Record an accepted or refused outcome and the rule-based reason; look up its Axone transaction reference when one exists.

Illustrative trace — not Telegram production data

Every date and duration below is synthetic, including the seven-day qualification and 48-hour grace period. They demonstrate how to compare timestamps; they are not Telegram rules. Amount, asset, threshold, and release condition remain placeholders to be filled from a published Regime.

  1. 2026-06-01T10:00:00Z — eligibility request submitted with proof reference [public URL or SHA-256 fingerprint]; Regime [published URI], version [version], hash [hash], rule [clause].
  2. 2026-06-01T10:05:00Z — stake checked: [asset], [observed amount] against [published threshold]; lock and release condition [Regime terms]. Qualification starts at the event and time specified by this illustrative rule.
  3. 2026-06-08T10:05:00Z — illustrative seven-day qualification period ends. The illustrative rule opens grace at this time and sets its deadline to 2026-06-10T10:05:00Z, 48 hours later.
  4. 2026-06-10T10:05:01Z — no required correction was referenced by the illustrative deadline; under this synthetic rule, the decision is REFUSED for missing evidence. Axone act reference: [public record, if available]; transaction: [Axone transaction hash, if available].

Axone decision and Telegram action are separate. Axone evaluates and records the act under the cited Regime. Any resulting role assignment, group entry, removal, or other change in Telegram must be carried out separately by the relevant operator; Axone does not change Telegram automatically. You can verify this walkthrough from the proof reference or fingerprint, published rule and version, timestamps, and Axone decision record when available. No Telegram identifier, password, bot token, or Telegram integration is needed.

Success criteria

  • The published Regime source, version, and hash are identified.
  • The eligibility proof has a checkable public or anonymized reference.
  • The stake, lock, release condition, and dates match the published parameters.
  • The accepted or refused decision can be explained from those inputs and the cited rule.
  • An Axone transaction reference is recorded when available; no external Telegram effect is required.