Build on QBit

A deterministic WASM VM with post-quantum security and parallel execution.

QBit Virtual Machine (QVM)

The QVM runs deterministic WASM. No floating-point arithmetic, no non-deterministic host calls. Every execution trace is provable via ZK-STARKs.

Runtime

Deterministic WASM VM

Max Trace Length

2²⁶ steps per batch

Floating Point

Not supported (strict determinism)

Gas Schedule

Base Transaction

21,000 gas

Cold Storage Write

20,000 gas

Block Gas Limit

50,000,000 gas

Account Model

QBit uses an Ethereum-like account model with a Poseidon Merkle state tree for post-quantum secure state commitments. Accounts use strict nonce incrementing to prevent replay attacks and ensure deterministic ordering.

Model

Ethereum-like accounts

State Tree

Poseidon Merkle tree

Nonce Policy

Strict incrementing

Transaction Format

json

{
  "from":       "0x...",
  "to":         "0x...",
  "nonce":      42,
  "value":      "1000000000",
  "gas_limit":  21000,
  "data":       "0x...",
  "sig_version": 1,
  "σ":          "<ML-DSA-65 signature>"
}

Parallel Execution

QBit supports parallel transaction execution through Associative State Deltas for additive operations (balance transfers, counter increments). For non-commutative operations, a ReadSet/WriteSet conflict detection mechanism ensures correctness by re-executing conflicting transactions sequentially.

Additive Ops

Associative State Deltas (parallel)

Conflict Detection

ReadSet / WriteSet analysis

Conflict Resolution

Sequential re-execution

Launch Your Own QChain

QChains are sovereign app-chains with QBit's post-quantum security and shared finality. Stake the bond, deploy your WASM runtime, get 5 Sentries, and your chain is live.

Registration Bond

50,000 QBIT (permissionless)

Annual Chain Rent

5,000 QBIT/year (burned)

Cross-Chain Fee

5× base fee (always QBIT, burned)

Min. Sentries

5 for activation

Runtime

Deterministic WASM, verified by SHA3-256

Chain ID

2-byte u16 (chain_id=0 is QBit native)

State Rent

State rent parameters are deferred to a separate specification (QIP-002). Not active at launch.

Read the Whitepaper