Learn · stop 5 of 5
Questions everyone asks
Is this like Ethereum smart contracts?
Same goal — programmable rules on-chain — different shape. Ethereum runs programs against big shared account balances. Kaspa covenants attach rules directly to specific coins (UTXOs): smaller and stricter per contract, but the rules travel with the money itself and inherit Kaspa's speed and proof-of-work security.
Do I need to understand covenants to hold KAS?
No. Plain sending and receiving is unchanged. The stack matters when you want more than transfer: vaults, escrow, tokens with chain-enforced rules — or when you want to judge a project that claims to use them.
What is actually audited?
As of this site's last review: Silverscript hit v1.0.0 on 2026-09-09 but names no external audit and its own security policy still calls it experimental. Argent has no tagged release at all. The status board tracks this daily — and any project's "audited" claim deserves a named auditor and a date before you believe it.
What is KCC-20, in one line?
Tokens whose supply and transfer rules are checked by Kaspa consensus itself — no off-chain bookkeeper to trust. They are live and traded on mainnet while the written standard is still being consolidated.
What are vProgs, and can I use them?
Not yet — vProgs (native programs living in the DAG) are the research track, the roadmap beyond covenants. Anyone selling you a "vProg" today is early by definition.
Where would I actually start building?
Kascov.io lets you try covenant code with zero installation, and Silverscript is the language most things are written in today. The Build section walks the whole path: toolchain, a first 12-line covenant, testnet, and the examples worth reading.
That's the tour.
You now know more about Kaspa's programmability stack than most of crypto Twitter. From here: the comparison matrix for the details, the decision guide if you're building something, the build path when you're ready to write code, or the status board to see what moved today.