KREX Token 𐤊 retweeted
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.
KREX Token 𐤊 retweeted
programmability on steroids
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.
KREX Token 𐤊 retweeted
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:
github.com/kaspanet/kccs/blo…
Reference implementation:
github.com/argent-lang/kcc20…
KCC-20 walkthrough:
kcc20.manyfest.dev/
Hash-chain demo:
kcc20.manyfest.dev/hash-chai…
KCC-23 walkthrough:
kcc23.manyfest.dev/
KREX Token 𐤊 retweeted
PR #31 (KCC-20 Last Call advancement) was merged on October 7, 2026 at 20:38:09 UTC. 14 days from that is October 21.
KCC-20 is final on October 21.
Quick clarification on KCC-20 timing 👇
PR #31 moved KCC-20 to Last Call on 7 Oct, but the header has no Last-Call-Deadline. On a 14-day count that's ~21 Oct.
A few questions please:
1.Is 21 Oct the intended end of the review window, or is a deadline still to be set?
2.KCC-1 and KCC-2 went Last Call on 1 Oct — do all three move to Final together, or does KCC-20 wait on those two?
3.Is the argent-lang reference impl + merged vectors considered to satisfy the KCC-0 §4.2 "public implementation" requirement?
Asking so builders know when it's safe to ship against KCC-20 as Final rather than Last Call. Appreciate the work on this 🙏
@manyfest_ @michaelsuttonil
@IzioDev
@asaefstroem
KREX Token 𐤊 retweeted
KCC-20 has officially moved to Last Call status.
Developing software and developing standards are very different.
Software aims to solve a specific problem. A standard aims to define a general foundation for a wide class of solutions.
A special thanks to @michaelsuttonil , who was there from the start to finish , guided me in how to approach this complex craft.
KREX Token 𐤊 retweeted
Transition of KCC-20 to Last Call is pending peer review of the KCC-20 reference implementation, which is the final milestone in the KCC process. This is expected in the coming days.
KREX Token 𐤊 retweeted
KCC-1 and KCC-2 just entered Last Call.
Nice milestone from @IzioDev and the contributors working on Kaspa’s covenant standards.
KCC-1 gives builders a common language for covenant layouts, state and ABI conventions.
KCC-2 tackles another important piece: how applications represent authority — keys, scripts or even a continuing Covenant ID.
Sounds dry, but this is the stuff different wallets, tools and applications need to agree on if they’re going to work together.
Both changes were merged today.
Nothing was activated on mainnet. These are ecosystem standards, not consensus changes, and they’re not Final yet.
KCC-1:
github.com/kaspanet/kccs/pul…
KCC-2:
github.com/kaspanet/kccs/pul…
#Kaspa #KAS #Covenants
KREX Token 𐤊 retweeted
Krons new NFT platform on kaspa:native follow KCC-721, Kaspa's covenant-NFT standard, which is still a draft. When the final standard is ratified, new contracts will follow it. Existing NFTs keep working and can opt in to upgrade.
The contracts are written in SilverScript and compiled with silverc (kaspanet/silverscript v1.0.0).
@kaspaunchained @KASPAglobal @opensea
KREX Token 𐤊 retweeted
Tomorrow, $KASBTC turns 2 years old. But someone stole the damn birthday cake!
Get ready for the birthday heist inside our Kaspa NFT game GothDAG. Hidden inside: the key to a treasure.
Every ally is suspect.
@KrexToken has a damaged surveillance report.
@Kas_Ranks found something on the ocean floor.
@KasDuckClub is giving a highly questionable testimony.
@Bonkeyonkas has eaten part of the evidence.
Follow the crumbs. Question the allies. And trust absolutely nobody!
The Birthday Heist opens very soon. Players compare statements, find contradictions, and solve small puzzles. Every player will have a full week to investigate the scene until the final puzzle opens to find the damn ally who stole the birthday cake. The first person to solve the final puzzle gets access to a hidden treasure 👀
KREX Token 𐤊 retweeted
Things I didn’t expect to be doing in cryptocurrency r&d: formally analyzing the semantic rules of a multi-contract compiler
github.com/argent-lang/argen…
(of course if you spot any soundness issues, pls share them)
KREX Token 𐤊 retweeted
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa.
This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript.
I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.