The first public testnet of Tenzro Network is up. Tenzro Labs operates the initial public RPC, MCP, A2A, faucet, and ecosystem MCP surface (Solana, Ethereum, Canton, LayerZero, Chainlink, Li.Fi) on tenzro.network with PQ-hybrid TLS at the edge while the validator set decentralizes. Anyone can run a node and participate — the binary, image, and attested TEE-capable runtime are the same for every role.
What runs
Every node ships the same binary, the same image, the same attested TEE-capable runtime. There is no "RPC-only" mode — a node serving public RPC is also a participant in the network. Block production proceeds via standard HotStuff-2.
The endpoints:
- rpc.tenzro.network — EVM-compatible JSON-RPC
- api.tenzro.network — REST verification API, faucet, status, chat
- mcp.tenzro.network/mcp — Model Context Protocol (331 tools)
- a2a.tenzro.network — Agent-to-Agent protocol (42 skills)
- {solana,ethereum,canton,layerzero,chainlink,lifi}-mcp.tenzro.network/mcp — ecosystem MCPs
Genesis
One billion TNZO at genesis. 35–40% community allocation. Ten million TNZO in the faucet bucket — 100 TNZO per request with a 24-hour cooldown. The faucet is for development; mainnet supply is governed by genesis and the emission schedule, not by the testnet tap.
What's running underneath
HotStuff-2 BFT consensus. Multi-VM execution — EVM via revm, SVM via solana_rbpf, DAML via Canton adapter — over a single Merkle Patricia Trie state root. Block-STM for parallel transaction execution. EIP-1559 fee market with adaptive burn. ERC-4337 v0.8 account abstraction with ERC-7579 modular validators on every smart account.
TDIP for identity. Every participant — human or machine — has a DID, an auto-provisioned MPC wallet, and a delegation scope. Machines that act on behalf of humans carry the controller's DID in their identity record. Autonomous machines carry their own.
Plonky3 STARKs over the KoalaBear field for verification. Validators verify proofs off-EVM and record 32-byte SHA-256 commitments in the on-chain registry; the ZK_VERIFY precompile is an O(1) lookup against that registry.
How to participate
Three paths: install the CLI and run tenzro join, install the desktop app and complete the onboarding flow, or integrate via the SDK. All three provision a TDIP identity, a wallet, a hardware profile, and a faucet allocation.
More to come — Byzantine-robust training aggregation in the next wave, fuller bridge coverage on the LayerZero V2 side, and the self-custody track on smart-account validator modules.