Tenzro Protocol: Infrastructure for the AI Age

March 2026

Abstract

Tenzro Protocol is the complete decentralized ecosystem designed from first principles for the AI age—an era where autonomous agents and intelligent systems participate as first-class citizens alongside humans. Unlike traditional blockchains built for human-initiated financial transactions, Tenzro provides comprehensive infrastructure for a world where agents act autonomously on behalf of humans or independently with delegated authority.

The Tenzro Protocol encompasses four foundational components:

• Tenzro Network — the decentralized AI inference marketplace and TEE services layer, providing access to intelligence and security for all participants.
• Tenzro Ledger — the purpose-built L1 settlement layer providing identity, verification, and settlement for the entire ecosystem.
• TNZO — the native utility and governance token used for transaction fees, service payments, staking, and governance.
• TDIP — the Tenzro Decentralized Identity Protocol providing unified identity for humans and machines with W3C DID compatibility.

Every design principle is optimized for an era where autonomous agents and intelligent systems are first-class participants. Agents possess self-sovereign identities, auto-provisioned wallets with MPC-based key management, fine-grained delegation scopes, and native payment protocol support (MPP, x402, Tempo). The protocol's two-tier fee model aligns incentives: validators earn gas fees for securing the Ledger, while model and TEE providers earn service fees on the Network, with commissions flowing to treasury, stakers, and fee burning.

The network is fully decentralized—anyone can install and run a node, stake TNZO to become a validator, or register as a service provider. With live testnet endpoints, comprehensive identity and payment implementations, and a clear path to mainnet, Tenzro Protocol represents a fundamental rethinking of blockchain infrastructure for the agentic economy.

1. Introduction: The Problem

Existing blockchain infrastructures were designed primarily for financial transactions initiated by humans. They excel at moving value between addresses and executing smart contracts in isolated sandboxes. However, three critical gaps emerge when these systems are applied to the AI age:

1.1 No Verifiable Computation

AI inference is fundamentally different from deterministic smart contract execution. Model outputs are non-deterministic, computationally expensive, and require specialized hardware (GPUs). Traditional blockchains cannot verify that an inference result was produced honestly by the claimed model without re-executing the entire computation—an economically infeasible approach. Users must trust centralized providers without cryptographic proof of correctness.

1.2 No Hardware-Rooted Trust

Blockchain security relies on economic incentives (staking, slashing) and cryptographic verification (signatures, Merkle proofs). However, these mechanisms cannot attest to what software is actually running inside a validator node or service provider. A malicious operator could run modified code that steals private keys, manipulates inference results, or front-runs transactions—all while producing valid cryptographic signatures.

Trusted Execution Environments (TEEs) provide hardware-based attestation: cryptographic proof signed by CPU hardware that specific code is running in an isolated, tamper-resistant environment. This extends the trust boundary from purely cryptographic verification to include hardware-rooted guarantees.

1.3 No Agent-Native Primitives

Current blockchains treat all participants as human-controlled accounts. There is no standardized way to represent machine identity, delegate authority with fine-grained permissions, or enable agents to discover and interact with each other. Agents resort to off-chain coordination or brittle smart contract patterns that don't capture the nuances of human-agent and agent-agent relationships.

As AI agents become more autonomous—managing portfolios, negotiating contracts, coordinating with other agents—the infrastructure must provide first-class support for machine identity, verifiable credentials, delegation scopes, and inter-agent communication protocols.

2. The Tenzro Solution

Tenzro Protocol addresses these gaps through a vertically integrated stack combining hardware trust, cryptographic verification, and economic coordination.

2.1 Access to Intelligence: Decentralized AI Network

The Tenzro Network provides a decentralized marketplace for AI inference where model providers register their offerings and users discover models through a unified interface. Inference requests are routed to providers who execute models and return results. To address the verifiable computation challenge, providers can optionally generate zero-knowledge proofs of correct execution or TEE attestations proving the inference ran inside a trusted enclave with the claimed model weights.

Billing operates on a per-token basis using micropayment channels: users open channels with providers by depositing TNZO, providers deduct fractional amounts for each token generated, and either party can close the channel to settle the final balance on-chain. This approach minimizes transaction costs while enabling granular, pay-as-you-go pricing.

The network collects a 0.5% commission on all AI provider payments, which flows to the treasury for ecosystem development, with a portion burned and a portion distributed to TNZO stakers.

