ZIP-0015: Zoo L2 Chain Architecture

Abstract

Zoo Network operates as an L2 chain on the Lux Network, meaning it is validated by the Lux primary network validators rather than maintaining its own independent validator set. This architecture provides Zoo with inherited security from the primary network while reducing operational complexity and enabling faster ecosystem growth.

Motivation

Zoo Labs Foundation chose the L2 model for several strategic reasons:

Lower barrier to entry: No need to bootstrap a separate validator set
Inherited security: Benefits from Lux primary network's Byzantine fault tolerance
Focus on mission: Conservation and AI research, not validator operations
Ecosystem alignment: Deeper integration with Lux Network
Faster iteration: Quicker upgrades without validator coordination

Specification

Chain Configuration

chain:
  name: Zoo
  type: L2
  chainId: 200200
  ticker: ZOO
  
validation:
  type: primary-network
  inheritSecurity: true
  
consensus:
  engine: snowman
  parameters: inherit

Genesis Configuration

{
  "config": {
    "chainId": 200200,
    "chainType": "L2",
    "validatorSet": {
      "type": "primary-network",
      "inheritSecurity": true
    }
  },
  "timestamp": "0x0",
  "gasLimit": "0xb71b00",
  "alloc": {
    "0x9011E888251AB053B7bD1cdB598Db4f9DEd94714": {
      "balance": "0x..."
    }
  }
}

Network Endpoints

Network	Chain ID	RPC Endpoint
Mainnet	200200	`https://api.zoo.network/ext/bc/zoo/rpc`
Testnet	200201	`https://testnet.zoo.network/ext/bc/zootest/rpc`

Validation Model

As an L2, Zoo transactions are validated by Lux primary network validators:

User Transaction → Zoo Chain → Primary Network Validators → Consensus → Finality

Benefits:

No separate staking required for Zoo validators
Immediate security inheritance (80%+ BFT)
Shared infrastructure with Lux ecosystem
Cross-chain Warp messaging built-in

Tradeoffs:

Less sovereignty over consensus parameters
Dependent on primary network health
Shared block space with other L2s

Cross-Chain Communication

Zoo uses Warp messaging for cross-chain operations:

// Send message to Hanzo (L1)
IWarpMessenger(WARP_ADDRESS).sendMessage(
    HANZO_CHAIN_ID,
    abi.encode(payload)
);

// Receive message from C-Chain
function receiveWarpMessage(bytes calldata message) external {
    require(msg.sender == WARP_ADDRESS);
    // Process cross-chain message
}

Upgrade Path

Zoo can upgrade to L1 (sovereign) status if needed:

# Future: Migrate to L1 with own validators
lux chain upgrade zoo --type l1 --validators validator-set.json

This would require:

Establishing independent validator set
Migrating staking economics
Deploying validator infrastructure
Coordinating network upgrade

Rationale

Why L2 over L1?

Factor	L1 (Sovereign)	L2 (Zoo's Choice)
Validator ops	Required	Not required
Security bootstrap	Months	Immediate
Focus	Infrastructure	Mission (conservation)
Upgrade speed	Slow (validator coord)	Fast
Cross-chain	Manual setup	Built-in

Comparison with Hanzo

Zoo and Hanzo represent the two chain models:

Chain	Type	Validators	Use Case
Zoo	L2	Primary network	Conservation, community AI
Hanzo	L1	Own set	AI compute, sovereignty

This allows Lux ecosystem to demonstrate and optimize both approaches.

Security Considerations

Inherited Security

Zoo inherits Lux primary network security:

80%+ Byzantine fault tolerance
Economic security from LUX staking
Battle-tested consensus (Snow family)

Chain-Specific Security

Zoo implements additional security measures:

Conservation fund multisig (3-of-5)
AI model attestation via Z-Chain
Cross-chain message validation

Implementation

Deployment

# Deploy Zoo to mainnet (L2 mode)
lux chain deploy zoo --mainnet --type l2

# Verify chain type
lux chain info zoo
# Output: Type: L2 (Primary Network Validated)

Zoo L2 Chain Architecture