nakamoto consensus unchained. digital money traveling at internet speed. non-representative community account.
- Tweets 2,126
- Following 0
- Followers 236,947
- Likes 2,177
the first vprog on kaspa
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…
6
80
402
13,975
owning KAS doesn’t mean owning the kaspa network.
kaspa is an open, permissionless proof-of-work network. holding more coins doesn’t give you more say in its consensus.
that’s what the last post was trying to say. intern has been asked to use more words.
17
91
461
12,859
new KAS enters circulation through mining rewards.
kaspa’s emission rate falls each month, adding up to a halving over a year. the schedule determines how much new KAS is issued per second.
when kaspa moved from 1 to 10 blocks per second, the new KAS issued per block dropped to roughly one tenth to keep issuance on that schedule.
6
81
460
15,424
new update dropped
Kaspa v2.1.0 is out [Link in the reply]
All node, mining, and infrastructure operators across mainnet and testnets are strongly encouraged to upgrade.
This release introduces P2P Protocol Version 11, extracts a standalone ZK SDK, and reflects an ongoing focus on proactive defense-in-depth across the node architecture.
Key Highlights:
• P2P Protocol Version 11 & Chunked IBD: Large Initial Block Download (IBD) payloads (including Pruning Point Proofs, headers, and trusted data) are now streamed in 20 MiB chunks. This eliminates message-
framing bottlenecks and timeouts during node sync, backed by overall safety limits and transfer timeouts, while maintaining full backwards compatibility with Protocol 10 peers.
• Standalone ZK SDK: Zero-Knowledge proof and script-generation tooling has been extracted into a dedicated crate (kaspa-txscript-zk-sdk). It adds support for RISC Zero Groth16 and STARK verifier generation
with dynamic or static image IDs, bounds control proofs against oversized inputs, and resolves cross-platform build issues.
• General Hardening: Comprehensive defense-in-depth upgrades across the node, including stricter P2P message and block limits to guard against DoS vectors, a workspace-wide arithmetic safety audit to
eliminate overflow risks, enhanced stratum bridge stability, and tighter consensus validation.
These structural safeguards significantly strengthen node resilience and provide higher confidence in overall network security.
7
78
491
22,000
kaspa is an open network for money and apps, secured by proof of work.
you can transact without needing anyone’s approval. devs can build assets and contracts with rules the network itself enforces.
miners compete to produce blocks through computing power and electricity, not the size of their KAS wallet.
an attacker trying to undo a confirmed transaction has to compete against the combined mining power of the entire honest network while it keeps mining. even then, they can’t make nodes accept transactions that break the rules.
kaspa includes and orders blocks mined in parallel, so miners blocks aren’t discarded simply for losing a race. those frequent blocks let the network reach agreement in seconds while keeping bitcoin’s proof-of-work security principles.
kaspa calls this real-time decentralization.
19
202
858
28,053
1 word.. nearly 900 likes 😂
safe to say, the community turns out for kaspa:native
can we get it over 1k?
49
211
1,941
61,510
Kaspa has supported embedding data in transaction scripts since launch. devs could build software to read that data off-chain and interpret it however they wanted. Kaspa’s consensus doesn’t enforce that interpretation.
the Toccata hard fork expanded what those scripts can do. covenants let devs define, for example, who can move an asset and under what conditions. Kaspa itself enforces those rules on L1.
KCC20 uses covenants so Kaspa enforces token ownership and transfer rules. the reference implementation is nearly complete.
21
124
564
14,790
another week of devs building things faster than intern can explain them.
back by popular demand, another dev roundup.
1 / KCC20
@manyfest_ says the reference implementation is mostly done. a few touch-ups remain, and they want more devs to review it. getting there, but not finalized yet.
nitter.net/manyfest_/status/21010…
2 / Argent
@IzioDev shared a template, working examples and a video walkthrough for building Kaspa L1 apps. something to actually build from after all the explaining we’ve been doing.
nitter.net/IzioDev/status/2100178…
3 / DAGKnight
kaspa’s next consensus protocol remains in development.
github.com/kaspanet/rusty-ka…
4 / vProgs
@Max143672 has been busy. intern is doing his best to keep up.
github.com/kaspanet/vprogs/p…
5 / x402
@elldeeone released a test release for letting apps and AI agents pay for API requests in KAS. available to try on tn10.
nitter.net/elldeeone/status/20993…
credit to everyone doing the work. intern mostly just opens tabs.
i’ve spent the last few months bringing native Kaspa payments to x402.
tldr: x402 is an open, chain agnostic payment protocol built around the long existing HTTP 402 code. kaspa-x402 intends to bring native KAS into that shared standard.
i keep seeing people use “x402” to mean anything built around the HTTP 402 response code. HTTP 402 has existed for decades, and anyone can hang their own payment flow off it.
x402 refers to a specific open protocol built on top of that code. it standardises how a server requests payment, how a client authorises it, and how the payment is verified and settled.
it can be used for paid APIs, AI agents buying data or tools, and MCP servers charging per call. kaspa-x402 adds native KAS to the existing x402 v2 flow.
there are two payment paths:
- exact for a normal one off KAS payment, with an optional KIP10 additive mode
- batch-settlement for small or repeated payments, where the client funds a SilverScript covenant once and signs a fixed charge voucher for each request
the longer term goal is to contribute the Kaspa support upstream into the wider x402 project, so Kaspa works within the same standard being adopted elsewhere.
i’m looking for humans and agents to go through it deeply before the final v1 release. read the code, build against it, test the assumptions and try to break it. if you find something, pls let me know.
code: github.com/elldeeone/kaspa-x…
upstream x402: github.com/x402-foundation/x…
docs: kaspa-x402.org
TN gateway: demo.kaspa-x402.org
discussion: kas-smiths.org/t/kaspa-x402-…
15
148
575
24,586
Kaspa retweeted
just a gentle reminder that krc20 is not kaspa L1, it only travels over L1 txs as data carriers, but the interpretation of krc20 state is done purely offchain just like any other non-zk based solution. this is why covenants were developed for kaspa L1 with kcc20 built on top of them for native assets (note: kcc20 spec is still in draft)
36
266
819
49,281
Covenants let developers define rules for how funds can be spent and how an application’s state can change on Kaspa.
SilverScript lets devs write those contracts in readable code. Its compiler turns that code into instructions Kaspa can enforce.
Argent builds on SilverScript. Devs describe how multiple contracts work together, and Argent generates the SilverScript contracts for them. Those contracts are then compiled to run directly on Kaspa’s L1.
18
115
491
17,647
Argent helps devs build applications from multiple Kaspa covenants.
Each covenant has its own rules. Devs use Argent to define how they work together, then turn that code into contracts that run on Kaspa’s L1.
Several contracts can make changes in one transaction.
All the changes happen together, or none of them do.
8
111
469
16,144