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 27501 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
Original IP/address posted has since gone down. From now on use 16bit.doesntexist.com - This one is constantly updated to my IP as it changes and is up 24/7.
Dynamic DNS. sawyer12.homeip.net. Not running 24/7 however.
I don't have a static IP, but I have a dedicated domain that points to it.
ewt5.tk
Just sent 0.01ewt5.tk
I don't have a static IP, but I have a dedicated domain that points to it.
ewt5.tk
Just sent 0.01ewt5.tk
I don't have a static IP, but I have a dedicated domain that points to it.
ewt5.tk
ewt5.tk
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
:~$ ./bitcoind getinfo"balance" : 0.000000000000000
Waaah! My client was on, so it should have worked. Hostname sending should work or be added, I shall suggest that up.
Post your IP and I will try again...
200.35.150.50
My client is running pretty much 24/7 and can be reached at either 65.60.177.164(adminitator.com) or 75.118.213.133(wan2.adminitator.com)
Both failed to accept a connection. Maybe a firewall rule?
My clients are running pretty much 24/7 and can be reached at:
wan1.adminitator.com or wan2.adminitator.com
The IP addresses should be pretty static from now on and both address should be running 24/7.
wan1.adminitator.com or wan2.adminitator.com
The IP addresses should be pretty static from now on and both address should be running 24/7.
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
:~$ ./bitcoind getinfo"balance" : 0.000000000000000
Waaah! My client was on, so it should have worked. Hostname sending should work or be added, I shall suggest that up.
Post your IP and I will try again...
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
Also I got one reply on the next block cycle!
Oh I was wondering about that, I actually sent the 0.01 back, hehe. Also I got one reply on the next block cycle!
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
:~$ ./bitcoind getinfo"balance" : 0.000000000000000
Waaah! My client was on, so it should have worked. Hostname sending should work or be added, I shall suggest that up.
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
Also I got one reply on the next block cycle!
Also I got one reply on the next block cycle!
hmm, I am pretty sure I was online, but my firewall is zonealarm free, and can be a pain to get anything open.
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
Also I got one reply on the next block cycle!
Also I got one reply on the next block cycle!
Got yours
Sent it back...
I just sent 0.01 to 14 different IPs, I tried all of them, but some were not responding. Also I just noticed that the send coin dialog only works with IP address, not host names.
Also I got one reply on the next block cycle!
Also I got one reply on the next block cycle!
IP 97.106.27.225
Host bender.nethoncho.com
Address 1BCepBALaCMsc3pKSdvXfb3HeN89AcTLsA
Host bender.nethoncho.com
Address 1BCepBALaCMsc3pKSdvXfb3HeN89AcTLsA
n/m
the ip addresses aren't for trading purposes, only for staying in connection with the network.
Is posting your IP address not a security risk (albeit minor)?
Would a receivebyaddress not be as good? 1TPspb1BprCWnEdM7Rwz7NMzfvBBfvZsJ
Btw, I'm just testing out the system to see if I've got things running properly. Will post my IP address if that's preferable.
Would a receivebyaddress not be as good? 1TPspb1BprCWnEdM7Rwz7NMzfvBBfvZsJ
Btw, I'm just testing out the system to see if I've got things running properly. Will post my IP address if that's preferable.
And if someone can share an init.d script (Ubuntu) it can be more permanent, in case of reboots.
This should set one up:
echo '#!/bin/sh' | sudo tee /etc/init.d/bitcoin
echo "su -c 'bitcoind -daemon' $(whoami)" | sudo tee -a /etc/init.d/bitcoin
sudo chmod a+x /etc/init.d/bitcoin
sudo ln -s ../init.d/bitcoin /etc/rc3.d/S90bitcoin
Assuming bitcoind is in the PATH and should be run as the current user.
I'll share (2) IPs
64.186.154.76
and
64.186.155.104
64.186.154.76
and
64.186.155.104
bitcoin.exceede.com
And if someone can share an init.d script (Ubuntu) it can be more permanent, in case of reboots.
And if someone can share an init.d script (Ubuntu) it can be more permanent, in case of reboots.
Hi! Mine is:
bitcoin.alt.md
Should be up 24/24 with minor outages
bitcoin.alt.md
Should be up 24/24 with minor outages
76.181.196.213
There's mine. not up 24/7, but pretty close.
There's mine. not up 24/7, but pretty close.
75.158.131.108 or lfmcal.dontexist.org
should work for a while at least
should work for a while at least
IP: 99.109.109.230
Domain: gxp.ath.cx
Installed on Windows 7 on my laptop which is on constantly except on Wednesday's.
Domain: gxp.ath.cx
Installed on Windows 7 on my laptop which is on constantly except on Wednesday's.
Enjoy:
bitcoin.allowed.org
178.44.168.159
or
17NBh8Ei8HiWcMtureN1Y2P1ScPT5xmDfi
Thanks.
Thanks for the coin, I checked my server and saw a donation out of nowhere, hehe. or
17NBh8Ei8HiWcMtureN1Y2P1ScPT5xmDfi
Thanks.
77.245.114.35 or bloof.dlinkddns.com
Thanks.
Thanks.
66.221.254.71
I'm running it on my co-located server in Dallas.
I'm running it on my co-located server in Dallas.
bitcoin.modernjob.info
Hi there, new to the project. I find it interesting so here is my support to it
IP:200.69.244.1
Edit: Not reliable.
IP:
Edit: Not reliable.
74.82.216.10
24/7 High Bandwidth Seed-node, courtesy of https://vekja.net
Newcomers to Bitcoin, for faster block downloads to get you started , run bitcoin with the parameter:
"-addnode=74.82.216.10"
24/7 High Bandwidth Seed-node, courtesy of https://vekja.net
Newcomers to Bitcoin, for faster block downloads to get you started , run bitcoin with the parameter:
"-addnode=74.82.216.10"
bitlex.co.cc
supposed to automate exchange bitcoin4L$, so it should be up an running 24/7.
supposed to automate exchange bitcoin4L$, so it should be up an running 24/7.
I am new here, but I just started running the Bitcoind, and I plan to keep it running unless I find anything "wrong" with the project (which I don't think I shall).
You can strap onto ipv4.harry.lu, and it should work. Main harry.lu points to the same address, but it is a dual-stack host, and I don't know if IPv6 will break the client.
You can strap onto ipv4.harry.lu, and it should work. Main harry.lu points to the same address, but it is a dual-stack host, and I don't know if IPv6 will break the client.
My VPS, validity.alloscomp.com (resolves to 208.98.52.221), should also be up nearly 24/7.
(deleted as nodes are down currently)
bitcoin.thruhere.net // 75.81.184.156
Both are the same thing, first is just DynDNS in case my IP changes.
Both are the same thing, first is just DynDNS in case my IP changes.
greg0.info
or
74.210.187.179
or
74.210.187.179
Found these ones online:
(I2P / port 8333)
7dcgf6w3ahd7rjmhyzbu6mvji2pncv2sywlhjhoxkoi6gsjqucxq.b32.i2p
(TOR / port 8333)
ijzt2eeizty3p5xe.onion
They are listed on http://hosts.i2p (on I2P)
(I2P / port 8333)
7dcgf6w3ahd7rjmhyzbu6mvji2pncv2sywlhjhoxkoi6gsjqucxq.b32.i2p
(TOR / port 8333)
ijzt2eeizty3p5xe.onion
They are listed on http://hosts.i2p (on I2P)
Thank you everyone. I will put up a hidden service relay soon enough..for those who wish to be truly anonymous.
EDIT: Tor users try aaiuestmhzt6pjsl.onion as a node! Should be up!
GUIDE:
Essentially put this in your torrc. The hiddenservicedir really can be anywhere though. Bitcoin/Relaydata is just logical, because if you back that folder up(holds your wallet), you will also back up your relay's private keys, which will let you keep the same .onion address.
HiddenServiceDir C:\Documents and Settings\\Application Data\Bitcoin\Relaydata
HiddenServicePort 8333 127.0.0.1:8333
EDIT: Tor users try aaiuestmhzt6pjsl.onion as a node! Should be up!
GUIDE:
Essentially put this in your torrc. The hiddenservicedir really can be anywhere though. Bitcoin/Relaydata is just logical, because if you back that folder up(holds your wallet), you will also back up your relay's private keys, which will let you keep the same .onion address.
HiddenServiceDir C:\Documents and Settings\
HiddenServicePort 8333 127.0.0.1:8333
192.168.1.12 Aside from a minor outage due to weather, it will be up 24/7...
This pretty much looks like your local ip.look here http://whatismyipaddress.com for your public ip.
Thnx 65.33.97.204
98.149.111.20
To all who use TOR--good luck to you!
To all who use TOR--good luck to you!
192.168.1.12 Aside from a minor outage due to weather, it will be up 24/7...
This pretty much looks like your local ip.look here http://whatismyipaddress.com for your public ip.
192.168.1.12 Aside from a minor outage due to weather, it will be up 24/7...
Should be up most of the time, although, I sometimes turn it off...
94.209.188.239Don't got the resources to run it anymore... up!
And donate me something!
94.209.188.239
And donate me something!
I'm at theymos.ath.cx. I should be online 24/7.
You need to look up my IP address before you give it to Bitcoin. My IP address only changes infrequently, so this should be OK.
You need to look up my IP address before you give it to Bitcoin. My IP address only changes infrequently, so this should be OK.
It would be nice to have a list of static IPs for new users to send test donations to so they can see how the software works. If you can accept incoming connections and you have a static IP address, post it here!
Anything sent to these IPs should be considered a donation.
If you do request a round-trip, be sure to include your return bitcoin address or IP in the comment, but please assume it'll be one-way. They won't necessarily be watching for incoming transactions to send back.
Anything sent to these IPs should be considered a donation.
If you do request a round-trip, be sure to include your return bitcoin address or IP in the comment, but please assume it'll be one-way. They won't necessarily be watching for incoming transactions to send back.
Jump to: