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
  • Why We Chose This Architecture
  • Inspired by Metaphor

Architectural Philosophy

Why We Chose This Architecture

The current generation of blockchains are becoming increasingly efficient within their own boundaries — but that efficiency comes at the cost of fragmentation. Each major chain functions as a self-contained silo, with its own standards for wallets, tokens, programming languages, and user experiences. This separation increases developer burden, splits liquidity, and results in redundant infrastructure being built again and again.

Arichain was created to move beyond this paradigm. Rather than enforcing a single execution model, Arichain embraces plurality — supporting multiple virtual machines natively and independently, under a unified consensus and system architecture.

We believe:

  • Developers should be free to build using the VM best suited to their application logic, without compromising security or performance.

  • Users should be able to explore diverse application ecosystems within a single chain, without switching between fragmented networks.

  • Specialized environments should coexist with equal security and sovereignty, not compete for dominance.

This is why Arichain is a Multi-Dimensional Layer 1 — not just a faster or more scalable chain, but a redefinition of what a blockchain can be: a common foundation where diverse execution environments are equally first-class, modular, and fully native.

Each VM operates with its own standards, languages, and design space, while benefiting from shared consensus, staking, and infrastructure. This architecture reflects our belief that modularity and composability are not optional for the future of Web3 — they are essential.

Our goal is to make Arichain the network where infrastructure fades into the background, and user experience remains unified, no matter how many execution environments are being served.


Inspired by Metaphor

Arichain’s design is rooted in metaphor — a symbolic reflection of its architecture and its ethos.

ARI = ANT

In Japanese, “Ari (アリ)” means ant — a creature that thrives in distributed, multi-layered colonies without centralized control. Each ant has a role. Each unit operates independently. Yet together, they move with remarkable coordination and shared intent.

So does Arichain. Each VM in the network is built for a specific purpose, with its own execution logic and tools. The consensus layer acts like a pheromone trail — aligning finality across the system, keeping the network coherent without constraining its diversity.

Arichain is not a stack of interchangeable parts. It is a living, evolving network of specialized execution layers, working in parallel, sharing trust — and expanding what’s possible in Web3.

PreviousDetails to readNextMonolithic vs Modular: Why Multi-VM

Last updated 1 month ago