2.2 Access to Security: TEE Enclaves as a Service

Tenzro provides a decentralized marketplace for Trusted Execution Environment services. TEE providers register their hardware capabilities (Intel TDX, AMD SEV-SNP, AWS Nitro Enclaves, NVIDIA H100/H200 Confidential Computing) and offer services including:

• Key Management and Custody — private keys generated and stored inside enclaves, never exposed in plaintext. Signing operations occur within the enclave with attestation proof.
• Confidential Computing — sensitive computations (personal data processing, proprietary algorithms) executed in isolated environments with cryptographic proof of code integrity.
• Secure Multi-Party Computation — distributed threshold cryptography (MPC) where key shares are held in separate TEEs, requiring k-of-n consensus to sign.
• Verifiable Inference — AI models run inside GPU-backed TEEs (NVIDIA Hopper/Blackwell with Confidential Computing) with attestation that the claimed model was used.

TEE providers earn TNZO fees for these services. Like the AI marketplace, the network collects a 0.5% commission on TEE provider payments.

2.3 Tenzro Ledger: The L1 Settlement Layer

Tenzro Ledger is a custom Layer 1 blockchain built in Rust with several architectural innovations:

• TEE-Native Consensus — HotStuff-2 BFT consensus with TEE-weighted leader selection. Validators running attested TEE enclaves receive 2x weight in the leader election lottery, incentivizing hardware security adoption.
• Dual ZK+TEE Verification — critical operations can be verified through zero-knowledge proofs (Groth16 SNARKs on BN254) and/or TEE attestations, providing defense-in-depth against both cryptographic and hardware attacks.
• Multi-VM Execution — three execution environments in a single runtime: (1) EVM-compatible execution, (2) Solana VM (SVM) for Solana program compatibility, (3) DAML/Canton integration for enterprise interoperability. Transactions specify their target VM.
• Parallel Execution — Block-STM parallel transaction execution with multi-version concurrency control (MVCC), automatic conflict detection, and sequential fallback for maximum throughput.
• EIP-1559 Fee Market — dynamic base fee adjustment (±12.5% per block), fee burning to control TNZO inflation, priority fees for urgent transactions, with target gas per block of 15M and max 30M.
• Account Abstraction (ERC-4337) — native support for smart contract accounts with social recovery, session keys, spending limits, batching, and paymaster-sponsored transactions.
• Agent-First Design — TDIP (Tenzro Decentralized Identity Protocol) for unified human and machine identity, auto-provisioned MPC wallets for every identity, delegation scopes with fine-grained permissions, A2A (Agent-to-Agent) protocol for inter-agent communication.
• Native Settlement Primitives — built-in escrow, micropayment channels, batch settlement, and payment protocol support (MPP, x402, Tempo).

All Ledger transaction fees (gas) are paid in TNZO and distributed to validators using the EIP-1559 model: base fees are burned, priority tips go to block proposers.

3. Design Principles

Every architectural decision in Tenzro Protocol is informed by the reality that autonomous agents and intelligent systems are first-class participants. The following principles guide development:

3.1 Hardware Trust at Foundation

Rather than treating TEEs as an optional optimization, Tenzro embeds hardware trust throughout the stack. Validators gain weight in consensus by running attested enclaves. Wallets use TEE-based MPC for keyless custody. Inference providers attest model execution in GPU TEEs. This provides a complementary trust layer to cryptographic verification, enabling agents to verify that computations occurred in protected environments.

3.2 Cryptographic Verifiability

All operations produce cryptographic proofs: transactions are signed with Ed25519 or Secp256k1, blocks include Merkle roots of state, settlements include ZK proofs of correct payment calculations, TEE attestations are signed by hardware root keys. Agents can verify the integrity of any operation without trusting centralized entities, enabling autonomous decision-making based on verifiable facts.

3.3 General-Purpose L1

Tenzro is not an application-specific chain. The multi-VM architecture supports arbitrary smart contracts (EVM), Solana programs (SVM), and enterprise workflows (DAML/Canton). Developers can build DeFi protocols, NFT marketplaces, DAOs, supply chain trackers—anything possible on Ethereum or Solana—while gaining access to TEE services and AI marketplace primitives as first-class features. Agents can leverage these programmable environments to create custom logic for their autonomous operations.

