#dusk $DUSK @Dusk Kept getting pulled back to that January notice from Dusk instead of the charts.

What actually stuck with me wasn’t the incident itself. It was the tone. Their official update on the 17th (Georgian Sgura) framed it as monitoring catching odd activity on a team-controlled wallet, bridge paused, addresses rotated, and a clear statement that user funds weren’t touched. Very measured, almost clinical.

Meanwhile a bunch of independent trackers were already calling it an unauthorized drain of DUSK from the Dusk–EVM bridge, with numbers in the millions floating around.

Same event, completely different energy.

That gap feels more interesting than the size of the hit. How a privacy-and-compliance focused chain chooses to talk about something that hits the least “core” part of the stack (the bridge). They moved fast to draw a line between this and DuskDS itself, slower to put hard numbers on the table. Makes sense from a liability standpoint, still leaves a weird taste from a user one.

I re-read the notice a couple times after eating and I still can’t tell whether “limited number of transactions” means a handful or a few hundred.

Anyone actually go look at the on-chain flows from that window themselves instead of just picking a side’s version?
#DUSKARMY. #Dusk/usdt✅ #Dusk. #duskcoin $DUSK