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. General Architecture Overview

Consensus Mechanism

Arichain utilizes a Delegated Proof-of-Stake (DPoS) consensus mechanism with a unique multi-VM validation approach that ensures security and performance across all supported virtual machine environments.

Delegated Proof-of-Stake Overview

Validator Set Configuration Arichain operates with a carefully balanced validator set designed for optimal performance and decentralization:

  • Active Validators: TBD block-producing validators ensuring fast block times

  • Total Validator Set: TBD validators providing security and redundancy

  • Byzantine Fault Tolerance: Network remains secure with up to 1/3 malicious validators

  • Geographic Distribution: Validators distributed globally for network resilience

Performance Characteristics The consensus mechanism is optimized for Multi-VM operations:

  • Block Time: TBD seconds for fast transaction finality

  • Transaction Throughput: TBD TPS with TBD active validators

  • Finality: Immediate finality without probabilistic confirmation delays

  • Multi-VM Validation: Parallel validation of EVM and SVM transactions

Authority-Based Initial Operation

To ensure network stability during the initial launch phase, Arichain implements an authority-based operation model:

Phase 1: Authority-Based (Current)

  • Pre-selected trusted validators ensure network stability

  • Deterministic block production schedule prevents initial chaos

  • Focus on performance optimization and ecosystem development

Phase 2: Community DPoS (Future)

  • Gradual transition to community-selected validators

  • Stake-based validator selection with democratic governance

  • Full decentralization while maintaining performance standards

Multi-VM Block Validation

Arichain's consensus mechanism includes specialized features for Multi-VM environments:

Combined Transaction Processing

  • Validators receive transaction bundles from both EVM and SVM mempools

  • Parallel execution of VM-specific transactions

  • Multi-VM state reconciliation before block commitment

Enhanced Security Model

  • Multi-signature validation requiring consensus from validator majority

  • Multi-VM state verification through cryptographic proofs

  • Automatic rollback mechanisms for failed Multi-VM operations

Economic Incentives and Failure Protection

Validator Rewards

  • Block rewards paid in native ARI tokens

  • Transaction fee distribution among active validators

Network Security

  • Economic security through validator stake requirements

  • Slashing mechanisms for malicious behavior

  • Progressive penalty system for different violation types

PreviousMulti-VM Execution EnvironmentNextToken Design

Last updated 24 days ago