duke
/
duke.hush.is
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

WIP dev update

master
Duke 1 year ago
parent
b07bdafe1f
commit
5783721112
2 changed files with 107 additions and 0 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. BIN
      memos/3/hush-is-privacy.png
  2. 107
      memos/3/index.html

BIN
memos/3/hush-is-privacy.png
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 844 KiB

107
memos/3/index.html
View File

@ -0,0 +1,107 @@
<!DOCTYPE html>
<html>
<head>
<title>Duke Leto Memos - Hush Dev Update #0</title>
<style>
body {
width: 42em;
margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif;
background-color: black;
color: white;
}
a {
color: #63c0f5;
text-shadow: 0 0 5px rgba(104, 182, 255, 0.5);
}
</style>
</head>
<body>
<h1>Hush Dev Update #0</h1>
<p>
</p>
<center>
<a href="./hush-is-privacy.png" target=_blank>
<img width=80% src="">
</a>
</center>
<p>
Some people have requested more insight into what is going on in Hush development so this memo aims to improve that situation.
These dev updates may or may not happen on a regular basis, depending on if they are seen as useful.
</p>
<p>
<a href="...">Hush 3.9.3 "Lateral Larvacean"</a> was recently released. It <a href="https://git.hush.is/hush/hush3/pulls/253">adds support for Tor v3 and i2p</a> networking via <a href="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. <a href="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. "<a href="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 "<a href="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 <a href="https://git.hush.is/hush/hush3/src/branch/master/doc/randomx.md">RandomX</a> mining process, which is used by <a href="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 .
</p>
<p>
So far we have found <a href="https://git.hush.is/hush/hush3/issues/270">one bug</a> in the 3.9.3 release, which only affects solo miners or mining pools using the stratum pool feature of hushd. When BIP155 support was merged, the `stratumallowip` feature was broken if a netmask is used, such as "-stratumallowip=192.168.1.0/24". It has been fixed on the dev branch. If this bug
affects you, workarounds including specifying "-stratumallowip" multiple times to list specific IP addresses, using the dev branch, or contacting Hush devs on <a href="https://hush.is/tg">Telegram</a> to ask for a binary of the dev branch.
</p>
<p>
Hush developers are currently in the process of making releases of SilentDragon (SD) and SilentDragonLite (SDL). One large change will be that support for our old android app SilentDragonAndroid (SDA) is being removed. That is the app that requires "pairing" to a wallet via websockets. We now have a new SDA which does not require pairing, it's is a "lite wallet" that talks to a lite wallet backend server, which is much easier to use. Since the old SDA is deprecated and no longer supported, the SilentDragonWormhole is also no longer supported, since it was only needed to allow devices on different networks to pair with each other.
</p>
<p>
SDL has many new features and bugfixes coming in the new release, a few will be described here.
<ul>
<li>Improved privacy by <a href="https://git.hush.is/hush/SilentDragonLite/commit/a8fc12e0e2b2324db21407f4848f2d4aa59f4575">changing lite servers after sending a tx</a> </li>
<li> Various new lite servers have been added </li>
<li> Many improvements to the New Wallet Wizard </li>
<li> Fixed various bugs in the Welcome Screen </li>
<li> New Polish language translation and updates to various translations</li>
<li> Updated checkpoints which means syncing new wallets will be extremely faster</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 <a href="https://git.hush.is/hush/SilentDragonLite/src/branch/dev/doc/relnotes.md">Release Notes</a> for full details </li>
</ul>
</p>
<p>
SD also has a huge number of new features and bugfixes coming in the next release, a few are described here:
<ul>
<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>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>
</ul>
<center>
<a href="" target=_blank>
<img width=80% src="">
</a>
</center>
<p>
Recently Hush released a lite wallet Android app called <a href="https://hush.is/sda">SilentDragonAndroid</a> to replace our old Android app (of the same name). The old app requires pairing to a desktop wallet of SD or SDL, the new app can be used solely with any compatible Android device.
</p>
<p>
It would be nice to add SDA to F-Droid but there are some <a href="https://git.hush.is/hush/SilentDragonAndroid/issues/4">technical issues</a> that need to be solved before that happens. The Hush team currently recommends users download SDA directly from the <a href="https://hush.is">hush.is</a> website. This requires changing the default setting in Android to allow installing from unknown sources.
<hr width=75%>
<p>
<br>
<b>-- Duke Leto</b>
</p>
<p>
<a href="https://duke.hush.is/?back">Back</a>
</p>
</body>
</html>
Write Preview
Loading…
Cancel
Save