Gray Wind

$kaspa 共识协议 #Phantom #GHOSTDAG 已完成Ⅰ-Ⅷ部分的翻译。🥳 此部分为论文主要部分。 翻译件已上传Google Cloud：drive.google.com/drive/folders/… 另外，若想要阅读DAG KNIGHT协议翻译件，可在drive.google.com/drive/folders/… 中获取。 @kaspaChinese #Kaspa

@binance, Thanks for including me in the top 100 blockchain people list, appreciate the signal! I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out. Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed. There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <> A TBTF CEX should know better and play a different game with hardcore crypto projects. When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement. You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog? Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point. @cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity. Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto. We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes. Please fix this. Thanks again, hashdag cc @michaelsuttonil Exhibit A: Binance Innovation Zone Exhibit B: 10 bps Nakamoto Consensus

Kasplex zkEVM: Smart contracts arrive on Kaspa Layer 2 Kasplex, in collaboration with the Kaspa Ecosystem Foundation (KEF) @Kaspa_KEF , has officially launched its zkEVM Layer-2 mainnet, bringing Ethereum-compatible smart contracts to the Kaspa network. This launch represents more than just a technical achievement. It’s the first time that programmable dApps, DeFi protocols, and complex smart contracts can run on Kaspa; an ecosystem known for its ultra-fast, Layer-1 proof-of-work blockchain. For developers, it opens a brand-new design space; for the Kaspa community, it’s a leap into decentralized finance, tokenization, and beyond. Background: The foundation laid by “Crescendo” Kaspa’s Crescendo hard fork, activated on May 5, 2025, was a historic milestone for the network. Internally labeled v1.0.0, Crescendo was the culmination of years of research into blockDAG scaling Kaspa’s unique consensus innovation that allows blocks to be created and confirmed in parallel. Key upgrades introduced with Crescendo include: • Block rate increase: Kaspa’s throughput jumped from 1 block per second (BPS) to 10 BPS, multiplying raw network capacity by a factor of 10. • Transaction ordering improvements: Ordered transaction execution was made possible; an essential prerequisite for any Layer-2 that relies on determinism in state changes. • Layer-2 readiness: Protocol updates for latency reduction, parallelism, and data availability ensured that Kaspa could support zk-rollups and other scaling solutions. • Developer foundations: By upgrading the underlying infrastructure, Crescendo essentially “primed” Kaspa for programmable logic, while retaining its hallmark instant confirmation and finality. Without Crescendo, Kasplex would not have been possible. It transformed Kaspa into a foundation ready for programmability at scale. What Is Kasplex zkEVM? Kasplex is the first zkEVM rollup deployed on Kaspa. Kasplex inherits Ethereum compatibility, meaning that developers can use the same tools they already know Solidity, Hardhat, Remix, Truffle, MetaMask without learning a brand-new development stack. Deployment is as simple as redirecting RPC endpoints. Some of Kasplex’s defining features include: • Gas in $KAS: Unlike most L2s that introduce a separate token, Kasplex uses bridged $KAS from Layer-1 as the native gas token. This preserves economic alignment and keeps value within the Kaspa ecosystem. • Bridging mechanism: A two-way bridge enables users to move $KAS from L1 → L2 to use in smart contracts, and back from L2 → L1 seamlessly. • Open node infrastructure: Kasplex offers three types of nodes that anyone can run, ensuring decentralization rather than limiting validation to a closed set of operators. This is more than a technical upgrade, it’s a strategic expansion for Kaspa: • For developers, Kasplex lowers the entry barrier: if you can code on Ethereum, you can now code on Kaspa. • For users, it means fast, low-cost DeFi, NFTs, DAOs, and experimental applications all secured by Kaspa’s proof-of-work Layer-1. • For the ecosystem, it’s the bridge to mass adoption: Kaspa goes from being a high-throughput Layer-1 to a complete smart contract platform. L2 Testnet: Key metrics & early performance Here are some of the notable statistics from Kasplex’s testnet since launch • Blocks generated: ~ 6.5 million (Kasplex does not generate empty blocks); blocks are produced only when there is payload to commit from L1. • Transactions: ~ 24 million • Unique wallets: over 300,000 • Throughput: over 1,000 transactions per second (tps) • Average block time: 0.9–1 (bps) These numbers speak to robustness, stability, and growing adoption. They suggest the system is performing well under load. Components Here’s how Kasplex is structured, and what its ecosystem includes: • Two-way bridge: Supports transfers from L1 → L2 → L1, so users can move $KAS into the Layer-2 environment, use them for gas/contracts, then exit if needed. kasbridge-evm.kaspafoundation.org • RPC / API: Full RPC endpoints supporting EVM-compatible calls evmrpc.kasplex.org • Explorer: Blockchain explorer for viewing transactions, blocks, and smart contract state on L2. explorer.kasplex.org • Chain ID: 202555 (this is the identifier for the Kasplex Layer-2 chain). • Token: $KAS • Official website: kasplex.org • Documentation: docs-kasplex.gitbook.io/l2-network • Layer 2 audit: github.com/kasplex/evm-l2… • Community: linktr.ee/kasplex What’s Next: Roadmap & Upgrades Kasplex is not static; several future developments are in motion: • KRC-20 (Kasplex’s token/inscription standard) will receive important upgrades before year-end. • A new EVM-Lua interface is in development that will allow for alternative smart contract languages or scripting paradigms. • Further Layer-2 functionality upgrades leveraging innovations from Kaspa itself (for instance, zero-knowledge proof improvements, “vprogs” or virtual programs, etc.). Why this matters: Implications for Kaspa & the ecosystem • DeFi readiness: Kasplex unlocks detailed smart contracts and composability, enabling AMMs, lending/borrowing, stablecoins, and all the tools of decentralized finance. • Developer onboarding: Because it’s zkEVM + Ethereum‐compatible, porting existing dApps is much easier. This will accelerate ecosystem growth. • Scalability with security: Kaspa’s PoW + blockDAG architecture combined with Kasplex’s roll-up design aims to maintain strong security and decentralization. • KAS utility: Using $KAS as the gas token helps retain economic alignment, not relying on an external token. Closing thoughts We extend our sincere gratitude to the Kaspa core developers, whose groundbreaking work made this possible, and to the Kaspa community, whose vision and energy continue to inspire us. A special thanks goes to all the teams and builders who tested their applications on the Kasplex testnet, providing invaluable feedback that helped shape the mainnet launch. Kasplex zkEVM is not just our achievement, it is the result of collective dedication, collaboration, and belief in what Kaspa can become. This milestone belongs to all of us, and it marks just the beginning of what we can build together.

