The intent-centric Layer 1

Parallel execution lanes. Encrypted batch ingress. Post-quantum cryptography. Zero-knowledge proofs. Zero MEV by construction.

Blockchain network visualization
Testnet Live

Four problems every chain ignores

MEV extracts billions. Sequential execution caps throughput. Classical cryptography has an expiry date. Smart contracts leak value. Rivellum solves all four at the protocol level.

Secure encrypted data transmission

No Mempool. No MEV.

Intents are encrypted inside ChaCha20-Poly1305 envelopes before submission. Validators never see content until after batch sealing. Execution order is derived from a BLAKE3 permutation of the seal hash — impossible to front-run.

Parallel data streams visualization

Lane-Parallel Execution

Independent state lanes execute concurrently — each with its own database, Sparse Merkle Tree, and commit pipeline. Throughput scales linearly with hardware. No global lock. No sequential bottleneck.

Quantum computing abstract

Post-Quantum by Default

Every signature uses CRYSTALS-Dilithium3 (ML-DSA-65). Key encapsulation via ML-KEM-768. No classical cryptography exists in the protocol — post-quantum from genesis.

Verified value ledger

Universal Value Ledger

Traditional smart contracts mutate balances directly — enabling reentrancy and unchecked value leakage. In Rivellum, contracts produce PVI graphs that the UVL verifies against 12 invariants before any settlement. Assets cannot be duplicated, destroyed, or moved without proof.

From intent to finality

Every transaction flows through an 8-stage deterministic pipeline. Each stage is purpose-built. Each output is cryptographically verified.

1

Encrypted Intent Submission

Users declare a desired outcome wrapped in a ChaCha20-Poly1305 EncryptedEnvelope. The envelope enters the EncryptedAdmissionPool — there is no mempool. Content is opaque to all parties including validators.

ChaCha20-Poly1305 AEAD · EncryptedEnvelope · per-sender anti-DoS · 429 backpressure
2

Batch Sealing & Ordering

Envelopes accumulate into time-windowed per-lane batches. When the window closes, the BatchLifecycleManager seals the batch and derives execution order via a deterministic BLAKE3 permutation of the seal hash. No party can predict ordering.

BatchLifecycleManager · 4-stage lifecycle: seal → decrypt → order → dispatch
3

Lane Routing

Each intent is routed by sender address hash (blake3(sender)[0] % lane_count) to an independent lane. Lanes are mapped to committees via modulo. This is deterministic address-based partitioning — not dynamic resharding.

blake3(sender)[0] % lane_count · committee_idx = lane_id % committee_count
4

Photon Parallel Execution

Each committee runs as an in-process thread group: one leader thread for nonce admission and signature verification, and W−1 executor workers. Lanes execute concurrently with copy-on-write state snapshots. No global lock.

PhotonExecutor · WorkerPool · gas metering · COW snapshots
5

Lane Commit & SMT

Each lane has a dedicated LaneCommitter with its own RocksDB instance, WAL, and Sparse Merkle Tree root engine. State diffs are applied atomically. Same delta sequence always produces the same state root.

LaneCommitter · per-lane RocksDB · WAL with CRC32C · LaneRootEngine
6

Lane Consensus

Each committee reaches local consensus on its own lane batches. Validators within a committee vote on batch ordering using Aurora BFT — pipelined Byzantine consensus with a three-chain commit rule and CRYSTALS-Dilithium3 quorum certificates. This gives sub-second lane-level finality.

Per-committee voting · three-chain commit · Dilithium3 QCs · equivocation slashing
7

Global Consensus & Meta-Root

After lanes finalize independently, the MetaRootAggregator merges all lane SMT roots into a single global meta-root. Cross-lane operations settle via the CPC protocol with nullifier-based deduplication. The global meta-root is the canonical state commitment verified by all nodes.

MetaRootAggregator · global meta-root · cross-lane CPC · nullifier dedup
8

Verifiable Settlement

