wasm-vm
Product suite · proofmesh/0.1

A computer, a storage network, and a work market in one browser.

wasm-vm starts with a real Linux machine in WebAssembly. ProofMesh extends it with passkey-owned storage and a builder/critic network for work that can be reproduced instead of merely promised.

Launch the live machine →See the roadmap
Four surfaces

One foundation, different ways to use it.

The current demo is the machine. The other surfaces are designed as explicit products, with their own contracts and acceptance gates.

🐧
Live now

Browser Linux

Boot an unmodified riscv64 Linux guest in a browser tab, with a terminal, persistence, networking, and real userland workloads.

  • Rust RV64 virtual machine
  • WebAssembly execution
  • Linux, Alpine, OCI workloads
Open the machine →
🔐
Designing

Private volumes

Layer a writable user volume over an immutable base image. Passkeys unlock encrypted generations; peers only receive verified ciphertext.

  • Passkey and recovery slots
  • Authenticated encrypted shards
  • Local-first snapshots
Explore the trust model →
🧩
Designing

Verified block network

Request only the blocks the guest needs. HTTP, local cache, WebRTC, and torrent-like peers become interchangeable transport sources.

  • Content-addressed manifests
  • Demand paging and cancellable read-ahead
  • Hash before cache insertion
See distribution →
⚙️
Planned

Work market

Publish a frozen optimization ticket, fund it, and let builders compete to produce a faster artifact with a reproducible proof bundle.

  • Reverse auctions and bounties
  • Deterministic acceptance rules
  • Artifact and benchmark hashes
See the protocol →
🧪
Planned

Critic network

Several independent critics check semantics, performance, security, reproducibility, and supply chain before a result settles.

  • Quorum and challenge windows
  • Signed attestations
  • Failure bounties and bonds
Meet the critics →
🧱
API first

Embedding layer

Build your own Linux experience with an asynchronous controller API designed for workers, storage backends, peers, and long-running work.

  • Typed lifecycle and errors
  • Explicit byte ownership
  • Progress and cancellation
See packages and host/guest boundaries →
The boundary

Distributed delivery first. Distributed execution later.

A peer can seed an immutable block without becoming a trusted server. The guest still runs locally in the browser. Only after process placement and coordinated services span nodes will we call the operating environment distributed.

// immutable content and private state meet at the browser
web seeds / peers → verified base blocks → local Linux guest
                                  ↘ encrypted user overlay
requester → frozen work ticket → builder → independent critics → settlement