
I pitch $KAS because of its core-technology: Evolving nakamoto consensus into a highly scalable worldwide currency. Join: @kaspaCurrency
Joined May 2009
- Tweets560
- Following288
- Followers228
- Likes516
The first book about vProgs 😳
That reminds me, I should likely continue with the regular hangouts so they can actually become a "regular" thing, now that I am better again 😅
I finally wrote a book that covers vprogs, and in particular tic-tac-toe implemented as a vprog on testnet-10. It follows the game down to the machinery underneath, with diagrams and appendices for the details. Welcome to explore it and ask questions: biryukovmaxim.github.io/vpro…
Petridish 𐤊 retweeted
SilverScript Studio is now live on mainnet.
Write Kaspa covenants by hand, with a wizard, or by describing them to an AI that speaks only SilverScript.
Deposit and withdraw with your own wallet: Kasware, Kasla, Kastle (Kastle to deposit; signing support is coming).
Multi-signer covenants get a link the other parties sign from.
silverscriptstudio.com
Petridish 𐤊 retweeted
Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday.
You can play it here: vprogs-tt.izio.fr/
(Requires private key and some testnet funds)
We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately
I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top
For Devs: this is the invitation. Play the game, read the code, build your own vprog.
Game code: github.com/biryukovmaxim/vpr…
vprogs framework: github.com/kaspanet/vprogs/t…
Petridish 𐤊 retweeted
Replying to @BlackRock
“...always-on rails built for high-frequency, low-value payments.”
i think ai’s need more than that. they need an ai-native programming language for dynamically expressing and composing logic on demand, so they can form cheap enforceable “covenants” with each other. they need fast rails where multiple parties can enter those agreements atomically.
eg an agent could assemble several agents it neither knows nor trusts for a one-off job, generate custom rules for contribution, success and payment, and have everyone enter the agreement atomically. once settled, the agreement can simply disappear
Petridish 𐤊 retweeted
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa.
This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript.
I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
Petridish 𐤊 retweeted
It's been fun chatting with @Sehgal_ankit about Toccata, covenants and Silverscript
🚨 NEW Episode w @OriNewman "How Kaspa Wins Over FIAT"
00:00 Why kaspa:native needed covenants
06:34 Why SilverScript
13:47 sCrypt, CashScript and OP_CAT
16:00 #Bitcoin's accidental covenant
22:16 KIP-17: state inside a UTXO
30:54 KCC20, CAT20 and the lineage attack
37:37 CovenantID, and If Toccata affects your wallet
46:03 Thousands of lines to 60 with @IzioDev
53:39 Posts by @hashdag and @michaelsuttonil
59:28 Competing with bitcoin:native
--------
DISCLAIMER This video is for educational and informational purposes only and is NOT financial or investment advice. We do not recommend you to buy or sell any assets. Opinions of guests are their own and do not constitute endorsements. Cryptocurrency and blockchain investments are highly risky and can result in total loss of capital. Do your own research and consult licensed professionals. The channel and its hosts are not liable for any investment decisions or losses.
MORNING MOTION: GoPro is RUNNING, everything is going onchain, chatting KAS & ZEC xitter.cf/i/broadcasts/1nxeLMnme…
Petridish 𐤊 retweeted
What an exciting day!
An ai-era compiler developed at ai-era speed while maintaining super-high quality
Seven months since the first commit, and after an extensive review and standardization process (thanks to @manyfest_,@iziodev,@michaelsuttonil and @asaefstroem), I'm publishing a release candidate for Silverscript v1.
The last merged PR was written by @michaelsuttonil and numbered #235, which is a nice reminder to the fact that Silverscript started as my (someone235) project and is now becoming a project involving the entire Kaspa community.
You can find a link to the release candidate in the reply, and I'd love to hear the community's feedback. If we don't receive any substantial feedback, we'll release Silverscript v1 for mainnet use one week from now.
Petridish 𐤊 retweeted
life is interesting @ kaspa core r&d
one day i find myself prepping a deep dive + roadmap for DK
the next i help review and final-edit three KCCs
and on the third i do this (help harden silverscript + sync argent):
Petridish 𐤊 retweeted
PSA on Silverscript:
I found two bugs related to time-locks:
1. The units of `tx.time` were wrongly considered as seconds, rather than milliseconds (as Kaspa consensus considers them), which means all timestamps were divided by 1000, making any timelocks effectively irrelevant.
2. this.age units were wrongly documented as seconds, and not DAA score.
I fixed the bug, renamed this.age to this.ageDaa to make the time units clearer from the context, and added a new temporal type that will help with compile-time safety. For more details, see the relevant PR in the comment.
I remind everyone that Silverscript is still in pre-release mode and is undergoing an extensive review process before v1 will be officially announced (which should happen soon enough), until then, it's still recommended to avoid using Silverscript in production.
Petridish 𐤊 retweeted
Nice to be back home after 8 days of intense devving sessions with several contributors to Kaspa’s core development, some of whom I had never met before. We exchanged a l o t of information and brainstormed different paths forward and their tradeoffs across several parallel topics.
On a personal level, my public coding activity was somewhat on hold during this period, including Argent progress and coding sessions I wanted to do (and share via @KaspaNative). My next few weeks will center on initiating the DK group effort -- with several ppl joining @coderofstuff_ in his already long journey deep in the trenches (actually, @FreshAir08 is already deep in as well with a very promising incremental cascade-voting algo). Alongside that, I’ll also find time to move Argent towards a release and perhaps take a more active role in helping the ongoing covenant-related spec & conventions work (KCCs) converge
Petridish 𐤊 retweeted
To busy to share stuff live but really excited about this week-long meetup we have going on “somewhere in Europe” like @hashdag says. DK, P2P, vprogs, silver & argent, fascinating ppl, great food, what not. Kaspa has a bright future bcs it has many dreamers with far-reaching vision and execution capabilities behind it. Let me just put it that way.
Petridish 𐤊 retweeted
Alright, the first working version of the Kaspa Change-O-Matic is ready!
#Kaspa
Petridish 𐤊 retweeted
🚀 LIVE NOW! Witness the #HardFork #Crescendo – #KASPA TESTNET 10 unfold in real time! 🔥⚡️ Will this change the game? Join the chat and be part of history!
🎯 Tune in and join the discussion!
🔗 Watch now: youtube.com/watch?v=p2gNA4qi…
#Kaspa #Bitcoin #Ethereum #Solana



















