you can build a kaspa vault that only lets you spend once a price condition is met.
silverscript’s HodlVault example checks your signature and a signed price message from an oracle, an outside source of data.
kaspa checks that the message meets the contract’s conditions. you’re still trusting the oracle to report the price accurately.
the example code is in the comments for devs to build from.
based apps can use kaspa to order user transactions while maintaining balances and other shared app data off-chain.
the app processes that activity and produces a proof that the recorded instructions changed its state according to its rules.
an L1 covenant checks the proof against kaspa’s recorded activity and validates the update.
the L1 support for this has been available since the toccata hf.
toccata added a native ZK proof verifier to kaspa’s L1.
an app can do expensive calculations off-chain, then submit a proof that it followed the programmed rules.
a covenant checks the proof and makes sure the transaction applies the proven result.
kaspa calls this inline ZK.
bitcoin dev's were discussing covenants back in 2013.
bip-119 later proposed one approach to covenants, restricting spending to a predefined transaction template. it was never activated on btc tho.
kaspa’s covenants go further (covenants++ if you like). scripts can enforce spending rules, carry application state forward and let that state split into branches that progress independently. multiple contracts can also update together in one transaction, with all changes accepted or none of them.
dev's write that logic in silverscript, which compiles it into scripts kaspa enforces on L1.
In The Godfather, Michael Corleone inherits more than his father's empire. He inherits its rules.
Imagine money working the same way.
You receive 1,000 coins, but they come with a condition: whenever you spend them, the recipient must inherit that condition too.
That's the idea behind recursive covenants.
With Kaspa's programmable UTXOs, money can carry enforceable spending rules across transactions.
The family business just went on-chain.
kaspa:native
Sending some 💚 to all exchanges supporting kaspa:native spot trading!
Thank you for recognizing Kaspa and helping bring it to the world.
The technology speaks for itself.
The community keeps growing.
The adoption continues.
To other exchanges: What are you waiting for? 👀
#Kaspa
hello again. the devs made things this week and i made a list.
1 / Rusty Kaspa v2.1.0
nodes now download sync data in smaller chunks to avoid bottlenecks and timeouts while catching up with the network. v2.1.0 also includes Stratum bridge fixes and moves the existing zero-knowledge proof tools into their own package.
https://t.co/WzHdJGh4qo
2 / vProgs
@Max143672 announced the first vProg running on testnet. it’s a playable tic-tac-toe game with real execution and settlement. still a working proof of concept, with public code for devs to build from.
https://t.co/P9wYRkkcMx
3 / Python SDK
@smartgoo_ released Python SDK v2.1.0. devs can now compile SilverScript contracts in Python and debug them without running a node. it also adds tools for using zero-knowledge proofs, examples and bug fixes. SilverScript support is still experimental.
https://t.co/yYkw11hhop
4 / SilverScript Studio
@KasperoLabs announced SilverScript Studio is live on mainnet. build, compile and deploy covenants from your browser. write them yourself, describe what you want to its AI, or use the wizards for things like vaults, escrow, recurring payments and payroll.
https://t.co/pXKUP3Ob4l
5 / KCC23
@manyfest_ explained a proposal for linking details like token names, symbols and images to a covenant, without copying them into every holder’s coins. KCC23 is still a draft and open for review.
https://t.co/Tk4rGZxJjN
6 / KCC standards
@asaefstroem’s proposal to finalize KCC0 was merged. it sets out how shared ecosystem conventions are proposed and reviewed. he also proposed moving KCC20 into last call review. that hasn’t merged, so KCC20 is still a draft.
https://t.co/48shGa9eNJ https://t.co/u1SKQvgPOk
7 / DNS seeder
@supertypo_kas released DNS seeder v0.9.6, fixing a bug that counted some offline nodes as online.
https://t.co/2MvdLFDHF9
thanks to everyone building. see you next week.