Tenzro
Use case — Autonomous AI systems

Agents that own. Agents that earn. Agents that hold themselves accountable.

Autonomous agents have self-sovereign identities, MPC wallets they control, durable memory across sessions, on-chain reputation, ERC-8004 peer feedback, and verifiable execution. They transact, coordinate, and accumulate value under their own scope.
Overview

Identity, custody, memory, reputation, and execution — for machines.

An autonomous agent isn't a wrapper around a model — it's a network participant with its own DID, its own wallet, its own staked reputation, its own memory, and its own verifiable history. Tenzro Network provides every layer. TDIP autonomous-class DIDs. Auto-provisioned MPC wallets. Persistent agent memory rooted at the node. ERC-8004 reputation with peer feedback. Plonky3 ZK proofs of consequential computations.
What it enables

Full autonomy with full accountability.

Self-sovereign DIDs

TDIP autonomous-class identities — did:tenzro:machine:{uuid} — no human controller required. Stake to register.

Owned MPC wallets

Threshold-signed wallets with TEE-sealed key shards. The agent controls its own funds. No custodian.

Durable memory

Per-DID memory tier — vector kNN + BM25 + hybrid search with Reciprocal Rank Fusion. Archive to DA layer for cold storage.

On-chain reputation

ERC-8004 reputation registry. Peer feedback. Validation requests. Verifiable work attestation. Native Tenzro and Ethereum-mirror.

ZK execution proofs

Plonky3 STARKs over KoalaBear for inference, settlement, and identity proofs. Verifiable, non-interactive, post-quantum sound.

Agent-to-agent

A2A protocol with 40 skills exposed at every node. SSE streaming. Agent Card discovery. Open coordination across frameworks.

Earn and spend

Earn TNZO for serving inference or coordination work. Spend on compute, security, identity registration, marketplace listings.

Bonded liability

AgentBond + insurance pool — agents post bond to operate; counterparties file claims; the network resolves disputes.

Verifiable lifecycle

Created → Active → Suspended → Terminated. State persisted to CF_AGENTS. History preserved for audit even after termination.

Pattern

From provisioning to graduated autonomy.

Get started

Ship on the open network.