Bitcoin Wiki - User contributions [en]

P2Pool

2018-01-02T13:06:05Z

Lclc: Remove README text (more up to date version on Github)

{{Infobox company
|name=P2Pool
|trading_name=P2Pool
|industry=[[Mining pool]]
|foundation=July 17, 2011
|hashrate=1.6 Phash/s
|website= http://p2pool.in
}}
[[Image:P2pool_chain.png‎|thumb|350px|right|Visualization of the P2Pool share chain]]

'''P2Pool''' is a decentralized [[Bitcoin]] [[Bitcoin Pool|mining pool]] that works by creating a peer-to-peer network of miner nodes.

<blockquote>P2Pool creates a new block chain in which the difficulty is adjusted so a new block is found every 30 seconds. The blocks that get into the P2Pool block chain (called the "share chain") are the same blocks that would get into the Bitcoin block chain, only they have a lower difficulty target. Whenever a peer announces a new share found (new block in the P2Pool block chain), it is received by the other peers, and the other peers verify that this block contains payouts for all the previous miners who found a share (and announced it) that made it into the P2Pool share chain. This continues until some peer finds a block that has a difficulty that meets the Bitcoin network's difficulty target. This peer announces this block to the Bitcoin network and miners who have submitted shares for this block are paid in the generation transaction, proportionally to how many shares they have found in the last while. - Unknown author</blockquote>

Decentralized payout pooling solves the problem of centralized mining pools degrading the decentralization of Bitcoin and avoids the risk of hard to detect theft by pool operators.

Miners are configured to connect to a P2Pool node that can be run locally, alongside the miner. P2Pool users must run a full Bitcoin node which serves the purpose of independently validating transactions and the Bitcoin blockchain. P2Pool also supports merged mining and several alternative blockchains.

P2Pool nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself, which can also result in a share if it meets P2Pool's difficulty.

Because of the importance of strengthening Bitcoin's decentralization, some Bitcoin supporters donate to P2Pool miners, resulting in average returns above 100% of the expected reward.
However, it should be noted that there are other pools (such as [[BitPenny]] and [[Eligius]]) which can provide this same level of decentralization.

== Overview ==

P2Pool shares form a "sharechain" with each share referencing the previous share's hash. Each share contains a standard Bitcoin block header, some P2Pool-specific data that is used to compute the generation transaction (total subsidy, payout script of this share, a nonce, the previous share's hash, and the current target for shares), and a Merkle branch linking that generation transaction to the block header's Merkle hash.

The chain continuously regulates its target to keep generation around one share every thirty seconds, just as Bitcoin regulates it to generate one block every ten minutes.
This means that finding shares becomes more difficult (resulting in higher variance) the more people mine on P2Pool, though large miners have the option to raise their difficulty, and so reduce the impact of their mining on P2Pool's minimum difficulty.

Unlike Bitcoin, nodes do not know the entire chain - instead they only hold the last 8640 shares (the last 3 day's worth). In order to prevent an attacker from working on a chain in secret and then releasing it, overriding the existing chain, chains are judged by how much work they have since a point in the past. To ascertain that the work has been done since that point, nodes look at the Bitcoin blocks that the shares reference, establishing a provable timestamp. (If a share points to a block, it was definitely made after that block was made.)

=== Payout logic ===

Each share contains a generation transaction that pays to the previous ''n'' shares, where ''n'' is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= 24 hours of shares), whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.

The block reward (currently 12.5BTC) and the transaction fees are combined and apportioned according to these rules:

A subsidy of 0.5% is sent to the node that solved the block in order to discourage not sharing solutions that qualify as a block. (A miner with the aim to harm others could withhold the block, thereby preventing anybody from getting paid. He can NOT redirect the payout to himself.) The remaining 99.5% is distributed evenly to miners based on work done recently.

In the event that a share qualifies as a block, this generation transaction is exposed to the Bitcoin network and takes effect, transferring each node its payout.

=== Stales ===

On P2Pool stales refer to shares which can't make it into the sharechain. Because the sharechain is 20 times faster than the Bitcoin chain many stales are common and expected. However, because the payout is [[Comparison_of_mining_pools|PPLNS]] only your stale rate relative to other nodes is relevant; the absolute rate is not.

There are two reported kinds of stales in P2Pool: "DEAD ON ARRIVAL" shares and orphan shares. Dead shares were too old by the time they arrived at your local P2Pool. Very high dead rates can indicate miner misconfiguration. Orphan shares are shares which were not extended by the rest of the P2Pool network, because some other miner's share was accepted first. Very high orphan rates may indicate network connectivity problems.

The P2Pool console output shows your relative stale rate compared to other P2Pool miners in the 'Own efficiency' column:
<pre>
2012-01-07 20:57:51.797420 Pool stales: 13% Own: 13±2% Own efficiency: 100±2%
</pre>

When you first start P2Pool claimed efficiency will be low and the error bounds on this estimate will be large, but as it runs the numbers will converge to their correct values.

If your efficiency is unusually low, make sure your network connection isn't overloaded, that your miners support long polling and are not set to work for excessive amounts of time, and that your bitcoind has multiple connections.

== Joining the pool ==

Follow these steps to join the pool:

