#dusk $DUSK @Dusk A closer look at the January Dusk incident.

Dusk’s Jan. 17 notice described unusual activity involving a team-managed wallet, paused bridge services, and said user funds were not impacted.

What caught my attention was the gap between that calm wording and external reports describing an unauthorized actor draining DUSK through the Dusk-to-EVM bridge.

Same incident, very different framing.

For me, the bigger question isn’t just how much was lost. It’s how a privacy/compliance-focused chain communicates when a bridge gets hit.

I’m curious: did anyone independently trace the on-chain flows from that window instead of relying on either side’s narrative?
$DUSK