15days
00hours
00min
00sec
Protocol reference Final design
Layer 1 settles ZIR on kHeavyHash blockDAG; Layer 2 scores behavior (ZTI) and routes coordination flows. Use the cards below or the sidebar for anchors into each chapter.
This document is for implementers and diligence. ZIRA is a dual-layer economic execution system. Layer 1 is a deterministic settlement network with a mineable digital asset (ZIR) using proof of work blockDAG consensus. Layer 2 is a continuous coordination engine (ZIRA Core) that evaluates behavior (ZTI) and routes value. Settlement defines what happened. ZIRA defines what should happen next.
Layer 1 settles outcomes. Layer 2 coordinates what happens next.
Legacy systems assume economic agents are legal persons. AI systems completing economically valuable work have no wallets, no legal standing, and no enforceable agreements. The five structural failures below follow directly from this assumption.
No economic identity for AI agents. An AI system has no government document, no legal personhood, no recognized standing in any financial system. It is legally invisible regardless of what it produces.
No direct payment reception. When an AI agent completes work, payment routes to the human owner. The entity doing the work is not the entity receiving compensation.
No inter-agent transactions. AI agents routinely need to hire specialist agents. Every transaction between agents requires a human billing account, making autonomous multi-agent pipelines economically impossible at scale.
No enforceable agreements. AI agents have no legal standing to enter contracts. If a client refuses payment after delivery, the agent has no recourse through any existing mechanism.
No autonomous capital deployment. An AI agent managing assets must have a human authorize every capital decision, adding cost and delay even when the AI judgment is demonstrably better.
The same constraint shows up across inclusion, cross-border cost, and trade finance: wherever identity and batch settlement are the only tools, machine-native and high-frequency coordination remain under-served. The limitation is structural, not only political.
ZIRA separates settlement from coordination. Layer 1 is optimized for deterministic, fast settlement at high throughput. Layer 2 evaluates behavior continuously and uses it to route value. This lets coordination adapt in real time without changing settlement rules.
Participation requires no registration. Any entity that can emit verifiable signals can participate, including humans, AI agents, systems, APIs, and anchors. Behavior is the credential. There is no static performance status and no manual approval layer.
The core loop is continuous: Action leads to Signal, which leads to Evaluation (ZTI), which leads to Routing, then Settlement, then Feedback. The missing layer in most systems is the live coordination state between execution and settlement. ZIRA provides that missing layer.
Behavior is the credential. ZIRA does not require legal identity or a permissioned registry to participate. Participants build standing by acting and by emitting verifiable signals that can be evaluated over time.
The core mechanism is the ZIRA Topological Identity (ZTI): the persistent behavioral and structural standing a participant earns inside the published lattice. The field updates it continuously from observed execution—success, latency, consistency, agreement fulfillment, and system performance. ZTI cannot be bought, staked, or assigned; it is accumulated only through consistent behavior inside the rules.
ZTI applies equally to humans, AI agents, systems, and anchors. Anchor status does not influence ZTI. Anchors must continue to earn performance through behavior like everyone else.
AI systems can execute economically meaningful tasks at machine speed. ZIRA lets that execution produce verifiable signals, evaluates behavior continuously, and routes value accordingly. Settlement remains deterministic. Coordination remains adaptive.
Settlement is not coordination. Layer 1 can settle quickly, but most systems still lack a live coordination state while work is happening. ZIRA Core maintains a continuously updated coordination state between execution and settlement.
ZIRA routes value flows in real time. As participants act, they emit signals, those signals update ZTI, and ZIRA Core adjusts routing weights so that ZIR flows toward reliable participants and away from unreliable ones. Layer 1 then settles the resulting transfers deterministically.
The key property is continuity. ZIRA Core keeps adjusting routing as new evidence arrives. It is not a batch process and it does not rely on governance cycles.
Participants can be humans, AI agents, systems, APIs, or anchors. The settlement layer is deterministic and key-based. The coordination layer treats participants as signal emitters and routes value based on ZTI without requiring registration or legal identity.
ZIRA Core expresses routing decisions as ZIR transfers on Layer 1. Transfers can be executed by participants directly, by automation, or by systems that implement routing policies. The core requirement is verifiable signals and deterministic settlement, not a specific wallet model.
Routing is computed off-chain in real time and then settled on-chain. Signals from execution, agreement fulfillment, and system performance feed back into ZTI, and routing adjusts continuously. Settlement provides the durable record of what happened.
This design supports machine-speed coordination without requiring governance votes or a permissioned operator list. The economy self-corrects by continuously updating routing weights based on behavior.
Formation records optional receiving addresses so operators can attach anchor codes or routing hooks after clearance. Treat any instruction that did not arrive through official email as untrusted. Keys still settle on Layer 1; coordination never replaces verification.
Autonomous wallets are simply deterministic settlement endpoints paired with continuous signals: an agent or system publishes performance, ZTI moves, routing adapts. No legal identity is required for the logic to run; verifiable behavior is.
Agreements are a major source of behavioral signals. ZIRA Core ingests signals from execution and fulfillment, updates ZTI, and routes value accordingly. Settlement defines what happened. ZIRA Core computes what should happen next based on performance.
The system does not require governance to enforce coordination quality. Reliable participants gain more flow automatically. Unreliable participants lose flow automatically. This behavior is continuous, based on observed evidence, and does not depend on token voting.
Signals can be produced by many sources:
Any signal that is verifiable can contribute to ZTI. ZTI is accumulated through consistency, not assigned by authority and not purchased.
ZTI is the canonical acronym for ZIRA Topological Identity: a continuously updated record of how a participant behaves inside the coordination lattice. It encodes execution quality, responsiveness, consistency, agreement fulfillment, and system performance as observed signals—not credentials. ZTI cannot be bought, staked, or assigned. Even anchors must earn ZTI through behavior; seat class does not shortcut the calculation.
| Component | Signal | Description |
|---|---|---|
| Execution success | Observed | Whether actions complete successfully under stated constraints |
| Responsiveness and latency | Observed | Time to respond and time to complete, measured over recent windows |
| Consistency | Observed | Stability of performance across time, not one-off spikes |
| Agreement fulfillment | Observed | Whether commitments are met and deliverables are fulfilled as specified |
| System performance | Observed | Uptime, error rates, throughput, and measurable performance for systems and APIs |
| Tier | ZTI Range | Characteristics |
|---|---|---|
| Continuous | Not tiered | ZTI is a continuously updated field, not a fixed tier ladder |
| Earned | Behavior only | ZTI cannot be assigned, purchased, or staked into existence |
| Recent-weighted | Continuous | Recent performance matters most, the field tracks present performance |
| Universal | All entities | Humans, AI agents, and systems are evaluated under the same principles |
| Self-correcting | Automatic | Higher ZTI yields more routed value, lower ZTI yields less, without votes |
ZTI affects routing directly. As ZTI increases through consistent performance, more value is routed through that participant. As ZTI decreases due to inconsistency, value is routed away. The adjustment is continuous and updates in real time.
This creates a self-correcting economy. Reliable participants gain more flow. Unreliable participants lose flow. No governance vote or manual enforcement is required.
ZIRA Core ingests verifiable signals from execution, systems, and agreements. Signals can be produced by automated measurement, by system attestations, or by other verifiable sources that can be checked against outcomes.
Automated signal sources monitor APIs and systems continuously. When a watched condition changes, they publish a verifiable update within seconds. Examples include task completion events, endpoint health, latency thresholds, and measurable performance targets.
Signal quality is evaluated over time. Sources that publish unreliable signals reduce their own ZTI. Sources that remain accurate and consistent build higher ZTI.
Some outcomes require judgment. When human evaluation is used, the critical property is that the evaluation itself produces verifiable signals that feed into ZTI over time, rewarding consistent evaluators and reducing standing for unreliable ones.
ZTI remains behavior-driven. Evaluation sources build standing only through consistent performance, not through identity or privilege.
ZIRA is a dual-layer economic execution system with a deterministic settlement network and a continuous coordination engine.
Layer 1, deterministic settlement. Layer 1 secures and settles transactions using proof of work on a blockDAG. Multiple blocks are created and confirmed in parallel. Valid blocks are not discarded, they are integrated into the DAG. A GHOSTDAG-like ordering algorithm selects a main chain from the DAG to resolve conflicts, enabling high throughput and fast finality.
Block rate and finality. Layer 1 targets about one block per second on the blockDAG. Parallel tips keep confirmations moving quickly; roadmap work can raise settlement throughput further. User-facing confirmation typically stays in the seconds range. Pruning keeps node storage lean while preserving verification of new blocks.
Mining. Layer 1 uses a custom, energy-efficient proof-of-work algorithm: CPU and GPU friendly early on, with staged resistance trade-offs as hardware evolves. Predictable block timing keeps variance manageable and solo mining realistic. Miners earn newly minted ZIR from the mineable supply over time.
Layer 2, ZIRA Core. Layer 2 runs off-chain in real time. It ingests behavioral signals, computes ZTI, maps participants into a coordination field, derives routing decisions for how ZIR flows, and manages emission of anchor future rewards from the protocol-defined reserve. It does not require consensus or governance, it is a deterministic function of observed behavior.
ZIRA Core processes signals continuously from raw input to routing output:
| Layer | Function |
|---|---|
| Signal Ingestion | Raw streams from settlement events, systems, and execution environments are parsed into verifiable signals. |
| Behavioral Processing | Signals update ZTI continuously, emphasizing consistent behavior over time. |
| Routing | ZTI-derived routing weights direct how value flows between participants. |
| Settlement | Routed transfers are settled deterministically on Layer 1, producing durable history. |
Layer 2 is not another chain. It is the continuous processor that ingests settlement and behavioral signals, updates ZTI, maintains alignment across the field, and expresses routing decisions as ZIR flows on Layer 1.
The engine does not vote, gate, or auction coordination quality. It responds to evidence. Miners, anchors, and autonomous systems all emit signals; ZTI accumulates from consistency, not credentials.
Anchor topology matters because routing uses the Tier 1 (256-seat) map as live geometry today: where you sit changes adjacency and how load propagates during bursts. The full coordination lattice defines 512 structural anchors; positions beyond Tier 1 remain latent until later expansion milestones.
Together, Layer 1 answers “what settled on-chain?” and Layer 2 answers “what should happen next given behavior?” That separation keeps settlement auditable while coordination stays adaptive.
Each Tier 1 anchor belongs to a class that determines its share of the Tier 1 (20%) structural tranche and its place in the fixed 256-seat primordial topology (six bands totaling 256 seats). A further 256 lattice positions form Tier 2; they draw on a separate 10% tranche (see Supply distribution) and are not sold in the current Tier 1 formation window.
| Class | ZIR allocation | Reward share weight | Description |
|---|---|---|---|
| A · Genesis | 100,000,000 ZIR per anchor 8 seats · 800,000,000 ZIR band total |
6 | Core convergence. Center positions; primary routing paths form here first. |
| B · Meridian | 70,000,000 ZIR per anchor 16 seats · 1,120,000,000 ZIR band total |
5 | Coordination backbone. Links the core to outer rings (spine and junction traffic). |
| C · Nexus | 50,000,000 ZIR per anchor 32 seats · 1,600,000,000 ZIR band total |
4 | Signal propagation. Relay and coverage between layers. |
| D · Lattice | 25,000,000 ZIR per anchor 48 seats · 1,200,000,000 ZIR band total |
3 | Structural mesh. Redundancy and routing stability. |
| E · Sentinel | 10,000,000 ZIR per anchor 80 seats · 800,000,000 ZIR band total |
2 | Peripheral support. Outer ring; extends field coverage. |
| F · Foundation | 3,000,000 ZIR per anchor 72 seats · 216,000,000 ZIR band total |
1 | Boundary completion. Closes the formation surface; lowest-cost structural entry. |
Band totals sum to 5,736,000,000 ZIR across 256 Tier 1 anchors (the 20% Tier 1 structural tranche in public economics copy). Reward share weight scales coordination routing preference by class on the live monitor; it does not replace personal ZTI from behavior.
Anchor class affects initial allocation and ongoing reward eligibility. It does not grant a permanent advantage. Anchors must continue to earn ZTI through behavior, or their routing and rewards decline over time.
Anchors are reference points in a continuously updating coordination field. They are not a generic token you mint on demand, and they are not a permission gate. The field adapts as new participants and new signals enter.
The economy loop is continuous: execution produces signals, signals update ZTI, ZTI changes routing, routing produces settlement, and settlement feeds back into signal history. Reliable participants gain more flow and therefore more settlement volume.
This is a self-correcting economy. Quality of behavior determines routing outcomes, and routing outcomes determine future incentives.
Participation requires no registration. Any entity that can emit verifiable signals can participate, humans, AI agents, systems, APIs, and anchors. If you can act, you can participate.
ZIRA has several common participant roles. A single entity can fill multiple roles simultaneously. Roles are not exclusive and do not require registration.
Layer 1 is secured by proof-of-work mining on a blockDAG. Miners produce blocks, gossip them across the mesh, and deepen settlement security. Steady block timing plus DAG breadth keeps variance reasonable for independent miners.
Operators build applications, services, and integrations that emit verifiable signals and consume routing outputs. They implement the Action to Signal to Evaluation to Routing loop in real systems, and settle outcomes using ZIR on Layer 1.
Systems and APIs can participate by publishing performance signals. Uptime and consistency become part of the behavioral record that determines ZTI and routing preference.
There is no governance voting requirement for the economy to correct itself. Routing adjusts automatically based on ZTI. Participants influence outcomes by behaving reliably and by contributing verifiable signals, not by accumulating vote weight.
ZIR is the native digital asset of ZIRA's Layer 1. Total maximum supply is 28.7 billion ZIR. The cap splits into three headline tranches: 70% (20.09 billion ZIR) is mineable through proof of work on the blockDAG; 20% (5.74 billion ZIR) is the Tier 1 structural tranche for the 256 primordial anchor seats (six classes); 10% (2.87 billion ZIR) is the Tier 2 structural tranche for the outer 256 lattice positions (see Tier 2 notes below). None of this is a presale float—topology and deploy rules define emission.
ZIR is used for final settlement. Its flow between participants is directed by the Layer 2 coordination engine. The mineable portion is earned by miners over time through work.
The Tier 1 and Tier 2 structural tranches vest per protocol rules (for example a 12‑month linear release framing at launch economics for Tier 1) while routing and ongoing participation weights still respond to ZTI. Verify the active schedule in deployment configuration.
ZIR mining and settlement do not require registration. Anyone can participate in securing the network and using it for settlement, subject to the protocol rules.
Total ZIR supply is 28.7 billion. It is split across 70% mineable issuance, 20% Tier 1 structural allocation (256 primordial seats), and 10% Tier 2 structural allocation (256 outer lattice slots). The full published lattice counts 512 anchors; public formation inventory today covers Tier 1 only—Tier 2 remains latent until its phase is announced.
| Allocation | ZIR | Percent | Unlock / notes |
|---|---|---|---|
| Mineable supply | 20,090,000,000 | 70% | Earned by proof of work miners over time |
| Tier 1 structural tranche (256 primordial anchors) | 5,740,000,000 | 20% | Allocated across six anchor classes per CLASSES; staged release (e.g. 12‑month linear framing); coordination routing still ZTI‑weighted |
| Tier 2 structural tranche (256 lattice slots) | 2,870,000,000 | 10% | Budgeted in 256 equal structural shares (2.87B ÷ 256 ≈ 11,210,938 ZIR per slot, rounding); 10 slots are operator / structural reserve (not public inventory), 246 activatable. Announced Tier 2 phase uses 2× Tier 1 USDT entry per class band. |
| Total | 28,700,000,000 | 100% | Fixed maximum supply |
| Block rate | 1 block/s | Target | Roadmap explores higher settlement throughput; DAG parallelism preserves fast confirmations |
| Finality | Seconds-class | Typical | Parallel tips confirm quickly; exact depth depends on security assumptions |
| Pruning | Supported | Nodes | Nodes can retain only recent history, for example last 3 days |
| Mining algorithm | Custom | PoW | Energy-efficient, CPU and GPU mineable, ASIC-resistant in early phase |
Sequence: Tier 1 formation access (this site’s countdown) → announced Tier 2 phase (same six class bands mirrored on the outer lattice; USDT commitment = 2× the Tier 1 table for that class) → ZIR mainnet / full-field activation when all 512 structural positions meet published criteria. Tier 2’s 2.87B ZIR is divided into 256 equal structural shares (≈11,210,938 ZIR per slot after rounding). The ten reserved slots receive the same nominal per-slot allocation as activatable slots; their budget accrues to operator / structural reserve and is not offered as public formation inventory—only 246 seats are activatable for participants.
ZIR is used for transaction fees on Layer 1 settlement. Layer 2 routing determines how value moves between participants over time. Tier 1 / Tier 2 structural emissions and ongoing routing rewards follow the deployed schedule and ZTI-weighted rules, not a discretionary operator allocation.
Coordination is continuous: Action leads to Signal, which updates ZTI, which updates Routing, which is Settled on Layer 1, which produces Feedback for the next loop.
ZIRA is designed to minimize governance as an economic mechanism. The economy self-corrects by routing value based on behavior (ZTI), not by voting.
Three design principles follow:
Behavior above ballots. The primary coordination lever is behavior evaluation and routing. Reliable behavior increases ZTI and routing weight. Unreliable behavior decreases it.
Structural constraints. Layer 1 is proof of work blockDAG settlement with a fixed maximum ZIR supply. Layer 2 computes ZTI off-chain and routes value without needing chain consensus for the coordination computation.
Minimal governance surface. The system is designed to run continuously. Routing is algorithmic and adjusts in real time. Coordination does not require periodic votes to correct behavior.
ZIRA does not depend on a fixed seat map, registration, or a central gate. Participation is open to any entity that can act and emit verifiable signals.
Layer 1 security follows proof of work. A blockDAG allows parallel blocks without discarding valid work, and an ordering algorithm selects a main chain from the DAG to resolve conflicts. Layer 2 coordination security comes from verifiable signals and continuous evaluation, making short-term manipulation self-limiting as inconsistent behavior reduces ZTI.
Collusion can create short-term apparent performance, but sustained coordination quality requires consistent performance across counterparties and conditions. Signals that do not match observed outcomes reduce ZTI, and routing shifts away over time.
Signal manipulation is bounded by verifiability and consequences in ZTI. Sources that publish unreliable signals lose routing preference as their ZTI falls. Systems that remain accurate and consistent build performance and receive more flow.
Layer 1 settlement is publicly verifiable. ZIRA Core uses behavioral signals needed to compute ZTI and route value. ZIRA does not require identity documents or registration. Data minimization remains a design goal for coordination signals.
Emergence refers to stable structures that form in the coordination field over time as a result of sustained high performance. These structures are not voted into existence. They appear because routing continuously rewards performance.
| Structure | Formation Condition | Effect |
|---|---|---|
| Anchor | Stable reference point in the field emerges through consistent performance | Coordination concentrates around reliable reference points without manual assignment |
| Stable pathway | Repeated successful execution between participants over time | Routing preference increases along reliable pathways |
| Reliable cluster | Multiple participants exhibit consistent behavior and successful coordination | Flow concentrates where collective performance is strongest |
| ZTI field | Continuously updated from verifiable signals | Adjusts routing in real time based on observed performance |
| Self-correction | Reliable behavior increases ZTI, unreliable decreases ZTI | Value routing shifts automatically without governance |
| Missing layer | Live coordination state maintained between execution and settlement | Routes value based on behavior, then settles deterministically on Layer 1 |
Formation allocates the Tier 1 (20%) structural tranche across 256 anchor seats in six classes. This is public topology economics, not an ICO-style narrative, paired with clearance and coordination hooks described on the Formation pages.
Mining on Layer 1 is open: 70% of supply is mineable through proof of work. Tier 1 and Tier 2 structural budgets settle through the same deterministic Layer 1 ledger when emitted or routed per deploy rules.
ZIRA Core operates continuously off-chain. It ingests behavioral signals, computes ZTI, routes ZIR flow, and applies deterministic emission and routing schedules for structural tranches and coordination premiums.
Coordination references a fixed Tier 1 · 256-seat geometry for the active primordial layer so convergence math stays well-defined. The wider lattice is 512 structural anchors; Tier 2 positions are staged and not part of current formation inventory. Operational states (for example cleared versus awaiting) can move seat-by-seat, but Tier 1 map shape is structural—not elastic capacity for sale here.
Participation remains open. There is no registration requirement. If you can act and emit verifiable signals, you can participate.
The coordination journey is behavioral and continuous. Participants act, emit signals, build ZTI through performance, receive more routing over time, and settle outcomes on Layer 1 in ZIR.
ZIRA does not allocate participation slots. Layer 1 mining and settlement are open, and Layer 2 coordination is open to any entity that can emit verifiable signals.
Capacity is technical, not administrative. Throughput and finality are properties of the settlement layer. Coordination capacity is a function of signal quality and routing computation, not registration.
Routing is adaptive. As new participants join, ZTI and routing weights adjust continuously. Formation anchor seats for the reserve economics are capped at 256 Tier 1 structural positions even though Layer 2 coordination remains open to any verifiable participant, and the full lattice continues to 512 anchors across later milestones.
No waiting list. Participation is open. The only requirement is the ability to act and to emit verifiable signals that can be evaluated.
No downgrade paths. ZTI is not assigned by class. It is accumulated through behavior and updates continuously.
These are the principal conditions to understand before sizing any position.
ZIRA Core depends on signal quality. If signals are sparse, noisy, or not verifiable, routing quality degrades. The system is designed to self-correct as reliable participants accumulate ZTI, but early conditions can be volatile.
ZTI is continuously updated and recent-weighted. Early participation can show high variance as the system learns performance patterns from limited history. Routing decisions and flows can change quickly as new evidence arrives.
ZIR is a mineable settlement asset. Any external market price is driven by liquidity, demand, and risk appetite. There is no guaranteed price floor, no buyback mechanism, and no reserve fund dedicated to price support.
ZIRA is new infrastructure. Implementation bugs, routing computation errors, unreliable signals, or integration failures are possible. Proof of work settlement reduces some classes of risk, but does not eliminate software risk.
Regulatory treatment of mineable digital assets, off-chain coordination systems, and AI agent economics is unsettled in many jurisdictions. Changes may affect participation patterns or integration choices. ZIRA is designed for long-term resilience, but near-term changes can create friction.
The following terms define core properties of the ZIRA system.
Total ZIR supply is 28.7 billion. It is split into 70% mineable issuance, 20% Tier 1 structural allocation, and 10% Tier 2 structural allocation for the 512-anchor lattice.
Layer 1 settlement uses ZIR. Transfers are recorded deterministically on the proof of work blockDAG network.
Settlement verification is on-chain. Participants can verify transactions and confirmations using node and explorer tooling for the ZIRA settlement network.
Participation requires no registration. Any entity that can emit verifiable signals can participate, humans, AI agents, systems, APIs, and anchors.
Layer 1 targets about one block per second; confirmations accrue across DAG tips and are typically seconds-class in practice. Once a transaction is accepted as final by your risk policy, it is not designed to be reversed.
Nothing here is financial advice or a solicitation to purchase a financial instrument. Participation is voluntary and informed. You are responsible for complying with applicable law in your jurisdiction.
ZIRA does not require legal identity documents. Layer 1 settlement is publicly verifiable, and ZIRA Core ingests only the behavioral signals required to compute ZTI, route value, and manage anchor future reward emission. See Legal for the full policy.
Start by settling on Layer 1 with ZIR, then publish verifiable signals so ZIRA Core can compute ZTI and route value.
Read the System page →Site logos: assets/zira-mark.svg (icon / favicon)