Daily Pulse

Your daily dose of Kaspa market insights, news, and analysis.

Bitget hacked: why was $KAS untouched?

Bitget hacked: why was $KAS untouched?

Why was KAS untouched when a major exchange was hit? Today's Pulse covers the breach fallout and the self-custody scramble that followed.

Hey, welcome to Kaspa Daily Pulse, here's what the Kaspa community's been buzzing about today.

First up, the biggest story was the reported Bitget hack. Numbers shared in the chat varied, with estimates ranging from roughly $180 million to $352 million. One update claimed around $183 million had been swapped into Ether-based tokens. Withdrawals were suspended while Bitget tightened security, and CEO Gracy Chen was quoted saying, “User funds are safe.” Community members also said cold wallets were unaffected and funds were insured up to $420 million, although plenty of users remained nervous.

Interestingly, several people said the attackers focused on XRP and ETH, apparently leaving KAS untouched. The community had mixed feelings about that one. Some saw it as good news, while others joked that Kaspa simply was not worth stealing.

The incident triggered a much broader self-custody debate. Tangem, Ledger, Trezor, hot wallets, cold wallets, seed phrases, and exchange insurance all got dragged into the conversation. The dominant mood was clear: keeping crypto on a centralized exchange creates counterparty risk, especially when withdrawals can be frozen without warning. Tangem’s previously resolved issue, where wallet keys could potentially reach customer support through logs, was also raised as a reminder that hardware wallets are not automatically flawless.

Next, Kasplex users reported wallet problems, including a network error with status 530 and KRC-20 balances temporarily disappearing from view. Community members linked this to an indexer outage and possibly the recent hack, but that connection was not confirmed. The reassuring technical point was that the tokens remain stored on the blockchain, even when an indexer or wallet interface cannot display them.

On development, contributors offered a rare glimpse into the size of the team. One estimate put recurring contributors at around ten, with roughly five or six working full-time. Max was identified as hosting the prover, while another contributor said they operate the data availability layer and web app. The community also discussed pending pull requests, DAGKnight, vProgs, and the upcoming energy summit involving KII.

Finally, price sentiment heated up. Traders said KAS had risen about 50 percent from recent levels and was challenging the four-cent area, with five cents becoming the immediate target. Bulls were calling for six or even eight cents, while skeptics warned that another rejection remained possible.

That's it for today's pulse. Let's see what tomorrow brings. Catch you then.

All Episodes