KREX Token 𐤊 retweeted
Replying to @CyberpunkGame
Dreams Die. Legends Don't.
@CyberpunkGame
🤖 Made with AI
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
Replying to @frank_r2d2
KCC-20 makes stablecoins a practical reality on Kaspa, yes
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 Migration Notice ⚠️
Just to avoid any misunderstandings later on, let me clarify how the snapshot-based #KREX migration will work. 🤜🤛
🟢 1. Snapshot
The snapshot will be taken at the specific date, which I will officially announce once everything is ready.
It will generate a JSON file containing every KREX holder wallet and its exact KREX balance at that moment.
🟢 2. You do NOTHING
You do not need to claim anything.
You do not need to fill out anything.
You do not need to migrate anything.
You do not need to press any buttons.
Just keep your KREX in a wallet that you control.
I will handle the rest.
🟢 3. 1:1 Airdrop
The new KCC20 KREX will be distributed 1:1 based on the snapshot.
If you hold 100,000 KRC20 KREX at the snapshot, you will receive 100,000 KCC20 KREX.
If you hold 1,000,000 KRC20 KREX, you get 1,000,000 KCC20 KREX. etc.
Exactly 1:1.
No more. No less.
🟢 4. Same supply and tokenomics
The new KCC20 KREX will have EXACTLY the same max supply and tokenomics as the current KRC20 KREX.
The supply will be redistributed to the eligible holders according to their exact snapshot balances.
21B max supply, 8 decimals, etc. Same as the current KREX.
🟢 5. What will happen to your tokens
Because this will not be a Bridge migration involving burn/lock/mint mechanisms, your old KRC20 KREX will not automatically disappear. It will not be burned or locked somewhere else.
You will therefore have TWO separate tokens in your wallet:
KRC20 KREX: the old token, which will no longer be supported in the ecosystem.
KCC20 KREX: the new token and the continuation of KREX on KCC20.
They will have the same tokenomics, but they will be different.
This is only a technological shift, not a fundamental change to KREX.
🟢 6. Remaining supply
Any remaining supply from dead/scam/dust wallets will be offered as a PUBLIC MINT for the community.
Existing holders get their KREX 1:1. The remaining supply will be available to everyone through a public mint at a fair price.
No extra supply, no dev or other allocations.
Just a fair launch, the way KREX has been since day one. We continue the tradition.
Everything that remains after the migration process will be fully offered to the community.
KaspaCom gets protocol fees. Miners get a boost from the mints again.
🟢 So, in simple terms:
Hold your KREX in a wallet you control, then snapshot is taken, then I handle the deployment and distribution, then you receive the same amount of KCC20 KREX 1:1.
No claiming. No migration window. No complicated process for holders.
The entire work and stress is on me as the dev. 😅🙏
#kaspa #kcc20 #migration #krc20
#KREX L2 Migration Notice ⚠️
If you currently hold KREX on L2, the best and easiest option will be to move your KREX back to KRC20 L1 before the migration.
However, after the recent issues involving kasplex indexer and centralized bridges, I am also preparing an additional backup solution, in case if some holders will get stuck there.
The amount of KREX reserved for the migration will also include the amount from the KAT Bridge wallet. This is the wallet that holds all the KREX on the L2 side across both networks, and whatever amount is in that wallet at the snapshot date will be reserved for the L2 holders.
The backup process will most likely be a simple Claim tool on Kasparex. Holders will connect their EVM wallet, connect the L1 Kaspa wallet where they want to receive their KCC20 KREX,, and verify both. I will then send the exact KCC20 amount based on their L2 balance at the snapshot.
However, there arent that many holders, and most of them are wallets with dust amounts (less than 1,000 KREX), which will most likely be excluded from the airdrop, so if anything, I can also handle everything manually, just in case. 🤝
Have a nice day, everyone! ☕️🌤️
OG33Z! ⚡️
Whoever hasnt seen it yet, check out this absolutely awesome collection created by the OG @AlxnderGomez 🔥😉
Thanks for the gift, brother, I feel super honoured! 🙏🍻
KaspaCom: kaspa.com/nft/collections/OG…
KasNftHub: kasnfthub.com/OG33Z
#ForTheCulture @Spudzbynotshore
KREX Token 𐤊 retweeted
Replying to @KrexToken
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
Who remembers what was happening during the KRC-20 minting era? ABSOLUTE MADNESS. 😉
People were chasing mints like crazy, haha... and I have a feeling we might see history repeat itself once it's live again.
Just an idea 💡
As some of you already know, KRC20 KREX has some dead/scam wallets holding large amounts of KREX, such as KnotMeme, Ascendex, and the old XT wallet.
Now, during the snapshot-based migration process, If I did a full 1:1 airdrop, I would have to make the KCC20 supply 100% preminted and send new KREX to these wallets as well and we would lose it for ever.
Old XT dead wallet: 1.85B KREX
AscendEX scam wallet: 393M KREX
KnotMeme scam wallet: 273M KREX
That's about ~2.5B KREX (dead/scam wallets)
Holder wallets: 18.5B KREX (your KREX balances)
Public mint
So the idea is, instead of sending the new KCC20 KREX to these scam/dead wallets, we could use that portion for the community as a public mint, giving everyone one last chance to get their bags cheap before the rocket lifts off, so to speak. ;)
This way, KRC20 KREX holders get their 1:1 share, while there is also room for the community to mint additional KREX to fill the gap created by the scam/dead wallet supply. KaspaCom would also get the protocol fees, and everyone would benefit. 🔥
On top of that, we would get a great boost for the project, and the KAS collected into the treasury could be used for many things, mainly providing liquidity, which could become a problem if we simply airdrop the new KREX to the old holders and that is it.
And whoever remembers the minting era doesnt need me to explain what could happen to your bags if the project gets another boost from new, fresh mints hehe 👀 🚀🚀🚀
What do you think about this idea? :)
------
PS
In the screenshot above, you can see a migration tool that I created for myself only, to help me go through the migration process smoothly, cover all the holders, and manage the entire process correctly.
The numbers you see are just raw, rounded draft calculations for example purposes.
#KREX HOLDER NOTICE ⚠️
Once the Kasplex indexer is working again, all KREX holders are strongly advised to move their KREX from CEXs such as CoinEx and XT into a personal, supported Kaspa wallet.
Make sure you control and have access to the wallet holding your KREX, as this wallet will be used for the migration/redemption process.
Tangem users should also move their KREX to a supported Kaspa wallet. That's because Tangem might not support KCC-20 anytime soon, so you may not be able to see or move your KCC-20 KREX. Tangem wallets use the following prefix: "kaspa:qy...".
Once the indexer is back, verify your balance, move your KREX to your own supported wallet and keep it there. 🔥
Also, I am reminding you that CoinEx is shutting down all operations, so I strongly advise moving your KREX to your self-custodial wallet as soon as possible.
"CoinEx to Cease Operations Starting Sep 15, 2026
CoinEx will cease operations starting Sep 15, 2026, and gradually discontinue related services.
Withdrawals will remain available until 02:00 on Dec 22, 2026 (UTC). Please complete asset disposal and withdrawals as early as possible."
Do not wait until the last minute. ⚡️
KREX Token 𐤊 retweeted
hello again. the devs made things this week and i made a list.
1 / Rusty Kaspa v2.1.0
nodes now download sync data in smaller chunks to avoid bottlenecks and timeouts while catching up with the network. v2.1.0 also includes Stratum bridge fixes and moves the existing zero-knowledge proof tools into their own package.
github.com/kaspanet/rusty-ka…
2 / vProgs
@Max143672 announced the first vProg running on testnet. it’s a playable tic-tac-toe game with real execution and settlement. still a working proof of concept, with public code for devs to build from.
xitter.cf/Max143672/status/21034…
3 / Python SDK
@smartgoo_ released Python SDK v2.1.0. devs can now compile SilverScript contracts in Python and debug them without running a node. it also adds tools for using zero-knowledge proofs, examples and bug fixes. SilverScript support is still experimental.
github.com/kaspanet/kaspa-py…
4 / SilverScript Studio
@KasperoLabs announced SilverScript Studio is live on mainnet. build, compile and deploy covenants from your browser. write them yourself, describe what you want to its AI, or use the wizards for things like vaults, escrow, recurring payments and payroll.
xitter.cf/KasperoLabs/status/210…
5 / KCC23
@manyfest_ explained a proposal for linking details like token names, symbols and images to a covenant, without copying them into every holder’s coins. KCC23 is still a draft and open for review.
xitter.cf/manyfest_/status/21030…
6 / KCC standards
@asaefstroem’s proposal to finalize KCC0 was merged. it sets out how shared ecosystem conventions are proposed and reviewed. he also proposed moving KCC20 into last call review. that hasn’t merged, so KCC20 is still a draft.
github.com/kaspanet/kccs/pul… github.com/kaspanet/kccs/pul…
7 / DNS seeder
@supertypo_kas released DNS seeder v0.9.6, fixing a bug that counted some offline nodes as online.
github.com/supertypo/simply-…
thanks to everyone building. see you next week.
While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined.
On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state.
On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant).
This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it.
A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information.
The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity.
After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself.
Read more on Kas-Smiths:
kas-smiths.org/t/kcc-23-conv…
Or read the KCC draft:
github.com/kaspanet/kccs/pul…















