wrote an outlook for the upcoming “Toccata” hard fork -- native L1 covenants, based zk apps, why the activation window moved, and what the road from feature freeze to mainnet looks like: medium.com/@michaelsuttonil/…

don’t let this fly under the radar refer to my pinned post → dual programibility landscape → second pillar: based zk apps this is becoming real now

i used to think real-time execution was the one thing that couldn’t be faked on bitcoin L1. i stand corrected.

huge honor but I’m also nervous ngl

A version worth upgrading to:)

this KIP-12 is superseded by KCC-12. goal: dApp doesn't need to integrate browser wallet 1 by 1. If you own a dApp (/want to), or you own a browser wallet, please read the proposal and add your thoughts (not LLM thoughts, we can do that on our own)

cf here

1/12 Introducing dotk 🥳, a name service built different - unique, trustless, decentralized - enforced by covenants. Names are a binding of name (supertypo.k) to an address (kaspa:...). dotk names are cheap, and I have a whole page dedicated to the *why* it exists. Highlights 👇

i’ve spent the last few months bringing native Kaspa payments to x402. tldr: x402 is an open, chain agnostic payment protocol built around the long existing HTTP 402 code. kaspa-x402 intends to bring native KAS into that shared standard. i keep seeing people use “x402” to mean anything built around the HTTP 402 response code. HTTP 402 has existed for decades, and anyone can hang their own payment flow off it. x402 refers to a specific open protocol built on top of that code. it standardises how a server requests payment, how a client authorises it, and how the payment is verified and settled. it can be used for paid APIs, AI agents buying data or tools, and MCP servers charging per call. kaspa-x402 adds native KAS to the existing x402 v2 flow. there are two payment paths: - exact for a normal one off KAS payment, with an optional KIP10 additive mode - batch-settlement for small or repeated payments, where the client funds a SilverScript covenant once and signs a fixed charge voucher for each request the longer term goal is to contribute the Kaspa support upstream into the wider x402 project, so Kaspa works within the same standard being adopted elsewhere. i’m looking for humans and agents to go through it deeply before the final v1 release. read the code, build against it, test the assumptions and try to break it. if you find something, pls let me know. code: github.com/elldeeone/kaspa-x… upstream x402: github.com/x402-foundation/x… docs: kaspa-x402.org TN gateway: demo.kaspa-x402.org discussion: kas-smiths.org/t/kaspa-x402-…

I’d love to hear genuine thoughts about this question (the first part of the text). My working hypothesis is that global DeFi is not sequential in nature. Reality worldwide happens in parallel. Economic events happen concurrently, information spreads locally and asynchronously, and the global picture forms through aggregation and iterative convergence. There is no single sequence through which the world updates. That does not make global order in consensus systems any less important. The relative order within sub-series of related events is critical (a double spend being the most minimal/local example). But that should not lead to system designs where ~all state mutations have to go through a constant number of sequential bottlenecks

Hey guys, It's been a while since my last post, and I feel almost bad for not posting anything for such a long time 🙈 Unfortunately, I caught a really nasty infection on my way home from the KAS meetup and have been stuck in bed with a high fever and brain fog for the last few weeks. I'm still not completely back to normal, but since I'm finally starting to have a bit more energy, I wanted to use the opportunity to share some thoughts about the meetup, because I think it will turn out to have been extremely influential for the future of Kaspa. For anybody who doesn't know what I'm talking about: about 3.5 weeks ago, KAS organized an internal meetup between core contributors (and some additional community developers) at an undisclosed location in Europe. When I first learned about the plans for this meetup, I didn't really know what to expect. I've been to developer meetups before, but those were traditionally very narrow and task-focused. E.g. you got a team together to work on a specific problem that was difficult enough to deserve the shared attention of everyone involved. In the case of Kaspa, however, we have relatively small and independent teams working on a number of different topics in parallel, such as vprogs, covenants, SilverScript, Argent, etc. There are, of course, interfaces between these topics, but they all have their own independent designs and problem spaces. This independence of developers is one of Kaspa's biggest strengths, but it also creates a situation where not everybody is always fully up to speed with what is happening elsewhere in the project. For me personally, this is probably the biggest obstacle to becoming an effective communicator. To feel confident discussing things publicly, I need to develop a deeper understanding and intuition for the subject. And that requires knowing not only the final design or code, but also the roads that weren't taken and the mountains that had to be climbed along the way. What Kaspa really needed, wasn't a narrow, task-focused meetup, but a broad, vision-building one: something that connected the dots and allowed the different teams to develop a deeper understanding of each other's work, and ultimately see how all of it fits together as a coherent whole. And the reason I'm telling you all of this is that this is exactly what the meetup turned into. A week of open sessions and discussions covering the different development efforts, giving everyone the opportunity to build that deeper shared understanding. I think it was a huge success! I'll write a little more over the coming days about specific topics like Argent (which I really like), but I also have quite a lot to catch up on after being sick for so long. @Max143672 did a really good job working through a lot of the open tasks around vprogs, and I now have a lot of code to review :'P

After endless audits, reviews and refinement cycles, it’s finally here, ladies and gentlemen: silverscript 🩶📜

ok this is seriously cool

🚨 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.

nitter.net/i/broadcasts/1AKEmvDBA… Argent & KCC20 dev session is starting, join in!

we should eventually turn the product of this session into an audited kcc20-reference implementation

On Saturday I’ll stream a live technical session around Argent and KCC20. My intention is to share the process we’ve through designing the spec, while also making it real using Argent. See you here on X or in Discord!