i’ll do everything in my power on the technical side to help this initiative move forward and navigate any protocol-level obstacles along the way.
on a personal note, Alex has a rare mix of technical depth, bizdev talent and deep Kaspa knowledge. i honestly can’t think of anyone better suited to lead it, and i really appreciate him taking this on
We have a winner! 🥳💚
Full Kaspa teal logo it is!
Personally, I preferred the two-tone version, but the community has spoken. And that's the way to go! 🚀
KaspaDollar is the first decentralized stablecoin on the $KAS Network
This is a MASSIVE development in the #Kaspa ecosystem
Great work @asaefstroem in leading this initiative!
The #Kaspa community keeps building, even in the depths of a bear market. Bullish on the $KAS community and network
They declared $KAS dead.
The network didn’t get the memo🗿
“Kaspa is finished.”
“It’ll never come back.”
Meanwhile the chain keeps running.
Past 7 days:
$KAS — 5.8M transactions
$BTC — 4.9M
$LTC — 1.25M
This is happening while $KAS is down, attention has shifted, and the timeline is flooded with new launches fighting for the same liquidity.
Markets can ignore a project for months, that doesn’t mean the builders stopped or the network stopped operating.
When sentiment is this low, it’s fair to ask whether price is reflecting fundamentals or simply the lack of attention.
Transaction counts alone won’t take $KAS into the top 10. But writing it off while the network keeps putting up these numbers deserves a second look.
$KAS
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.
@manyfest_ and the bonus: you get kcc20-standardized borrow-receive for native KAS micropayments (kip10 to those who remember; see parts 12-15 in this thread as well https://t.co/auzqUnbtJ9)
Onwards!
KCC-20 lets us create tokens that work together through a shared interface. Native KAS is a fungible token as well, but it isn’t a KCC-20 token.
Imagine a DEX, for example. KCC-20 lets us write a generic pool covenant that supports any pair of KCC-20 tokens. But if one side of the pair is KAS, we’d need special logic to handle it.
Representing KAS as a KCC-20 token would let covenants handle KAS the same way they handle other KCC-20 tokens. There could be different implementations and deployments of a KAS-backed KCC-20 token, but it would be beneficial to agree on a single one to avoid fragmentation.
I'm proposing a simple implementation, KAS20. Join the discussion on Kas-Smiths:
https://t.co/bq3htUe0FA
We open our migration tool and deployment to the layer 1 (KCC-20) in the coming days, most likely by Monday.
Keep those ears up for announcements!
$KAS $NACHO 🐈⬛
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!
$KAS is going to flip $BTC
$KAS is going to flip $ETH
$KAS is going to flip $SOL
There’s no golden rule that “Bitcoin is king” and will remain #1 forever
It’s ultimately a zero sum game and the winner takes all, KASPA.
KCC20 is final. A new era begins for KaspaCom. ⚡️
Now we can test the full KCC20 experience end to end: Order Book DEX. Minting. Token Launches. KCC20 Bridge.
We led KRC20 trading. We’re ready to do the same for KCC20.
Trade, launch, and stack points ahead of $KCOM. It’s all coming together soon on KaspaCom Markets.
4 months ago Toccata enabled native L1 programmability.
Last month, SilverScript brought a high-level language for covenants.
Today KCC-20 finalization gives the ecosystem a shared convention for defining, deploying, interacting with, and composing fungible token assets.
There is still more work to do on indexers, tooling, and KRC-20 migration, but the pieces are coming together.
I made some interactive walkthroughs so curious interns can explore these conventions visually. They cover the Argent reference implementation, hash-chain borrowing, and KCC-23 metadata declaration.
KCC-20 spec:
https://t.co/eKL4Ch1VQE
Reference implementation:
https://t.co/wRu7c5CG6y
KCC-20 walkthrough:
https://t.co/Wa9YHbk18n
Hash-chain demo:
https://t.co/AlVv9cF1Bl
KCC-23 walkthrough:
https://t.co/Jo7aPYTrV8