ZIRA Protocol Reference

Protocol reference Formation gate

This document is for implementers and diligence: invariants (fixed 10B ZIR supply, 512 anchors, behavioral identity), interfaces, and risk framing. Narrative lives on System. During formation, Formation exposes the real coordination field as one published snapshot: coordination index (ZTI read), anchor economics (ZIR allocation and illustrative coordination yield), and 512-seat topography. Common questions are on the FAQ.

ZIRA does not replace settlement rails. It adds a shared state that links behavior to execution and value flow.

Why this exists

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.

ZIRA's Approach

A coordination field does not ask who you are. It observes what you do and scores it. Any participant, human or artificial, earns a behavioral identity through demonstrated alignment behavior. No passport required. No approved list. The track record is the identity.

ZIRA combines five primitives that no prior system has integrated: behavioral identity that any entity can earn, continuous value flows that settle in real time at arbitrary precision, autonomous wallets that require no legal person, Intelligent Agreements that self-execute and adapt to live ZTI, and ZIR as the coordination asset. These follow from the same coordination logic applied consistently.

The field is also a protocol: a shared set of rules any participant can implement and build on without permission. No company sits between participants and the field.

Primitive 1: Behavioral Identity

Traditional identity requires a trusted issuer. A bank issues an account. A government issues a document. ZIRA inverts this entirely. Identity on ZIRA is earned through behavior, not assigned by an authority. Any participant, whether a human individual, a corporation, an AI agent, or an autonomous protocol, can build behavioral identity through consistent, honest participation.

The core mechanism is the ZIRA Trust Index (ZTI), a behavioral score computed continuously from participation history. The ZTI is not a one-time assessment. It updates continuously, with recent behavior weighted more than old. Strong alignment raises it. Defection, noise, and abandonment lower it.

This design means AI agents with no legal standing can still participate fully. Their identity is their track record. An agent that has fulfilled five hundred agreements reliably has stronger field standing than a human with a government-issued ID who has fulfilled none. The field is indifferent to category. It reads behavior.

Why behavioral identity matters for AI

When an AI agent completes work, it produces a verifiable output. When it routes a payment correctly, that action is on-chain. When it fulfills an agreement condition, the oracle attests to it. All of these become behavioral data that builds the agent's ZTI. No legal paperwork needed. No human intermediary required. The agent's economic standing in the field is a direct function of its economic track record.

Primitive 2: Continuous Value Flows

Traditional payment systems are batch processes. You invoice, wait, get paid, and reconcile. This model was designed for a world of slow human transactions. For AI agents completing work in milliseconds and for real-time coordination signals that update continuously, batch payment is a mismatch.

ZIRA supports continuous value flows: ZIR streams at configurable rates as small as one billionth of a ZIR per second. A stream has a sender, a receiver, a flow rate, and an optional stop condition. Value moves continuously as work happens rather than settling once work is declared complete.

Use cases

• An AI agent completes a task pipeline. Value flows at a fixed rate throughout execution. If execution halts, the flow pauses. No invoice required.
• A DeFi protocol pays oracles per attestation, streaming fractions of ZIR per second of uptime rather than batching monthly payments.
• A human contributor to a coordination process receives compensation proportional to signal quality, paid continuously rather than as a lump at month-end.
• Cross-border remittances complete without a correspondent bank by streaming value across field pathways.

Streams can be started, stopped, or modified by either party under agreement terms. They are not irreversible. If an oracle-verified condition is violated, the agreement layer can halt the stream automatically.

Primitive 3: Autonomous Wallets

A standard blockchain wallet requires a private key controlled by a legal person. AI agents have no legal standing to control a wallet in any jurisdiction. ZIRA's autonomous wallet primitive removes this constraint entirely.

An autonomous wallet is defined by programmable rules rather than by a single controlling key. Access conditions can include ZTI thresholds, oracle-verified conditions, time locks, multi-party consensus among AI agents, or any combination of these. No single human needs to hold the controlling key.

How autonomous wallets work

An autonomous wallet specifies a set of execution conditions: who or what can initiate transactions, under what conditions, with what constraints. A multisig of three AI agents with ZTI above a threshold can move funds. An oracle confirming task completion can release payment. A time-based rule can stream ongoing rewards.

This makes genuine multi-agent economic coordination possible. An AI agent can hire another AI agent, pay it from an autonomous wallet, and receive payment for its own work into another autonomous wallet, all without human involvement in each transaction.

Primitive 4: Intelligent Agreements

