Regarding the Benjamin Cowen Situation:

Even after being wrong about the bottom, @benjamincowen has been more accurate than 99%!

Time to take my $KAS profits and rotate into $ZEC

Bro admitted he was wrong like that’s gonna make up for the millions of dollars I missed out on (didn’t deploy capital at the summer lows because I thought we were going lower in October like Benjamin COWARD said)

I was wrong Not going to make excuses I deserve to be dunked on

I wonder how this dude is doing... He sold $KAS at the literal bottom It's been rallying ever since

I was wrong Not going to make excuses I deserve to be dunked on

Update: $KAS KRC20 activity is currently suspended while the issue is being investigated. Our previous guidance remains - please avoid buying, bridging, transferring or accepting KRC20 tokens, including $NACHO, until further notice. We’ll keep sharing verified updates as the situation develops. 🐾

KRC-20 incident explained in simple terms 👇 Based on the information currently circulating, an attacker appears to have exploited the Kasplex KRC-20 indexing/accounting layer, creating balances that should never have existed. Those tokens could then be bridged into L2 environments and used against real liquidity, reportedly affecting pools involving $ZEAL and $NACHO. Think of it like this: Kaspa L1 = the bank vault KRC-20 indexer = the accounting software The vault wasn’t broken into. The accounting system was tricked into recognizing money that wasn’t actually there. That distinction matters. KRC-20 token balances are reconstructed off-chain by indexers. They are not balances enforced directly by Kaspa’s consensus rules. So, based on what we know right now: ✅ No evidence that Kaspa L1 consensus was compromised ✅ No indication that native kaspa:native itself was hacked ❌ The issue appears to be inside the KRC-20 accounting/indexing layer ⚠️ Bridged representations of affected KRC-20 assets may therefore have backing problems Until the teams publish the final post-mortem, I would personally: • avoid bridging KRC-20 assets • avoid providing liquidity to affected ZEAL/NACHO L2 pools • treat KRC-20 balances cautiously until the canonical indexer state is confirmed There’s also a bigger lesson here. The ecosystem was already moving toward KCC20 / native, L1-enforced assets, with plans to gradually retire KRC-20 routes. This incident shows why that distinction matters. Kaspa didn’t fail. An application/accounting layer built on top of Kaspa appears to have failed. Those are two very different things. Waiting for the official post-mortem before drawing harder conclusions.

just a gentle reminder that krc20 is not kaspa L1, it only travels over L1 txs as data carriers, but the interpretation of krc20 state is done purely offchain just like any other non-zk based solution. this is why covenants were developed for kaspa L1 with kcc20 built on top of them for native assets (note: kcc20 spec is still in draft)

What $If your favourite content creator got a free bag to hype $if then hype you telling you it is going to get you rich with bs and then sell before you even realised? If you still listen to them you deserved to be loose all your money because you don’t have a brain kaspa:native

We are in the rally now after the golden cross dump. A rally to a higher high and weekly closes above the 50W SMA would materially weaken the bear case. A rejection at these levels would still be in line with a bear market continuation

This one is for all the kaspa miners that just are in kaspa to get rich. Start moving you ass and create kaspa marketing you lazy mofos kaspa:native #miners #ks7 #acsis #kaspa

Kaspa fam, I need your help. After repeatedly falling in the loop of chasing losses upon losses, I’m literally down to zero. I even owe friends and I even struggle with basic expenses kaspa:qp2vxsuhfclkr43zxk3jwlxf4w3feajrn25tl643wqntpfcrpdct6ad6p6ejh Pls, help a fren. 🙏