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. Validator

Use Cases

One chain. Multiple execution environments. Each VM operates independently, but shares consensus and security.

1. Multi-VM dApp Hub

Description: Users can access dApps built on EVM, SVM, or MoveVM — all within a single network — using one wallet and one account.

Example:

  • Trade assets on an EVM-based DEX

  • Play a high-speed game built on SVM

  • Manage secure assets in a MoveVM vault

Key Point: A unified UX layer across VMs, even though each executes independently.

2. Developer-Selectable Execution Environments

Description: Developers can choose the most appropriate VM for their application logic — all while staying within the same chain and token economy.

Example:

  • DeFi apps on EVM

  • Game engines on SVM

  • High-security enterprise tools on MoveVM

Key Point: Execution is decoupled from infrastructure. Developers build where it makes the most sense.

3. Unified Governance & Staking

Description: All VMs are secured by the same consensus protocol, allowing for shared staking, governance, and incentives — regardless of execution layer.

Example:

  • $ARI token holders govern the chain globally

  • Staking rewards apply to validators serving all VMs

Key Point: Security is unified. Execution remains modular.

4. VM-as-a-Service Platform

Description: Arichain can host and scale new virtual machines as modular runtime instances — each with its own ecosystem, tooling, and apps.

Example:

  • Onboard a ZKVM for privacy-preserving apps

  • Launch an AI-optimized VM or gaming-specific VM

  • Run multiple MoveVM instances for isolated domains

Key Point: New VMs can be added or deprecated without affecting the core chain.

5. Multi-VM UX

Description: While VMs do not interact at the execution layer, Arichain supports unified UX flows: one wallet, one dashboard, one identity across environments.

Example:

  • View assets from multiple VMs in a single interface

  • Use one wallet to interact with EVM and MoveVM apps separately

  • Track activity across environments in a unified dashboard

Key Point: Multi-VM experience is seamless.

PreviousStakingNextNode Operations

Last updated 27 days ago