It is possible to run Qogecoin as a Tor hidden service, and connect to such services.
The following directions assume you have a Tor proxy running on port
Many distributions default to having a
SOCKS proxy listening on port
9050, but others may not. In particular, the Tor Browser Bundle defaults to
listening on port
9150. See the Tor Project FAQ
for how to properly configure Tor.
1. Run qogecoin behind a Tor proxy¶
The first step is running Qogecoin behind a Tor proxy. This will already make all outgoing connections be anonymized, but more is possible.
Set the proxy server. If SOCKS5 is selected (default), this proxy server will be used to try to reach
.onionaddresses as well.
Set the proxy server to use for tor hidden services. You do not need to set this if it’s the same as
-proxy. You can use
-noonionto explicitly disable access to hidden services.
-proxy, listening is disabled by default. If you want to run a hidden service (see next section), you’ll need to enable it explicitly.
When behind a Tor proxy, you can specify
.onionaddresses instead of IP addresses or hostnames in these parameters. It requires SOCKS5. In Tor mode, such addresses can also be exchanged with other P2P nodes.
In a typical situation, this suffices to run behind a Tor proxy:
3. Automatically listen on Tor¶
Starting with Tor version
0.2.7.1 it is possible, through Tor’s control
socket API, to create and destroy ‘ephemeral’ hidden services programmatically.
Qogecoin Core has been updated to make use of this.
This means that if Tor is running (and proper authentication has been
configured), Qogecoin Core automatically creates a hidden service to listen on.
This will positively affect the number of available
This new feature is enabled by default if Qogecoin Core is listening
-listen), and requires a Tor connection to work. It can be explicitly
-listenonion=0 and, if not disabled, configured using the
-torpassword settings. To show verbose debugging
Connecting to Tor’s control socket API requires one of two authentication
methods to be configured. For cookie authentication the user running
qogecoind must have write access to the
CookieAuthFile specified in Tor
configuration. In some cases this is preconfigured and the creation of a hidden
service is automatic.
If permission problems are seen with
-debug=tor they can be resolved by
adding both the user running tor and the user running
qogecoind to the same
group and setting permissions appropriately. On Debian-based systems the user
running qogecoind can be added to the debian-tor group, which has the
appropriate permissions. An alternative authentication method is the use of the
-torpassword flag and a
hash-password which can be enabled and specified
in Tor configuration.
4. Privacy recommendations¶
Do not add anything but
qogecoinports to the hidden service.
If you run a web service too, create a new hidden service for that. Otherwise it is trivial to link them, which may reduce privacy. Hidden services created automatically (as in section 3) always have only one port open.