Re: ★[ANN] [NAV] NAV COIN - ANONYMOUS TECH. ● ANDROID WALLET LIVE ● NAV 2.1 SOON
Herewith, NAV Tor addnode=.onion support ;
addnode=navfxoktwa7zu3m2.onion:8443
addnode=navfx2yawr6eb4fp.onion:8443
addnode=navfxfkchwclvpbj.onion:8443
addnode=navfxujp7ninsup6.onion:8443
addnode=navcavlevqgjzozx.onion:8443
addnode=navcaqr6y4yfvei4.onion:8443
addnode=navcavq6roeray7h.onion:8443
addnode=navcajegwg62zecy.onion:8443
addnode=navfxkdrgk2oo3ja.onion:8443
addnode=navfxu6w2iptaj3m.onion:8443
addnode=navfxjtmt42smvcj.onion:8443
addnode=navfxosoed7hd4db.onion:8443
An example Tor navcoin.conf (which can be used with the Tor Browser Bundle - https://www.torproject.org/download/download-easy.html
- out-of-the-box) ;
It is advisable to add regular IP addnodes at the base of this .conf for 'failover', which will enable your client to also exit connections via Tor. hidden_service connections (.onion) never leave the Tor network.
Remember that less connections are preferable over more connections, in terms of anonymity and privacy. 6 to 8 connections are probably optimal for broadcasting transactions.
Port 8443 has been selected as it is a common Tor Exit port - see: https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy - whereas the 'default' Navcoin port 44440 is not.
NAV Support for server up keep etc. to : NWeyG7jpQm1wWeYeV7tnNuYLUHmW4FMAr8
Cheers!
addnode=navfxoktwa7zu3m2.onion:8443
addnode=navfx2yawr6eb4fp.onion:8443
addnode=navfxfkchwclvpbj.onion:8443
addnode=navfxujp7ninsup6.onion:8443
addnode=navcavlevqgjzozx.onion:8443
addnode=navcaqr6y4yfvei4.onion:8443
addnode=navcavq6roeray7h.onion:8443
addnode=navcajegwg62zecy.onion:8443
addnode=navfxkdrgk2oo3ja.onion:8443
addnode=navfxu6w2iptaj3m.onion:8443
addnode=navfxjtmt42smvcj.onion:8443
addnode=navfxosoed7hd4db.onion:8443
An example Tor navcoin.conf (which can be used with the Tor Browser Bundle - https://www.torproject.org/download/download-easy.html
- out-of-the-box) ;
Code:
listen=0
port=8443
proxy=127.0.0.1:9150
onion=127.0.0.1:9150
onlynet=tor
maxconnections=8
addnode=navfxoktwa7zu3m2.onion:8443
addnode=navfx2yawr6eb4fp.onion:8443
addnode=navfxfkchwclvpbj.onion:8443
addnode=navfxujp7ninsup6.onion:8443
addnode=navcavlevqgjzozx.onion:8443
addnode=navcaqr6y4yfvei4.onion:8443
addnode=navcavq6roeray7h.onion:8443
addnode=navcajegwg62zecy.onion:8443
addnode=navfxkdrgk2oo3ja.onion:8443
addnode=navfxu6w2iptaj3m.onion:8443
addnode=navfxjtmt42smvcj.onion:8443
addnode=navfxosoed7hd4db.onion:8443
port=8443
proxy=127.0.0.1:9150
onion=127.0.0.1:9150
onlynet=tor
maxconnections=8
addnode=navfxoktwa7zu3m2.onion:8443
addnode=navfx2yawr6eb4fp.onion:8443
addnode=navfxfkchwclvpbj.onion:8443
addnode=navfxujp7ninsup6.onion:8443
addnode=navcavlevqgjzozx.onion:8443
addnode=navcaqr6y4yfvei4.onion:8443
addnode=navcavq6roeray7h.onion:8443
addnode=navcajegwg62zecy.onion:8443
addnode=navfxkdrgk2oo3ja.onion:8443
addnode=navfxu6w2iptaj3m.onion:8443
addnode=navfxjtmt42smvcj.onion:8443
addnode=navfxosoed7hd4db.onion:8443
It is advisable to add regular IP addnodes at the base of this .conf for 'failover', which will enable your client to also exit connections via Tor. hidden_service connections (.onion) never leave the Tor network.
Remember that less connections are preferable over more connections, in terms of anonymity and privacy. 6 to 8 connections are probably optimal for broadcasting transactions.
Port 8443 has been selected as it is a common Tor Exit port - see: https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy - whereas the 'default' Navcoin port 44440 is not.
NAV Support for server up keep etc. to : NWeyG7jpQm1wWeYeV7tnNuYLUHmW4FMAr8
Cheers!
A quick note that the above NAV Tor addnode=.onion nodes are running the latest release of Navcoin and are working fine currently.
Anyone experiencing issues with syncing the blockchain would probably be advised to reach the current block height on 'clearnet' before connecting with Tor.
...
As someone new to Navcoin, if you follow this upgrade guide from shahim :
- https://bitcointalk.org/index.php?topic=679791.msg15828726#msg15828726
then syncing with the current block height will be done within a matter of hours.
For the linux daemon I just did ;
Code:
wget http://www.navcoin.org/files/Nav-Blockchain.zip
Code:
unzip Nav-Blockchain.zip -d ~/.navcoin2
Code:
cd navcoin2/src && ./navcoind
After following the comprehensive compiling instructions from : https://github.com/navcoindev/navcoin2/blob/master/doc/build-unix.txt
and editing the navcoin.conf of course.
Code:
cd ~/.navcoin2 && sudo nano navcoin.conf
Again, all nodes fully synced up within a matter of hours.
I'd imagine that the network will be much more stable when more clients have the correct block height.
