Skip to main content

​
Overview

Paxeer Network is a high-performance EVM-equivalent blockchain designed for scalability, security, and developer experience.

​
Core Components

Execution Layer

EVM-compatible execution environment

Consensus Layer

Block production and validation

Networking Layer

P2P communication and data propagation

Storage Layer

State and transaction data storage

​
Architecture Diagram

​
Execution Layer

The execution layer is responsible for processing transactions and maintaining state.

​
Components

Role: Orders and executes transactionsResponsibilities:
  • Select transactions from mempool
  • Order by priority fee
  • Create blocks (~2 second intervals)
  • Execute transactions via EVM
  • Update state
Address: Sequencer fee vault at 0x4200000000000000000000000000000000000011
Role: Execute smart contract bytecodeSpecifications:
  • Fully EVM equivalent
  • Same opcodes as Ethereum
  • Same gas costs
  • Same execution semantics
Version: Compatible with latest Ethereum upgrades
Role: Manage blockchain stateFunctions:
  • Store account balances
  • Store contract code
  • Store contract storage
  • Compute state roots
  • Provide state access

​
Block Production

​
Block Structure

{
  "number": 1234567,
  "hash": "0x...",
  "parentHash": "0x...",
  "stateRoot": "0x...",
  "transactionsRoot": "0x...",
  "receiptsRoot": "0x...",
  "timestamp": 1699564800,
  "gasLimit": 30000000,
  "gasUsed": 15234567,
  "baseFeePerGas": 1000000000,
  "miner": "0x...",
  "transactions": [...]
}

​
Block Time

  • Target: 2 seconds
  • Range: 1-3 seconds under normal conditions
  • Deterministic: Blocks produced at regular intervals

​
Transaction Processing

1

Validation

Transaction is validated:
  • Signature verification
  • Nonce check
  • Balance verification
  • Gas limit validation
2

Mempool

Valid transactions enter the mempool
  • Ordered by effective gas price
  • Duplicate nonce handling
  • Eviction policy for full mempool
3

Selection

Sequencer selects transactions:
  • Highest fee first
  • Nonce order respected
  • Gas limit constraints
4

Execution

EVM executes transactions:
  • State changes applied
  • Events emitted
  • Gas consumed
  • Result determined (success/fail)
5

Inclusion

Transaction added to block:
  • Receipt generated
  • State root updated
  • Block propagated

​
State Management

​
State Trie Structure

Paxeer Network uses a Merkle Patricia Trie for state storage: 
State Root
├── Account 0x1111...
│   ├── Balance: 100 PAX
│   ├── Nonce: 5
│   ├── Code Hash: 0x...
│   └── Storage Root
│       ├── Slot 0: value1
│       └── Slot 1: value2
├── Account 0x2222...
│   ├── Balance: 50 PAX
│   └── Nonce: 2
└── ...

​
Storage Slots

contract Example {
    uint256 public slot0;           // Storage slot 0
    mapping(address => uint256) public balances; // Slot 1 base
    
    // balances[addr] stored at keccak256(addr, 1)
}

​
Networking

​
P2P Network

  • Protocol: DevP2P (Ethereum’s networking protocol)
  • Discovery: Discv4/Discv5 for peer discovery
  • Bootnodes: Hardcoded initial peers
  • Max Peers: Configurable (default: 50)

​
Block Propagation

Propagation Time: < 1 second for full network

​
Data Storage

​
Database Structure

datadir/
├── chaindata/         # Blockchain and state data
│   ├── ancient/      # Old blocks (compressed)
│   └── current/      # Recent blocks
├── lightchaindata/   # Light client data
├── nodes/            # P2P network data
└── keystore/         # Account keys (if any)

​
Storage Requirements

Node TypeMinimumRecommendedGrowth Rate
Full Node500 GB1 TB~50 GB/month
Archive Node2 TB5 TB~200 GB/month

​
Performance Characteristics

​
Throughput

  • Theoretical Max: ~2,000 TPS
  • Typical Load: 500-1,000 TPS
  • Block Gas Limit: 30,000,000
  • Average Gas/Tx: ~50,000

​
Latency

  • Block Time: ~2 seconds
  • Transaction Inclusion: 2-6 seconds (1-3 blocks)
  • Finality: ~24 seconds (12 confirmations)

​
Comparison with Ethereum

FeatureEthereumPaxeer Network
Block Time~12 seconds~2 seconds
Gas CostsHigh99%+ lower
TPS~15-30~1,500
Finality~15 minutes~24 seconds
EVM VersionLatestLatest (equivalent)

​
System Contracts

Paxeer Network includes several predeployed system contracts:

​
Core System Contracts

ContractAddressPurpose
Sequencer Fee Vault0x4200000000000000000000000000000000000011Collects transaction fees
Gas Price Oracle0x420000000000000000000000000000000000000FGas price information
L1 Block Info0x4200000000000000000000000000000000000015L1 data (if applicable)

​
Accessing System Contracts

interface ISequencerFeeVault {
    function withdraw() external;
}

// Access fee vault
ISequencerFeeVault vault = ISequencerFeeVault(
    0x4200000000000000000000000000000000000011
);

​
Consensus Mechanism

Paxeer Network uses a centralized sequencer for high performance with plans for decentralization:

​
Current: Centralized Sequencer

Advantages:
  • High performance
  • Low latency
  • Predictable block times
  • Simple operation
Considerations:
  • Single point of control
  • Liveness depends on sequencer
  • Trust in sequencer operation

​
Future: Decentralized Sequencing

Planned Features:
  • Multiple sequencer rotation
  • Fault tolerance
  • Censorship resistance
  • Community participation

​
Security Model

  • EVM equivalent execution
  • Deterministic state transitions
  • Gas metering prevents DoS
  • Safe math in Solidity 0.8+
  • Peer authentication
  • Block validation
  • State root verification
  • Transaction signature verification
  • Gas fees prevent spam
  • Priority fees incentivize proper behavior
  • Fee vault ensures sustainability

​
Upgrades and Governance

​
Network Upgrades

Network upgrades follow a structured process:
1

Proposal

Upgrade proposed by core team
2

Testing

Extensive testing on testnet
3

Announcement

Community notification with timeline
4

Deployment

Coordinated upgrade at specific block
5

Verification

Post-upgrade monitoring and verification

​
Resources

GitHub

View source code

Technical Specs

Detailed specifications

Node Operators

Run your own node

Security

Security best practices