Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

n-VM: A Multi-VM Layer-1 Architecture with Shared Identity and Token State

Jian Sheng Wang

Abstract

Multi-chain ecosystems suffer from fragmented identity, siloed liquidity, and bridge-dependent token transfers. We present n-VM, a Layer-1 architecture that hosts n heterogeneous virtual machines as co-equal execution environments over shared consensus and shared state. The design combines three components: a dispatcher that routes transactions by opcode prefix, a unified identity layer in which one 32-byte commitment anchors VM-specifific addresses, and a unified token ledger that exposes VM-native interfaces such as ERC-20 and SPL over a common balance store. We formalize routing, identity derivation, and token transfer semantics, and prove cross-VM transfer atomicity and identity isolation under standard cryptographic assumptions. We describe a concrete instantiation with five VMs: a native runtime, EVM, SVM, Bitcoin Script, and TVM. We also present context-based sharding and a write-set scheduler for parallel execution. Under an analytical throughput model, the architecture admits a projected range of about 16,000 to 66,000 transactions per second on commodity hardware.

n-VM: A Multi-VM Layer-1 Architecture with Shared Identity and Token State

Abstract

Multi-chain ecosystems suffer from fragmented identity, siloed liquidity, and bridge-dependent token transfers. We present n-VM, a Layer-1 architecture that hosts n heterogeneous virtual machines as co-equal execution environments over shared consensus and shared state. The design combines three components: a dispatcher that routes transactions by opcode prefix, a unified identity layer in which one 32-byte commitment anchors VM-specifific addresses, and a unified token ledger that exposes VM-native interfaces such as ERC-20 and SPL over a common balance store. We formalize routing, identity derivation, and token transfer semantics, and prove cross-VM transfer atomicity and identity isolation under standard cryptographic assumptions. We describe a concrete instantiation with five VMs: a native runtime, EVM, SVM, Bitcoin Script, and TVM. We also present context-based sharding and a write-set scheduler for parallel execution. Under an analytical throughput model, the architecture admits a projected range of about 16,000 to 66,000 transactions per second on commodity hardware.
Paper Structure (44 sections, 5 theorems, 15 equations, 1 figure, 5 tables, 2 algorithms)

This paper contains 44 sections, 5 theorems, 15 equations, 1 figure, 5 tables, 2 algorithms.

Table of Contents

  1. Introduction
  2. Motivation
  3. Key Insight: VM-Agnostic Identity--Authorization Separation
  4. Contributions
  5. Background
  6. The ACE-GF Identity Primitive
  7. The Attest--Execute--Prove Pipeline
  8. Existing Multi-VM Approaches
  9. Architecture
  10. Overview
  11. Opcode-Based Transaction Routing
  12. VM Engine Interface
  13. Block Execution
  14. Unified Identity Layer
  15. Cross-VM Address Derivation
  16. ...and 29 more sections

Key Result

Theorem 4.1

For any two distinct VM tags $\mathsf{tag}_i \ne \mathsf{tag}_j$ and any $\texttt{id\_com}$, the derived addresses $\alpha_{V_i}$ and $\alpha_{V_j}$ are computationally independent under the collision resistance of SHA-256.

Figures (1)

  • Figure 1: Layered n-Vm architecture.

Theorems & Definitions (18)

  • Definition 1: Opcode Routing Function
  • Definition 2: VM Engine
  • Definition 3: Address Derivation
  • Theorem 4.1: Address Isolation
  • proof : Proof sketch
  • Definition 4: Raw Chain Transaction
  • Definition 5: Unified Token State
  • Theorem 5.1: Cross-VM Atomicity
  • proof : Proof sketch
  • Definition 6: Write Set
  • ...and 8 more