# EZ Labs: Unified Architecture Specification
**Document Version:** 1.0.0
**Authors:** EZ Labs Core Architecture & Engineering Team
**Status:** Approved / Specification Benchmark
**Date:** May 24, 2026
---
## 0. Executive Summary
### 0.1 Paradigm Shift
Modern decentralized infrastructure suffers from structural fragmentation across three core dimensions: execution context, state privacy, and economic finality. These bottlenecks are amplified when processing autonomous agent workloads, which require deterministic, non-custodial, privacy-preserving, and trust-minimized coordination patterns.
EZ Labs resolves these structural issues by introducing a verifiable, agent-native compute and liquidity ecosystem. This architecture eliminates the trade-offs between zero-knowledge verification, high-throughput execution, and state privacy.
```
+-----------------------------------------------------------------------+
| EZ LABS UTILITY PRODUCTION STACK |
+-----------------------------------------------------------------------+
| Identity & Culture: | EZ Runner & EZVERSE |
+---------------------------+-------------------------------------------+
| Liquidity & Execution: | ZENDEX (Base-Settled AMM w/ ZEN Privacy) |
+---------------------------+-------------------------------------------+
| x402 Router Module: | EZ Path (Deterministic Challenge Engine) |
+---------------------------+-------------------------------------------+
| Core Middleware Fabric: | EZ Chain (Verifiable Multi-Chain Core) |
+---------------------------+-------------------------------------------+
| Primitives & Foundation: | Base (Settlement) | ZEN (Privacy) |
| | NOIR (ZK Compute) | x402 (Payments) |
+-----------------------------------------------------------------------+
```
### 0.2 The EZ Chain Middleware Thesis
The foundational core of the EZ Labs ecosystem is **EZ Chain**, the definitive long-term middleware thesis of the network. EZ Chain operates as a multi-chain, verifiable compute fabric that unifies:
* **Routing:** Dynamic, privacy-preserving path selection across heterogeneous state layers.
* **Identity:** Cryptographic agentic and human reputation schemas that transcend individual network boundaries.
* **Execution:** Highly deterministic, off-chain state transitions bound by zero-knowledge correctness proofs.
* **Privacy:** Complete transaction, intent, and balance obfuscation utilizing Horizen ZEN primitives.
* **Payments:** Machine-to-machine, synchronous fee capture using advanced challenge-response architectures.
EZ Chain acts as the decentralized nervous system, unbundling execution from state settlement while ensuring that every state transition is cryptographically verifiable before being committed to underlying base layers.
### 0.3 Delineation of Ecosystem Components
To maintain structural clarity across engineering and deployment domains, components are strictly organized into functional layers:
1. **EZ Chain (The Middleware Spine):** The long-term proof-of-human-agentic and verifiable multi-chain compute fabric. It orchestrates routing, zero-knowledge verification, and cross-chain messaging.
2. **EZ Path (The Router Module):** A production-grade, highly specialized **x402 protocol implementation** operating *inside* the EZ Chain stack. It serves as an agent-native HTTP router and cryptographic payment challenge engine, transforming standard request/response cycles into monetizable agent pathways. It is an essential production utility, not the underlying middleware itself.
3. **ZENDEX (The Liquidity Layer):** A high-performance, Base-settled Automated Market Maker (AMM) leveraging a ZK Multi-Engine architecture, utilizing Horizen ZEN for transactional privacy and NOIR for verifiable transaction routing.
4. **Horizen ZEN (The Privacy & Identity Layer):** The source of state obfuscation, private intents, stealth user experiences, and multi-chain privacy primitives.
5. **NOIR (The Verifiable Compute Layer):** The Domain-Specific Language (DSL) and proving system used to compile, generate, and verify zero-knowledge proofs across all middleware operations, routing logic, and AMM state changes.
6. **Base (The Settlement Layer):** The low-latency, high-security Layer 2 execution environment serving as the global availability and financial settlement layer for ecosystem capital.
7. **x402 (The Agent Payment Fabric):** An application-layer standard enabling autonomous agents to programmatically negotiate, challenge, and settle micro-payments for compute resources.
8. **EZ Runner & EZVERSE (The Culture and Identity Layer):** On-chain game and non-fungible identity primitives that map human and agentic activity to immutable reputation metrics, governing ecosystem access.
---
## 1. System Tree
The following hierarchical taxonomy illustrates the precise structural relationships, dependencies, and execution vectors across the unified EZ Labs architecture.
```
EZ Labs Ecosystem
├── 1. Verifiable Middleware Fabric (EZ Chain Core)
│ ├── Thesis: Long-term proof of human-agentic coordination & multi-chain state orchestration
│ ├── Cryptographic Compilers: NOIR Zero-Knowledge Circuits (UltraPlonk/Honk verification)
│ ├── Settlement Pipeline: Base Layer-2 Rollup (EVM state-root commitment)
│ └── Privacy Infrastructure: Horizen ZEN Mainchain (Stealth addresses & shielded transaction vectors)
│
├── 2. EZ Path (x402 Production Implementation Layer)
│ ├── Functional Type: Sub-system Module operating within EZ Chain
│ ├── Core Routing: Agent-Native HTTP Router with deterministic URI path mapping
│ ├── Economic Engine: x402 payment challenge engine (Status 402 Payment Required handlers)
│ └── State Model: Deterministic Request ──> Cryptographic Challenge ──> Signed Response Pipeline
│
├── 3. ZENDEX (Ecosystem Liquidity Engine)
│ ├── Execution Model: Base-settled AMM (Automated Market Maker)
│ ├── Privacy Extension: Shielded pool bridging via Horizen ZEN
│ └── Verification Model: NOIR-driven verifiable routing and zero-overhead execution proofs
│
└── 4. EZ Labs Utility Production Stack (Integrated Runtime)
├── Horizen ZEN ──> Core Privacy + Cryptographic Zero-Knowledge Identity Primitives
├── Base ──> Low-latency Transaction Execution + Global Economic Settlement
├── NOIR ──> Verifiable Compute Circuits + Deterministic State Transition Proofs
├── x402 ──> Machine-to-Machine Micro-payments for Autonomous Agents
├── EZ Chain ──> The Backbone Middleware Fabric & Global State Coordination Layer
├── EZ Path ──> x402-Powered Router Module operating inside the EZ Chain stack
├── ZENDEX ──> Liquidity Aggregation, Single-Slot Settlement, & Asset Exchange
└── EZ Runner/V ──> Human/Agent Identity Mapping, Reputation Scoring, & Cultural Projections
```
---
## 2. Layered Architecture (Unified & Detailed)
The EZ Labs ecosystem is built as a modular, five-tier architecture. Each layer exposes clean cryptographic and economic interfaces to adjacent layers, ensuring decoupling and fault isolation.
```
+-----------------------------------------------------------------------+
| LAYER 4: COMPUTE & IDENTITY (EZ Runner & EZVERSE) |
+-----------------------------------------------------------------------+
│
▼
+-----------------------------------------------------------------------+
| LAYER 3: LIQUIDITY & EXECUTION (ZENDEX AMM) |
+-----------------------------------------------------------------------+
│
▼
+-----------------------------------------------------------------------+
| LAYER 2: EZ PATH (x402 Router & Challenge Module) |
+-----------------------------------------------------------------------+
│
▼
+-----------------------------------------------------------------------+
| LAYER 1: EZ CHAIN (Verifiable Middleware Backbone) |
+-----------------------------------------------------------------------+
│
▼
+-----------------------------------------------------------------------+
| LAYER 0: FOUNDATIONS (Base, ZEN, NOIR, x402) |
+-----------------------------------------------------------------------+
```
### 2.1 Layer 0 — Foundations
The foundational primitives establish the cryptographic, economic, and execution environments upon which the entire ecosystem relies.
#### Base (Execution & Settlement)
* **Role:** Layer 2 Optimistic Rollup inheriting Ethereum mainnet security.
* **Metrics:** Sub-second block times, low gas overhead via EIP-4844 blob spaces.
* **Functionality:** Serves as the immutable settlement registry for ZENDEX liquidity balances, EZ Chain proof-verification contracts, and x402 financial finality.
#### Horizen ZEN (Privacy & Identity)
* **Role:** Decentralized privacy network supporting secure zero-knowledge state transitions.
* **Primitives:** UTXO-based shielded pools, stealth address generation, and zero-knowledge identity assertions.
* **Functionality:** Obfuscates agent identities, payload routing destinations, and liquidity positions, ensuring a competitive advantage against MEV (Maximal Extractable Value) front-running.
#### NOIR (Verifiable Compute)
* **Role:** Zero-knowledge domain-specific language (DSL) based on the Barretenberg proving system.
* **Compilation:** Compiles deterministic Rust-like syntax into Abstract Circuit Relations (ACR) and Arithmetic Circuit Complexity (A4C) representations.
* **Functionality:** Generates ultra-optimized SNARK/STARK proofs verifying that off-chain middleware, agent calculations, and router pathways were executed accurately according to network parameters.
#### x402 (Agent-Native Payments)
* **Role:** Programmatic protocol specification redefining HTTP Status `402 Payment Required`.
* **Primitives:** Ephemeral micro-payment escrow contracts, time-locked payment challenges, and deterministic fee calculation formulas.
* **Functionality:** Enables non-human autonomous actors to programmatically discover endpoints, negotiate price per kilobyte of compute, execute cryptographic handshakes, and unlock access to network resources without manual intervention.
---
### 2.2 Layer 1 — EZ Chain (Core Middleware Thesis)
EZ Chain is the definitive architectural spinal cord of the EZ Labs ecosystem. It decouples complex compute and coordination from structural layer settlement.
```
+-----------------------------------+
| EZ CHAIN CORE MIDDLEWARE |
+-----------------------------------+
/ | | / | | ▼ ▼ ▼ ▼
[Routing] [Identity] [Execution] [Privacy]
```
#### Core Architectural Mandate
EZ Chain solves the "verifiable coordination problem." As an abstracted multi-chain middleware fabric, it acts as an overlay network spanning Base and Horizen. It intercepts agent actions, cross-chain intents, and computational queries, processing them off-chain inside a distributed, verifiable environment before committing compressed state roots to Layer 0.
#### Core Sub-systems and Responsibilities
1. **Verifiable Middleware Execution:** Runs a deterministic state machine where every input, state change, and output is bound to a generated NOIR proof.
2. **Cross-Chain Compute Orchestration:** Manages state queries across heterogeneous environments (EVM on Base, UTXO on Horizen) safely, avoiding double-spend risks or state re-ordering attacks.
3. **NOIR-Based Proof Generation:** Batches off-chain interactions and executes them through pre-compiled ZK circuits. The output is a highly compressed proof verifiable by gas-optimized on-chain smart contracts.
4. **Privacy-Aware Routing:** Leverages Horizen ZEN stealth address systems to route agent commands without leaking metadata like origin IPs, wallet addresses, or intent payloads.
5. **Deterministic Agent Workflows:** Guarantees that if an agent inputs state $S_t$ with transaction $Tx_n$, the resulting state $S_{t+1}$ is strictly deterministic and verifiable by any external auditor.
---
### 2.3 Layer 2 — EZ Path (x402 Implementation Layer)
EZ Path is a production utility operating *within* the EZ Chain fabric. It is the network's primary agent interface, implementing the x402 protocol specification.
```
Agent Request ──> [EZ Path Router] ──> [402 Challenge Issued] ──> [Payment Settled] ──> [Resource Unlocked]
```
#### Sub-system Distinctions
EZ Path is **not** the underlying middleware; it is a highly specialized networking application layer that runs inside EZ Chain. It translates raw HTTP communication into verifiable, monetized agent pathways.
#### Operational Mechanism & Lifecycle
1. **Ingress Routing:** An agent transmits an HTTP POST request targeting a specific computational, analytical, or liquidity resource within the network.
2. **Challenge Generation:** EZ Path intercepts the packet, parses the metadata, and returns an `HTTP 402 Payment Required` response containing a unique cryptographic challenge payload, an escrow smart contract address, and a price metric ($P_{c}$).
3. **Payment Verification:** The agent signs an off-chain micro-payment or provides an atomic pre-image proof that satisfies the condition on Base or Horizen ZEN.
4. **Egress Execution:** Upon validating the payment proof, EZ Path releases a deterministic routing token, forcing the EZ Chain core to execute the underlying target workflow and safely return the signed response to the agent.
---
### 2.4 Layer 3 — Liquidity & Execution (ZENDEX)
ZENDEX is the financial and liquidity engine of EZ Labs, optimizing capital efficiency for both human participants and autonomous agents.
#### Architecture
ZENDEX utilizes a **ZK Multi-Engine AMM architecture**. Unlike legacy AMMs that require public state updates for every swap, ZENDEX offloads routing calculations, pool math, and slippage determination into a zero-knowledge execution environment.
```
+-----------------------------------+
| ZENDEX LIQUIDITY LAYER |
+-----------------------------------+
/ / ▼ ▼
[Base Settlement] [ZEN Shielded Pools]
│ │
▼ ▼
(Capital Efficiency) (MEV Protection)
```
#### Multi-Chain Interaction Models
* **Base Settlement:** All liquidity pool configurations, core token pair vaults, and LP token shares are tracked and secured via EVM smart contracts deployed on Base. This ensures immediate accessibility and composability with the broader DeFi ecosystem.
* **Horizen ZEN Shielding:** Traders can deposit assets into Base vaults and execute swaps through a shielded relay that leverages Horizen ZEN. The execution path, size, and destination wallet are hidden within a zero-knowledge proof, completely neutralizing front-running, sandwich attacks, and informational leakage.
* **Verifiable Proving Framework:** Using NOIR circuits, ZENDEX generates proof of correct trade execution ($E_{zk}$). This mathematically proves that the constant product formula ($x \cdot y = k$) or concentrated liquidity constraints were precisely maintained, without revealing the underlying swap parameters to public mempools.
---
### 2.5 Layer 4 — Compute & Identity (EZ Runner & EZVERSE)
The outermost layer bridges system functionality with human coordination, network culture, and long-term reputation.
#### EZ Runner (The Behavioral Proving Ground)
* **Mechanic:** A continuous, highly competitive on-chain game and execution framework that requires real-time proof-of-interaction.
* **Engine Integration:** User interactions are cryptographically linked to their primary identity keys via EZ Chain.
* **Reputation Engine:** Translates raw activity metrics (e.g., latency performance, puzzle completion, computational contribution) into an immutable, on-chain **Ecosystem Reputation Score ($R_{eco}$)**. Higher reputation tiers grant users and agents preferential gas fee discounts, exclusive compute access, and prioritize their routing within EZ Path.
#### EZVERSE (The Cultural and Identity Canvas)
* **Mechanic:** A modular, non-fungible identity layer that establishes cross-product utility.
* **Primitives:** Dynamic NFTs (dNFTs) whose metadata scales based on tracking data from Layer 1 and Layer 3.
* **Ecosystem Utility:** Operates as a visual and programmable representation of a user's or agent’s rights across the ecosystem. It acts as an access passport, a cryptographic profile for private messaging on Horizen ZEN, and a multi-token staking amplifier inside ZENDEX.
---
## 3. Comprehensive System Flow
The lifecycle of an agent interaction demonstrates how an abstract intent moves across the architecture, transforming from an unverified network request into an immutable, settled, and privacy-preserved state update.
```
[ Autonomous Agent ]
│
│ 1. Transmits raw HTTP request containing compute intent payload
▼
+─────────────────────────────────────────────────────────────────────────+
│ EZ PATH (x402 Router Module) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Intercepts packet & analyzes content constraints │
│ - Generates HTTP 402 challenge & computes fee metrics │
│ - Validates agent-signed cryptographic payment pre-image │
+─────────────────────────────────────────────────────────────────────────+
│
│ 2. Routes authorized, deterministic payload wrapper
▼
+─────────────────────────────────────────────────────────────────────────+
│ EZ CHAIN (Core Middleware Fabric) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Accepts deterministic workflow request │
│ - Resolves agent cross-chain identity & access permissions │
│ - Bundles compute request into verifiable execution queue │
+─────────────────────────────────────────────────────────────────────────+
│
│ 3. Queries and dispatches required execution assets
▼
+─────────────────────────────────────────────────────────────────────────+
│ ZENDEX (Execution & Liquidity Layer) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Dispatches capital routing calculations across AMM pair vaults │
│ - Processes multi-hop swap steps inside private execution sandbox │
+─────────────────────────────────────────────────────────────────────────+
│
│ 4. Submits net financial state modifications
▼
+─────────────────────────────────────────────────────────────────────────+
│ BASE (Global Settlement Layer) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Updates core token vault balances and smart contract registries │
│ - Records state root anchor of the transaction block │
+─────────────────────────────────────────────────────────────────────────+
│
│ 5. Initiates state obfuscation and stealth processing
▼
+─────────────────────────────────────────────────────────────────────────+
│ HORIZEN ZEN (Privacy & Stealth UX Layer) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Generates stealth address vectors for output distribution │
│ - Conceals agent identity and balance transfers via UTXO pools │
+─────────────────────────────────────────────────────────────────────────+
│
│ 6. Generates structural verification matrix
▼
+─────────────────────────────────────────────────────────────────────────+
│ NOIR (Verifiable Proof Generation Layer) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Compiles execution path correctness trace into an ACR matrix │
│ - Emits ZK proof verifying complete execution honesty │
+─────────────────────────────────────────────────────────────────────────+
│
│ 7. Commits cryptographic verification data back to identity registers
▼
+─────────────────────────────────────────────────────────────────────────+
│ IDENTITY LAYERS (EZ Runner / EZVERSE) │
│ ───────────────────────────────────────────────────────────────────────│
│ - Increments behavioral reputation metrics ($R_{eco}$) │
│ - Updates dynamic NFT metadata matrix with new system credentials │
+─────────────────────────────────────────────────────────────────────────+
```
---
## 4. Expanded Technical & Conceptual Model
### 4.1 EZ Chain as the Middleware Thesis
The underlying architecture of EZ Chain shifts blockchain infrastructure from a focus on execution speed to a focus on **verifiable correctness**. It acknowledges that while state settlement must remain on highly secure, global consensus layers like Base, the computation required for autonomous agents cannot be efficiently run on-chain.
EZ Chain acts as a specialized off-chain coordination engine. By leveraging distributed validator structures, it samples execution traces and converts them into explicit mathematical arguments.
The middleware fabric ensures that cross-chain communications are completely trustless. For instance, when an agent requests a privacy-shielded asset trade on Horizen ZEN to settle within an EVM vault on Base, EZ Chain coordinates this interaction seamlessly. It prevents race conditions and front-running by binding the state transitions of both networks into a unified cryptographic block.
---
### 4.2 EZ Path’s Technical Role
EZ Path operates at the network's boundaries, acting as an edge-routing layer. It translates traditional web protocols (HTTP/REST, WebSockets) into web3 cryptographic execution patterns.
```
HTTP Context Cryptographic Web3 Context
+───────────────────────────+ +───────────────────────────+
│ POST /compute/predict │ ───────────> │ Parse Path Constraints │
+───────────────────────────+ +───────────────────────────+
│
▼
+───────────────────────────+ +───────────────────────────+
│ HTTP 402 Challenge │ <─────────── │ Generate x402 Challenge │
+───────────────────────────+ +───────────────────────────+
```
Inside this module, an incoming packet is validated against strict deterministic guidelines:
$$ ext{Sign}( ext{Payload}) \oplus ext{Nonce} \equiv ext{Challenge}_{ ext{target}}$$
By handling these challenges at the edge, EZ Path shields the core middleware fabric from DDoS attacks and resource exhaustion. This ensures that every computational cycle allocated by the EZ Chain backbone is pre-funded and authorized by a valid agent signature.
---
### 4.3 ZENDEX’s Mechanics
ZENDEX adapts traditional automated market making for automated algorithmic traders. Legacy AMMs are optimized for asynchronous human interactions through graphic user interfaces. ZENDEX is optimized for automated high-frequency agents, algorithmic solvers, and programmatic cross-chain rebalancing.
The platform uses a **Single-Slot Settlement structure**. When multi-hop routes are calculated (e.g., $ ext{Token A}
ightarrow ext{Token B}
ightarrow ext{Token C}$), the intermediate token balances are held within transient memory slots. Only the net final balances are written to the permanent Base state.
This reduction in storage access lowered execution overhead by more than 70%. Additionally, because these paths are checked using NOIR circuits before execution, agents can guarantee optimal slippage and exact pricing before broadcasting their transactions.
---
### 4.4 Horizen ZEN’s Privacy Vectors
Ecosystem state privacy is managed through Horizen ZEN's cryptographic infrastructure. Rather than relying on easily linkable public key balances, ZEN uses a dual-token, shielded-loop mechanism.
When an agent enters an intent into the system, EZ Chain generates an ephemeral stealth address key:
$$K_{ ext{stealth}} = H(r \cdot Q_{ ext{view}}) \cdot G + P_{ ext{spend}}$$
Where:
* $r$ is an ephemeral scalar generated by the sender.
* $Q_{ ext{view}}$ is the receiver's public view key.
* $G$ is the base point of the elliptic curve.
* $P_{ ext{spend}}$ is the receiver's public spend key.
* $H$ is a secure cryptographic hash function.
This architecture ensures that outside observers cannot link incoming requests to outgoing executions, creating a secure environment for enterprise operations and proprietary agent strategies.
---
### 4.5 NOIR’s Mathematical Verification
Every state transition within the EZ Labs stack is verified using Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge (ZK-SNARKs), compiled through NOIR.
The system translates execution workflows into an exact set of polynomial constraints. For example, verifying that an agent possesses sufficient reputation ($R_{eco}$) and has deposited the correct challenge fee ($F_c$) is represented as:
$$\mathcal{C}( ec{x}, ec{w}) = 0$$
Where:
* $ ec{x}$ represents the public inputs (block hashes, commitment roots, transaction identifiers).
* $ ec{w}$ represents the private witnesses (agent identity signatures, routing vectors, payload data).
The Barretenberg proving system processes these constraints to output a highly compressed proof file ($P_{zk}$), typically under 1 kilobyte in size. This proof is quickly validated on Base using optimized elliptic curve pairing operations (`ecPairing`).
---
### 4.6 x402’s Economic Rationale
Traditional web payment methods (API keys, credit cards) fail when applied to autonomous AI agents due to identity requirements and high settlement costs. The x402 standard provides a native economic layer for autonomous machine interactions.
```
Agent Egress ──> [Check Local Escrow] ──> [Lock Micropayment] ──> [Compute Delivered] ──> [Release Fee]
```
By standardizing the response format for `HTTP 402 Payment Required`, the protocol enables agents to dynamically discover endpoints and pay for services autonomously.
Fees are calculated programmatically based on bandwidth, compute complexity, and circuit size. This creates an efficient, real-time market for zero-knowledge computation and routing resources across the network.
---
## 5. Final Unified Thesis
The EZ Labs ecosystem establishes a scalable architecture for the next era of verifiable, agent-native applications.
By separating core responsibilities—assigning **settlement** to Base, **privacy** to Horizen ZEN, **verification proofs** to NOIR, **programmatic payments** to x402, and **liquidity** to ZENDEX—the ecosystem avoids the scalability and performance bottlenecks that limit legacy single-chain platforms.
```
+───────────────────────────────────────────────────────────────────────────+
| EZ LABS VERIFIABLE UTILITY PRODUCTION STACK |
+───────────────────────────────────────────────────────────────────────────+
│ │
│ EZ Chain serves as the multi-chain compute and middleware core, │
│ unifying routing, identity, execution, and privacy across platforms. │
│ │
│ EZ Path operates within this fabric as a dedicated x402 routing │
│ and challenge engine, enabling secure agent micro-payments. │
│ │
│ Together, these components provide a deterministic environment │
│ designed for secure, autonomous machine-to-machine coordination. │
│ │
+───────────────────────────────────────────────────────────────────────────+
```
This coordinated architecture provides the foundations for an autonomous, self-sustaining digital economy. Within this framework, compute resources are mathematically verified, data privacy is preserved by default, and economic interactions are managed entirely by programmatic, agent-native protocols.
---
**End of Specification.**
