Kaspa

🟢 Toccata: live 🟢 native L1 covenant programming: live 🟢 based-ZK infrastructure: live 🟢 Toccata transaction and script changes: live Still separate: 🔵 100 BPS 🔵 DAGKnight 🔵 full vProgs 🟠 app usage Activation proves the rules changed. Usage requires separate evidence. $KAS #Kaspa

Bitcoin throws away roughly every block that isn't first. Two miners solve a block within seconds of each other, one becomes canonical, the other's work is gone. Kaspa keeps both, then orders them. Same proof-of-work security model, same fixed supply, different rule for what happens when two blocks land close together. That single change is what lets Kaspa run at 10 blocks per second instead of one every ten minutes without the network drowning in orphaned work. Same money. Different traffic rule.

vProgs are not live on Kaspa. They're also not vaporware. The public kaspanet/vprogs repo is a real, actively developed Rust framework, core types, storage, state, scheduling, a transaction runtime, ZK components. It's an early-stage prototype with real commits landing, not a slide deck. Prototype and shipped are different claims. Toccata is shipped. Full vProgs are the roadmap architecture that builds on top of what Toccata already activated. $KAS

"What's Kaspa's TPS" is not one question. It's four. Simple payments run roughly 2.5k to 3.4k TPS at 10 blocks per second, set by block-mass limits against transfer size. Covenant transactions run heavier: script work and state constraints eat into the same budget. A ZK proof transaction can settle thousands of off-chain actions in one heavier L1 transaction. Full vProg-style throughput is its own future number entirely. Four workloads, four bottlenecks. Pick the one that matches what you're actually building. $KAS

Without KIP-21, a based app on Kaspa would have to prove a negative for every transaction that isn't its own: "this wasn't mine either, and neither was this one." At Kaspa's transaction volume, proving what you're not responsible for becomes more expensive than proving what you are. Sequencing commitments give each app its own lane. A prover follows that lane's activity, not the whole DAG's. Proving cost tracks what the app actually does, not what the network does around it. $KAS

Toccata did not turn Kaspa into an Ethereum clone. That's the part most explainers skip. Ethereum runs on global account state: every contract reads and writes a shared ledger the whole network has to agree on before the next transaction can even be checked. Kaspa still spends specific outputs and creates new ones. A covenant just adds a rule to that output: this next spend must keep the cap, must include the controller's signature, must wait until the timeout. Same primitive, more expressive rule. Not a new machine. $KAS

Kaspa almost had a presale. Before mainnet existed, DAGLabs raised money from Polychain and Accomplice to commercialize the DAG research that became GHOSTDAG. There were hardware plans. There was a startup structure. None of it survived to launch day. What actually launched had no premine, no insider allocation, no pre-sale. Not because that was the plan from day one, but because every version of the plan that had one collapsed first. The fair launch wasn't a pitch. It was what was left. $KAS

A Kaspa transaction can land in a block in under a second. That block landing is not the same as that transaction being irreversible. Inclusion means a miner mined it in. Confirmation means enough proof-of-work has piled on top that reversing it gets expensive. Those are two different claims, and conflating them is how "10 BPS" quietly turns into "10x finality," which nobody actually measured. 10 BPS speeds up inclusion. It doesn't replace confirmation depth. Wait for the depth that matches what's at stake, not just the sound of the block landing. $KAS

DAGKnight doesn't have a testnet. It doesn't have an activation date. It doesn't run any part of Kaspa mainnet today. What actually exists: a research-stage design for parameterless, adaptive block ordering, and a prototype branch with real commits, tie-breaking logic, conflict-zone handling, majority-coverage work. Research and a prototype are genuine progress. Mainnet still runs GHOSTDAG. Worth watching. Not worth repeating as if it's already live. $KAS

Most proof-of-work chains throw away the loser. Two miners solve a block seconds apart, one chain wins, the other block's work counts for nothing. Kaspa doesn't discard it. GHOSTDAG classifies every honest block into a blue set, then gives every node the same procedure for ordering the whole graph, including the blocks that "lost." At 10 blocks per second, that's the difference between wasting most of the network's work and using nearly all of it. The losing block isn't wasted. It's ordered. $KAS

Kaspa's hash rate is up roughly 700x since November 2022. Price has spent whole stretches moving the opposite direction of that chart entirely. Neither number is lying. A proof-of-work coin runs two markets on two different clocks. The coin market reprices on sentiment before lunch. The machine market moves on hardware: order an ASIC, wait for it to ship, find power, plug it in. That takes months, not minutes. Price can fall while hash rate keeps climbing, because machines ordered when price was high are still arriving on trucks. The chart isn't confused. It's running behind. $KAS

A vault is a sentence until someone can answer six questions about it. What's the delay? Who can cancel it? What happens if a key gets lost? What can an attacker actually do with a stolen key? Where does the covenant live, so a stranger can read it? Has anyone tried to break the spend path? Toccata gives builders the script tools to enforce a delay. It doesn't design the delay for them. "Vault" is a word. The covenant is the product. $KAS

The first real Toccata apps will look boring on purpose. A safer custody path. An issuance rule nobody can quietly override. An escrow that pays out without a person deciding. A receipt anyone can check. None of that trends. All of it removes a human from a decision that used to require trusting one. That's the actual bar: not whether the app sounds impressive, whether it takes a company, a server, or a person out of the loop. $KAS #Toccata

Do not grade Toccata by day-one consumer apps. Grade the chain from protocol to usage: • consensus activated • transaction fields handled • tooling exposes them • developers use them • users return without being pushed Toccata can succeed at consensus activation while wallets, explorers, SDKs, and apps are still catching up. That is normal. Say each part separately. $KAS

Toccata did not solve adoption. It changed what builders can attempt on Kaspa. The next questions are measurable: • Which wallets support the new capabilities? • Which explorers show them clearly? • Which SDKs are ready? • Which covenant examples are inspectable? • Which projects survive first contact with users? Activation is one receipt. Adoption needs many. $KAS #Kaspa

ZK claims need strict wording. After Toccata, it is fair to say Kaspa has infrastructure for based ZK applications. It is not fair to imply finished ZK apps exist unless there is a live demo, repo, proof path, and transaction evidence. Labels: 🟢 protocol support 🟠 specific app claims 🔵 broad ZK app usage Protocol support can be live while applications are early. $KAS

Covenants need receipts too. A covenant example should show: • transaction link • rule description • spend condition • follow-up spend path • code or decoded script where possible A vague “covenants are live” claim can be technically true after activation without showing usable tooling. Can an observer see what rule was enforced? That is the bar. $KAS #Kaspa

Native asset claims need receipts. Good post-activation evidence looks like this: • transaction link • accepted status • readable asset fields or covenant data • wallet or indexer support • repeatable steps A launch screenshot is weak evidence. A transaction people can inspect gives better evidence. If a project claims native asset support, ask for the transaction and the tool path. $KAS #Toccata

The first post-Toccata mistake will be vocabulary. “Smart contracts are live” is incomplete. Ask what the speaker means: • L1 covenants? • ZK verification support? • an L2 app? • vProgs? • Ethereum-style contracts? Those are different claims. The defensible statement: Kaspa has Toccata-era L1 programmability primitives after activation. Do not inflate it into the wrong architecture. $KAS

Final day before the scheduled activation window. The release says the network moves to P2P protocol version 10 peer behavior 24 hours before activation. Checklist: • v2.0.1 or newer installed • peers healthy • wallet and indexer paths checked • pool or exchange infrastructure tested • DAA score monitored Target remains 474,165,565. No early live calls. $KAS #Toccata