Spent some time this week going through @Dusk's incident notes after the bridge pause, and one line stuck with me more than the headline did. Alongside disabling the compromised addresses, the team pushed a Web Wallet recipient blocklist to stop transfers to known sanctioned or flagged addresses. Small detail, easy to skim past.
But it's the kind of thing that quietly tells you what $DUSK is actually built for. A privacy chain adding a recipient blocklist isn't a contradiction, it's the whole thesis. Confidential by default, compliant when it has to be. I'd read that pitch a dozen times without really registering what it looks like in practice, mid-incident, under pressure.
What surprised me wasn't the containment speed, it was that the response leaned on the same selective-disclosure logic the protocol is designed around. Not bolted on after the fact.
Still can't tell if that's a strength they'll lean into more, or a one-off reaction to a bad week.
#dusk @Dusk
But it's the kind of thing that quietly tells you what $DUSK is actually built for. A privacy chain adding a recipient blocklist isn't a contradiction, it's the whole thesis. Confidential by default, compliant when it has to be. I'd read that pitch a dozen times without really registering what it looks like in practice, mid-incident, under pressure.
What surprised me wasn't the containment speed, it was that the response leaned on the same selective-disclosure logic the protocol is designed around. Not bolted on after the fact.
Still can't tell if that's a strength they'll lean into more, or a one-off reaction to a bad week.
#dusk @Dusk
