Arithmic Documentation
  • Introduction
  • Gen 1.0 - Gen 2.0 VMs and Staking
    • Gen 1.0 VM and its Limitations
    • Gen 2.0 VM Paradigm
    • Recursion in Gen 1.0 and Gen 2.0 VMs
    • Staking & LSTs
    • Restaking & LRTs
  • Arithmic Gen 2.0 zkVM Soma: The future of zkEVMs
    • Soma System Design
    • Hardware Acceleration
    • Performance
    • Outperforming the Competition
  • Network Architecture
    • Nodes
    • Client and Explorer
    • Data Availability
    • Decentralized Sequencing
    • Computation & Decentralized Infrastructure
  • Arithmic Network's Staking Model
    • Problem of Fractured Incentives
    • Aligning Network Incentives
  • Arithmic’s Multichain Staking Pools (MSP)
    • How does an Arithmic MSP work?
      • Stable Hyper-Staked Token (sHST)
      • Equity Hyper-Staked Token (eHST)
      • MSP Example
    • Types of Staking Pools
  • Arithmic Rewards System
    • Earning Arithmic Points
    • Participating in Arithmic MSPs
  • Arithmic Network's Roadmap
  • Our Vision
Powered by GitBook
On this page
  1. Gen 1.0 - Gen 2.0 VMs and Staking

Gen 2.0 VM Paradigm

Recent developments in SNARKs aim to prove non-algebraic operations entirely using lookups, that greatly reduce overheads for such computations. This enables the design of SNARKs with reduced prover overheads for CPUs like RISC-V with non-algebraic operations. We term this approach to designing virtual machines for validity roll-ups as Gen 2.0, i.e., a virtual machine (VM) that proves all the operations in a CPU (e.g. RISC-V) entirely using lookups. VMs built on the Gen 2.0 paradigm have two major advantages: a) isolation of protocol errors to just the lookup arguments, and hence, increased security, and b) friendly towards developers who can code in a language like C or Rust, as we have existing compilers that build C/Rust code to assemblies like RISC-V.

PreviousGen 1.0 VM and its LimitationsNextRecursion in Gen 1.0 and Gen 2.0 VMs

Last updated 1 year ago