Verified compute · 2026
Verse.
Run code on a machine you don’t trust — and get a cryptographic receipt that an independent node re-ran it and got the same answer.
Not “trust the cloud.” Check the re-run.
Re-running only proves something if the answer can’t drift.
IEEE-754 pins arithmetic but says nothing about exp, ln, sin, cos — which is why cross-platform replays desync on trig. Verse pins them too, and publishes the evidence.
$ verse det check
✓ 255 conformance vectors identical · x86-64, arm64, wasm
The network has no center.
Apps connect directly to the machines and capabilities they need.
Nobody else stores, executes, or approves the work.
One interface. Many capabilities.
Use compute, storage, models, tools, and verification without building around one provider.
Your app stays portable. Nodes stay independent.
Three things. That’s it.
What exists.
Signed, expiring records describing capabilities, applications, active work, and shared state.
What happens.
Portable WASM components with typed interfaces, explicit permissions, and resource limits.
What connects it.
A temporary signed agreement defining access, execution, verification, and settlement.
One loop. Composed at any scale.
Each operation runs where it fits. Apps compose those operations into something larger.
Apps move through the mesh.
Machines remain independent.
State stays where it belongs.
Only the nodes that need it store it.
Plate IV · Light on the altar
Portable logic. Native power.
WASM controls permissions and execution.
Native CPUs, GPUs, storage, and model runtimes do the heavy work.
Built for agents.
Typed capabilities. Explicit permissions. Hard spending limits.
Agents can discover, combine, execute, and verify network capabilities without receiving root keys, unrestricted wallets, or access to entire machines.
Controlled by users.
Every action is bounded by a signed mandate.
Natural language can propose an action. It cannot authorize one.
The field finds its own shape.
Every served byte leaves heat. Heat decays on its own. From that one rule the mesh organizes itself — busy data replicates toward demand, traffic flows to the nearest copy, price follows load. Nobody schedules it.
Caching, routing, replication, price — one field, read many ways.
And trust needs no ledger. Work runs on a machine you don’t own, and you check it by running it again — one honest re-run settles it. The same trick hands you a debugger and a verifiable AI council for free.
Nothing global unless it must be.
Left out
- − Native token
- − Global ledger
- − Permanent history
- − Central scheduler
- − Global contract VM
- − Network-wide consensus
Kept
- + Direct peer links
- + Portable WASM
- + Compute, storage, models
- + Signed Pacts + receipts
- + Pluggable payments
- + Data that expires
Plate V · Two thrones
Only the participants coordinate.
Not every machine. Not every validator. Not forever.
One honest
re-run settles it.
No consensus, no majority to bribe, no chain. One signed receipt and a node willing to run it again.
One binary. MIT/Apache. No token. Zero proprietary blobs.
It is also young, and honest about it: the verifier set and the mint are permissioned today, which makes this a trusted committee that never false-slashes within its trust set — not yet trustless refereed delegation. The threat model says so out loud ↗