Crypto Trader & Early x100 Gem Hunter. KRC20/Kaspa TG Community: https://xitter.cf/t.co/QZuImzx7bN https://xitter.cf/t.co/BngxNpeEn8 $KAS #KRC20 enthusiast - DM for collabs

Joined April 2021
hashdag (“Opening the Pandora box” with Ori Newman) & myself (DAG Knight), speaking here next
14
189
4
586
11,272
There is clear sell liquidity above between 0.0365 and 0.0385 and strong buy liquidity sitting below around 0.0350-0.0345. That’s the only thing holding price up right now, we’re stuck right in the middle, price keeps testing both sides but nothing is breaking yet and volume is also pretty low, so neither side has real strength. We'll see when one of these levels actually gets taken out with force. A break and hold above 0.0365 would be the first good sign and until then it just feels like more sideways action. #kaspa kaspa:native
Kaspa remains caught between significant liquidity clusters on both sides of the market. Sell-side liquidity is concentrated above the current price, particularly around $0.0365–$0.0385, while substantial buy-side liquidity sits below, near $0.0350–$0.0345. With liquidity stacked in both directions, KAS remains range-bound at the moment.
3
34
827
RT @Kaptain_Kaspa: Hey Kaptains & Kaspa fam 👋 Been a little quiet lately...the team got split up on different continents, half a world a…
2
122
Crypto is back in Israel’s national conversation. ⚡️ Earlier this year, KaspaCom CEO @cryptosione appeared on national economic TV to talk Kaspa, its technology, and adoption. Tune in. 👇
20
136
9
498
25,058
Here is another important one I missed, great potential with this also. #GUZA #Kaspa kaspa:native
I went through the KCC20 board and these early memes are already doing their thing. DAGAS is still sitting on top with a clean +337% and holding around 0.120 KAS with solid volume for the size, LUCIFER climbed into second at +170% but it’s still paper thin and super concentrated. LKAS just ripped to +133% in the last stretch and pushed higher, though six holders tells you everything about how fragile that move is. BTE cooled off to around +76% but still looks the healthiest so far, Price is near 0.232 KAS, market cap over $8.7k, best volume on the list and fifty holders. That distribution and actual activity is what draws my attention compared to the rest. LOCK is trailing at +50%. The ones with a bit more participation and real volume are the only ones that feel like they have any staying power right now. Early days of native Kaspa tokens and this looks promising. #kaspa $kas
4
7
32
1,005
📢 nacho-the-kat:native Incident Recovery & KCC20 Migration: Where We Stand Original KRC20 supply: 287B Migration snapshot supply: 330B What happened on Sept 20: A vulnerability in the KRC-20 standard (Kasplex) was exploited to forge ~49B NACHO from the layer 1 (L1) vault, inflating the total supply with unbacked layer 2 mints. Incident response: → Paused KatBridge the same day → 6B+ nacho-the-kat:native voluntarily burned by holders working with us (legends forever) → Burned all remaining nacho-the-kat:native in the L1 vault to lock in the final number. 🔗 Vault Burn TX: kaspa.stream/transactions/9f… The L1 vault now holds zero NACHO, and every token is accounted for. Next step, finalize the KCC20 migration tool that any project that was supported by KatBridge will be able to use. Then, deploy the nacho-the-kat:native KCC20 token and begin migration from KRC20 NACHO or ERC20 NACHO on Kasplex or Igra. The burn has only just begun. Supply keeps going down from here: 🔥 → Voluntary burns during the KCC20 migration. 🔥 → Migration fees used to buy and burn. 🔥 → Unmigrated tokens burned after the window closes. Every token burned, even on KCC20, reduces all calculated supply metrics including the max supply, total supply, and circulating supply. These are the standard supply metrics that are verified across crypto dashboards that we will keep updated, so that you can see the direct impact of each burn! ⚠️ There is no official KCC20 NACHO token yet. Anything claiming to be one is a scam. The official migration will be announced only through our verified channels. Stay nacho-the-kat:native. 🐾
14
40
2
152
6,958
I went through the KCC20 board and these early memes are already doing their thing. DAGAS is still sitting on top with a clean +337% and holding around 0.120 KAS with solid volume for the size, LUCIFER climbed into second at +170% but it’s still paper thin and super concentrated. LKAS just ripped to +133% in the last stretch and pushed higher, though six holders tells you everything about how fragile that move is. BTE cooled off to around +76% but still looks the healthiest so far, Price is near 0.232 KAS, market cap over $8.7k, best volume on the list and fifty holders. That distribution and actual activity is what draws my attention compared to the rest. LOCK is trailing at +50%. The ones with a bit more participation and real volume are the only ones that feel like they have any staying power right now. Early days of native Kaspa tokens and this looks promising. #kaspa $kas
6
1
3
38
2,352
I've been seeing some people say nothing is happening with Kaspa, price is quiet and a lot of people have already moved on but that’s when you should pay the most attention. The real work on a network doesn’t always show up in the daily candles, infrastructure keeps getting refined in the background, standards keep moving forward. The chain just keeps running while most of the market looks elsewhere, you don’t get rewarded for only showing up when everything feels exciting and the narrative is already loud. You get rewarded for staying through the stretches that feel slow but waiting until everything looks obvious before deciding something is worth holding feels like the wrong approach to me. The quiet periods are often where the real positioning happens and that's the part I focus on with Kaspa. #Kaspa $KAS
2
14
1
136
2,847
🚨Korea INSIGHT: Kaspa privacy development has reached a new milestone, with developer Olaf Weller (@WellerOlaf) completing a proof of concept for shielded native $KAS payments on testnet TN10. The tests demonstrated transaction ordering, zero-knowledge proof execution and proof-based settlement directly on Kaspa Layer 1. The next phase will focus on designing private notes, commitments, nullifiers and the proof rules needed to support shielded transactions. However, the system has not undergone an independent audit and remains a work in progress, rather than a finished privacy protocol. @kaspaunchained
11
70
341
9,335
Once any wallet or indexer starts ranking what’s “legit” nacho or any other token, you’re just back to trusting some external list again, which is the opposite of what people wanted after krc20. Partial covenant id next to the ticker helps the ones who actually look and github pr style database is clean for the builders who care, but most people still won’t check. kcc-23 binding the metadata is a solid step, still doesn’t stop two different people deploying the exact same looking thing though. I’m curious if a lightweight name service for covenants ends up being the pragmatic middle ground, or if we just accept that retail will always need some curated layer and design around that honestly. #kaspa $kas
Wallets and indexers: how are you planning to tell identical KCC-20 tokens apart? I deployed two tokens with the same name, ticker and image. The only difference between them is the covenant ID. I can show the covenant ID, but how does that help a normal user? Are they expected to compare it against the project’s website themselves? Will every comment section turn into “yeah, but did you check it was covenant ID d9182f3e6fdbf9e98d4ecae07dccd3a022606810720259f40eb4133686d05f4d before buying?” For a wallet it’s mostly a display problem. Trading platforms and DEXs have the harder job. I’d love to hear how others are approaching it.
7
21
935
We’ve come down hard from the recent highs and price is sitting right on the lower Bollinger Band. Volume came in on the sell, which is normal but the structure here feels like it’s testing a zone that could offer a bounce if buyers step in. I’m not calling a bottom, but after a move like this I usually pay attention when it reaches the lower band with the kind of exhaustion we’re seeing. If it holds and starts to reclaim the middle band, this could turn into a solid accumulation area for me. I'll be watching how it behaves from here. #Kaspa kaspa:native
2
3
35
1,424
Kaspa largest wallet, Entity X, continues accumulating. Another 1.98 million KAS has been transferred from Gate. io, bringing its total holdings to approximately 1.53 billion KAS, currently valued at $54.83 million. Despite occasional outflows, the wallet's balance has been trending higher in recent weeks, indicating continued net accumulation.
16
2
123
3,955
Yeah the stickiness is the proof that people see beyond charts. Most projects lose probably half their community the second the chart stops going up as expected for a while and kaspa community just keep building and buying more like nothing happened. That quiet conviction is rare and the agent angle hits different too. Once you have software that actually needs to transact on its own, the chain has to be fast, cheap, and actually decentralized. Kaspa is one of the few that was designed for that from day one instead of trying to add or build it on later. Appreciate you putting eyes on it. #kaspa $kas
$KAS community is still alive 🐂 Very rare honestly to have people stick around even through a bear market and still be just as bullish on the asset. Love to see it. In the age of agents, $KAS is still interesting for the cypherpunk crowd wielding agents and creating software of the decentralized ethos and who will need a decentralized, secure, and scalable cryptocurrency for agents to use to transact. The world’s focus is very much on AI and less so on forms of money, but understanding how the two relate may be useful as a value gauge and investment thesis on cryptocurrencies over the next ten years.
2
20
811
CryptOG retweeted
kcc20 is about making it easier for wallets and apps to work with tokens on kaspa. it proposes a shared way to describe who owns the tokens, how many they hold and how transfers work. it gives builders a common format to follow when their wallets and apps read token information or prepare transfers. kcc20 is now in last call, its final review before becoming a finalized standard.
11
110
7
473
18,462
Consistent energy and effort from you Anticipating the release 😉 #kaspa $kas $KPTKAS
⚓ Kaptains, the wait is almost over! The team has been building in silence for a while now… and we're finally ready to reveal something special. 👀 🖼️ Introducing the upcoming $KPTKAS NFT collection: 🔥Kaspa People Borderless Horizons 🔥 Launching soon on @KaspaCom! 💎 Genuinely affordable mints. 💰 100% of mints will go straight to $KPTKAS treasury to fuel future $KAS marketing missions and help secure a proper CEX listing, bringing us closer to trading $KPTKAS on a major exchange. No empty promises. Just a community building, creating, and pushing Kaspa adoption forward. 🦾 👀 Stay tuned, Kaptains! This is just the beginning, we got LOTS of surprises 🔥 🔥 Here's a little teaser of what's coming 👇
1
15
562
Remember when.. Bro came Bro build Bro won most votes on Binance Bro said f you Binance Bro left Be like bro.
10
25
1
346
7,231
ZEAL Recovery Update The Kasplex KRC20 indexer is now operational again, and the custody balances now align across the independent indexers. This gives us enough clarity to publish the current ZEAL supply situation and the recovery measures we are moving forward with. The original KRC20 supply remains 240,000,000 ZEAL. Of that, 167,187,982.93 ZEAL is held by the bridge custody address and backs ZEAL on the L2s, while 72,812,017.07 ZEAL is held directly by users on KRC20 L1. On the L2s, Igra currently holds 216,275,848.19 ZEAL and Kasplex L2 holds 48,337,560.83 ZEAL, bringing the combined L2 supply to 264,613,409.01 ZEAL. Since only 167,187,982.93 ZEAL is backed by L1 custody, this leaves a 97,425,426.08 ZEAL supply gap created by the KRC20 indexer incident. As part of the recovery plan, the first decision we have made is to permanently burn the entire 24,000,000 ZEAL team allocation. We believe taking responsibility should start with us. Even though the incident did not originate from ZealousSwap, preserving a future team allocation while the community deals with the consequences of the incident is not the direction we want to take. The full allocation will be removed permanently, and there will be no future team unlock. Farm rewards and Infinity Pool emissions will also remain paused. On Igra, we will burn 43,794,947.23 ZEAL in Farm rewards that have not yet been distributed and 38,409,590.09 ZEAL in future Infinity Pool emissions. This brings the total Igra burn to 82,204,537.32 ZEAL. On Kasplex L2, in addition to the full team allocation, we will burn 7,200,000 ZEAL from the Insurance Fund, 4,586,310.61 ZEAL in undistributed Farm rewards and 681,650.32 ZEAL in future Infinity Pool emissions. The total Kasplex L2 burn will be 36,467,960.94 ZEAL. Altogether, 118,672,498.26 ZEAL will be permanently burned. This is 21,247,072.18 ZEAL more than the 97,425,426.08 ZEAL supply gap, meaning the gap is covered approximately 1.22x. Following the burns, the maximum ZEAL supply will fall from 240,000,000 to 218,752,927.82 ZEAL. We also want to be very clear about what these burns do and do not change. They do not reduce the ZEAL already circulating today. The tokens sold during the incident are now held by users who purchased them legitimately, and those trades remain valid. We will not rewrite what happened onchain or treat those holders differently. Circulating supply was approximately 118,087,936.62 ZEAL before the incident and is approximately 215,627,642.88 ZEAL today, an increase of roughly 97,539,706.26 ZEAL. The supply we are burning comes from protocol reserves that had not yet entered circulation. Before the incident, approximately 121.9 million ZEAL was still scheduled to enter the market over time through Farm emissions, Infinity Pool emissions, the team allocation and the Insurance Fund. After these burns, that future supply overhang is effectively removed. Approximately 98.6% of all ZEAL that will ever exist is already circulating. The remaining portion consists primarily of Farm rewards that users have already earned but have not yet claimed. This means there will be no future team unlock from the burned allocation, no future Insurance Fund allocation entering circulation, and no further Farm or Infinity Pool emissions from the reserves being removed. ZEAL’s future inflation from these allocations is effectively eliminated. Approximately 98.6% of all ZEAL that will ever exist is already circulating, with the remaining portion consisting primarily of rewards farmers have already earned but not yet claimed. There is no longer a large emission schedule or unlock overhang waiting to enter the market. We are still waiting for Igra to provide an update regarding the future of the funds recovered from the attacker, and we will update the community as soon as there is more clarity there. 👇
31
44
10
153
11,817
Every covenant leaves its mark on the DAG $KAS
5
23
2
62
1,060
CryptOG retweeted
MARA continues moving KAS out of its main wallet. After a large outflow of roughly 30M KAS on September 28, that ended up goinf to Gate .io, since then additional outflows have continued daily. The wallet balance has now fallen from around 28M KAS immediately after the initial transfer to roughly 20M KAS today, another ~8M KAS moved since.
10
16
1
123
8,302
The most interesting new Kaspa development is happening above consensus: the ecosystem is beginning to standardize how programmable applications actually talk to each other. Toccata gave Kaspa covenants, covenant IDs, ZK verification and sequencing commitments, but those primitives alone do not create an application economy. Developers still need common answers to questions like: How is covenant state encoded? How does a wallet identify an entrypoint? How does one covenant authorize another? What does a token transfer look like to an indexer that did not create the token? This is what the emerging Kaspa Calls for Conventions, or KCCs, are attempting to solve. KCC-1 and KCC-2 have now progressed to Last Call. KCC-1 defines common covenant terminology, byte layouts, state encoding, dispatch tags, Covenant ID lineage and ABI conventions. KCC-2 goes one level higher by defining standardized authority schemes: Schnorr keys, key hashes, P2SH programs and even Covenant IDs themselves can act as authorities. That last mechanism is particularly important because it allows one persistent covenant lineage to authorize actions inside another application. In other words, Kaspa is developing standardized inter-covenant communication. Then KCC-20 applies these foundations to fungible tokens, defining common token state and transfer behavior rather than forcing every token implementation to invent an incompatible protocol. This may sound less exciting than 100 BPS or DAGKnight, but it addresses a completely different scaling problem: ecosystem fragmentation. A programmable network becomes dramatically more useful when wallets, indexers, exchanges, Argent applications, SilverScript covenants and eventually vProgs can interpret the same objects without bespoke integration work. Kaspa spent years solving how decentralized transactions should be ordered quickly. Toccata added programmability. The KCC layer is beginning to answer the next question: how do thousands of independently built programs understand each other? That is the point where primitives start becoming an ecosystem.
2
41
2
118
2,741