Raw thoughts re Kaspa’s next big upgrade(s) You don’t end on a crescendo, and it is no secret that several anticipated upgrades are waiting on the sidelines for Kaspa. Primarily, the Dagknight (DK) protocol and the ZK L1<>L2 bridge. These two major endeavors may look independent, but I see strong merit in bundling them into a single hardfork (reasons below). I also argue this bundled effort is the right window to incorporate the foundational L1 changes needed to support ongoing research into MEV‑resistance and oracle‑voting. A word on deferring DK to this point. I acknowledge that per past statements we expected to be post‑DK by now. Context for the long delay: (1) after the Rust rewrite, moving from 1→10 bps (blocks/sec) was too natural a follow‑up to ignore, and I dove into ~1‑year of work there. (2) Strong community push for smart contracts; in the absence of formal committees planning the next phase we reasoned that prioritizing smart contract enablement would let a builder community form around the Kaspa app layer, and that unleashing this potential (and its ripple effects) would let us refocus on L1 perfection without bottlenecking ecosystem growth. This post provides a bird’s‑eye overview of active + upcoming Kaspa R&D efforts and sketches their relation graph. DK: Dagknight is a ’22 ordering‑protocol research paper by myself & @hashdag; it evolves GHOSTDAG (GD). A (mostly written) follow‑up post will deep‑dive DK across: - practical benefits / applications of its abstract “no a priori delay bound” property - a breakdown into four main components → raw development phases - broader system / consensus implications - applied research for efficient incremental algorithms (notably the cascade voting procedure) - protocol (and paper) relaxations / simplifications - “resistance to Internet chaos”: practical limits + engineering caveats ZK: In the past year, there has been an ongoing publicly visible effort to establish the landscape of ZK over Kaspa. The results of these efforts can mostly be viewed in Kaspa’s research forum under the L1<>L2 category. Kaspa’s approach is to support based ZK rollups, where “based” means the ZK layers / rollups / dapps fully commit to L1 sequencing—so L1 serves all three roles: sequencing, data availability, settlement. The base mechanisms to support this are largely established. The main area still under heavy research is atomic / synchronous composability (multi‑rollup transactions that land atomically). Explaining the vision and mapping current research there deserves its own dedicated post. Why bundle DK + ZK: Their technical complexities barely overlap, so development can proceed in parallel and merge cleanly. That’s the engineering case. There is also a safety case: we (strongly) conjecture DK yields faster practical convergence of total DAG ordering. Under normal operation the delta is likely inconsequential; under powerful attack attempts DK’s convergence could be much faster—possibly by orders of magnitude. Faster convergence of total order is especially valuable for smart‑contract systems that are highly order‑sensitive. This further strengthens the case for linking the two upgrades. Additional elements that should ship with them are support for reverse MEV auctions and oracle voting mechanisms (two of @hashdag’s ongoing research efforts with @yaish_aviv and @elimmea respectively; see his recent Sydney/HK talks), seizing the opportunity to address some of DeFi’s hardest problems using Kaspa’s unique structure. Once full smart contracts are live we will inevitably inherit the MEV + oracle weak spots seen elsewhere. By making a few minimal, high‑leverage consensus changes now, we can “apply the remedy before the blow”. Engineering cost here is negligible relative to DK + ZK while ecosystem upside is large. Here is how we can approach each: MEV. Proposed approach: reverse auctions in which miners offer kickbacks to users for transaction‑ordering (or bundle) rights. Kaspa’s parallel 10 bps DAG already produces intra‑round competition; formalizing a kickback path captures that value for users instead of private orderflow brokers. L1 requirements are small: add a canonical kickback route and a deterministic auction‑ordering rule in consensus (how to rank conflicting bids; details are still open afaik). Game‑theoretic refinements can follow post‑fork, but a base path should exist in my opinion. Oracles. The strategy for oracles is to leverage Kaspa’s high bps to enable a robust, real-time attestation network, with data aggregated from numerous miners each round. From an L1 perspective, the main consideration is whether to tie this system to PoW for greater security/sybil resistance. The practical step would be to add miner voting mechanics at the consensus level. This is a low-cost, preparatory change that provides significant future flexibility for L2 oracle designs. ————— Overall I expect dk/zk branches to begin landing soon in rk’s main repository. Looking forward to this turning into a beautiful decentralized open source coding voyage

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.

