Spent some time on a Dusk task for CreatorPad and the thing I kept chewing on afterward wasn't the tech, it was the sequencing. On August 16, bridge addresses got flagged, disabled, and recycled before most users even noticed anything was wrong. A blocklist went up. Binance got looped in only after part of the suspicious flow touched their platform.
So the order was: internal detection, internal containment, then external coordination. Regular users found out last, if at all.
That's not necessarily bad you don't want a bridge incident trending before it's contained. But it did shift how I think about "self-custody" claims around $DUSK . Self-custody is real for your funds, sure, but the response to a threat is still very centralized in practice. Someone with admin-level visibility saw this before anyone on-chain did.
Not a criticism exactly. Just noting the gap between the privacy pitch and how incident response actually works.
#dusk @Dusk
So the order was: internal detection, internal containment, then external coordination. Regular users found out last, if at all.
That's not necessarily bad you don't want a bridge incident trending before it's contained. But it did shift how I think about "self-custody" claims around $DUSK . Self-custody is real for your funds, sure, but the response to a threat is still very centralized in practice. Someone with admin-level visibility saw this before anyone on-chain did.
Not a criticism exactly. Just noting the gap between the privacy pitch and how incident response actually works.
#dusk @Dusk
