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--|
@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
@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
vrypan |--o--|
@vrypan.eth
Companies would like to use private txs (who wants everyone to know how much they paid their suppliers, who they are doing business with, etc?), but on the other hand without view keys they can't comply with tax authorities, and other regulation or laws. So this is a good approach. The actual danger comes from the extent that this is happening on a chain. If the details of 90% of tx (probably much less) are known to authorities, then they can probably deduct the details of the rest. But if we actually want our employer to be able to pay us onchain, and us pay our rent, insurance, etc onchain, then there does not seem to be any other way.
0 reply
0 recast
2 reactions