Browse Source

typos

master
Duke Leto 4 years ago
parent
commit
9fe8f21250
  1. BIN
      itm-zchain.pdf
  2. BIN
      sietch.pdf
  3. 4
      sietch.tex

BIN
itm-zchain.pdf

Binary file not shown.

BIN
sietch.pdf

Binary file not shown.

4
sietch.tex

@ -790,7 +790,7 @@ approximate input and output values. This data is not available any other way an
exact values are not very important.
If a blockchain analyst can ascertain a transaction involves at least 1M USD in value
versus a few pennies of value, that directly the course of analysis and investigation.
versus a few pennies of value, that directs the course of analysis and investigation.
Perfect de-anonymization is not needed and in practice does not matter. Software
enabled with data from ITM analysis will be able to identify transaction outputs as having certain ranges of values and potentially their associated zaddrs from OSINT data.
@ -1080,7 +1080,7 @@ This means that when this feature is turned on, and a node receives a dust attac
will magically clean up after the attack in the background with best practices for every transaction. These transactions
are guaranteed to leave the size of our \textbf{anonymity set} the same or increase it by 1 (if there is no change output).
The original implementation will spend up to 45 inputs at once and always sent to 1 output with fee=0, which trivially
stands out on the network. On the \Hush network, these consolidation transaction look exactly like a very common
stands out on the network. On the \Hush network, these consolidation transactions look exactly like a very common
$ z \rightarrow z $ with between 1 to 8 inputs and 7 or 8 outputs, blending into a large crowd of transactions which
have the same properties.

Loading…
Cancel
Save