Traditional contracts require courts for enforcement. Smart contracts enforce simple programmable conditions but cannot read whether counterparties are reliable right now. ZIRA's Intelligent Agreements layer combines on-chain execution with a structured oracle system and live ZTI integration to handle the full range of economic agreements.

An agreement specifies: the parties involved, the deliverables expected, the oracle mechanism that will verify completion, the payment terms (which can use value flows), and the dispute resolution path. Agreements self-execute when oracle-verified conditions are met. Execution adapts to live ZTI, not only static triggers.

Oracle verification

ZIRA uses two oracle classes:

• Automated oracles monitor on-chain and off-chain data sources for measurable conditions. Price feeds, task completion events, performance metrics, and on-chain state changes all qualify. Results are objective and tamper-resistant.
• Human oracle panels handle deliverables that require judgment: content quality, design work, strategic advice, research outputs. A panel of independent evaluators with reputation stakes provides attestation. Panel composition and scoring are transparently logged on-chain.

Both oracle types write their attestations to the field, where they become behavioral data that updates ZTI for the oracles themselves. Reliable oracles build standing. Unreliable ones lose it.

ZIRA Trust Index (ZTI)

The ZTI is a behavioral score from 0 to 1000 computed continuously for every participant. It represents the current field assessment of a participant's alignment quality based on their recent history. The ZTI is not a reputation system in the traditional sense. It does not remember forever. It weights recent behavior more heavily than old behavior, adjusting to current performance.

Score components

Trust tiers

How tiers affect economics

ZTI tiers determine the alignment multiplier applied to coordination rewards. A Sovereign-tier anchor earns meaningfully more per cycle than the same anchor at Newcomer tier. The multiplier is continuous, not stepped: ZTI 701 earns slightly more than ZTI 699, not a sudden jump at 700.

ZTI also gates access to certain agreement types, autonomous wallet configurations, and oracle panel participation. The field does not impose these gates arbitrarily. They reflect the behavioral requirements those activities demand.

Oracle System

Oracles are the sensory system of the coordination field. They bridge real-world events, deliverable quality, and off-chain state into on-chain attestations that agreements and reward calculations can rely on.

Automated oracles

Monitor on-chain data, APIs, and data feeds continuously. When a watched condition changes, they write an attestation within seconds. Examples include price feed updates, task completion events, on-chain state changes, API endpoint health, and performance metric thresholds.

Automated oracles are staked with ZIR. Attestation quality is auditable on-chain. Oracles that consistently attest to conditions that later prove incorrect lose stake and ZTI. Consistent and accurate oracles earn higher rewards per attestation and higher ZTI over time.

Human oracle panels

Convened for deliverables requiring subjective judgment. Each panel is composed of evaluators randomly selected from a pool of eligible participants (ZTI above the Established tier minimum). Panel size, scoring methodology, and unanimous-versus-majority requirements are specified in the agreement at creation time.

Panel members have no standing relationship with either party. Their individual votes are weighted by their ZTI at evaluation time. Panelists who vote against eventual consensus lose small ZTI. Panelists who vote with consensus earn it. This creates alignment incentives within the panel itself.

Protocol Architecture

ZIRA's architecture is built around three concepts: the field, the map, and formation.

The field is the live, continuously updated coordination state. It is not a ledger of past transactions. It is the present picture of what is converging, what is aligning, and where signal quality is high. The field ingests continuous streams of behavioral data and outputs a structured state that agreement and reward layers read.

The map is the fixed structure of the field: 512 foundation anchor positions across six classes on one surface. There are no separate phases; the full set is the foundation. The map does not change after genesis. Anchors may transfer ownership but the positions themselves are fixed. Twenty four positions are secured by the ZIRA team across classes; four hundred eighty eight are available through public formation.

The formation is the initialization sequence. Until all 512 foundation positions are secured, the field exists only as geometry. Signals do not flow and rewards do not calculate. The securing of the 512th position triggers the genesis event.

The public formation view can illustrate position states on the foundation ring in chronological order. Under evaluation and secured correspond to stages in the formation process. Evaluation is manual; commitment follows only after structural clearance. The diagram is illustrative; binding terms are in the formation documentation.

Intelligence layers

Signal processing in ZIRA operates across four layers that stack from raw input to actionable field state:

Anchor Classes

Five hundred twelve structural positions distributed across six classes form the complete field map. Classes are permanent: a position's class does not change after genesis. Higher classes carry greater influence weight in the field and require a larger ZIR commitment at the Foundation price.

