#dusk $DUSK @Dusk Spent the CreatorPad window poking around @Dusk's transaction models instead of just reading the pitch deck, and the bridge incident from last week is what actually made it click for me.
Aug 16, Dusk's monitoring flagged suspicious activity tied to a team-managed wallet used in bridge operations. Team disabled and recycled the related addresses, paused bridge services, and this is the part that stuck shipped a Web Wallet recipient blocklist to stop transfers to known dangerous or sanctioned addresses. Coordinated with Binance once part of the flow touched their platform. No user funds impacted, per the team's own notice.
Here's the thing. $DUSK's whole pitch is Phoenix and Moonlight, pick your privacy level, switch back and forth whenever. Phoenix is the shielded UTXO model, notes and nullifiers, ZK proofs, no sender/receiver/amount visible without a view key. Moonlight is account-based and public, balances sit in plain sight, built for easy compliance reporting.
Cool duality on paper. But watch what got reached for the second something looked wrong: the fix that shipped was a blocklist on the transparent side. You can screen a Moonlight address against a sanctions list in real time. Screening a Phoenix note the same way is a lot harder, that's the whole point of it existing.
So "switch back and forth at the click of a button," sure, technically true. But the emergency lever was the public rail. Not knocking the call, probably right. Just noticing the dual model isn't symmetric under stress.
Makes me wonder if regulated users end up defaulting to Moonlight for anything that might need fast incident response, and Phoenix stays the wrapper for stuff nobody's worried about freezing. Anyone seen an actual Phoenix-side incident response yet, or is that still untested?