Frequently asked questions.
What is Tenzro Network?
Tenzro is an open network where AI runs — owned by everyone, not one company. AI models, providers, secure hardware, validators, identities, agents, payments, and settlement — all held together by TNZO, the network's money. Tenzro Ledger is the settlement layer inside the network; it is one part, not the whole.
What is TNZO used for?
TNZO is the economic unit of the network. It pays for compute and access — transaction fees, AI inference, TEE-backed confidential compute, agent operations, and settlement. It is also staked by validators and providers, and used to vote on governance. 1B genesis supply, 18 decimals, fixed. No team allocation and no investor allocation — community-owned from day one, earned by contributing value to the network.
Who can run a node?
Anyone. Validators participate in a three-tier model — Tier 1 (resource-only, runs the same protocol and signs the same QCs, but quorum weight is the node's own bond, so an unbonded node adds nothing to the tally — no governance vote, no slashing exposure), Tier 2 (bonded 10k TNZO, full eligibility plus governance vote plus high-trust roles), Tier 3 (RPC provider, bonded 100k TNZO, additionally sanctioned to mint scoped tenant API keys and broker upstream credentials). Service roles bond their own rung on the stake ladder without carrying consensus weight: ModelProvider 1k TNZO (serves inference), TeeProvider 10k (confidential compute, hardware attested), TrainingProvider and Syncer 1k each (Tenzro Train), ComputeProvider from 500 scaling per accelerator card, StorageProvider from 100 scaling per terabyte, CloudProvider 1k/5k/25k by the highest service class offered. LightClient verifies without producing blocks and bonds nothing. Admission above each bond is permissionless — no allowlist, no approval step. All open source, all paid in TNZO.
What is testnet status?
Testnet is live. Tenzro Labs operates the initial public RPC nodes (rpc, api, mcp, a2a, faucet, and ecosystem MCP endpoints on tenzro.xyz) with PQ-hybrid TLS at the edge while the validator set decentralizes. 10M TNZO faucet allocation, 1,000 TNZO per request, 24-hour cooldown. Pre-alpha — external security audit scheduled before mainnet.
How are agents secured?
Agents hold their own TDIP DID and MPC-provisioned wallet. Three identity classes: human, delegated machine, autonomous machine. Three-ceiling enforcement on every spend: intent + protocol delegation scope + runtime spending policy. Custody enforced at signing time via ERC-7579 modular validators on the smart account itself.
How do payments work?
MPP (Stripe + Tempo co-author), x402 (Coinbase), AP2 (Visa / Mastercard cart mandates), Visa Trusted Agent Protocol, Mastercard Agent Pay, Tempo for stablecoin settlement, RFC 9421 signed HTTP. All HTTP 402-gated, all settle on Tenzro Ledger. The network's share of a settled payment is set by the serving node's economic mode: a private node keeps the whole payment, a public validating node pays 10% to the treasury, and a public node that does not validate pays 10% to the treasury and 10% to the RPC provider validating for its users.
What models can I serve?
Default catalog: Qwen 3, Gemma 3, Mistral, Phi 3, DeepSeek V3, Granite (language). TimesFM 2.5 (forecasting). CLIP, SigLIP2, DINOv3 (vision). SAM 2, EdgeSAM, MobileSAM (segmentation). RF-DETR, D-FINE (detection). Whisper, Parakeet, Canary, Moonshine (audio). Qwen3-Embedding, EmbeddingGemma, BGE-M3, Snowflake Arctic (text embedding).
What about cross-chain?
Wormhole NTT is the primary TNZO bridge. LayerZero V2 with a mandatory Tenzro DVN handles messaging. Chainlink CCIP + CCT v1.6+ pools, deBridge DLN for intent-based swaps, Li.Fi as the aggregator across 130+ chains, Canton for regulated enterprise ledgers.
How is the network upgraded?
On-chain governance. Stake-weighted proposals, timelock queue, executor calls. The adaptive burn dial has a fast-track path with reduced delay. Validator set rotates per epoch through the EpochManager — any staked node can join via pending_validators at the next epoch boundary.
How do validators upgrade their binary without breaking the network?
Image rolls preserve the local chain DB; on boot the node verifies the configured genesis (chain_id + state_root) matches what's on disk and refuses to start if either drifts. Bootstrap peers are resolved via DNS (--bootstrap-dns) instead of hardcoded peer IDs, so rotating one validator's key is a zone edit, not a fleet-wide wrapper update. Validator consensus / PQ / BLS keys rotate via the consensus-mediated tenzro_rotateValidatorKey RPC — the new key tuple becomes live at the next epoch boundary with no split-key window. Fresh validators self-bootstrap from snapshots verified against a weak-subjectivity anchor embedded in genesis. Details in the operator guide §9 (Validator Lifecycle Operations).
Where do I start?
Install the CLI, claim TNZO from the faucet, run your first inference, and register an identity. The start-building page walks through each step with copy-pasteable commands.