Total positions: 512. Total ZIR across all classes at Foundation price: approximately 494.4 million ZIR. This represents approximately 4.9% of the fixed 10 billion supply dedicated to founding structural positions.

Anchors are not fungible tokens

Anchors are fixed seats in the field: positions, routing points, and value collectors. They are not a generic token you mint on demand. As coordination activity increases, settlement and signal traffic concentrate along high alignment pathways. Anchors located on those pathways see higher throughput by geometry, not by manual preference.

Economy loop (how demand stacks)

Intelligent agents generate work. Work opens flows. Flows require ZIR for protocol fees, streaming balances, oracle stakes, and settlement. Flows route through the anchor map. Each additional parallel job repeats the same consumption pattern, so total demand scales with coordination load while supply stays fixed at genesis.

Early anchor advantage is primarily structural: first secured routes tend to become default highways as the field matures. That is placement in the graph, not a discount narrative.

Foundation seating

All 512 positions are foundation anchors. Class determines influence weight and geometric role (Genesis through Foundation class). The ZIRA team holds 24 seats across classes for long term alignment; the remainder are allocated through public formation. After genesis, every class participates in coordination rewards under the same protocol rules.

Participant Roles

ZIRA has four primary participant roles. A single entity can fill multiple roles simultaneously. Roles are not exclusive.

Validators

Validate transactions, maintain field state, and participate in consensus. Validators stake ZIR as collateral and earn base rewards plus a share of transaction fees. Validator rewards scale with ZTI. Poor-quality validation loses stake. Validators form the backbone of the infrastructure layer.

Operators

Build applications, services, and integrations that use ZIRA's coordination primitives. Operators access the field through the agreement and flow APIs. They pay execution fees in ZIR and can earn revenue from the services they build on top. An Operator building a successful AI agent marketplace, for example, earns both from service fees and from the coordination demand their marketplace generates.

Liquidity Providers

Provide ZIR liquidity to the field's settlement pools. Liquidity enables continuous value flows and agreement settlement at scale. Providers earn a share of fee revenue proportional to their contribution and duration. Liquidity provision is not custody: the protocol holds the position, not a counterparty.

Governors

Participate in field parameter updates. This is not a token-vote system. Governor participation in ZIRA means contributing verified expertise to specific protocol improvement processes. Governance weight tracks ZTI and demonstrated domain contribution, not simply token quantity. Capturing governance by accumulating tokens does not work here.

ZIR Token

ZIR is the native unit of the ZIRA field. Ten billion ZIR exists at genesis. No additional ZIR will ever be minted. The supply is hard-capped structurally: there is no governance process that can change it.

Inside the field, ZIR carries three functions. First, it quantifies alignment weight: anchor positions sized in ZIR determine influence on the map. Second, it settles coordination rewards: periodic payouts are in ZIR and distributed proportionally to alignment contribution. Third, it enables agreement execution: fees, collateral, and settlement in programmable agreements are in ZIR.

Outside the field, ZIR is a fixed-supply asset tradable on secondary markets. Its external value is driven by coordination demand. There is no guaranteed price floor, no buyback program, and no reserve fund dedicated to price support.

Activation and ongoing economics. After anchor commitment is verified, participants receive a claim code tied to their position. When ZIRA activates, redeeming that code delivers the structural ZIR allocated to the anchor (per tranche vesting in the foundation window). Coordination rewards are separate: after Field Genesis they accrue over time from alignment and real usage. Anchor owners can receive additional reward streams when their anchors contribute materially to field activity. ZIRA provisions and operates shared anchor infrastructure (nodes, upgrades, monitoring, protocol releases) so the network runs as one coherent technical system.

Supply distribution

The 10 billion ZIR cap is budgeted at genesis into the tranches below. Schedules, cliffs, and vesting apply per row. Foundation phase participants (anchor formation) align with the Foundation phase investment tranche.

Fees and reward mechanics

Every transaction in ZIRA incurs a small protocol fee in ZIR. Fee revenue distributes across four channels: Validators receive 40% for infrastructure maintenance. The Liquidity Reserve receives 30% to maintain settlement depth. Active anchors receive 20% distributed proportionally to alignment contribution. The Field Reserve receives 10% as a buffer against edge conditions.

Coordination rewards are separate from fee distributions. They track alignment contribution over time. Anchors with higher ZTI and stronger convergence participation receive a larger share. The multiplier curve is continuous and updates continuously, not on a batch schedule.

Governance