🚨Caravel Testnet Is Coming ! The ZK-Ready, DAO-Governed L2 Built by @Igra_Labs Igra Labs just dropped the roadmap + deep dive for their Caravel Testnet,packed with innovation Let’s break down what Igra is,who’s building it,and why it’s huge for $KAS 👇

Dear $kas community, this is a farewell. I have a lot to say. I'll start with the ugly, move on to the bad, and end with the good. ---------- I often envisaged telling my story in Kaspa once it was concluded, but I never imagined it would end with betrayal. In the span of two days, three people whom I considered friends and colleagues not so long ago have posted ugly, unfair, and misleading comments about me, with the clear purpose of undermining my integrity, the breadth of my contributions, and my character as a whole. I want to respond to these accusations, and I want the reader to notice the common thread -- poor communication. The accusation common to all three posts is an insinuation that I am trying to squander the title of "core". Yonatan said that I "misrepresent [myself] as Core dev", Michael talked about the fact that I am "perceived as a builder", and Eyal (who wrote the ugliest thing a someone I know in person ever wrote about me, by a far margin) states that "the question remains if he can embrace humility and contribute as any other dedicated Kaspian does, without the perceived status of a "core" member." So here's the thing: I do not present myself as a core dev. Haven't for a long while now. I correct people who address me as devs. I ask conferences and interviewers not to list me as a dev. When asked what I do for Kaspa, the short answer is "education and narration", and the longer answer will mention that I used to be a core contributor, and now I occasionally help when asked. People who have been around longer know that I always preferred to introduce myself in ways that do not affiliate me with any particular group or effort. Stuff like "Knows a bit about Kaspa", "unemployed at Kaspa", etc.. Even my X bio has had "ex $kas core" in it for weeks now, ffs. Moreover, I was always approachable and receptive to comments about how I present myself. And Michael knows that. For example, he mentioned "going on to represent Kaspa’s L2 design efforts way before they were clearly understood and communicated [...]". Maybe he should have also mentioned that he brought it to my attention in private. I agreed that the optics are misleading and immediately posted a clarification: x.com/DesheShai/stat… He acknowledged it as sufficient, said that we are "aligned", and even commended me for my readiness to accept criticism and adapt. This is an example of a phenomenon that is very rare in this post: resolving a disagreement by talking about it and reaching a solution together. Michael knows very well that, even when our relationship was very strained, he can always message me "I think you should post more explicitly that you do not consider yourself a core dev", and I would have done so gladly. I have receipts for that. He could have told me that he wants to post a clarification himself, but at least let me have a look and help him make the clarification balanced and fair. That is what made it so hurtful. Not the statement that distances me from "core", I think we've quite established that I don't really care about it. Michael's portrayal of the situation cast me in a very unfair light, making me out to be conceited, self-centered, and oblivious. Moreover, it was just unnecessary. Anyone with eyes can see that I am actively distancing myself from the core team. I changed my cover picture, added a very explicit "ex $kas core" to my X bio, and pretty much stopped answering dev questions altogether, moving forward to do my own thing. The videos I make carefully avoid any attribution to "we" or "us" that could indicate that I am a part of the dev process. I don't know what drove Michael to make this post, but I do not think it was malfeasance. Michael is not a vindictive person. What I do consider deliberate sabotage is Yonatan's reply. I hate to say it, but Yonatan is a vindictive man who is not above sabotaging those he feels have wronged him. He knew exactly what optics he was generating describing me as an "influencer and Youtuber", in a comment to a post that claims that I "don't know cryptography". What is Yonatan vindictive about? I stood up to him for the forceful way he facilitated the change in the X account. Not the decision to make the change, just the way it was facilitated. Yonatan's conduct hurt people, broke the community clean in half, and alienated passionate and long-standing community members. He could have achieved the exact same result without any of this, but he refused to communicate. I pressed on that, and got ostracized for it, and I have been facing vindictive behavior ever since, both private and public. This latest stunt is just the last in a sequence of deliberate unkind acts I have patiently gritted my teeth through while looking the other way. Eyal's post. Well, what a load of crap, which is what I'm used to from Eyal. But I have two unique grievances. One is how hypocritical he gets: The guy talks about my "vocal, aggressive, and often impulsive style" while writing a diatribe about me that is tenfold more toxic, vehement, impulsive, and cruel than my entire bibliography combined. Imagine writing a post like this about someone who is supposed to be your friend, who you know is already down, and post it publicly. And what was even the purpose? Is humiliating me supposed to be helpful? What did he try to achieve with that? But what I find truly insulting is the way he ended his lovely description of me: "albeit private conversations". This is not unfair wording, or biased framing. That is a simple lie. Eyal did approach me about my style. Once. I admit, I reacted poorly at first, for reasons that don't matter right now. But a few days later, I apologized and asked him if he still wanted to have that conversation. He said he is busy (getting ready for a conference) and he'll get back to me in a couple of days. That was more than two months ago, and it was the last time we ever interacted. I am sure that Eyal knew very well how inaccurate, unreasonable, and downright demeaning some of his statements were. Maybe that's what he wanted. I again stress the common threads here: failure to communicate and lack of integrity. A lot of people asked why we don't solve this in private. My only answer is that I tried, but there was no cooperation. That being said, what stung the most was that none of these people congratulated me on my wedding. ---------- Like every cake needs a cherry, every recent Kaspa shitstorm needs a Junny. Some background: A while ago, I was given a monthly grant from KEF and Kasmedia to write a book about GHOSTDAG and Kaspa, based on the stipulation that the grant would be paid for a period of one year. Halfway through, both Kasmedia and KEF decided to pull their funding. The payment was cut, and so was the work. Junny tried to downplay the quality of my product by describing what I produced as "two chapters in a rough draft state". In reality, I wrote about 40k words and created about 150 illustrations, which total in 200-250 pages. The reason for Junny's mistake is that he was looking at the new book website, which I created after the deal ended. I am in the slow process of migrating the book from the Kasmedia platform to the new site while heavily editing it. So far it only contains a half of what was published. So it only has about half of what was published. Having said that, here are a few posts from that website. You tell me if they merit the description "rough draft": shai-deshe.gitbook.io/understanding-… shai-deshe.gitbook.io/understanding-… shai-deshe.gitbook.io/understanding-… I think the work speaks for itself. But what's more important is the unpublished part. You see, I completed one part about abstract blockchains, and another part about abstract blockDAGs, and then came the most important and sensitive part: how GHOSTDAG is efficiently implemented in Kaspa. This is a complicated subject with a lot of interconnected moving parts, making it very challenging to find the correct order of introduction. As I worked on it, I kept having to reorder things. Up to this point, I would divide each chapter into small parts and post them as they are completed, but here I decided to go with a different approach: write the entire thing and publish it at once. And writing this thing is hard work. I'll let the work speak for itself. It has missing parts, it was not reviewed by anyone but me, and it needs quite a few layers of polish. And still, it is the best damn documentation of how GHOSTDAG is implemented you could find, and the only documentation of reachability queries: kasmedia.com/article/unders… Just imagine if we had this level of documentation for all central components of Kaspa. How it would benefit productivity. How easier it would make being a builder on Kaspa, especially a new builder. That was the plan, and it would have been very close to completion right now if KEF had just. let. me. finish. So does Junny's description align with reality? You decide. And Junny, if you are reading this: you are the worst person in the Kaspa community. You are a blight. So many bad things that happened can be traced back to the terrible business and conversation culture you brought into this community. The best thing the Kaspa community can do is to have you exiled to St. Helena, and they would have had they known how divisive your business practices are. Keep writing your cutesy little slander tantrums, keep trying to convince people that I "don't know cryptography", that I can't write a book, that I'm a KOL. These posts won't help you, you know. You will never be a real boy. ---------- Now, for the community as a whole. In the last two months or so, I made extreme efforts to steer clear of controversy. Despite very unkind comments made about me by Yonatan, Michael, Junny, and others, I decided to lay low and keep doing my thing. I thought the Kaspasphere was big enough for all of us, that if I ignore them, they will eventually relent. But then this three-pronged attack happened, and I just couldn't take it lying down. "Surely," I thought to myself, "the community will understand, and not stand for this injustice". I was wrong. Seeing the reaction to this character assassination made my heart sink. Seeing so few people saying "guys, what are you doing? This is insane", calling them out for the injustice. What I saw instead was people I cared about being indifferent, community members whom I spent hours and days of effort on -- answering their questions, writing posts they requested, slaying FUD -- lambasting me, mocking my appearance, belittling my work, analyzing my personality, etc.. The community ate me alive. And this is why I do not want to be associated with this community any longer. Because if I'm something, it is a man of principle. And it is against my principles to belong to a movement that eats its own. ---------- OK, that was the ugly. Let us briefly go through the bad so we can reach the good. So what does this practically mean? Essentially that I will not volunteer any of my time or resources to help Kaspa. All related X activity (including any heated discussion the current post might beget) will cease. I will not represent Kaspa on any media or platform. Interviews, AMAs, FUD slaying, educational posts, all that stuff. I will be leaving almost all social channels related to Kaspa. I am the owner of the main TG group. Due to F2A annoyances, I will not be able to leave it in the coming week (without deleting it). I will mute the group and after the week is done, transfer ownership to @LiberatedPotato and leave. I am not going to disappear from the Kaspa ecosystem or abandon any project I am involved with. I still enjoy Kaspa as a technology, and I dedicated many years to building my expertise around it. That's not a resource I am going to let go to waste. I'd say that Kaspa used to be my life, but now it's just my job. Want me to slay a fud or write a post? DM me, we can discuss prices. My content making will remain unaffected. And yes, I will still be producing content about Kaspa as I wish. I still adore Kaspa as a technology, and have a lot to say about it. ---------- OK, time for the good. First and foremost, I still have every faith that Kaspa will be a huge success. It is a uniquely good project, the only one of its kind, destined for great things. All these petty squabbles will be forgotten by history very soon, but Kaspa will prevail. I agree with Michael's assessment that Yonatan is one of the three brightest visionaries in all of crypto. My own assessment is that Michael is one of the three brightest devs in all of crypto. With these two guys at the helm, Kaspa is going places. Especially if they work on their communication issues. And it definitely doesn't end with these two. The Kaspa developer community, especially the Rusty Kaspa team, is packed to the brim with raw talent. So no, I will not be selling. While the ungratefulness of some people sank my heart, it was lifted by the kindness of others. What carried me through this is the absolute barrage of support messages and posts. It is humbling to see so many people lining up to share my impact on their lives, or rage with me, or offer advice, or tell me about themselves, or just express simple gratitude. Some people sent photos of their cat. This support didn't just lift my spirit, it is a constant reminder that I can still do great things. It is empowering to know there are so many people across the world who feel for me, appreciate me, and like me as a person. This inspired me to create a TG group for people who want to be in touch. We can be our own small community (assuming anyone joins): t.me/+91AxjMfbecdlN… Bye $kas, it was fun (until it wasn't)

