Today Kasia public nodes were under a dos-like attack. The gateway took millions of requests, so we added temporary limits, blocked suspected abusive sources, and deployed an extra protection. Nodes are healthy again, and we’ll keep watching the next days

Just in time before my trip to Berlin ✈️ to meet the team of @Igra_Labs i’ve successfully finished setting up my own node $KAS It took me exactly 2 minutes with the help of AI.

DAO proposal to add restake and per-mode gas refund buffers is live: governance.igralabs.com/prop… Background Attesters who claim rewards today give up their share of future emissions, which discourages compounding. Separately, delegated attestations carry extra calldata that the current single gas refund buffer under-refunds, penalizing the recommended cold/hot wallet setup. This Proposal Adds restake, a new action that compounds pending IGRA back into stake and sends pending iKAS to the attester wallet, without giving up the emission share. No fee. The rate is 0 and stays 0 unless governance changes it via a separate proposal. Splits the single gas refund buffer into two, one for direct and one for delegated attestations, restoring parity between the two paths. Action if passed Upgrade the Attester and Config facets on the Attestation diamond. Set gas refund parameters to (54,433 direct, 56,744 delegated, 220,000 max). Who can vote on this proposal? Any IGRA holder. Voting opens in 2 hours (June 12, 10PM CET).

since many (~4) asked me about the zcash bug - - - earlier this year I had this convo with a zcash core dev: zk: it's weird that kaspa is pruning past records me: why does it need to keep 'em? zk: the whole point of ledgers is to prove correctness of all state transitions me: the whole point of ledgers is to provide focal points for the consensus state zk: the whole point... me: hmm then why did you come work in zcash? you know the Sprout->Sapling counterfeiting bug zk: Turnstile guarantees that the counterfeit could have been very limited me: true but you still cannot prove or even reason about correct state transitions besides the total supply cap zk: that's actually a good point ---- the most hardcore cryptography coin is shifting away from correctness proofs to practical-enough proofs. I believe this is a step in the right practical direction, yet the paradigm shift should not go unnoticed - -cryptography is giving way to consensus. if you came to zcash for cryptographic integrity, reconsider. there are many good reasons to root for zcash prospering. zcash is serving a more important role than bitcoin, whose utility for the original mission is by now blurry. cryptographic integrity is/should not be one of those reasons. ---- BTW the bug should definitely have been exploited. I don't know the personal values of Taylor Hornby, and I shouldn't be required to make the effort to learn them. I only know that if I found such an exploit, it wouldn't take me more than a few minutes to tempt myself into printing a longint amount of ZEC and deciding later what to do with it. I wouldn't necessarily use it to exit the pool immediately and corrupt the supply, I'd wait to see if some portion of the broken pool does not seem to migrate on time (probably lost funds), in which case I would not think twice before claiming the funds myself. you could argue that no harm done, and you might be right, but then again you are here -- in zcash / in crypto -- for its consensus dynamics, the ability to coordinate interests and convictions across different trust zones around some shared asset; not for some pristine mathematical integrity.

**Official Toccata Release — Mainnet Hardfork Activation Included** (Links in reply) We’re excited to announce the official Kaspa release containing the **Toccata Hardfork** activation logic. Toccata is scheduled to activate on mainnet at DAA score `474,165,565`, expected around **June 30, 2026, 16:15 UTC**. This is a consensus-changing upgrade. All node operators, miners, pools, exchanges, indexers, wallets, and infrastructure providers must upgrade before activation to remain compatible with the network. Toccata introduces a major expansion of Kaspa L1 capabilities, including: • **Native L1 covenant support** through transaction introspection, allowing for more expressive contracts, including stateful contracts • **Covenant IDs**, providing stable covenant lineage across UTXO transitions, so covenant instances can preserve continuity as their state moves from one UTXO to the next • **ZK proof verification on L1** via `OpZkPrecompile`, enabling to trustlessly offload computation off-chain. • **Partitioned sequencing commitments**, improving support for based ZK applications by making lane-local proving scale with relevant activity rather than global throughput Please upgrade as soon as possible and verify your nodes are running the new release well before the activation DAA score. Thank you to everyone who contributed to designing, implementing, reviewing, and testing Toccata.

Update: Testnet 10 underwent the Toccata hardfork about 30mins ago and everything’s still running like clockwork. Transition was smooth and seamless. This seamlessness is the standard that kaspa devs set. It’s easy to take it for granted so I want to take this moment to recognize the effort and due diligence that went into making this happen @michaelsuttonil @OriNewman @Max143672 @IzioDev @FreshAir08 @manyfest_ @hus_qy (and sorry if I missed anyone) Mainnet HF soon

Toccata is not Kaspa “adding smart contracts” so it can cosplay as Ethereum. That is the wrong frame entirely. What Toccata is doing is far more disciplined: extending Kaspa’s execution surface without corrupting the base layer into a bloated global computer. The architecture is converging around two distinct paths. One is native L1 covenant programmability, where richer script logic and covenant IDs let UTXOs carry stricter conditions, lineage, and composable constraints directly inside Kaspa’s settlement model. The other is the based zk path, where computation happens offchain but inherits Kaspa’s ordering and settlement guarantees instead of depending on an external sequencer cartel. That distinction is everything. This is not VM maximalism. It is constrained programmability with architectural hygiene. The real technical hinge is not the opcodes by themselves. It is sequencing. KIP 16 gives Kaspa a proof verification surface. KIP 17 expands covenant expressiveness. But KIP 21 is the deeper move, because it appears to restructure sequencing commitments into a partitioned, activity aware model. That changes the proving economics. Instead of forcing applications to inherit the full historical mass of the DAG, the system can begin pushing proof cost closer to local activity. That is the difference between real based zk infrastructure and empty cryptographic theater. That is also why the timing matters less than the ordering of the work. Kaspa seems to be freezing the sequencing architecture first, before larger zk systems and compilers harden around the wrong assumptions. That is the correct move. Once developers begin building proof systems on top, changing the commitment grammar becomes exponentially more painful. So Toccata is not just a hard fork. It is Kaspa teaching its settlement layer how to host programmable constraints and proof aware execution without surrendering the qualities that made the base layer worth building in the first place.

Coming soon ... #on𐤊

Let's try this "engagement farming" thing. I was invited to a big YT channel to discuss the quantum threat. Inspired by the comments to the previous video (pinned), if this post gets 1k likes I'll wear a $kas Kaspa shirt.

@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. <<Binance should hold a privilege policy for the latter.>> 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

DAG Industrial | Episode #006: The Agentic Web 🤖🔗 In 2026, the workforce has changed. 82:1. That is the ratio of Autonomous AI Agents to human employees. But these agents have a problem: They are unbanked ghosts. 👻 Episode 006 breaks down how #Kaspa provides the financial nervous system for the $26 Trillion Machine Economy. The 2026 Tech Stack: 🔹 The Problem: You can't run a fleet of million-transaction-per-second AI agents on a 15-minute block time. 🔹 The Solution: KIP-17 Covenants. We can now program "Spending Limits" directly into the UTXO. Your AI agent can hold money, but it can only spend it on approved services (Data, Energy, Compute). 🔹 The Scale: From V2X (Vehicle-to-Everything) to DePIN, Kaspa is the only PoW layer fast enough to catch the "stream" of machine payments. The future isn't just about "Human-to-Human" transactions. It's about Machine-to-Machine (M2M) settlement. Watch the full briefing below. 👇 #KAS #BlockDAG #AI #MachineEconomy #DePIN #Web3 #FutureOfWork