LogoLogo
  • Introduction
    • What is Arichain
    • Why Arichain
    • Vision: Redefining Layer 1, Empowering Every Builder.
    • TL;DR Summary for Builders
    • Details to read
  • Architectural Philosophy
    • Monolithic vs Modular: Why Multi-VM
    • Native Composability over Interoperability
    • Unified Chain State and Execution Environment
    • Chain Structure: Multi-VM under One Consensus
    • Identity & User Abstraction
  • General Architecture Overview
    • Multi-VM Execution Environment
    • Consensus Mechanism
    • Token Design
    • Unified Gas System
    • GAID: Global Account Identity
    • Future Roadmap
  • Technical Overview
    • Consensus Protocol Details
    • Token Design and Interoperability
    • Gas System Architecture
    • GAID Architecture
    • State Management
    • Bridge Infrastructure
  • Developer Experience
    • SDK
    • Developer tools
  • Validator
    • Validator Roles & Node Types
    • Reward System
    • Staking
    • Use Cases
    • Node Operations
  • Security
    • Design Goals
    • Threat Model and Risk Assessment
    • Continuous Security Verification
  • Token Economics & Validator Incentives
    • Token Utility
    • Validator Incentives
    • Token Supply and Distribution
    • Onboarding Workflow
  • Roadmap
Powered by GitBook
On this page
  1. General Architecture Overview

Multi-VM Execution Environment

Arichain's Multi-VM architecture represents a breakthrough in blockchain design, enabling native execution of both Ethereum and Solana-compatible smart contracts within a single blockchain infrastructure.

System Architecture Overview

┌─────────────────┐     ┌─────────────────┐
│   EVM Engine    │     │   SVM Engine    │
│   (Rust-based)  │     │   (Rust-based)  │
└─────────────────┘     └─────────────────┘
         │                       │
         ▼                       ▼
┌─────────────────────────────────────────┐
│         Global State Database           │
│        (Unified State Access)           │
└─────────────────────────────────────────┘
         │                       │
         ▼                       ▼
┌─────────────────────────────────────────┐
│           Native VM Wrapper             │
│          (Token Management)             │
└─────────────────────────────────────────┘
                    │
                    ▼
┌─────────────────────────────────────────┐
│             Consensus Layer             │
│             (X-BFT / DPoS)              │
└─────────────────────────────────────────┘
                    │
                    ▼
┌─────────────────────────────────────────┐
│          Unified Chain Storage          │
└─────────────────────────────────────────┘

Dual Virtual Machine Support - On Phase 1

Ethereum Virtual Machine (EVM) Integration Arichain provides full EVM compatibility, ensuring existing Ethereum applications can migrate seamlessly:

  • Complete Protocol Compatibility: Support for all Ethereum Improvement Proposals (EIPs) including the latest protocol upgrades

  • Familiar Developer Tools: Native integration with MetaMask, Hardhat, Truffle, Remix, and other Ethereum development tools

  • Existing dApp Migration: Ethereum dApps can deploy on Arichain without code modifications

  • JSON-RPC API: Full support for standard Ethereum APIs (eth_, net_, web3_*)

Solana Virtual Machine (SVM) Integration Arichain maintains full compatibility with Solana's high-performance execution environment:

  • Account Model Support: Native implementation of Solana's account-based architecture

  • BPF Program Execution: Full Berkeley Packet Filter (BPF) program support for maximum performance

  • Solana Tooling: Compatible with Solana CLI, Anchor framework, and existing development tools

  • Program Derived Addresses: Native support for PDAs and cross-program invocations

Single Wallet Multi-VM Architecture

Unified Wallet Experience Arichain provides a seamless user experience through a single wallet that can interact with both VM environments:

  • Single Private Key: One private key pair works across all supported virtual machines

  • VM-Specific Calls: Users specify target VM through transaction flags or parameters

  • Consistent Address Format: Unified address format with VM-specific derivation

  • Native Token Access: Same wallet can hold and manage tokens from both EVM and SVM ecosystems

VM Selection Mechanism Transactions are routed to the appropriate VM based on explicit user selection:

// EVM transaction with VM flag
const evmTransaction = {
  to: contractAddress,
  data: contractData,
  targetVM: 'EVM',
  gasLimit: 21000
};

// SVM transaction with VM flag
const svmTransaction = {
  instructions: [instruction],
  targetVM: 'SVM',
  computeLimit: 200000
};

Execution Performance

The Multi-VM architecture is designed for optimal performance across both execution environments:

Parallel Execution

  • EVM and SVM transactions can execute simultaneously when there are no state conflicts

  • Intelligent dependency analysis ensures correct ordering of interdependent transactions

  • Resource isolation prevents one VM from impacting the other's performance

Optimized State Management

  • Shared global state database enables efficient cross-VM data access

  • Merkle trie optimization for fast state verification

  • Atomic commitment protocols ensure consistency across all VMs

Real-World Benefits

For Developers

  • Use familiar tools and languages from both ecosystems

  • No need to learn new programming paradigms or tools

  • Access to the combined liquidity and user base of both ecosystems

For Users

  • Single wallet works across all applications regardless of underlying VM

  • Consistent user experience across different dApp types

  • Lower transaction costs through optimized execution paths

For dApp Projects

  • Access to broader developer talent pool (both Ethereum and Solana developers)

  • Ability to optimize different parts of applications for specific VM strengths

  • Reduced technical debt from maintaining multiple chain deployments

PreviousGeneral Architecture OverviewNextConsensus Mechanism

Last updated 24 days ago