My prophecy: Kaspa core will keep researching, budling and delivering. Yonatan will continue to lead it in terms of vision, far-reaching long-term research and short-term endless day-to-day brainstorming. Core R&D will continue to scale and expand to wider and wider circles. Builders and developers will keep joining L2 testnets and build dapps which utilize Kaspa’s inherent superiorities. Kaspa’s marketing will decentralize more and more. There will be no central voice. As part of the many voices, core members will find ways to communicate their vision and nuanced discussions to the broader crypto community. Truthfulness will prevail. Kaspa core will identify with people who actively contribute, build, research and think about Kaspa from the moment they wake up until the moment they fall asleep. Educators, pedagogues and evangelizers will do what they do best and communicate at different levels based on their knowledge and expertise. I will keep researching, thinking, developing and posting about Kaspa and speak as directly, accurately and truthfully as I can. I love you all (not a prophecy). We just started.

Kasplex will officially launch its L2 public testnet $kas this month, this is a huge milestone ahead of imminent mainnet. This release introduces full EVM compatibility, a working faucet, and a growing set of developer tools, enabling builders to deploy smart contracts and test DeFi protocols in a live environment. The testnet is not just a preview, it’s a critical phase for stress testing the network under real conditions. We invite builders, infrastructure developers , and early adopters to actively engage, experiment, and help us push the limits of performance and reliability. As expected with any testnet, small bugs or brief downtime may occur during ongoing upgrades and fixes. Your feedback during this phase is invaluable as we refine and finalise the Kasplex platform. Please feel free to share it directly on our Telegram channel. Mainnet is approaching rapidly. Finally: this couldn’t have been achieved without the 24/7 work done by our dedicated team. Here’s to new beginnings!

