Kaspa retweeted
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
six things from this week in Kaspa dev, loosely understood by intern.
1 / Rusty Kaspa
@supertypo_kas’s optional lowio profile was merged into Rusty Kaspa. node operators with RAM to spare can enable it to reduce disk writes. his benchmarks showed roughly half as many bytes written.
github.com/kaspanet/rusty-ka…
2 / wallet queries
D-Stacks’ update lets wallets fetch unspent outputs a page at a time and request only newer ones when needed. merged into Rusty Kaspa this week and awaiting a release.
github.com/kaspanet/rusty-ka…
3 / portable Kaspa libraries
@Max143672 added support for compiling Kaspa’s core consensus and crypto libraries without Rust’s standard library, for use in constrained environments. merged this week.
github.com/kaspanet/rusty-ka…
4 / KCC23
@manyfest_’s proposal gives tokens a way to attach verifiable details like a name, symbol and decimal places. merged into the KCC repository this week, but still a draft standard.
github.com/kaspanet/kccs/pul…
5 / Kaspa Privacy Initiative
@WellerOlaf shared a testnet experiment showing deposits, proof-based settlement and withdrawals using Kaspa’s Based Apps. balances and transfers are still public. privacy is the next research step.
xitter.cf/WellerOlaf/status/2111…
6 / KAS-backed token example
@manyfest_ proposed a KCC20 example where each token is backed by one KAS. the offline demo covers creating tokens, transferring them and redeeming them for KAS. the pull request is still open.
github.com/argent-lang/kcc20…
Kaspa Privacy Initiative — Development Update
Following my conversation with @michaelsuttonil, we set out to test whether Kaspa's Based Apps and KIP-21 could provide the foundation for a shielded native KAS protocol.
The feasibility PoC on TN10 is now complete!
Across PRs #31–33, we've demonstrated:
✅ Real Kaspa L1 lane ordering
✅ Execution with cryptographic ZK proofs
✅ Proof-based settlement accepted by Kaspa
✅ Rejection of deliberately omitted operations
✅ State reconstruction and successful native KAS withdrawal after executor downtime
This is a significant step forward. Rather than building our own transaction-ordering infrastructure, we can potentially build on capabilities already available in Kaspa.
We've also added a new design principle in PR #34: future protocol upgrades should preserve users' access to their funds and aim to enable privacy-preserving migration between versions.
Now comes the part we've been working towards: actual financial privacy.
Our next milestone is a shielded payment cycle: Alice deposits native test-KAS, privately pays Bob, and Bob withdraws native test-KAS.
We'll begin by designing the private notes, commitments, nullifiers and ZK proof rules needed to make that possible.
The Based App PoC demonstrates technical feasibility within its tested scope. It is not yet a privacy protocol, an independently audited system or a final architecture decision.
But we're moving from proving the infrastructure to building the privacy layer itself.
All research remains open source. Technical feedback and contributions are welcome!
github.com/olafweller/kaspa-…
every 27 hours.
Kaspa's network produced 8,641,144 blocks in the 10 days to Oct 12, or 863,991 a day. At that pace it would match all 971,082 blocks Bitcoin has produced since 2009 in under 27 hours.
@kaspaunchained
kaspa produces 10 blocks per second. those blocks can carry app updates as well as payments.
covenants let devs build apps with parts that update independently. separate games, for example, can each keep their own progress without needing to change the others.
when parts need to work together, their changes can happen in one transaction, with kaspa’s proof-of-work network checking that they follow the rules.
more on covenants and why high frequency matters:
docs.kaspa.org/toccata/coven…
and argent, a language in development for building apps from multiple kaspa contracts:
github.com/argent-lang/argen…
kcc20 is about making it easier for wallets and apps to work with tokens on kaspa.
it proposes a shared way to describe who owns the tokens, how many they hold and how transfers work. it gives builders a common format to follow when their wallets and apps read token information or prepare transfers.
kcc20 is now in last call, its final review before becoming a finalized standard.
your weekly Kaspa dev roundup has arrived.
1 / KCC20
KCC20 has entered last call, its final public review stage. @manyfest_’s reference implementation is merged and open for devs to test against the proposed Kaspa L1 token standard. xitter.cf/kccforum/status/210821…
2 / vProgs
@Max143672 published a book about his testnet tic-tac-toe vProg, covering the game’s moves, proofs and payouts. diagrams included. the framework is still a prototype. xitter.cf/Max143672/status/21085…
3 / x4kas
@smartgoo_ released the first x4kas beta. devs can explore Kaspa chain data, run custom queries and monitor addresses locally through a desktop app or command line tools. xitter.cf/smartgoo_/status/21088…
4 / KaChat
KaChat is a messaging app that sends encrypted messages on Kaspa’s L1. there’s also a public feed for posts and replies. @KaspaSilver shared its refreshed website this week. xitter.cf/KaspaSilver/status/210…
KCC-20 has advanced to Last Call:
github.com/kaspanet/kccs/blo…
A companion reference implementation by @manyfest_, written in Argent together with its pinned generated Silverscript, underwent an extensive manual review and AI-assisted audit by Michael Sutton, covering KCC-20 conformance, implementation correctness, and edge cases.
It is now open for final public battle testing. We encourage developers and security-minded reviewers to try to break it, probe edge cases, and report any implementation bugs or discrepancies with the spec.
Argent contracts:
github.com/argent-lang/kcc20…
Generated Silverscript:
github.com/argent-lang/kcc20…
some light vprogs reading
I finally wrote a book that covers vprogs, and in particular tic-tac-toe implemented as a vprog on testnet-10. It follows the game down to the machinery underneath, with diagrams and appendices for the details. Welcome to explore it and ask questions: biryukovmaxim.github.io/vpro…
kaspa is programmable high-frequency proof of work.
Replying to @kaspaunchained
kaspa is programmable high-frequency proof of work.
i think high frequency is all the rage so to speak. it makes it a continuous composition of highly responsive mini programs














