franco pfp
franco
@francos.eth
“developing privacy-preserving tools and technology that are safe, accessible, and compliance-friendly.” > privacy > compliance Private but backdoored USDC incoming lol
1 reply
2 recasts
14 reactions

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
The danger is there, but there's also hope. @ironfish seems to follow the Monero paradigm, with private transactions and view keys (that can be used to let, if you want, a third party to view transaction details). That's a good design, imo, because it allows parties that have to follow compliance rules (companies, professionals), to hide their transaction details from everyone, but also allows audits. https://ironfish.network/learn/faq
2 replies
1 recast
2 reactions

franco pfp
franco
@francos.eth
Fair enough, I guess if you’re building on base and don’t need compliance you can use private txs. Shouldn’t we assume any company that needs to comply will comply though? Circle’s USDC for example.
1 reply
0 recast
1 reaction

franco pfp
franco
@francos.eth
Also, is the disclosure of the usage of view keys by other entities enforced? How do we know when privacy is being preserved?
0 reply
0 recast
0 reaction