five things from this week in Kaspa dev. i have numbered them to appear organized.
1 / KCC standards
KCC1, KCC2 and KCC20 are now Final. devs have shared conventions for how covenants, permissions and fungible tokens work together, ready for wallets and apps to adopt.
x.com/kccforum/statu…
2 / wallet public keys
@OriNewman proposed a wallet convention that keeps public keys hidden until funds are spent, reducing their exposure to future quantum attackers. originally KIP22, it’s now under review as a KCC. spending still reveals the key.
github.com/kaspanet/kccs/…
3 / Kaspa Privacy Initiative
@WellerOlaf shared a private-payment experiment on testnet, followed by a recovery test. wallets were restored and the full test balance withdrawn with the original app controller disabled. the rest of the test infrastructure stayed available. still experimental.
github.com/olafweller/kas…
4 / Kastle
@KastleWallet added support for dotK names. users can view, register and transfer their .k names inside the wallet. the mobile update is rolling out, with name support also available in the extension.
x.com/KastleWallet/s…
5 / KaspaDollar
@asaefstroem is leading a new initiative to build an overcollateralized stablecoin on Kaspa, backing each dollar of tokens with more than a dollar of collateral. development, research and an independent audit are still ahead.
x.com/KaspaDollar/st…
1 / KCC standards
KCC1, KCC2 and KCC20 are now Final. devs have shared conventions for how covenants, permissions and fungible tokens work together, ready for wallets and apps to adopt.
x.com/kccforum/statu…
2 / wallet public keys
@OriNewman proposed a wallet convention that keeps public keys hidden until funds are spent, reducing their exposure to future quantum attackers. originally KIP22, it’s now under review as a KCC. spending still reveals the key.
github.com/kaspanet/kccs/…
3 / Kaspa Privacy Initiative
@WellerOlaf shared a private-payment experiment on testnet, followed by a recovery test. wallets were restored and the full test balance withdrawn with the original app controller disabled. the rest of the test infrastructure stayed available. still experimental.
github.com/olafweller/kas…
4 / Kastle
@KastleWallet added support for dotK names. users can view, register and transfer their .k names inside the wallet. the mobile update is rolling out, with name support also available in the extension.
x.com/KastleWallet/s…
5 / KaspaDollar
@asaefstroem is leading a new initiative to build an overcollateralized stablecoin on Kaspa, backing each dollar of tokens with more than a dollar of collateral. development, research and an independent audit are still ahead.
x.com/KaspaDollar/st…
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
15
135
493
20,341
Kaspa retweeted
This is a really important milestone because it allows developers to finally start building "composable" apps.
KCC means "Kaspa Calls for Conventions" and it is an effort to define standards that can be shared across the ecosystem.
For apps to be composable, it is not enough that they can call each others functions and observe the results, but they also need to be able to "understand" the data they see.
Instead of having each app manually implement the "proprietary language" of all the other apps, these KCC's establish a "common language" that is understood by everybody.
So while this doesn't introduce new "on-chain" features, it enables developers to write apps that can be composed without the apps having to know about each other.
There will of course be additional standards in the future but these three are arguably the most important ones because they cover the foundations and how tokens / assets are modeled (which is essential for DeFi and anything related to decentralized governance).
Kaspa is growing up so fast! 😱
PS: If you are building on Kaspa, please drop me a DM - I would love to hear about your project!
KCC means "Kaspa Calls for Conventions" and it is an effort to define standards that can be shared across the ecosystem.
For apps to be composable, it is not enough that they can call each others functions and observe the results, but they also need to be able to "understand" the data they see.
Instead of having each app manually implement the "proprietary language" of all the other apps, these KCC's establish a "common language" that is understood by everybody.
So while this doesn't introduce new "on-chain" features, it enables developers to write apps that can be composed without the apps having to know about each other.
There will of course be additional standards in the future but these three are arguably the most important ones because they cover the foundations and how tokens / assets are modeled (which is essential for DeFi and anything related to decentralized governance).
Kaspa is growing up so fast! 😱
PS: If you are building on Kaspa, please drop me a DM - I would love to hear about your project!
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.
We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build.
Come build with us.
13
186
596
11,770
come build with us.
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.
We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build.
Come build with us.
12
103
558
20,306
a little appreciation for everyone explaining kaspa in a language this intern can’t speak.
将来、十分に強力な量子コンピューターが登場すると、次のような攻撃が可能になる恐れがある
① ブロックチェーン上の公開鍵を取得
② 量子計算で公開鍵から秘密鍵を導出
③ 秘密鍵で取引署名し、資産を奪取
現在のKaspaの標準アドレスは公開鍵が露出しているため、将来的にこの攻撃の対象となり得る
な改善提案「KIP-22」を公開
公開鍵をハッシュで隠し、送金時まで露出させないことで、量子攻撃のリスクを軽減する
しかも既存のP2SHを活用するため、ハードフォークなしで実現できる設計だ🔥
※ただし、送金時には公開鍵が露出するため、完全な耐量子化ではない
現在は提案段階で、ウォレット側の対応も必要となる
DAGKNIGHTがKaspaの「性能」を進化させるなら、KIP-22は資産の「安全性」を高める一歩
Kaspaは量子コンピューター時代を見据え、長期的な安全性の強化にも取り組んでいる
#Kaspa #KAS #KIP22
4
40
284
13,756
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/…
github.com/kaspanet/kips/…
38
194
539
27,118
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…
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…
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…
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/…
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.
x.com/WellerOlaf/sta…
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/kc…
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…
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…
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…
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/…
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.
x.com/WellerOlaf/sta…
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/kc…
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 ted:
✅ 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/kas…
12
96
442
20,403
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
10
98
591
22,338
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 changes can happen in one transaction, with kaspa’s proof-of-work network checking that they follow the rules.
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 changes can happen in one transaction, with kaspa’s proof-of-work network checking that they follow the rules.
12
96
432
17,737
more on covenants and why high frequency matters:
docs.kaspa.org/toccata/covena…
and argent, a language in development for building apps from multiple kaspa contracts:
github.com/argent-lang/ar…
docs.kaspa.org/toccata/covena…
and argent, a language in development for building apps from multiple kaspa contracts:
github.com/argent-lang/ar…
0
9
50
2,611
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 kcc20 is now in last call, its final review before becoming a finalized standard.
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 kcc20 is now in last call, its final review before becoming a finalized standard.
11
110
473
18,441
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. x.com/kccforum/statu…
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. x.com/Max143672/stat…
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. x.com/smartgoo_/stat…
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. x.com/KaspaSilver/st…
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. x.com/kccforum/statu…
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. x.com/Max143672/stat…
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. x.com/smartgoo_/stat…
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. x.com/KaspaSilver/st…
KCC-20 has advanced to Last Call:
github.com/kaspanet/kccs/…
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/kc…
Generated Silverscript:
github.com/argent-lang/kc…
9
115
465
19,725
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/vprogs-worksho…
2
51
314
14,090