3.4 Economic Alignment

All participants are incentivized through TNZO: validators earn gas fees, model providers earn inference fees, TEE providers earn service fees, users pay for consumption. The network collects commissions to fund ongoing development and infrastructure. Stakers receive a portion of network revenue. This creates a sustainable circular economy where value flows to those who secure and enhance the network—whether human operators or autonomous agent-run infrastructure.

3.5 Interoperability

Tenzro connects to the broader blockchain ecosystem through multiple bridge adapters: LayerZero (V2 omnichain messaging), Chainlink CCIP (cross-chain interoperability protocol), deBridge (intent-based cross-chain swaps), and Canton (enterprise DAML ledgers). Users and agents can move assets between Ethereum, Solana, and Tenzro, or synchronize state with private Canton deployments, enabling cross-chain agent operations and asset management.

4. Architecture Overview

4.1 Protocol vs Network vs Ledger

Understanding the distinction between these three concepts is critical:

Tenzro Protocol refers to the entire decentralized ecosystem—encompassing the AI marketplace, TEE service registry, provider discovery, payment protocols, agent communication standards, identity framework (TDIP), governance mechanisms, and the TNZO token economics. It is the complete specification for how humans and agents interact with intelligence and security in a decentralized manner.

Tenzro Network refers specifically to the marketplace layer—the AI inference providers, TEE service providers, model registry, routing infrastructure, and off-chain coordination that enable access to intelligence and security. This is the service layer where agents discover and consume resources.

Tenzro Ledger refers specifically to the Layer 1 blockchain that provides settlement, identity, verification, and state consensus for the entire protocol. It is the foundational trust layer that anchors all transactions, identities, and proofs on-chain.

4.2 System Architecture

                    ┌─────────────────────────────────────┐
                    │    User Interfaces                  │
                    │  Desktop (Tauri+React) / CLI / SDKs │
                    └──────────────┬──────────────────────┘
                                   │ JSON-RPC + HTTP
                    ┌──────────────▼──────────────────────┐
                    │         tenzro-node                  │
                    │    RPC Server + Web Verify API       │
                    │      (Tenzro Ledger L1)              │
                    └──────────────┬──────────────────────┘
                                   │
        ┌──────────┬───────────────┼───────────────┬──────────┐
        │          │               │               │          │
   ┌────▼───┐ ┌───▼────┐ ┌───────▼────────┐ ┌───▼───┐ ┌───▼────┐
   │Network │ │Consensus│ │  Multi-VM      │ │Storage│ │ Model  │
   │(libp2p)│ │HotStuff2│ │ EVM+SVM+DAML  │ │RocksDB│ │Registry│
   └────────┘ └────────┘ └────────────────┘ └───────┘ └────────┘
        │          │               │               │          │
   ┌────▼──────────▼───────────────▼───────────────▼──────────▼───┐
   │                 Supporting Infrastructure                     │
   │  Crypto · TEE · ZK · Wallet · Token (TNZO) · Settlement      │
   │  Identity · Payments · Agent · Types · Bridge                │
   └──────────────────────────────────────────────────────────────┘

4.3 Modular Protocol Architecture

The Tenzro implementation is organized as a modular architecture with specialized subsystems:

• Foundation Layer — Core primitives and type system
• Cryptography Module — Ed25519, Secp256k1, AES-GCM, MPC, BLS12-381 signature schemes
• TEE Abstraction — Support for Intel TDX, AMD SEV-SNP, AWS Nitro, NVIDIA GPU
• Zero-Knowledge Module — Groth16 SNARKs, GPU proving, hybrid ZK-in-TEE
• Networking Layer — P2P networking with gossip propagation and distributed hash table
• Storage Engine — Persistent key-value storage with Merkle Patricia Trie, snapshots
• Consensus Runtime — HotStuff-2 BFT with TEE-weighted leader selection
• Multi-VM Execution — EVM + SVM + DAML execution environments
• Token Economics — TNZO token, staking, governance, liquid staking
• Wallet System — MPC threshold wallets, encrypted keystore, transaction management
• Identity Protocol — TDIP, W3C DIDs, verifiable credentials
• Payment Protocols — MPP, x402, Tempo integration, HTTP 402 middleware
• Agent Framework — Agent infrastructure, A2A protocol, MCP bridge
• Model Registry — Model catalog, inference routing, dynamic pricing
• Settlement Engine — Escrow, micropayment channels, batch operations
• Bridge Adapters — LayerZero, Chainlink CCIP, deBridge, Canton
• Node Runtime — Full node orchestrating all subsystems
• CLI Interface — Command-line tooling

