On August 16, Dusk's team caught something off — suspicious activity tied to a wallet used in bridge ops. Was reading through the response while going through Dusk $DUSK #dusk Network @Dusk Foundation for this task and hmm… it wasn't the privacy tech that kicked in first.
The team didn't reach for Phoenix's shielded layer to contain anything. They disabled and recycled the bridge addresses, paused bridge services, and rolled out a Web Wallet blocklist to stop transfers reaching flagged addresses — then coordinated directly with Binance once they traced part of the flow. All of that sits on the transparent, account-based Moonlight side, not the zero-knowledge one.
Kind of reframed how I was thinking about the whole "dual transaction model" pitch. Phoenix gets the spotlight in every deck — shielded balances, confidential UTXOs, ZK proofs. But when something actually goes sideways, it's the auditable, blocklist-capable rail that does the work. Privacy is the feature you market. Traceability is the feature you reach for when it counts.
Not knocking the design — arguably that's the point of having both. Just wasn't expecting the "boring" transparent side to be the one pulling containment duty in a live incident.
Makes me wonder how often Phoenix actually gets touched in situations like this versus just sitting there as the marketing centerpiece
The team didn't reach for Phoenix's shielded layer to contain anything. They disabled and recycled the bridge addresses, paused bridge services, and rolled out a Web Wallet blocklist to stop transfers reaching flagged addresses — then coordinated directly with Binance once they traced part of the flow. All of that sits on the transparent, account-based Moonlight side, not the zero-knowledge one.
Kind of reframed how I was thinking about the whole "dual transaction model" pitch. Phoenix gets the spotlight in every deck — shielded balances, confidential UTXOs, ZK proofs. But when something actually goes sideways, it's the auditable, blocklist-capable rail that does the work. Privacy is the feature you market. Traceability is the feature you reach for when it counts.
Not knocking the design — arguably that's the point of having both. Just wasn't expecting the "boring" transparent side to be the one pulling containment duty in a live incident.
Makes me wonder how often Phoenix actually gets touched in situations like this versus just sitting there as the marketing centerpiece