#dusk $DUSK @Dusk I shielded a test transfer through Hedger Alpha on Sepolia last night, expecting the usual crypto-privacy promise: hide the transaction, hide me. Got half of that.

The amount shielded cleanly, balance and transfer value both encrypted end-to-end, exactly as advertised. What didn't disappear was the address doing the sending. DuskEVM runs on Ethereum's account model, not the UTXO model Dusk's native chain uses, and that account model doesn't let identity vanish the way a UTXO can. So the number is hidden. The account attached to it isn't.

Like mailing a sealed envelope with the return address still printed on the outside. Nobody can read what's inside without authorization. Everyone can still see exactly who sent it.

That's not a bug, it's the actual design choice regulated finance needs. Full anonymity is exactly what compliance teams can't work with, they need to know who's transacting even when they can't see how much. Hedger's confidentiality-without-anonymity split is what makes it auditable by a regulator on request instead of opaque to everyone including the people legally required to check.

So "private" here means something narrower and more useful than crypto-Twitter usually means by it. Not invisible. Reviewable, selectively, by someone with the authority to ask.

Curious how many people testing Hedger walk in expecting full anonymity and find out the address trail was never the part being hidden.

@Dusk $DUSK #dusk