@ -36,15 +36,15 @@ These dev updates may or may not happen on a regular basis, depending on if they
<p>
<ahref="https://git.hush.is/hush/hush3/releases/tag/v3.9.3">Hush 3.9.3 "Lateral Larvacean"</a> was recently released. It <ahref="https://git.hush.is/hush/hush3/pulls/253">adds support for Tor v3 and i2p</a> networking via <ahref="https://bips.dev/155/">BIP155</a> being ported from BTC to HUSH. This is also known as "addrv2". The reason for this change is because originally Tor v2 addresses were shorter and happen to fit inside the P2P messages that full nodes send to each other about which nodes they are connected to.Since the Tor network deprecated Tor v2 due to security bugs and upgraded to Tor v3 these addresses became much longer and no longer fit in these P2P messages, meaning that full nodes could no longer tell each other about Tor v3 nodes they were connected to. <ahref="https://geti2p.net">i2p</a> addresses have always been long and never fit inside those P2P messages, so BIP155 adds support for i2p for the first time. To address these issues BTC Core added BIP155 in 2020 and now that has finally landed in HUSH, so you can once again use Tor with a Hush full node and now, for the first time, you can also use i2p. HUSH now has seed nodes for both Tor v3 and i2p networks, so if your node knows how to connect to them, it will be able to find peers over those networks. Thanks to the various Hush team members that run seed nodes to help the network run.
<ahref="https://git.hush.is/hush/hush3/releases/tag/v3.9.3">Hush 3.9.3 "Lateral Larvacean"</a> was recently released. It <ahref="https://git.hush.is/hush/hush3/pulls/253">adds support for Tor v3 and i2p</a> networking via <ahref="https://bips.dev/155/">BIP155</a> being ported from BTC to HUSH. This is also known as "addrv2". The reason for this change is because originally <ahref="https://www.torproject.org/">Tor</a> v2 addresses were shorter and happen to fit inside the P2P messages that full nodes send to each other about which nodes they are connected to.Since the Tor network deprecated Tor v2 due to security bugs and upgraded to Tor v3 these addresses became much longer and no longer fit in these P2P messages, meaning that full nodes could no longer tell each other about Tor v3 nodes they were connected to. <ahref="https://geti2p.net">i2p</a> addresses have always been long and never fit inside those P2P messages, so BIP155 adds support for i2p for the first time. To address these issues BTC Core added BIP155 in 2020 and now that has finally landed in HUSH, so you can once again use Tor with a Hush full node and now, for the first time, you can also use i2p. HUSH now has seed nodes for both Tor v3 and i2p networks, so if your node knows how to connect to them, it will be able to find peers over those networks. Thanks to the various Hush team members that run seed nodes to help the network run.
</p>
<p>
Additionally in 3.9.3 there are two new RPCs which node operators may find useful. "<ahref="https://faq.hush.is/rpc/getrescaninfo.html">getrescaninfo</a>" tells you info about a current rescan, including what percentage complete it is. This is much more convenient that searching for this data in debug.log. There is also "<ahref="https://faq.hush.is/rpc/abortrescan.html">abortrescan</a>" which will abort a current rescan if one is happening. This is an extremely useful RPC in case you accidentally started a rescan (possible for all-time) which could take hours or days to complete. Previously there was no good way to stop a rescan, except forcefully killing a node and risking disk or wallet corruption. This RPC should be especially useful for nodes with large wallets, where rescans take a very long time.
Additionally in 3.9.3 there are two new <ahref="https://faq.hush.is/rpc/">RPCs</a> which node operators may find useful. "<ahref="https://faq.hush.is/rpc/getrescaninfo.html">getrescaninfo</a>" tells you info about a current rescan, including what percentage complete it is. This is much more convenient that searching for this data in debug.log. There is also "<ahref="https://faq.hush.is/rpc/abortrescan.html">abortrescan</a>" which will abort a current rescan if one is happening. This is an extremely useful RPC in case you accidentally started a rescan (possible for all-time) which could take hours or days to complete. Previously there was no good way to stop a rescan, except forcefully killing a node and risking disk or wallet corruption. This RPC should be especially useful for nodes with large wallets, where rescans take a very long time.
</p>
<p>
For users of Hush Smart Chains, 3.9.3 fixes some bugs in the <ahref="https://git.hush.is/hush/hush3/src/branch/master/doc/randomx.md">RandomX</a> mining process, which is used by <ahref="https://dragonx.is">DragonX</a> for instance. All DragonX miners should update to 3.9.3 and anyone wanting to create an HSC should use 3.9.3 .
For users of Hush Smart Chains, 3.9.3 fixes some bugs in the <ahref="https://git.hush.is/hush/hush3/src/branch/master/doc/randomx.md">RandomX</a> mining process, which is used by <ahref="https://dragonx.is">DragonX</a> for instance. All DragonX miners should update to 3.9.3 and anyone wanting to <ahref="https://hush.is/hsc-creator">create an HSC</a> should use 3.9.3 .
</p>
<p>
@ -76,9 +76,11 @@ SD also has a huge number of new features and bugfixes coming in the next releas
<li>SD is now able to be a GUI wallet for DragonX, which is called SilentDragonX (SDX).</li>
<li>This is the very first GUI wallet for a Hush Smart Chain and we believe DragonX users will really enjoy it.</li>
<li>SDX also includes a Mining tab which allows users to mine via a GUI, no more CLI required to mine!</li>
<li>The Mining tab has been translated to Spanish (ES), Chinese (ZH) and Russian (RU) so far.</li>
<li>You now can choose a language translation while the wallet is running. You no longer need to use the same language as the operating system uses. All currently supported translations are options in a dropdown list. </li>
<li>Previously only port 9050 was supported for proxying via Tor. This would not work with any custom port, or with Tor Browser which uses port 9150. SD now supports a custom proxy port and supports being used with the Tor proxy provided with Tor Browser. This means users can install Tor via a GUI use a Hush GUI wallet with Tor, without ever using the CLI </li>
<li>Pairing to the old SilentDragonAndroid (SDA) app has been removed. The new SDA does not need to pair to a desktop wallet.</li>
<li>Read the <ahref="https://git.hush.is/hush/SilentDragon/src/branch/dev/doc/relnotes/README.md">Release Notes</a> for full details</li>
Duke
1 year ago