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

Identity & User Abstraction

Building a Unified User Experience

GAID (Global Account Identity)

  • One wallet address to access all VMs through a unified account system.

  • Seamless login and transaction signing across EVM, SVM, WASM, and future VMs without the need for separate wallets.

  • Reduced wallet management complexity for both users and dApps.

Unified Wallet Experience

  • MetaMask, Phantom, and other popular wallets are integrated to deliver a smooth, familiar user experience.

  • Users can access Arichain’s network and all supported VMs without manual network switching.

  • Wallet connection, VM selection, and application usage are streamlined into a single continuous flow.

Multi-VM Address Derivation Logic

  • A single key pair is used to derive addresses optimized for different VMs.

  • Address derivation logic complies with each VM’s native address format (EVM, SVM, WASM, etc.).

  • Users manage one private key while seamlessly interacting with multiple VM-native addresses.

Key Message

Arichain eliminates complexity with a unified wallet experience, allowing users to seamlessly interact with multiple VMs through a single identity.

PreviousChain Structure: Multi-VM under One ConsensusNextGeneral Architecture Overview

Last updated 20 days ago