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. Architectural Philosophy

Unified Chain State and Execution Environment

Arichain introduces a Global State Layer that harmonizes state management across different virtual machines.

Key Components:

  • EVM State Tree: A modified Patricia Merkle Trie for Ethereum smart contracts.

  • SVM State Tree: A high-performance, account-based model for Solana programs.

  • GAID Registry: Manages global identities and multi-VM permissions.

  • Bridge State: Handles native cross-chain asset movements with on-chain proofs.

This unified global state ensures:

  • Atomicity: State changes across VMs are committed atomically, preventing partial failures.

  • Consistency: Cross-VM interactions maintain strict state consistency.

  • Efficiency: Parallel execution and optimized Merkle proof generation reduce overhead.

Each VM maintains its own execution environment, optimized for its workload:

  • EVM: Robust compatibility for Ethereum-based contracts.

  • SVM: High throughput for performance-intensive applications.

Through the Global State Manager, all state updates — regardless of VM — are coordinated, validated, and finalized under the same architecture.

PreviousNative Composability over InteroperabilityNextChain Structure: Multi-VM under One Consensus

Last updated 23 days ago