Budget that cannot drain at once
A treasury output can require each next spend to leave enough value or respect a cap.
Kaspa builder funnel
Kaspa covenants explained.
Kaspa covenants are spending rules that can restrict how a coin or UTXO is spent next. In product terms, they can make a budget, vault, asset, escrow, or commitment follow visible rules.
Timing note: payments are live today. New app-layer rules need Toccata activation and supporting wallets or tools.
Kaspa covenants in plain language.
A normal wallet signature says who is allowed to spend. A covenant-style rule can also inspect the spending transaction and require the next output to preserve a rule, route funds, limit value, or carry state forward.
That turns some app logic into a money rule users can inspect. It does not remove wallet UX, audits, liquidity, legal risk, or oracle design.
Examples.
Withdrawal with recovery
A vault can route normal withdrawal and emergency recovery through different paths.
Asset with controller
A ticket or pass can require an issuer or controller input before transfer or redemption.
Commitment with refund
A funding rule can release only after a threshold, then refund if the threshold is missed.
Covenant evidence checklist.
- User need. Say what the user does before naming the opcode or compiler.
- Accepted path. Show the accepted transaction or test artifact.
- Rejected path. Show what fails when the rule is violated.
- Status label. Say live, testnet, targeted, roadmap, or research.
- Missing product work. Name wallet signing, audits, indexing, support, liquidity, and custody gaps.