Bitcoin Wiki - User contributions [en]

Running Bitcoin

2016-01-25T22:18:23Z

Imsaguy: Updated commandline options and major reformat

There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__

==Linux Quickstart==

The simplest way to start from scratch with the command line client, automatically syncing blockchain and creating a wallet, is to just run this command (without arguments) from the directory containing your bitcoind binary:

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

These commands are accurate as of Bitcoin Core version v0.12.0rc1.

{| style="valign:top;"
! scope="col" style="width: 20pt;border: 0px" |
! scope="col" style="width: 150pt;" | Command
! scope="col" | Description
|-
| || -? || This help message
|-
| || -alerts || Receive and display P2P network alerts (default: 1)
|-
| || -alertnotify=<cmd> || Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
|-
| || -blocknotify=<cmd> || Execute command when the best block changes (%s in cmd is replaced by block hash)
|-
| || -checkblocks=<n> || How many blocks to check at startup (default: 288, 0 = all)
|-
| || -checklevel=<n> || How thorough the block verification of -checkblocks is (0-4, default: 3)
|-
| || -conf=<file> || Specify configuration file (default: bitcoin.conf)
|-
| || -datadir=<dir> || Specify data directory
|-
| || -dbcache=<n> || Set database cache size in megabytes (4 to 16384, default: 100)
|-
| || -loadblock=<file> || Imports blocks from external blk000??.dat file on startup
|-
| || -maxorphantx=<n> || Keep at most <n> unconnectable transactions in memory (default: 100)
|-
| || -maxmempool=<n> || Keep the transaction memory pool below <n> megabytes (default: 300)
|-
| || -mempoolexpiry=<n> || Do not keep transactions in the mempool longer than <n> hours (default: 72)
|-
| || -par=<n> || Set the number of script verification threads (-2 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
|-
| || -prune=<n> || Reduce storage requirements by pruning (deleting) old blocks. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, >550 = target size in MiB to use for block files)
|-
| || -reindex || Rebuild block chain index from current blk000??.dat files on startup
|-
| || -txindex || Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)
|-
|-
| colspan="3" | <br /> '''Connection options:'''
|-
| || -addnode=<ip> || Add a node to connect to and attempt to keep the connection open
|-
| || -banscore=<n> || Threshold for disconnecting misbehaving peers (default: 100)
|-
| || -bantime=<n> || Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
|-
| || -bind=<addr> || Bind to given address and always listen on it. Use [host]:port notation for IPv6
|-
| || -connect=<ip> || Connect only to the specified node(s)
|-
| || -discover || Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)
|-
| || -dns || Allow DNS lookups for -addnode, -seednode and -connect (default: 1)
|-
| || -dnsseed || Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect)
|-
| || -externalip=<ip> || Specify your own public address
|-
| || -forcednsseed || Always query for peer addresses via DNS lookup (default: 0)
|-
| || -listen || Accept connections from outside (default: 1 if no -proxy or -connect)
|-
| || -listenonion || Automatically create Tor hidden service (default: 1)
|-
| || -maxconnections=<n> || Maintain at most <n> connections to peers (default: 125)
|-
| || -maxreceivebuffer=<n> || Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
|-
| || -maxsendbuffer=<n> || Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
|-
| || -onion=<ip:port> || Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
|-
| || -onlynet=<net> || Only connect to nodes in network <net> (ipv4, ipv6 or onion)
|-
| || -permitbaremultisig || Relay non-P2SH multisig (default: 1)
|-
| || -peerbloomfilters || Support filtering of blocks and transaction with bloom filters (default: 1)
|-
| || -port=<port> || Listen for connections on <port> (default: 8333 or testnet: 18333)
|-
| || -proxy=<ip:port> || Connect through SOCKS5 proxy
|-
| || -proxyrandomize || Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1)
|-
| || -seednode=<ip> || Connect to a node to retrieve peer addresses, and disconnect
|-
| || -timeout=<n> || Specify connection timeout in milliseconds (minimum: 1, default: 5000)
|-
| || -torcontrol=<ip>:<port> || Tor control port to use if onion listening enabled (default: 127.0.0.1:9051)
|-
| || -torpassword=<pass> || Tor control port password (default: empty)
|-
| || -upnp || Use UPnP to map the listening port (default: 0)
|-
| || -whitebind=<addr> || Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
|-
| || -whitelist=<netmask> || Whitelist peers connecting from the given netmask or IP address. Can be specified multiple times. Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway
|-
| || -whitelistalwaysrelay || Always relay transactions received from whitelisted peers (default: 1)
|-
| || -maxuploadtarget=<n> || Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)
|-
| colspan="3" | <br /> '''Wallet options:'''
|-
| || -disablewallet || Do not load the wallet and disable wallet RPC calls
|-
| || -keypool=<n> || Set key pool size to <n> (default: 100)
|-
| || -fallbackfee=<amt> || A fee rate (in BTC/kB) that will be used when fee estimation has insufficient data (default: 0.0002)
|-
| || -mintxfee=<amt> || Fees (in BTC/kB) smaller than this are considered zero fee for transaction creation (default: 0.00001)
|-
| || -paytxfee=<amt> || Fee (in BTC/kB) to add to transactions you send (default: 0.00)
|-
| || -rescan || Rescan the block chain for missing wallet transactions on startup
|-
| || -salvagewallet || Attempt to recover private keys from a corrupt wallet.dat on startup
|-
| || -sendfreetransactions || Send transactions as zero-fee transactions if possible (default: 0)
|-
| || -spendzeroconfchange || Spend unconfirmed change when sending transactions (default: 1)
|-
| || -txconfirmtarget=<n> || If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 2)
|-
| || -maxtxfee=<amt> || Maximum total fees (in BTC) to use in a single wallet transaction; setting this too low may abort large transactions (default: 0.10)
|-
| || -upgradewallet || Upgrade wallet to latest format on startup
|-
| || -wallet=<file> || Specify wallet file (within data directory) (default: wallet.dat)
|-
| || -walletbroadcast || Make the wallet broadcast transactions (default: 1)
|-
| || -walletnotify=<cmd> || Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
|-
| || -zapwallettxes=<mode> || Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup (1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)
|-
| colspan="3" | <br /> '''Debugging/Testing options:'''
|-
| || -debug=<category> || Output debugging information (default: 0, supplying <category> is optional). If <category> is not supplied or if <category> = 1, output all debugging information.<category> can be: addrman, alert, bench, coindb, db, lock, rand, rpc, selectcoins, mempool, mempoolrej, net, proxy, prune, http, libevent, tor, zmq, qt.
|-
| || -gen || Generate coins (default: 0)
|-
| || -genproclimit=<n> || Set the number of threads for coin generation if enabled (-1 = all cores, default: 1)
|-
| || -help-debug || Show all debugging options (usage: --help -help-debug)
|-
| || -logips || Include IP addresses in debug output (default: 0)
|-
| || -logtimestamps || Prepend debug output with timestamp (default: 1)
|-
| || -minrelaytxfee=<amt> || Fees (in BTC/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.00001)
|-
| || -printtoconsole || Send trace/debug info to console instead of debug.log file
|-
| || -shrinkdebugfile || Shrink debug.log file on client startup (default: 1 when no -debug)
|-
| colspan="3" | <br /> '''Chain selection options:'''
|-
| || -testnet || Use the test chain
|-
| colspan="3" | <br /> '''Node relay options:'''
|-
| || -bytespersigop || Minimum bytes per sigop in transactions we relay and mine (default: 20)
|-
| || -datacarrier || Relay and mine data carrier transactions (default: 1)
|-
| || -datacarriersize || Maximum size of data in data carrier transactions we relay and mine (default: 83)
|-
| colspan="3" | <br /> '''Block creation options:'''
|-
| || -blockminsize=<n> || Set minimum block size in bytes (default: 0)
|-
| || -blockmaxsize=<n> || Set maximum block size in bytes (default: 750000)
|-
| || -blockprioritysize=<n> || Set maximum size of high-priority/low-fee transactions in bytes (default: 0)
|-
| colspan="3" | <br /> '''RPC server options:'''
|-
| || -server || Accept command line and JSON-RPC commands
|-
| || -rest || Accept public REST requests (default: 0)
|-
| || -rpcbind=<addr> || Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces)
|-
| || -rpcuser=<user> || Username for JSON-RPC connections
|-
| || -rpcpassword=<pw> || Password for JSON-RPC connections
|-
| || -rpcauth=<userpw> || Username and hashed password for JSON-RPC connections. The field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. A canonical python script is included in share/rpcuser. This option can be specified multiple times
|-
| || -rpcport=<port> || Listen for JSON-RPC connections on <port> (default: 8332 or testnet: 18332)
|-
| || -rpcallowip=<ip> || Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times
|-
| || -rpcthreads=<n> || Set the number of threads to service RPC calls (default: 4)
|-
| colspan="3" | <br /> '''UI Options:'''
|-
| || -choosedatadir || Choose data directory on startup (default: 0)
|-
| || -lang=<lang> || Set language, for example "de_DE" (default: system locale)
|-
| || -min || Start minimized
|-
| || -rootcertificates=<file> || Set SSL root certificates for payment request (default: -system-)
|-
| || -splash || Show splash screen on startup (default: 1)
|-
| || -resetguisettings || Reset all settings changes made over the GUI
|}

Many of the boolean options can also be set to off by specifying them with a "no" prefix: e.g. -nodnseed.

==Bitcoin.conf Configuration File==
All command-line options (except for -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

Note: if running Bitcoin in testnet mode, the sub-folder "testnet" will be appended to the data directory automatically.

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=0

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin-QT to accept JSON-RPC commands.
#server=0

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=random_authvalue_DO_NOT_USE_THIS_STRING_OR_YOU_WILL_GET_ROBBED._USE_THE_ONE_BITCOIND_RECOMMENDS_WHEN_RUN_WITHOUT_ONE_SET_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts. As of Bitcoin Core 0.10.0, wildcards are no longer allowed. Use one of the sample forms below.
# NOTE: opening up the RPC port to hosts outside your local
# trusted network is NOT RECOMMENDED, because the rpcpassword
# is transmitted over the network unencrypted.
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.0/255.255.255.0
#rpcallowip=172.16.0.0/24

# Listen for RPC connections on this TCP port:
#rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
#gen=0

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

You might use the configuration-file, or the GUI-Settings:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on system startup

[[{{ns:file}}:Client_Settings_Options_windows.png]]

====Batch automation====
To work with batch, you have to start the daemon (bitcoind.exe). The bitcoin.exe run with option "-server" will respond with GUI-messages you are not able to process its answers.

===Mac===
[[{{ns:file}}:MacBitcoinStartOnLogin.png]]

===Linux===
[[{{ns:file}}:Client_Settings_Options.png]]

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

{{Bitcoin Core documentation}}

Running Bitcoin

2016-01-21T22:10:58Z

Imsaguy: XP is long gone and all versions going forward follow same appdata structure

There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__

==Linux Quickstart==

The simplest way to start from scratch with the command line client, automatically syncing blockchain and creating a wallet, is to just run this command (without arguments) from the directory containing your bitcoind binary:

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

Give bitcoind the -? or –-help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Bitcoin Core Daemon version v0.10.2

Usage:
bitcoind [options] Start Bitcoin Core Daemon

Options:
-? This help message
-alertnotify=<cmd> Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
-blocknotify=<cmd> Execute command when the best block changes (%s in cmd is replaced by block hash)
-checkblocks=<n> How many blocks to check at startup (default: 288, 0 = all)
-checklevel=<n> How thorough the block verification of -checkblocks is (0-4, default: 3)
-conf=<file> Specify configuration file (default: bitcoin.conf)
-daemon Run in the background as a daemon and accept commands
-datadir=<dir> Specify data directory
-dbcache=<n> Set database cache size in megabytes (4 to 1024, default: 100)
-loadblock=<file> Imports blocks from external blk000??.dat file on startup
-maxorphantx=<n> Keep at most <n> unconnectable transactions in memory (default: 100)
-par=<n> Set the number of script verification threads (-32 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
-pid=<file> Specify pid file (default: bitcoind.pid)
-reindex Rebuild block chain index from current blk000??.dat files on startup
-sysperms Create new files with system default permissions, instead of umask 077 (only effective with disabled wallet functionality)
-txindex Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)
-prune=<n> Reduce storage requirements by pruning (deleting) old blocks(default: 0 =
disable pruning blocks, >550 = target size in MiB to use for block
files)

Connection options:
-addnode=<ip> Add a node to connect to and attempt to keep the connection open
-banscore=<n> Threshold for disconnecting misbehaving peers (default: 100)
-bantime=<n> Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
-bind=<addr> Bind to given address and always listen on it. Use [host]:port notation for IPv6
-connect=<ip> Connect only to the specified node(s)
-discover Discover own IP address (default: 1 when listening and no -externalip)
-dns Allow DNS lookups for -addnode, -seednode and -connect (default: 1)
-dnsseed Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect)
-externalip=<ip> Specify your own public address
-forcednsseed Always query for peer addresses via DNS lookup (default: 0)
-listen Accept connections from outside (default: 1 if no -proxy or -connect)
-maxconnections=<n> Maintain at most <n> connections to peers (default: 125)
-maxreceivebuffer=<n> Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
-maxsendbuffer=<n> Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
-onion=<ip:port> Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
-onlynet=<net> Only connect to nodes in network <net> (ipv4, ipv6 or onion)
-permitbaremultisig Relay non-P2SH multisig (default: 1)
-port=<port> Listen for connections on <port> (default: 8333 or testnet: 18333)
-proxy=<ip:port> Connect through SOCKS5 proxy
-seednode=<ip> Connect to a node to retrieve peer addresses, and disconnect
-timeout=<n> Specify connection timeout in milliseconds (minimum: 1, default: 5000)
-whitebind=<addr> Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
-whitelist=<netmask> Whitelist peers connecting from the given netmask or IP address. Can be specified multiple times.
Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway

Wallet options:
-disablewallet Do not load the wallet and disable wallet RPC calls
-keypool=<n> Set key pool size to <n> (default: 100)
-paytxfee=<amt> Fee (in BTC/kB) to add to transactions you send (default: 0.00)
-rescan Rescan the block chain for missing wallet transactions on startup
-salvagewallet Attempt to recover private keys from a corrupt wallet.dat on startup
-sendfreetransactions Send transactions as zero-fee transactions if possible (default: 0)
-spendzeroconfchange Spend unconfirmed change when sending transactions (default: 1)
-txconfirmtarget=<n> If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 2)
-maxtxfee=<amt> Maximum total fees to use in a single wallet transaction, setting too low may abort large transactions (default: 0.10)
-upgradewallet Upgrade wallet to latest format on startup
-walletbroadcast=<n> Automatic transaction broadcast and rebroadcast (default=1)
-wallet=<file> Specify wallet file (within data directory) (default: wallet.dat)
-walletnotify=<cmd> Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
-zapwallettxes=<mode> Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup
(1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)

