Bitcoin Wiki - User contributions [en]

Fallback Nodes

2011-07-28T17:11:28Z

WakiMiko: /* IPv4 Nodes */ fixing nodelist

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| bitcoin.es || neutrino || 188.165.138.165 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-24 16:00:04 || ?
|-
| 98.143.152.19 || osmosis || 98.143.152.19 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-24 16:00:04 || ?
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-24 16:00:06 || ?
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-07-24 16:00:06 || ?
|-
| 46.4.13.200 || WakiMiko || 46.4.13.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-07-24 15:00:03 || ?
|-
| fallback1.kr105.com || kR105 || 190.101.85.148 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-07-24 02:00:55 || No
|-
| faucet.bitcoin.st || Bitcoin Street || 64.27.57.225 || {{Table Value Unknown}} || {{Fallback Nodes/Node Down}} || 2011-07-24 06:00:07 || ?
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-07-24 04:00:06 || No
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.25}} || 2011-07-27 16:08:31 || No
|-
| 50.23.217.19 || Senseless || 50.23.217.19 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-27 16:08:31 || No

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

Fallback Nodes

2011-07-27T23:57:38Z

WakiMiko: -dns parameter info

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| bitcoin.es || neutrino || 188.165.138.165 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-24 16:00:04 || ?
|-
| 98.143.152.19 || osmosis || 98.143.152.19 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-24 16:00:04 || ?
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-24 16:00:06 || ?
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-07-24 16:00:06 || ?
|-
| 46.4.13.200 || WakiMiko || 46.4.13.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-07-24 15:00:03 || ?
|-
| fallback1.kr105.com || kR105 || 190.101.85.148 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-07-24 02:00:55 || No
|-
| faucet.bitcoin.st || Bitcoin Street || 64.27.57.225 || {{Table Value Unknown}} || {{Fallback Nodes/Node Down}} || 2011-07-24 06:00:07 || ?
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-07-24 04:00:06 || No
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.25}} || 2011-07-27 16:08:31 || No
|-
| 50.23.217.19 || Senseless || 50.23.217.19 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-27 16:08:31 || No
|-

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

Fallback Nodes

2011-07-21T15:12:08Z

WakiMiko: re-added all nodes that got purged when wikibot started working again. dunno how many of those are still valid, but wikibot should sort it out in the next 24h

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