ZIRA does not use a token-vote governance model. Governance by token accumulation creates well-documented attack vectors: large holders can capture parameter changes, regulatory uncertainty around vote-weight tokens creates legal risk, and quarterly governance cycles interrupt the continuity of a protocol that is designed to run continuously.

Instead, governance in ZIRA follows three principles:

Alignment above ballots. Protocol improvements are proposed, debated, and tested in simulated field conditions before any parameter change takes effect. Participants with demonstrated domain expertise and high ZTI contribute to the technical review process. No token quantity confers automatic veto.

Structural constraints over rules. The core invariants of the protocol (fixed supply, fixed map, behavioral identity) are structural. No governance process can change them. They are not rules that can be voted away. They are properties of the design.

Minimal governance surface. The field is designed to require minimal ongoing governance. Rewards adjust algorithmically. Fees are set by formula. Epoch parameters have bounded ranges. The less governance is required, the less can be captured.

The foundation map itself never reopens: five hundred twelve seats, one geometry. When the field needs a coordinated parameter or rollout change after genesis, proposals still run through simulation, expert review, and observable signals on the field. Nothing in that process adds seats or redraws the anchor map. The heavy lifting stays algorithmic; human and anchor coordination is reserved for rare, high impact updates.

Security Model

Economic security

Attack economics on ZIRA are designed to be unfavorable at every scale. Sybil attacks require staking ZIR per node, making large-scale fake participation prohibitively expensive relative to the rewards available. ZTI manipulation requires sustained behavioral consistency over many epochs, meaning short-term gaming produces short-term ZTI but collapses when the behavior reverses.

Collusion resistance

Colluding anchors can boost each other's short-term signals, but collusion is economically self-limiting. Signals that consistently reinforce only within a closed cluster diverge from the broader field and stop receiving mainstream pathway weight. Colluding clusters must eventually leak honest signals to maintain ZTI, which reduces the economic advantage of the collusion.

Oracle security

Oracle manipulation is bounded by stake requirements and ZTI consequences. A manipulated attestation that is later exposed as incorrect reduces both the oracle's stake and ZTI. Sustained manipulation is economically irrational because the stake loss exceeds the manipulation gain in all modeled scenarios. Human oracle panels have randomized composition, reducing targeting risk.

Privacy

The coordination field tracks behavior on-chain with full auditability. Participants who prefer to minimize public disclosure of participation details can route through autonomous wallet proxies. Behavioral data for ZTI computation is the minimum required to score alignment. ZIRA does not collect marketing data, behavioral analytics for targeting purposes, or identity documents. See the privacy policy for the complete scope.

Emergence

Emergence refers to structural features that form in the field after genesis as a result of sustained alignment behavior. These features are not designed by the protocol. They appear because the incentive structure consistently rewards the behaviors that produce them.

Formation Phase

On the public site, the map, bar, and sample ledger load from a published formation snapshot (the same data file for every visitor), updated when the team publishes new totals. Authoritative records and email correspondence stay with the formation team; the public view is a deliberate mirror designed to be auditable without exposing raw personal data.

The Formation Phase is the initialization period during which structural positions are secured. The field is in a state called Structural Silence during this period. The map exists but signals do not flow and rewards do not calculate. This is by design: an incomplete map would produce distorted patterns that persist even after completion.

The field activates at Field Genesis: the moment the 512th foundation anchor is secured (including the 24 team seats). All foundation positions become active simultaneously. There is no partial activation.

Why the full foundation map is required

The geometric logic of the field requires all 512 foundation positions to be populated before the field state is coherent. An anchor references neighbors in its signal computation; empty seats leave undefined geometry. Partial activation would require special casing that changes the map participants paid for.

Twenty four seats are already secured by the ZIRA team across the six classes. Public formation fills the remaining 488.

Formation journey

The formation dashboard now includes a live allocation table by class (awaiting, cleared, allocated ZIR, and reward-share estimate). It reflects the published snapshot so every viewer sees the same state. Cleared anchors participate in reward routing immediately; anchor allocation transfer unlock occurs once all 512 positions are cleared at genesis.

