This is a pretty cool and simple way to modify Tornado Cash protocol to be natively compliant.

The design allows the "privacy revoker" with its private key to link the deposit address and the withdrawal address, thus deanonymizing the withdrawal

This is a pretty cool and simple way to modify Tornado Cash protocol to be natively compliant.

The design allows the "privacy revoker" with its private key to link the deposit address and the withdrawal address, thus deanonymizing the withdrawal

https://np.engineering/posts/tornado-anonymity-revoker-design/

this has the same anonymity model as routing funds through coinbase or any  other cex

one party knows all depositors and can disclose withdrawers to anyone, even privately

privacy pools with anonymity sets are a secure implementation but imo still enable censorship

prev: /nook, protocol @ opensea, co-author seaport & stuff.
professional @slokh and @0xalexander fanboy

yeah i guess it's kinda like a decentralized version of the cex approach

this has the same anonymity model as routing funds through coinbase or any  other cex

one party knows all depositors and can disclose withdrawers to anyone, even privately

privacy pools with anonymity sets are a secure implementation but imo still enable censorship

https://github.com/ameensol/privacy-pools

I enjoy my cats, privacy tech, & ice cream.

Now: VP @ Polygon Labs
Previous: USAA, Ethereum Foundation, Flashbots, Zcash Grants

Poly/Bi 🏳️‍🌈

The existing tool from Tornado Cash allows users to reveal their transaction details, which can then be checked by a 3rd party.

The tool from NPLabs allow a 3rd party to reveal the transaction details without the involvement of the transaction users.

I think they're very different

Tornado Cash already has that capability :D

https://docs.tornadoeth.cash/tornado-cash-classic/compliance-tool