pfservermt.dnsalias.org
Bitcoin newbie here. Much to learn.
Any donations or test transactions go straight to EFF.
Thanks in advance.
Topic: Post your static IP (Read 27505 times)
68.68.16.43 or vps.andrew12.net
Running mainnet node and 0.3.20 testnet node (with open RPC (port 18332 testnet:testnet)).
Should be on most of the time.
Running mainnet node and 0.3.20 testnet node (with open RPC (port 18332 testnet:testnet)).
Should be on most of the time.
(-addnode=) 142.58.248.28
High speed, 24/7
Any test coins received will be donated to organizations working for privacy and security (eg. the EFF)
High speed, 24/7
Any test coins received will be donated to organizations working for privacy and security (eg. the EFF)
Found another one:
nlnsivjku4x4lu5n.onion:8333
nlnsivjku4x4lu5n.onion:8333
I found these on IRC:
h4kklwodpcmo6cbq.onion:8333
vv6kcfscuntybrzm.onion:8333
h4kklwodpcmo6cbq.onion:8333
vv6kcfscuntybrzm.onion:8333
Hi,
I'm digging this thread and bringing it back up to introduce the new fallback nodes list on bitcoin.it.
The list is parsed by a mediawiki bot every hour, and nodes are checked (are they up, are they up to date, etc).
https://en.bitcoin.it/wiki/Fallback_Nodes
Explanations are given on how to add your own node in the list. I'll add the ability to poke tor nodes to the bot later. Nodes which are down for more than 24 hours will be removed from the list.
I'm digging this thread and bringing it back up to introduce the new fallback nodes list on bitcoin.it.
The list is parsed by a mediawiki bot every hour, and nodes are checked (are they up, are they up to date, etc).
https://en.bitcoin.it/wiki/Fallback_Nodes
Explanations are given on how to add your own node in the list. I'll add the ability to poke tor nodes to the bot later. Nodes which are down for more than 24 hours will be removed from the list.
i just hooked up another tor-node at
rnam4cxam62nkcyf.onion
rnam4cxam62nkcyf.onion
I took all of the IP addresses in this thread, tested them, and put the working ones on the wiki.
http://www.bitcoin.org/wiki/doku.php?id=fallback_nodes
Please put new entries there from now on.
http://www.bitcoin.org/wiki/doku.php?id=fallback_nodes
Please put new entries there from now on.
I would like to update my last post. It seems bitcoin allows 10.0.0.0/8 to bypass the socks proxy settings, which will cause hidden service connections to hang.
The IP block in these configuration settings should work...
torrc:
mapaddress 192.0.2.1 aaiuestmhzt6pjsl.onion
mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion
mapaddress 192.0.2.5 c5qvugpewwyyy5oz.onion
mapaddress 192.0.2.6 xqzfakpeuvrobvpj.onion
mapaddress 192.0.2.7 vso3r6cmjoomhhgg.onion
bitcoin.conf:
addnode=192.0.2.1
addnode=192.0.2.2
addnode=192.0.2.3
addnode=192.0.2.4
addnode=192.0.2.5
addnode=192.0.2.5
addnode=192.0.2.6
addnode=192.0.2.7
Thanks goes out to theymos from #bitcoin-dev.
The IP block in these configuration settings should work...
torrc:
mapaddress 192.0.2.1 aaiuestmhzt6pjsl.onion
mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion
mapaddress 192.0.2.5 c5qvugpewwyyy5oz.onion
mapaddress 192.0.2.6 xqzfakpeuvrobvpj.onion
mapaddress 192.0.2.7 vso3r6cmjoomhhgg.onion
bitcoin.conf:
addnode=192.0.2.1
addnode=192.0.2.2
addnode=192.0.2.3
addnode=192.0.2.4
addnode=192.0.2.5
addnode=192.0.2.5
addnode=192.0.2.6
addnode=192.0.2.7
Thanks goes out to theymos from #bitcoin-dev.
Here are some that I've collected from various forums that are not on your list.
pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion
pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion
Maybe add to http://www.bitcoin.org/wiki/doku.php?id=74638_nodes or combine that wiki page with teh additions in forming a new wiki page with a more appropriate name?
Here are some that I've collected from various forums that are not on your list.
pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion
pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion
New Tor bitcoind service: j43z65b6r2usg3vk.onion
However, somebody brought up a good point on the IRC channel: since Bitcoin uses Socks4A, do .onion addresses even work, or does the DNS lookup fail and no connection to any Tor-ified .onion addresses even get attempted?
Anybody know?
That's true, but theymos also mentioned that you can mapaddress the .onion addresses to an IP.However, somebody brought up a good point on the IRC channel: since Bitcoin uses Socks4A, do .onion addresses even work, or does the DNS lookup fail and no connection to any Tor-ified .onion addresses even get attempted?
Anybody know?
On that note, I would like to add my own hidden service address to the list: vso3r6cmjoomhhgg.onion
So this is what your torrc should include:
mapaddress 10.10.10.1 aaiuestmhzt6pjsl.onion
mapaddress 10.10.10.2 ijzt2eeizty3p5xe.onion
mapaddress 10.10.10.3 vso3r6cmjoomhhgg.onion
mapaddress 10.10.10.4 j43z65b6r2usg3vk.onion
and in your ~/.bitcoin/bitcoin.conf:
addnode=10.10.10.1
addnode=10.10.10.2
addnode=10.10.10.3
addnode=10.10.10.4
Hopefully they will add socks 4a/5 + dns support soon.
New Tor bitcoind service: j43z65b6r2usg3vk.onion
However, somebody brought up a good point on the IRC channel: since Bitcoin uses Socks4A, do .onion addresses even work, or does the DNS lookup fail and no connection to any Tor-ified .onion addresses even get attempted?
Anybody know?
However, somebody brought up a good point on the IRC channel: since Bitcoin uses Socks4A, do .onion addresses even work, or does the DNS lookup fail and no connection to any Tor-ified .onion addresses even get attempted?
Anybody know?
lzsaver.dlinkddns.com
I hope that next Bitcoin version will accept DNS addresses.
I hope that next Bitcoin version will accept DNS addresses.
You're right. :3 *hides*
It is no longer necessary to post ip addresses at this time. The reason there was an abundance of hype regarding everyone to quickly publish their addresses was due to a severe vulnerability in a previous version of Bitcoin and to alert everyone to quickly reorganize using a new version of Bitcoin client that was patched to fix/prevent the vulnerability.
https://bitcointalksearch.org/topic/strange-block-74638-822
https://bitcointalksearch.org/topic/overflow-bug-serious-823
https://bitcointalksearch.org/topic/version-0310-block-74638-overflow-patch-827
https://bitcointalksearch.org/topic/sfg-828
https://bitcointalksearch.org/topic/blocks-minus-1-837
https://bitcointalksearch.org/topic/strange-block-74638-822
https://bitcointalksearch.org/topic/overflow-bug-serious-823
https://bitcointalksearch.org/topic/version-0310-block-74638-overflow-patch-827
https://bitcointalksearch.org/topic/sfg-828
https://bitcointalksearch.org/topic/blocks-minus-1-837
Well if you look at the start of THIS thread you will see a different reason for THIS thread.
It is no longer necessary to post ip addresses at this time. The reason there was an abundance of hype regarding everyone to quickly publish their addresses was due to a severe vulnerability in a previous version of Bitcoin and to alert everyone to quickly reorganize using a new version of Bitcoin client that was patched to fix/prevent the vulnerability.
https://bitcointalksearch.org/topic/strange-block-74638-822
https://bitcointalksearch.org/topic/overflow-bug-serious-823
https://bitcointalksearch.org/topic/version-0310-block-74638-overflow-patch-827
https://bitcointalksearch.org/topic/sfg-828
https://bitcointalksearch.org/topic/blocks-minus-1-837
https://bitcointalksearch.org/topic/strange-block-74638-822
https://bitcointalksearch.org/topic/overflow-bug-serious-823
https://bitcointalksearch.org/topic/version-0310-block-74638-overflow-patch-827
https://bitcointalksearch.org/topic/sfg-828
https://bitcointalksearch.org/topic/blocks-minus-1-837
Hello im gatsu im new here im trying to understand this program and my IP is 90.229.148.152
I set up bitcoind on bitcoin.torservers.net now. Hopefully up 24/7 
Feel free to test, I'm not so sure, it went too smoothly 
Feel free to test, I'm not so sure, it went too smoothly Jump to: