|
|
|
@ -347,11 +347,11 @@ linkability, transaction graphs, shielded transactions, blockchain analysis } |
|
|
|
\newcommand{\zkSNARKs}{\term{zk-SNARKs}} |
|
|
|
\newcommand{\libsnark}{\term{libsnark}} |
|
|
|
\newcommand{\memo}{\term{memo field}} |
|
|
|
\newcommand{\taddr}{\textbf{\term{taddr}}} |
|
|
|
\newcommand{\taddrs}{\textbf{\term{taddrs}}} |
|
|
|
\newcommand{\zaddr}{\textbf{\term{zaddr}}} |
|
|
|
\newcommand{\taddr}{\textbf{\term{taddr} }} |
|
|
|
\newcommand{\taddrs}{\textbf{\term{taddrs} }} |
|
|
|
\newcommand{\zaddr}{\textbf{\term{zaddr} }} |
|
|
|
\newcommand{\zksnarks}{\textbf{\term{ZK-SNARKs}}} |
|
|
|
\newcommand{\zaddrs}{\textbf{\term{zaddrs}}} |
|
|
|
\newcommand{\zaddrs}{\textbf{\term{zaddrs} }} |
|
|
|
\newcommand{\memos}{\term{memo fields}} |
|
|
|
\newcommand{\Memos}{\titleterm{Memo Fields}} |
|
|
|
\newcommand{\keyAgreementScheme}{\term{key agreement scheme}} |
|
|
|
@ -609,8 +609,8 @@ single payout. They will now know one of the zaddrs and the exact amount being p |
|
|
|
pools are a wealth of information to de-anonymize \zaddrs and must be very careful to not leak useful metadata. |
|
|
|
|
|
|
|
We would like to mention \cite{LuckPool} as an example of Best Practices by a mining pool that supports \zaddrs, |
|
|
|
they do not list any \zaddr publicly and do not allow searching by \zaddr and do not show which \zaddrs are being |
|
|
|
paid out. The Hush community also reached out to Pirate mining pools long ago and many of them removed public metadata |
|
|
|
they do not list any \zaddr publicly, do not allow searching by \zaddr and do not show which \zaddrs are being |
|
|
|
paid out. The Hush community also reached out to all Pirate mining pools long ago and they emoved public metadata |
|
|
|
about \zaddr miners when their were told the privacy implications. All mining pools which can pay out to \zaddrs |
|
|
|
should follow these guidelines. All public data about \zaddrs can be fed into ITM and Metaverse attacks. |
|
|
|
|
|
|
|
|
