it’s exciting to watch y’all starting to realize (as well as actually realize/build) what can be built on post-Toccata Kaspa

just to be clear, there’s a lot going on across many fronts. it’s just not helpful to talk about things before they happen; they simply need to happen, and serious things take time. some serious efforts also won’t necessarily mature for various reasons, which is another reason ppl don’t always lay out their plans publicly (until they happen). i anticipate something of a “baby boom” in a few months, but teams will simply pursue delivery rather than talk

I want, perhaps for the first time ever on this platform, to write a post from a personal perspective. This post isn’t going to address any other person, and as such, I would appreciate not receiving any sharp-tongued comments or personal remarks about any particular case. Read the post as it is, or ignore it. Please respect my personal request, at least in this one instance, even if every fiber of your being rebels against what you perceive as an injustice. For the last three years, my entire sphere of activity, the one that consumes all my time and energy, has been Kaspa. The development of Kaspa. The research of Kaspa. Where the coin is today. And which line of code will run tomorrow. I don’t work on Kaspa to become a rich man. My life’s goal is not to make a lot of money and retire. I enjoy fundamental, deep research in computer science, and I am especially thrilled when I have the privilege of applying it at scale in the real world. I believe I have the right to claim that I care about Kaspa as a collective. I care about the whole that is greater than the sum of its parts. As a person of faith, I believe I have been granted the privilege of being a conduit for some of the science that constitutes Kaspa. For the discovery of this science in the world. And for its complete implementation. Along with this privilege comes great responsibility. In Kaspa’s first year, I was under constant stress. Returning from any weekend or period of disconnection was met with the feeling that anything could happen. All hell could break loose. The pounding of my heart at the crescendo moment didn’t subside for weeks. At a certain point, as a lead developer and researcher, you discover that your responsibility extends beyond the technical domain. That as a creator and, in effect, a continuous founder of the technology, you have a growing responsibility for the proper communication of this thing you are an essential part of creating. We are, admittedly, in a decentralized open-source community, but the creation process ultimately comes from specific people, and no one else can authentically reflect the essence of the creation and its strengths more than those who continuously forge the path itself. This responsibility is both a community and a project-level one. You find yourself in a situation for which your academic degrees did not prepare you. Luckily for me, if you were to tell people who know me in my personal life that I only understand zeros and ones, they would find it deeply amusing. Until a few years ago, I actively managed a social media community of thousands of people that led and was part of a social change. Anyone who knows me or has even worked closely with me will tell you that my emotional intelligence is no less than my intellectual one. With great responsibility comes the capacity for error. I can be wrong. Like any human being. But I ask here for the right to a minimum of respect and appreciation for my integrity and the purity of my intentions. I have no ego when it comes to Kaspa and its creation. And I am happy (and actively working) to share in its future creation and to give credit for the past to all who deserve it. Every action I take within the Kaspa space stems from my belief that it is for the good of the project. And from my belief that although I am primarily a researcher and developer, I have an angle and a complete perspective on the project that is nearly unrivaled. Sometimes, you are deeply and intuitively convinced of something, but it takes time to clearly articulate the crux of the problem and the argument. And still, the urgency mounts, and so you are forced to act. And when you try to explain your reasoning to people without the full context, you only manage to reflect fragments of ideas that don’t always connect for the perplexed observer and sometimes even seem contradictory. If, for example, I wrote a line about Kaspa’s market value and you believe it could be interpreted in a personal, unfair manner, do not attack and sting me based on your wrong assumption. Ask honestly what I meant, and you might be surprised by the answer. (In that specific case, I was speaking about my assessment, and that of others smarter than me, that a fundamental change in Kaspa’s social media presence is required for us to break through in the market cap rankings towards the top ten. I wasn’t referring to the price noise of the past year, nor am I influenced by it. I operate under the complete belief (a kind of knowing) that Kaspa will reach its rightful place in terms of market weight. I also didn’t blame any individual. I spoke of a perception and an approach that, in my view, have a glass ceiling. And I prioritized the common good, as I thought and felt that this truth needed to be heard, even if there are individuals for whom it could be interpreted as criticism.) In the same vein, and as in the example above, so it is with every community and social action I’ve taken recently. You can, of course, argue and believe that I was mistaken; that is certainly a possibility. But I ask to be given the credit that I, at least, believe I am doing the right and critical thing for the Kaspa community and project as a whole. And that I have a basic social and philosophical analytical ability that grants me the right to my own opinion in these areas as well, even if I am mainly a developer and researcher who deals with abstract combinatorial ideas and code. I don’t have to be a marketing expert to express a crypto-philosophical opinion on the source and authority of core ideas for something that I am a continuous part of creating. Thank you for reading this far. I sincerely appreciate it. My next post will be out tomorrow, and it will discuss something cool and immediately relevant to Kaspa that myself and others have been working on these past few days. After that, or at least in the near future, Yonatan or I, or both of us, will try to outline Kaspa’s roadmap for the next one to two years, up to the achievement of zk/dk.

argent now has a first implementation of covenant genesis proofs: github.com/argent-lang/argen… idk how to emphasize this enough, but i expect *every stateful covenant* deployed on kaspa to eventually provide such a proof. the goal is a verifiable link from a covenant id back to the source code, deployment parameters, and genesis state that produced it. we should strive for an ecosystem where explorers expose this proof data for every covenant id they discover onchain, assuming its deployers want public trust. think of it as the analogue of contract verification on etherscan, extended to stateful covenants: you should be able to inspect what a covenant is, audit the code behind it, and verify how it was instantiated. kudos to @supertypo_kas for being an early-bird example of such a proper deployment process: github.com/supertypo/dotk-in… (not sure if the sil contracts themselves are public yet)