I'm not great, I'm not good, not even decent. But I'm trying, out of curiosity.
Yet another human on earth, just like you.
KEF grantee since 12/15/2025
**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.
@KaspaMobile@BankQuote@michaelsuttonil I don't understand, but it seems wrong to use a CPU to mine on Kaspa as the hashpower is largely dominated by ASICs.
@brt2412 As a reminder: you will need to upgrade again once the final release is out, same procedure.
And the procedure @brt2412 shows is the exact same for any operating system, just make sure to click the link matching your operating system
@callebtc Intuitively, how would you deal with root possibly being outdated (compared to off-chain most up-to-date state) without inducing a new source of authority?
Just saving this here to document a story and as a self reflection on whether AI is really making me more productive
Yesterday morning I found a way to complete the new HVM approach, that is much faster than before. I spent a few hours writing a spec, and then used Opus to implement. About 3k lines of C code later, everything worked and performance was incredible: 5x faster than HVM4 (stable at ~10x now). So, in one day I had outclassed HVM4. Incredible. I'd never have implemented that so fast manually.
Now, enter today. I want to turn this into a real thing, but I haven't fully read the 3k lines yet. So, how do I trust it? I spent the whole day auditing the code. With AI. Several bugs found, most minor like forgetting to collect() some argument. But then I stumble upon this:
λ{ inl: 1 ; inr: 1 }
This was a test. But wait. This is matching on inl/inr. So the branches should receive the value of the Either. But they were numbers instead. Numbers aren't functions. This makes no sense. So why this is a test?
It then stuck me. The AI completely misunderstood how function arities work. It literally assumed for no good reason that HVM5 was supposed to handle under/over-applied functions. For no good reason. I never wrote that. It never asked either. It just kinda thought "HVM is weird in some aspects, this might be one of them..." - and then it went on to implement a massive system to handle cases that should never happen to begin with. And all of that code is obviously wrong because it should not even exist. It is wrong. It is damage. And it is there.
But it isn't too bad either. I just told Opus that it was wrong. Perhaps not so politely. And it solved it just fine.
But then this begs the question. I spent ~20 hours in this file, and it is STILL not done. I went from 0 to 95% in the first 5 hours. Yet, 15 hours later, it is still not 100%. I suppose that is the real effect of using AI. If I had just written the C file manually in the last two days, would I not be further than where I am *right now*?
Surely, the first version would have taken much longer to drop. But when I'd finish writing all that code, there would be zero, literally zero retarded shit. And, just today, I caught 5 or 6 retarded shit. And the worst part is: I don't know what the number of retarded shit left is, but I'm afraid it is >0.
So if I have to read it all, review it all to ensure there is no retarded shit... what did I achieve by using AI, other than that dopamine anticipation?
It's very satisfying to progressively assemble pieces of the software you love.
1 year ago I only knew one Kaspa surface layer and today I'm starting to feel confident in many of them.
I didn't fully realize the deepness, nor how big I would progress in my beloved field.
@bathtoob30@L0RINC@MotoleseOficial One already can run a pruned btc node. However it's weaker than kas node, because a node cannot trustlessly sync from a pruned node. You have to either start from genesis or trust a peer.