#dusk $DUSK @Dusk Was digging through Dusk Network's recent bridge incident notice for a CreatorPad task, and something small stuck with me more than the actual security stuff.
On August 16, $DUSK's team flagged suspicious activity on a team-managed bridge wallet — disabled the addresses, paused bridge services, shipped a Web Wallet recipient blocklist, looped in Binance once part of the flow touched their platform. @DuskFoundation confirmed DuskDS mainnet itself was never touched, no protocol-level issue. All handled fast, in what reads like hours.
Here's the part that got me though — none of that response ran through any governance process. No vote, no proposal, no token holders weighing in. Just the team, moving quickly, making calls unilaterally. Which… makes sense, honestly, you can't put a live security incident to a vote. But it did make the "on-chain governance is on the roadmap" framing feel more like a future promise than a present reality.
Had this half-written assuming I'd find some proposal thread buried in a forum. Didn't. Just a team blog post and a blocklist shipped straight to the Web Wallet. Not a criticism, just noticing the gap between decentralized-by-design messaging and who's actually pulling levers when something breaks.
Curious if that changes once #Dusk governance actually goes live — or if crisis response always ends up centralized no matter what the docs say.
On August 16, $DUSK's team flagged suspicious activity on a team-managed bridge wallet — disabled the addresses, paused bridge services, shipped a Web Wallet recipient blocklist, looped in Binance once part of the flow touched their platform. @DuskFoundation confirmed DuskDS mainnet itself was never touched, no protocol-level issue. All handled fast, in what reads like hours.
Here's the part that got me though — none of that response ran through any governance process. No vote, no proposal, no token holders weighing in. Just the team, moving quickly, making calls unilaterally. Which… makes sense, honestly, you can't put a live security incident to a vote. But it did make the "on-chain governance is on the roadmap" framing feel more like a future promise than a present reality.
Had this half-written assuming I'd find some proposal thread buried in a forum. Didn't. Just a team blog post and a blocklist shipped straight to the Web Wallet. Not a criticism, just noticing the gap between decentralized-by-design messaging and who's actually pulling levers when something breaks.
Curious if that changes once #Dusk governance actually goes live — or if crisis response always ends up centralized no matter what the docs say.