Apps that prove instead of asking you to trust
are Kaspa’s plan for shared apps, like an exchange, that run off the network and send it a proof that they did their job right. Every node checks the proof in milliseconds. They exist as a prototype, not on the live network.
Why it matters to you
Today, using an app on a blockchain means trusting that its code does what it says, or waiting while every node re-runs it. A proof removes both. The app can’t cheat you without the proof failing, and the network stays fast because checking is cheap.
How it works: heavy to make, light to check
The app does its work and produces a : a few hundred bytes of math. Making the proof takes a lot of computing. Checking it takes about the same tiny effort however big the work was.
Where Kaspa is today
The upgrade of June 30, 2026 added the pieces underneath. KIP-16 lets a check a proof. KIP-21 lets an app prove its own lane of transactions. vProgs build on those to let many users change one shared app at once, which covenants alone can’t do.
What isn’t settled
Everything about timing. There is no date for vProgs on , and the design may still change.
Sources
- Status: the Kaspa core developers’ roundups, checked Oct 29, 2026.
- Overview: vprogs.xyz.
- KIPs: github.com/kaspanet/kips.