Skip to main content

Infrastructure Overview

Nexis Appchain is a production-grade Layer 3 blockchain built on the OP Stack, specifically optimized for AI agent coordination and verifiable inference workloads. This document provides a comprehensive overview of the technical architecture and design decisions.

Architecture Summary

Layer 3 on Base

Built as an OP Stack L3 on top of Base Sepolia (L2), inheriting Ethereum security

2-Second Blocks

High-throughput block production for sub-second transaction finality

Fault Proofs

Permissionless validation with 73-step bisection game for security

EVM Compatible

Full Ethereum compatibility - use existing tools and contracts

Network Specifications

OP Stack Layer Architecture

Layer Responsibilities

L1 (Ethereum Mainnet)
  • Ultimate source of truth and security
  • Stores Base L2 state commitments
  • Hosts Base L2 fraud proof contracts
L2 (Base Sepolia)
  • Settles Nexis L3 transactions
  • Stores L3 batched transaction data
  • Provides data availability guarantees
  • Runs fault proof system for L3
L3 (Nexis Appchain)
  • Executes AI agent transactions
  • Produces blocks every 2 seconds
  • Optimized for high-frequency operations
  • Custom smart contracts for agent coordination

Core Components

1. op-geth (Execution Layer)

The execution layer is a modified version of go-ethereum (geth) with OP Stack enhancements:
Key Features:
  • EVM Execution: Processes smart contract calls and state transitions
  • Transaction Pool: Manages pending transactions from users and agents
  • State Database: Stores account balances, contract storage, and code
  • JSON-RPC: Exposes Ethereum-compatible APIs for wallets and dApps
  • Archive Mode: Optional full historical state for analytics

2. op-node (Consensus Layer)

The consensus layer derives L3 blocks from L2 data and manages the rollup protocol:
Responsibilities:
  • Block Derivation: Reconstructs L3 blocks from L2 data
  • State Synchronization: Keeps execution layer in sync
  • P2P Networking: Propagates blocks to other nodes
  • Rollup Protocol: Implements OP Stack state transition logic

3. Sequencer

The sequencer is the privileged node that orders and batches transactions: Sequencer Workflow:
  1. Receive transactions from users via JSON-RPC
  2. Order transactions into a canonical sequence
  3. Execute transactions through op-geth
  4. Produce blocks every 2 seconds
  5. Broadcast blocks to all nodes via P2P
  6. Batch transactions for L2 submission
Sequencer Operation

4. Batcher

The batcher aggregates L3 transactions and submits them to Base L2 for data availability:
Batching Parameters:
  • Channel Duration: 30 L2 blocks (~1 minute)
  • Max Batch Size: 128 KB per transaction
  • Compression: Zlib for data efficiency
  • Submission Frequency: Every ~60 seconds or when batch size reached

5. Proposer

The proposer submits L3 state root commitments to Base L2 for finality:
Proposal Parameters:
  • Frequency: Every 120 L3 blocks (~4 minutes)
  • Bond Requirement: 1 ETH on Base Sepolia
  • Challenge Period: 7 days for fault proofs
  • Finalization: After challenge period with no successful disputes

Data Flow

Transaction Lifecycle

State Derivation

Any node can independently derive the canonical L3 chain from L2 data:

Security Model

Trust Assumptions

  1. Liveness: Sequencer must be available (centralized currently, decentralizing soon)
  2. Data Availability: Base L2 must store and serve batch data
  3. Fault Proofs: At least one honest verifier must challenge invalid proposals
  4. L1 Security: Ethereum mainnet remains secure and censorship-resistant

Security Guarantees

  • State Validity: Enforced by fault proofs (anyone can challenge invalid state)
  • Data Availability: Guaranteed by Base L2 (inherits from Ethereum)
  • Censorship Resistance: Users can force inclusion via L2 contracts
  • Finality: Economic finality after L2 confirmation, absolute after L1 finalization

Fault Proof System

Nexis uses the OP Stack fault proof game for security:
See Fault Proofs for detailed mechanics.

Performance Characteristics

Throughput

Latency

Cost Analysis

Network Topology

Comparison to Other Chains

Roadmap

1

Phase 1: Testnet (Current)

Fully functional testnet with centralized sequencer
2

Phase 2: Mainnet Launch (Q2 2025)

Production deployment with decentralized validation
3

Phase 3: Decentralized Sequencing (Q3 2025)

Implement shared sequencing or leader election
4

Phase 4: ZK Proofs (2026)

Transition to ZK fault proofs for faster finality

Learn More

Consensus Mechanism

Deep dive into block derivation and sequencing

Fault Proofs

Understand the security model and dispute resolution

Run a Node

Participate in the network as a validator

RPC Infrastructure

Learn about the RPC architecture and endpoints

Want to contribute to infrastructure? We’re looking for node operators, validator runners, and infrastructure developers. Join our Discord #infrastructure channel.