Debugging/Testing options:
-debug=<category> Output debugging information (default: 0, supplying <category> is optional)
If <category> is not supplied, output all debugging information.
<category> can be: addrman, alert, bench, coindb, db, lock, rand, rpc, selectcoins, mempool, net.
-gen Generate coins (default: 0)
-genproclimit=<n> Set the number of threads for coin generation if enabled (-1 = all cores, default: 1)
-help-debug Show all debugging options (usage: --help -help-debug)
-logips Include IP addresses in debug output (default: 0)
-logtimestamps Prepend debug output with timestamp (default: 1)
-printtoconsole Send trace/debug info to console instead of debug.log file
-shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)
-testnet Use the test network

Node relay options:
-minrelaytxfee=<amt> Fees smaller than this (in satoshi) are considered zero fee (relaying and mining) (default: 0.00001)
-limitfreerelay=<n> Rate-limit free transactions to <n>*1000 bytes per minute (default: 15)
-datacarrier Relay and mine data carrier transactions (default: 1)
-datacarriersize Maximum size of data in data carrier transactions we relay and mine (default: 40)

Block creation options:
-blockminsize=<n> Set minimum block size in bytes (default: 0)
-blockmaxsize=<n> Set maximum block size in bytes (default: 750000)
-blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 50000)

RPC server options:
-server Accept command line and JSON-RPC commands
-rest Accept public REST requests (default: 0)
-rpcbind=<addr> Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces)
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332 or testnet: 18332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times
-rpcthreads=<n> Set the number of threads to service RPC calls (default: 4)
-rpckeepalive RPC support for HTTP persistent connections (default: 1)

RPC SSL options: (has been removed as of upcoming v0.12)
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-rpcsslcertificatechainfile=<file.cert> Server certificate file (default: server.cert)
-rpcsslprivatekeyfile=<file.pem> Server private key (default: server.pem)
-rpcsslciphers=<ciphers> Acceptable ciphers (default: TLSv1.2+HIGH:TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!3DES:@STRENGTH)

Many of the boolean options can also be set to off by specifying them with a "no" prefix: e.g. -nodnseed.

==Bitcoin.conf Configuration File==
All command-line options (except for -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

Note: if running Bitcoin in testnet mode, the sub-folder "testnet" will be appended to the data directory automatically.

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=0

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin-QT to accept JSON-RPC commands.
#server=0

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=random_authvalue_DO_NOT_USE_THIS_STRING_OR_YOU_WILL_GET_ROBBED._USE_THE_ONE_BITCOIND_RECOMMENDS_WHEN_RUN_WITHOUT_ONE_SET_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts. As of Bitcoin Core 0.10.0, wildcards are no longer allowed. Use one of the sample forms below.
# NOTE: opening up the RPC port to hosts outside your local
# trusted network is NOT RECOMMENDED, because the rpcpassword
# is transmitted over the network unencrypted.
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.0/255.255.255.0
#rpcallowip=172.16.0.0/24

# Listen for RPC connections on this TCP port:
#rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
#gen=0

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

You might use the configuration-file, or the GUI-Settings:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on system startup

[[{{ns:file}}:Client_Settings_Options_windows.png]]

====Batch automation====
To work with batch, you have to start the daemon (bitcoind.exe). The bitcoin.exe run with option "-server" will respond with GUI-messages you are not able to process its answers.

===Mac===
[[{{ns:file}}:MacBitcoinStartOnLogin.png]]

===Linux===
[[{{ns:file}}:Client_Settings_Options.png]]

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

{{Bitcoin Core documentation}}

Running Bitcoin

2015-01-08T09:18:28Z

Imsaguy: Updated to reflect the new rpcallow formats.

There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__

==Linux Quickstart==

The simplest way to start from scratch with the command line client, automatically syncing blockchain and creating a wallet, is to just run this command (without arguments) from the directory containing your bitcoind binary:

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

Give Bitcoin (or bitcoind) the -? or –-help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Usage:
bitcoin-qt [command-line options]

Options:
-? This help message
-conf=<file> Specify configuration file (default: bitcoin.conf)
-datadir=<dir> Specify data directory
-testnet Use the test network
-pid=<file> Specify pid file (default: bitcoind.pid)
-gen Generate coins (default: 0)
-dbcache=<n> Set database cache size in megabytes (4 to 4096, default: 100)
-timeout=<n> Specify connection timeout in milliseconds (default: 5000)
-proxy=<ip:port> Connect through SOCKS proxy
-socks=<n> Select SOCKS version for -proxy (4 or 5, default: 5)
-onion=<ip:port> Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
-dns Allow DNS lookups for -addnode, -seednode and -connect
-port=<port> Listen for connections on <port> (default: 8333 or testnet: 18333)
-maxconnections=<n> Maintain at most <n> connections to peers (default: 125)
-addnode=<ip> Add a node to connect to and attempt to keep the connection open
-connect=<ip> Connect only to the specified node(s)
-seednode=<ip> Connect to a node to retrieve peer addresses, and disconnect
-externalip=<ip> Specify your own public address
-onlynet=<net> Only connect to nodes in network <net> (IPv4, IPv6 or Tor)
-discover Discover own IP address (default: 1 when listening and no -externalip)
-checkpoints Only accept block chain matching built-in checkpoints (default: 1)
-listen Accept connections from outside (default: 1 if no -proxy or -connect)
-bind=<addr> Bind to given address and always listen on it. Use [host]:port notation for IPv6
-dnsseed Find peers using DNS lookup (default: 1 unless -connect)
-banscore=<n> Threshold for disconnecting misbehaving peers (default: 100)
-bantime=<n> Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
-maxreceivebuffer=<n> Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
-maxsendbuffer=<n> Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
-upnp Use UPnP to map the listening port (default: 1 when listening)
-debug=<category> Output debugging information (default: 0, supplying <category> is optional)
If <category> is not supplied, output all debugging information.
<category> can be: addrman, alert, coindb, db, lock, rand, rpc, selectcoins, mempool, net, qt.
-logtimestamps Prepend debug output with timestamp (default: 1)
-shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)
-printtoconsole Send trace/debug info to console instead of debug.log file
-regtest Enter regression test mode, which uses a special chain in which blocks can be solved instantly.
This is intended for regression testing tools and app development.
-server Accept command line and JSON-RPC commands
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332 or testnet: 18332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcthreads=<n> Set the number of threads to service RPC calls (default: 4)
-blocknotify=<cmd> Execute command when the best block changes (all %s in cmd are replaced by block hash)
-alertnotify=<cmd> Execute command when a relevant alert is received or we see a really long fork (all %s in cmd are replaced by message)
-keypool=<n> Set key pool size to <n> (default: 100)
-checkblocks=<n> How many blocks to check at startup (default: 288, 0 = all)
-checklevel=<n> How thorough the block verification is (0-4, default: 3)
-txindex Maintain a full transaction index (default: 0)
-loadblock=<file> Imports blocks from external blk000??.dat file
-reindex Rebuild block chain index from current blk000??.dat files
-par=<n> Set the number of script verification threads (up to 16, 0 = auto, <0 = leave that many cores free, default: 0)

Wallet options:
-disablewallet Do not load the wallet and disable wallet RPC calls
-paytxfee=<amt> Fee per kB to add to transactions you send
-rescan Rescan the block chain for missing wallet transactions
-zapwallettxes Clear list of wallet transactions (diagnostic tool; implies -rescan)
-salvagewallet Attempt to recover private keys from a corrupt wallet.dat
-upgradewallet Upgrade wallet to latest format
-wallet=<file> Specify wallet file (within data directory)
-walletnotify=<cmd> Execute command when a wallet transaction changes (all %s in cmd are replaced by TxID)
-spendzeroconfchange Spend unconfirmed change when sending transactions (default: 1)

Block creation options:
-blockminsize=<n> Set minimum block size in bytes (default: 0)
-blockmaxsize=<n> Set maximum block size in bytes (default: 750000)
-blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 50000)

SSL options: (see the Bitcoin Wiki for SSL setup instructions)
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-rpcsslcertificatechainfile=<file.cert> Server certificate file (default: server.cert)
-rpcsslprivatekeyfile=<file.pem> Server private key (default: server.pem)
-rpcsslciphers=<ciphers> Acceptable ciphers (default: TLSv1.2+HIGH:TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!3DES:@STRENGTH)

UI options:
-lang=<lang> Set language, for example "de_DE" (default: system locale)
-min Start minimized
-splash Show splash screen on startup (default: 1)
-choosedatadir Choose data directory on startup (default: 0)

Many of the boolean options can also be set to off by specifying them with a "no" prefix: e.g. -nodnseed.

==Bitcoin.conf Configuration File==
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| (XP) C:\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf
(Vista, 7) C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

Note: if running Bitcoin in testnet mode, the sub-folder "testnet" will be appended to the data directory automatically.

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=0

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin-QT to accept JSON-RPC commands.
#server=0

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=random_authvalue_DO_NOT_USE_THIS_STRING_OR_YOU_WILL_GET_ROBBED._USE_THE_ONE_BITCOIND_RECOMMENDS_WHEN_RUN_WITHOUT_ONE_SET_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts. As of Bitcoin Core 0.10.0, wildcards are no longer allowed. Use one of the sample forms below.
# NOTE: opening up the RPC port to hosts outside your local
# trusted network is NOT RECOMMENDED, because the rpcpassword
# is transmitted over the network unencrypted.
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.0/255.255.255.0
#rpcallowip=172.16.0.0/24

# Listen for RPC connections on this TCP port:
#rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
#rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
#gen=0

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

You might use the configuration-file, or the GUI-Settings:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on system startup

[[{{ns:file}}:Client_Settings_Options_windows.png]]

====Batch automation====
To work with batch, you have to start the daemon (bitcoind.exe). The bitcoin.exe run with option "-server" will respond with GUI-messages you are not able to process its answers.

===Mac===
[[{{ns:file}}:MacBitcoinStartOnLogin.png]]

===Linux===
[[{{ns:file}}:Client_Settings_Options.png]]

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

CGMiner

2014-05-10T19:33:56Z

Imsaguy: Remove GPU reference

'''CGMiner''' is an open source ASIC/FPGA miner written in C, cross platform for Linux, Windows and OS X, and including support and binaries for RPi, OpenWrt routers and others.

==Features==

Features are listed here:
https://bitcointalk.org/index.php?topic=28402.0

==See Also==

* [[Pooled mining]]

==External Links==

