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

Monolithic vs Modular: Why Multi-VM

In blockchain design, two architectural paradigms dominate the landscape: monolithic and modular.

  • Monolithic Chains — like Bitcoin and Ethereum — handle consensus, data availability, and execution in a tightly coupled stack. They are simpler but face limitations in scalability and specialization.

  • Modular Chains — like Celestia and Polkadot — separate these layers, enabling more flexibility but introducing fragmentation and interoperability overhead.

At Arichain, we chose a different path — the Multi-VM Architecture — to balance the benefits of both:

  • Monolithic Security: A single consensus layer secures all virtual machines.

  • Modular Execution: Each VM (EVM, SVM, and future VMs) operates independently but under the same chain.

  • Unified Chain State: Despite multiple execution environments, all state changes are synchronized through a global state database.

This design enables:

  • Scalability through parallel execution.

  • Security through unified finality.

  • Flexibility without the complexity of cross-chain communication.

In short, Arichain is monolithic where it matters — for security and finality — and modular where it counts — for execution and scalability.

PreviousArchitectural PhilosophyNextNative Composability over Interoperability

Last updated 20 days ago