why I’m personally excited about Kaspa’s upcoming Toccata covenants
- for the first time, I can build creative, complex apps directly over infrastructure I helped design and build
- we designed under architectural constraints, but the result came out surprisingly expressive and powerful
- Silverscript is cool as hell
- I can literally open a *.sil file and write a complex contract that will be fully verified on Kaspa L1
- (nottoself: create a 10-minute video showing the building of such an app e2e)
- I can design my own vaults and safeguards, and manage funds securely without risking a heart attack each time I touch a wallet
- covenant ids, contract templates, and inter-covenant communication (ICC) feel like a new set of axioms, or a new algebra to work with and discover
- sig verify from stack / sighash anyone-can-pay + covenant ids can allow interesting shared-state covenants (requires a non-consensus miner policy; kudos to @maxibitcat for pushing this line of thinking)
- complex contract systems can be deployed in one spk hash. no storage rent, no deployment tax; users pay only the transient mass for tx data as they use it
- as I’ve mentioned in the past, this becomes especially interesting for AI/agentic environments, where bots could cheaply create one-time agreements between themselves
- I didn’t even mention based apps yet. That’s a whole vertical that isn’t ready for exploration yet, but will be very soon
@iboQuai@ShalomOnKaspa#kaspa doesn't scale with L2. Currently the L2 is for EVM. Kaspa will have native programmability starting this month with the basic framework
@iboQuai@ShalomOnKaspa Crypto a a whole is still very niche and need time to build and gain adoption. Quai isnt doing anything ground breaking. Zilliqa used to be sharded POW many years ago, it didnt work out. #kaspa scales without the need for sharding.