* [https://github.com/ckolivas/cgminer cgminer] project page on GitHub
* [http://bitcointalk.org/index.php?topic=28402.0 Project Thread]
* [http://ck.kolivas.org/apps/cgminer/ Binaries and Source - All Versions]
* [https://github.com/ckolivas/cgminer/blob/master/windows-build.txt Windows Native Compile Guide]
* [http://fabulouspanda.co.uk/commandline/cgminer/ cgminer compiled for Mac OS X]

==References==
<references />

[[Category:Miners]]
[[Category:Free Software]]
[[Category:License/GPL-3]]
[[Category:Open Source]]

Talk:Bitcoin IRC Channel Guidelines

2014-05-09T03:53:52Z

Imsaguy: Created page with "I'd like to see this as more of a bulleted table. For example "Don't do this", "Do this", etc. Perhaps a second column has the longer explanation, but the first column would..."

I'd like to see this as more of a bulleted table. For example "Don't do this", "Do this", etc. Perhaps a second column has the longer explanation, but the first column would essentially be TL;DR [[User:Imsaguy|Imsaguy]] ([[User talk:Imsaguy|talk]]) 03:53, 9 May 2014 (UTC)

CryptoPayment

2014-04-25T17:44:11Z

Imsaguy:

'''CryptoPayment''' is a MediaWiki extension to limit spam by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this Wiki will be used offset moderate expenses (hosting, DDoS protection, security maintenance). If any money is remaining it will go toward funding Bitcoin development.

==Usage==

In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins. The current fee amount is 0.001 BTC, which is presently less than 1 USD.

Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.

===Confirmations===

Payments will be considered paid after it is confirmed in a Bitcoin block.

==Privacy==

Please note that with this payment may allow people to connect your bitcoin wallet to your wiki account via blockchain analysis. If this is a concern to you, take the appropriate steps to protect your [[Anonymity]].

== Code ==
Source will be released after the backend interface to bitcoind is rewritten.

== Disclaimer ==
This payment is merely an anti-spam measure as a one-time measure to enable an account for edit access. The volunteer administrators of this site may revoke edit access for any or no reason, usually in response to abuse or spamming. You are not entitled to any refund under any circumstance.

==Questions or comments?==

If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.

Main Page

2014-04-19T05:45:23Z

Imsaguy: Protected "Main Page": Main page, no one should be moving this. ([Move=Allow only administrators] (indefinite))

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:CryptoPayment]]</div>
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''
|}

| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org Bitcoin.org]</span>
| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[[Forums]]</span>
| style="width:13%; font-size:120%; padding-right: 40px;" |
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.

Languages needing translation work: {{Main Page interwikis}}</noinclude>__NOTOC____NOEDITSECTION__

Comparison of mining pools

2014-04-18T16:51:47Z

Imsaguy: Add information regarding Eligius broken NMC payments

Reward types & explanation:
* '''CPPSRB''' - Capped Pay Per Share with Recent Backpay. [http://eligius.st/wiki/index.php/Capped_PPS_with_Recent_Backpay]
* '''DGM''' - Double Geometric Method. A hybrid between PPLNS and Geometric reward types that enables to operator to absorb some of the variance risk. Operator receives portion of payout on short rounds and returns it on longer rounds to normalize payments. [https://bitcointalk.org/index.php?topic=39497.0]
* '''ESMPPS''' - Equalized Shared Maximum Pay Per Share. Like SMPPS, but equalizes payments fairly among all those who are owed. [http://forum.bitcoin.org/index.php?topic=12181.msg378851#msg378851]
* '''POT''' - Pay On Target. A high variance PPS variant that pays on the difficulty of work returned to pool rather than the difficulty of work served by pool [https://bitcointalk.org/index.php?topic=131376.0]
* '''PPLNS''' - Pay Per Last N Shares. Similar to proportional, but instead of looking at the number of shares in the round, instead looks at the last N shares, regardless of round boundaries.
* '''PPLNSG''' - Pay Per Last N Groups (or shifts). Similar to PPLNS, but shares are grouped into "shifts" which are paid as a whole.
* '''PPS''' - Pay Per Share. Each submitted share is worth certain amount of BC. Since finding a block requires <current difficulty> shares ''on average'', a PPS method with 0% fee would be 25 BTC divided by <current difficulty>. It is risky for pool operators, hence the fee is highest.
* '''Prop.''' - Proportional. When block is found, the reward is distributed among all workers proportionally to how much shares each of them has found.
* '''RSMPPS''' - Recent Shared Maximum Pay Per Share. Like SMPPS, but system aims to prioritize the most recent miners first. [http://eligius.st/wiki/index.php/Shared_Maximum_PPS]
* '''Score''' - Score based system: a proportional reward, but weighed by time submitted. Each submitted share is worth more in the function of time ''t'' since start of current round. For each share score is updated by: score += exp(t/C). This makes later shares worth much more than earlier shares, thus the miner's score quickly diminishes when they stop mining on the pool. Rewards are calculated proportionally to scores (and not to shares). (at slush's pool C=300 seconds, and every hour scores are normalized)
* '''SMPPS''' - Shared Maximum Pay Per Share. Like Pay Per Share, but never pays more than the pool earns. [http://eligius.st/wiki/index.php/Shared_Maximum_PPS]
[http://eligius.st/~luke-jr/samples/800MH-3/ Visual examples of the various payout methods]

{| class="wikitable sortable" border="1"
|-
! Name !! Location !! TH/s<ref name="hashrate2"/>
! Merged Mining<ref name="merged"/>
! Reward Type !! Transaction fees!!PPS Fee!!Other Fee!! [[getwork|GWK]] !! [[Stratum|STM]] !! [[getblocktemplate|GBT]]
! Launched !! Variance !! Forum !! Website
|-
| [[50BTC]] || Germany/USA/Russia || || No || PPS or PPLNS || {{PoolFees}} || 6%<ref name="50btchack"/><ref name="50btchack2"/>|| 1.5%<ref name="50btchack"/><ref name="50btchack2"/> || {{Yes}} || {{Yes}} ||
| 2011-11-11 || User<ref name="changeable"/> || [http://bitcointalk.org/?topic=54673 link] || [http://50btc.com/ link]
|-
| [[PolishPool]] || Poland || 0.27 || NMC,DVC ||PPLNS,PPS<ref name="jackpot"/>|| {{SharedFees}} || 0% || 0% || {{Yes}} || {{Yes}} || {{Yes}}
| 2014-03-02 || Dynamic
| [https://bitcointalk.org/index.php?topic=496980.0 link] || [http://polishpool.pl link]
|-
| [[ABCPool.co]] || USA || || No || PPS<ref name="stales"/> || {{PoolFees}} || 5% || || {{Yes}} || {{No}} || {{No}}
| 2011-08-02 || Diff 1 || [http://bitcointalk.org/?topic=33586 link] || [http://www.ABCPool.co/ link]
|-
| [[alvarez.sfek.kz]] || Kazakhstan || 0.06 || No || PPLNS || {{PoolFees}} || || 0% || {{Yes}} || ||
| 2012-04-19 || Diff 1 || [http://bitcointalk.org/?topic=80135 link] || [http://alvarez.sfek.kz/ link]
|-
| [[Bitalo]] || USA/Europe || 1.1 || No || PPLNS || {{SharedFees}} || 0% || || {{Yes}} || {{Yes}} ||
| 2014-04-08 || Dynamic || || [https://bitalo.com/mining/ link]
|-
| [[BitClockers]] || USA/Europe || || [[NMC]] || PPS || {{PoolFees}} || 8% || || {{Yes}} || ||
| 2011-05-27 || Diff 1 || [http://bitcointalk.org/?topic=10127 link] || [http://bitclockers.com/ link]
|-
| [[BitcoinMining.Co]] || USA || || [[No]] || {{PoolFees}} || {{PoolFees}} || 2% || || {{Yes}} || ||
| 2013-08-13 || Diff 1 || [http://bitcointalk.org/?topic=273259.0 link] || [http://bitcoinmining.co/ link]
|-
| [[BitcoinPool.com]] || USA || || No || Prop. || {{PoolFees}} || || 0% || {{Yes}} || ||
| 2011-03-08 || Diff 1 || [http://bitcoinpool.com/forum/ link] || [http://www.bitcoinpool.com/ link]
|-
| [[Bitcoin Pooled Mining|Slush's pool (mining.bitcoin.cz)]]
| France || 677 || No || Score || {{SharedFees}} || || 2% || || {{Yes}} ||
| 2010-11-27 || User<ref name="changeable"/> || [http://bitcointalk.org/?topic=1976 link] || [http://mining.bitcoin.cz/ link]
|-
| [[BitMinter]] || USA/Germany || 370 || [[NMC]] || PPLNSG || {{SharedFees}} || || 1% || {{Yes}} || {{Yes}} || {{Yes}}
| 2011-06-26 || User<ref name="changeable"/>/Dynamic || [http://bitcointalk.org/?topic=27062 link] || [https://bitminter.com link]
|-
| [[BTCPoolman]] || UK/Europe || 0.5 || No || Prop. || {{SharedFees}} || || 2% || {{Yes}} || {{Yes}} || {{No}}
| 2013-03-01 || Diff 1 || [https://twitter.com/BTCPoolMan Twitter] || [https://www.btcpoolman.com/register Register]
|-
| [[BTC Guild]] || USA/Europe || 6600 || [[NMC]]
| PPLNSG || {{SharedFees}} || || 2% || {{Yes}} || {{Yes}} || {{No}}
| 2011-05-09 || User<ref name="changeable"/>/Dynamic
| [http://bitcointalk.org/?topic=49417 link] || [https://www.btcguild.com/ link]
|-
| [[BTC Oxygen]] || Europe || || No || PPS || {{PoolFees}} || 2% || || {{Yes}} || {{Yes}} ||
| 2012-11-01 || Diff 1 || [http://bitcointalk.org/?topic=127815 link] || [http://www.btcoxygen.com/ link]
|-
| [[BTCMine]] || USA || 0.1 || No || Score || {{PoolFees}} || || 0% || {{Yes}} || ||
| 2011-03-11 || Diff 1 || [http://bitcointalk.org/?topic=4251 link] || [http://btcmine.com/ link]
|-
| [[BTCDig]] || USA || 7 || No || DGM || {{PoolFees}} || || 0% || || {{Yes}} ||
| 2013-07-04 || User<ref name="changeable"/>/Dynamic 20SPM || [https://bitcointalk.org/index.php?topic=249627 link] || [http://btcdig.com/ link]
|-
| [[BTCmow]] || Europe || || No || PPLNS || {{PoolFees}} || || 2.5% || || {{Yes}} ||
| 2013-05-31 || Diff 1 || [https://bitcointalk.org/index.php?topic=221306.0 link] || [http://www.btcmow.com/ link]
|-
| [[btcmp.com]] || Germany || 1.4 || No || PPS || {{PoolFees}} || 4% || || {{Yes}} || ||
| 2011-06-28 || Diff 1 || || [http://www.btcmp.com/ link]
|-
| [[BTCWarp]] || USA || || No || Score || {{PoolFees}} || || 0% || {{Yes}} || ||
| 2011-07-29 || Diff 1 || [http://www.bitcoinbalkan.com/forum link] || [http://www.btcwarp.com/ link]
|-
| [[Coin Miners]] || USA || || No || PPLNS || {{PoolFees}} || || 0% || || {{Yes}} ||
| 2014-02-27 || Diff 1 || [https://bitcointalk.org/index.php?topic=481194.0 link] || [https://www.coinminers.co link]
|-
| [[CoinLab Protected Pool]] || USA || || No || PPS || {{PoolFees}} || 2-5% || || {{Yes}} || ||
| 2012-08-09 || Diff 1 || [http://bitcointalk.org/?topic=99643 link] ||
|-
| [[Coinotron]] || Poland || || No || DGM || {{PoolFees}} || || 0% || {{Yes}} || ||
| 2011-07-06 || Diff 1 || [http://bitcointalk.org/?topic=26727 link] || [http://www.coinotron.com link]
|-
| [[DeepBit]] || Germany || 0.1 || No || PPS/Prop. || {{PoolFees}} || 10% || 3% || {{Yes}} || ||
| 2011-02-26 || Diff 1 || [http://bitcointalk.org/?topic=3889 link] || [http://deepbit.net/ link]
|-
| [[Eclipse Mining Consortium]]
| USA/Europe/Australia/Asia || 246 || No || DGM/PPS || {{PoolFees}} || 5% || 0% || {{Yes}} || {{Yes}} || {{Yes}}
| 2011-06-14 || User<ref name="changeable"/>/Dynamic
| [http://bitcointalk.org/?topic=16385 link] || [https://eclipsemc.com link]
|-
| [[Eligius]] || USA || 4000 || [[NMC]] 105% PPS<ref name="eligiusnmc"/> || CPPSRB || {{SharedFees}} || 0% || || {{Yes}} || {{Yes}} || {{Yes}}
| 2011-04-27 || Dynamic: 32 shares/m || [http://bitcointalk.org/?topic=23768 link] || [http://eligius.st link]
|-
| [[GHash.IO]] || Netherlands || 7000 || [[NMC]], IXC, [[Devcoin]] || PPLNS || {{SharedFees}} || 0% || 0% || {{No}} || {{Yes}} || {{No}}
| 2013-07-01 || User<ref name="changeable"/> || [https://cexio.zendesk.com/forums link] || [https://ghash.io/ link]
|-
| [[Give Me COINS]] || USA, Europe || 25 || [[NMC]] || PPLNS || {{SharedFees}} || || 0%|| {{No}} || {{Yes}} || {{Yes}}
| 2013-08-12 || Dynamic || [https://bitcointalk.org/index.php?topic=272017.0 link] || [http://give-me-coins.com link]
|-
| [[MaxBTC]] || USA || || [[NMC]] || DGM || {{PoolFees}} || || 0% || {{Yes}} || ||
| 2012-03-15 || Diff 1 || [http://bitcointalk.org/?topic=68734 link] || [https://www.maxbtc.com/ link]
|-
| [[Merge Mining Pool]] || USA || 50 || [[NMC]], IXC, [[Devcoin]]
| DGM || {{SharedFees}} || || 1.5% || {{No}} || {{Yes}} || {{No}}
| 2012-01-08 || User<ref name="changeable"/> || [http://bitcointalk.org/?topic=57148 link] || [http://mmpool.org link]
|-
| [[Multipool]] || USA, Europe || 40 || [[NMC]], IXC, [[Devcoin]] || Prop. || {{SharedFees}} || || 0% || {{Yes}} || {{Yes}} || {{No}}
| 2012-03-15 || User || [https://bitcointalk.org/index.php?topic=311067.0 link] || [https://www.multipool.us/ link]
|-
| [[MuPool]] || USA/Europe || 0.3 || NO ||PPLNS|| {{SharedFees}} || || 0% || {{Yes}} || {{Yes}} || {{Yes}} || 2014-02-23 || Dynamic || [https://bitcointalk.org/index.php?topic=483856.0 link] || [https://mupool.com link]
|-
| [[Ozcoin]] || USA/Europe/Australia || 4 || No || DGM/PoT || shared on DGM || || 1%/2% || {{No}} || {{Yes}} || {{No}}
| 2011-06-07 || User<ref name="changeable"/>/Dynamic
| [http://bitcointalk.org/?topic=14085 link] || [https://www.ozcoin.net link]
|-
| [[P2Pool]] || Earth (P2P) || 170 || Solo<ref name="solomm"/> || PPLNS || {{SharedFees}} || || 0% || {{No}}<ref name="local"/> || {{No}}<ref name="local"/> || {{No}}
| 2011-06-17 || User<ref name="changeable"/> || [http://bitcointalk.org/?topic=18313 link] ||
|-
| [[pool.itzod.ru]] || Russia || 38 || No || RSMPPS || {{SharedFees}} || 0% || || {{Yes}} || {{Yes}} || {{Yes}}
| 2011-08-01 || User<ref name="changeable"/> || [http://bitcointalk.org/?topic=25127 RU] [https://bitcointalk.org/index.php?topic=44024.0 EN] || [https://pool.itzod.ru/ link]
|-
| [[Triplemining]] || Europe || 7.5 || No ||PPLNS<ref name="jackpot"/>|| {{PoolFees}} || || 0% || {{Yes}} || {{Yes}} || {{Yes}}
| 2011-06-28 || Diff 1 for getwork/GBT, dynamic for stratum
| [http://bitcointalk.org/?topic=23664 link] || [https://www.triplemining.com link]
|-
|}
<references>
<ref name="50btchack">On or around October 18, 2013, the pool stopped payouts of mining earnings. 50BTC.com claims the pool was hacked and all mining earnings and records of the earnings were lost. They claim as a result, many people are blackmailing them with unrealistic claims. https://bitcointalk.org/index.php?topic=359277.0</ref>
<ref name="50btchack2">On or around February 11, 2014, the pool failed to payout mining earnings. 50BTC.com claims their system was unable to deal with the transaction malleability problem. They claim this has been fully corrected. https://50btc.com/en/news/view/161</ref>
<ref name="hashrate2">Note that pool hashrate is largely irrelevant but can be seen as a popularity measurement. Note however that it is a theoretical security issue if one pool gains above 50% of the total computational power of the network, thus consider joining a pool based on other metrics.</ref>

<ref name="merged">Merged mining allows miners to mine on multiple [[block chains]] at the same time with the same hashing.</ref>

<ref name="stales">Pool also rewards stale shares</ref>
<ref name="local">Miner-operated proxy available.</ref>
<ref name="changeable">The difficulty of the shares can be changed by the user.</ref>
<ref name="solomm">Merged mining can be done on a "solo mining" basis (payouts in the merged chain are not pooled).</ref>

<ref name="jackpot">Triplemining keeps 1% to redistribute using a weekly jackpot and affiliations</ref>
<ref name="eligiusnmc">As of March 8, 2014, payouts have been labelled as broken by the pool operator. There is no current ETA to a fix.</ref>
</references>

== See also ==
*[[Pooled mining]]
*[http://blockorigin.pfoe.be/chart.php Hashrate distribution pie chart]

[[Category:Mining]]

Satoshi Dice

2014-04-07T05:05:10Z

Imsaguy: /* History */

SatoshiDice is a "blockchain-based betting game."

Some consider it to be DDoS attack against the Bitcoin network since it is bypassing the built-in anti-DDoS features of Bitcoin (transaction fees). Others see it as proof that the incentives created by the bitcoin transaction fee scheme do not produce the results originally expected.

Unlike traditional online gaming software, wagers with SatoshiDice can be sent without access to the website nor running any client software. To play, a Bitcoin transaction is made to one of the static addresses operated by the service, each having differing payouts. The service determines if the wager wins or loses and sends a transaction in response with the payout to a winning bet or it returns a tiny fraction of the house's gain to a losing bet.
As a result, the game spams the p2p network and blockchain with useless data.
SatoshiDice forces players to pay a transaction fee on each result so the spam will successfully flood both the p2p relay network and the blockchain.

There has been the suggestion that the service might be also be used as a [[mixing service]], as the composition of a wallet can be materially changed after running wagers through SatoshiDice<ref>[http://bitcointalk.org/index.php?topic=79079.0 Blockchain-based betting services function as mixing services?]</ref>.
Though this approach could change the makeup of the wallet, it does not sufficiently serve the mixing purpose as the coins returned in winning bets are tied to the coins from the wager transaction.

There is no reason to believe that [[Satoshi Nakamoto]] has anything to do with this attack, other than the service choosing to include the noun Satoshi in the brand.

SatoshiDice.com was [https://bitcointalk.org/index.php?topic=77870.0 announced] on bitcointalk on April 24th, 2012, by its operator, Eric Voorhees. A user of this wiki [https://en.bitcoin.it/w/index.php?title=SatoshiDice&diff=prev&oldid=38056 claimed] that it is currently operated by and licensed under Costa Rica-based Blockchain Limitada. It is unclear whether Mr. Voorhees controls Blockchain Limitada. A [http://www.google.com/search?client=safari&rls=en&q=%22blockchain+limitada%22&ie=UTF-8&oe=UTF-8 google search for "Blockchain Limitada"] yields no hits.

SatoshiDice permanently blocked US players in May 2013 citing potential legal concern.

==Random Number Generation==

To determine if a wager is a winner or loser, the site uses a method to produce a number between 0 and 65,535, similar to how a random number generator (RNG) would be used. The service uses a combination of the transaction hash from the wager transaction from the blockchain and performs a 512-bit SHA2 hash for that transaction hash using a secret unknown to the player. The first four bytes of that hash become the lucky number in determining winner or loser.

==Odds==

Each wager address has different odds, and each gives the house an edge of 1.90% (i.e., payouts are 98.1% when including the payout to the losing bets). The website shows the full list of wager addresses and odds.

==Automated Betting==

Some gamblers have built automated betting bot scripts employing the Martingale betting system and variants thereof<ref>[http://bitcointalk.org/index.php?topic=80245.0 PHP martingale bot for satoshiDICE]</ref>.

==History==

SatoshiDice was the brand given the service initially created by [[BitcoinTalk]] forum user FireDuck before selling the system to another operator<ref>[http://www.reddit.com/r/Bitcoin/comments/segz0/anyone_want_to_run_my_bitcoin_casino Anyone want to run my bitcoin casino]</ref>. The service was announced on April 24, 2012<ref>[http://bitcointalk.org/index.php?topic=77870.0 SatoshiDICE.com - Verified rolls, up to 65,000x winning]</ref>.
Within weeks, the site became responsible for more Bitcoin transactions than all other uses of Bitcoin combined<ref>[http://bitcointalk.org/index.php?topic=79285.0 All-time transaction record was just hit]</ref>.

Since August 20, 2012 some SatoshiDice shares are traded<ref>https://bitcointalk.org/index.php?topic=101902.0 IPO shares announcement</ref> on the Romanian exchange platform [[MPEx]] under S.DICE symbol and paying monthly dividends.

'''1dice1e6pdhLzzWQq7yMidf6j8eAg7pkY''', is a version-0 Bitcoin [[address]]. By sending coins to this address, one participates in SatoshiDice's "lessthan 1" gambling game, which offers a 0.0015% chance to win 64000× the original bet. As SatoshiDice is fully automatic, transactions sent to this address will receive payment almost immediately after it is broadcast.

As with all SatoshiDice betting addresses, this address is a [[Vanitygen|vanity]] one, specially generated to have a "1dice" prefix. The address that holds the "1dice" firstbits, however, is 1DicEcEgURmiRqfunhFWgUjd4HZZLkzyWQ, an insignificant address likely unrelated to SatoshiDice.

Thus far, SatoshiDice's appeal has caused this address to be among the most-used addresses.

==See Also==

* [[Mixing service]]
* [[Bitcoin Ladder]]

== Reviews ==

[http://www.bitcoincasinopro.com/reviews/satoshi-dice/ SatoshiDice Review] A+ Bitcoin Casino Pro Rating

==External Links==

* [http://www.SatoshiDice.com SatoshiDice.com] website

==References==
<references />

[[Category:Gambling]]

File:Redirect arrow.png

2014-04-06T18:37:32Z

Imsaguy: Protected "File:Redirect arrow.png": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite))

== Licensing ==
{{FAL}}

Category:Forums

2014-04-06T18:16:59Z

Imsaguy: Unrelated

Forums related to Bitcoin:
<br /><br />
'''Web Forums:'''<br />
https://bitcointalk.org/<br />
http://bitcoinforums.net/<br />
https://bitcoin.org.uk/<br />
https://coinforum.ca/<br />

Template:Uw-block

2014-04-06T18:15:17Z

Imsaguy: Protected "Template:Uw-block": template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<noinclude>{{template}}</noinclude>{{mbox
|title=You have been permanently blocked from editing.
|content=
|bgcol=ff8888
|bordercol=880000
}}

Template:Uw-scam

2014-04-06T18:15:08Z

Imsaguy: Protected "Template:Uw-scam" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<noinclude>{{template}}</noinclude>{{{icon|[[File:Stophand.png|32px|alt=Information icon]]}}} You appear to be inserting links to malicious or fraudulent sites. This is your <b>last warning</b>. Should you do this again, <b>you will be blocked without further notice</b>.
<includeonly>[[Category:Con artists|{{PAGENAME}}]]</includeonly>

Template:Uw-vandalism1

2014-04-06T18:14:31Z

Imsaguy: Protected "Template:Uw-vandalism1": Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<noinclude>{{template}}</noinclude>{{{icon|[[File:Information.png|25px|alt=Information icon]]}}} Hello, I'm <includeonly>[[User:{{safesub<noinclude></noinclude>st:REVISIONUSER}}|{{safesub<noinclude></noinclude>st:REVISIONUSER}}]]</includeonly><noinclude>[[Satoshi Nakamoto|satoshi]]</noinclude>. I wanted to let you know that I undid one or more of [[Special:Contributions/{{<includeonly>safesubst:</includeonly>BASEPAGENAME}}|your recent contributions]]{{<includeonly>safesubst:</includeonly>#if:{{{1|}}}| to [[:{{{1}}}]]}} because it did not appear constructive. If you would like to experiment, please use your userspace. If you think I made a mistake, or if you have any questions, you can leave me a message on [[User_talk:<includeonly>{{safesub<noinclude></noinclude>st:REVISIONUSER}}</includeonly><noinclude>satoshi</noinclude>|my talk page]]. {{{2|Thanks!}}}<noinclude>
</noinclude><includeonly>[[Category:Level 1 vandals|{{PAGENAME}}]]</includeonly>

Template:Uw-vandalism2

2014-04-06T18:14:14Z

Imsaguy: Protected "Template:Uw-vandalism2": Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<noinclude>{{template}}</noinclude>{{{icon|[[File:Information orange.png|25px|alt=Information icon]]}}} Please refrain from making unconstructive edits to the Bitcoin wiki{{<includeonly>safesubst:</includeonly>#if:{{{1|}}}|, as you did at [[:{{{1}}}]]}}. Your edits appear to constitute vandalism and have been reverted or removed. If you would like to experiment, please use your userspace. Administrators have the ability to block users from editing if they repeatedly engage in vandalism. {{{2|Thank you.}}}
<includeonly>[[Category:Level 2 vandals|{{PAGENAME}}]]</includeonly>

Template:Uw-vandalism3

2014-04-06T18:14:00Z

Imsaguy: Protected "Template:Uw-vandalism3": Template ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<noinclude>{{template}}</noinclude>{{{icon|[[File:Stophand.png|32px|alt=Information icon]]}}} This is your <b>last warning</b>. The next time you vandalize, <b>you will be blocked without further notice</b>.
<includeonly>[[Category:Level 3 vandals|{{PAGENAME}}]]</includeonly>

Distributed Autonomous Community / Decentralized Application

2014-04-06T17:05:14Z

Imsaguy:

A '''Distributed Autonomous Community''' ('''DAC''') is an "entity" without any central point of control, with a certain agenda, business plan, and protocol. A '''Decentralized Application''' or '''DA''' is an alternative formulation of a DAC. The concept is currently being developed by David Johnston.

There is an accelerating trend of more and more DACs being formed.

== List of DACs ==
* [[Bitcoin]] itself, the first DAC?
* Altcurrencies, all of Bitcoin forks
* [[Ripple]] Labs is borderline ... they are a registered company and could be ordered to shutdown. The protocol is perhaps a DAC.
* [[Mastercoin]], a DAC replacement for Forex, Shares, and much more. Later evolved into a ProtoShares competitor.
* [[ProtoShares]], a meta DAC with the purpose of provding infrastructure for other DACs. It is composed of
** DomainShares, a DAC replacement for Namecoin
** BitShares, a competitor to Mastercoin 
** Keyhotee, a DAC replacement for OpenID
** Other infrastructure components to follow... ?
* [[Mitosys]] - a DAC replacement for Bit-Message
* [[Colored Coins]] are working on defining themselves as a DAC ... no working business model spotted yet.

== Ideas ==
* A social network - Monetizable Diaspora

== External links ==
* [http://bitcoinmagazine.com/7050/bootstrapping-a-decentralized-autonomous-corporation-part-i/ Bitcoin Magazine: Bootstrapping a DAC]
* [http://bitsharestalk.org/index.php?topic=297.0 Topic on bitsharestalk]
* [http://invictus-innovations.com/i-dac/ What is a DAC?]
* [http://invictus-innovations.com/i-dac-1/ The Three Laws of Robotics for DACs]
* [https://github.com/DavidJohnstonCEO/DecentralizedApplications Decentralized Application]

[[Category:DACs]]

World Bitcoin Exchange

2014-04-06T17:03:11Z

Imsaguy:

{{outdated|Defunct}}
A [[currency exchange|exchange]] that offered AUD (BTC/AUD) trading.

High Net Worth Property Pty Ltd owns the World Bitcoin Exchange.

==History==

The service was launched on August 10th, 2011<ref>[https://bitcointalk.org/index.php?topic=37079.0 Australian Bitcoin exchange is now live]</ref>. The site uses the open source Intersango [[:Category:Open Source|open source]] software <ref>[http://www.bitcoin.org/smf/index.php?topic=4579.0 Free Bitcoin exchange software- Intersango]</ref>.

==See Also==

* [[Buying bitcoins]]
* [[Selling bitcoins]]

==References==
<references/>

Aqoin

2014-04-06T16:58:11Z

Imsaguy:

{{outdated|Defunct}}
Aqoin is an online Bitcoin wallet. The main objetive of the aqoin wallet is security.

The languages supported by the site are Spanish and English.

The service was announced September 1th, 2011.

==External Links==

* [http://www.aqoin.me Aqoin] web site
* [http://aqoin.blogspot.com Aqoin blog]
* [http://twitter.com/aqoin Aqoin in Twitter]
* [http://facebook.com/aqoin Aqoin in Facebook]
* [https://plus.google.com/101312835816191517070 Aqoin in Google+]

==References==
<References />

[[Category:EWallets]]

MtGox/API/HTTP/

2014-04-06T16:08:03Z

Imsaguy: Redirected page to MtGox/API/HTTP

#REDIRECT [[MtGox/API/HTTP]]

WalletBit/API/SendTo

2014-04-06T16:06:50Z

Imsaguy: Add disclaimer

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751

The article is kept only as historic documentation.

===Send to Email or Mobile number (SMS)===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com', // Requires a valid WalletBit account with API key.
'to' => '4550142790', // Email or Mobile number
'from' => '4591614856', // Email, Name or Phone number
'details' => 'You got Bitcoins!' // Message to recipient
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['to'] . ':' . $fields['from'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/sendto');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = json_decode(curl_exec($ch));
curl_close($ch);

if (is_object($response))
{
// everythings good
if ($response->status == 1)
{
// any bitcoin sent to this address will be forwarded
print $response->address;
}
else
{
// print error message
print $response->message;
}
}
</source>

==Send Bitcoin Methods==

Parameters:<br />
Merchant - WalletBit email<br />
To * - The recipient's email address or mobile phone number (712 mobile networks in 212 countries)<br />
From - The sender's name, phone number or email address<br />
Details - Optional details to include. (22 characters message limit on phone messages)<br />

* Numbers MUST be in their international format, (no leading zeroes). The UK number 0870 711 111 will become 44870711111<br /><br />

Return:<br />
Status - Indicating if the transaction was successful by a one or zero.<br />
Message - Response from sendTo containing possible errors or similar.<br />
Address - A Bitcoin address. Send bitcoins to it, and it will be forwarded immediately.<br />

When bitcoin is sent to the generated bitcoin address, the system will send out IPN to the defined url in your account.<br />

Our sendTo system covers 712 mobile networks in 212 countries — we can reach almost all mobile phones, however please test if we can reach your mobile or the mobile you want to send to, prior to utilize sending bitcoin via SMS. If the mobile is not covered, you can still enjoy sending instant to email addresses with WalletBit.

WalletBit/API/SendTo

2014-04-06T16:06:25Z

Imsaguy: Undo revision 39485 by WalletBit (talk)

===Send to Email or Mobile number (SMS)===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com', // Requires a valid WalletBit account with API key.
'to' => '4550142790', // Email or Mobile number
'from' => '4591614856', // Email, Name or Phone number
'details' => 'You got Bitcoins!' // Message to recipient
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['to'] . ':' . $fields['from'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/sendto');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = json_decode(curl_exec($ch));
curl_close($ch);

if (is_object($response))
{
// everythings good
if ($response->status == 1)
{
// any bitcoin sent to this address will be forwarded
print $response->address;
}
else
{
// print error message
print $response->message;
}
}
</source>

==Send Bitcoin Methods==

Parameters:<br />
Merchant - WalletBit email<br />
To * - The recipient's email address or mobile phone number (712 mobile networks in 212 countries)<br />
From - The sender's name, phone number or email address<br />
Details - Optional details to include. (22 characters message limit on phone messages)<br />

* Numbers MUST be in their international format, (no leading zeroes). The UK number 0870 711 111 will become 44870711111<br /><br />

Return:<br />
Status - Indicating if the transaction was successful by a one or zero.<br />
Message - Response from sendTo containing possible errors or similar.<br />
Address - A Bitcoin address. Send bitcoins to it, and it will be forwarded immediately.<br />

When bitcoin is sent to the generated bitcoin address, the system will send out IPN to the defined url in your account.<br />

Our sendTo system covers 712 mobile networks in 212 countries — we can reach almost all mobile phones, however please test if we can reach your mobile or the mobile you want to send to, prior to utilize sending bitcoin via SMS. If the mobile is not covered, you can still enjoy sending instant to email addresses with WalletBit.

ResponsePay

2014-04-06T16:04:12Z

Imsaguy: Add disclaimer

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751

The article is kept only as historic documentation.

ResponsePay is a lightweight mobile bitcoin payment solution [[eWallet]] built with responsive & adaptive web design so will scale to fit. ResponsePay provides people with a simple yet very effective method of sending bitcoin locally and internationally. ResponsePay can reach almost all mobile phones, and it is instant.

==Transfer Methods==

===E-Mail===
Bitcoins can be send as an e-mail, the recipient will receive an claim link to redeem the bitcoins.

===SMS (Text messaging)===
Allow users in 212 countries to access their bitcoins via SMS messages. Send to mobile phones not registered in ResponsePay and the recipient will receive a claim link to redeem the bitcoins at ResponsePay.

They are working to be the equivalent to M-Pesa for bitcoin. It's important to realize they are just getting started and this is only the beginning of their path to fruition. A small fee of 0.0225 may apply if sending to a mobile phone number not registered in ResponsePay. A flat fee of 0.0005 BTC is deducted per all other transactions. The mobile provider may charge additional fees.

==History==

The service was launched on July 4, 2012<ref>[https://bitcointalk.org/index.php?topic=91431.0 [ANN] ResponsePay - Mobile Wallet, Subsidiary of WalletBit.]</ref>.

==External Links==

* [https://responsepay.com ResponsePay] web site.

==References==
<references />

==See Also==

* [[WalletBit]] Simple, Flexible & Secure Bitcoin.

[[Category:EWallets]]
[[Category:Financial]]
[[Category:Mobile]]

ResponsePay

2014-04-06T16:03:44Z

Imsaguy: Undo revision 39493 by WalletBit (talk)

ResponsePay is a lightweight mobile bitcoin payment solution [[eWallet]] built with responsive & adaptive web design so will scale to fit. ResponsePay provides people with a simple yet very effective method of sending bitcoin locally and internationally. ResponsePay can reach almost all mobile phones, and it is instant.

==Transfer Methods==

===E-Mail===
Bitcoins can be send as an e-mail, the recipient will receive an claim link to redeem the bitcoins.

===SMS (Text messaging)===
Allow users in 212 countries to access their bitcoins via SMS messages. Send to mobile phones not registered in ResponsePay and the recipient will receive a claim link to redeem the bitcoins at ResponsePay.

They are working to be the equivalent to M-Pesa for bitcoin. It's important to realize they are just getting started and this is only the beginning of their path to fruition. A small fee of 0.0225 may apply if sending to a mobile phone number not registered in ResponsePay. A flat fee of 0.0005 BTC is deducted per all other transactions. The mobile provider may charge additional fees.

==History==

The service was launched on July 4, 2012<ref>[https://bitcointalk.org/index.php?topic=91431.0 [ANN] ResponsePay - Mobile Wallet, Subsidiary of WalletBit.]</ref>.

==External Links==

* [https://responsepay.com ResponsePay] web site.

==References==
<references />

==See Also==

* [[WalletBit]] Simple, Flexible & Secure Bitcoin.

[[Category:EWallets]]
[[Category:Financial]]
[[Category:Mobile]]

WalletBit/API

2014-04-06T16:01:14Z

Imsaguy:

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751.new

The article is kept only as historic documentation.

Four APIs are currently available:

* [[WalletBit/API/Send|Send API]]
* [[WalletBit/API/SendTo|SendTo API]]
* [[WalletBit/API/Getnewaddress|Getnewaddress API]]
* [[WalletBit/API/Lookup|Lookup API]]

===Send to Email or Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'customer_email' => 'johnsmith@example.com',
'address' => '',
'amount' => 0.01000000,
'details' => 'You got Bitcoins!'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['customer_email'] . ':' . $fields['amount'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);

if ($response == '1')
{

}
</source>

If 'customer_email' is not on WalletBit, it will try to send to the defined bitcoin address.

===Send to Email or Mobile number (SMS)===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com', // Requires a valid WalletBit account with API key.
'to' => '4550142790', // Email or Mobile number
'from' => '4591614856', // Email, Name or Phone number
'details' => 'You got Bitcoins!' // Message to recipient
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['to'] . ':' . $fields['from'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/sendto');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = json_decode(curl_exec($ch));
curl_close($ch);

if (is_object($response))
{
// everythings good
if ($response->status == 1)
{
// any bitcoin sent to this address will be forwarded
print $response->address;
}
else
{
// print error message
print $response->message;
}
}
</source>

==Send Bitcoin Methods==

Parameters:<br />
Merchant - WalletBit email<br />
To * - The recipient's email address or mobile phone number (712 mobile networks in 212 countries)<br />
From - The sender's name, phone number or email address<br />
Details - Optional details to include. (22 characters message limit on phone messages)<br />

* Numbers MUST be in their international format, (no leading zeroes). The UK number 0870 711 111 will become 44870711111<br /><br />

Return:<br />
Status - Indicating if the transaction was successful by a one or zero.<br />
Message - Response from sendTo containing possible errors or similar.<br />
Address - A Bitcoin address. Send bitcoins to it, and it will be forwarded immediately.<br />

When bitcoin is sent to the generated bitcoin address, the system will send out IPN to the defined url in your account.<br />

Our sendTo system covers 712 mobile networks in 212 countries — we can reach almost all mobile phones, however please test if we can reach your mobile or the mobile you want to send to, prior to utilize sending bitcoin via SMS. If the mobile is not covered, you can still enjoy sending instant to email addresses with WalletBit.

===Generate new Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'label' => 'TEST'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['label'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/getnewaddress');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response will contain your new bitcoin address, otherwise empty.

===Lookup deposit to Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'address' => '1BPeF1tGHQj1tHoyZkFps1QKCbnqdx2yHE'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['address'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/lookup/deposit');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response returns a json encoded array containing batch number, amount, fee, confirmations, txid, address and timestamp of deposit to the provided Bitcoin address, otherwise empty.

WalletBit/Integrate

2014-04-06T16:00:23Z

Imsaguy:

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751.new

The article is kept only as historic documentation.

Below you'll find tutorials that will teach you how to use [[WalletBit]] API, and reference documentation for all the moving parts

Three methods are currently available for integrating to your online shop:

==Create a payment form==

===If you want to integrate WalletBit On-site payment system===

Copy the following code, then place it immediately before the closing </head>

<source lang="javascript">
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>
<script type="text/javascript">
(function() {
var wb = document.createElement('script'); wb.type = 'text/javascript'; wb.async = true;
wb.src = 'https://walletbit.com/pay/01ee1e83d3d38627af1ee8bf88fe8a0c?url=' + escape(parent.location.href);
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(wb, s);
})();
</script>
</source>

And the following anywhere in your HTML where you want a payment button. Adjust the product name in text and amount in the rel value. You can define where you want to send customers after purchase by editing href value. If you need additional variable place them in target of the a tag splitted by pipe |

<source lang="html4strict"><a rel="0.01000000" target="wb_1=red|wb_2=green" test="0" href="https://walletbit.com/" class="WalletBitButton">Auction Goods</a></source>

You can also build your own payment button, for instance a support button looks like this, notice the class WalletBitButtonCustom

<source lang="html4strict"><a rel="0.50" test="0" href="https://walletbit.com/" title="Support this free service" class="WalletBitButtonCustom" >1MrcomYR9JrbeYzyPTCSH9usfAuW5WjtJu</a></source>

===If you want a standard checkout process where customers leave your site and come back once completed===

<source lang="html4strict">
<form method="post" action="https://walletbit.com/pay">
<input type="hidden" name="token" value="01ee1e83d3d38627af1ee8bf88fe8a0c" />
<input type="hidden" name="item_name" value="Auction Goods" />
<input type="hidden" name="amount" value="0.01000000" />
<input type="hidden" name="returnurl" value="https://walletbit.com/" />
<input type="hidden" name="additional" value="wb_1=red|wb_2=green" />
<input type="hidden" name="test" value="0" />
<input type="image" class="walletbitcheckout" src="https://walletbit.com/includes/checkout.png" border="0" name="submit" alt="WalletBit - Simple, Flexible & Secure Bitcoin" title="WalletBit - Simple, Flexible & Secure Bitcoin" />
</form><script type="text/javascript" src="https://walletbit.com/scripts/checkout.js"></script>
</source>

===Subscription form===

<source lang="html4strict">
<form class="walletbit" method="post" action="https://walletbit.com/checkout/subscribe">
<input name="token" value="01ee1e83d3d38627af1ee8bf88fe8a0c" type="hidden">
<input name="item_name" value="Magazine" type="hidden">
<input name="amount" value="1" type="hidden">
<input name="period" value="1" type="hidden">
<input name="cycle" value="M" type="hidden">
<input name="adjustable" value="1" type="hidden">
<input name="returnurl" value="" type="hidden">
<input name="additional" value="" type="hidden">
<input name="test" value="0" type="hidden">
<input id="walletbitsubscribe" src="https://walletbit.com/subscribebutton/1" name="submit" alt="WalletBit - Simple, Flexible & Secure Bitcoin" title="WalletBit - Simple, Flexible & Secure Bitcoin" border="0" type="image"></form><script type="text/javascript" src="https://walletbit.com/jq/subscribe"></script>
</source>

Remember to replace the TOKEN with your own.

WalletBit/API/Lookup

2014-04-06T15:59:50Z

Imsaguy: Add disclaimer

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751.new

The article is kept only as historic documentation.

===Lookup deposit to Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'address' => '1BPeF1tGHQj1tHoyZkFps1QKCbnqdx2yHE'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['address'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/lookup/deposit');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response returns a json encoded array containing batch number, amount, fee, confirmations, txid, address and timestamp of deposit to the provided Bitcoin address, otherwise empty.

WalletBit/API/Getnewaddress

2014-04-06T15:59:37Z

Imsaguy: Add disclaimer

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751.new

The article is kept only as historic documentation.

===Generate new Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'label' => 'TEST'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['label'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/getnewaddress');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response will contain your new bitcoin address, otherwise empty.

WalletBit/API/Send

2014-04-06T15:59:24Z

Imsaguy: Add disclaimer

The following information may no longer be true, WalletBit service was suspended
See https://bitcointalk.org/index.php?topic=249751.new

The article is kept only as historic documentation.

===Send to Email or Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'customer_email' => 'johnsmith@example.com',
'address' => '',
'amount' => 0.01000000,
'details' => 'You got Bitcoins!'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['customer_email'] . ':' . $fields['amount'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);

if ($response == '1')
{

}
</source>

If 'customer_email' is not on WalletBit, it will try to send to the defined bitcoin address.

WalletBit/API/Lookup

2014-04-06T15:58:15Z

Imsaguy: Undo revision 39487 by WalletBit (talk)

===Lookup deposit to Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'address' => '1BPeF1tGHQj1tHoyZkFps1QKCbnqdx2yHE'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['address'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/lookup/deposit');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response returns a json encoded array containing batch number, amount, fee, confirmations, txid, address and timestamp of deposit to the provided Bitcoin address, otherwise empty.

WalletBit/API/Getnewaddress

2014-04-06T15:57:58Z

Imsaguy: Undo revision 39486 by WalletBit (talk)

===Generate new Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'label' => 'TEST'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['label'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/getnewaddress');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response will contain your new bitcoin address, otherwise empty.

WalletBit/API/Send

2014-04-06T15:57:43Z

Imsaguy: Undo revision 39484 by WalletBit (talk)

===Send to Email or Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'customer_email' => 'johnsmith@example.com',
'address' => '',
'amount' => 0.01000000,
'details' => 'You got Bitcoins!'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['customer_email'] . ':' . $fields['amount'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);

if ($response == '1')
{

}
</source>

If 'customer_email' is not on WalletBit, it will try to send to the defined bitcoin address.

WalletBit/Integrate

2014-04-06T15:57:05Z

Imsaguy: Undo revision 39482 by WalletBit (talk)

Below you'll find tutorials that will teach you how to use [[WalletBit]] API, and reference documentation for all the moving parts

Three methods are currently available for integrating to your online shop:

==Create a payment form==

===If you want to integrate WalletBit On-site payment system===

Copy the following code, then place it immediately before the closing </head>

<source lang="javascript">
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>
<script type="text/javascript">
(function() {
var wb = document.createElement('script'); wb.type = 'text/javascript'; wb.async = true;
wb.src = 'https://walletbit.com/pay/01ee1e83d3d38627af1ee8bf88fe8a0c?url=' + escape(parent.location.href);
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(wb, s);
})();
</script>
</source>

And the following anywhere in your HTML where you want a payment button. Adjust the product name in text and amount in the rel value. You can define where you want to send customers after purchase by editing href value. If you need additional variable place them in target of the a tag splitted by pipe |

<source lang="html4strict"><a rel="0.01000000" target="wb_1=red|wb_2=green" test="0" href="https://walletbit.com/" class="WalletBitButton">Auction Goods</a></source>

You can also build your own payment button, for instance a support button looks like this, notice the class WalletBitButtonCustom

<source lang="html4strict"><a rel="0.50" test="0" href="https://walletbit.com/" title="Support this free service" class="WalletBitButtonCustom" >1MrcomYR9JrbeYzyPTCSH9usfAuW5WjtJu</a></source>

===If you want a standard checkout process where customers leave your site and come back once completed===

<source lang="html4strict">
<form method="post" action="https://walletbit.com/pay">
<input type="hidden" name="token" value="01ee1e83d3d38627af1ee8bf88fe8a0c" />
<input type="hidden" name="item_name" value="Auction Goods" />
<input type="hidden" name="amount" value="0.01000000" />
<input type="hidden" name="returnurl" value="https://walletbit.com/" />
<input type="hidden" name="additional" value="wb_1=red|wb_2=green" />
<input type="hidden" name="test" value="0" />
<input type="image" class="walletbitcheckout" src="https://walletbit.com/includes/checkout.png" border="0" name="submit" alt="WalletBit - Simple, Flexible & Secure Bitcoin" title="WalletBit - Simple, Flexible & Secure Bitcoin" />
</form><script type="text/javascript" src="https://walletbit.com/scripts/checkout.js"></script>
</source>

===Subscription form===

<source lang="html4strict">
<form class="walletbit" method="post" action="https://walletbit.com/checkout/subscribe">
<input name="token" value="01ee1e83d3d38627af1ee8bf88fe8a0c" type="hidden">
<input name="item_name" value="Magazine" type="hidden">
<input name="amount" value="1" type="hidden">
<input name="period" value="1" type="hidden">
<input name="cycle" value="M" type="hidden">
<input name="adjustable" value="1" type="hidden">
<input name="returnurl" value="" type="hidden">
<input name="additional" value="" type="hidden">
<input name="test" value="0" type="hidden">
<input id="walletbitsubscribe" src="https://walletbit.com/subscribebutton/1" name="submit" alt="WalletBit - Simple, Flexible & Secure Bitcoin" title="WalletBit - Simple, Flexible & Secure Bitcoin" border="0" type="image"></form><script type="text/javascript" src="https://walletbit.com/jq/subscribe"></script>
</source>

Remember to replace the TOKEN with your own.

WalletBit/API

2014-04-06T15:56:27Z

Imsaguy: Undo revision 39483 by WalletBit (talk)

Four APIs are currently available:

* [[WalletBit/API/Send|Send API]]
* [[WalletBit/API/SendTo|SendTo API]]
* [[WalletBit/API/Getnewaddress|Getnewaddress API]]
* [[WalletBit/API/Lookup|Lookup API]]

===Send to Email or Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'customer_email' => 'johnsmith@example.com',
'address' => '',
'amount' => 0.01000000,
'details' => 'You got Bitcoins!'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['customer_email'] . ':' . $fields['amount'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);

if ($response == '1')
{

}
</source>

If 'customer_email' is not on WalletBit, it will try to send to the defined bitcoin address.

===Send to Email or Mobile number (SMS)===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com', // Requires a valid WalletBit account with API key.
'to' => '4550142790', // Email or Mobile number
'from' => '4591614856', // Email, Name or Phone number
'details' => 'You got Bitcoins!' // Message to recipient
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['to'] . ':' . $fields['from'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/sendto');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = json_decode(curl_exec($ch));
curl_close($ch);

if (is_object($response))
{
// everythings good
if ($response->status == 1)
{
// any bitcoin sent to this address will be forwarded
print $response->address;
}
else
{
// print error message
print $response->message;
}
}
</source>

==Send Bitcoin Methods==

Parameters:<br />
Merchant - WalletBit email<br />
To * - The recipient's email address or mobile phone number (712 mobile networks in 212 countries)<br />
From - The sender's name, phone number or email address<br />
Details - Optional details to include. (22 characters message limit on phone messages)<br />

* Numbers MUST be in their international format, (no leading zeroes). The UK number 0870 711 111 will become 44870711111<br /><br />

Return:<br />
Status - Indicating if the transaction was successful by a one or zero.<br />
Message - Response from sendTo containing possible errors or similar.<br />
Address - A Bitcoin address. Send bitcoins to it, and it will be forwarded immediately.<br />

When bitcoin is sent to the generated bitcoin address, the system will send out IPN to the defined url in your account.<br />

Our sendTo system covers 712 mobile networks in 212 countries — we can reach almost all mobile phones, however please test if we can reach your mobile or the mobile you want to send to, prior to utilize sending bitcoin via SMS. If the mobile is not covered, you can still enjoy sending instant to email addresses with WalletBit.

===Generate new Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'label' => 'TEST'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['label'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/getnewaddress');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response will contain your new bitcoin address, otherwise empty.

===Lookup deposit to Bitcoin address===

<source lang="php">
$fields = array(
'merchant' => 'owner@example.com',
'address' => '1BPeF1tGHQj1tHoyZkFps1QKCbnqdx2yHE'
);
$fields['encrypted'] = strtoupper(hash('sha256', $fields['merchant'] . ':' . $fields['address'] . ':' . 'API Key'));

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://walletbit.com/api/lookup/deposit');
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, TRUE);
curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
curl_setopt($ch, CURLOPT_POST, count($fields));
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($fields));
$response = curl_exec($ch);
curl_close($ch);
</source>

If successful $response returns a json encoded array containing batch number, amount, fee, confirmations, txid, address and timestamp of deposit to the provided Bitcoin address, otherwise empty.

Bitcoin Wiki:AboutWiki

2014-04-06T15:48:07Z

Imsaguy: Cleanup the grammer

This Wiki is a public resource for the community of Bitcoin users, developers, and businesses as well as anyone interested in Bitcoin.

Unlike Wikipedia, the Bitcoin Wiki is ''not'' an encyclopedia, and includes things like non-encyclopedia details (e.g., exact specifications on service fees, product performance, etc), how-to manuals, protocol specifications, etc. There are also no notability requirements beyond the requirement that the material be of general interest to some segment of the Bitcoin community or the Bitcoin-curious general public.

Because this resource is open to editing by the general public, readers should be aware that the material presented here often does not reflect the views of the entire Bitcoin community and may be outdated, incorrect, or outright malicious at times.

== Some advice for editing ==

Content on the Wiki should generally be factual in nature where possible, but because Bitcoin is relatively new, many important subjects are not yet completely understood and are sometimes best described by opinion. When there is controversy, the Bitcoin wiki should teach it and explain all the major views. Editors should refrain from asserting ownership over an article and seek compromise where possible. Opinion pieces that are of general community interest can be posted under the user's personal namespace. Generally, if you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.

While the Wiki doesn't exist to promote any particular businesses or commercial activity, such things are important parts of the Bitcoin ecosystem and get discussed here, but biased editing with a strong pecuniary interest is frowned upon and spamming up the wiki with referral links is prohibited. Non-Bitcoin alternatives may, at times, be discussed here, especially for comparison purposes or to illustrate a point but this wiki is a Bitcoin community resource and edits which promote competing systems may be frowned on by the community.

To prevent unnecessary drama, editors should refrain from adding material which they believe may be unlawful for them or other editors to post. Bitcoin Wiki respects your freedom to communicate but since this is a shared resource you should respect other people's right to be free from the association with your views and their consequences.

As a small community resource, the Bitcoin Wiki is often less formal than generic references like Wikipedia and because it addresses a broad community of interests, not all pages will be suitable for all readers: Some pages are written for a technical audience about a technical subject and wouldn't serve their intended audience if simplified for the layman. In cases where audience goals conflict and can't be resolved, we should ExpandSpace and create new pages to cover the subject from different angles if we need to. Editors should be mindful, however, of the work it takes to maintain pages and try to avoid an excessive proliferation of pages which will not be well maintained.

Protocol documentation

2014-03-31T04:08:53Z

Imsaguy: Fix the hash.

Sources:
* [[Original Bitcoin client]] source

Type names used in this documentation are from the C99 standard.

For protocol used in mining, see [[getblocktemplate]].

==Common standards==

=== Hashes ===

Usually, when a hash is computed within bitcoin, it is computed twice. Most of the time [http://en.wikipedia.org/wiki/SHA-2 SHA-256] hashes are used, however [http://en.wikipedia.org/wiki/RIPEMD RIPEMD-160] is also used when a shorter hash is desirable (for example when creating a bitcoin address).

Example of double-SHA-256 encoding of string "hello":

hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 (first round of sha-256)
d7914fe546b684688bb95f4f888a92dfc680603a75f23eb823658031fff766d9 (second round of sha-256)

For bitcoin addresses (RIPEMD-160) this would give:

hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 (first round is sha-256)
b6a9c8c230722b7c748331a8b450f05566dc7d0f (with ripemd-160)

=== Merkle Trees ===

Merkle trees are binary trees of hashes. Merkle trees in bitcoin use a '''double''' SHA-256, the SHA-256 hash of the SHA-256 hash of something.

If, when forming a row in the tree (other than the root of the tree), it would have an odd number of elements, the final double-hash is duplicated to ensure that the row has an even number of hashes.

First form the bottom row of the tree with the ordered double-SHA-256 hashes of the byte streams of the transactions in the block.

Then the row above it consists of half that number of hashes. Each entry is the double-SHA-256 of the 64-byte concatenation of the corresponding two hashes below it in the tree.

This procedure repeats recursively until we reach a row consisting of just a single double-hash. This is the '''merkle root''' of the tree.

For example, imagine a block with three transactions ''a'', ''b'' and ''c''. The merkle tree is:

d1 = dhash(a)
d2 = dhash(b)
d3 = dhash(c)
d4 = dhash(c) # a, b, c are 3. that's an odd number, so we take the c twice

d5 = dhash(d1 concat d2)
d6 = dhash(d3 concat d4)

d7 = dhash(d5 concat d6)

where

dhash(a) = sha256(sha256(a))

''d7'' is the merkle root of the 3 transactions in this block.

Note: Hashes in Merkle Tree displayed in the [[Block Explorer]] are of little-endian notation. For some implementations and [http://www.fileformat.info/tool/hash.htm calculations], the bits need to be reversed before they are hashed, and again after the hashing operation.

=== Signatures ===

Bitcoin uses [http://en.wikipedia.org/wiki/Elliptic_curve_cryptography Elliptic Curve] [http://en.wikipedia.org/wiki/Digital_Signature_Algorithm Digital Signature Algorithm] ([http://en.wikipedia.org/wiki/Elliptic_Curve_DSA ECDSA]) to sign transactions.

For ECDSA the secp256k1 curve from http://www.secg.org/collateral/sec2_final.pdf is used.

Public keys (in scripts) are given as 04 <x> <y> where ''x'' and ''y'' are 32 byte big-endian integers representing the coordinates of a point on the curve or in compressed form given as <sign> <x> where <sign> is 0x02 if ''y'' is even and 0x03 if ''y'' is odd.

Signatures use [http://en.wikipedia.org/wiki/Distinguished_Encoding_Rules DER encoding] to pack the ''r'' and ''s'' components into a single byte stream (this is also what OpenSSL produces by default).

=== Transaction Verification ===
Transactions are cryptographically signed records that reassign ownership of Bitcoins to new addresses. Transactions have ''inputs'' - records which reference the funds from other previous transactions - and ''outputs'' - records which determine the new owner of the transferred Bitcoins, and which will be referenced as inputs in future transactions as those funds are respent.

Each ''input'' must have a cryptographic digital signature that unlocks the funds from the prior transaction. Only the person possessing the appropriate [[private key]] is able to create a satisfactory signature; this in effect ensures that funds can only be spent by their owners.

Each ''output'' determines which Bitcoin address (or other criteria, see [[Scripting]]) is the recipient of the funds.

In a transaction, the sum of all inputs must be equal to or greater than the sum of all outputs. If the inputs exceed the outputs, the difference is considered a [[transaction fee]], and is redeemable by whoever first includes the transaction into the block chain.

A special kind of transaction, called a [[coinbase transaction]], has no inputs. It is created by [[miners]], and there is one coinbase transaction per block. Because each block comes with a reward of newly created Bitcoins (e.g. 50 BTC for the first 210,000 blocks), the first transaction of a block is, with few exceptions, the transaction that grants those coins to their recipient (the miner). In addition to the newly created Bitcoins, the coinbase transaction is also used for assigning the recipient of any transaction fees that were paid within the other transactions being included in the same block. The coinbase transaction can assign the entire reward to a single Bitcoin address, or split it in portions among multiple addresses, just like any other transaction. Coinbase transactions always contain outputs totaling the sum of the block reward plus all transaction fees collected from the other transactions in the same block.

The [[coinbase transaction]] in block zero cannot be spent. This is due to a quirk of the reference client implementation that would open the potential for a block chain fork if some nodes accepted the spend and others did not<ref>[http://bitcointalk.org/index.php?topic=119645.msg1288552#msg1288552 Block 0 Network Fork]</ref>.

Most Bitcoin outputs encumber the newly transferred coins with a single ECDSA private key. The actual record saved with inputs and outputs isn't necessarily a key, but a ''script''. Bitcoin uses an interpreted scripting system to determine whether an output's criteria have been satisfied, with which more complex operations are possible, such as outputs that require two ECDSA signatures, or two-of-three-signature schemes. An output that references a single Bitcoin address is a ''typical'' output; an output actually contains this information in the form of a script that requires a single ECDSA signature (see [[OP_CHECKSIG]]). The output script specifies what must be provided to unlock the funds later, and when the time comes in the future to spend the transaction in another input, that input must provide all of the thing(s) that satisfy the requirements defined by the original output script.

=== Addresses ===

A bitcoin address is in fact the hash of a ECDSA public key, computed this way:

Version = 1 byte of 0 (zero); on the test network, this is 1 byte of 111
Key hash = Version concatenated with RIPEMD-160(SHA-256(public key))
Checksum = 1st 4 bytes of SHA-256(SHA-256(Key hash))
Bitcoin Address = Base58Encode(Key hash concatenated with Checksum)

The Base58 encoding used is home made, and has some differences. Especially, leading zeroes are kept as single zeroes when conversion happens.

== Common structures ==

Almost all integers are encoded in little endian. Only IP or port number are encoded big endian.

=== Message structure ===

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || magic || uint32_t || Magic value indicating message origin network, and used to seek to next message when stream state is unknown
|-
| 12 || command || char[12] || ASCII string identifying the packet content, NULL padded (non-NULL padding results in packet rejected)
|-
| 4 || length || uint32_t || Length of payload in number of bytes
|-
| 4 || checksum || uint32_t || First 4 bytes of sha256(sha256(payload))
|-
| ? || payload || uchar[] || The actual data
|}

Known magic values:

{|class="wikitable"
! Network !! Magic value !! Sent over wire as
|-
| main || 0xD9B4BEF9 || F9 BE B4 D9
|-
| testnet || 0xDAB5BFFA || FA BF B5 DA
|-
| testnet3 || 0x0709110B || 0B 11 09 07
|-
| namecoin || 0xFEB4BEF9 || F9 BE B4 FE
|}

=== Variable length integer ===

Integer can be encoded depending on the represented value to save space.
Variable length integers always precede an array/vector of a type of data that may vary in length.
Longer numbers are encoded in little endian.

{|class="wikitable"
! Value !! Storage length !! Format
|-
| < 0xfd || 1 || uint8_t
|-
| <= 0xffff || 3 || 0xfd followed by the length as uint16_t
|-
| <= 0xffffffff || 5 || 0xfe followed by the length as uint32_t
|-
| - || 9 || 0xff followed by the length as uint64_t
|}

If you're reading the Satoshi client code (BitcoinQT) it refers to this as a "CompactSize". Modern BitcoinQT has also CVarInt class which implements even more compact integer for the purpose of local storage (which is incompatible with "CompactSize" described here). CVarInt is not a part of the protocol.

=== Variable length string ===

Variable length string can be stored using a variable length integer followed by the string itself.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || length || [[Protocol_specification#Variable_length_integer|var_int]] || Length of the string
|-
| ? || string || char[] || The string itself (can be empty)
|}

=== Network address ===

When a network address is needed somewhere, this structure is used. This protocol and structure supports IPv6, '''but note that the original client currently only supports IPv4 networking'''. Network addresses are not prefixed with a timestamp in the version message.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || time || uint32 || the Time (version >= 31402)
|-
| 8 || services || uint64_t || same service(s) listed in [[#version|version]]
|-
| 16 || IPv6/4 || char[16] || IPv6 address. Network byte order. The original client only supports IPv4 and only reads the last 4 bytes to get the IPv4 address. However, the IPv4 address is written into the message as a 16 byte [http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses IPv4-mapped IPv6 address]
(12 bytes ''00 00 00 00 00 00 00 00 00 00 FF FF'', followed by the 4 bytes of the IPv4 address).
|-
| 2 || port || uint16_t || port number, network byte order
|}

Hexdump example of Network address structure

<pre>
0000 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010 00 00 FF FF 0A 00 00 01 20 8D ........ .

Network address:
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK: see services listed under version command)
00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 - IPv6: ::ffff:a00:1 or IPv4: 10.0.0.1
20 8D - Port 8333
</pre>

=== Inventory Vectors ===

Inventory vectors are used for notifying other nodes about objects they have or data which is being requested.

Inventory vectors consist of the following data format:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || type || uint32_t || Identifies the object type linked to this inventory
|-
| 32 || hash || char[32] || Hash of the object
|}

The object type is currently defined as one of the following possibilities:

{|class="wikitable"
! Value !! Name !! Description
|-
| 0 || ERROR || Any data of with this number may be ignored
|-
| 1 || MSG_TX || Hash is related to a transaction
|-
| 2 || MSG_BLOCK || Hash is related to a data block
|}

Other Data Type values are considered reserved for future implementations.

=== Block Headers ===

Block headers are sent in a headers packet in response to a getheaders message.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || Block version information, based upon the software version creating this block
|-
| 32 || prev_block || char[32] || The hash value of the previous block this particular block references
|-
| 32 || merkle_root || char[32] || The reference to a Merkle tree collection which is a hash of all transactions related to this block
|-
| 4 || timestamp || uint32_t || A timestamp recording when this block was created (Will overflow in 2106<ref>http://en.wikipedia.org/wiki/Unix_time#Notable.C2.A0events.C2.A0in.C2.A0Unix.C2.A0time</ref>)
|-
| 4 || bits || uint32_t || The calculated difficulty target being used for this block
|-
| 4 || nonce || uint32_t || The nonce used to generate this block… to allow variations of the header and compute different hashes
|-
| 1 || txn_count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of transaction entries, this value is always 0
|}

== Message types ==

=== version ===

When a node creates an outgoing connection, it will immediately [[Version Handshake|advertise]] its version. The remote node will respond with its version. No futher communication is possible until both peers have exchanged their version.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || int32_t || Identifies protocol version being used by the node
|-
| 8 || services || uint64_t || bitfield of features to be enabled for this connection
|-
| 8 || timestamp || int64_t || standard UNIX timestamp in seconds
|-
| 26 || addr_recv || net_addr || The network address of the node receiving this message
|-
|colspan="4"| version >= 106
|-
| 26 || addr_from || net_addr || The network address of the node emitting this message
|-
| 8 || nonce || uint64_t || Node random nonce, randomly generated every time a version packet is sent. This nonce is used to detect connections to self.
|-
| ? || user_agent || [[#Variable length string|var_str]] || [[BIP_0014|User Agent]] (0x00 if string is 0 bytes long)
|-
| 4 || start_height || int32_t || The last block received by the emitting node
|-
| 1 || relay || bool || Whether the remote peer should announce relayed transactions or not, see [[BIP 0037]], since version >= 70001
|}

A "verack" packet shall be sent if the version packet was accepted.

The following services are currently assigned:

{|class="wikitable"
! Value !! Name !! Description
|-
| 1 || NODE_NETWORK || This node can be asked for full blocks instead of just headers.
|}

Hexdump example of version message (OBSOLETE EXAMPLE. This example lacks a checksum and user-agent):
<pre>
0000 F9 BE B4 D9 76 65 72 73 69 6F 6E 00 00 00 00 00 ....version.....
0010 55 00 00 00 9C 7C 00 00 01 00 00 00 00 00 00 00 U....|..........
0020 E6 15 10 4D 00 00 00 00 01 00 00 00 00 00 00 00 ...M............
0030 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 ................
0040 20 8D 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 FF FF 0A 00 00 02 20 8D DD 9D 20 2C .......... ... ,
0060 3A B4 57 13 00 55 81 01 00 :.W..U...

Message header:
F9 BE B4 D9 - Main network magic bytes
76 65 72 73 69 6F 6E 00 00 00 00 00 - "version" command
55 00 00 00 - Payload is 85 bytes long
- No checksum in version message until 20 February 2012. See https://bitcointalk.org/index.php?topic=55852.0
Version message:
9C 7C 00 00 - 31900 (version 0.3.19)
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK services)
E6 15 10 4D 00 00 00 00 - Mon Dec 20 21:50:14 EST 2010
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 20 8D - Recipient address info - see Network Address
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 02 20 8D - Sender address info - see Network Address
DD 9D 20 2C 3A B4 57 13 - Node random unique ID
00 - "" sub-version string (string is 0 bytes long)
55 81 01 00 - Last block sending node has is block #98645
</pre>

And here's a modern (60002) protocol version client advertising itself to a local peer...

Newer protocol includes the checksum now, this is from a mainline (satoshi) client during
an outgoing connection to another local client, notice that it does not fill out the
address information at all when the source or destination is "unroutable".

<pre>

0000 f9 be b4 d9 76 65 72 73 69 6f 6e 00 00 00 00 00 ....version.....
0010 64 00 00 00 35 8d 49 32 62 ea 00 00 01 00 00 00 d...5.I2b.......
0020 00 00 00 00 11 b2 d0 50 00 00 00 00 01 00 00 00 .......P........
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ................
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 00 ................
0060 3b 2e b3 5d 8c e6 17 65 0f 2f 53 61 74 6f 73 68 ;..]...e./Satosh
0070 69 3a 30 2e 37 2e 32 2f c0 3e 03 00 i:0.7.2/.>..

Message Header:
F9 BE B4 D9 - Main network magic bytes
76 65 72 73 69 6F 6E 00 00 00 00 00 - "version" command
64 00 00 00 - Payload is 100 bytes long
3B 64 8D 5A - payload checksum

Version message:
62 EA 00 00 - 60002 (protocol version 60002)
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK services)
11 B2 D0 50 00 00 00 00 - Tue Dec 18 10:12:33 PST 2012
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 00 00 00 00 00 00 - Recipient address info - see Network Address
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 00 00 00 00 00 00 - Sender address info - see Network Address
3B 2E B3 5D 8C E6 17 65 - Node ID
0F 2F 53 61 74 6F 73 68 69 3A 30 2E 37 2E 32 2F - "/Satoshi:0.7.2/" sub-version string (string is 15 bytes long)
C0 3E 03 00 - Last block sending node has is block #212672
</pre>

=== verack ===

The ''verack'' message is sent in reply to ''version''. This message consists of only a [[#Message structure|message header]] with the command string "verack".

Hexdump of the verack message:

<pre>
0000 F9 BE B4 D9 76 65 72 61 63 6B 00 00 00 00 00 00 ....verack......
0010 00 00 00 00 5D F6 E0 E2 ........

Message header:
F9 BE B4 D9 - Main network magic bytes
76 65 72 61 63 6B 00 00 00 00 00 00 - "verack" command
00 00 00 00 - Payload is 0 bytes long
5D F6 E0 E2 - Checksum
</pre>

=== addr ===

Provide information on known nodes of the network. Non-advertised nodes should be forgotten after typically 3 hours

Payload:
{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 1+ || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of address entries (max: 1000)
|-
| 30x? || addr_list || (uint32_t + net_addr)[] || Address of other nodes on the network. version < 209 will only read the first one. The uint32_t is a timestamp (see note below).
|}

'''Note''': Starting version 31402, addresses are prefixed with a timestamp. If no timestamp is present, the addresses should not be relayed to other peers, unless it is indeed confirmed they are up.

Hexdump example of ''addr'' message:
<pre>
0000 F9 BE B4 D9 61 64 64 72 00 00 00 00 00 00 00 00 ....addr........
0010 1F 00 00 00 ED 52 39 9B 01 E2 15 10 4D 01 00 00 .....R9.....M...
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF ................
0030 FF 0A 00 00 01 20 8D ..... .

Message Header:
F9 BE B4 D9 - Main network magic bytes
61 64 64 72 00 00 00 00 00 00 00 00 - "addr"
1F 00 00 00 - payload is 31 bytes long
ED 52 39 9B - checksum of payload

Payload:
01 - 1 address in this message

Address:
E2 15 10 4D - Mon Dec 20 21:50:10 EST 2010 (only when version is >= 31402)
01 00 00 00 00 00 00 00 - 1 (NODE_NETWORK service - see version message)
00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 - IPv4: 10.0.0.1, IPv6: ::ffff:10.0.0.1 (IPv4-mapped IPv6 address)
20 8D - port 8333
</pre>

=== inv ===

Allows a node to advertise its knowledge of one or more objects. It can be received unsolicited, or in reply to ''getblocks''.

Payload (maximum payload length: 1.8 Megabytes or 50000 entries):

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of inventory entries
|-
| 36x? || inventory || [[Protocol specification#Inventory Vectors|inv_vect]][] || Inventory vectors
|}

=== getdata ===

getdata is used in response to inv, to retrieve the content of a specific object, and is usually sent after receiving an ''inv'' packet, after filtering known elements. It can be used to retrieve transactions, but only if they are in the memory pool or relay set - arbitrary access to transactions in the chain is not allowed to avoid having clients start to depend on nodes having full transaction indexes (which modern nodes do not).

Payload (maximum payload length: 1.8 Megabytes or 50000 entries):

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of inventory entries
|-
| 36x? || inventory || [[Protocol specification#Inventory Vectors|inv_vect]][] || Inventory vectors
|}

=== notfound ===

notfound is a response to a getdata, sent if any requested data items could not be relayed, for example, because the requested transaction was not in the memory pool or relay set.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of inventory entries
|-
| 36x? || inventory || [[Protocol specification#Inventory Vectors|inv_vect]][] || Inventory vectors
|}

=== getblocks ===

Return an ''inv'' packet containing the list of blocks starting right after the last known hash in the block locator object, up to hash_stop or 500 blocks, whichever comes first.

The locator hashes are processed by a node in the order as they appear in the message. If a block hash is found in the node's main chain, the list of its children is returned back via the ''inv'' message and the remaining locators are ignored, no matter if the requested limit was reached, or not.

To receive the next blocks hashes, one needs to issue getblocks again with a new block locator object. Keep in mind that some clients (specifically the Satoshi client) will gladly provide blocks which are invalid if the block locator object contains a hash on the invalid branch.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || the protocol version
|-
| 1+ || hash count || [[Protocol_specification#Variable_length_integer|var_int]] || number of block locator hash entries
|-
| 32+ || block locator hashes || char[32] || block locator object; newest back to genesis block (dense to start, but then sparse)
|-
| 32 || hash_stop || char[32] || hash of the last desired block; set to zero to get as many blocks as possible (500)
|}

To create the block locator hashes, keep pushing hashes until you go back to the genesis block. After pushing 10 hashes back, the step backwards doubles every loop:

<pre>
// From libbitcoin which is under AGPL
std::vector<size_t> block_locator_indices(int top_depth)
{
// Start at max_depth
std::vector<size_t> indices;
// Push last 10 indices first
size_t step = 1, start = 0;
for (int i = top_depth; i > 0; i -= step, ++start)
{
if (start >= 10)
step *= 2;
indices.push_back(i);
}
indices.push_back(0);
return indices;
}
</pre>

Note that it is allowed to send in fewer known hashes down to a minimum of just one hash. However, the purpose of the block locator object is to detect a wrong branch in the caller's main chain. If the peer detects that you are off the main chain, it will send in block hashes which are earlier than your last known block. So if you just send in your last known hash and it is off the main chain, the peer starts over at block #1.

=== getheaders ===

Return a ''headers'' packet containing the headers of blocks starting right after the last known hash in the block locator object, up to hash_stop or 2000 blocks, whichever comes first. To receive the next block headers, one needs to issue getheaders again with a new block locator object. The ''getheaders'' command is used by thin clients to quickly download the blockchain where the contents of the transactions would be irrelevant (because they are not ours). Keep in mind that some clients (specifically the Satoshi client) will gladly provide headers of blocks which are invalid if the block locator object contains a hash on the invalid branch.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || the protocol version
|-
| 1+ || hash count || [[Protocol_specification#Variable_length_integer|var_int]] || number of block locator hash entries
|-
| 32+ || block locator hashes || char[32] || block locator object; newest back to genesis block (dense to start, but then sparse)
|-
| 32 || hash_stop || char[32] || hash of the last desired block header; set to zero to get as many blocks as possible (2000)
|}

For the block locator object in this packet, the same rules apply as for the [[Protocol_specification#getblocks|getblocks]] packet.

=== tx ===

''tx'' describes a bitcoin transaction, in reply to ''getdata''

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || Transaction data format version
|-
| 1+ || tx_in count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of Transaction inputs
|-
| 41+ || tx_in || tx_in[] || A list of 1 or more transaction inputs or sources for coins
|-
| 1+ || tx_out count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of Transaction outputs
|-
| 9+ || tx_out || tx_out[] || A list of 1 or more transaction outputs or destinations for coins
|-
| 4 || lock_time || uint32_t || The block number or timestamp at which this transaction is locked:
{|class="wikitable"
! Value !! Description
|-
| 0 || Always locked
|-
| < 500000000 || Block number at which this transaction is locked
|-
| >= 500000000 || UNIX timestamp at which this transaction is locked
|}
If all TxIn inputs have final (0xffffffff) sequence numbers then lock_time is irrelevant. Otherwise, the transaction may not be added to a block until after lock_time (see [[NLockTime]]).

|}

TxIn consists of the following fields:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 36 || previous_output || outpoint || The previous output transaction reference, as an OutPoint structure
|-
| 1+ || script length || [[Protocol_specification#Variable_length_integer|var_int]] || The length of the signature script
|-
| ? || signature script || uchar[] || Computational Script for confirming transaction authorization
|-
| 4 || [http://bitcoin.stackexchange.com/q/2025/323 sequence] || uint32_t || Transaction version as defined by the sender. Intended for "replacement" of transactions when information is updated before inclusion into a block.
|}

The OutPoint structure consists of the following fields:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 32 || hash || char[32] || The hash of the referenced transaction.
|-
| 4 || index || uint32_t || The index of the specific output in the transaction. The first output is 0, etc.
|}

The Script structure consists of a series of pieces of information and operations related to the value of the transaction.

(Structure to be expanded in the future… see script.h and script.cpp and [[Script]] for more information)

The TxOut structure consists of the following fields:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 8 || value || int64_t || Transaction Value
|-
| 1+ || pk_script length || [[Protocol_specification#Variable_length_integer|var_int]] || Length of the pk_script
|-
| ? || pk_script || uchar[] || Usually contains the public key as a Bitcoin script setting up conditions to claim this output.
|}

Example ''tx'' message:
<pre>
000000 F9 BE B4 D9 74 78 00 00 00 00 00 00 00 00 00 00 ....tx..........
000010 02 01 00 00 E2 93 CD BE 01 00 00 00 01 6D BD DB .............m..
000020 08 5B 1D 8A F7 51 84 F0 BC 01 FA D5 8D 12 66 E9 .[...Q........f.
000030 B6 3B 50 88 19 90 E4 B4 0D 6A EE 36 29 00 00 00 .;P......j.6)...
000040 00 8B 48 30 45 02 21 00 F3 58 1E 19 72 AE 8A C7 ..H0E.!..X..r...
000050 C7 36 7A 7A 25 3B C1 13 52 23 AD B9 A4 68 BB 3A .6zz%;..R#...h.:
000060 59 23 3F 45 BC 57 83 80 02 20 59 AF 01 CA 17 D0 Y#?E.W... Y.....
000070 0E 41 83 7A 1D 58 E9 7A A3 1B AE 58 4E DE C2 8D .A.z.X.z...XN...
000080 35 BD 96 92 36 90 91 3B AE 9A 01 41 04 9C 02 BF 5...6..;...A....
000090 C9 7E F2 36 CE 6D 8F E5 D9 40 13 C7 21 E9 15 98 .~.6.m...@..!...
0000A0 2A CD 2B 12 B6 5D 9B 7D 59 E2 0A 84 20 05 F8 FC *.+..].}Y... ...
0000B0 4E 02 53 2E 87 3D 37 B9 6F 09 D6 D4 51 1A DA 8F N.S..=7.o...Q...
0000C0 14 04 2F 46 61 4A 4C 70 C0 F1 4B EF F5 FF FF FF ../FaJLp..K.....
0000D0 FF 02 40 4B 4C 00 00 00 00 00 19 76 A9 14 1A A0 ..@KL......v....
0000E0 CD 1C BE A6 E7 45 8A 7A BA D5 12 A9 D9 EA 1A FB .....E.z........
0000F0 22 5E 88 AC 80 FA E9 C7 00 00 00 00 19 76 A9 14 "^...........v..
000100 0E AB 5B EA 43 6A 04 84 CF AB 12 48 5E FD A0 B7 ..[.Cj.....H^...
000110 8B 4E CC 52 88 AC 00 00 00 00 .N.R......

Message header:
F9 BE B4 D9 - main network magic bytes
74 78 00 00 00 00 00 00 00 00 00 00 - "tx" command
02 01 00 00 - payload is 258 bytes long
E2 93 CD BE - checksum of payload

Transaction:
01 00 00 00 - version

Inputs:
01 - number of transaction inputs

Input 1:
6D BD DB 08 5B 1D 8A F7 51 84 F0 BC 01 FA D5 8D - previous output (outpoint)
12 66 E9 B6 3B 50 88 19 90 E4 B4 0D 6A EE 36 29
00 00 00 00

8B - script is 139 bytes long

48 30 45 02 21 00 F3 58 1E 19 72 AE 8A C7 C7 36 - signature script (scriptSig)
7A 7A 25 3B C1 13 52 23 AD B9 A4 68 BB 3A 59 23
3F 45 BC 57 83 80 02 20 59 AF 01 CA 17 D0 0E 41
83 7A 1D 58 E9 7A A3 1B AE 58 4E DE C2 8D 35 BD
96 92 36 90 91 3B AE 9A 01 41 04 9C 02 BF C9 7E
F2 36 CE 6D 8F E5 D9 40 13 C7 21 E9 15 98 2A CD
2B 12 B6 5D 9B 7D 59 E2 0A 84 20 05 F8 FC 4E 02
53 2E 87 3D 37 B9 6F 09 D6 D4 51 1A DA 8F 14 04
2F 46 61 4A 4C 70 C0 F1 4B EF F5

FF FF FF FF - sequence

Outputs:
02 - 2 Output Transactions

Output 1:
40 4B 4C 00 00 00 00 00 - 0.05 BTC (5000000)
19 - pk_script is 25 bytes long

76 A9 14 1A A0 CD 1C BE A6 E7 45 8A 7A BA D5 12 - pk_script
A9 D9 EA 1A FB 22 5E 88 AC

Output 2:
80 FA E9 C7 00 00 00 00 - 33.54 BTC (3354000000)
19 - pk_script is 25 bytes long

76 A9 14 0E AB 5B EA 43 6A 04 84 CF AB 12 48 5E - pk_script
FD A0 B7 8B 4E CC 52 88 AC

Locktime:
00 00 00 00 - lock time
</pre>

=== block ===

The '''block''' message is sent in response to a getdata message which requests transaction information from a block hash.

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || version || uint32_t || Block version information, based upon the software version creating this block
|-
| 32 || prev_block || char[32] || The hash value of the previous block this particular block references
|-
| 32 || merkle_root || char[32] || The reference to a Merkle tree collection which is a hash of all transactions related to this block
|-
| 4 || timestamp || uint32_t || A unix timestamp recording when this block was created (Currently limited to dates before the year 2106!)
|-
| 4 || bits || uint32_t || The calculated [[Difficulty|difficulty target]] being used for this block
|-
| 4 || nonce || uint32_t || The nonce used to generate this block… to allow variations of the header and compute different hashes
|-
| ? || txn_count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of transaction entries
|-
| ? || txns || tx[] || Block transactions, in format of "tx" command
|}

The SHA256 hash that identifies each block (and which must have a run of 0 bits) is calculated from the first 6 fields of this structure (version, prev_block, merkle_root, timestamp, bits, nonce, and standard SHA256 padding, making two 64-byte chunks in all) and ''not'' from the complete block. To calculate the hash, only two chunks need to be processed by the SHA256 algorithm. Since the ''nonce'' field is in the second chunk, the first chunk stays constant during mining and therefore only the second chunk needs to be processed. However, a Bitcoin hash is the hash of the hash, so two SHA256 rounds are needed for each mining iteration.
See [[Block hashing algorithm]] for details and an example.

=== headers ===

The ''headers'' packet returns block headers in response to a ''getheaders'' packet.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || count || [[Protocol_specification#Variable_length_integer|var_int]] || Number of block headers
|-
| 81x? || headers || [[Protocol_specification#Block_Headers|block_header]][] || [[Protocol_specification#Block_Headers|Block headers]]
|}

Note that the block headers in this packet include a transaction count (a var_int, so there can be more than 81 bytes per header) as opposed to the block headers which are sent to miners.

=== getaddr ===

The getaddr message sends a request to a node asking for information about known active peers to help with finding potential nodes in the network. The response to receiving this message is to transmit one or more addr messages with one or more peers from a database of known active peers. The typical presumption is that a node is likely to be active if it has been sending a message within the last three hours.

No additional data is transmitted with this message.

=== mempool ===

The mempool message sends a request to a node asking for information about transactions it has verified but which have not yet confirmed. The response to receiving this message is an inv message containing the transaction hashes for all the transactions in the node's mempool.

No additional data is transmitted with this message.

It is specified in [[BIP_0035|BIP 35]]. Since [[BIP_0037|BIP 37]], only transactions matching the filter are replied.

=== checkorder ===

This message was used for [[IP Transactions]]. As IP transactions have been deprecated, it is no longer used.

=== submitorder ===

This message was used for [[IP Transactions]]. As IP transactions have been deprecated, it is no longer used.

=== reply ===

This message was used for [[IP Transactions]]. As IP transactions have been deprecated, it is no longer used.

=== ping ===

The ''ping'' message is sent primarily to confirm that the TCP/IP connection is still valid. An error in transmission is presumed to be a closed connection and the address is removed as a current peer.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 8 || nonce || uint64_t || random nonce
|}

=== pong ===

The ''pong'' message is sent in response to a ''ping'' message. In modern protocol versions, a ''pong'' response is generated using a nonce included in the ping.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 8 || nonce || uint64_t || nonce from ping
|}

=== filterload, filteradd, filterclear, merkleblock ===

These messages are related to Bloom filtering of connections and are defined in [[BIP 0037]].

=== alert ===

An '''alert''' is sent between nodes to send a general notification message throughout the network. If the alert can be confirmed with the signature as having come from the the core development group of the Bitcoin software, the message is suggested to be displayed for end-users. Attempts to perform transactions, particularly automated transactions through the client, are suggested to be halted. The text in the Message string should be relayed to log files and any user interfaces.

Alert format:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| ? || payload || var_str || Serialized alert payload
|-
| ? || signature || var_str || An ECDSA signature of the message
|}

The developers of Satoshi's client use this public key for signing alerts:
04fc9702847840aaf195de8442ebecedf5b095cdbb9bc716bda9110971b28a49e0ead8564ff0db22209e0374782c093bb899692d524e9d6a6956e7c5ecbcd68284
(hash) 1AGRxqDa5WjUKBwHB9XYEjmkv1ucoUUy1s

The payload is serialized into a var_str to ensure that versions using incompatible alert formats can still relay alerts among one another. The current alert payload format is:
{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 4 || Version || int32_t || Alert format version
|-
| 8 || RelayUntil || int64_t || The timestamp beyond which nodes should stop relaying this alert
|-
| 8 || Expiration || int64_t || The timestamp beyond which this alert is no longer in effect and should be ignored
|-
| 4 || ID || int32_t || A unique ID number for this alert
|-
| 4 || Cancel || int32_t || All alerts with an ID number less than or equal to this number should be canceled: deleted and not accepted in the future
|-
| ? || setCancel || set<int> || All alert IDs contained in this set should be canceled as above
|-
| 4 || MinVer || int32_t || This alert only applies to versions greater than or equal to this version. Other versions should still relay it.
|-
| 4 || MaxVer || int32_t || This alert only applies to versions less than or equal to this version. Other versions should still relay it.
|-
| ? || setSubVer || set<string> || If this set contains any elements, then only nodes that have their subVer contained in this set are affected by the alert. Other versions should still relay it.
|-
| 4 || Priority || int32_t || Relative priority compared to other alerts
|-
| ? || Comment || string || A comment on the alert that is not displayed
|-
| ? || StatusBar || string || The alert message that is displayed to the user
|-
| ? || Reserved || string || Reserved
|}

Sample alert (no message header):
73010000003766404f00000000b305434f00000000f2030000f1030000001027000048ee0000
0064000000004653656520626974636f696e2e6f72672f666562323020696620796f75206861
76652074726f75626c6520636f6e6e656374696e672061667465722032302046656272756172
79004730450221008389df45f0703f39ec8c1cc42c13810ffcae14995bb648340219e353b63b
53eb022009ec65e1c1aaeec1fd334c6b684bde2b3f573060d5b70c3a46723326e4e8a4f1

Version: 1
RelayUntil: 1329620535
Expiration: 1329792435
ID: 1010
Cancel: 1009
setCancel: <empty>
MinVer: 10000
MaxVer: 61000
setSubVer: <empty>
Priority: 100
Comment: <empty>
StatusBar: "See bitcoin.org/feb20 if you have trouble connecting after 20 February"
Reserved: <empty>

== Scripting ==

See [[script]].

== Wireshark dissector ==
A [[Bitcoin Dissector|dissector]] for wireshark is being developed.

==See Also==

* [[Network]]
* [[Protocol rules]]
* [[Hardfork Wishlist]]

==References==
<references />

[[zh-cn:协议说明]]
[[Category:Technical]]
[[Category:Developer]]

Category:Articles using content from the old wiki

2014-03-28T05:07:46Z

Imsaguy:

__HIDDENCAT__
{{delete}}
Articles are put into this category if they use the [[:Template:fromold]] template.

Template:Delete

2014-03-28T05:05:46Z

Imsaguy: Add link to category for quicker naviation.

<div style="width:80%;background-color:#ff9090;">
<center>
A request has been made to delete this page.
See discussion on the talk page.
Reason: {{{1}}}
</center>
</div>
<noinclude>[[:category:deletion_requests|View pages marked for deletion]]</noinclude>

Purecoin

2014-03-28T04:28:14Z

Imsaguy: Add stub.

{{stub}}
Purecoin is a Haskell full-node implementation, by [http://r6.ca/ Russell O'Connor], available [https://github.com/laanwj/Purecoin on github] (mirrored from darcs).

[[Category:Nodes]]

Caesure

2014-03-28T04:28:03Z

Imsaguy: Add stub.

{{stub}}
Caesure is a Python implementation aiming for full-node features, by [http://www.nightmare.com/~rushing/ Sam Rushing], available [https://github.com/samrushing/caesure on github].

[[Category:Nodes]]

Haskoin

2014-03-28T04:27:51Z

Imsaguy: Add stub.

{{stub}}
Haskoin is a Haskell implementation aiming for full-node features, by Philippe Laprade, available [https://github.com/plaprade/haskoin on github].

[[Category:Nodes]]

Template:Main Page interwikis

2014-03-27T23:27:23Z

Imsaguy:

<includeonly>[[ar:]] [[id:]] [[ms:]] [[bg:]] [[ca:]] [[cs:]] [[da:]] [[de:]] [[et:]] [[el:]] [[es:]] [[eo:]] [[eu:]] [[fa:]] [[fr:]] [[gl:]] [[ko:]] [[he:]] [[hr:]] [[it:]] [[ka:]] [[lv:]] [[lt:]] [[hu:]] [[nl:]] [[ja:]] [[no:]] [[nn:]] [[pl:]] [[pt:]] [[ro:]] [[ru:]] [[sk:]] [[sl:]] [[sr:]] [[sh:]] [[fi:]] [[sv:]] [[th:]] [[vi:]] [[tr:]] [[uk:]] [[zh-cn:]]</includeonly><noinclude>
This page has a list of all languages available on the bitcoin wiki. If any show as red, there's a problem with that language's main page.
</noinclude>

Main Page

2014-03-27T23:26:59Z

Imsaguy:

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div>
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:CryptoPayment]]</div>
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''
|}

| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span>
| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[[Forums]]</span>
| style="width:13%; font-size:120%; padding-right: 40px;" |
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.

Languages needing translation work: {{Main Page interwikis}}</noinclude>__NOTOC____NOEDITSECTION__

Template:Main Page interwikis

2014-03-27T23:26:09Z

Imsaguy:

<includeonly>[[simple:]] [[ar:]] [[id:]] [[ms:]] [[bg:]] [[ca:]] [[cs:]] [[da:]] [[de:]] [[et:]] [[el:]] [[es:]] [[eo:]] [[eu:]] [[fa:]] [[fr:]] [[gl:]] [[ko:]] [[he:]] [[hr:]] [[it:]] [[ka:]] [[lv:]] [[lt:]] [[hu:]] [[nl:]] [[ja:]] [[no:]] [[nn:]] [[pl:]] [[pt:]] [[ro:]] [[ru:]] [[sk:]] [[sl:]] [[sr:]] [[sh:]] [[fi:]] [[sv:]] [[th:]] [[vi:]] [[tr:]] [[uk:]] [[zh-cn:]]</includeonly><noinclude>
This page has a list of all languages available on the bitcoin wiki. If any show as red, there's a problem with that language's main page.
</noinclude>

Template:Main Page interwikis

2014-03-27T23:19:23Z

Imsaguy:

Template:Main Page interwikis

2014-03-27T23:18:03Z

Imsaguy:

[[ar:]] [[id:]] [[ms:]] [[bg:]] [[ca:]] [[cs:]] [[da:]] [[de:]] [[et:]] [[el:]] [[es:]] [[eo:]] [[eu:]] [[fa:]] [[fr:]] [[gl:]] [[ko:]] [[he:]] [[hr:]] [[it:]] [[ka:]] [[lv:]] [[lt:]] [[hu:]] [[nl:]] [[ja:]] [[no:]] [[nn:]] [[pl:]] [[pt:]] [[ro:]] [[ru:]] [[sk:]] [[sl:]] [[sr:]] [[sh:]] [[fi:]] [[sv:]] [[th:]] [[vi:]] [[tr:]] [[uk:]] [[zh-cn:首页]]

Template:Main Page interwikis

2014-03-27T23:16:47Z

Imsaguy:

Template:Main Page interwikis

2014-03-27T23:13:41Z

Imsaguy:

Main Page

2014-03-27T23:09:21Z

Imsaguy: Clarify why all the bad links.

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div>
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:CryptoPayment]]</div>
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''
|}

| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span>
| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[[Forums]]</span>
| style="width:13%; font-size:120%; padding-right: 40px;" |
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.

Languages needing translation work: <noinclude>{{Main Page interwikis}}</noinclude>__NOTOC____NOEDITSECTION__

Main Page

2014-03-27T23:07:23Z

Imsaguy: Move languages to template

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div>
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:CryptoPayment]]</div>
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''
|}

| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span>
| style="width:13%; font-size:120%;" |
* <span class="plainlinks">[[Forums]]</span>
| style="width:13%; font-size:120%; padding-right: 40px;" |
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.

<noinclude>{{Main Page interwikis}}</noinclude>__NOTOC____NOEDITSECTION__