NEW WALLET JUST APPEARED Wallet was created today (Sep 23, 2026) and immediately received 24,960,857 $KAS worth approximately $965,000 in its very first transaction. Is this the start of a new institutional accumulation? Or just a routine transfer? Time will tell. #kaspa

$BTC $LTC and $ZEC all walked so the 10 blocks per second kaspa:native could run. The tech isn’t even close. #ProofOfWork #Crypto #Kaspa

Quiet but big: Kaspa's standards process just proved it works. 🏁 KCC-0 — the document that defines HOW Kaspa conventions get finalised — reached Final on Sept 21. The first KCC ever to cross the line. 📣 And now KCC-20, THE covenant token standard, has an open PR proposing Last Call — the final review stage before Final. Also in the pipeline: a wallet API standard (KCC-12), covenant metadata (KCC-23), and a brand-new domain — reputation, bonds and identity as covenants. No foundation decree. No backroom. Every stage change is a public pull request anyone can read. That's how you grow a standard.

October 7th, 8 PM CET

We appreciate the update and the work already in motion. One ask from the community: please do this revert the careful way. Replay the full Kaspa history on the fixed indexer if you can, rather than skipping a DAA score range. @argonmining raised that here. A lot of KRC-20 / L2 holders are just trying not to get caught in the middle. Happy to wait on the 3–5 days. Clarity on the method would help everyone sleep. $KAS $NACHO

huge honor but I’m also nervous ngl

Another great one is kaspa:native. This one signaled a bottom was happening at the low, as there was a strong bullish divergence in play. Since then: continuation with higher highs, higher lows and constant flips of the levels. I don't think that this will stop soon, especially if this takes out the recent high, the next target for me is $0.0743.

@binance, Thanks for including me in the top 100 blockchain people list, appreciate the signal! I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out. Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed. There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <<Binance should hold a privilege policy for the latter.>> A TBTF CEX should know better and play a different game with hardcore crypto projects. When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement. You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog? Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point. @cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity. Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto. We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes. Please fix this. Thanks again, hashdag cc @michaelsuttonil Exhibit A: Binance Innovation Zone Exhibit B: 10 bps Nakamoto Consensus

Never. Stop. Fighting. $NACHO $KAS

$KAS Wants Binance Spot Listing! The Kaspa community is making noise. Let’s show Binance the demand for a $KAS spot listing. Like, repost, and comment to spread the word. 🔥 Binance, are you listening?

kaspa:native — breaking out of a massive Rectangle 👀 KAS has been ranging between $0.025 and $0.045, with buyers now pushing toward the top of the range. A clean breakout above $0.045 resistance could signal a major momentum expansion 📈🔥 The chart projects a potential move toward $0.065 if the breakout holds. Market sentiment: Bullish — bulls are testing a major breakout zone. kaspa:native #Kaspa #Crypto #KAS #Trading

Wait a minute. What’s going on here.

Yeah, not going to hold my breath for 5% lower.. We got a few jaded investors talking that -75% is still on the table for kaspa:native Honestly love the imagination and creativity to draw lines to trick yourself into thinking .01 is still in play

We're not stopping!! Now it's time to make some real noise for Binance. Let's make sure Binance hears us loud and clear: we want $KAS listed! Let's show them the strength of the Kaspa community. Like, repost, and drop a comment to spread the word!

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…

Confirmed by Kaspa. Feasting on $KAS. 🐈‍⬛ we thicc

⚠️ KRC-20 incident response update Thank you for your support and understanding. It's been encouraging to see the professionalism and coordination across the Kaspa ecosystem during a difficult few days. We're working with Swiss legal counsel on the handling of incident-linked and returned funds, including the final distribution plan. iKAS to KAS canonical exits have resumed. Under the updated settlement policy, operators will release the portion cleared by review and withhold only the amount attributed to the incident. Because of these reviews, waiting times are longer than usual. Additional hardening is planned for the Hyperlane bridge before it reopens. We'll share the implementation and reopening criteria as they are confirmed. Our priority is restoring access for legitimate users while continuing recovery efforts for those affected. With questions or comments, please reach out in DM, on Telegram t.me/IgraCommunity and Discord discord.gg/invite/igralabs.

nacho-the-kat:native Nation and kaspa:native never stops fighting! 🥊💚

PEak

internet money should move at internet speed.