MapAddress

ToxAndTorInChinaAndIran.md

@@ -43,15 +43,23 @@ VirtualAddrNetworkIPv4 172.16.0.0/12
 AutomapHostsOnResolve 1
 ```
 Then with the list of onion addresses for BS nodes that are running Tox as OnionV3,
-then you can use ```tor-resolve``` or ```tor-resolve -4``` to get the
+you can simply add aliases for the OnionV3 BS nodes directly into the torrc.
+Then the client running Tox over Tor can add aliases for each BS node directly
+into your ```/etc/torrc``` with the ```MapAddress``` command
+```
+MapAddress onion1.tox.xyz h5g52d26mmi67pzzln2uya5msfzjdewengefaj75diipeskoo252lnqd.onion
+```
+The domainname you map to does not have to be real, and should not exist.
+Or you can use ```tor-resolve``` or ```tor-resolve -4``` to get the
 good-for-you-only IP addresses of OnionV3 BS nodes in IPv4. So the Tox user
-does this and puts these addresses into his ```DHTnodes.json``` and boostraps his
+does this, and then puts these addresses into his ```DHTnodes.json``` and boostraps his
 Tox client over Tor Onions. This works with libtoxcore is it is today, as long as
 your client doesn't suffer from the dreaded deranged-hard-coded-bs syndrome.
 
 These steps would be automated by a simple bash or Python script, perhaps a
-Python script wrapped into an exe for Windows/Android. These addresses are
-good for life of the Tor instance, and the script would need rerunning
+Python script wrapped into an exe for Windows/Android. If you use MapAddress these
+mapped addresses are stable, and if you use ```tor-resolve```, these addresses are
+good for life of the Tor instance and the script would need rerunning
 when Tor is restarted. You can also get the IPv4 address of each Onion BS node,
 (for-life-of-the-tor-instance which is usually long enough) in
 Python using the Tor stem library.