#Dusk $DUSK @Dusk

I kept going back to Dusk’s Jan. 17 incident notice instead of the token chart.

What caught my attention wasn’t just the incident. It was the wording.

Dusk said monitoring detected unusual activity involving a team-managed wallet, bridge services were paused, and no user funds were impacted.

Very clean. Very controlled.

But other trackers were already describing an unauthorized actor draining DUSK through the Dusk → EVM bridge, with figures reportedly reaching the millions.

Same incident. Two very different narratives.

That gap is what interests me.

I’m not claiming I know the exact damage. I don’t.

What I find interesting is how a privacy and compliance-focused chain communicates when a bridge gets compromised.

Dusk was quick to separate the incident from DuskDS, but the actual scale seemed less clear at first.

From a legal perspective, I understand why.

From a user perspective, though, clarity matters.

Did anyone actually trace the on-chain movements from that window?

I’d rather see the wallet flows than trust either side’s framing.