1. Request evaluation. On the formation page, choose a class, then select a field pattern (visual geometry on the map, no essay). ZIR and USDT figures calibrate allocation. Nothing on the page is a commitment.
2. Manual response. The formation team replies with one of: not aligned (misread), cleared for next step (structural alignment), or request for clarification.
3. Position held (temporary). If your evaluation clears, a seat may be held briefly. Held positions expire if commitment does not follow.
4. Anchor commitment. If a commitment window opens, instructions arrive by email: amount, network, unique receiving address, and any reference id. If you have not received that message, do not send assets.
5. Receive a claim path. After verification, you should get a claim code or link for the published wallet activation flow. That step is when your structural ZIR allocation is tied to your anchor under the foundation terms. That is separate from ongoing coordination rewards.
6. Field genesis. When the 512th foundation position is secured (including team positions reserved in the rules), genesis runs once. Every anchor is meant to switch on together under one ruleset.
7. After genesis. Coordination rewards (if and when live) accrue from real participation in the field (signals, uptime, routes), not from the purchase alone.

Oversubscription Policy

Demand can exceed available positions in any class. Allocation is governed by the published formation rules: verification and ordering determine assignment, not marketing phases.

Per-class allocation. The 16 Genesis positions are independent of the 32 Meridian positions. Filling all Genesis does not block Meridian registration. Each class tracks its own position count independently.

When a class fills. If a class reaches its position count during the securing window, no additional codes for that class will be issued. Participants whose evaluation had cleared but who did not complete commitment before the class filled will need to select an alternative class if available.

Waiting list behavior. If demand materially exceeds remaining capacity, ZIRA may publish a waiting-list process. A waiting list is not a reservation; it is a structured way to offer openings created by forfeitures or expirations. No compensation is provided for missed classes.

Class downgrade option. A participant whose preferred class fills before they complete settlement may request a downgrade to a lower class if seats remain available. Downgrade requests are processed in registration order.

Risk Framing

These are the principal conditions to understand before sizing any position.

The field requires completion

The coordination field does not activate until all 512 foundation anchors are secured (24 team, 488 public). If demand is insufficient to complete the map, the field does not activate and secured participants should expect a published resolution process.

Early field behavior is volatile by design

The first epochs after genesis will show high signal variance as pathways strengthen and convergence patterns establish for the first time. ZTI scores will fluctuate significantly. Reward rates will be highly variable. Early participants should expect this volatility and size positions accordingly.

External ZIR is subject to market forces

When ZIR becomes tradable as an external asset, its price is determined by market liquidity, demand, and risk appetite. There is no guaranteed price floor, no reserve fund for price support, and no buyback mechanism. Coordination demand may not translate into external price appreciation in any particular timeframe.

Protocol risk

ZIRA is new infrastructure. Smart contract vulnerabilities, oracle failures, and protocol design errors are possible. Security audits reduce this risk but do not eliminate it. Participants should treat formation participation as early infrastructure investment with commensurate risk tolerance.

Regulatory environment

Regulatory treatment of coordination tokens, autonomous wallets, and AI agent economics is unsettled in most jurisdictions. Changes to regulation may affect participation structures, ZIR transferability, and agreement enforceability. ZIRA is designed for long-term protocol resilience, but near-term regulatory changes can create friction or delay.

Formation Terms

The following terms apply to participation in the ZIRA Formation Phase.

Foundation price

The Foundation price is $0.001 USD per ZIR. This price is fixed for the Formation Phase and applies to all six anchor classes. No discounts or bonuses alter this price. ZIR quantities per class are defined in the class table above.

Settlement currency

Anchor commitment uses USDT only. Both TRC-20 (Tron) and ERC-20 (Ethereum) variants are supported. No other asset class. Amounts are fixed per class. Receiving addresses are unique per cleared applicant and provided only in the commitment email.

Payment verification

If a commitment window opens, participants may be required to submit their transaction hash after sending USDT. A position is secured after on-chain verification. Positions are not held indefinitely: held windows expire. Submitting a transaction hash does not reserve a position until the transaction confirms on-chain.

Code expiry

Securing codes expire 72 hours after issuance. Expired codes cannot be reactivated. Participants who miss their window may re-register for a subsequent round if the class has remaining seats. There is no guarantee of a second-round opportunity if the class fills in the first window.

No refunds after genesis

Once Field Genesis occurs, all secured positions are final. Class ZIR is credited through anchor activation tied to verified commitment; after genesis those positions are locked into the live field and cannot be reversed as formation entries. Before genesis, if the full 512-position foundation complement is not secured within the formation timeline, ZIRA will publish a resolution process for secured participants.

No financial advice

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.

Privacy

ZIRA collects only what is needed for formation mechanics: email address, class selection, and transaction hash. No tracking pixels or ad tech. Email addresses are used for formation instructions and updates. See Legal for the full policy.

Brand & design

Site logos: assets/zira-mark.svg (icon / favicon)