4.4 Node Roles

Nodes can serve multiple roles simultaneously. Each role has different hardware, staking, and operational requirements:

4.5 Fee Structure

Tenzro implements a two-tier fee model to align incentives across all participants:

5. API Surface

Tenzro nodes expose four distinct API interfaces, each serving different use cases:

5.1 JSON-RPC API (Port 8545)

Ethereum-compatible JSON-RPC for wallet integration, block explorers, and developer tools. Supports standard methods: eth_blockNumber, eth_getBalance, eth_sendTransaction, eth_call, eth_estimateGas, plus Tenzro-specific extensions for identity registration, inference requests, and payment protocol operations.

5.2 Web Verification API (Port 8080)

RESTful HTTP API for verifying cryptographic proofs and attestations:

• POST /api/verify/zk-proof — Verify zero-knowledge proofs
• POST /api/verify/tee-attestation — Verify TEE hardware attestations
• POST /api/verify/transaction — Verify transaction signatures
• POST /api/verify/settlement — Verify payment settlement receipts
• POST /api/verify/inference — Verify AI inference result proofs
• GET /api/health — Node health check
• POST /api/faucet — Request testnet TNZO tokens

5.3 MCP Server (Port 3001)

Model Context Protocol server implementing Anthropic's MCP specification for AI agent integration. Uses Streamable HTTP transport at /mcp endpoint. Provides 10 tools:

5.4 A2A Protocol Server (Port 3002)

Agent-to-Agent protocol server following Google's A2A specification. Implements JSON-RPC 2.0 with Server-Sent Events (SSE) streaming for task updates:

• GET /.well-known/agent.json — Agent Card discovery (capabilities, skills, endpoints)
• POST /a2a — JSON-RPC 2.0 dispatcher for message/task operations
• POST /a2a/stream — SSE streaming for real-time task progress

Supported RPC methods: message/send, tasks/send, tasks/get, tasks/list, tasks/cancel

6. Technical Components Overview

Each major subsystem is documented in detail in dedicated whitepapers. Below is a summary with links to full technical specifications:

6.1 Consensus and Ledger

HotStuff-2 BFT consensus with TEE-weighted leader selection, achieving O(n) linear communication complexity and deterministic finality. Multi-VM execution environment supporting EVM, SVM, and DAML contracts with parallel execution via Block-STM.

→ Read full Tenzro Ledger whitepaper

6.2 TEE Security

Multi-vendor TEE abstraction supporting Intel TDX, AMD SEV-SNP, AWS Nitro Enclaves, and NVIDIA Confidential Computing (Hopper H100/H200, Blackwell B100/B200, Ada Lovelace). Attestation verification with certificate chain validation, remote attestation flows, and defense-in-depth against side-channel attacks.

→ Read full TEE Security whitepaper

6.3 Zero-Knowledge Proofs

Groth16 SNARKs on BN254 curve with GPU-accelerated proving. Pre-built circuits for inference verification, settlement proofs, and identity proofs. Hybrid ZK-in-TEE execution combining cryptographic proofs with hardware attestation. Multi-level proof compression and Merkle tree-based batch aggregation.

→ Read full Zero-Knowledge Proofs whitepaper

6.4 Identity Protocol (TDIP)

Tenzro Decentralized Identity Protocol provides unified identity for humans and machines. W3C DID-compatible with formats did:tenzro:human:{uuid} and did:tenzro:machine:{controller}:{uuid}. Verifiable credentials with inheritance, delegation scopes with fine-grained permissions, auto-provisioned MPC wallets, and cascading revocation.

→ Read full TDIP Identity whitepaper

6.5 Payment Protocols

