I went digging for that old BEP20 bridge address today, the one from before January, just checking I'd never used it.

Found Dusk's incident notice instead. Jan 16th, the team's bridge-ops wallet got compromised, DUSK moved to BSC before the route shut down.

First read, I lowkey figured that was it, an ops mistake, contained, not my problem since DuskDS itself wasn't touched.

That's not quite where it stops. DuskDS holding everything correctly was never in question, storage wasn't the weak point. Availability was, that wallet had to stay hot and reachable to work, and the same reachability made it a target.

Moving DUSK to BSC never touches consensus. It routes through a wrap step needing one operational signer to say yes, sitting outside anything DuskDS itself guarantees.

Makes sense why the roadmap keeps moving BEP20 and ERC20 DUSK into DuskEVM's native bridge, no separate hot wallet standing in between.

I don't know the timeline for retiring the old routes entirely, or what's still quietly using them.

Institutional volume through NPEX keeps growing 👍. What happens next time convenience needs one wallet to stay hot somewhere in the stack, and nobody notices until it's the story?

#dusk $DUSK @Dusk