Pinned post
IzioDev
Verified account This account is verified. Learn more@IzioDev
I'm not great, I'm not good, not even decent. But I'm trying, out of curiosity.
Yet another human on earth, just like you.
@Kaspa_KEF grantee since 12/15/2025
Yet another human on earth, just like you.
@Kaspa_KEF grantee since 12/15/2025
454 Following 1.8K Followers 1.6K Posts
Latest posts 5
a community funding wallet has been opened to reward security reporters who contributed in the software hardening, something that should be encouraged further.
here are all the details: discord.com/channels/59915…
here are all the details: discord.com/channels/59915…
get utxos by covenant id, which was a long awaited node feature is now approved.
you can build the node from source code and try this feature out now, or wait for upcoming release.
WASM support and JS example provided, should be easy to use.
just add "--covenant-index" to the arguments list.
thanks to @Max143672 for the feature :)
cc @kascovio
you can build the node from source code and try this feature out now, or wait for upcoming release.
WASM support and JS example provided, should be easy to use.
just add "--covenant-index" to the arguments list.
thanks to @Max143672 for the feature :)
cc @kascovio
Kas the coin can also be 'tokenized' as a kcc-20.
the need may not be very clear to everyone, but basically: my L1 app may want to uniformly manage kcc-20 and Kas the coin, without extra 'custom code'.
@manyfest_ details one of the direct use-case.
i have been convinced that designing kas-20 correctly only gives benefit with no tradeoff.
is it possible to have such an atomic covenant transaction that:
1. convert Kas to kas-20
2. trade it for the Many kcc-20 token
(=without adding one extra conversion step)
the need may not be very clear to everyone, but basically: my L1 app may want to uniformly manage kcc-20 and Kas the coin, without extra 'custom code'.
@manyfest_ details one of the direct use-case.
i have been convinced that designing kas-20 correctly only gives benefit with no tradeoff.
is it possible to have such an atomic covenant transaction that:
1. convert Kas to kas-20
2. trade it for the Many kcc-20 token
(=without adding one extra conversion step)
Onwards!View quoted post on X
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:
kas-smiths.org/t/a-kas-backed…
Status final = beginning of a new era
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.View quoted post on X
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.