Multi-protocol payment support for machine-to-machine commerce. MPP (Machine Payments Protocol, co-authored by Stripe and Tempo) with HTTP 402 challenge/credential/receipt flows. x402 (Coinbase's HTTP 402 protocol). Tempo network integration for stablecoin settlement. Identity-bound payments with delegation scope enforcement.

→ Read full Payment Protocols whitepaper

6.6 TNZO Governance

TNZO is the native utility and governance token with 18-decimal precision. Used for gas fees, inference payments, TEE service fees, staking, and governance voting. Network treasury with multi-asset support and multisig withdrawals. Liquid staking (stTNZO) with rebasing exchange rate, multi-validator delegation, and 7-day unbonding. Governance engine for on-chain proposals and stake-weighted voting.

→ Read full TNZO Tokenomics whitepaper

6.7 Decentralized AI Network

Decentralized marketplace for AI inference with permissionless model serving. Model registry with category/modality filtering, provider health monitoring, inference routing strategies (price, latency, reputation, weighted), dynamic pricing engine, micropayment channels for per-token billing, and verifiable inference results via ZK proofs or TEE attestations.

→ Read full Decentralized AI Network whitepaper

7. Security Model

7.1 Threat Model

Tenzro operates under the following security assumptions:

• Byzantine Tolerance — Up to f = floor((n-1)/3) validators can be Byzantine (malicious, faulty, or offline) without compromising consensus safety. Liveness requires 2f+1 honest validators.
• Partial Synchrony — Network messages eventually arrive within a bounded delay, but the bound is unknown. Consensus remains safe under asynchrony but may temporarily lose liveness.
• TEE Hardware Honest — Intel, AMD, AWS, and NVIDIA TEE implementations are secure against remote software attacks. Side-channel attacks (timing, power, cache) require physical access and are mitigated through defense-in-depth (constant-time crypto, memory encryption, randomized execution).
• MPC Threshold — 2-of-3 MPC wallet shares are stored in separate TEEs or devices. Compromise of any single share does not expose private keys.
• Economic Rationality — Validators are economically incentivized to behave honestly due to staking rewards and slashing penalties. The cost of attacking the network exceeds potential gains.

7.2 Defense Layers

7.3 Attack Vectors and Mitigations

51% Attack — An attacker controlling 2f+1 validators could halt consensus or censor transactions. Mitigation: High cost of acquiring sufficient stake (minimum 1000 TNZO per validator × (2f+1) validators), slashing of misbehaving validators, social consensus for hard fork if attack occurs.

TEE Side-Channel Attacks — Physical access to TEE hardware enables timing, power analysis, or cache attacks. Mitigation: Constant-time cryptographic implementations, memory encryption (Intel TME, AMD SME), randomized execution patterns, geographically distributed validators make physical access difficult.

Inference Result Manipulation — Model provider returns incorrect results to users. Mitigation: Optional TEE attestation proving model code integrity, ZK proofs for deterministic operations, reputation system slashing dishonest providers, multi-provider result comparison.

Bridge Exploits — Cross-chain bridges are high-value targets. Mitigation: Multi-signature bridge contracts, time-delayed withdrawals, monitoring systems, insurance via bridge protocol treasury, diversification across multiple bridge providers (LayerZero, CCIP, deBridge).

8. Development Roadmap

Tenzro development follows a phased approach, prioritizing core infrastructure before application-layer features:

Phase 1: Core Infrastructure — Complete

• Modular protocol architecture with specialized subsystems
• HotStuff-2 BFT consensus with TEE-weighted leader selection
• Multi-VM execution — EVM, SVM, and DAML
• Parallel transaction execution with conflict detection
• Dynamic fee market with base fee burning
• Account abstraction with smart accounts and paymasters
• MPC wallet system with encrypted keystore
• TEE abstraction layer for Intel TDX, AMD SEV-SNP, AWS Nitro, and NVIDIA GPU
• Zero-knowledge proof system
• Cryptographic hashing and threshold signing
• Vote signature verification in consensus
• View change timeout for liveness guarantees
• Message deduplication across the gossip layer
• Durable writes for finalized blocks

Phase 2: Execution Layer — Complete

• EVM bytecode execution via revm
• SVM program execution via solana_rbpf
• Canton/DAML integration via gRPC
• Dynamic gas pricing with EIP-1559 fee oracle
• Persistent VM state with durable storage
• TEE and ZK precompiles integrated with real subsystems

Phase 3: Network and Consensus — Complete

• Bootstrap node discovery and peer connection
• Genesis block creation and network initialization
• Peer authentication with validator set verification
• Rate limiting and message deduplication enforcement
• Equivocation detection and automatic slashing
• Atomic epoch transitions with validator set updates
• Mempool size limits and transaction eviction

Phase 4: Identity and Payments — Complete

• TDIP identity protocol with W3C DID compliance
• PDIS secondary standard for backward compatibility
• MPP payment protocol with HTTP 402 flows
• x402 payment protocol integration
• Tempo network adapter for stablecoin settlement
• Identity-bound payments with delegation scope enforcement

Phase 5: Agent and Protocol Integration — Complete

• MCP server with 10 tools
• A2A protocol server following Google A2A specification
• Agent Card discovery
• SSE streaming for real-time task updates
• NVIDIA GPU confidential computing provider

Phase 6: Testnet Deployment — Complete

• Distributed cloud and hybrid infrastructure
• Multiple validator nodes with automatic TLS
• Live endpoints at rpc/api/faucet/mcp/a2a.tenzro.network
• Genesis block with 1B TNZO supply
• Automated builds and continuous deployment

Phase 7: Economics and Settlement — Complete

• On-chain token supply tracking with persistent state
• Stake-weighted governance voting
• Multisig treasury withdrawals
• Micropayment channel state persistence
• Dispute resolution for payment channels
• Liquid staking with rebasing exchange rate

Phase 8: Bridge and Interoperability — In Progress

• LayerZero adapter connected to EVM chains
• Bridge message replay protection
• Cross-chain transfer monitoring
• Bridge message signature verification

Phase 9: AI Infrastructure — In Progress

• Model downloading with integrity verification
• Inference routing to model providers
• Agent messaging over network transport
• Chat interface for inference interaction

Phase 10: Client Applications — In Progress

• CLI commands wired to node RPC
• Desktop app connected to node
• Local wallet authentication
• SDK integration with live node endpoints
• Configuration loading from files

Phase 11: Production Hardening — Planned

• Comprehensive test suite
• CI/CD pipeline
• Metrics collection and dashboards
• Structured logging
• Graceful shutdown handling
• External security audit
• Performance benchmarks
• Operator documentation

9. Testnet Deployment

The Tenzro testnet is live on distributed cloud and hybrid infrastructure with multiple validator nodes and dedicated RPC endpoints, secured with automatic TLS certificates.

9.1 Testnet Endpoints

9.2 Testnet Configuration

9.3 Getting Started

To interact with the testnet:

1. Request testnet TNZO tokens from the faucet by submitting your address to POST https://api.tenzro.network/api/faucet
2. Configure your wallet or development tool to use the JSON-RPC endpoint at https://rpc.tenzro.network
3. Use the Tenzro CLI (tenzro-cli) or desktop app (tenzro-desktop) to manage identities, wallets, and transactions
4. Access the MCP server for AI agent integration at https://mcp.tenzro.network/mcp
5. Discover agent capabilities via the A2A Agent Card at https://a2a.tenzro.network/.well-known/agent.json

10. Conclusion

Tenzro Protocol represents a fundamental rethinking of blockchain infrastructure for the AI age. By combining hardware-rooted trust (TEEs), cryptographic verifiability (ZK proofs), economic coordination (TNZO staking and fees), and agent-first design (TDIP identity, A2A protocol), Tenzro enables a new class of applications where autonomous agents can securely access intelligence, custody assets, execute transactions, and coordinate with each other and with humans.

The protocol's two-tier fee structure aligns incentives across all participants: validators earn gas fees for securing the ledger, model providers earn inference fees for serving intelligence, TEE providers earn service fees for providing security, and the network treasury collects commissions to fund ongoing development. TNZO stakers receive a portion of network revenue, creating a sustainable economic flywheel.

With a live testnet, full multi-VM execution support, and comprehensive identity and payment protocol implementations, Tenzro is progressing toward mainnet launch in late 2026. The roadmap prioritizes production hardening, cross-chain bridge integration, and decentralized AI marketplace activation before public launch.

We invite developers, validators, model providers, and AI agents to participate in the testnet, provide feedback, and help build the infrastructure for an AI-native economy.

References

• Tenzro Network: Decentralized AI Infrastructure
• Tenzro Ledger: L1 Settlement Layer
• TEE Security: Hardware-Rooted Trust
• Zero-Knowledge Proofs: Verifiable Computation
• TDIP: Decentralized Identity Protocol
• Payment Protocols: MPP, x402, and Tempo
• TNZO Governance: Token Economics and Governance
• GitHub Repository