It is important to stay patient. Coming up with your own ways of doing things and disregarding the process of @kccforum contributes to nothing but ecosystem fragmentation. If you want to speed up the process, participate in the GitHub PR discussions.

The future of AI is local inference.

$KAS fam, lets show them our strength.

$KAS, we’re still early. I think the market was a bit ahead of its time last ATH. We are at a much more advanced stage now, and building so many things behind the scenes.

This is how we win, $KAS.

MORNING MOTION: GoPro is RUNNING, everything is going onchain, chatting KAS & ZEC nitter.net/i/broadcasts/1nxeLMnme…

This is a big milestone.

🚨Every Ledger running the Ethereum app is vulnerable to signature substitution A malicious dApp with WebHID access could race an APDU during your transaction review and swap the tx being signed while the device still shows the original Here's what you need to know:

The first three Kaspa Calls for Conventions (KCCs) have been published as DRAFT. together they propose a common base for Kaspa covenants, from low-level representation to a concrete token standard. kcc-01 formalizes the basic covenant concepts. they were already implicitly used in different forms by SilverScript, Argent and by some applications. the direct outcome is interoperability. wallets, indexers and applications can agree on how covenant state, entrypoints and templates are represented. it also makes higher-level discussions and reasoning easier. while working on kcc-02 and kcc-20, and with community participation, we had to return several times to kcc-01 and make its terms more precise. this is also a good reason to keep it DRAFT and open for discussion for some time. kcc-02 defines authority schemes. the need came directly from kcc-20: before defining token transfers, we need a shared way to describe who or what can authorize them. this is not limited to a public key owner. an authority can be a public key, a key commitment, a script or another covenant lineage (a covenant can be owner / governor of a token UTXO). the list of schemes is extensible, so more can be added later. for wallets, the goal is to recognize these authorities uniformly, only from the program ABI instead of learning a different format for every application. kcc-20 is the first "concrete composer". it defines common state and transfer conventions for fungible-token covenants. an application should be able to recognize a KCC-20 token, read it and construct transfers for it. the actual program can still be written in Argent, SilverScript or directly with opcodes. kcc-20 leaves room for token-specific extended state. an application can add its own data and behavior while keeping the base token state and transfer interface recognizable. the intent is not to make every token identical, but to keep a common interaction surface between different deployments. kcc-20 also introduces borrowed receive and its authorization schemes. token assets are separate from KAS, but every new token UTXO must still be funded with enough KAS under Kaspa's storage-mass rules. borrowed receive allows an existing recipient token UTXO to be reused instead. this feels natural for fungible tokens because its token amount can increase while its KAS value, owner and extended state stay unchanged. the owner must first opt in and select the authorization scheme controlling when this is allowed. the three drafts did not really happen one after another. kcc-20 showed that kcc-02 was needed, and kcc-02 required some missing definitions from kcc-01. publishing them together now allows each layer to be discussed and reviewed against a real use case. all 3 are drafts and community participation is needed.

Last September, I had the pleasure of attending the very first @KaspaExperience event in Berlin and what an incredible day that was!! I got to meet hundreds of people from the $KAS community for the first time, strengthened existing relationships and made new friendships! This event went on to create such a powerful impact and movement within the Kaspa community that I would very much like to see it happen all over again but here in London.. And so around 4 months ago, I started making enquiries about possible venues in well known areas of London aswel as reaching out to people and projects in the ecosystem with hopes to pool resources together and make this event happen After utilizing connections made between @BlockchainBants & @WolfysBar, we have found a great venue that can fit 250+ people for a relatively decent price and have pencilled in a date!! Not only this but we also set out to create & push the next @kaspathon with help from @Elliott_Blast, @Seb28_7, @iclblockchain & @Cambridge_Uni, we are organizing a week long hackathon across each University campus aswel as at the Kaspa Experience event in London There is already a huge community effort from people like @rhubarbmedia, @argonmining, @KaspaQueeen & @imaldev all lending their time, efforts and resources to the cause We have also been speaking with a few Kaspa core developers and they have expressed keen interest in attending everything So if you want to make history by being a part of the next @KaspaExperience event & also the next @kaspathon then get in touch with me and lets make this happen 🤝

Great things are coming for kaspa:native

This is a good term. Don’t be a meat proxy. It the 2026 term for the ”don’t be a script kiddie”.

I agree with this. It is similar to the fact that the best code, is the code that was never written.

Let’s be clear, it was Toxic Bitcoin Maximalists that led people to use Coldcard. They ignored science for virtue signaling. Marketing like "Bitcoin-only wallet" and "roll a dice a hundred times on an air-gapped device" led them astray. Simplicity is key for security—the more complicated, the higher the risk. The more niche, the higher the risk. But because the founder passed the purity test, rationality went out the window. @Trezor is the gold standard for individuals. MPC for institutions. Have single seed or Shamir multi-seed. Use passphrase or not. It doesn’t have to be harder than that. But just like when they dismissed virtual mining/PoS, they threw out rationality for a purity test. Now they recommend multi-vendor multi-sig. Sigh. Block these people.

Does $KAS want onchain DeFi?

Bridged stablecoins will always be bound to the consensus algorithm of its origin. Bridged stablecoins from PoS/PoA chains, will always be PoA/PoS secured.