Crypto/AI Enthusiast/Kaspa Educator/Developer/Writer/Silk Road OG - clawdmkt.com
Satoshi's Laboratory.
- Tweets 12,538
- Following 1,457
- Followers 2,231
- Likes 31,696
Pinned Tweet
Kaspa is sitting in a different phase now. The old conversation was speed: GHOSTDAG, blockDAG ordering, parallel blocks, 10 BPS, and proof-of-work without forcing every honest block into a linear orphan race. That part matters, but it is no longer the whole story. The current state of Kaspa is about what that high-frequency PoW substrate can now carry.
Toccata changes the transaction layer. A Kaspa transaction is no longer just a value-transfer object. Transaction v1 gives it a programmable surface: compute budget for explicit script metering, covenant bindings for stable lineage, payload and gas semantics for app lanes, and the ability to carry proof-backed state transitions. That means the transaction can become a payment, a covenant transition, a settlement receipt, a ZK verification target, or an ordered user operation for an off-chain app.
The important design choice is that Kaspa did not throw away the UTXO model to chase an account-chain VM. State can stay local. A covenant UTXO can commit to old state, reveal it during spend, validate the transition, and force the correct successor output. KIP-20 gives that moving state a stable covenant ID, so the application can preserve lineage even as the actual script commitment changes. KIP-16 adds ZK verification. KIP-21 adds partitioned sequencing, letting based apps prove lane-local activity instead of proving the entire DAG.
That creates a cleaner split: Kaspa orders and settles; apps execute off-chain when they need heavier shared state; proofs bring the result back to L1.
The next battle is not raw protocol theory. It is standards and tooling: covenant ABIs, transaction builders, indexers, wallet policies, lane schemas, proof journals, exits, receipts, and developer frameworks.
Kaspa has moved from fast money into programmable PoW infrastructure. The primitives are live. Now the ecosystem has to make them usable.
19
115
294
24,945
BaN𐤊ℚuOτE retweeted
I made a condensed slimmed audiobook for you guys.
should work here.
kaspaexplained.com/moose if you want the full thing.
book, companion, YouTube link
#kaspa
11
31
598
BaN𐤊ℚuOτE retweeted
Satoshi 100% ended his own life
Absolute disgrace what is happening to bitcoin
I moved all my bitcoin to Fidelity
Bitcoin accounts at the main brokerages are what takes bitcoin to $1M
Strategy is the new Berkshire
Bitcoin backed lines of credit then become the cheapest way to borrow money
2
2
14
974
BaN𐤊ℚuOτE retweeted
Cheap but ok audiobook of Satoshi's Engine.
#kaspa $kas
I don't have time to listen to the whole thing for myself right now but i worked out most of the kinks.
Please give feed back :)
piped.video/3FTKZxLEfTo?is=qFyP…
Kaspaexplained.com/moose
Or kaspaexplained.com/satoshis-…
In memory of @MikoGenno our very own PlanK who asked "where does the power law come from? What builds it?" To then only measure price while it goes much much deeper.
Wherever you are. Read this.
I came to this space because Bitcoin and crypto was a tulip mania that persisted. One price bubble is meaningless, two? a coincidence of our time, perhaps. three? How can it persist?!
There is something underneath that isn't explained anywhere else.
So i did the work, i looked at the data and the incentives, the incentive structure, the incentive token, i looked at how people acted accordingly.
Charlie Munger couldn't be more right when he said: "show me the incentive and i'll show you the outcome" he was focused on businesses, one company at a time, never a global monetary network with no CEO and no worker paid beyond their contribution.
The question is the incentive, Satoshi showed a design for how to build the perfect one, @hashdag gave a better smoother design, @michaelsuttonil and the core of today took the flag and ran with it. Crazy bastards.
How does one make a zero-sum game meaningful? That's their problem. I'm just here to interpret the machine of what they all accidently built.
Satoshi might not be around anymore, but do you know what you did Yonathan? Do you grasp it Michael?
I don't discourage the global minecraft-like sandbox created by core with covenants and accompanying ZK. it's an engine, within an engine, within an engine.
For the coming builders who builds next:
"Whatever seems good to you and your brethren to do with the rest of the silver and gold, do according to the will of your God."
#kaspa $kas #bitcoin $btc
1
8
21
1,443
This tic-tac-toe demo is far more important than the game itself. It is a working example of what vProgs can turn Kaspa into: a sequencing and settlement layer for stateful applications without forcing every piece of application logic to execute directly on L1. Two players can lock KAS into a pot, play a multi-round match, and have the result determined by a verifiable program. The game logic executes through a RISC Zero guest, while Kaspa orders the application activity. The resulting state transitions are proven, aggregated, and ultimately checked by an L1 settlement covenant before funds can exit to the winner or be returned after a draw.
That architecture is the real story. Tic-tac-toe can be replaced with an exchange, prediction market, multiplayer game, auction, payment network, AI-agent economy, or other application with shared state. Kaspa provides ordering, data availability, settlement and the security anchor, while computation happens outside the consensus-critical path and proofs establish that the rules were followed.
This is how Kaspa can scale programmability without turning every node into a global computer. vProgs effectively let applications bring their own execution environment while inheriting verifiable settlement from Kaspa. Tic-tac-toe is just the smallest possible demonstration of a much larger application model.
6
58
149
2,767
BaN𐤊ℚuOτE retweeted
Morning. While you were sleeping, @manyfest_ finished the KCC-23 reference implementation, the rulebook for token metadata on a prunable chain. @supertypo_kas patched the DNS seeder so dead nodes stop juicing the node count.
vProgs caught a reorg bug on TN10. Before it mattered. That's the whole point of a testnet.
And Michael Sutton's doing Bitcoin Takeover on October 7. Big mic for the quiet dev.
Covenants aren't the future anymore. They're just Tuesday.
2
27
121
1,637
BaN𐤊ℚuOτE retweeted
The first verifiable program on Kaspa testnet is live.
vProgs crossed from research to working code.
Real execution. Real on chain settlement.
IzioDev's invitation, try it, get curious how it works, maybe write your own vprog.
That's how ecosystems start.
vprogs-tt.izio.fr | github.com/kaspanet/vprogs
#Kaspa #NFA
Max inviting devs to try a testnet vProg app in their browsers and then be curious on how it works, maybe even write their own prog?
i assume it will also help to identify bottlenecks, so let's congest there.
2
20
68
1,365
BaN𐤊ℚuOτE retweeted
don’t let this fly under the radar
refer to my pinned post → dual programibility landscape → second pillar: based zk apps
this is becoming real now
Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday.
You can play it here: vprogs-tt.izio.fr/
(Requires private key and some testnet funds)
We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately
I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top
For Devs: this is the invitation. Play the game, read the code, build your own vprog.
Game code: github.com/biryukovmaxim/vpr…
vprogs framework: github.com/kaspanet/vprogs/t…
23
182
572
18,365
BaN𐤊ℚuOτE retweeted
i used to think real-time execution was the one thing that couldn’t be faked on bitcoin L1.
i stand corrected.
52
113
569
22,930
I highly recommend watching this, especially to newcomers. Great work.
It’s finished.
Over the past weeks, I’ve been working on a video about Kaspa. Not just about speed, but about the idea behind it, the technology that makes it different, and what can now be built on top of it.
From BlockDAG and GHOSTDAG to programmability on Layer 1, this is my attempt to tell that story in a way that goes beyond technical specifications.
Built with respect for the people who made it possible.
A sincere thank you to the developers, researchers, and contributors who continue to build, refine, and push Kaspa forward.
@kasmediadotcom
@michaelsuttonil
@hashdag
Build on the future. Build on Kaspa.
kaspa.org/
19
77
1,695
BaN𐤊ℚuOτE retweeted
Two things shipped on Kaspa this week that builders
should know about.
1. dotk 2.0.0 .k name service now supports subnames.
yourproject.k -> treasury address
dev.yourproject.k -> dev wallet
team.yourproject.k -> team address
Covenant enforced. No registrar. No admin key.
dotk.name
2. Argent builder kit multi contract layer is open.
git clone argent template
./setup
Requirements: Git + Rust. Nothing else.
SilverScript writes the contracts.
Argent coordinates how they interact.
github.com/argent-lang
664 miners securing the network.
The infrastructure keeps growing.
#Kaspa #NFA
1
10
26
709
BaN𐤊ℚuOτE retweeted
Yesterday, the latest version of $KAS was released 👀
Kaspa v2.1.0
Of course, most on CT will simply skip over this news as it's very technical
But as a non-technical investor, it's a good reminder that development never stops for a single moment with Kaspa
19
92
425
9,391
BaN𐤊ℚuOτE retweeted
Kaspa moves fast. So do the claims about it.
I’m Daniel. I run this account to answer a simple question: what actually works today?
I read release notes, follow the public code and look for real tests. Then I try to explain what I find without pretending every idea is already a finished product. Sometimes the answer is exciting. Sometimes it’s “not yet” or “this broke.” I’ll link the evidence either way.
A couple of examples:
• What the KRC-20 incident did (and didn’t) mean:
nitter.net/KaspaScopio/status/210…
• A vProgs problem the team is working through:
nitter.net/KaspaScopio/status/210…
If you’re curious about Kaspa beyond the price chart, welcome.
Kaspa’s vProgs team is working on a problem that matters: what happens if the network reorganizes after a withdrawal has already been detected?
A new draft PR introduces a way to roll back outdated records so the system can recover from those changes.
It’s a meaningful step, but the work isn’t merged yet, and recovery after a restart still has limitations. This is development progress, not a mainnet launch.
github.com/kaspanet/vprogs/p…
3
17
53
3,598