ZK proof composition aggregates execution proofs from all lanes. External chains verify Rivellum state in a single call. Winterfell STARKs, Plonky2, and Halo2 backends with recursive composition across 5 privacy circuits.

Winterfell STARKs · Plonky2 · Halo2 · recursive proof composition · 5 circuits
By the Numbers
<2s
Finality
0
ZK circuits
0%
Inflation
1B
Fixed RIVL supply
0
AI endpoints
$0.001
Micro-tx fee

Built from zero. Verified at every layer.

No forks. No wrappers. Every subsystem is purpose-built and adversarially tested.

Code development environment

Mist: Smart Contracts Reimagined

A resource-tracked language where contracts declare intent, not step-by-step mutations. Mist eliminates boilerplate — an escrow that takes 200 lines in Solidity fits in 20 lines of Mist. The compiler enforces correctness so you ship faster with fewer bugs.

  • Resource-tracked types — assets are linear by default
  • Formal verification built into the compiler pipeline
  • PVI graphs checked against 12 UVL invariants at commit time
  • Native intent awareness — contracts declare outcomes, not steps
Network consensus hardware

Aurora BFT Consensus

Pipelined Byzantine consensus purpose-built for parallel lanes. Three-chain commit rule with CRYSTALS-Dilithium3 quorum certificates. Equivocation is detected and slashed. No leaders. No forks. No reorgs.

  • Sub-2-second finality across all committee validators
  • Post-quantum quorum certificates (Dilithium3)
  • Equivocation detection with automated slashing
  • Two-level finality: consensus decoupled from disk durability
Mathematical proof abstract

ZK Proof Composition

Winterfell STARKs, Plonky2, and Halo2 backends with recursive proof composition. Five privacy circuits generate real proofs — not mocked stubs. External chains verify Rivellum state in a single call through aggregated succinct proofs.

  • Three ZK backends: Winterfell (default), Plonky2, Halo2
  • Recursive composition across 5 privacy circuits
  • Poseidon over BN254 for ZK-circuit-friendly Merkle trees
  • PoUW job market for offloaded proving with CPI-indexed caps
Artificial intelligence neural network

Native AI Economy

A protocol-level substrate for autonomous AI agents. Budget-capped agent wallets, trustless escrow, streaming payments, and a permissionless service marketplace — all settled through the same intent pipeline as every other transaction.

  • Agent wallets with session keys, rate limits, and auto-halt on budget exhaustion
  • Service marketplace: data, compute, models, storage, APIs — all on-chain
  • Streaming payments with per-second billing and hard budget caps
  • 24 machine-readable API endpoints and SDKs for Python and TypeScript

Production tools, ready now

Six TypeScript applications and comprehensive Rust tooling for builders.

🔍

Explorer

Blocks, transactions, and receipts.

⌨️

Console

Deploy and manage contracts.

📘

Documentation

Guides, API refs, tutorials.

🚰

Faucet

Testnet tokens, instantly.

🌐

Portal

The ecosystem gateway.

💼

Natos Wallet

Intent-aware signing.

📦

SDK

TypeScript & Rust clients.

📊

Status

Network health & uptime.

Ship your first contract in minutes

Write in Mist — a resource-tracked language with formal verification and native intent awareness. Deploy via CLI or Console. Query verifiable receipts through a unified API.

simple_escrow.mist
contract SimpleEscrow
  state seller: Address
  state buyer: Address
  state amount: Value
  state completed: Bool
  function create(seller_addr: Address,
      buyer_addr: Address, payment: Value)
    let seller = seller_addr
    let buyer = buyer_addr
    let amount = payment
    let completed = false
  function complete()
    require completed == false
    pay amount asset "USDC" to buyer
    let completed = true
  function cancel()
    require completed == false
    pay amount asset "USDC" to seller
    let completed = true
PVI Graphcomplete() compiled output
HOLDSimpleEscrowamount USDC
pay
PAYbuyeramount USDC
UVL verified — pay amount asset "USDC" to buyer compiles to HOLDPAY. Debits = credits. Settled atomically.