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. Token Economics & Validator Incentives

Onboarding Workflow

TBD

  • Testnet Faucet & Sandbox: Developers can request VM-specific tokens and deploy cross-VM test contracts

  • Arichain Explorer: Cross-VM block viewer with transaction tracing

  • Dev Portal & Documentation: Includes templates, tooling examples, and SDK references

By treating each VM as a composable module within a larger dApp architecture, Arichain allows teams to build across execution paradigms without sacrificing simplicity.

Details will be disclosed at a later date.

PreviousToken Supply and DistributionNextRoadmap

Last updated 24 days ago