What if money
had rules?

Rules that nobody can break.
Not even you.

Start ↓
Today

Right now, Kaspa is cash.

You hand someone a $20 bill. It's theirs. They can spend it, save it, or give it away. The bill has no opinion. No memory. No rules.

1,000 KAS

Prove you own it. Send it. Done.
That's all Kaspa can do today.

Covenants

Now imagine writing rules on that bill.

"Only spendable at a grocery store. Only after March 1st. Max $5 at a time."

And every person who ever touches that bill is forced to follow those rules. Not because they're honest. Because the money itself won't let them break it.

That's a covenant. Rules that travel with the coin and are enforced by every node on the network.

1,000 KAS
Only sendable to approved addresses
Locked until June 2026
Max 100 KAS per transaction
If untouched for 1 year, goes to heir
Enforced by every node. No exceptions.
So What?

Here's what becomes possible.

Someone steals your key.
A vault with a 24-hour delay. You see the attempt, cancel it, move everything to backup. Thief gets nothing.
You die unexpectedly.
A dead-man switch. If your coins don't move for a year, they unlock for your family. No lawyer. No seed phrase hunt. Just math.
You're buying from a stranger online.
Escrow. Coins are locked until both sides confirm — or refunded after a timeout. No middleman.
A project wants to create a token.
Native token issuance directly on Kaspa. Validated by every node. As real as KAS itself.
These are just examples. A covenant is any rule you can express in script. If you can describe the condition, the network can enforce it. Covenants are the building blocks — it's up to developers to assemble them into products.
The Limit

But each coin is alone.

A covenant can control its own coin. But it can't see other coins. It can't check someone's balance in another contract. It can't coordinate with anything else.

Think of vending machines. Each one follows rules perfectly. But the drink machine doesn't know what you bought from the snack machine. They can't work together.
You can build a vault.
You can't build an exchange.

For that, programs need to share information.

Verifiable Programs

Enter VProgs.

VProgs (Verifiable Programs) are Kaspa's answer. Programs that can share state, work together, and do anything — but prove they did it correctly.

On Ethereum, every computer on the network re-runs every program. Thousands of machines doing identical math. Slow and expensive. Kaspa does it differently.

One computer runs the program. Then it creates a mathematical proof that the answer is correct. Every Kaspa node checks the proof — not the work. Same guarantee. A thousandth of the effort.

That proof is called a zero-knowledge proof.
The base layer never runs programs. It just checks receipts.

Covenants are what make VProgs possible — they're the L1 anchor that secures every program's state. VProgs build on that foundation with shared state, atomic composability, and zero-knowledge proofs.
What can VProgs do?
But What If

What if a program goes offline?

Fair question. If a VProg runs off-chain, what happens to your funds if the operators disappear?

1. Anyone can run it.
VProg provers are permissionless. There's no single company running the show. If one prover goes offline, anyone else can spin one up and pick up exactly where it left off.
2. Everything lives on L1.
Kaspa is the sequencer and the data layer. Every transaction is posted to L1 — not to some off-chain server. A new prover can rebuild the entire state from the DAG alone. Nothing is hidden. Nothing is lost.
3. Programs can't take each other down.
Each VProg is sovereign. It runs independently, advances independently, and fails independently. One program going offline has zero effect on any other.
Most blockchains with off-chain programs depend on a centralized sequencer — a single point of failure. If it goes down, everything stops. Kaspa's design removes that entirely. L1 is the sequencer. The data is always there. The provers are permissionless. The architecture is built so that no single party can hold your funds hostage — by design, not by promise.
The Stack

Three layers. One network.

VProgs
Full programs. Run off-chain. Proven with math.
Covenants
Rules on coins. Enforced by every node.
BlockDAG + PoW
10 blocks per second. Validates everything.

Covenants add rules to coins. VProgs add programs that work together.
Neither requires trust.

Status

This is already happening.

May 2025
Crescendo. 10 BPS. First introspection opcodes. Done.
Jan 2026
Testnet 12. Full covenants. ZK proofs. Devs building. Done.
June 2026
Toccata. Covenants, native assets, ZK opcodes go live on mainnet.
Late 2026
VProgs. Full programmability. DeFi lands on Kaspa.
tn12.kaspa.stream — explore Testnet 12 live
rusty-kaspa · KIPs · vprogs · vprogs.xyz
The fastest L1
is becoming programmable.
Without slowing down.
PoW Protocol University

KIP-10 · KIP-17 · KIP-20 · Covenant++ Roadmap · VProgs Architecture

Genesis Proof · Lost Data