Ran a small transfer through Dusk's Web Wallet earlier this week while wrapping up a CreatorPad task, and got stopped mid-flow by a blocklist warning I wasn't expecting. Nothing dramatic, just a red flag before the transaction would submit. For a chain built around $DUSK 's selective-disclosure privacy model, #dusk , @Dusk , that felt like an odd thing to run into.

Turns out the warning traces back to the recipient blocklist the team shipped to the Web Wallet after the mid-August incident involving a compromised bridge operations wallet. It screens outgoing transfers against known flagged addresses before you can send.

I'd assumed privacy-first meant fewer checkpoints, not more. Watching it actually fire on a real attempt changed that a little. The mechanism only works if someone is maintaining and updating that list in near real time, which means there's a curatorial layer sitting quietly underneath the "confidential by default" pitch.

Not saying that's wrong, just noticing it. Selective disclosure and address screening aren't the same thing, but they're now living in the same wallet. Still working out how comfortable I am with that, and who exactly decides what gets added to the list going forward.

Which part of this stood out most to you? 👀