The fundraiser to get #Kaspa at Imperial College London has reached its $8,000 milestone!
Its great to see the $KAS donations coming in: 138 transactions so far.
We are happy to have reached enough funds and can go to Imperial to create awareness about Kaspa.
The funds upto $10,000 will be used for the streched goals for additional visibility including merchandise.
ps. If it happens to be the case that the donations keep going and we reach Silver, a lot more can be done even. Silver includes a booth and a 30-minute keynote talk during the opening and closing ceremony as awell as a bounty for the hackaton. That will increase the exposure a lot.
We do expect to be signing off with the organizers coming week. If so, we will ofcourse give another update.
To donate visit https://t.co/evk0x5h9G3 for the details or use:
kaspa:qrryda035xkx02l7yg7lx65ct89zk6ku2greszt475rvn80z6ydkyy9q3zl8r
Tipping on X just got real. ⚡
Send $KAS to anyone on X straight from your phone — tap Share → KasTip → done. On-chain in ~1 second.
Non-custodial: your keys never leave your device. We can't touch your funds.
📱 Coming to Google Play & App Store soon. Follow for launch.
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.
Product Two.
We’re building a full suite of covenant-native products on Kaspa. This one is a proven category.
Will $KAS hit $0.2 this year? You can bet on it.
Meet Auspice — a native prediction market based on Kaspa Toccata covenant. No custodians. No bridges. No L2. No extra token.
Collateral sits in the market’s own covenant. Payouts are enforced by consensus, not promises.
You trust code and covenants. Not us.
Live end-to-end on TN10 today. Mainnet the moment covenants land.
Read the signs. Trade the morrow.
This marks the end of the Bitcoin religion.
Meanwhile, $KAS impresses with new records and features. As do many other alt coin.
Bitcoin maxis are a dying breed.
Kaspa Activates Toccata Hard Fork...
@Kaspaunchained officially launches the Toccata Hard Fork release, with mainnet activation scheduled for June 30, 2026, at DAA score 474,165,565.
This consensus-changing upgrade introduces native L1 covenant support and transaction introspection, allowing for expressive stateful contracts on $KAS.
The update also features the OpZkPrecompile for trustless L1 ZK proof verification and partitioned sequencing commitments to scale-based ZK applications.
**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.
Kaspa Toccata mainnet process update:
Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1–2 days of broader network sanity testing.
Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today
That's a really good question, but it's hard to answer in a single tweet because our mission is quite extensive, and it requires a lot of background knowledge to really understand what sets Kaspa apart.
Currently, a lot of people see Kaspa as “Bitcoin’s crazy little brother” that improves time-to-finality by leveraging the benefits of DAG-based consensus protocols without accepting their traditional drawbacks, such as decreased decentralization or a limited validator set.
This perception is somewhat accurate, but it falls short of conveying the full picture, because Kaspa’s vision extends far beyond just trying to be a better Bitcoin.
Anyone willing to study Kaspa and its broader vision will discover similarities to nearly all major existing DLT designs: from Bitcoin, to Ethereum, to Solana, Sui, Celestia, and beyond.
My personal view is that “research” in the DLT space is approaching a point of convergence. We increasingly understand how to push distributed systems close to the limits of what physics permits. The frontier is no longer only about raw throughput or faster finality. The attention is shifting toward game theory, incentives, sequencing, MEV, alignment, and how to build systems where the economic incentives of users, builders, miners, validators, applications, and infrastructure providers do not work against each other.
That is why debates like based rollups versus arbitrary sequencing, shared sequencing, MEV mitigation, proposer-builder separation, and execution-layer incentives matter so much. These are not niche technical details. They determine whether a network can remain neutral, decentralized, and aligned while scaling to global usage.
And this is where I think Kaspa is pushing the boundaries in a very important way.
Kaspa is not merely trying to be “fast.” The goal is to build an L1 where speed, decentralization, security, and incentives are aligned at the base layer. A system that does not scale by hiding complexity behind trusted committees, privileged sequencers, centralized validator sets, or opaque coordination mechanisms, but instead tries to preserve the spirit of proof-of-work while extending what an L1 can realistically do.
Because Kaspa arrived later than many other major projects, it does not carry the same degree of technological debt. It can absorb lessons from Bitcoin, Ethereum, rollups, modular blockchains, high-throughput monolithic chains, DAG research, MEV research, and the broader history of decentralized systems, and combine those lessons into something more optimal.
To me, that is what Kaspa is building: not just a faster blockchain, but a more incentive-aligned decentralized infrastructure layer.
But this also creates a different challenge.
Kaspa’s biggest problem today is not its technology. It is the lack of centralized coordination around communicating the vision. And because Kaspa is a grass-roots movement, that responsibility does not belong to a marketing department, or a single leadership team. It belongs to the community.
That also means the community has a different role to play.
There will always be holders who are mainly interested in price, and that is completely fine. But there also need to be people who are here because they want to use the technology to build a different future. People who care about the architecture, the incentives, the open questions, the trade-offs, and the long-term trajectory of decentralized infrastructure.
I am one of those people.
I am not interested in DLTs merely as a way to generate wealth. I am interested in them because I believe they can change the trajectory of humanity as a whole.
For that reason, I want to use this opportunity to announce a regular community hangout where we discuss the current state of development, the open questions, and where we can align our vision together.
The first session will be on Tuesday, June 9th, 2026.
We will talk about the vProgs framework, how the codebase works, what sets Kaspa apart, where we improve on existing solutions, and what still needs to be done. The goal is for this to become a regular, possibly bi-weekly, event where we as a community come together to discuss the future and understand the technology.
Eventually, we can invite people from other projects as well, but the main focus at the beginning will be explaining and communicating how things work under the hood.
There is still a lot of work to be done, and I do not want to waste precious time. So the first sessions may feel a little improvised, but we can improve as we go.
The important thing is that we start.
So mark the date: Tuesday, June 9th, 2026.
The kaspa community has been loud.
We've been listening👂
Now we're making it official!
If you want @kaspaunchained on Cypherock, here's your one shot to be counted.
Fill the form. Share it with every Kaspa holder you know.
This isn't forever open.
👉 https://t.co/OO1LTjFSg2