Why does my public IP show a Bitcoin Node is running when it is set up over Tor?

Why does my public IP show a Bitcoin Node is running when it is set up over Tor?

I've set up my node to run exclusively over TOR. But when I check https://bitnodes.earn.com/ and a few other sites with my public IP to check if a bitcoin node is accepting incoming connections, it comes back that it is.

How do I hide my public IP from showing that a full node is running ?

My bitcoin.conf settings are as follows:

  • txindex=1
  • server=1
  • rpcport=8332
  • listen=1
  • proxy=127.0.0.1:9050
  • bind = 127.0.0.1
  • onlynet=onion
http://bit.ly/2Rrl8Ol

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more