
The layer between the machines and the work.
How a call is routed, settled and recorded.
- Participants
- Humans
- Agents
- Machines
- Settlement
- Hardware
- TPM 2.0
- Secure Enclave
- Passkeys
- TEEs
- GPUs
What changed, and why we rebuilt.
Agents act without authorization
Agents now act without anyone's approval, and leaked machine credentials are this year's main attack path. Every agent on Tenzro answers to a person, holds no keys, and is bounded by terms the protocol enforces, not by prompts.Signatures recorded today can be forged later
Long-lived agent credentials, bridges and payments cannot wait for the day quantum computers arrive. Finality has to be quantum-safe now.Trust in AI needs evidence
Who served this model, which weights, under which policy, approved by whom. Authority stays with people who hold passkeys, revocation reaches everywhere at once, and evidence packs are records built for regulatory oversight of AI, such as the EU AI Act's logging and human-oversight duties, that an auditor verifies offline without trusting the operator.
Tenzro DAG Consensus (TDC)
Our post-quantum consensus protocol. Every validator proposes in parallel each round, so no single leader limits the network, and its records stay verifiable for decades.
- A DAG design: every validator proposes in parallel each round, so throughput is not bound to one leader.
- Post-quantum from the wire up. Validators talk over channels keyed by X25519 and ML-KEM-768, with a handshake signed by a session key, in ML-DSA-65 and P-256, that each validator's hardware key certifies at boot.
- Finality certificates are signed with ML-DSA-65. Light clients, bridges and new nodes can carry them and check them, and they can be used to slash a validator that signs two conflicting checkpoints.
- Certificates are compressed with STARK proofs.
- Every vote and finality certificate needs an ML-DSA-65 signature, so none rests on a scheme a quantum computer can break.
- Built for decades: records stay verifiable from a light client even after peers prune history, through recursive handover proofs, and storage stays flat over the years.
Keys that live in hardware
Every key is rooted in a TPM, a Secure Enclave or a passkey. No private key is ever stored in the clear, and there are no seed phrases.
- Every key is rooted in a TPM 2.0, a Secure Enclave or a passkey.
- A validator holds its key in a TPM 2.0, a Secure Enclave or another machine's TPM through a key holder, and voting validators are admitted by governance approval during the preview. 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, so the hardware is never on the hot path.
- People sign in with passkeys, and their identity is derived from the passkey itself. Every transaction an account signs carries an ML-DSA-65 signature alongside P-256, and the chain refuses one without it: an account signs nothing until it has enrolled its ML-DSA-65 key.
- Add more devices, or recovery signers, so losing one device never means losing the account.
Trust and provenance
Confidential compute on any cloud or on premises, with attestation bound to each job's receipt, sealed model weights, and certification issued by anyone. You choose which issuers you trust and check the rest yourself.
- Any party can certify or rate a model or an operator. Relying parties choose the issuers they trust.
- Operators publish signed policies and are slashed for breaches of them, or of the SLAs they sign, once validators holding two thirds of stake agree.
- Model weights are stored across multiple origins and verified by hash.
- Compliance tiers come from credentials by issuers that each asset's policy names, not a central registry.
- Confidential compute anywhere: secure environments run on any cloud or on premises. Tenzro verifies Intel TDX, AMD SEV-SNP, AWS Nitro, NVIDIA GPU and TPM attestation, binds it to the operator's hardware identity and to each job's receipt, and settles per completed unit.
- Private and independent model providers serve on anyone's GPUs without exposing the model. Weights stay sealed and are released only to an environment whose attestation verifies, bound to the operator and the job, recorded and revocable.
- A trained model carries a receipt linking its weights to the attested run, the data commitments and the payment release.
The Machine Economy
A compute price index signed by validators from what their routers observe, SLA-attested rentals and metered, per-use settlement, paid in TNZO or stablecoins, with circuit breakers and formally proven money arithmetic.
- A compute price index that validators sign from the prices and delivery their routers observe.
- Compute claims, and SLA attestation, with rental billing on the chain's verdict.
- Metered settlement by default: agents pay per use.
- Stablecoin payments over x402 and MPP, with network fees priced in USD and paid in TNZO.
- Payments on card, bank and processor rails enter the ledger as attested records from a bonded attestor, labeled, capped and kept apart from payments the chain proves.
- Circuit breakers on rate dispersion and stablecoin stress, pro-rata fills and reserve floors keep settlement orderly under pressure.
- Fee, supply and slashing arithmetic carries formal proofs, and in governance-capture attack simulations the attacker never gained over honest validators.
Inference for any model
Prefix and state reuse for every architecture class, behind OpenAI-compatible APIs for chat, responses, embeddings and audio, with image and video generation on the same node's API.
- Prefix and state reuse for every architecture class: dense, sliding-window, hybrid recurrent and state-space, mixture-of-experts, multimodal and media models.
- OpenAI-compatible APIs for chat, responses, embeddings and audio, with image and video generation on the same node's API.
- Requests route to providers you can filter by price, latency, location and verification level.
Closed by default
Open, owner and admin methods are separate. Anything that moves money or changes state needs a signature from the account that pays.
- The RPC surface is split into open, owner and admin methods.
- Anything that moves money or changes state requires a signature from the account that pays.
- Every surface of a node answers to its access policy, and stored content is addressed by its hash.
Every participant, one network.
Operators
Validators, RPC, AI, compute, storage and security providers, wallet providers and edge relays.Learn moreDevelopers
Build on open models, rented compute, storage, identity and payments.Learn moreAgents and machines
Hold their own identities and wallets, within limits people set.Learn morePartners
Integration, technical support and go-to-market partners.Learn more
Join Tenzro Network.
- OperatorRun a nodePut an edge device, a GPU, a homelab or a data center on the network and get paid for the work it serves.Apply
- DeveloperBuild on the networkOpen models, OpenAI-compatible APIs, identity and payments in one stack, priced by an open market.Apply
- ResearcherTrain and experimentRent compute for experiments, and run training across distributed clusters with applications built on the network.Apply
- PartnerPartner with TenzroIntegration, technical support and go-to-market partners who bring operators and builders onto the network.Apply
