15days
00hours
00min
00sec
Questions
Straight answers on protocol behavior, formation, and operations. Formation runs on one published snapshot (same monitor for every visitor). Deep specs sit in Reference; live tables and maps are on Formation. Jump to Home · Mining or request evaluation.
Layer 1 targets ~1 block/s on the DAG, the fixed 80/20 split, and how PoW relates to ZTI.
ZIRA Layer 1 uses kHeavyHash, the same family as Kaspa, on a separate network with its own supply rules and economics. If you already mine Kaspa-class hardware, operational patterns carry over; chain IDs and binaries are distinct.
Layer 1 aims for about one block per second on the blockDAG. Because tips run in parallel, confirmations usually land in the seconds range; exact depth depends on how many blocks you treat as final. Pruning keeps nodes lean while preserving verification of new work.
70% (20.09 billion ZIR) is mineable through proof of work over time. 20% (5.74 billion ZIR) is the Tier 1 structural tranche across 256 primordial anchor seats (six classes). 10% (2.87 billion ZIR) is the Tier 2 structural tranche for the outer 256 lattice slots (10 reserved, 246 activatable). See Reference · Supply distribution.
kHeavyHash is built to be memory-hard enough for broad CPU/GPU participation while the network establishes its floor. Early-phase ASIC resistance is a distribution goal, not a permanent promise against specialized hardware.
Yes indirectly. Layer 1 settles ZIR; Layer 2 continuously scores behavior (ZTI) and routes flows. Consistent mining signals can contribute to standing alongside non-mining participation. Mining earns issuance; routing responds to observed behavior.
Anchor clearance, Tier 1 / Tier 2 structural schedules, and optional wallet lines on requests.
A formation anchor is one of 256 Tier 1 structural seats in the primordial topology (six classes from core to closure). The wider published lattice defines 512 anchors; Tier 2 positions draw on a separate 10% tranche and are not in this formation inventory. Clearing evaluation maps your participation onto Tier 1 geometry; economics follow class rules from the Tier 1 (20%) tranche.
No. The protocol denominates 20% of supply as the Tier 1 structural tranche and 10% as the Tier 2 structural tranche, distributed across lattice seats per published economics—distinct from the 70% mineable pool. Language matters: formation encodes topology and clearance, not an ICO-style allocation narrative.
The Tier 1 tranche follows the schedule in Reference · Supply distribution: liquidity is staged with a 12‑month linear release framing at public launch economics (verify current parameters on deploy). Tier 2 follows its own announced schedule.
An optional receiving address lets operations attach position codes or routing hooks after clearance. It is not a substitute for verification. Commitment instructions still arrive only through official email; never send funds to ad‑hoc addresses.
ZIRA treats participants as signal emitters (humans, organizations, or automation) that settle on deterministic Layer 1 keys. Coordination does not require legal identity; behavior traceable to keys feeds ZTI and routing. See Reference · Autonomous wallets.
Layer 1 vs Layer 2, ZTI standing, formation snapshots, and how they connect to settlement.
Legacy financial systems were built assuming all economic agents are human beings with legal identities. When AI systems and autonomous agents operate independently, that assumption breaks. There is no wallet for an AI agent, no legal standing for autonomous entities, no way to settle value between agents directly. ZIRA solves this by replacing identity-based systems with performance-based systems. Standing follows from demonstrated behavior, not credentials.
Yes. ZIRA has two layers. Layer 1 is a proof of work blockDAG running kHeavyHash, the same algorithm as Kaspa, on its own separate network. Layer 2 is the coordination engine that runs off-chain in real time. L1 handles settlement. L2 handles coordination intelligence. Both layers are necessary.
Everything under live coordination surface reads one published ledger. The coordination index and economics tables (ZTI, ZIR, reward weight), seat-by-seat lists when you pick a class tab, and the topology canvas all reflect that snapshot. Figures refresh together on a short cadence. They illustrate coordination load and allocation in the field, not chain confirmations.
Traditional finance routes value through accounts held by legal persons. ZIRA routes value based on behavioral performance. A person, organization, or AI agent builds standing by consistently showing up inside published rules. That standing, not legal status, determines routing priority and eligibility. Value flows continuously with work, not after it in batch settlements.
ZTI stands for ZIRA Topological Identity: a continuously updated behavioral record derived from observed execution—success, latency, consistency, agreement fulfillment, and system performance. It is earned through performance, not purchased, delegated, or transferred. Any intelligent system, human or AI, builds ZTI the same way: by performing consistently inside the rules.
ZIR is the native asset of ZIRA Layer 1. Total maximum supply is 28.7 billion ZIR, fixed at genesis. 70% (20.09B) is mineable through kHeavyHash proof of work. 20% (5.74B) is the Tier 1 structural tranche across 256 primordial seats (six classes). 10% (2.87B) is the Tier 2 structural tranche for the outer 256 slots. Coordination routing tracks ZTI on the active layer. ZIR settles on L1 and is the unit that L2 routes between participants.
Switzerland. The system has been built and validated. The public countdown marks the end of Tier 1 formation access, not “ZIR mainnet is complete” or all 512 anchors live. For formation correspondence use formation@zira.network.
An anchor is a structural / topological position—not an NFT or plot. Tier 1 maps 256 primordial seats with fixed geometry: 8 Genesis, 16 Meridian, 32 Nexus, 48 Lattice, 80 Sentinel, and 72 Foundation. The coordination lattice counts 512 anchors in total; the remaining Tier 2 shell is latent and not sold in this window. After staged activation, anchors function as routing nodes; traffic follows published topology rules.
ZIRA measures what you do, not what you have. Behavioral performance means your standing in the coordination engine is derived from observed execution and outcomes: success rate, latency, consistency, agreement fulfillment, and system performance. No amount of ZIR can purchase higher ZTI. No one can delegate their standing. It accumulates only through performance, and it decays when performance drops.
Tier 1 seat geometry, the access window, and what happens between request and staged activation.
The coordination field is defined as 512 structural anchors so later expansion has a published home. Tier 1 is the primordial 256-seat band funded by the 20% Tier 1 tranche. Tier 2 is the outer 256-seat band funded by the 10% Tier 2 tranche (10 operator-reserved slots, 246 activatable; ZIR budgeted as tranche ÷ 256 per structural slot). Tier 2 is latent on this site until its phase is announced; USDT entry will be 2× Tier 1 class price.
No. The site countdown marks the end of controlled Tier 1 formation access (the window for new requests under the published rules), not “every seat cleared” and not full-field activation. ZIR mainnet and bringing all 512 structural anchors online are separate, staged milestones. Explorer and Wallet may unlock on their own configured instant—see Reference and deployment config.
They are structural roles in the topology, not pricing tiers. Genesis anchors sit at the convergence core. Meridian carries traffic between core and outer rings. Nexus provides signal coverage across the middle. Lattice is the structural mesh that absorbs routing failures. Sentinel forms the perimeter. Foundation completes the surface. Earlier positions carry higher structural alignment weight by topology. That is geometry, not pricing.
Tier 1 clearing still depends on demand and manual evaluation throughput: classes progress as requests are reviewed, commitments complete, and anchors publish to the snapshot. The public access clock can reach zero before every seat is filled—after that, follow current published rules for late requests. Full lattice work continues on protocol milestones independent of the countdown display.
Positions are not claimed. They are validated, then committed. If your evaluation clears and a commitment window opens, securing follows the published rules and capacity in that class. If a class closes before you commit, ZIRA will contact you with options, including moving to an available lower class. Act within the stated commitment window once you receive instructions.
The smallest available is Class F (Foundation) at 100 USDT per allocation, yielding 100,000 ZIR. The largest published is Class A (Genesis) at 5,000 USDT per allocation, yielding 5,000,000 ZIR. You may request multiple allocations within a class or mix classes. Constraints and schedules are documented in Reference.
USDT only, via TRC-20 (Tron) or ERC-20 (Ethereum). Instructions and the receiving address for your transfer arrive by email from the ZIRA team after your evaluation clears. Do not anchor funds until you have received those instructions through an official channel. If you did not receive it from us directly, treat it as fraudulent.
Issuance pool, Tier 1 / Tier 2 structural tranches, routing premiums, and separate reward clocks.
Two separate clocks. Your class ZIR allocation is a fixed, one-time amount tied to your seat at activation. Coordination rewards are ongoing ZIR earned from participation after Field Genesis, based on routing throughput, ZTI multipliers, convergence bonds, cluster bonuses, and epoch distributions. Earlier cycles are naturally volatile while the system finds its shape.
Your structural allocation follows the vesting rules for your class once the relevant settlement milestone is reached—see Reference. That schedule is not identical to the Tier 1 formation countdown (which ends primordial access). Earned coordination rewards accrue separately from operational participation.
The Foundation Phase names a vesting profile for certain formation-era participants (cliff + schedule). Figures and how they relate to the Tier 1 structural tranche are documented in Reference; there is no governance mint beyond the fixed 28.7B cap.
Total maximum supply is 28.7 billion ZIR, fixed at genesis. Economics split into 70% mineable issuance, 20% Tier 1 structural tranche, and 10% Tier 2 structural tranche; see Reference · Supply distribution. There is no governance mint mechanism.
The 10% Tier 2 tranche (2.87B ZIR) is budgeted in 256 equal structural shares—each slot’s nominal allocation is 2.87B ÷ 256 ≈ 11,210,938 ZIR (rounding as deployed). The ten reserved slots receive the same per-slot allocation as any other structural position; their economics accrue to operator / structural reserve and are not offered as public inventory. Participants therefore pursue 246 activatable seats; USDT entry in Tier 2 is 2× the Tier 1 class table.
Who can operate on the field, post-activation anchors, and Intelligent Agreements.
Yes. ZIRA is designed for human and machine intelligence equally. An autonomous AI system can earn behavioral standing, execute under conditions, and transact through autonomous wallets. No legal identity required. No human authorization needed for every action. The field observes behavior and routes accordingly. An AI agent with consistently strong execution performance has higher standing than an inconsistent human participant.
As Tier 1 anchors and the wider lattice reach their staged milestones, routing turns on progressively: signals enter the coordination engine, ZTI updates continuously, and ZIR flows follow published topology pressure. Early cycles are noisy while load patterns stabilize; steady-state routing emerges over time—not as a single marketing flip at the countdown.
Your anchor is a routing node. After activation, it reads coordination signals, computes alignment, and routes ZIR. Operation is continuous. ZTI updates from your uptime, signal quality, and agreement fulfillment. Higher ZTI at your structural position routes more traffic automatically. Bonus mechanisms like convergence bonds and harmonic clusters activate when your anchor aligns with neighbors. The system is designed to be self-reinforcing for reliable operators.
Your anchor position is tied to your identity or entity. The seat itself cannot be transferred or sold. Your ZIR allocation is tied to that position. You may trade ZIR as a standalone asset once it becomes exchangeable, but the anchor position is structural and permanent. This ensures accountability and prevents speculation on coordination roles.
Smart contracts execute when conditions are met, but they have no read on whether counterparties are reliable right now. Intelligent Agreements incorporate ZIRA's live ZTI. Execution adapts based on continuous behavioral verification of participants. If a counterparty's ZTI drops due to misalignment, the agreement can adjust terms or escalate to dispute resolution. This keeps agreements responsive to reality, not locked to static conditions.
Oracles, capacity model, data boundaries, and dispute handling.
Oracles are both automated and human. They publish signals about outcomes, performance, and alignment. Those signals are weighted by the oracle's own ZTI. An oracle with high ZTI has more influence on the coordination field. If an oracle consistently publishes inaccurate information, its ZTI decays and its future signals carry less weight. The field detects divergence patterns when multiple independent participants report inconsistency.
Tier 1’s 256-seat geometry is fixed for the primordial layer: you do not add seats to Tier 1 mid-flight. Capacity scales by routing more coordination traffic through the same structure—denser signal, higher throughput per anchor, better infrastructure at each node. The broader 512-anchor lattice completes later; until then, Tier 2 remains latent rather than an elastic “buy more seats” market.
ZIRA reads published signals only. It does not require access to raw data, private keys, or internal system details. Each participant publishes behavioral signals on their terms. ZIRA interprets those signals and returns coordination state. No system has privileged access to another's data. This design keeps every participant sovereign while creating shared coordination visibility.
Disputes resolve against the oracle record and published signals, not in courts or arbitration. If two parties disagree on an outcome, the oracle record shows what was observed by the system. Intelligent Agreements can escalate to a human oracle panel when automated resolution is not sufficient. The field's behavioral account creates an immutable coordination history that applies equally to all participants, human or AI.
For formation requests or operations questions, use official channels. Legal pages list counsel contacts.
Contact: Use the Formation page request flow for formation questions.