🆕
$KAS Proposal Update (Aug 7, 2025): Introducing a synchronously‑composable verifiable programs architecture—a fresh L1/L2 design concept to supercharge Kaspa’s smart contract ecosystem.
Non-technical summary (scroll down for tech)
What’s happening?
#Kaspa is experimenting with a new smart-contract setup called vProgs (“verifiable programs”). Think of them as mini self-contained computers living on the blockchain — each with its own rules, memory, and “fuel tank” for running.
The big ideas:
1. Self-governing apps
Every vProg controls its own speed and storage needs, so one busy app won’t slow down or bloat the whole network.
2. No dependency risks
vProgs don’t need to trust each other to be online or working correctly. If one breaks, the others keep running fine.
3. Game-changer: instant cross-app transactions
You can make a single transaction that reads info from one vProg and updates another — all at once — so either everything happens together or nothing happens. This is called atomicity. It’s like making a bank transfer and an investment purchase in one click, with no risk of one part going through without the other.
Why it matters for Kaspa holders:
If it works, this design could create a modular, secure, and private smart-contract world on Kaspa where apps can work together instantly and safely — potentially attracting more developers, users, and activity to the network.
Kaspa vProgs aim is to keep Ethereum’s flexibility, Solana’s speed, Tron’s efficiency, and Cardano’s rigor, minus the bottlenecks, outages, or centralization issues, by giving each contract sovereignty, instant cross-contract atomicity, and Kaspa’s ultra-fast BlockDAG backbone.
Technical Summary, Key Highlights:
vProgs (verifiable programs) act like mini zkVMs—each has its own logic, state, and gas model.
They maintain full sovereignty, controlling throughput and data growth independently.
Trustless composability: vProgs operate without relying on each other’s availability or execution integrity.
The standout feature: atomic cross-vProg transactions, which means that you can read from one vProg and write to another, all in a single atomic, synchronous transaction.
TL;DR This architecture could pave the way for a secure, modular, and composable vProg ecosystem, enabling atomic, cross-program transactions, all while keeping performance, privacy, and on-chain sovereignty intact.
NB. this is a best-effort description, but there probably are some inaccuracies/errors in it. Please watch the comment section for rectifications etc.
research.kas.pa/t/concrete-p…