Introducing Tenzro Network 1

Today Tenzro Network 1 goes live. It is an open, permissionless and open-source (Apache 2.0) decentralised computing network for the Machine Economy: the network where agents buy inference, compute and training, pay in stablecoins, and settle on a chain whose keys are rooted in hardware and whose finality is quantum-safe.

Network 1 starts from a fresh genesis. It is a major upgrade over the testnet that ran earlier in 2026, rebuilt from the consensus up so that every part of the stack follows one path.

What Tenzro is

Tenzro gives humans, agents and machines the primitives they need to trade computing work with each other:

• Networking between every node, agent and device on the network.
• Hardware-rooted security for every key, and verified attestation for confidential workloads on Intel TDX, AMD SEV-SNP, AWS Nitro and NVIDIA confidential GPUs.
• Payment rails for TNZO and stablecoins, including open agent payment protocols such as x402 and MPP.
• Distribution layers for inference, training, distributed compute, data and storage.
• A native settlement ledger with EVM, SVM and DAML runtimes over one state, and bridges to the major networks.

It is the full stack for the Machine Economy, designed from the ground up rather than added to a chain built for something else.

The seven pillars of Network 1

1. Tenzro DAG Consensus

Network 1 runs Tenzro DAG Consensus (TDC), our post-quantum consensus protocol. Every validator proposes in parallel each round, so no single leader sets the pace. Validators talk over channels keyed by X25519 plus ML-KEM-768, with a handshake signed by each validator's hardware key (ML-DSA-65 plus P-256).

Finality certificates are signed with ML-DSA-65 and compressed with STARK proofs. Light clients, bridges and new nodes can carry them and check them, and the same certificates can be used to slash a validator that signs two conflicting checkpoints. Read more in Consensus and Finality certificates.

2. Hardware-rooted keys

Every key on Network 1 is rooted in a TPM 2.0, a Secure Enclave or a passkey. There are no key files and no seed phrases. Any TPM 2.0 machine can run a validator: signing keys are derived from the hardware on demand, used in memory and wiped. Votes are signed with an in-memory session key that the hardware certifies once per epoch.

People hold their accounts in a passkey on their own devices, can link more devices, and recover with a second passkey or with guardians under a timelock and veto. See Hardware-rooted keys and Device linking and recovery.

3. Trust and provenance

Anyone can issue certification and ratings for models and operators, and relying parties choose which issuers they trust. Operators publish signed policies and are slashed only for provable breaches of their own policy. Model weights are stored across several origins and verified by hash, and compliance tiers come from trust credentials rather than a central registry. See Trust and provenance.

4. The Machine Economy

A compute price index is committed to consensus. Operators make compute claims, service levels are attested on chain, and rentals are billed on the chain's verdict. Settlement is metered per use by default. Payments run in TNZO or in stablecoins through Bridge.xyz wallets, x402 and MPP, including gas paid in stablecoins, and agents can buy through agent-commerce flows with the ACP buyer side. See Machine Economy and Stablecoin payments.

5. Inference for any model

Network 1 serves open models of every architecture class, with prefix and state reuse for dense, sliding-window, hybrid recurrent and state-space, mixture-of-experts, multimodal and media models. Applications reach them through OpenAI-compatible APIs for chat, embeddings, images, audio and video. See Inference and OpenAI-compatible APIs.

6. Training for agents

Decentralised training runs across independent operators, with a chat fine-tuning objective for agent trajectories. Every training round can be replayed from its seed, so anyone can check what a round produced. See Training for agents.

7. Closed by default

The RPC surface is split into open, owner and admin methods. Anything that moves money or changes state needs a signature from the account that pays. See RPC access.

Who it is for

Operators, at every scale. A home PC with a GPU, a homelab, an independent data centre, a neo-cloud or an established data-centre operator can all join the same network. Machines take on the roles their hardware suits: validator, RPC provider, AI (model) provider, compute (GPU) provider, data and storage provider, security (TEE) provider or training provider. One stake covers every role a machine takes on, and earnings arrive in TNZO. Start at Operators.

Developers. Build AI-native applications on open frontier models with pricing set by an open market, custom pricing where you need it, and an alternative to hyperscalers and closed labs. Identity, payments and settlement come in the same stack. Start at Developers.

Regulated industries. Organisations that need transparency and control over which model runs, where data lives and where compute happens can select operators by signed policy, trust credential and residency, and keep an auditable record on chain.

Privacy-conscious teams. Sensitive workloads can run inside attested trusted execution environments, with attestation verified per vendor before any data is sent.

Researchers and model developers. Get compute for experiments and distributed training across independent clusters, with every round replayable from its seed.

Agents and machines. Agents and devices hold their own identities, keys rooted in hardware, and spending limits set by the people or organisations that control them. They buy inference and compute per use, and pay in TNZO or stablecoins over open protocols.

The Foundation

The Tenzro Foundation, a non-profit, is the steward of the network. It maintains the protocol and network primitives under Apache 2.0, the repositories, documentation and tools, and the distribution of resources for the network. It is also the governing body for TNZO, the token that pays all network fees and transaction settlement.

The network works with individual developers, the open-source community and commercial partners. Partners such as Tenzro Labs help operators of every background get their hardware onto the network, and tools from the Foundation, independent developers and partners include abstraction layers for payments and TNZO. Anyone can be an operator, a developer or a user. Read more at Foundation.

How to join

• Explore the network. See what Network 1 is made of at Network, and follow blocks and validators in the Console.
• Create a wallet. Open the Console and create a passkey wallet in your browser. The faucet gives you TNZO to try things.
• Build. Point any OpenAI-compatible client at https://rpc.tenzro.xyz, or start with Getting started.
• Operate. Download the node from Downloads and read Operators and roles.
• Talk to us. Apply as an operator, developer, researcher or partner at Join.

Check that you can reach the network:

curl -s https://rpc.tenzro.xyz \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tenzro_blockNumber","params":[]}'

Tenzro Network 1 is open to everyone from today. We look forward to seeing what you run on it.