The [[Original Bitcoin client]] do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(host ndrix.com |sed s/"^.*has address "//)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 46.4.13.200 || WakiMiko || 46.4.13.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-21 15:00:02 || ?
|-
| 98.143.152.19 || osmosis || 98.143.152.19 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-21 15:00:03 || ?
|-
| fallback2.bitcoin.me.uk || Vladimir [Pool] || 178.255.199.86 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-07-21 15:00:03 || No
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-07-21 09:00:08 || No
|-
| 109.72.80.77 || devriesi
|-
| ndrix.com || mndrix
|-
| 69.164.218.197 || Gavin Andresen
|-
| jun.dashjr.org || Lightfoot Hosting
|-
| mining.bitcoin.cz || slush
|-
| fallback1.kr105.com || kR105 [CL]
|-
| bitcoin.csy.ca || Martok
|-
| nat.router.dashjr.org || Luke-Jr
|-
| bitcoin.sipa.be || sipa
|-
| bluematt.me || BlueMatt
|-
| btc1.justmoon.net || justmoon
|-
| bitcoins.ca || humble
|-
| BiddingPond.com || BiddingPond
|-
| 178.63.15.200 || hendi
|-
| 109.75.176.193 || MagicalTux [DE]
|-
| 173.224.125.222 || MagicalTux [US]
|-
| 178.63.62.15 || MagicalTux [DE]
|-
| bitlex.org || BitLex
|-
| 74.82.216.10 || thufir
|-
| 64.31.38.250 || TDT
|-
| 74.57.236.239 || ?
|-
| 67.176.86.181 || BobSGI
|-
| BTCSportsBet.com || Cusipzzz
|-
| 86.5.50.90 || ?
|-
| eudemocracia.org.ar || Eudemocracia
|-
| faucet.bitcoin.st || Bitcoin Street
|-
| meerkatmischief.com || nallar
|-
| 204.9.55.71 || toasty
|-
| 46.182.18.245 || DontMindMe
|-
| 77.245.75.130 || embreym
|-
| 87.127.127.226 || NiccyB
|-
| tech.dyndns-blog.com || Carsonb
|-
| 184.107.48.198 || meehow
|-
| 178.32.120.164 || meehow
|-
| 89.200.139.134 || Joe59101
|-
| 74.91.19.46 || btcfan

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

User:WakiMiko

2011-04-03T14:26:57Z

WakiMiko: Created page with "im poor plz donate 17myaBoAvPoBXDx9opS81cb7jTQY658K1K"

im poor plz donate

17myaBoAvPoBXDx9opS81cb7jTQY658K1K

Original Bitcoin client/API calls list

2011-04-03T14:25:24Z

WakiMiko: remove non-existing arguments, update to version 0.3.20.2

Bitcoin API call list (as of version 0.3.20.2)

== Common operations ==

=== Listing my bitcoin addresses ===

Listing the bitcoin addresses in your wallet is easily done via ''listreceivedbyaddress''. It normally lists only addresses which already have received transactions, however you can list all the addresses by setting the first argument to 0, and the second one to true

== Full list ==

Required arguments are denoted inside < and > Optional arguments are inside [ and ].

{|class="wikitable"
! Command !! Parameters !! Description
|-
| backupwallet || <destination> || Safely copies wallet.dat to destination, which can be a directory or a path with filename.
|-
| getaccount || <bitcoinaddress> || Returns the account associated with the given address.
|-
| getaccountaddress || <account> || Returns the current bitcoin address for receiving payments to this account.
|-
| getaddressesbyaccount || <account> || Returns the list of addresses for the given account.
|-
| getbalance || [account] [minconf=1] || If [account] is not specified, returns the server's total available balance.<br/>If [account] is specified, returns the balance in the account.
|-
| getblockbycount || height || Dumps the block existing at specified height. '''Note: this is not available in the official release'''
|-
| getblockcount || || Returns the number of blocks in the longest block chain.
|-
| getblocknumber || || Returns the block number of the latest block in the longest block chain.
|-
| getconnectioncount || || Returns the number of connections to other nodes.
|-
| getdifficulty || || Returns the proof-of-work difficulty as a multiple of the minimum difficulty.
|-
| getgenerate || || Returns true or false whether bitcoind is currently generating hashes
|-
| gethashespersec || || Returns a recent hashes per second performance measurement while generating.
|-
| getinfo || || Returns an object containing various state info.
|-
| getnewaddress || [account] || Returns a new bitcoin address for receiving payments. If [account] is specified (recommended), it is added to the address book so payments received with the address will be credited to [account].
|-
| getreceivedbyaccount || <account> [minconf=1] || Returns the total amount received by addresses with <account> in transactions with at least [minconf] confirmations.
|-
| getreceivedbyaddress || <bitcoinaddress> [minconf=1] || Returns the total amount received by <bitcoinaddress> in transactions with at least [minconf] confirmations.
|-
| gettransaction || <txid> || Get detailed information about <txid>
|-
| [[getwork]] || [data] || If [data] is not specified, returns formatted hash data to work on:
* "midstate" : precomputed hash state after hashing the first half of the data
* "data" : block data
* "hash1" : formatted hash buffer for second hash
* "target" : little endian hash target
If [data] is specified, tries to solve the block and returns true if it was successful.
|-
| help || [command] || List commands, or get help for a command.
|-
| listaccounts || [minconf=1] || Returns Object that has account names as keys, account balances as values.
|-
| listreceivedbyaccount || [minconf=1] [includeempty=false] || Returns an array of objects containing:
* "account" : the account of the receiving addresses
* "amount" : total amount received by addresses with this account
* "confirmations" : number of confirmations of the most recent transaction included
|-
| listreceivedbyaddress || [minconf=1] [includeempty=false] || Returns an array of objects containing:
* "address" : receiving address
* "account" : the account of the receiving address
* "amount" : total amount received by the address
* "confirmations" : number of confirmations of the most recent transaction included
To get a list of accounts on the system, execute bitcoind listreceivedbyaddress 0 true
|-
| listtransactions || <account> [count=10] || Returns up to [count] most recent transactions for account <account>.
|-
| move || <fromaccount> <toaccount> <amount> [minconf=1] [comment] || Move from one account in your wallet to another.
|-
| sendfrom || <fromaccount> <tobitcoinaddress> <amount> [minconf=1] [comment] [comment-to] || <amount> is a real and is rounded to the nearest 0.01
|-
| sendtoaddress || <bitcoinaddress> <amount> [comment] [comment-to] || <amount> is a real and is rounded to the nearest 0.01
|-
| setaccount || <bitcoinaddress> <account> || Sets the account associated with the given address.
|-
| setgenerate || <generate> [genproclimit] || <generate> is true or false to turn generation on or off.<br/>Generation is limited to [genproclimit] processors, -1 is unlimited.
|-
| stop || || Stop bitcoin server.
|-
| validateaddress || <bitcoinaddress> || Return information about <bitcoinaddress>.
|}

==See Also==

* [[Original Bitcoin client]]
* [[API reference (JSON-RPC)]]
* [[Lazy_API]]

[[Category:Technical]]
[[Category:Developer]]