@ztipme when you say "mathematically governed" in (1) it seems you are comfortable restricting this property to the 21M supply. This is a good and practical approach, worth explicating
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.
$KAS Mainnet Toccata Release - v2.0.0 is here! Activation on June 30th at 11AM EST.
Expect multiple videos to come out about running Kaspa nodes with this new update on windows, linux, and mac.
**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
Here we go again: rehearsing a major hardfork on testnet 10, this time crescendoing into Toccata
Activation is scheduled for tomorrow May 18, 16:00 UTC.
Existing TN10 miners/operators should upgrade now. In a few hours upgraded p2p nodes will stop connecting to non-upgraded nodes as we enter the 24h pre-activation window.
Let’s make the mainnet activation boring by making the TN10 rehearsal as mainnet-real-world as possible
The upcoming upgrade was chosen without regards to vprogs, and no meaningful effort was made to optimize it for vprogs (definitely nothing delaying Tocatta by more than a few days).
Tocatta is a principled implementation of bitcoin-originating covenants which, if ever implemented in bitcoin, would use the op_cat workaround. It is the default method to introduce programmability into a thin verification-oriented L1 to preserve its decentralized lean value prop.
vprogs are outside core’s focus precisely because we are optimizing for usability over theoretical superiority.
I hope this helps you and grok update your premise.
(BTW counterexample to your claim about inevitability of fragmentation: Solana)
Fast, secure, and simple: swap Kaspa (KAS) in Ledger Wallet!
No need to move your assets to an exchange. Approve your swap directly on your Ledger signer and keep your private keys offline 🔐
Head over to Ledger Wallet now to swap KAS.
Kaspa is mentioned on the front page of @DiiDesertEnergy, a partnership of 126 global companies with a total valuation in the tens of trillions of dollars.
why I’m personally excited about Kaspa’s upcoming Toccata covenants
- for the first time, I can build creative, complex apps directly over infrastructure I helped design and build
- we designed under architectural constraints, but the result came out surprisingly expressive and powerful
- Silverscript is cool as hell
- I can literally open a *.sil file and write a complex contract that will be fully verified on Kaspa L1
- (nottoself: create a 10-minute video showing the building of such an app e2e)
- I can design my own vaults and safeguards, and manage funds securely without risking a heart attack each time I touch a wallet
- covenant ids, contract templates, and inter-covenant communication (ICC) feel like a new set of axioms, or a new algebra to work with and discover
- sig verify from stack / sighash anyone-can-pay + covenant ids can allow interesting shared-state covenants (requires a non-consensus miner policy; kudos to @maxibitcat for pushing this line of thinking)
- complex contract systems can be deployed in one spk hash. no storage rent, no deployment tax; users pay only the transient mass for tx data as they use it
- as I’ve mentioned in the past, this becomes especially interesting for AI/agentic environments, where bots could cheaply create one-time agreements between themselves
- I didn’t even mention based apps yet. That’s a whole vertical that isn’t ready for exploration yet, but will be very soon
You know why $KAS never got listed on Binance or Coinbase?
That's because it never paid exchanges to get listed, and it never gave supply away
It reached top 100 only through the sheer power of its community of holders and buyers
And it's not stopping
JUST IN: Binance Founder CZ says Elon Musk is an "alien."
"My theory is that he is an alien. He wants to return to his home planet, and Mars is just a stepping stone."
Feature freeze is here for Toccata! This means that no further consensus rule changes will be made as preparations are being made for the Toccata hard fork.
Toccata is going to bring loads of features to Kaspa such as ZK proofs, Programmable UTXOs, and more!