Went looking for something to write about $DUSK for CreatorPad and landed on @Dusk bridge incident notice from August 16 instead of the roadmap pages. The phrase that got me: "a team-managed wallet used in bridge operations." For a project that leans so hard on decentralized, compliant, self-custodial messaging, that's a fairly plain admission that a human-controlled key sits somewhere in the bridge path.
Nothing catastrophic happened, by their own account. Addresses were disabled and recycled, bridge services paused, a small set of transactions occurred in the window, and coordination with Binance closed off part of the flow. DuskDS itself wasn't touched.
What changed for me wasn't the severity, it was the framing. I'd been treating "self-custody" as something that applied everywhere in the stack. It applies to the user's wallet. It doesn't automatically apply to the infrastructure moving assets between chains on their behalf, and that's a distinction most users, including me, gloss over.
Bridge is still offline while they finish hardening it. Not sure that gap gets closed just by better monitoring.
#dusk @Dusk
Nothing catastrophic happened, by their own account. Addresses were disabled and recycled, bridge services paused, a small set of transactions occurred in the window, and coordination with Binance closed off part of the flow. DuskDS itself wasn't touched.
What changed for me wasn't the severity, it was the framing. I'd been treating "self-custody" as something that applied everywhere in the stack. It applies to the user's wallet. It doesn't automatically apply to the infrastructure moving assets between chains on their behalf, and that's a distinction most users, including me, gloss over.
Bridge is still offline while they finish hardening it. Not sure that gap gets closed just by better monitoring.
#dusk @Dusk
