Suspicious wallet activity hit Dusk's bridge infrastructure on Aug 16 — team caught it fast, recycled the compromised addresses, paused bridge ops. Normal incident response. But the fix they shipped is the part that made me stop scrolling.
They added a recipient blocklist to the Web Wallet. Transfers to known bad addresses now get flagged before you can even submit. On #dusk the network built around privacy-first tx architecture, $DUSK , @Dusk . Sit with that for a sec.
Here's the thing — Phoenix (shielded) was always opt-in, Moonlight (transparent) is default. Everyone talks about that split like it's the whole story. But this incident shows the real compliance layer isn't even at the protocol level, it's sitting right at the wallet UI, watching where your funds are headed. That's not a privacy chain reflex, that's a fintech reflex.
Kept refreshing the explorer waiting for bridge status to flip back, still paused as of now, tied to the DuskEVM rollout timeline apparently. Makes sense operationally. Still — a "privacy" project's fastest, most visible post-incident move was building a blocklist. Not shielding. Blocking.
Anyone else notice how often the "privacy narrative" and the "actual first response" point in opposite directions?
They added a recipient blocklist to the Web Wallet. Transfers to known bad addresses now get flagged before you can even submit. On #dusk the network built around privacy-first tx architecture, $DUSK , @Dusk . Sit with that for a sec.
Here's the thing — Phoenix (shielded) was always opt-in, Moonlight (transparent) is default. Everyone talks about that split like it's the whole story. But this incident shows the real compliance layer isn't even at the protocol level, it's sitting right at the wallet UI, watching where your funds are headed. That's not a privacy chain reflex, that's a fintech reflex.
Kept refreshing the explorer waiting for bridge status to flip back, still paused as of now, tied to the DuskEVM rollout timeline apparently. Makes sense operationally. Still — a "privacy" project's fastest, most visible post-incident move was building a blocklist. Not shielding. Blocking.
Anyone else notice how often the "privacy narrative" and the "actual first response" point in opposite directions?
