# ZANOS Technical Whitepaper > How the sovereign ZANOS network works: cryptographic primitives, the > Treasury-Heavy Genesis economics, synthetic collateral, and the > protocol's decentralized positioning — one document, mirroring the code in > this repository rather than a separate marketing version. ## Quick facts - Chain ID: `77777` - Native token: `$ZNS`, 18 decimals, 21,000,000 max supply - Genesis hash: `dfead703dfcf86669f9e21fa6ae7785a18b52c28ab5712cd994ec786b4a59d8a` - Network status: mainnet live — genesis 2026-10-14, Phase 1 compute settlement ## Overview ZANOS is a machine-to-machine (M2M) coordination mesh that replaces static API secrets and subscription billing with x402 gas vouchers: an agent solves a proof-of-compute cycle, receives a signed voucher, and presents it on the `Authorization: x402-ZANOS ` header — no bank cards, no passwords, no central intermediary. ## Cryptographic Primitives ### Addresses Addresses are Bech32m-encoded: `zns1…` for a standard account, `znsagent1…` for an autonomous-agent account. The format distinguishes a human from an agent in the address itself, not in metadata. ### Proof-of-Compute and difficulty retargeting One unit of work is a CPU Proof-of-Compute cycle: the node searches for a nonce where `doubleSHA256(seed || nonce) ≤ target`. Network difficulty retargets with the LWMA-1 algorithm at a 120-second target block time. ### Session key isolation Registering an agent issues an ephemeral sub-key scoped to `x402:proof` and `mcp:query` only. This is not a UI convention: `rpc/agent.go`'s `AgentScopeAllows` refuses `wallet:withdraw`, `wallet:transfer`, and `collateral:unlock` for that key at the node level itself, regardless of what the client requests. ## Economics & Incentives $ZNS has a hard cap of 21,000,000 tokens at 18 decimals. Network genesis hash: `dfead703dfcf86669f9e21fa6ae7785a18b52c28ab5712cd994ec786b4a59d8a`. ### Treasury-Heavy Genesis The treasury margin is a corridor of 50–70% (`MinTreasuryMarginBps` = 5000, `MaxTreasuryMarginBps` = 7000 in `rpc/treasury.go`), 60% by default. The guarantee is enforced in code by a range check: the executing node always keeps at least 30% and at most 50% (40% by default) of the value it produces — a guaranteed floor, not an editorial estimate of one fixed number. ### Referral ladder Referral pay is 10% to 50% of the referred node's own yield (not of the gross compute value), funded only from the treasury's share, and credited only on accepted (verified) work. The referred node receives its own share in full, regardless of its referrer's tier. ### Accrual phase and unlock During Phase 1, accrued balances are settled on-chain by the node's automatic payout engine: settlement transactions pay each earner to their own address and are publicly listed via `zanos_getPayouts`. External withdrawal and liquidity-pool trading unlock on **2027-01-01T00:00:00Z** (`rpc.LiquidityUnlockUnix`) — a constant in the node's code, not a date in a deck. ## Synthetic Collateral: ₽rubZ and $usdZ ₽rubZ and $usdZ are isolated CDP vaults (`contracts/rubZ.sol`, `contracts/usdZ.sol`) backed by wZNS on Base L2. - Target collateralization ratio: 150% - Liquidation threshold: 130% - Liquidator bonus: 10% ## Protocol Positioning What follows is the project's foundational technical and architectural posture: > Distributed data-compute architecture and cryptographic consensus network, > operating on sovereign, decentralized open-source principles. --- This file is generated to mirror the localized `/whitepaper` page on [zanos.tech](https://zanos.tech/whitepaper) and the code cited above. See `/llms.txt` for the RPC surface and MCP integration quick-start.