hush
/
hush-v3-whitepaper
8
0
Fork 1
Code Issues 1 Pull Requests Projects Releases Wiki Activity
Browse Source

reformating to make Knuth happy

master
Jonathan "Duke" Leto 5 years ago
parent
b1ca3149e5
commit
3a28647224
1 changed files with 15 additions and 15 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 30
      hush-v3.tex

30
hush-v3.tex
View File

@ -705,27 +705,27 @@ was orphaned and replaced by the 45 block subchain:
\end{quote} \end{quote}
Note that the above block hashes must be looked up on a legacy HUSH block Note that the above block hashes must be looked up on a legacy HUSH block
explorer such as https://explorer.hush.zelcore.io and additionally, the orphaned explorer such as explorer.hush.zelcore.io and additionally, the orphaned block
block will not be in the main chain and only will exist as an orphaned block on will not be in the main chain and only will exist as an orphaned block on nodes
nodes which originally saw that invalidated chain. which originally saw that invalidated chain.
Via blockchain analysis and detailed transaction logs from Cryptopia, who gave Via blockchain analysis and detailed transaction logs from Cryptopia, who gave
us details about which addresses the attacker was using, it was determined us details about which addresses the attacker was using, it was determined that
that the following addresses are owned by the Cryptopia Double Spend Attacker, the following addresses are owned by the Cryptopia Double Spend Attacker, with
with old HUSH v2 addresses on the left and new HUSH v3 addresses on the right. old HUSH v2 addresses on the left and new HUSH v3 addresses on the right.
\begin{quote} \begin{quote}
651000 HUSH t1bEBr1LdBQtHun7B5L82R65FgpWyyWFx8L = RSdmvBomouuGP9RUc5J2NoJYCRnVqT3j5V t1bEBr1LdBQtHun7B5L82R65FgpWyyWFx8L = RSdmvBomouuGP9RUc5J2NoJYCRnVqT3j5V
29279.8 HUSH t1KttMaacGw17oFitV448TGfwM2yovm4g6Q = RBJURm3kuS26Gd3C1oE8QyuDreFKpkNT2Z t1KttMaacGw17oFitV448TGfwM2yovm4g6Q = RBJURm3kuS26Gd3C1oE8QyuDreFKpkNT2Z
\end{quote} \end{quote}
These two addresses own a total of ~680,000 HUSH which was not dispersed to the The first address owns 651000 HUSH and the second owns 29279.8 HUSH on the
equivalent addresses on the new HUSH v3 mainnet. These funds currently remain in legacy HUSH v2 chain which was not dispersed to the equivalent addresses on the
the HUSH Founders Reward wallet and will be used to reimburse all who were new HUSH v3 mainnet. These funds currently remain in the HUSH Founders Reward
stolen from at Cryptopia, which will enable HUSH trading to resume. Any remaining wallet and will be used to reimburse all who were stolen from at Cryptopia,
funds will be used for additional exchange listings. which will enable HUSH trading to resume. Any remaining funds will be used for
additional exchange listings.
\nsection{Immutability of HUSH v2 + v3} \nsection{Immutability of HUSH v2 + v3}
@ -737,7 +737,7 @@ pubkeys can make transactions which they shouldn't, to spend funds which were
lost or stolen, etc. This was deemed unacceptable, for obvious moral, security lost or stolen, etc. This was deemed unacceptable, for obvious moral, security
and financial reasons. and financial reasons.
Instead, we have chosen to keep our original intentations, which is that we do Instead, we have chosen to keep our original intentions, which is that we do
not believe that forcibly turning off peoples nodes is right. So people on the not believe that forcibly turning off peoples nodes is right. So people on the
legacy Hush chain are free to continue using it. They should note, that the legacy Hush chain are free to continue using it. They should note, that the
Sprout Inflation bug is still waiting to be exploited there and that DPoW is no Sprout Inflation bug is still waiting to be exploited there and that DPoW is no

Write Preview
Loading…
Cancel
Save