Content
@
0 reply
0 recast
0 reaction
Flying Nobita
@flyingnobita
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/
2 replies
9 recasts
37 reactions
Hudson Jameson
@hudsonjameson
Tornado Cash already has that capability :D https://docs.tornadoeth.cash/tornado-cash-classic/compliance-tool
1 reply
0 recast
0 reaction
Flying Nobita
@flyingnobita
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
1 reply
0 recast
0 reaction
Hudson Jameson
@hudsonjameson
True for sure. But why would you want 3rd parties to deanonymize their tx? Technically you could allow a third party to reveal the tx with the current setup if you give them the 3rd party access to the note that TC generates.
1 reply
0 recast
0 reaction
Flying Nobita
@flyingnobita
Yes of course. I think whether it is sufficient for TC to allow a user the choice to reveal, or to require TC to reveal transaction details without users intervention is ultimately the choice of the regulators
0 reply
0 recast
0 reaction