72 hours to a big crescendo moment in permissionless distributed systems, showing that a multi-leader consensus real-world system can achieve block times shorter than global internet round-trip time (RTT) without artificially suppressing the P2P network size or assuming proximity

We are thrilled to announce that our DevNet for ZkEVM is now live! This marks a major milestone for the $KAS ecosystem and our community, unlocking new possibilities for innovation and development. A public testnet will be announced at a later date, but if you’d like early access to the DevNet, please fill out the form below. We will grant access to those eager to explore, test, and build using Kasplex’s solution. docs.google.com/forms/d/e/1FAI…

@DesheShai Is there any sdk in rusty-kaspa to support traversing blocks according to block height?

Any questions?

Are 🫵 BULLISH on $KAS ???

Almost done with the realization of this KIP in bits and lines of code. So many details and so much responsibility, but we’re almost there

@LiXianyu4869 gbp走fps也很快，手续费2.5gbp

刚刚试了下这个，wc 秒到，我要去仔细了解这个是啥了

Dropped a technical post on L1/L2 design, atomic composability, and other discussions Atomic composability sounds like a nuance but it's vital for ensuring defragmented unified shared-state which doesn't force users, devs, LPs to work in isolated rollups research.kas.pa/t/atomic-compo…

OPEN LETTER TO COINBASE Subject: Request for Transparency and Fair Listing Practices for Kaspa (KAS) on Coinbase As a foundation dedicated to promoting Kaspa (KAS), the Kaspa Industrial Initiative (Kii) is writing this open letter to respectfully request clarification regarding the status of KAS's application for listing on the Coinbase platform. This letter also serves to inform the Kaspa community of our ongoing efforts and to address broader concerns in the cryptocurrency space about fair listing practices and transparency. We acknowledge Mr. Armstrong’s November 2nd, 2024, tweet claiming “free listings“ . However, this contradicts public reports of substantial listing fees, raising serious questions about potential material misrepresentations under securities law. This lack of transparency erodes trust and necessitates a clear and forthright response from Coinbase. Despite Kaspa’s repeated attempts to engage with Coinbase, no response has been received to date. The timeline of the attempts includes: • October 7, 2022: Initial introduction of Kaspa and correspondence with Francisco Esqueda at Coinbase. • October 11, 2022: Coinbase Asset Hub questions submitted. • January 8, 2023: Formal application submitted via Asset Hub (screenshot confirmation available). • Date approximately one month ago: Resubmission of a revised application. Mr. Armstrong’s public call for applications and invitation to “drop us a note”, even after our initially fruitless earlier requests, encourages the KAS community and us to reiterate our request for a Kaspa listing. We strongly suggest that Coinbase evolve its Asset Hub process to be genuinely inclusive of all legitimate cryptocurrency projects, regardless of their organisational structure. Currently, the requirement for information inherently unavailable to truly decentralised projects like Kaspa and indeed, Bitcoin itself—creates an uneven playing field and undermines the core principles of decentralised cryptocurrency. This structure risks inadvertently favouring venture-capital-backed initiatives, potentially stifling innovation, limiting consumer choice, and raising legitimate antitrust concerns. We urge Coinbase to take proactive steps to address this systemic issue and create a more equitable listing process that reflects the diverse and innovative landscape of the cryptocurrency ecosystem. KAS is a prominent cryptocurrency: • Top 30 Cryptocurrency: KAS consistently ranks among the top cryptocurrencies by market capitalisation. • High Transaction Volume: KAS demonstrates impressive transaction throughput, showcasing its practical utility. • KRC-20 Token Standard: The recent launch of KRC-20 expands the KAS ecosystem and fosters further innovation with many innovative projects launching on it. • Block-DAG Technology: This unique technology offers significant advantages in scalability and efficiency compared to traditional blockchain architectures. Kii firmly believes that a Coinbase listing would significantly benefit both the Kaspa community and the broader cryptocurrency ecosystem by providing greater access to this promising technology. Kaspa, with its unique blockDAG architecture, offers compelling advantages. It consistently achieves extremely high transactional volumes, significantly outperforming many established PoW cryptocurrencies. Its robust and active community of over 400,000 members across various platforms demonstrates organic growth and fervent support, vital indicators of a project's long-term viability. In the interest of clarity and fair practices, we respectfully request the following from Coinbase, including a formal meeting to discuss these critical issues: 1. Application Status: A detailed and transparent update on KAS’s application, addressing the reasons for the extended silence and acknowledging the documented communication attempts. 2. Listing Process Transparency: A comprehensive explanation of Coinbase’s listing review process, timelines, criteria, and a direct address of community concerns regarding listing fee discrepancies and the discriminatory nature of the Asset Hub requirements for decentralised projects. 3. Specific Concerns Regarding KAS: If any specific concerns prevent KAS’s listing, they must be clearly articulated to enable the Kaspa community to address them. 4. Listing Criteria: A complete and detailed explanation of all listing criteria employed by Coinbase is required to ensure transparency, trust and fairness. Kii and the Kaspa community are committed to building a transparent and trustworthy ecosystem for decentralised projects. We look forward to a constructive response from Coinbase and a meeting to address these critical issues. Listing KAS presents a mutually beneficial opportunity for both Coinbase and the Kaspa community, driving increased trading volume and expanding access to a thriving and innovative ecosystem. Sincerely, Kaspa Industrial Initiative (Kii) @brian_armstrong @KaspaCurrency @Kaspa_KEF #kaspa @coinbase @Kaspa_HypeMan @elldeeone @cz_binance

Assets under consideration: $AERO $AKT $APT $AR $ARB $ATOM $CELO $CORE $DOGE $ENA $FET $HNT $ICP $IMX $INJ $JUP* $KAS $MNT* $METIS $NEON* $OM $ONDO* $OP $PENDLE $POL $PYTH $RUNE $SEI $STRK $TIA $TON $TRX $UMA $VET $WLD *Assets not included in our Crypto Sectors as of 9.30.2024

As a curious observer of the anticipated KRC20 load on Kaspa's mainnet, I prepared a mempool stats collector by customizing my local node. Although more data could have been collected with finer granularity, this is what I managed to compile just a few minutes before the launch on September 15th. In any case, I thought I’d share some of the raw data here as well. Full links to my code and a Jupyter notebook with self-contained data will be provided below. The first two figures offer an overview of the processing throughput, with the first showing the average number of transactions per block (TPB)

You know that feeling when an optimization you designed and implemented is adopted by several entities or a network and you know that hundreds/thousands of computers are not wasting millions of CPU cycles anymore and you're all happy about it but no one else really cares? Oh you don't? Ok me too, I didn't say anything 🤫