I found something in Dusk’s history that I didn't particularly enjoy reading.
Not because the protocol got hacked.
It didn't.
The bridge did.
On January 16, 2026, someone got access to a signing wallet used by Dusk's Dusk-to-EVM bridge.
Then the numbers started getting ugly.
9,000 DUSK.
89,700.
2.74 million.
Then another 8.07 million.
By the time Dusk shut the bridge down, several million DUSK had already been moved. A final 8.91 million DUSK bridge attempt failed after the shutdown.
I actually like reading incidents like this more than another “our security is industry-leading” announcement.
Because this is where architecture gets tested for real.
The interesting part wasn't some mysterious consensus attack.
The attacker didn't break Dusk's finality.
They got the signing wallet.
And once that wallet was compromised, too much authority was sitting behind one operational path.
Dusk's post-mortem admits that pretty directly.
The redesign separated signing from event handling, introduced an explicit transaction lifecycle, reduced the balance exposed to the hot signer, and isolated the bridge service.
That's a much less exciting story than “Dusk stopped a massive exploit.”
But honestly, I prefer it.
Because bridges don't get to hide behind the phrase “the underlying chain is secure.”
If users trust the bridge with their assets, the bridge becomes part of the security perimeter whether the protocol likes it or not.
I don't think one incident tells me that Dusk is unsafe.
But I also don't think it should be forgotten just because the bridge was rebuilt.
I'd rather watch what happens next.
$DUSK #Dusk @Dusk #dusk $DUSK @Dusk
Not because the protocol got hacked.
It didn't.
The bridge did.
On January 16, 2026, someone got access to a signing wallet used by Dusk's Dusk-to-EVM bridge.
Then the numbers started getting ugly.
9,000 DUSK.
89,700.
2.74 million.
Then another 8.07 million.
By the time Dusk shut the bridge down, several million DUSK had already been moved. A final 8.91 million DUSK bridge attempt failed after the shutdown.
I actually like reading incidents like this more than another “our security is industry-leading” announcement.
Because this is where architecture gets tested for real.
The interesting part wasn't some mysterious consensus attack.
The attacker didn't break Dusk's finality.
They got the signing wallet.
And once that wallet was compromised, too much authority was sitting behind one operational path.
Dusk's post-mortem admits that pretty directly.
The redesign separated signing from event handling, introduced an explicit transaction lifecycle, reduced the balance exposed to the hot signer, and isolated the bridge service.
That's a much less exciting story than “Dusk stopped a massive exploit.”
But honestly, I prefer it.
Because bridges don't get to hide behind the phrase “the underlying chain is secure.”
If users trust the bridge with their assets, the bridge becomes part of the security perimeter whether the protocol likes it or not.
I don't think one incident tells me that Dusk is unsafe.
But I also don't think it should be forgotten just because the bridge was rebuilt.
I'd rather watch what happens next.
$DUSK #Dusk @Dusk #dusk $DUSK @Dusk