s3v3nh4cks posted a forum message last week with regards to 'testing' anonymity and privacy settings for this crypto, when using Tor.
Being interested in this project purely from the network perspective of a crypto-currency towards
digital-cash, herewith some example configurations;
CLIENT only (example);.conf
listen=0
port=989
proxy=127.0.0.1:9150
maxconnections=8
onion=127.0.0.1:9150
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
Allows .exit traffic (pushes peer connectivity through Tor for anonymity) and addnode=.onion connectivity (within the Tor network).
torrc (example);
ClientOnly 1
SOCKSPolicy accept 127.0.0.1/8
LongLivedPorts 21, 22, 706, 989, 1863, 5050, 5190, 5222, 5223, 6523, 6667, 6697, 8300
ExitPolicy reject *:*
EDIT: SOCKSPort 9150 and ControlPort 9051 are already set in torrc-defaults in TBB, removed from above to avoid confusion / start-up conflicts.
N.B. 'Default' LongLivedPorts + Port 989
See:
https://www.torproject.org/docs/tor-manual.html- Using SOCKSPort 9150 allows connectivity through the Tor Browser Bundle. 'Expert' Tor package is still SOCKSPort 9050.
See:
https://www.torproject.org/docs/faq.html#TBBSocksPortCLIENT only addnode=.onion (example);.conf
listen=0
port=989
maxconnections=4
onion=127.0.0.1:9150
onlynet=onion
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
N.B. addnode=.onion's / maxconnections=8 (you don't need more than 8 connections - more connections are worse for privacy.)
Disable wallet UPnP. Disable incoming connections.
'Dual Stack' Nodes and/or Masternode (example);See: How-to set-up Tor on a Linux VPS:
https://bitcointalk.org/index.php?topic=1374919.0Regular dual stack node .conf (example) ;
listen=1
port=51472
maxconnections=256
onion=127.0.0.1:9050
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
or dual stack masternode .conf (example) ;
listen=1
daemon=1
server=1
port=51472
externalip=xxx.xxx.xxx.xxx
rpcport=51471
rpcallowip=127.0.0.1
rpcuser=long random username
rpcpassword=longer random password
maxconnections=256
onion=127.0.0.1:9050
addnode=y5kcscnhpygvvnjn.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
logtimestamps=1
masternode=1
masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Linux masternode VPS / Tor torrc (example);
ClientOnly 1
SOCKSPort 9050
SOCKSPolicy accept 127.0.0.1/8
Log notice file /var/log/tor/notices.log
ControlPort 9051
HiddenServiceDir /var/lib/tor/dnet/
HiddenServicePort 989 127.0.0.1:51472
HiddenServiceStatistics 0
ORPort 9001
LongLivedPorts 989
ExitPolicy reject *:*
DisableDebuggerAttachment 0
NumEntryGuards 8
N.B. example config. enables your
addnode=.onion incoming address located here:
sudo nano /var/lib/tor/dnet/hostname
- Port 989 (ftps-data) example presented for better network transition over Tor, which is not really designed for P2P usage.
-
https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy...
This request coincided with the release of Bitcoin Core version 0.12.0 ...
Automatically use Tor hidden services
-------------------------------------
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.
Bitcoin Core has been updated to make use of this.
This means that if Tor is running (and proper authorization is available),
Bitcoin Core automatically creates a hidden service to listen on, without
manual configuration. Bitcoin Core will also use Tor automatically to connect
to other .onion nodes if the control socket can be successfully opened. This
will positively affect the number of available .onion nodes and their usage.
This new feature is enabled by default if Bitcoin Core is listening, and
a connection to Tor can be made. It can be configured with the `-listenonion`,
`-torcontrol` and `-torpassword` settings. To show verbose debugging
information, pass `-debug=tor`.Thus, as to how exactly alt. crypto-currencies like DASH - with an existing focus towards privacy and anonymity of transactions were already handling this in terms of user required know-how - was interesting research.
...
It will also be interesting to see how the developers here can manage to
successfully transition from PoW to PoS , with masternodes.
~ True anonymity and privacy of transactions will probably always remain less than 98.9% 'snake-oil' anyway ...- Privacy and Money
-
https://www.youtube.com/watch?v=BTRFuWtxawM - not a 'crazy' person
- 'CASHLESS SOCIETY'
-
https://www.youtube.com/watch?v=gbLJ_ztxxAs -
"from a non-practising agnostic" 
~ SWIM
Poll