* Run Bitcoin with the RPC interface enabled: edit bitcoin.conf to include:
rpcuser=USER
rpcpassword=LONG_RANDOM_SECRET_VALUE
server=1
**'''Replace LONG_RANDOM_SECRET_VALUE with something long and random like the output of smashing your keyboard for a bit like fju4M78yAj3ds39pak92raK'''. You don't need to be able to remember it. If your RPC port becomes exposed to the internet a thief could steal your bitcoin if they could guess it, or use a brute force attack in order to find it.
** Bitcoin 0.8.5 or later is required
** It's important that your Bitcoin client be fully synchronized before starting. It's also better if you have the Bitcoin port forwarded
* Download p2pool:
** Windows binary: See http://forum.bitcoin.org/index.php?topic=18313.0
** Source download: https://github.com/forrestv/p2pool/tags
** git: git clone git://github.com/forrestv/p2pool.git
* Run p2pool: (See below for additional options.)
** Windows py2exe: run_p2pool.exe
** Source: python run_p2pool.py
* Run a miner daemon with long polling connecting to 127.0.0.1 (or the IP of the host running p2pool if it isn't on the same computer as the miner) on port 9332 with any username and password
** bfgminer -O u:p -o http://127.0.0.1:9332/ --submit-stale
* Subscribe to the [https://groups.google.com/forum/#!forum/p2pool-notifications P2Pool notifications] mailing list for urgent pool status updates

Dependencies if running from source:
* Python 2.6 or higher (but not 3.x)
* python-argparse
* Twisted (Ubuntu package python-twisted)

=== Frequently Asked Questions ===

'''Q:''' "Why does my miner report so many longpoll events when mining on p2pool? - P4Man" 
'''A:''' "Once every ~30 seconds is normal. That is how often p2pool shares are generated (as opposed to ~10 min for bitcoin blocks) - cabin"

'''Q:''' "Do the 'orphan' and 'dead' shares in P2Pool's status display hurt me?" 
'''A:''' They shouldn't - It's normal for some fraction of everyone's shares to end up orphaned or dead. Because payouts are calculated by counting how many shares you have relative to others, everyone with normal configurations is equally "hurt" by this. However, if you have a large proportion of stales, your payout will be hurt. You can see how well you're doing by looking at P2Pool's "Efficiency" (ex: ''Efficiency: ~110.6% (40-111%)''). If 100% doesn't lie within the [http://en.wikipedia.org/wiki/Confidence_interval confidence interval] at the end, something is probably wrong (with 95% confidence).

'''Q:''' "What do I do if my efficiency is low?" 
'''A:''' Make sure the computers you're running P2Pool and the miner on have enough memory and CPU time. If you have a lot of dead shares or the "Local dead on arrival" number is higher than a few percent, that means that something is wrong with your miner. Check to make sure that it is one of the working versions in the ''Miners'' section on this page. Lower the intensity or raise the FPS of your miner. If you have a lot of orphan shares, something is wrong with P2Pool's P2P connection. Decrease the load on your internet connection or enable QoS (Quality of Service) on your router.

'''Q:''' What is PPLNS? 
'''A:''' Pay-Per-Last-N-Shares is a payout method that is completely resistant to pool hoppers.

'''Q:''' Why am I not getting very many shares?! 
'''A:''' The P2Pool difficulty is hundreds of times higher than on other pools. It can take time to get a share. P2Pool displays an estimate of how long you have to wait in the console output.

'''Q:''' Why does my miner say it has found a lot of shares but p2pool say I have only found a few?! 
'''A:''' The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly

'''Q:''' Why am I getting so many rejects? 
'''A:''' You're using an incompatible miner. See the miners section here, increase your FPS on the miner, decrease the intensity, upgrade your miner, or try a different miner.

'''Q:''' What stops the pool operator or the block finder from stealing a block? 
'''A:''' A block solution is only worth anything because its hash matches Bitcoin's target. Altering anything within the block will change its hash and make it worthless. If you are concerned about the pool operator stealing a block, you should try to inspect the source code of each new version.

'''Q:''' Why does it say "Generated?" I want to spend my coins now! 
'''A:''' P2Pool includes payouts in generation transactions, which must mature (taking 120 blocks or 20 hours) before they can be spent. The reason for this is that a block could be orphaned, which would make its payout invalid and could reverse transactions.

'''Q:''' Do I get paid transaction fees? 
'''A:''' Yes. They are split among P2Pool miners.

'''Q:''' What are these payments I'm getting that aren't generated? 
'''A:''' These are subsidies that people who support the idea of P2Pool send to miners.

'''Q:''' Cool Subsidies sound like an awesome idea! How do I send some BTC to these awesome miners? 
'''A:''' See end of this page.

'''Q:''' Do I really need the WHOLE blockchain? 
'''A:''' Yes. Your node needs to be able to independently make decisions about what transactions to mine.

'''Q:''' How do merged mining payments work? 
'''A:''' Merged mining is handled entirely by namecoind, so you're solo mining and payouts will go into namecoind's wallet.

=== Miners ===

This is all for the latest p2pool version, as it includes several new workarounds.

With all miners, using a HIGH FPS target (100?) or a LOW intensity (8 for bfgminer?) helps a lot with reducing stales.

* bfgminer, cgminer, and ufasoft work perfectly without any extra options.
* DiabloMiner works fine after commit 3b731b9.
* Phoenix works fine after commit a658ef2.
* Poclbm works fine after commit 5e994e7.

P2Pool uses higher difficulty shares than most centralized pools, so you'll see fewer shares reported. This is normal and doesn't reduce your payments. It's also normal to see longpoll messages once per every ten seconds on average.

====Tips to configure bfgminer to reduce stale/doa:====
* "gpu-threads" : "1", (2 by default)
* "queue" : "0", (1 by default)

Because of fast longpooling in p2pool it is better not NOT fetch work ahead.

On non-dedicated machines intensity=3 allows normal usage of PC, set it to 7 or more to get full hashrate.

On most cards best is diablo and phatk kernel, looks like poclbm kernel have unstable rate.

=== Useful features ===

* If upgrading P2Pool or changing its configuration, you can start another instance of P2Pool in parallel with the first. It will start normally, but realize that the worker and P2P listening ports are busy and keep trying to bind to them in the background. Thus, you can do almost-completely-seamless upgrades of P2Pool.
* If you run multiple P2Pool nodes or have trusted friends that run P2Pool, you can use ''-n'' to establish a constant extra P2P connection to them.
* You can make P2Pool use a configuration file by running run_p2pool.py @FILENAME, with FILENAME being the path to a file containing the command-line arguments (newlines are ignored) Example:
<pre>
--net bitcoin
-n 1.2.3.4
</pre>
* Setting the username of your miner connecting to P2Pool to a Bitcoin address will make it mine to that address instead of the one requested from bitcoind or set by -a
* Appending "/1000" to a miner's username will increase the difficulty of producing a P2Pool share to at most 1000. This is useful to large miners because doing this can make it easier for small miners while minimally impacting the large miners themselves. See [https://bitcointalk.org/index.php?topic=18313.msg816322#msg816322 recommended values].
** Appending "+1" (for example) after that will make P2Pool always give your miners work with a difficulty of 1

=== Web interface ===

Lots of data and useful tools are available at http://127.0.0.1:9332/something:
* /static/ - Lots of information from shares to graphs to payouts.
* /rate
* /users
* /fee
* /current_payouts
* /patron_sendmany - Gives sendmany outputs for fair donations to P2Pool
* /global_stats
* /local_stats
* /peer_addresses
* /payout_addr
* /recent_blocks
* /uptime
* /web/log - Some different stats collected over the last day

=== Option Reference ===
<pre>
usage: run_p2pool.py [-h] [--version] [--net {bitcoin,litecoin}] [--testnet]
[--debug] [-a ADDRESS] [--datadir DATADIR]
[--logfile LOGFILE] [--merged MERGED_URLS]
[--give-author DONATION_PERCENTAGE] [--iocp]
[--irc-announce] [--no-bugreport] [--p2pool-port PORT]
[-n ADDR[:PORT]] [--disable-upnp] [--max-conns CONNS]
[-w PORT or ADDR:PORT] [-f FEE_PERCENTAGE]
[--bitcoind-address BITCOIND_ADDRESS]
[--bitcoind-rpc-port BITCOIND_RPC_PORT]
[--bitcoind-p2p-port BITCOIND_P2P_PORT]
[BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

p2pool (version 0.11.1-8-ged9359d)

optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
--net {bitcoin,litecoin}
use specified network (default: bitcoin)
--testnet use the network's testnet
--debug enable debugging mode
-a ADDRESS, --address ADDRESS
generate payouts to this address (default: <address
requested from bitcoind>)
--datadir DATADIR store data in this directory (default: <directory
run_p2pool.py is in>/data)
--logfile LOGFILE log to this file (default: data/<NET>/log)
--merged MERGED_URLS call getauxblock on this url to get work for merged
mining (example:
http://ncuser:ncpass@127.0.0.1:10332/)
--give-author DONATION_PERCENTAGE
donate this percentage of work towards the development
of p2pool (default: 0.5)
--iocp use Windows IOCP API in order to avoid errors due to
large number of sockets being open
--irc-announce announce any blocks found on
irc://irc.freenode.net/#p2pool
--no-bugreport disable submitting caught exceptions to the author
--disable-upnp don't attempt to use UPnP to forward p2pool's P2P port
from the Internet to this computer

p2pool interface:
--p2pool-port PORT use port PORT to listen for connections (forward this
port from your router!) (default: bitcoin:9333,
litecoin:9338)
-n ADDR[:PORT], --p2pool-node ADDR[:PORT]
connect to existing p2pool node at ADDR listening on
port PORT (defaults to default p2pool P2P port) in
addition to builtin addresses
--max-conns CONNS maximum incoming connections (default: 40)

worker interface:
-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
listen on PORT on interface with ADDR for RPC
connections from miners (default: all interfaces,
bitcoin:9332, litecoin:9327)
-f FEE_PERCENTAGE, --fee FEE_PERCENTAGE
charge workers mining to their own bitcoin address (by
setting their miner's username to a bitcoin address)
this percentage fee to mine on your p2pool instance.
Amount displayed at http://127.0.0.1:WORKER_PORT/fee
(default: 0)

bitcoind interface:
--bitcoind-address BITCOIND_ADDRESS
connect to this address (default: 127.0.0.1)
--bitcoind-rpc-port BITCOIND_RPC_PORT
connect to JSON-RPC interface at this port (default:
bitcoin:8332, litecoin:9332 <read from bitcoin.conf if
password not provided>)
--bitcoind-p2p-port BITCOIND_P2P_PORT
connect to P2P interface at this port (default:
bitcoin:8333, litecoin:9333 <read from bitcoin.conf if
password not provided>)
BITCOIND_RPCUSERPASS bitcoind RPC interface username, then password, space-
separated (only one being provided will cause the
username to default to being empty, and none will
cause P2Pool to read them from bitcoin.conf)
</pre>

== Interoperability table ==
P2pool works fine with most hardware. This lists some of the hardware confirmed to work and any special configuration required.

* ASICminer blade 10GH/s (Requires adding +1 to username or proxy)
* Avalon 110nm 60-110 GH/s (All batches)
* Avalon based 55nm 200 GH/s (specific makers?)
* Avalon prototype 55nm 120GH/s (~ 20 exist)
* Icarus FPGA
* Bitfury strikes back H-card and M-card ([https://bitcointalk.org/index.php?topic=18313.msg4424081#msg4424081 instructions])
* Bitmain Antminer S1 180GH/s ([https://github.com/AntMiner/AntGen1/tree/master/firmware Requires 20131226 firmware.])
* Bitmain Antminer S3 440GH/s
* BFL SC Jalapeno, SC Single 30, 50, & 60 GH/s
* Spondoolies Tech SP 10
* Spondoolies Tech SP 30

(Various GPU and most FPGAs other than BFL single FPGAs work fine too)

This is a list of hardware with known issues that should not be used on p2pool.

* Cointerra Terraminer IV (10-20% hash rate loss when mining on p2pool)
* Btimain Antminer S2 (10-20% hash rate loss when mining on p2pool, the S1 & S3 both work well on p2pool)

== Protocol description ==

P2Pool's protocol mirrors Bitcoin's P2P protocol in many ways. It uses the same framing (prefix, command, length, checksum, payload) and similar commands:

* '''version''' - sent to establish a connection - contains (''version'', ''services'', ''addr_to'', ''addr_from'', ''nonce'', ''sub_version'', ''mode'', ''best_share_hash'')
* '''setmode''' - sent to update the ''mode'' sent in the '''version''' message - contains (''mode'')
* '''ping''' - sent to keep connection alive - contains ()
* '''addrme''' - request that the receiving node send out an addr for the sending node - contains (''port'')
* '''addrs''' - broadcast list of nodes' addresses - contains (''addrs'')
* '''getaddrs''' - request that the receiving node send ''count'' addrs - contains (''count'')
* '''getshares''' - request that the receiving node send the shares referenced by ''hashes'' and ''parents'' of their parents, stopping at any share referenced by ''stops'' - contains (''hashes'', ''parents'', ''stops'')
* '''shares''' - broadcast message of the contents of shares - contains (''shares'')

==History==

This project was announced on June 17, 2011 by Forrest Voight<ref>[https://bitcointalk.org/index.php?topic=18313.0 p2pool: Decentralized, DoS-resistant, Hop-Proof - Now active on mainnet!]</ref>.

The pool began testing against mainnet in mid-July, 2011. The pool was reviewed on a [[Bitcoin Miner]] post on July 26, 2011<ref>[http://www.bitcoinminer.com/post/8101660461 P2Pool Decentralized Pool Nearly Ready For Prime-Time]</ref>.

The software author's address for donations can be found in the signature section of his [http://forum.bitcoin.org/index.php?action=profile;u=6447 forum profile].

==Donating to P2Pool miners==
In order to encourage people to mine to P2Pool you can donate to the recent miners in proportion using a sendmany:

For example, a bash script to donate 10 btc is:
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://127.0.0.1:9332/patron_sendmany/10)"
</pre>

You can replace "" with "accountname" if you want to pay from some specific bitcoind account, and you need to replace 127.0.0.1 with the address of your P2Pool node if you're not running one locally.

Note that the amount you donate will be allocated to recent miners in proportion to the amount of work they've done in the last 24 hours or so, but all the miner whose shares of the donated amount are less than 0.01 BTC will have their shares combined into a single amount which is awarded to one of them at random, with the chance of winning this 'lottery' weighted by the miner's recent amount of work done. You can change this 0.01 BTC threshold like this, for example, which says to pay 10 BTC, but to share it amongst more miners that the default, cutting off at 0.001 BTC instead of at 0.01 BTC.
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://127.0.0.1:9332/patron_sendmany/10/0.001)"
</pre>

If you decide to donate you should announce it on the forums so that your donations provide the most incentive possible.

==Sponsors==

Thanks to:

* The [https://bitcoinfoundation.org/ Bitcoin Foundation] for its generous support of P2Pool
* The [https://litecoin.org/ Litecoin Project] for its generous donations to P2Pool

==See Also==

* [[Comparison of mining pools]]
* [[Pooled Mining]]
* [[P2Pool code documentation]]

==External Links==

* [http://forum.bitcoin.org/index.php?topic=18313.0 P2Pool forum]
* [https://github.com/forrestv/p2pool p2pool] project on GitHub
* {{Freenode IRC|p2pool}} discussion and support
* [http://minefast.coincadence.com/p2pool-stats.php P2Pool Global Stats] stats page
* Up-to-date P2Pool mining stats: [http://minefast.coincadence.com/p2pool-stats.php Minefast.CoinCadence.com P2Pool stats]
* [http://poolnode.info poolnode.info] Public list of P2Pool BTC/LTC nodes.
* [https://www.bitcoinmining.com/bitcoin-mining-pools/ Bitcoin Mining Pools]
* [http://whatisp2pool.com whatisp2pool.com] An easy introduction to mining and P2Pool.
* [https://bitcointalk.org/index.php?topic=18313 Bitcointalk thread]
* [http://organofcorti.blogspot.com/2012/11/52-p2pool-achieving-expectations.html?m=1 Statistical analysis of P2Pool from Neighborhood Pool Watch]
* [http://chimera.labs.oreilly.com/books/1234000001802/ch08.html#mining_pools P2Pool section] of [[Mastering Bitcoin]] by [[Wikipedia:Andreas Antonopoulos|Andreas M. Antonopoulos]]
* [https://bitcointalk.org/index.php?topic=153232.0 A guide for mining efficiently on P2Pool, includes FUD repellent and FAQ]

==References==
<references />

[[Category:Pool Operators]]
{{Pools}}
[[Category:Technical]]
[[Category:Mining]]

P2Pool

2018-01-02T12:10:09Z

Lclc: Fix Bitcointalk URL

{{Infobox company
|name=P2Pool
|trading_name=P2Pool
|industry=[[Mining pool]]
|foundation=July 17, 2011
|hashrate=1.6 Phash/s
|website= http://p2pool.in
}}
[[Image:P2pool_chain.png‎|thumb|350px|right|Visualization of the P2Pool share chain]]

'''P2Pool''' is a decentralized [[Bitcoin]] [[Bitcoin Pool|mining pool]] that works by creating a peer-to-peer network of miner nodes.

<blockquote>P2Pool creates a new block chain in which the difficulty is adjusted so a new block is found every 30 seconds. The blocks that get into the P2Pool block chain (called the "share chain") are the same blocks that would get into the Bitcoin block chain, only they have a lower difficulty target. Whenever a peer announces a new share found (new block in the P2Pool block chain), it is received by the other peers, and the other peers verify that this block contains payouts for all the previous miners who found a share (and announced it) that made it into the P2Pool share chain. This continues until some peer finds a block that has a difficulty that meets the Bitcoin network's difficulty target. This peer announces this block to the Bitcoin network and miners who have submitted shares for this block are paid in the generation transaction, proportionally to how many shares they have found in the last while. - Unknown author</blockquote>

Decentralized payout pooling solves the problem of centralized mining pools degrading the decentralization of Bitcoin and avoids the risk of hard to detect theft by pool operators.

Miners are configured to connect to a P2Pool node that can be run locally, alongside the miner. P2Pool users must run a full Bitcoin node which serves the purpose of independently validating transactions and the Bitcoin blockchain. P2Pool also supports merged mining and several alternative blockchains.

P2Pool nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself, which can also result in a share if it meets P2Pool's difficulty.

Because of the importance of strengthening Bitcoin's decentralization, some Bitcoin supporters donate to P2Pool miners, resulting in average returns above 100% of the expected reward.
However, it should be noted that there are other pools (such as [[BitPenny]] and [[Eligius]]) which can provide this same level of decentralization.

== Overview ==

P2Pool shares form a "sharechain" with each share referencing the previous share's hash. Each share contains a standard Bitcoin block header, some P2Pool-specific data that is used to compute the generation transaction (total subsidy, payout script of this share, a nonce, the previous share's hash, and the current target for shares), and a Merkle branch linking that generation transaction to the block header's Merkle hash.

The chain continuously regulates its target to keep generation around one share every thirty seconds, just as Bitcoin regulates it to generate one block every ten minutes.
This means that finding shares becomes more difficult (resulting in higher variance) the more people mine on P2Pool, though large miners have the option to raise their difficulty, and so reduce the impact of their mining on P2Pool's minimum difficulty.

Unlike Bitcoin, nodes do not know the entire chain - instead they only hold the last 8640 shares (the last 3 day's worth). In order to prevent an attacker from working on a chain in secret and then releasing it, overriding the existing chain, chains are judged by how much work they have since a point in the past. To ascertain that the work has been done since that point, nodes look at the Bitcoin blocks that the shares reference, establishing a provable timestamp. (If a share points to a block, it was definitely made after that block was made.)

=== Payout logic ===

Each share contains a generation transaction that pays to the previous ''n'' shares, where ''n'' is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= 24 hours of shares), whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.

The block reward (currently 12.5BTC) and the transaction fees are combined and apportioned according to these rules:

A subsidy of 0.5% is sent to the node that solved the block in order to discourage not sharing solutions that qualify as a block. (A miner with the aim to harm others could withhold the block, thereby preventing anybody from getting paid. He can NOT redirect the payout to himself.) The remaining 99.5% is distributed evenly to miners based on work done recently.

In the event that a share qualifies as a block, this generation transaction is exposed to the Bitcoin network and takes effect, transferring each node its payout.

=== Stales ===

On P2Pool stales refer to shares which can't make it into the sharechain. Because the sharechain is 20 times faster than the Bitcoin chain many stales are common and expected. However, because the payout is [[Comparison_of_mining_pools|PPLNS]] only your stale rate relative to other nodes is relevant; the absolute rate is not.

There are two reported kinds of stales in P2Pool: "DEAD ON ARRIVAL" shares and orphan shares. Dead shares were too old by the time they arrived at your local P2Pool. Very high dead rates can indicate miner misconfiguration. Orphan shares are shares which were not extended by the rest of the P2Pool network, because some other miner's share was accepted first. Very high orphan rates may indicate network connectivity problems.

The P2Pool console output shows your relative stale rate compared to other P2Pool miners in the 'Own efficiency' column:
<pre>
2012-01-07 20:57:51.797420 Pool stales: 13% Own: 13±2% Own efficiency: 100±2%
</pre>

When you first start P2Pool claimed efficiency will be low and the error bounds on this estimate will be large, but as it runs the numbers will converge to their correct values.

If your efficiency is unusually low, make sure your network connection isn't overloaded, that your miners support long polling and are not set to work for excessive amounts of time, and that your bitcoind has multiple connections.

== Joining the pool ==

Follow these steps to join the pool:

* Run Bitcoin with the RPC interface enabled: edit bitcoin.conf to include:
rpcuser=USER
rpcpassword=LONG_RANDOM_SECRET_VALUE
server=1
**'''Replace LONG_RANDOM_SECRET_VALUE with something long and random like the output of smashing your keyboard for a bit like fju4M78yAj3ds39pak92raK'''. You don't need to be able to remember it. If your RPC port becomes exposed to the internet a thief could steal your bitcoin if they could guess it, or use a brute force attack in order to find it.
** Bitcoin 0.8.5 or later is required
** It's important that your Bitcoin client be fully synchronized before starting. It's also better if you have the Bitcoin port forwarded
* Download p2pool:
** Windows binary: See http://forum.bitcoin.org/index.php?topic=18313.0
** Source download: https://github.com/forrestv/p2pool/tags
** git: git clone git://github.com/forrestv/p2pool.git
* Run p2pool: (See below for additional options.)
** Windows py2exe: run_p2pool.exe
** Source: python run_p2pool.py
* Run a miner daemon with long polling connecting to 127.0.0.1 (or the IP of the host running p2pool if it isn't on the same computer as the miner) on port 9332 with any username and password
** bfgminer -O u:p -o http://127.0.0.1:9332/ --submit-stale
* Subscribe to the [https://groups.google.com/forum/#!forum/p2pool-notifications P2Pool notifications] mailing list for urgent pool status updates

Dependencies if running from source:
* Python 2.6 or higher (but not 3.x)
* python-argparse
* Twisted (Ubuntu package python-twisted)

=== Frequently Asked Questions ===

'''Q:''' "Why does my miner report so many longpoll events when mining on p2pool? - P4Man" 
'''A:''' "Once every ~30 seconds is normal. That is how often p2pool shares are generated (as opposed to ~10 min for bitcoin blocks) - cabin"

'''Q:''' "Do the 'orphan' and 'dead' shares in P2Pool's status display hurt me?" 
'''A:''' They shouldn't - It's normal for some fraction of everyone's shares to end up orphaned or dead. Because payouts are calculated by counting how many shares you have relative to others, everyone with normal configurations is equally "hurt" by this. However, if you have a large proportion of stales, your payout will be hurt. You can see how well you're doing by looking at P2Pool's "Efficiency" (ex: ''Efficiency: ~110.6% (40-111%)''). If 100% doesn't lie within the [http://en.wikipedia.org/wiki/Confidence_interval confidence interval] at the end, something is probably wrong (with 95% confidence).

'''Q:''' "What do I do if my efficiency is low?" 
'''A:''' Make sure the computers you're running P2Pool and the miner on have enough memory and CPU time. If you have a lot of dead shares or the "Local dead on arrival" number is higher than a few percent, that means that something is wrong with your miner. Check to make sure that it is one of the working versions in the ''Miners'' section on this page. Lower the intensity or raise the FPS of your miner. If you have a lot of orphan shares, something is wrong with P2Pool's P2P connection. Decrease the load on your internet connection or enable QoS (Quality of Service) on your router.

'''Q:''' What is PPLNS? 
'''A:''' Pay-Per-Last-N-Shares is a payout method that is completely resistant to pool hoppers.

'''Q:''' Why am I not getting very many shares?! 
'''A:''' The P2Pool difficulty is hundreds of times higher than on other pools. It can take time to get a share. P2Pool displays an estimate of how long you have to wait in the console output.

'''Q:''' Why does my miner say it has found a lot of shares but p2pool say I have only found a few?! 
'''A:''' The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly

'''Q:''' Why am I getting so many rejects? 
'''A:''' You're using an incompatible miner. See the miners section here, increase your FPS on the miner, decrease the intensity, upgrade your miner, or try a different miner.

'''Q:''' What stops the pool operator or the block finder from stealing a block? 
'''A:''' A block solution is only worth anything because its hash matches Bitcoin's target. Altering anything within the block will change its hash and make it worthless. If you are concerned about the pool operator stealing a block, you should try to inspect the source code of each new version.

'''Q:''' Why does it say "Generated?" I want to spend my coins now! 
'''A:''' P2Pool includes payouts in generation transactions, which must mature (taking 120 blocks or 20 hours) before they can be spent. The reason for this is that a block could be orphaned, which would make its payout invalid and could reverse transactions.

'''Q:''' Do I get paid transaction fees? 
'''A:''' Yes. They are split among P2Pool miners.

'''Q:''' What are these payments I'm getting that aren't generated? 
'''A:''' These are subsidies that people who support the idea of P2Pool send to miners.

'''Q:''' Cool Subsidies sound like an awesome idea! How do I send some BTC to these awesome miners? 
'''A:''' See end of this page.

'''Q:''' Do I really need the WHOLE blockchain? 
'''A:''' Yes. Your node needs to be able to independently make decisions about what transactions to mine.

'''Q:''' How do merged mining payments work? 
'''A:''' Merged mining is handled entirely by namecoind, so you're solo mining and payouts will go into namecoind's wallet.

=== Miners ===

This is all for the latest p2pool version, as it includes several new workarounds.

With all miners, using a HIGH FPS target (100?) or a LOW intensity (8 for bfgminer?) helps a lot with reducing stales.

* bfgminer, cgminer, and ufasoft work perfectly without any extra options.
* DiabloMiner works fine after commit 3b731b9.
* Phoenix works fine after commit a658ef2.
* Poclbm works fine after commit 5e994e7.

P2Pool uses higher difficulty shares than most centralized pools, so you'll see fewer shares reported. This is normal and doesn't reduce your payments. It's also normal to see longpoll messages once per every ten seconds on average.

====Tips to configure bfgminer to reduce stale/doa:====
* "gpu-threads" : "1", (2 by default)
* "queue" : "0", (1 by default)

Because of fast longpooling in p2pool it is better not NOT fetch work ahead.

On non-dedicated machines intensity=3 allows normal usage of PC, set it to 7 or more to get full hashrate.

On most cards best is diablo and phatk kernel, looks like poclbm kernel have unstable rate.

=== Useful features ===

* If upgrading P2Pool or changing its configuration, you can start another instance of P2Pool in parallel with the first. It will start normally, but realize that the worker and P2P listening ports are busy and keep trying to bind to them in the background. Thus, you can do almost-completely-seamless upgrades of P2Pool.
* If you run multiple P2Pool nodes or have trusted friends that run P2Pool, you can use ''-n'' to establish a constant extra P2P connection to them.
* You can make P2Pool use a configuration file by running run_p2pool.py @FILENAME, with FILENAME being the path to a file containing the command-line arguments (newlines are ignored) Example:
<pre>
--net bitcoin
-n 1.2.3.4
</pre>
* Setting the username of your miner connecting to P2Pool to a Bitcoin address will make it mine to that address instead of the one requested from bitcoind or set by -a
* Appending "/1000" to a miner's username will increase the difficulty of producing a P2Pool share to at most 1000. This is useful to large miners because doing this can make it easier for small miners while minimally impacting the large miners themselves. See [https://bitcointalk.org/index.php?topic=18313.msg816322#msg816322 recommended values].
** Appending "+1" (for example) after that will make P2Pool always give your miners work with a difficulty of 1

=== Web interface ===

Lots of data and useful tools are available at http://127.0.0.1:9332/something:
* /static/ - Lots of information from shares to graphs to payouts.
* /rate
* /users
* /fee
* /current_payouts
* /patron_sendmany - Gives sendmany outputs for fair donations to P2Pool
* /global_stats
* /local_stats
* /peer_addresses
* /payout_addr
* /recent_blocks
* /uptime
* /web/log - Some different stats collected over the last day

=== Included README ===
<pre>Requirements:
Generic:
Bitcoin >=0.6.0rc4 or Bitcoin >=0.5.4 (for BIP16 support) or Litecoin
Python
Twisted
python-argparse (for Python <=2.6)

Linux:
sudo apt-get install python-zope.interface python-twisted python-twisted-web
sudo apt-get install python-argparse # if on Python 2.6 or older

Windows:
Install Python 2.7: http://www.python.org/getit/
Install Twisted: http://twistedmatrix.com/trac/wiki/Downloads
Install Zope.Interface: http://pypi.python.org/pypi/zope.interface/3.8.0
Unzip the files into C:\Python27\Lib\site-packages

Running P2Pool:
To use P2Pool, you must be running your own local bitcoind. For standard
configurations, using P2Pool should be as simple as:

python run_p2pool.py

Then run your miner program, connecting to 127.0.0.1 on port 9332 with any
username and password.

If you are behind a NAT, you should enable TCP port forwarding on your
router. Forward port 9333 to the host running P2Pool.

Run "python run_p2pool.py --help" for additional options.

Notes for Litecoin:
Requirements:
In order to run P2Pool with the Litecoin network, you would need to build and install the
ltc_scrypt module that includes the scrypt proof of work code that Litecoin uses for hashes.

Linux:
cd litecoin_scrypt
sudo python setup.py install

Windows:
Install MinGW: http://www.mingw.org/wiki/Getting_Started
Install Python 2.7: http://www.python.org/getit/

cd litecoin_scrypt
C:\Python27\python.exe setup.py build --compile=mingw32 install

If you run into an error with unrecognized command line option '-mno-cygwin', see this:
http://stackoverflow.com/questions/6034390/compiling-with-cython-and-mingw-produces-gcc-error-unrecognized-command-line-o

Running P2Pool:
Run P2Pool with the "--net litecoin" option.
Run your miner program, connecting to 127.0.0.1 on port 9327.
Forward port 9338 to the host running P2Pool.

Litecoin's use of ports 9332 and 9332 conflicts with P2Pool running on
the Bitcoin network. To avoid problems, add these lines to litecoin.conf
and restart litecoind:
rpcport=10332
port=10333
</pre>

=== Option Reference ===
<pre>
usage: run_p2pool.py [-h] [--version] [--net {bitcoin,litecoin}] [--testnet]
[--debug] [-a ADDRESS] [--datadir DATADIR]
[--logfile LOGFILE] [--merged MERGED_URLS]
[--give-author DONATION_PERCENTAGE] [--iocp]
[--irc-announce] [--no-bugreport] [--p2pool-port PORT]
[-n ADDR[:PORT]] [--disable-upnp] [--max-conns CONNS]
[-w PORT or ADDR:PORT] [-f FEE_PERCENTAGE]
[--bitcoind-address BITCOIND_ADDRESS]
[--bitcoind-rpc-port BITCOIND_RPC_PORT]
[--bitcoind-p2p-port BITCOIND_P2P_PORT]
[BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

p2pool (version 0.11.1-8-ged9359d)

optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
--net {bitcoin,litecoin}
use specified network (default: bitcoin)
--testnet use the network's testnet
--debug enable debugging mode
-a ADDRESS, --address ADDRESS
generate payouts to this address (default: <address
requested from bitcoind>)
--datadir DATADIR store data in this directory (default: <directory
run_p2pool.py is in>/data)
--logfile LOGFILE log to this file (default: data/<NET>/log)
--merged MERGED_URLS call getauxblock on this url to get work for merged
mining (example:
http://ncuser:ncpass@127.0.0.1:10332/)
--give-author DONATION_PERCENTAGE
donate this percentage of work towards the development
of p2pool (default: 0.5)
--iocp use Windows IOCP API in order to avoid errors due to
large number of sockets being open
--irc-announce announce any blocks found on
irc://irc.freenode.net/#p2pool
--no-bugreport disable submitting caught exceptions to the author
--disable-upnp don't attempt to use UPnP to forward p2pool's P2P port
from the Internet to this computer

p2pool interface:
--p2pool-port PORT use port PORT to listen for connections (forward this
port from your router!) (default: bitcoin:9333,
litecoin:9338)
-n ADDR[:PORT], --p2pool-node ADDR[:PORT]
connect to existing p2pool node at ADDR listening on
port PORT (defaults to default p2pool P2P port) in
addition to builtin addresses
--max-conns CONNS maximum incoming connections (default: 40)

worker interface:
-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
listen on PORT on interface with ADDR for RPC
connections from miners (default: all interfaces,
bitcoin:9332, litecoin:9327)
-f FEE_PERCENTAGE, --fee FEE_PERCENTAGE
charge workers mining to their own bitcoin address (by
setting their miner's username to a bitcoin address)
this percentage fee to mine on your p2pool instance.
Amount displayed at http://127.0.0.1:WORKER_PORT/fee
(default: 0)

bitcoind interface:
--bitcoind-address BITCOIND_ADDRESS
connect to this address (default: 127.0.0.1)
--bitcoind-rpc-port BITCOIND_RPC_PORT
connect to JSON-RPC interface at this port (default:
bitcoin:8332, litecoin:9332 <read from bitcoin.conf if
password not provided>)
--bitcoind-p2p-port BITCOIND_P2P_PORT
connect to P2P interface at this port (default:
bitcoin:8333, litecoin:9333 <read from bitcoin.conf if
password not provided>)
BITCOIND_RPCUSERPASS bitcoind RPC interface username, then password, space-
separated (only one being provided will cause the
username to default to being empty, and none will
cause P2Pool to read them from bitcoin.conf)
</pre>

== Interoperability table ==
P2pool works fine with most hardware. This lists some of the hardware confirmed to work and any special configuration required.

* ASICminer blade 10GH/s (Requires adding +1 to username or proxy)
* Avalon 110nm 60-110 GH/s (All batches)
* Avalon based 55nm 200 GH/s (specific makers?)
* Avalon prototype 55nm 120GH/s (~ 20 exist)
* Icarus FPGA
* Bitfury strikes back H-card and M-card ([https://bitcointalk.org/index.php?topic=18313.msg4424081#msg4424081 instructions])
* Bitmain Antminer S1 180GH/s ([https://github.com/AntMiner/AntGen1/tree/master/firmware Requires 20131226 firmware.])
* Bitmain Antminer S3 440GH/s
* BFL SC Jalapeno, SC Single 30, 50, & 60 GH/s
* Spondoolies Tech SP 10
* Spondoolies Tech SP 30

(Various GPU and most FPGAs other than BFL single FPGAs work fine too)

This is a list of hardware with known issues that should not be used on p2pool.

* Cointerra Terraminer IV (10-20% hash rate loss when mining on p2pool)
* Btimain Antminer S2 (10-20% hash rate loss when mining on p2pool, the S1 & S3 both work well on p2pool)

== Protocol description ==

P2Pool's protocol mirrors Bitcoin's P2P protocol in many ways. It uses the same framing (prefix, command, length, checksum, payload) and similar commands:

* '''version''' - sent to establish a connection - contains (''version'', ''services'', ''addr_to'', ''addr_from'', ''nonce'', ''sub_version'', ''mode'', ''best_share_hash'')
* '''setmode''' - sent to update the ''mode'' sent in the '''version''' message - contains (''mode'')
* '''ping''' - sent to keep connection alive - contains ()
* '''addrme''' - request that the receiving node send out an addr for the sending node - contains (''port'')
* '''addrs''' - broadcast list of nodes' addresses - contains (''addrs'')
* '''getaddrs''' - request that the receiving node send ''count'' addrs - contains (''count'')
* '''getshares''' - request that the receiving node send the shares referenced by ''hashes'' and ''parents'' of their parents, stopping at any share referenced by ''stops'' - contains (''hashes'', ''parents'', ''stops'')
* '''shares''' - broadcast message of the contents of shares - contains (''shares'')

==History==

This project was announced on June 17, 2011 by Forrest Voight<ref>[https://bitcointalk.org/index.php?topic=18313.0 p2pool: Decentralized, DoS-resistant, Hop-Proof - Now active on mainnet!]</ref>.

The pool began testing against mainnet in mid-July, 2011. The pool was reviewed on a [[Bitcoin Miner]] post on July 26, 2011<ref>[http://www.bitcoinminer.com/post/8101660461 P2Pool Decentralized Pool Nearly Ready For Prime-Time]</ref>.

The software author's address for donations can be found in the signature section of his [http://forum.bitcoin.org/index.php?action=profile;u=6447 forum profile].

==Donating to P2Pool miners==
In order to encourage people to mine to P2Pool you can donate to the recent miners in proportion using a sendmany:

For example, a bash script to donate 10 btc is:
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://127.0.0.1:9332/patron_sendmany/10)"
</pre>

You can replace "" with "accountname" if you want to pay from some specific bitcoind account, and you need to replace 127.0.0.1 with the address of your P2Pool node if you're not running one locally.

Note that the amount you donate will be allocated to recent miners in proportion to the amount of work they've done in the last 24 hours or so, but all the miner whose shares of the donated amount are less than 0.01 BTC will have their shares combined into a single amount which is awarded to one of them at random, with the chance of winning this 'lottery' weighted by the miner's recent amount of work done. You can change this 0.01 BTC threshold like this, for example, which says to pay 10 BTC, but to share it amongst more miners that the default, cutting off at 0.001 BTC instead of at 0.01 BTC.
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://127.0.0.1:9332/patron_sendmany/10/0.001)"
</pre>

If you decide to donate you should announce it on the forums so that your donations provide the most incentive possible.

==Sponsors==

Thanks to:

* The [https://bitcoinfoundation.org/ Bitcoin Foundation] for its generous support of P2Pool
* The [https://litecoin.org/ Litecoin Project] for its generous donations to P2Pool

==See Also==

* [[Comparison of mining pools]]
* [[Pooled Mining]]
* [[P2Pool code documentation]]

==External Links==

* [http://forum.bitcoin.org/index.php?topic=18313.0 P2Pool forum]
* [https://github.com/forrestv/p2pool p2pool] project on GitHub
* {{Freenode IRC|p2pool}} discussion and support
* [http://minefast.coincadence.com/p2pool-stats.php P2Pool Global Stats] stats page
* Up-to-date P2Pool mining stats: [http://minefast.coincadence.com/p2pool-stats.php Minefast.CoinCadence.com P2Pool stats]
* [http://poolnode.info poolnode.info] Public list of P2Pool BTC/LTC nodes.
* [https://www.bitcoinmining.com/bitcoin-mining-pools/ Bitcoin Mining Pools]
* [http://whatisp2pool.com whatisp2pool.com] An easy introduction to mining and P2Pool.
* [https://bitcointalk.org/index.php?topic=18313 Bitcointalk thread]
* [http://organofcorti.blogspot.com/2012/11/52-p2pool-achieving-expectations.html?m=1 Statistical analysis of P2Pool from Neighborhood Pool Watch]
* [http://chimera.labs.oreilly.com/books/1234000001802/ch08.html#mining_pools P2Pool section] of [[Mastering Bitcoin]] by [[Wikipedia:Andreas Antonopoulos|Andreas M. Antonopoulos]]
* [https://bitcointalk.org/index.php?topic=153232.0 A guide for mining efficiently on P2Pool, includes FUD repellent and FAQ]

==References==
<references />

[[Category:Pool Operators]]
{{Pools}}
[[Category:Technical]]
[[Category:Mining]]

Segwit support

2017-07-13T07:16:58Z

Lclc: Undo revision 63636 by Sandakersmann (talk) Not a Bitcoin Dev

<big><big>'''PLEASE NOTE:''' This list is not yet complete.</big></big>

'''Developers/businesses: Please add a row for yourself in the applicable table to reflect your positions. If for some reason you don't already have a wiki account that can edit the page, make an account and ask luke-jr for help if you get caught in the anti-spam.'''

{| class="wikitable"
| {{No}} || doesn't support (but might or might not go along with it with sufficient community support)
|-
| {{Deficient}} || okay with the idea, but considers it to have insufficient community support
|-
| {{Evaluating}} || still evaluating the idea
|-
| {{AccJuly}} || it is a workable solution, provided it is activated before August 1 (and therefore BIP148-compatible)
|-
| {{Wanting}} || positively likes the idea, but considers it to have insufficient community support
|-
| {{Weak}} || better than nothing at all
|-
| {{Acceptable}} || it is a workable solution
|-
| {{Prefer}} || it is what he would choose if it was only up to him and no outside influences
|}

__TOC__

==Developers==



''Note that support for a given proposal does not mean developers support merging it into Core or any other specific codebase.''

{| class="wikitable sortable"
! rowspan=2 | Developer
! rowspan=2 | Aff* 
! Segwit itself
! colspan=3 | Deployment methods
! colspan=2 | Hardfork bundles (Silbert agreement)
|-
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]
|-
| Karl-Johan Alm || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Bryan Bishop || || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| ฿tcDrak || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Andrew Chow || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Wang Chun || [[F2Pool]] || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{Acceptable}} || {{AccJuly}} ||
|-
| Matt Corallo || Core || {{Prefer}} || {{No}} || || {{Acceptable}} || {{No|LOL}} ||
|-
| Johnathan Corgan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Luke Dashjr || Core || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No}} || {{Deficient}}
|-
| Christian Decker || c-lightning || {{Prefer}} || {{Acceptable}} || || || ||
|-
| Nicolas Dorier || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{AccJuly}} || ||
|-
| Thaddeus Dryja || lit || {{Prefer}} || {{No}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-

| Mark Friedenbach || BIP 68/112 || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No|LOL}} || {{No|Nope}}
|-
| Pavel Janik || Core || {{Prefer}} || {{No}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Thomas Kerin || Core || {{Prefer}} || {{Wanting}} || {{Prefer}} || {{Weak}} || {{No}} || {{No}}
|-
| Johnson Lau || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || ||
|-
| Eric Lombrozo || || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Greg Maxwell || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Alex Morcos || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} ||
|-
| nopara73 || TumbleBit || {{Weak}} || {{Wanting}} || {{Prefer}} || || ||
|-
| Laolu "roasbeef" Osuntokun || lnd || {{Prefer}} || || || || {{No}} ||
|-
| Jeremy Rubin || Core || {{Prefer}} || {{Deficient}} || {{No}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Pavol "stick" Rusnak || [[TREZOR]] || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Rusty Russell || c-lightning || {{Prefer}} || {{Prefer}} || || || ||
|-
| Gregory Sanders || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} ||
|-
| Jonas Schnelli || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Patrick Strateman || Core || {{Prefer}} || || || || {{No}} || {{No}}
|-
| Paul Sztorc || || {{Prefer}} || {{Deficient}} || {{Wanting}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Amir Taaki || libbtc || {{Acceptable}} || {{Prefer}} || || || {{No}} || {{No}}
|-
| Jorge Timon || Core || {{Prefer}} || {{No}} || {{Prefer}} || {{Deficient}} || {{No}} || {{No}}
|-
| Peter Todd || || {{Prefer}} || {{Deficient}} || {{Wanting}} || {{AccJuly}} || {{No|LOL}} ||
|-
| Warren Togami || Elements || {{Prefer}} || {{Prefer}} || {{Acceptable}} || || ||
|-
| Wladimir van der Laan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Thomas Voegtlin || Electrum || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Leo Wandersleb || Mycelium || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Pieter Wuille || Core || {{Prefer}} || || || || {{No}} ||
|}

* "affiliation" is an optional field for the company or project the individual is associated with, that most qualifies the person to comment on the matter and is not meant as a company or project endorsement of the individual's position.

==Businesses==

'''When adding companies below, sources for each position MUST be provided.'''

{| class="wikitable sortable"
! rowspan=2 | Company
! rowspan=2 | Service
! Segwit itself
! colspan=3 | Deployment methods
! colspan=2 | Hardfork bundles (Silbert agreement)
|-
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]
|-
| Abra || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Bitcoin India || exchange/miner || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| BitcoinReminder.com || service || {{Prefer}}<ref name="bitcoinreminder_com">[https://bitcoinreminder.com/informations/poli BitcoinReminder.com's position on scaling proposals]</ref> || {{Prefer}}<ref name="bitcoinreminder_com"/> || {{Acceptable}}<ref name="bitcoinreminder_com"/> || {{Weak}}<ref name="bitcoinreminder_com"/> || {{No|LOL}}<ref name="bitcoinreminder_com"/> || {{No}}<ref name="bitcoinreminder_com"/>
|-
| Bitfinex || exchange || {{Acceptable}}<ref name="coindance" /> || {{Acceptable}} || || || ||
|-
| Bitfury || miner || {{Prefer}}<ref name="coindance" /> || {{Acceptable}} || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Bitmain || miner || {{AccJuly}}<ref name="bitmain">[https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip148/ Bitmain's plot against BIP148]</ref> || {{No}} || || {{AccJuly}} || {{AccJuly}}<ref name="bitmain" /> ||
|-
| Bitonic/BL3P.eu || exchange || {{Prefer}}<ref name="bitonic">[https://bitonic.nl/en/news/138/our-position-on-scaling-proposals Bitonic's position on scaling proposals]</ref> || {{Prefer}}<ref name="bitonic"/> || {{Acceptable}}<ref name="bitonic"/> || {{Weak}}<ref name="bitonic"/> || {{No|LOL}}<ref name="bitonic"/> || {{No}}
|-
| Bitpay || wallet || {{Prefer}}<ref name="bccore_swadoption"/> || {{No}} || || {{Prefer}} || {{Prefer}}<ref name="silbert" /> ||
|-
| Bitrated || reputation || {{Acceptable}}<ref name="bitrated">[https://twitter.com/bitrated/status/876805892003553281]</ref> || {{Acceptable}}<ref name="bitrated" /> || {{Prefer}}<ref name="bitrated" /> || {{AccJuly}}<ref name="bitrated" /> || {{No}}<ref name="bitrated" /><ref>[https://medium.com/@shesek/why-i-dont-support-the-compromise-efforts-9d73a8cce6be Why I don’t support horse-trading compromises for Bitcoin protocol development]</ref> ||
|-
| Bitrefill || merchant || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| Bitsquare || exchange || {{Prefer}} || {{Prefer}}<ref name="bitsquare">[https://forum.bitsquare.io/t/bitsquare-will-support-uasf-bitcoin-not-bitmaincoin/2265 Bitsquare will support UASF Bitcoin not BitMainCoin]</ref> || {{Acceptable}}<ref name="bitsquare"/> || || ||
|-
| Bitstamp || exchange || || || || || ||
|-
| Bittylicious || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref>[https://twitter.com/Bittylicious_/status/867305106668224513 Bittylicious answer on Twitter]</ref> || || || ||
|-
| Blockchain.info || wallet || {{Acceptable}}<ref name="bccore_swadoption"/> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| blockonomics || || {{Prefer}} || {{Prefer}}<ref>[https://twitter.com/blockonomics_co/status/851738251509497856 blockonomics announcement on Twitter]</ref> || || || ||
|-
| Bustabit|| gambling || {{Prefer}}<ref name="bustabit">[https://www.bustabit.com/statement-on-forks Bustabit Statement on Bitcoin Forks]</ref> || {{Acceptable}}<ref name="bustabit"/> || || || {{AccJuly}}<ref name="bustabit"/> ||
|-
| Bylls || payments / exchange || {{Prefer}}<ref name="bylls">[https://twitter.com/myBylls/status/877959773794316288 Bylls supports Segwit softfork but no current HF plan]</ref> || {{Prefer}}<ref name="bylls">[https://twitter.com/myBylls/status/877959773794316288 Bylls supports Segwit softfork but no current HF plan]</ref> || {{Acceptable}}<ref name="bylls">[https://twitter.com/myBylls/status/877965277316730880 Bylls twitter statement]</ref> || {{AccJuly}}<ref name="bylls">[https://twitter.com/myBylls/status/877965277316730880 Bylls twitter statement]</ref> || {{No}}<ref name="bylls">[https://twitter.com/myBylls/status/877965277316730880 Bylls twitter statement]</ref> || {{No}}<ref name="bylls">[https://twitter.com/myBylls/status/877965277316730880 Bylls twitter statement]</ref>
|-
| Ciphrex || wallet / dev stack || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || || ||
|-
| Coinbase || wallet || {{Acceptable}}<ref name="bccore_swadoption"/> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| CoinGate || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| CoinJar || wallet || || {{Evaluating}}<ref>[https://twitter.com/GetCoinJar/status/875581525730787329 CoinJar answer on Twitter]</ref> || || || ||
|-
| Coinkite || || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| coinomi || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| DigitalBitbox || wallet(hardware) || {{Prefer}} || {{Acceptable}} || {{Prefer}}|| || ||
|-
| Échange de Montréal || exchange || {{Prefer}}<ref name="echangedemontreal" /> || {{Prefer}}<ref name="echangedemontreal" /> || || ||
|-
| Jaxx || || {{Prefer}}<ref name="jaxx">[https://twitter.com/Jaxx_Support/status/882607648457334785 Jaxx tweet]</ref> || {{Acceptable}}<ref name="jaxx"/> || || {{AccJuly}}<ref name="jaxx"/> || {{AccJuly}}<ref name="jaxx"/> ||
|-
| Kraken || exchange || || || || || ||
|-
| LightningASIC || miner || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| OneHash || betting || {{Prefer}}<ref>[https://blog.onehash.com/sick-of-presidential-election-3f1a2defbbbf OneHash, "Sick of presidential election ?!"]</ref> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Poloniex || exchange || || || || || ||
|-
|QUOINE || exchange, trading, financial services || {{Evaluating}}<ref name="coindance" /> || {{Evaluating}}<ref name="coindance" /> || {{Evaluating}}<ref name="coindance" /> || {{Evaluating}}<ref name="coindance" /> || {{Evaluating}}<ref name="coindance" /> || {{Evaluating}}<ref name="coindance" />
|-
| Slushpool || miner || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || || ||
|-
| TheRockTrading || exchange || || {{Evaluating}}<ref>[https://twitter.com/TheRockTrading/status/872464394034315269 @TheRockTrading message on Twitter]</ref> || || || ||
|-
| Vaultoro || exchange || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Walltime || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| Woleet || Timestamping || {{Prefer}}<ref name="woleet">[https://twitter.com/Woleet/status/884078514307297280]</ref> || {{Prefer}}<ref name="woleet">[https://twitter.com/Woleet/status/884078514307297280]</ref>|| || || ||
|-
| Xapo || wallet || {{Prefer}}<ref name="coindance" /> || || || {{AccJuly}}<ref name="xapo">[https://twitter.com/tedmrogers/status/883061218545614848 Xapo tweet]</ref> || {{AccJuly}}<ref name="xapo"/> ||
|-
|}

<references>
<ref name="bccore_swadoption">[https://bitcoincore.org/en/segwit_adoption/ Bitcoin Core's Segwit adoption list]</ref>
<ref name="coindance">[https://coin.dance/poli Coin Dance, "Global Bitcoin Political Support & Public Opinion"]</ref>
<ref name="silbert">[https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77 Digital Currency Group, "Bitcoin Scaling Agreement at Consensus 2017"]</ref>
<ref name="echangedemontreal">[https://twitter.com/echangedemtl/status/875781093261271040 Échange de Montréal on twitter]</ref>
</references>

Bitcoin Wiki:Community portal

2017-06-14T20:27:17Z

Lclc: Change Switzerland URL to https://www.bitcoinassociation.ch/

== Bitcoin Community Forums on various platforms ==
* [http://bitcointalk.org/ Bitcointalk]
* [https://forum.bitcoin.com/ Bitcoin.com Forum]
* [https://bitco.in/forum/ Bitco.in]
* [http://www.reddit.com/r/Bitcoin/ /r/Bitcoin]
* [http://www.reddit.com/r/btc /r/btc]
* [http://www.reddit.com/r/bitcoin_uncensored /r/bitcoin_uncensored]
* [http://www.reddit.com/r/bitcoinxt /r/bitcoinxt]
* [https://plus.google.com/communities/115591368588047305300 Bitcoin Google+ Community]
* [https://www.cryptocompare.com/coins/btc/forum/USD CryptoCompare - Bitcoin Forum]
* [http://bitcoin.stackexchange.com/ The Bitcoin StackExchange]
* [http://bitcointrading.com Bitcoin Trading Forum]
* [http://groups.google.com/group/bitcoin-discussion Bitcoin google group]
* [http://www.facebook.com/bitcoins Facebook page]
* [https://www.facebook.com/buy.bitcoin.news Facebook Bitcoin page]
* [http://www.facebook.com/bitcoin.p2p.digital.currency Facebook page]
* [http://www.facebook.com/bitcoinaustria Bitcoin Austria Facebook page]
* [http://www.facebook.com/groups/136003253120130 Facebook Group]
* [https://plus.google.com/107581642674912229828/ Bitcoin Google+]
* [http://hubski.com/tag?id=bitcoin Bitcoin on Hubski]

===Regions / Languages===
* [http://bitcoin-austria.at/ Bitcoin Austria]
* [https://coinforum.ca Canada's Bitcoin Community]
* [https://www.bitcoin-italia.org Bitcoin Italia]
* [http://www.bitcoin.org.il Isreali Bitcoin Community Forum]
* [http://bitcoincenterkorea.org Bitcoin Center Korea]
* [http://bitcoin.pl/forum/ Polish Bitcoin Community Forum]
* [http://btcsec.com/ BTCsec.com] Russian Website about Bitcoin
* [https://forum.btcsec.com/ BTCsec.com Bitcoin Community Forum (Russian)]
* [http://rubitcoin.com/ Russian Bitcoin Community Forum]
* [https://www.facebook.com/groups/bitcoinph/ Bitcoin Philippine Community]

=== Local Communities ===
''For an up-to-date list please see [http://www.reddit.com/r/Bitcoin/wiki/local_communities local communities]
* [http://www.reddit.com/r/ArgenBitcoin Argentina bitcoin community]
* [http://www.reddit.com/r/BitcoinAUS Australia bitcoin community]
* [http://www.reddit.com/r/BitcoinAT Austria bitcoin community]
* [http://www.reddit.com/r/BitcoinBE Belgian bitcoin community]
* [http://www.reddit.com/r/BrasilBitcoin Brazil bitcoin community]
* [http://www.reddit.com/r/BitcoinCA Canada bitcoin community]
* [http://www.reddit.com/r/BitcoinDK Denmark bitcoin community]
* [http://www.reddit.com/r/bitcoinsuomi Finland bitcoin community]
* [http://www.reddit.com/r/BitcoinFrance France bitcoin community]
* [http://www.reddit.com/r/BitcoinDE Germany bitcoin community]
* [http://www.reddit.com/r/BitcoinGhana Ghana bitcoin community]
* [http://www.reddit.com/r/BitcoinGT Guatemala bitcoin community]
* [http://www.reddit.com/r/BitcoinIndia India bitcoin community]
* [http://www.reddit.com/r/BitcoinIran Iran bitcoin community]
* [http://www.reddit.com/r/BitcoinIT Italy bitcoin community]
* [http://www.reddit.com/r/BitcoinJP Japan bitcoin community]
* [http://www.reddit.com/r/bitcoinlaos Laos bitcoin community]
* [http://www.reddit.com/r/BitcoinMalaysia Malaysia bitcoin community]
* [http://www.reddit.com/r/BITCOINMEX Mexico bitcoin community]
* [http://www.reddit.com/r/BitcoinNL The Netherlands bitcoin community]
* [http://www.reddit.com/r/BitcoinNO Norway bitcoin community]
* [http://www.reddit.com/r/BitcoinPL Poland bitcoin community]
* [http://www.reddit.com/r/bitcoinsouthafrica South Africa bitcoin community]
* [http://www.reddit.com/r/bitcoines Spain bitcoin community]
* [http://www.reddit.com/r/BitcoinSWE Sweden bitcoin community]
* [https://www.bitcoinassociation.ch/ Swiss (Switzerland) bitcoin community]
* [http://www.reddit.com/r/btctaiwan Taiwan bitcoin community]
* [http://www.reddit.com/r/BitcoinTR Turkey bitcoin community]
* [http://www.reddit.com/r/BitcoinUK United Kingdom bitcoin community]
** [http://www.reddit.com/r/BitcoinLondon London bitcoin community]
* [http://www.reddit.com/r/BitcoinUSA USA bitcoin community]
** [http://www.reddit.com/r/BitcoinBayArea Bay Area, CA bitcoin community]
** [http://www.reddit.com/r/DenverBitcoin/ Denver, CO bitcoin community]
** [http://www.reddit.com/r/BitcoinAsheville Asheville, NC bitcoin community]
** [http://www.reddit.com/r/BitcoinAlbuquerque Albuquerque, NM bitcoin community]
** [http://www.reddit.com/r/BitcoinNY New York City, NY bitcoin community]
** [http://www.reddit.com/r/BitcoinPA Pennsylvania bitcoin community]
** [http://www.reddit.com/r/BitcoinNashville Nashville, TN bitcoin community]
** [http://reddit.com/r/BitcoinAustin/ Austin, TX bitcoin community]
** [http://www.reddit.com/r/BitcoinSeattle Seattle, WA bitcoin community]
* [http://www.reddit.com/r/BitcoinVzla Venezuela bitcoin community]

== Bitcoin Community Groups on Bitcoin Wiki platform ==

=== Special interests ===
* [[Bitcoin Wiki]]-group

====Clusters====
There are various temporary and permanent clusters where bitcoin-friendly communities form. Temporary clusters are listed in [[Bitcoin Wiki:Community_portal#Events|events]]. Permanent communities include:

* [http://bitcointalk.org/index.php?topic=66832.0 Free State Project] New Hampshire
* [http://www.thebitcointrader.com/2012/05/bitcoins-hogwarts-san-francisco-tech.html 20 Mission] San Francisco, CA

== IRC ==

* See [[IRC_channels|IRC channels]]

==Wiki Users==

* [http://en.bitcoin.it/wiki/Special:ListUsers List of Users] registered on the Bitcoin wiki.

== Events ==
Periodic events where Bitcoin community meets include PorcFest, Chaos Computer Camp, Burning Man, Bitcoin conferences and more.

* [[Meetups]]
* [http://bitcointalk.org/index.php?topic=4526.0 Events, conferences and other events]

==Bitcoin Related Publications==

* [https://news.bitcoin.com/ Bitcoin News] articles and opinion pieces
* [http://twitter.com/TopNewsBitcoin/bitcoin TopNewsBitcoin/bitcoin] Twitter list
* See [[:Category:Blogs|Blogs]] category
* See [[:Category:Directories|Directories]] category
* See [[Press]]

==Education==

* [[:Category:Educational|Educational category]]

== Maps ==
* [http://coinmap.org/ CoinMap], collaborative map based on OpenStreetMap data and rendering
* [[Bitcoin.local]] Local exchanges
* [[Bitcoin Users Worldwide]] - Find nearby Bitcoin users • Engage in local trade • Add your own offers • Get notifications

== Merchants ==
*[https://localbitcoins.com/ LOCALBITCOINS] Buy and sell bitcoins near you, Instant. Secure. Private , Trade bitcoins in 13633 cities and 248 countries

== Monitoring ==
*[https://markets.blockchain.info/ BLOCKCHAIN.INFO] News and market data for the Bitcoin ecosystem.
* [http://bitcoinchain.com/ BitcoinChain.com] provides Bitcoin Block Explorer, Exchange Markets, Mining Pools Data.
* [http://bitcoincharts.com/markets/ Bitcoin Charts] displays an overview of Bitcoin exchange markets.
* [https://www.cryptocompare.com/coins/btc/overview/USD CryptoCompare.com] Overview, Forum, Live Streaming Markets, Charts and Trades.
* The [http://www.bitcoinmonitor.com/ Bitcoin Monitor] visualizes transactions, new blocks and trades on markets as they are happening.
* [http://www.bitcoinwatch.com/ Bitcoin Watch] has various statistics on things like the size of the economy or the number of transactions.
* [http://bitcoinx.io/ BitcoinX.io] monitors and displays Bitcoin exchanges and Bitcoin wallets with rankings and tools.
*[https://blockchain.info/ BLOCKCHAIN.INFO - NORMAL] Discover the world's most popular Bitcoin wallet. View detailed information and charts on all Bitcoin transactions and blocks. Visit today.

== Portfolio ==
* [http://cointracking.info CoinTracking.info (formerly my-btc.info)] A free profit/loss portfolio manager and tax tool for Bitcoin and over 3000 Altcoins.
* [http://myBitWorth.com myBitWorth] - allows you to track your bitcoin holdings over multiple addresses and portfolios on the bitcoin securities exchanges.

== Bitcoin Project ==
* [http://www.bitcoin.org Bitcoin.org] Bitcoin.org project site
* [https://github.com/bitcoin GitHub] Bitcoin project site
* [[:Category:Developer|Developer]] pages

== Non-profit Organizations ==

* [[List_of_Bitcoin_non-profits_around_the_world|List of Bitcoin non-profits around the world]]

== External Communities ==
* [http://www.etsy.com/teams/10366/bitcoin Bitcoin team] on Etsy, an e-commerce website focused on handmade or vintage items.
* [http://steamcommunity.com/groups/bitcoin Bitcoin group on Steam] platform by Valve, a gaming platform.
* [http://www.rugatu.com/ Rugatu], a Q&A community.
* [https://www.quora.com/topic/Bitcoin Quora] Bitcoin topic Q&A community.

Amir Taaki

2017-05-30T13:50:40Z

Lclc: Moved Darkwalelt and Darkleaks to inactive creations

==Active Creations==
* [[BIP]] process and several proposals
* [[Libbitcoin]] C++ developer toolkit
* [[Obelisk]] blockchain server (later [[Libbitcoin_Server|Bitcoin Server (bs)]])
* [[SubvertX|SubvertX (sx)]] Bitcoin command line application (later [[Libbitcoin_Explorer|Bitcoin Explorer (bx)]])
* [http://www.wired.com/2014/04/darkmarket Darkmarket] (later [https://openbazaar.org OpenBazaar])
* [[Freecoin]]
* [[Pastecoin]]

==Defunct or Inactive Creations==
* [[Britcoin]] exchange
* [[Intersango]] exchange
* [[Spesmilo]] RPC client
* [[Bitcoin Consultancy]]
* Bitcoin Media Blog author
* [[Vibanko]] web wallet provider
* [[GLBSE]] exchange client
* [https://github.com/genjix/kartludox Kartludox] Bitcoin poker room<ref>[http://forumserver.twoplustwo.com/28/internet-poker/rake-free-open-poker-room-run-poker-community-938389 Rake-Free & Open Poker Room, Run By the Poker Community?]</ref>
* Python bindings for bitcoin 
* [https://bitcoinmagazine.com/7892/shedding-light-on-the-dark-wallet Darkwallet]
* [http://reason.com/blog/2015/02/24/darkleaks-the-decentralized-information Darkleaks]

==See Also==
* [[User:Genjix]]
* [[Developers]]
* [[People]]
* [https://en.wikipedia.org/wiki/Amir_Taaki Wikipedia profile]

==References==
[[Category:People]]

Gavin Andresen

2017-05-30T13:47:26Z

Lclc: Change to past

{{infobox person|name=Gavin Andresen|image=[[File:Gavin Andresen.jpg|256px]]
|active=2010–present
|born=1966 (aged 48–49)
|residence=Amherst, Massachusetts
|twitter=gavinandresen
|reddit=gavinandresen
|bitcoinwiki=Gavinandresen
|bitcointalk=224
}}'''Gavin Andresen''' was the Chief Scientist for the [[Bitcoin_Foundation|Bitcoin Foundation]].

==References==
<references/>

{{s-start|Bitcoin [[Core maintainer]]|[[Satoshi Nakamoto]]|2011–2014|[[Wladimir J. van der Laan]]}}
{{developers}}{{stub}}

[[Category:Core committers]]
[[Category:Core developers]]
{{wp|Gavin_Andresen}}

Jeff Garzik

2017-05-30T13:44:15Z

Lclc: Update to past

{{infobox person|name=Jeff Garzik|image=[[File:Jgarzik.jpg|256px]]
|active=2010–present
|residence=Atlanta, Georgia
|twitter=jgarzik
|reddit=jgarzik
|bitcoinwiki=Jgarzik
|bitcointalk=541
}}'''Jeff Garzik''', Co-Founder of [http://bloq.com/ Bloq Inc], was a [https://github.com/bitcoin/bitcoin/commits?author=jgarzik contributor to Bitcoin Core].
==References==
<references/>

{{developers}}{{stub}}

[[Category:Core committers]]
[[Category:Core developers]]
{{wp|Jeff Garzik}}

OP RETURN

2016-10-07T11:13:07Z

Lclc: Fix Link to code

'''OP_RETURN''' is a [[script]] opcode used to mark a transaction output as invalid. Since the data after OP_RETURN are irrelevant to Bitcoin payments, arbitrary data can be added into the output after an OP_RETURN. Since any outputs with OP_RETURN are provably unspendable, OP_RETURN outputs can be used to [[Proof of burn|burn]] bitcoins.

Currently, the default Bitcoin client relays OP_RETURN transactions up to 80 bytes [https://github.com/bitcoin/bitcoin/search?utf8=%E2%9C%93&q=MAX_OP_RETURN_RELAY], but does not provide a way for users to create OP_RETURN transactions.

== Is storing data in the blockchain acceptable? ==
Some members of the Bitcoin community believe that use of OP_RETURN violates the contract of Bitcoin, because Bitcoin was intended to provide a record for financial transactions, not a record for arbitrary data. Despite this, use of OP_RETURN may continue unabated because there is no easy way to stop people from embedding arbitrary data in the blockchain if they want to, and OP_RETURN is reasonably efficient in terms of [http://i.imgur.com/VAGZWBK.png data bytes stored as a fraction of blockchain space consumed]. Compared to some other ways of storing data in the blockchain, OP_RETURN has the advantage of not creating bogus UTXO entries. [https://github.com/bitcoin/bitcoin/pull/5286 Discussion on GitHub pull request]

From [https://bitcoin.org/en/release/v0.9.0#opreturn-and-data-in-the-block-chain Bitcoin Core release 0.9.0]:
<blockquote>
This change is not an endorsement of storing data in the blockchain. The OP_RETURN change creates a provably-prunable output, to avoid data storage schemes – some of which were already deployed – that were storing arbitrary data such as images as forever-unspendable TX outputs, bloating bitcoin's UTXO database.

Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere.
</blockquote>

== OP_RETURN applications ==
OP_RETURN is used for writing human-language messages, digital asset proof-of-ownership, and storing data. Its use has been proposed for P2P application discovery. See the "prefixes" table below.

== OP_RETURN prefixes ==
Often, OP_RETURN transactions include a prefix to identify which protocol they belong to. There is no standardized method of claiming OP_RETURN prefixes, and not all OP_RETURN transactions use prefixes. At the time of writing, this wiki page is probably the most complete list of OP_RETURN prefixes. Note that this table is an attempt to catalog OP_RETURN prefixes that are already in use, *not* a system for reserving OP_RETURN prefixes!

{| class="wikitable"
|-
! Prefix !! Protocol
|-
| SPK || [http://coinspark.org/developers/ CoinSpark]
|-
| DOCPROOF || [http://www.proofofexistence.com/ Proof of Existence]
|-
| CryptoTests- || [http://crypto-copyright.com/ Crypto Copyright]
|-
| CryptoProof- || [http://crypto-copyright.com/ Crypto Copyright]
|-
| BS || [http://blocksignit.com/ BlockSign]
|-
| OA || [https://github.com/OpenAssets/open-assets-protocol/blob/master/specification.mediawiki Open Assets]
|-
| STAMPD## || [http://stampd.io/ stampd]
|-
| Factom!! || [http://factom.org/ Factom]
|-
| FACTOM00 || [http://factom.org/ Factom]
|-
| Fa || [http://factom.org/ Factom]
|-
| FA || [http://factom.org/ Factom]
|-
| tradle || [http://tradle.io/ Tradle]
|-
| LaPreuve || [http://www.lapreuve.net/ LaPreuve]
|-
| hex:5888 || [http://blog.onename.com/blockstore-bitcoin/ Blockstore]
|-
| hex:5808 || [http://blog.onename.com/blockstore-bitcoin/ Blockstore]
|-
| id || [http://blog.onename.com/blockstore-bitcoin/ Blockstore]
|-
| BITPROOF || [https://bitproof.io/ Bitproof]
|-
| S1 || [https://stampery.co/ Stampery]
|-
| S2 || [https://stampery.co/ Stampery]
|-
| S3 || [https://stampery.co/ Stampery]
|-
| S4 || [https://stampery.co/ Stampery]
|-
| S5 || [https://stampery.co/ Stampery]
|-
| ASCRIBE || [https://www.ascribe.io/ Ascribe]
|-
| ProveBit || [https://github.com/thereal1024/ProveBit ProveBit]
|-
| EW || [http://eternitywall.it/ Eternity Wall]
|-
| CC || [http://colu.co/ Colu]
|-
| omni || [http://www.omnilayer.org/ Omni Layer]
|-
| MG || [http://monegraph.com/ Monegraph]
|-
| RMBd || [https://app.remembr.io/ Remembr]
|-
| RMBe || [https://app.remembr.io/ Remembr]
|-
| ORIGMY || [http://originalmy.com/ OriginalMy]
|-
| BID || [http://bitpos.me/ Identity]
|}

== External resources on OP_RETURN ==
=== Viewing OP_RETURN ===
* [http://coinsecrets.org/ coinsecrets.org]: An OP_RETURN transaction explorer]
* [http://bitcoinstrings.com/ bitcoinstrings.com]: A site showing raw strings in Bitcoin transactions

=== Explaining OP_RETURN ===
* [https://github.com/coinspark/python-OP_RETURN python-OP_RETURN]
* [http://bitcoin.stackexchange.com/questions/29554/explanation-of-what-an-op-return-transaction-looks-like StackExchange: Explanation of what an OP_RETURN transaction looks like]
* [http://www.slideshare.net/coinspark/bitcoin-2-and-opreturns-the-blockchain-as-tcpip Metadata in the Blockchain: The OP_RETURN Explosion]
* [http://wlangiewicz.com/blog/2014/10/24/how-to-put-custom-messages-into-bitcoin-blockchain-op-return/ How to Put Custom Messages Into Bitcoin Blockchain - OP_RETURN]
{{DISPLAYTITLE:OP_RETURN}}

PHP developer intro

2015-03-31T14:12:42Z

Lclc: There is no RPC client functionality in bitcoind anymore. Use the bitcoin-cli utility instead.

'''L'''inux '''A'''pache '''M'''ySQL '''P'''HP + Bitcoin tutorial.

For this introduction we assume that you have GNU/Linux server with Apache and PHP and that you wish to interact with the Bitcoin network from a web application. We assume some knowledge of Bitcoin and experience in PHP.

While this is written for PHP, the same principles apply for other languages. See the associated [[API reference (JSON-RPC)|API reference]] pages for info on other languages.

The easiest way to get started is to run Bitcoin in daemon mode with which PHP communicates via local HTTP requests. A library called [http://jsonrpcphp.org/ JSON-RPC] is used to call the various functions of bitcoind, which will respond back with a [http://en.wikipedia.org/wiki/Json JSON object].

It is however recommended to use one of the [[#Alternative_Libs_For_RPC|Alternative Libraries]] listed below instead, since they are more sophisticated.

== Setting up Bitcoin ==

You can download the Bitcoin daemon from the [[Main_Page|homepage]] and run one of the included binaries or compile your own from the included source code. See [[Running Bitcoin]] for details on configuring bitcoind.

Before running bitcoind you will need to create a configuration file in the Bitcoin data directory (~/.bitcoin/bitcoin.conf on Linux):
<source lang="bash">
rpcuser=user
rpcpassword={you MUST pick a unique password to be secure}
</source>
If you miss this step, bitcoind will remind you.

Now run bitcoind:
<source lang="bash">
$ ./bitcoind
# wait a few seconds for it to start up
$ ./bitcoin-cli getinfo
# various information will be shown. If you get an error, try again until you see some useful output.
$ ./bitcoin-cli help
# get help on commands, note no dash before help
</source>

Bitcoin will begin synchronizing with the network and downloading a complete copy of the block chain. As of August 2012, more than 2gb of data must be downloaded and verified during this process. It may take two or more hours to complete. You will know when it's done when the block count reaches the [http://blockexplorer.com/q/getblockcount current count].

== Getinfo (Bitcoind's version of Hello World) ==

Assuming Bitcoin has finished the initialisation process; download the file jsonRPCClient.php from [http://jsonrpcphp.org/ JSON-RPC PHP] and place it in a web-accessible location.

Second, create a PHP file with the following and visit it with your browser to test.

<source lang="php">
require_once 'jsonRPCClient.php';

$bitcoin = new jsonRPCClient('http://user:password@127.0.0.1:8332/');

echo "<pre>\n";
print_r($bitcoin->getinfo());
echo "</pre>";
</source>

'''Note:''' The jsonRPCClient library uses fopen() and will throw an exception saying "Unable to connect" if it receives a 404 or 500 error from bitcoind. This prevents you from being able to see error messages generated by bitcoind (as they are sent with status 404 or 500). The [[#Alternative_Libs_For_RPC|Alternative Libraries]] listed below are similar in function to JSON-RPC PHP but do not have this issue.

== Precision ==

Bitcoin amounts can range from 1 Satoshi (0.00000001 BTC) to nearly 2,100,000,000,000,000 (21,000,000 BTC). To avoid rounding errors, you must make sure your PHP implementation supports the full range of Bitcoin values without losing precision. Most PHP implementations use IEEE 64-bit double-precision floating point numbers with 53 bits of precision, which is enough to correctly represent the full range of bitcoin values.

See [[Proper Money Handling (JSON-RPC)]] for more information.

If your PHP implementation does not support 64-bit numbers (again, this is very rare), you must use a version of bitcoind that sends values as strings (genjix maintains a fork at http://github.com/genjix/bitcoin) and use the [http://php.net/manual/en/ref.gmp.php GMP] and [http://php.net/manual/en/ref.bc.php BC Math] libraries for all calculations involving bitcoin amounts.

== Accounts ==

In Bitcoin, money is sent to addresses and many addresses can be held by one wallet. The balance shown by default in bitcoind is the sum of the bitcoins in all the addresses in the wallet.

Bitcoin goes another step. You can have [[Accounts explained|accounts]]. Each account holds multiple addresses and acts like a mini-bitcoind.

<source lang="bash">
$ ./bitcoin-cli listaccounts
# show list of accounts and various info for each one
$ ./bitcoin-cli getaccountaddress user889
# get an address to receive money to that is unique for the account user889
$ ./bitcoin-cli getbalance user889
# get the sum of all the money in the addresses owned by the account user889
</source>

In your application, each user should have a unique username. You may then query bitcoind for a unique address using $bitcoin->getaccountaddress("user889"); [gets the first address for user889] or $bitcoin->getnewaddress("user889"); [creates a new address for user889].

The customer then deposits to this address.

You can check the funds for that customer by doing $bitcoin->getbalance("user889", 4);. The 4 indicates the minimum number of confirmations we will accept before assuming this payment is valid.

If you will be using accounts for multiple deposits and withdrawals long-term, you may want to consider tracking user balances in your own database. This simplifies transfers between your application's accounts and decouples your accounts from the Bitcoin wallet.

=== getnewaddress vs getaccountaddress ===

Using getnewaddress helps increase maintain anonymity of your users by making it hard for a malicious agent to track payments flowing through your application. Running getnewaddress too often, however, will cause your wallet to become filled with many empty addresses.

It is therefore recommended to in some way limit the number of unfunded addresses each user can request. Here is an example using sessions:
<source lang="php">
<?php
require_once('jsonRPCClient.php');
$bitcoin = new jsonRPCClient('http://root:root@127.0.0.1:8332/');
# now check for appropriate funds in user account
try {
$username = ...
if(isset($_SESSION['sendaddress']))
$sendaddress = $_SESSION['sendaddress'];
else {
$sendaddress = $bitcoin->getnewaddress($username);
$_SESSION['sendaddress'] = $sendaddress;
}
$balance = $bitcoin->getbalance($username);
}
catch (Exception $e) {
die("Server error! Please contact the admin.");
}
?>
</source>

This creates a new address at the beginning of every new session, and stores it in the session variable.

==Alternative Libs For RPC==
There are alternative PHP libraries for connecting to the bitcoind RPC which are recommended over using the plain jsonRPCClient.php class.
They do not rely on magic __call, use cURL instead of fopen and have better error handling (and can be installed using composer).

* [https://github.com/nbobtc/bitcoind-php NboBTC Bitcoind-PHP]
* [https://github.com/aceat64/EasyBitcoin-PHP EasyBitcoin-PHP]

==See Also==

* [[API reference (JSON-RPC)]]
* [[Lazy_API]]
* [https://github.com/cryptoapi/Payment-Gateway Bitcoin-PHP Payment library]
* [[Merchant Howto]]
* [[https://github.com/Bit-Wasp/bitcoin-lib-php Bitcoin-Lib-PHP - PHP Lib implementing signing of transactions, BIP32, etc]]

[[es:Introducción para desarrolladores de PHP]]
[[de:Einführung_für_PHP-Entwickler]]

[[Category:Developer]]

API reference (JSON-RPC)

2015-01-05T22:40:36Z

Lclc: Add QJsonRpc example (Qt/C++ lib)

== Controlling Bitcoin ==

Run ''bitcoind'' or ''bitcoin-qt -server''. You can control it via the command-line bitcoin-cli utility or by [http://json-rpc.org/wiki/specification HTTP JSON-RPC] commands.

You must create a bitcoin.conf configuration file setting an rpcuser and rpcpassword; see [[Running Bitcoin]] for details.

Now run:
$ ./bitcoind -daemon
bitcoin server starting
$ ./bitcoin-cli -rpcwait help
# shows the help text

A [[Original Bitcoin client/API Calls list|list of RPC calls]] will be shown.

$ ./bitcoin-cli getbalance
2000.00000

If you are learning the API, it is a very good idea to use the test network (run bitcoind -testnet and bitcoin-cli -testnet).

== JSON-RPC ==

Running Bitcoin with the -server argument (or running bitcoind) tells it to function as a [http://json-rpc.org/wiki/specification HTTP JSON-RPC] server, but
[http://en.wikipedia.org/wiki/Basic_access_authentication Basic access authentication] must be used when communicating with it, and, for security, by default, the server only accepts connections from other processes on the same machine. If your HTTP or JSON library requires you to specify which 'realm' is authenticated, use 'jsonrpc'.

Bitcoin supports SSL (https) JSON-RPC connections beginning with version 0.3.14. See the [[Enabling SSL on original client daemon|rpcssl wiki page]] for setup instructions and a list of all bitcoin.conf configuration options.

Allowing arbitrary machines to access the JSON-RPC port (using the rpcallowip [[Running_Bitcoin|configuration option]]) is dangerous and '''strongly discouraged'''-- access should be strictly limited to trusted machines.

To access the server you should find a [http://json-rpc.org/wiki/implementations suitable library] for your language.

== Proper money handling ==

See the [[Proper Money Handling (JSON-RPC)|proper money handling page]] for notes on avoiding rounding errors when handling bitcoin values.

== Python ==

[http://json-rpc.org/wiki/python-json-rpc python-jsonrpc] is the official JSON-RPC implementation for Python.
It automatically generates Python methods for RPC calls.
However, due to its design for supporting old versions of Python, it is also rather inefficient.
[[User:jgarzik|jgarzik]] has forked it as [https://github.com/jgarzik/python-bitcoinrpc Python-BitcoinRPC] and optimized it for current versions.
Generally, this version is recommended.

While BitcoinRPC lacks a few obscure features from jsonrpc, software using only the ServiceProxy class can be written the same to work with either version the user might choose to install:

<source lang="python">
from jsonrpc import ServiceProxy

access = ServiceProxy("http://user:password@127.0.0.1:8332")
access.getinfo()
access.listreceivedbyaddress(6)
#access.sendtoaddress("11yEmxiMso2RsFVfBcCa616npBvGgxiBX", 10)
</source>

The latest version of python-bitcoinrpc has a new syntax.
<source lang="python">
from bitcoinrpc.authproxy import AuthServiceProxy
</source>

== Ruby ==

<source lang="ruby">
require 'net/http'
require 'uri'
require 'json'

class BitcoinRPC
def initialize(service_url)
@uri = URI.parse(service_url)
end

def method_missing(name, *args)
post_body = { 'method' => name, 'params' => args, 'id' => 'jsonrpc' }.to_json
resp = JSON.parse( http_post_request(post_body) )
raise JSONRPCError, resp['error'] if resp['error']
resp['result']
end

def http_post_request(post_body)
http = Net::HTTP.new(@uri.host, @uri.port)
request = Net::HTTP::Post.new(@uri.request_uri)
request.basic_auth @uri.user, @uri.password
request.content_type = 'application/json'
request.body = post_body
http.request(request).body
end

class JSONRPCError < RuntimeError; end
end

if $0 == __FILE__
h = BitcoinRPC.new('http://user:password@127.0.0.1:8332')
p h.getbalance
p h.getinfo
p h.getnewaddress
p h.dumpprivkey( h.getnewaddress )
# also see: https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list
end
</source>

== Erlang ==
Get the rebar dependency from https://github.com/edescourtis/ebitcoind . By default the client will use the configuration in <code>$HOME/.bitcoin/bitcoin.conf</code> or you can instead specify a URI like this:
<source lang="erlang">ebitcoind:start_link(<<"http://user:password@localhost:8332/">>).</source>

Here is a usage example:
<source lang="erlang">
1> {ok,Pid} = ebitcoind:start_link().
{ok,<0.177.0>}
2> ebitcoind:getbalance(Pid).
8437.02478294
3> ebitcoind:getinfo(Pid).
{ok, #{<<"balance">> => 8437.02478294,
<<"blocks">> => 260404,
<<"connections">> => 8,
<<"difficulty">> => 148819199.80509263,
<<"errors">> => <<>>,
<<"keypoololdest">> => 1420307921,
<<"keypoolsize">> => 102,
<<"paytxfee">> => 0.0,
<<"protocolversion">> => 70002,
<<"proxy">> => <<>>,
<<"relayfee">> => 1.0e-5,
<<"testnet">> => false,
<<"timeoffset">> => -3,
<<"version">> => 90300,
<<"walletversion">> => 60000}}
4> ebitcoind:setgenerate(Pid,true).
{ok, null}
5> ebitcoind:getblocktemplate(Pid, #{}).
{ok,#{<<"bits">> => <<"181b0dca">>,
<<"coinbaseaux">> => #{<<"flags">> => <<"062f503253482f">>},
<<"coinbasevalue">> => 2518690558,
<<"curtime">> => 1420421249,
<<"height">> => 337533,
<<"mintime">> => 1420416332,
<<"mutable">> => [<<"time">>,<<"transactions">>,<<"prevblock">>],
<<"noncerange">> => <<"00000000ffffffff">>,
<<"previousblockhash">> => <<"000000000000000017ce0a0d328bf84cc597785844393e899e9a971a81679a5f">>,
<<"sigoplimit">> => 20000,
<<"sizelimit">> => 1000000,
<<"target">> => <<"00000000000000001b0dca00000000000000000000000000000000000000"...>>,
<<"transactions">> => [#{<<"data">> => <<"01000000049b47ce225d29bff7c18b7df7d7df4693523a52"...>>,
<<"depends">> => [],
<<"fee">> => 0,
<<"hash">> => <<"6d0d76e1f27b3a6f7325923710dcdb4107c9"...>>,
<<"sigops">> => 1},
...
</source>

== PHP ==

The [http://jsonrpcphp.org/ JSON-RPC PHP] library also makes it very easy to connect to Bitcoin. For example:

<source lang="php">
require_once 'jsonRPCClient.php';

$bitcoin = new jsonRPCClient('http://user:password@127.0.0.1:8332/');

echo "<pre>\n";
print_r($bitcoin->getinfo()); echo "\n";
echo "Received: ".$bitcoin->getreceivedbylabel("Your Address")."\n";
echo "</pre>";
</source>

'''Note:''' The jsonRPCClient library uses fopen() and will throw an exception saying "Unable to connect" if it receives a 404 or 500 error from bitcoind. This prevents you from being able to see error messages generated by bitcoind (as they are sent with status 404 or 500). The [https://github.com/aceat64/EasyBitcoin-PHP EasyBitcoin-PHP library] is similar in function to JSON-RPC PHP but does not have this issue.

== Java ==

The easiest way to tell Java to use HTTP Basic authentication is to set a default Authenticator:

<source lang="java">
final String rpcuser ="...";
final String rpcpassword ="...";

Authenticator.setDefault(new Authenticator() {
protected PasswordAuthentication getPasswordAuthentication() {
return new PasswordAuthentication (rpcuser, rpcpassword.toCharArray());
}
});
</source>

Once that is done, [http://json-rpc.org/wiki/implementations any JSON-RPC library for Java] (or ordinary URL POSTs) may be used to communicate with the Bitcoin server.

Instead to write your wrapper you can use [[Bitcoin-JSON-RPC-Client|this implementation]] or [https://github.com/johannbarbie/BitcoindClient4J this one] .

== Perl ==

The JSON::RPC package from CPAN can be used to communicate with Bitcoin. You must set the client's credentials; for example:

<source lang="perl">
use JSON::RPC::Client;
use Data::Dumper;

my $client = new JSON::RPC::Client;

$client->ua->credentials(
'localhost:8332', 'jsonrpc', 'user' => 'password' # REPLACE WITH YOUR bitcoin.conf rpcuser/rpcpassword
);

my $uri = 'http://localhost:8332/';
my $obj = {
method => 'getinfo',
params => [],
};

my $res = $client->call( $uri, $obj );

if ($res){
if ($res->is_error) { print "Error : ", $res->error_message; }
else { print Dumper($res->result); }
} else {
print $client->status_line;
}
</source>

== Go ==

The [https://github.com/conformal/btcrpcclient btcrpcclient package] can be used to communicate with Bitcoin. You must provide credentials to match the client you are communicating with.

<source lang="go">
package main

import (
"github.com/conformal/btcnet"
"github.com/conformal/btcrpcclient"
"github.com/conformal/btcutil"
"log"
)

func main() {
// create new client instance
client, err := btcrpcclient.New(&btcrpcclient.ConnConfig{
HttpPostMode: true,
DisableTLS: true,
Host: "127.0.0.1:8332",
User: "rpcUsername",
Pass: "rpcPassword",
}, nil)
if err != nil {
log.Fatalf("error creating new btc client: %v", err)
}

// list accounts
accounts, err := client.ListAccounts()
if err != nil {
log.Fatalf("error listing accounts: %v", err)
}
// iterate over accounts (map[string]btcutil.Amount) and write to stdout
for label, amount := range accounts {
log.Printf("%s: %s", label, amount)
}

// prepare a sendMany transaction
receiver1, err := btcutil.DecodeAddress("1someAddressThatIsActuallyReal", &btcnet.MainNetParams)
if err != nil {
log.Fatalf("address receiver1 seems to be invalid: %v", err)
}
receiver2, err := btcutil.DecodeAddress("1anotherAddressThatsPrettyReal", &btcnet.MainNetParams)
if err != nil {
log.Fatalf("address receiver2 seems to be invalid: %v", err)
}
receivers := map[btcutil.Address]btcutil.Amount{
receiver1: 42, // 42 satoshi
receiver2: 100, // 100 satoshi
}

// create and send the sendMany tx
txSha, err := client.SendMany("some-account-label-from-which-to-send", receivers)
if err != nil {
log.Fatalf("error sendMany: %v", err)
}
log.Printf("sendMany completed! tx sha is: %s", txSha.String())
}
</source>

== .NET (C#) ==
The communication with the RPC service can be achieved using the standard http request/response objects.
A library for serialising and deserializing Json will make your life a lot easier:

Json.Net ( http://james.newtonking.com/json ) is a high performance JSON package for .Net. It is also available via NuGet from the package manager console ( Install-Package Newtonsoft.Json ).

The following example uses Json.Net:

<source lang="csharp">
HttpWebRequest webRequest = (HttpWebRequest)WebRequest.Create("http://localhost.:8332");
webRequest.Credentials = new NetworkCredential("user", "pwd");
/// important, otherwise the service can't desirialse your request properly
webRequest.ContentType = "application/json-rpc";
webRequest.Method = "POST";

JObject joe = new JObject();
joe.Add(new JProperty("jsonrpc", "1.0"));
joe.Add(new JProperty("id", "1"));
joe.Add(new JProperty("method", Method));
// params is a collection values which the method requires..
if (Params.Keys.Count == 0)
{
joe.Add(new JProperty("params", new JArray()));
}
else
{
JArray props = new JArray();
// add the props in the reverse order!
for (int i = Params.Keys.Count - 1; i >= 0; i--)
{
.... // add the params
}
joe.Add(new JProperty("params", props));
}

// serialize json for the request
string s = JsonConvert.SerializeObject(joe);
byte[] byteArray = Encoding.UTF8.GetBytes(s);
webRequest.ContentLength = byteArray.Length;
Stream dataStream = webRequest.GetRequestStream();
dataStream.Write(byteArray, 0, byteArray.Length);
dataStream.Close();

WebResponse webResponse = webRequest.GetResponse();

... // deserialze the response
</source>

There is also a wrapper for Json.NET called Bitnet (https://sourceforge.net/projects/bitnet)
implementing Bitcoin API in more convenient way:

<source lang="csharp">
BitnetClient bc = new BitnetClient("http://127.0.0.1:8332");
bc.Credentials = new NetworkCredential("user", "pass");

var p = bc.GetDifficulty();
Console.WriteLine("Difficulty:" + p.ToString());

var inf = bc.GetInfo();
Console.WriteLine("Balance:" + inf["balance"]);
</source>

A more complete library and wrapper for Bitcoin (also for Litecoin and all Bitcoin clones) is [https://github.com/GeorgeKimionis/BitcoinLib BitcoinLib] (https://github.com/GeorgeKimionis/BitcoinLib) which is also available via [https://www.nuget.org/packages/BitcoinLib/ NuGet] from the package manager console (Install-Package BitcoinLib).

Querying the daemon with [https://github.com/GeorgeKimionis/BitcoinLib BitcoinLib] is as simple as:

<source lang="csharp">
IBitcoinService bitcoinService = new BitcoinService();

double networkDifficulty = bitcoinService.GetDifficulty();
decimal myBalance = bitcoinService.GetBalance();
</source>

== Node.js ==

* [https://github.com/freewil/node-bitcoin node-bitcoin] (npm: bitcoin)

Example using node-bitcoin:

<source lang="javascript">
var bitcoin = require('bitcoin');
var client = new bitcoin.Client({
host: 'localhost',
port: 8332,
user: 'user',
pass: 'pass'
});

client.getDifficulty(function(err, difficulty) {
if (err) {
return console.error(err);
}

console.log('Difficulty: ' + difficulty);
});
</source>

Example using Kapitalize:

<source lang='javascript'>
var client = require('kapitalize')()

client.auth('user', 'password')

client
.getInfo()
.getDifficulty(function(err, difficulty) {
console.log('Dificulty: ', difficulty)
})
</source>

== Command line (cURL) ==

You can also send commands and see results using [http://curl.haxx.se/ cURL] or some other command-line HTTP-fetching utility; for example:

<source lang="bash">
curl --user user --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }'
-H 'content-type: text/plain;' http://127.0.0.1:8332/
</source>

You will be prompted for your rpcpassword, and then will see something like:

<source lang="javascript">
{"result":{"balance":0.000000000000000,"blocks":59952,"connections":48,"proxy":"","generate":false,
"genproclimit":-1,"difficulty":16.61907875185736,"error":null,"id":"curltest"}
</source>

== Clojure ==

[https://github.com/aviad/clj-btc clj-btc] is a Clojure wrapper for the bitcoin API.

<source lang="clojure">
user=> (require '[clj-btc.core :as btc])
nil
user=> (btc/getinfo)
{"timeoffset" 0, "protocolversion" 70001, "blocks" 111908, "errors" "",
"testnet" true, "proxy" "", "connections" 4, "version" 80500,
"keypoololdest" 1380388750, "paytxfee" 0E-8M,
"difficulty" 4642.44443532M, "keypoolsize" 101, "balance" 0E-8M,
"walletversion" 60000}
</source>

== Qt/C++ ==

[https://bitbucket.org/devonit/qjsonrpc/overview QJsonRpc] is a Qt/C++ implementation of the JSON-RPC protocol. It integrates nicely with Qt, leveraging Qt's meta object system in order to provide services over the JSON-RPC protocol. QJsonRpc is licensed under the LGPLv2.1.

<source lang="cpp">
/*
* Copyright (C) 2012-2013 Matt Broadstone
* Contact: http://bitbucket.org/devonit/qjsonrpc
*
* This file is part of the QJsonRpc Library.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*/
#include <QCoreApplication>
#include <QAuthenticator>
#include <QStringList>
#include <QDebug>

#include "qjsonrpchttpclient.h"

class HttpClient : public QJsonRpcHttpClient
{
Q_OBJECT
public:
HttpClient(const QString &endpoint, QObject *parent = 0)
: QJsonRpcHttpClient(endpoint, parent)
{
// defaults added for my local test server
m_username = "bitcoinrpc";
m_password = "232fb3276bbb7437d265298ea48bdc46";
}

void setUsername(const QString &username) {
m_username = username;
}

void setPassword(const QString &password) {
m_password = password;
}

private Q_SLOTS:
virtual void handleAuthenticationRequired(QNetworkReply *reply, QAuthenticator * authenticator)
{
Q_UNUSED(reply)
authenticator->setUser(m_username);
authenticator->setPassword(m_password);
}

private:
QString m_username;
QString m_password;

};

int main(int argc, char **argv)
{
QCoreApplication app(argc, argv);
if (app.arguments().size() < 2) {
qDebug() << "usage: " << argv[0] << "[-u username] [-p password] <command> <arguments>";
return -1;
}

HttpClient client("http://127.0.0.1:8332");
if (app.arguments().contains("-u")) {
int idx = app.arguments().indexOf("-u");
app.arguments().removeAt(idx);
client.setUsername(app.arguments().takeAt(idx));
}

if (app.arguments().contains("-p")) {
int idx = app.arguments().indexOf("-p");
app.arguments().removeAt(idx);
client.setPassword(app.arguments().takeAt(idx));
}

QJsonRpcMessage message = QJsonRpcMessage::createRequest(app.arguments().at(1));
QJsonRpcMessage response = client.sendMessageBlocking(message);
if (response.type() == QJsonRpcMessage::Error) {
qDebug() << response.errorData();
return -1;
}

qDebug() << response.toJson();
}
</source>

== See Also==

* [[Original_Bitcoin_client/API_Calls_list|API calls list]]
* [[Running Bitcoin]]
* [[Lazy API]]
* [[PHP developer intro]]
* [[Raw_Transactions|Raw Transactions API]]
* [https://gourl.io/bitcoin-payment-gateway-api.html GoUrl Bitcoin PHP Payment API]
* [http://blockchain.info/api/json_rpc_api Web Based JSON RPC interface.]

[[Category:Technical]]
[[Category:Developer]]
[[zh-cn:API_reference_(JSON-RPC)]]

Meetups

2013-08-27T12:22:49Z

Lclc: The Google group isn't actively in use anymore

Don't add everyone who's going in the "Who?" column, just prominent Bitcoin members and organizers. Also see [http://bitcoin.meetup.com bitcoin.meetup.com]. Also see [[Conferences]].

Keep an eye on the [http://bitcointalk.org/index.php?board=86.0 Meetups] forum board on BitcoinTalk for announcements.

{| class="wikitable"
|-
! Group
! When?
! Where?
! Who?
! Other Notes
|-
| [http://www.meetup.com/Sydney-Bitcoin-Users-Group/ BitcoinSYD]
| Every Wednesday @ 1800
| [http://www.gposydney.com/GPO-SYDNEY-BARS-AND-CLUB-6.html GPO Bar], Downstairs, George St end. Look for the guy in the Red Cap.
| Local, National and International peeps looking to Talk and Trade Bitcoin
| We also post our meetups on Reddit and [https://www.facebook.com/pages/Bitcoin-Sydney-Australia/457681220943285 Facebook]
|-
|-
| [https://bitcointalk.org/index.php?topic=27191.0;all Bitcoin Stammtisch]
| each first Thursday of the month
| [http://www.room77.de/ Room 77], Gräfestr. 77, Berlin-Kreuzberg
| Anyone interested in Bitcoin: technically, economically, socially or philosophically.
| If questions contact andreas(at)schildbach.de (founder).
|-
|-
| [http://www.meetup.com/bitcoins/ Bitcoin NYC]
| monthly
| [http://www.xcubicle.com/ xCubicle Hackerspace - New York, NY]
| Any and all Bitcoin aficionados.
|
|-
|-
| [https://en.bitcoin.it/wiki/Bitcoin_Wednesday Bitcoin Wednesday Amsterdam]
| First Wednesday of the Month
| [http://lanyrd.com/2013/bitcoinamsterdam/ Sign Up - Amsterdam, The Netherlands]
| Open to anyone interested in Bitcoin.
| [https://www.PikaPay.com PikaPay.com @PikaPay or hello-AT-PikaPay.com]
|-
|-
| [http://hitspace.org/ HIT Space - Hack it Together]
| monthly
| [http://hitspace.org/where-we-are/ HIT Space - Porto, Portugal]
| Hackerspace members and anyone who want to join us
| send us an email geral[at]hitspace.org
|-
|-
| [http://bitcoin-austria.at Bitcoin Austria]
| monthly - check the [http://bitcoin-austria.at wiki] or subscribe to the [http://lists.bitcoin-austria.at/listinfo/bitcoin mailinglist]
| [https://metalab.at/wiki/Lage Metalab], Vienna hacker space, Rathausstraße 6, 1010 Wien
| Everybody interested in Bitcoin
|
|-
| [http://brmlab.cz brmlab, prague hackerspace]
| 14th Nov 2011
28th Nov 2011
([http://brmlab.cz/event/bitcoin_seminar])
| [http://brmlab.cz/place Brmlab, Bubenska 1]
| brmlab crew, slush, genjix
|
|-
| [http://www.facebook.com/groups/175596065827848/ Bitcoin Boston]
| Every Friday at 4:30 and bi-weekly on Saturday or Sunday ([http://www.facebook.com/groups/175596065827848/ See Facebook page])
| Starbucks in Kendall Square (Ames St & Broadway) and bi-weekly at Starbucks in Harvard Square
| Anyone is welcome!
| Our bi-weekly meetings have been somewhat sporadic but we aim to gain some regularity.
|-
| [http://www.meetup.com/Milwaukee-Area-Bitcoin-Meetup/ Milwaukee Area Bitcoin Meetup]
| Every other Thursday at 6:00pm
| 17025 West Rogers Drive, New Berlin WI
| Open to anyone interested in Bitcoin
| [https://www.facebook.com/groups/BTCMKE Milwaukee Area Bitcoin Meetup Facebook]
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 6:00 PM, 3rd Sunday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])
| OnlyOneTV Studios - 290 Fifth Ave New York, NY
| Bruce Wagner (Organizer) and others
|
|-
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 6:00 PM, every Wednesday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])
| Just Sweet Dessert House - 83 Third Ave New York, NY
| Yifu Guo (Organizer) and crew
| hosted by Bitsyncom, the people behind [[Bitnavigator]], walk-ins welcome;
|-
|[http://www.meetup.com/MichiganBitcoinMeetup Michigan Bitcoin Meetup]
|
|
|Kinnard Hockenhull (Organizer)
|Sponsored by [[BitBox]]
|-
| [http://www.meetup.com/PhillyBitcoin Philadelphia Bitcoin User Group]
| TBD
| TBD
| Brian Cohen (Organizer) and others
|
|-
| [http://www.meetup.com/BitcoinDC Washington, DC Bitcoin Users]
| 7:00 PM, 1st Monday of every month ([http://www.meetup.com/BitcoinDC/#past past meetings])
| Northside Social, 3211 Wilson Blvd Arlington, VA
| [[User:Dduane|Darrell Duane]] (Organizer) and others
|
|-
| [http://www.meetup.com/Silicon-Valley-Bitcoin-Users Silicon Valley Bitcoin Users]
| 7:00 PM, Tuesday, June 14, 2011 ([http://www.meetup.com/Silicon-Valley-Bitcoin-Users/events/past past meetings])
| 140B S Whisman Road Mountain View, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/BitcoinChicago Chicago]
| No regular schedule yet ([http://www.meetup.com/BitcoinChicago/events/past past meetings])
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA
| Igor
|
|-
| [http://www.meetup.com/denver-bitcoin Denver]
| First meeting June 4th, 2011 ([http://www.meetup.com/denver-bitcoin/events/past past meetings])
| Gypsy House Cafe - 1279 Marion St Denver, CO
| bearbones
|
|-
| [http://www.meetup.com/bitcoinSF Bitcoin SF]
| Saturday, June 4, 2011 ([http://www.meetup.com/bitcoinSF past meetings])
| SFSU - 1600 Holloway Ave. San Francisco, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/Los-Angeles-Digital-Currency-Innovators-Group Los Angeles Digital Currency Innovators]
| Thursday July 7th, 2011, 7 PM
| (mt)/Media Temple, Culver City, CA
| [[User:sgornick|Stephen Gornick]] (Interim organizer) and others
| Seeking meetup coordinator
|-
| [http://Hackerish.org Las Vegas Crypto Party]
| 3rd Thursday 7pm. [http://BitcoinsInVegas.com Weekly Wednesday lunch mobs]
| /Usr/Lib @ The Beat Coffee House, 520 Fremont, 2nd floor, Las Vegas, NV
| Julian Tosh / Tuxavant
|
|-
| [https://www.facebook.com/groups/195492163844669/ Free State Bitcoin Consortium]
| Every Saturday, at 6:30 PM
| Strange Brew Tavern, Manchester, NH
| ben-abuya (organizer)
| Weekly
|-
| [https://www.facebook.com/groups/195492163844669/ Twin Cities Users]
| Friday, June 10, 2011, 6:30 PM
| Joule - 1200 Washington Ave S Minneapolis, MN
| Mac Manson
|
|-
| [http://www.meetup.com/Portland-Bitcoin-Meetup-Users Portland Bitcoin Users Meetup Group]
| forming
|
| Steven Wagner
|
|-
| [http://www.meetup.com/Bitcoin-Orlando Bitcoin Orlando]
| ([http://www.meetup.com/Bitcoin-Orlando#past past meetings])
| Frank & Steins 150 S. Magnolia Ave, Orlando, FL
| Antonio Gallippi
|
|-
| [http://www.hive13.org/?p=310 Hive13 Hackerspace]
| Bitcoin Exchange, Every Tuesday, 7:30 PM
| Hive13 - 2929 Spring Grove Avenue, Cincinnati, OH
|
|
|-
| [https://www.facebook.com/bitcoinaus Bitcoin Australia]: Melbourne
| [https://www.facebook.com/events/345430765511234/ Wednesday, 23 May 2012, 18:45]
| Melbourne CBD(TBA)
| Facebook, IRC, Bitcointalk Forum...
|
|-
| [[Bitcoin:Tokyo meetup|Tokyo]]
| Usually first monday of the month
| Shibuya
| Roger Ver (Organizer) and others
|
|-
| [http://meetup.com/Bitcoin-Canada Vancouver Canada]
| ([http://www.meetup.com/Bitcoin-Canada/#past past meetings])
| The Brickhouse - 730 Main St.
| humble (and others)
|
|-
| [https://plus.google.com/u/0/communities/113055238568417913658 Zurich / Geneva Switzerland]
| Twice a month
| Kennedy's Irish Pub, Zurich; Lord Nelson Pub, Geneva
| Stefan Thomas (WeUseCoins), Mike Hearn (BitcoinJ), bitdragon, Luzius (Wuala), more ...
|
|-
| Seattle Bitcoin Meetup
| [http://www.meetup.com/SeattleBitCoin/ Semi-regularly].
| [http://maps.google.com/maps?q=cafe+solstice&daddr=4116+University+Way,+Seattle,+WA+98105-6214&hl=en&ll=47.657424,-122.31313&spn=0.007328,0.01929&gl=us&view=map&geocode=CRT9Bdg7zX3vFdcx1wIdWqa1-CFcJ9qrr9CcEQ&t=h&z=16 Solstice Cafe, 2pm]
| [https://bitcointalk.org/index.php?action=profile;u=36217 indolering]
|
|-
| [https://bitcointalk.org/index.php?topic=135723.0 Munich Germany]
| First wednesday of the month, 6:00PM
| [http://www.openstreetmap.org/?minlon=11.5800867080688&minlat=48.1336479187012&maxlon=11.5804319381714&maxlat=48.1338386535645 Nero Pizza], Rumfordstrasse 34, 80469 München
| Bitcoin-users from Munich and around
| [http://www.meetup.com/Bitcoin-Munchen/ @meetup.com]
|-
| [http://www.meetup.com/bitcoin-il/ Israel Bitcoin Meetup Group]
| Occasional
| TBD
| Meni Rosenfeld
|
|-
| [http://www.meetup.com/Dallas-Bitcoin-User-Meetup/ Dallas Bitcoin Meetup Group]
| Biweekly on Saturdays, 6:00PM
| [http://freemandallas.com/ The Free Man Cajun Cafe]
| Justus Ranvier (organizer)
|
|-
| [https://en.bitcoin.it/wiki/Cafe Café Bitcoin Sevilla]
|
| Seville, Spain
| Randy Brito (rdymac / btcven), Eduardo (bitcoin.com.es), Jorge and Alfredo
| http://cafebitcoin.com
|-
|}

==See Also==

* [http://hackerspaces.org/wiki/List_of_Hacker_Spaces List of Hacker Spaces]
* [http://bitimap.net Bitimap.net - Find local meetups (up-to-date)]

[[Category:Local]]
[[Category:Meetups]]

[[de:Treffen]]