Bitcoin Wiki - User contributions [en]

Bech32 adoption

2021-11-15T17:43:22Z

Goonie: Bitcoin Wallet 9.0 supports Send to P2TR

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Yes|Since 2.2.0}} || {{Evaluating|??}} ||
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Evaluating|??}} ||
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|Depends on python-bitcointx}} || {{Evaluating|??}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Yes|Since 9.0}} || {{Evaluating|??}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Muun || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/MuunWallet/status/1459294066135474177
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Planned|Planned: via btcsuite}} || {{Evaluating|??}} ||
|-
| Exodus || {{Yes}} || {{Yes}} || {{Planned|Planned before activation, depends on bitcoinjs}} || {{No|Not yet planned}} ||
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor + Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: in December update}} || {{Planned|Planned: in December update}} || https://btc1.trezor.io/tx/350bb4ff380240fee0d2b7e1f7b90e719086de263cd02aedca105aec0c0bccc1
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Ledger Live Desktop 2.35 + Bitcoin App 2.0.0, Ledger Live Mobile support TBD. https://blockstream.info/tx/41d46e6f6e58a325eb6c913aa603f4db313f4a1db0649952f06fe2cd70546451
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|}

=== Web Wallets / Wallet Service Providers ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Full native segwit support on v2 platform, no plans to add native segwit support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9, Taproot: https://blog.bitgo.com/taproot-support-for-bitgo-wallets-9ed97f412460
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| Fireblocks || {{Yes}} || {{Yes}} || {{Planned|Nov 18, 2021}} || {{Planned|Planned for 2022}} ||
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://blog.bitmex.com/introducing-bech32-deposits-on-bitmex-to-deepen-bitcoin-integration-lower-fees/
|-
| Bitonic || {{Yes}} || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || https://twitter.com/BitcoinenNL/status/1460284373291384833
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Evaluating|??}} || {{No}} ||
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinfloor || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinfloor.zendesk.com/hc/en-us/articles/360018072678-Why-are-there-2-BTC-deposit-addresses-to-choose-from-
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Planned|Planned}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Acceptable|Working on Android, coming soon on iOS}} || {{Evaluating|??}} ||
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc1.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Yes|Ready, but old txns not reindexed yet}} || {{Yes|Ready, but old txns not reindexed yet}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-966393097, https://twitter.com/Blockchair/status/1458817396433731585
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OKLink || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.oklink.com
|-
| OXT || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Planned|In Review}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Yes|Since v6.0.0}} || {{Acceptable|Supported but needs manual involvement}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902, https://twitter.com/junderwood4649/status/1459006392086372355
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2021}} || https://twitter.com/Chris_Stewart_5/status/1459205497463136270
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://docs.rs/bdk
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/chaintope/bitcoinrb Bitcoinrb] || Ruby || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/chaintope/bitcoinrb/wiki/Taproot
|}


=== References ===

[[Category:Software]]

Bech32 adoption

2021-10-06T21:13:48Z

Goonie: /* Libraries */

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Evaluating|??}} ||
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|Depends on python-bitcointx}} || {{Evaluating|??}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Planned|Planned: via GDK before activation}} || {{Evaluating|??}} ||
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Planned|Planned before activation}} || {{Evaluating|??}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Muun || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Planned|After activation}} || https://twitter.com/MuunWallet/status/1415692517690023937
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Planned|Planned: via GDK before activation}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Planned|Planned: via btcsuite}} || {{Evaluating|??}} ||
|-
| Exodus || {{Yes}} || {{Yes}} || {{Planned|Planned before activation, depends on bitcoinjs}} || {{No|Not yet planned}} ||
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: before Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Planned|Planned: at activation}} || {{Planned|Planned: at activation}} || [https://twitter.com/darosior/status/1432371465815568390 Announced at Surfin' Bitcoin]
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: before Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Planned|Planned: via GDK before activation}} || {{Evaluating|??}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Planned|Before activation|}} || {{Evaluating|??}} || Full support on v2 platform, no plans to add support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://blog.bitmex.com/introducing-bech32-deposits-on-bitmex-to-deepen-bitcoin-integration-lower-fees/
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Evaluating|??}} || {{No}} ||
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinfloor || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinfloor.zendesk.com/hc/en-us/articles/360018072678-Why-are-there-2-BTC-deposit-addresses-to-choose-from-
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Planned}} || {{Planned}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-890016344
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Planned|Before Activation}} || {{Planned|Before Activation}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| chaindex || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool.space || {{Yes}} || {{Yes}} || {{Planned|Depends on Rust Bitcoin/Electrs}} || {{Evaluating|??}} ||
|-
| OXT || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Planned|PR in work}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Evaluating|??}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Around activation}} || https://twitter.com/benthecarman/status/1415741934992232457
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://docs.rs/bdk
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Planned|Before Activation}} || {{Planned|Before Activation}} || https://github.com/ElementsProject/libwally-core/pull/281
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Planned|Before Activation}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|}



=== References ===

[[Category:Software]]

Bech32 adoption

2021-10-06T21:10:24Z

Goonie: Bitcoin Wallet plans to implement send to bech32m

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Evaluating|??}} ||
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|Depends on python-bitcointx}} || {{Evaluating|??}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Planned|Planned: via GDK before activation}} || {{Evaluating|??}} ||
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Planned|Planned before activation}} || {{Evaluating|??}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Muun || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Planned|After activation}} || https://twitter.com/MuunWallet/status/1415692517690023937
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Planned|Planned: via GDK before activation}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Planned|Planned: via btcsuite}} || {{Evaluating|??}} ||
|-
| Exodus || {{Yes}} || {{Yes}} || {{Planned|Planned before activation, depends on bitcoinjs}} || {{No|Not yet planned}} ||
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: before Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Planned|Planned: at activation}} || {{Planned|Planned: at activation}} || [https://twitter.com/darosior/status/1432371465815568390 Announced at Surfin' Bitcoin]
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: before Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Planned|Planned: via GDK before activation}} || {{Evaluating|??}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Planned|Before activation|}} || {{Evaluating|??}} || Full support on v2 platform, no plans to add support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://blog.bitmex.com/introducing-bech32-deposits-on-bitmex-to-deepen-bitcoin-integration-lower-fees/
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Evaluating|??}} || {{No}} ||
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinfloor || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinfloor.zendesk.com/hc/en-us/articles/360018072678-Why-are-there-2-BTC-deposit-addresses-to-choose-from-
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b53e3bc5edbb41b34a963ecf67eb045266cf841cab73a780940ce6845377f141</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Planned}} || {{Planned}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-890016344
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Planned|Before Activation}} || {{Planned|Before Activation}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| chaindex || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool.space || {{Yes}} || {{Yes}} || {{Planned|Depends on Rust Bitcoin/Electrs}} || {{Evaluating|??}} ||
|-
| OXT || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Planned|PR in work}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Evaluating|??}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/pull/2099#issuecomment-887757918
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Around activation}} || https://twitter.com/benthecarman/status/1415741934992232457
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://docs.rs/bdk
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Planned|Before Activation}} || {{Planned|Before Activation}} || https://github.com/ElementsProject/libwally-core/pull/281
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Planned|Before Activation}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|}



=== References ===

[[Category:Software]]

Bech32 adoption

2019-04-06T19:01:01Z

Goonie: /* Software Wallets */ Bitcoin Wallet native SegWit has fully rolled out

[[Bech32]] is a new bitcoin [[address]] format specified by [[BIP 0173]]. This page tracks the adoption of [[Bech32]].

Ideally wallets and services would first support ''sending to'' bech32 addresses. After almost everything can send to, then people may be willing to adopt bech32 widely for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Bitcoin Core || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Knots || {{Yes}} || {{Yes}} ||
|-
| Electrum || {{Yes}} || {{Yes}} ||
|-
| Armory || {{Evaluating|??}} || {{No}} ||
|-
| JoinMarket || {{Yes}} || {{No}} ||
|-
| GreenAddress || {{Yes}} || {{Planned}} ||
|-
| Breadwallet || {{Yes}} || {{No}} || https://twitter.com/udiWertheimer/status/975810157941796864
|-
| Samourai Wallet || {{Yes}} || {{Yes}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} ||
|-
| Casa || {{Yes}} || {{No}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} ||
|-
| Trust Wallet || {{Yes}} || {{Yes}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Trezor web wallet || {{Acceptable|PR Merged}} || {{No}} ||
|-
| Ledger chrome app || {{No}} || {{No}} ||
|-
| Ledger Live (desktop app) || {{No}} || {{No}} ||
|-
| KeepKey chrome app || {{No}} || {{No}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} ||
|-
| BitGo || {{Evaluating|??}} || {{No}} ||
|-
| blockchain.info web wallet || {{Yes}} || {{No}} || https://twitter.com/provoost/status/1037802325874761728
|-
| HolyTransaction || {{Yes}} || {{No}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || open source JavaScript implementation
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || https://1fox.com/?c=en/content/blog&id=12
|-
| Anycoin Direct || {{Yes}} || {{No}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{No}} || {{No}} ||
|-
| BitMEX || {{Evaluating|??}} || {{No}} ||
|-
| Bittylicious || {{Yes}} || {{No}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{No}} || {{No}} ||
|-
| Bitwage || {{Evaluating|??}} || {{No}} ||
|-
| Bisq || {{No}} || {{No}} || https://github.com/bisq-network/bisq-desktop/issues/1139 https://bisq.community/t/bech32-address-support/6521
|-
| Coinbase.com || {{Yes}} || {{No}} || https://twitter.com/diogorsergio/status/983052769262292992
|-
| CoinFalcon || {{Yes}} || {{No}} ||
|-
| Coinfloor || {{Evaluating|??}} || {{No}} ||
|-
| Coinsbank.com || {{Yes}} || {{Yes}} ||
|-
| Flyp.me || {{Yes}} || {{No}} ||
|-
| GDax || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} ||
|-
| HitBTC || {{Yes}} || {{No}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Itbit || {{Evaluating|??}} || {{No}} ||
|-
| Kraken || {{Yes}} || {{No}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| Liberalcoins || {{Yes}} || {{Yes}} || https://liberalcoins.com
|-
| Localbitcoins.com || {{No}} || {{No}} ||
|-
| Paxful.com || {{Evaluating|??}} || {{No}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || The first European Crypto-exchange to enable deposits and withdrawals of Bech32 addresses
https://www.therocktrading.com/
(https://twitter.com/TheRockTrading/status/976787499648512003)
|-
| Walltime || {{Yes}} || {{Yes}} || https://walltime.info
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| GenesisCoin || {{No}} || {{No}} ||
|-
| General Bytes || {{No}} || {{No}} ||
|-
| Lamassu Douro || {{No}} || {{No}} ||
|}

=== Blockchain Explorers ===

For trying these out you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code>. And addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display !! Index !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || Bitcoin Block Explorer with SegWit support https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.info || {{Yes}} || {{No}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || https://blockchair.com/
|-
| Blockcypher || {{No}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || https://blockpath.com
|-
| blockstream.info || {{Yes}} || {{Yes}} || https://blockstream.info/
|-
| chaindex || {{Yes}} || {{Yes}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || Open source explorer, instances are https://insight.bitpay.com/ and https://chain.localbitcoins.com/
|-
| OXT || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! Invoice addresses !! Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || Payment notifications, Merchant dashboard, Bitcoin plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart etc.
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} ||
|}

=== Other Services ===

Casinos, marketplaces, etc that let users withdraw money

{| class="wikitable sortable"
|-
! Name !! Withdrawals !! Notes
|-
| 1Broker || {{Yes}} ||
|-
| Crypto-Games.net || {{Yes}} || [https://bitcointalk.org/index.php?topic=750760.msg31421151#msg31421151 bitcointalk source]
|-
| YOLOdice || {{Yes}} || A popular dice site https://yolodice.com
|}

=== References ===

[[Category:Software]]

Bech32 adoption

2019-03-14T12:20:12Z

Goonie: The Testnet version already creates native segwit addresses by default. The Mainnet version has everything ready to go, waiting for the switch to happen.

[[Bech32]] is a new bitcoin [[address]] format specified by [[BIP 0173]]. This page tracks the adoption of [[Bech32]].

Ideally wallets and services would first support ''sending to'' bech32 addresses. After almost everything can send to, then people may be willing to adopt bech32 widely for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Bitcoin Core || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Knots || {{Yes}} || {{Yes}} ||
|-
| Electrum || {{Yes}} || {{Yes}} ||
|-
| Armory || {{Evaluating|??}} || {{No}} ||
|-
| JoinMarket || {{Yes}} || {{No}} ||
|-
| GreenAddress || {{Yes}} || {{Planned}} ||
|-
| Breadwallet || {{Yes}} || {{No}} || https://twitter.com/udiWertheimer/status/975810157941796864
|-
| Samourai Wallet || {{Yes}} || {{Yes}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} ||
|-
| Casa || {{Yes}} || {{No}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Wallet for Android || {{Yes}} || {{Acceptable|PR Merged}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} ||
|-
| Trust Wallet || {{Yes}} || {{Yes}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Trezor web wallet || {{Acceptable|PR Merged}} || {{No}} ||
|-
| Ledger chrome app || {{No}} || {{No}} ||
|-
| Ledger Live (desktop app) || {{No}} || {{No}} ||
|-
| KeepKey chrome app || {{No}} || {{No}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} ||
|-
| BitGo || {{Evaluating|??}} || {{No}} ||
|-
| blockchain.info web wallet || {{Yes}} || {{No}} || https://twitter.com/provoost/status/1037802325874761728
|-
| HolyTransaction || {{Yes}} || {{No}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || open source JavaScript implementation
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || https://1fox.com/?c=en/content/blog&id=12
|-
| Anycoin Direct || {{Yes}} || {{No}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{No}} || {{No}} ||
|-
| BitMEX || {{Evaluating|??}} || {{No}} ||
|-
| Bittylicious || {{Yes}} || {{No}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{No}} || {{No}} ||
|-
| Bitwage || {{Evaluating|??}} || {{No}} ||
|-
| Bisq || {{No}} || {{No}} || https://github.com/bisq-network/bisq-desktop/issues/1139 https://bisq.community/t/bech32-address-support/6521
|-
| Coinbase.com || {{Yes}} || {{No}} || https://twitter.com/diogorsergio/status/983052769262292992
|-
| CoinFalcon || {{Yes}} || {{No}} ||
|-
| Coinfloor || {{Evaluating|??}} || {{No}} ||
|-
| Coinsbank.com || {{Yes}} || {{Yes}} ||
|-
| Flyp.me || {{Yes}} || {{No}} ||
|-
| GDax || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{No}} || {{No}} ||
|-
| Genesis || {{Evaluating|??}} || {{No}} ||
|-
| HitBTC || {{Yes}} || {{No}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Itbit || {{Evaluating|??}} || {{No}} ||
|-
| Kraken || {{Yes}} || {{No}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| Liberalcoins || {{Yes}} || {{Yes}} || https://liberalcoins.com
|-
| Localbitcoins.com || {{No}} || {{No}} ||
|-
| Paxful.com || {{Evaluating|??}} || {{No}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| Walltime || {{Yes}} || {{Yes}} || https://walltime.info
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| GenesisCoin || {{No}} || {{No}} ||
|-
| General Bytes || {{No}} || {{No}} ||
|-
| Lamassu Douro || {{No}} || {{No}} ||
|}

=== Blockchain Explorers ===

For trying these out you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code>. And addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display !! Index !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || Bitcoin Block Explorer with SegWit support https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.info || {{Yes}} || {{No}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || https://blockchair.com/
|-
| Blockcypher || {{No}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || https://blockpath.com
|-
| blockstream.info || {{Yes}} || {{Yes}} || https://blockstream.info/
|-
| chaindex || {{Yes}} || {{Yes}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || Open source explorer, instances are https://insight.bitpay.com/ and https://chain.localbitcoins.com/
|-
| OXT || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! Invoice addresses !! Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || Payment notifications, Merchant dashboard, Bitcoin plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart etc.
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} ||
|}

=== Other Services ===

Casinos, marketplaces, etc that let users withdraw money

{| class="wikitable sortable"
|-
! Name !! Withdrawals !! Notes
|-
| 1Broker || {{Yes}} ||
|-
| Crypto-Games.net || {{Yes}} || [https://bitcointalk.org/index.php?topic=750760.msg31421151#msg31421151 bitcointalk source]
|-
| YOLOdice || {{Yes}} || A popular dice site https://yolodice.com
|}

=== References ===

[[Category:Software]]

Bech32 adoption

2019-03-11T23:54:47Z

Goonie:

[[Bech32]] is a new bitcoin [[address]] format specified by [[BIP 0173]]. This page tracks the adoption of [[Bech32]].

Ideally wallets and services would first support ''sending to'' bech32 addresses. After almost everything can send to, then people may be willing to adopt bech32 widely for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Bitcoin Core || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Knots || {{Yes}} || {{Yes}} ||
|-
| Electrum || {{Yes}} || {{Yes}} ||
|-
| Armory || {{Evaluating|??}} || {{No}} ||
|-
| JoinMarket || {{Yes}} || {{No}} ||
|-
| GreenAddress || {{Yes}} || {{Planned}} ||
|-
| Breadwallet || {{Yes}} || {{No}} || https://twitter.com/udiWertheimer/status/975810157941796864
|-
| Samourai Wallet || {{Yes}} || {{Yes}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} ||
|-
| Casa || {{Yes}} || {{No}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Wallet for Android || {{Yes}} || {{Planned}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} ||
|-
| Trust Wallet || {{Yes}} || {{Yes}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Trezor web wallet || {{Acceptable|PR Merged}} || {{No}} ||
|-
| Ledger chrome app || {{No}} || {{No}} ||
|-
| Ledger Live (desktop app) || {{No}} || {{No}} ||
|-
| KeepKey chrome app || {{No}} || {{No}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} ||
|-
| BitGo || {{Evaluating|??}} || {{No}} ||
|-
| blockchain.info web wallet || {{Yes}} || {{No}} || https://twitter.com/provoost/status/1037802325874761728
|-
| HolyTransaction || {{Yes}} || {{No}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || open source JavaScript implementation
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || https://1fox.com/?c=en/content/blog&id=12
|-
| Anycoin Direct || {{Yes}} || {{No}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{No}} || {{No}} ||
|-
| BitMEX || {{Evaluating|??}} || {{No}} ||
|-
| Bittylicious || {{Yes}} || {{No}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{No}} || {{No}} ||
|-
| Bitwage || {{Evaluating|??}} || {{No}} ||
|-
| Bisq || {{No}} || {{No}} || https://github.com/bisq-network/bisq-desktop/issues/1139 https://bisq.community/t/bech32-address-support/6521
|-
| Coinbase.com || {{Yes}} || {{No}} || https://twitter.com/diogorsergio/status/983052769262292992
|-
| CoinFalcon || {{Yes}} || {{No}} ||
|-
| Coinfloor || {{Evaluating|??}} || {{No}} ||
|-
| Coinsbank.com || {{Yes}} || {{Yes}} ||
|-
| Flyp.me || {{Yes}} || {{No}} ||
|-
| GDax || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{No}} || {{No}} ||
|-
| Genesis || {{Evaluating|??}} || {{No}} ||
|-
| HitBTC || {{Yes}} || {{No}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Itbit || {{Evaluating|??}} || {{No}} ||
|-
| Kraken || {{Yes}} || {{No}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| Liberalcoins || {{Yes}} || {{Yes}} || https://liberalcoins.com
|-
| Localbitcoins.com || {{No}} || {{No}} ||
|-
| Paxful.com || {{Evaluating|??}} || {{No}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| Walltime || {{Yes}} || {{Yes}} || https://walltime.info
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| GenesisCoin || {{No}} || {{No}} ||
|-
| General Bytes || {{No}} || {{No}} ||
|-
| Lamassu Douro || {{No}} || {{No}} ||
|}

=== Blockchain Explorers ===

For trying these out you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code>. And addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display !! Index !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || Bitcoin Block Explorer with SegWit support https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.info || {{Yes}} || {{No}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || https://blockchair.com/
|-
| Blockcypher || {{No}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || https://blockpath.com
|-
| blockstream.info || {{Yes}} || {{Yes}} || https://blockstream.info/
|-
| chaindex || {{Yes}} || {{Yes}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || Open source explorer, instances are https://insight.bitpay.com/ and https://chain.localbitcoins.com/
|-
| OXT || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! Invoice addresses !! Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || Payment notifications, Merchant dashboard, Bitcoin plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart etc.
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} ||
|}

=== Other Services ===

Casinos, marketplaces, etc that let users withdraw money

{| class="wikitable sortable"
|-
! Name !! Withdrawals !! Notes
|-
| 1Broker || {{Yes}} ||
|-
| Crypto-Games.net || {{Yes}} || [https://bitcointalk.org/index.php?topic=750760.msg31421151#msg31421151 bitcointalk source]
|-
| YOLOdice || {{Yes}} || A popular dice site https://yolodice.com
|}

=== References ===

[[Category:Software]]

Bech32 adoption

2019-03-11T23:51:55Z

Goonie: Since version 7.0, native SegWit is implemented

[[Bech32]] is a new bitcoin [[address]] format specified by [[BIP 0173]]. This page tracks the adoption of [[Bech32]].

Ideally wallets and services would first support ''sending to'' bech32 addresses. After almost everything can send to, then people may be willing to adopt bech32 widely for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Bitcoin Core || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Knots || {{Yes}} || {{Yes}} ||
|-
| Electrum || {{Yes}} || {{Yes}} ||
|-
| Armory || {{Evaluating|??}} || {{No}} ||
|-
| JoinMarket || {{Yes}} || {{No}} ||
|-
| GreenAddress || {{Yes}} || {{Planned}} ||
|-
| Breadwallet || {{Yes}} || {{No}} || https://twitter.com/udiWertheimer/status/975810157941796864
|-
| Samourai Wallet || {{Yes}} || {{Yes}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} ||
|-
| Casa || {{Yes}} || {{No}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} ||
|-
| Bitcoin Wallet for Android || {{Yes}} || {{No}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} ||
|-
| Trust Wallet || {{Yes}} || {{Yes}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Trezor web wallet || {{Acceptable|PR Merged}} || {{No}} ||
|-
| Ledger chrome app || {{No}} || {{No}} ||
|-
| Ledger Live (desktop app) || {{No}} || {{No}} ||
|-
| KeepKey chrome app || {{No}} || {{No}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} ||
|-
| BitGo || {{Evaluating|??}} || {{No}} ||
|-
| blockchain.info web wallet || {{Yes}} || {{No}} || https://twitter.com/provoost/status/1037802325874761728
|-
| HolyTransaction || {{Yes}} || {{No}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || open source JavaScript implementation
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || https://1fox.com/?c=en/content/blog&id=12
|-
| Anycoin Direct || {{Yes}} || {{No}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{No}} || {{No}} ||
|-
| BitMEX || {{Evaluating|??}} || {{No}} ||
|-
| Bittylicious || {{Yes}} || {{No}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{No}} || {{No}} ||
|-
| Bitwage || {{Evaluating|??}} || {{No}} ||
|-
| Bisq || {{No}} || {{No}} || https://github.com/bisq-network/bisq-desktop/issues/1139 https://bisq.community/t/bech32-address-support/6521
|-
| Coinbase.com || {{Yes}} || {{No}} || https://twitter.com/diogorsergio/status/983052769262292992
|-
| CoinFalcon || {{Yes}} || {{No}} ||
|-
| Coinfloor || {{Evaluating|??}} || {{No}} ||
|-
| Coinsbank.com || {{Yes}} || {{Yes}} ||
|-
| Flyp.me || {{Yes}} || {{No}} ||
|-
| GDax || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{No}} || {{No}} ||
|-
| Genesis || {{Evaluating|??}} || {{No}} ||
|-
| HitBTC || {{Yes}} || {{No}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Itbit || {{Evaluating|??}} || {{No}} ||
|-
| Kraken || {{Yes}} || {{No}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| Liberalcoins || {{Yes}} || {{Yes}} || https://liberalcoins.com
|-
| Localbitcoins.com || {{No}} || {{No}} ||
|-
| Paxful.com || {{Evaluating|??}} || {{No}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| Walltime || {{Yes}} || {{Yes}} || https://walltime.info
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to !! Create/receive !! Notes
|-
| GenesisCoin || {{No}} || {{No}} ||
|-
| General Bytes || {{No}} || {{No}} ||
|-
| Lamassu Douro || {{No}} || {{No}} ||
|}

=== Blockchain Explorers ===

For trying these out you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code>. And addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display !! Index !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || Bitcoin Block Explorer with SegWit support https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.info || {{Yes}} || {{No}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || https://blockchair.com/
|-
| Blockcypher || {{No}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || https://blockpath.com
|-
| blockstream.info || {{Yes}} || {{Yes}} || https://blockstream.info/
|-
| chaindex || {{Yes}} || {{Yes}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || Open source explorer, instances are https://insight.bitpay.com/ and https://chain.localbitcoins.com/
|-
| OXT || {{Yes}} || {{Yes}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! Invoice addresses !! Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || Payment notifications, Merchant dashboard, Bitcoin plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart etc.
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} ||
|}

=== Other Services ===

Casinos, marketplaces, etc that let users withdraw money

{| class="wikitable sortable"
|-
! Name !! Withdrawals !! Notes
|-
| 1Broker || {{Yes}} ||
|-
| Crypto-Games.net || {{Yes}} || [https://bitcointalk.org/index.php?topic=750760.msg31421151#msg31421151 bitcointalk source]
|-
| YOLOdice || {{Yes}} || A popular dice site https://yolodice.com
|}

=== References ===

[[Category:Software]]

Wallet

2018-03-12T16:24:42Z

Goonie: Undo removal of Bitcoin Wallet.

A Bitcoin '''wallet''' is a collection of private keys but may also refer to [[Clients|client software]] used to manage those keys and to make transactions on the Bitcoin network.

This page covers various wallet formats in use.

=== [[Bitcoin Core]] ===

The original Bitcoin client stores private key information in a file named '''wallet.dat''' following the so called [https://bitcointalk.org/index.php?topic=4448.0 "bitkeys"] format.

It contains:

* keypairs for each of your [[address|addresses]]
* transactions done from/to your addresses
* user preferences
* default key
* reserve keys
* [[Accounts_explained|accounts]]
* a version number
* [[Key pool]]
* Since 0.3.21: information about the current best chain, to be able to rescan automatically when restoring from a backup.

The wallet.dat file is located in the [[data directory|Bitcoin data directory]] and may be [[Wallet_encryption|encrypted with a password]].

It is intended that a wallet file be used on only one installation of Bitcoin at a time. Attempting to clone a wallet file for use on multiple computers will result in "weird behavior"<ref>[http://forum.bitcoin.org/index.php?topic=5324.msg77896#msg77896 Multiple instance of bitcoin with the same wallet]</ref>.

The format of this file is Berkeley DB. Tools that can manipulate wallet files include [[pywallet]].

=== [[Armory]] ===

The Armory client uses a custom [[Deterministic wallet]] format [https://www.bitcoinarmory.com/wallet-format/ described here] and runs on top of [[Bitcoin Core]].

=== [[Bitcoin Wallet]] ===

[[File:bitcoin_wallet.png|192px]] Bitcoin Wallet uses the bitcoinj [http://code.google.com/p/protobuf/ protobuf] format for its wallet file. However, due to Android isolation of applications, it is impossible to access the wallet file as a non-root user.

=== [[Blockchain.info#Wallet|Blockchain.info]] ===

Blockchain.info offers a [[Browser-based_wallet#Hybrid_e-wallets|hybrid eWallet]] called "My Wallet". It use a plain text [https://blockchain.info/wallet/wallet-format JSON wallet format]. Private keys Keys are stored in base58.

=== [[Denarium.com]] ===

Denarium is Physical Bitcoin coin manufacturer. Denarium produces easy, handy and secure wallets in a coin form. The private key is stored under a security seal without password protection. Denarium also offers a trustless multisignature coins, which eliminates the need to trust the manufacturer.

=== [[Ledger Wallet]] ===

Ledger Wallet manufactures various hardware wallets.

=== [[Multibit]] ===

Multibit HD (the current version) uses a [[BIP 0032]] (type 2) [[Deterministic wallet]] with the [https://www.multibit.org/en/help/hd0.1/files.html format described here]. The "Classic" version used the bitcoinj [https://github.com/google/protobuf protobuf] wallet file.

=== [[Blocktrail]] ===

Blocktrail offers a [[BIP 0032]] (type 2) [[Deterministic wallet]] and for added security also implements [[Multisignature]] wallet technology.

=== [[TREZOR]] ===

TREZOR is an isolated hardware environment for offline transaction signing and using a small display you can visually verify the transaction contents.

=== [https://opendime.com Opendime] ===

Opendime is a small USB stick that allows you to spend Bitcoin like a dollar bill. Pass it along multiple times. Connect to any USB to check balance. Unseal anytime to spend online. Trust no one.

==See Also==

* [[Transaction fees]]
* [[Securing your wallet]]
* [[EWallet]]
* [[Deterministic Wallet]]
* [https://bitcoin.org/en/choose-your-wallet Choose your wallet]

==References==
<references />

Bitcoin Wallet

2015-06-10T16:13:12Z

Goonie:

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 4.0 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of June 2015, it is being used by 800.000 people.

==Key Derivation and Export==

Since version 4.0 Bitcoin Wallet supports HD Wallets<ref>[https://github.com/schildbach/bitcoin-wallet/releases/tag/v4.0 Release notes v4.0]</ref> and derives keys from a master node in the BIP32 format.

Since version 4.18 it provides a simple export functionality<ref>[https://github.com/schildbach/bitcoin-wallet/releases/tag/v4.18 Release notes v4.18]</ref> for the key in the format:

<code>xpub[key]?c=[birthday]&h=bip32</code>

Where the parameter "c" gives the creation date of the key and "h" the hierarchie. The value "key" is the derivation m/0' from the master node according to the [https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Master_key_generation BIP32 derivation scheme].

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://plus.google.com/communities/105515929887248493912] Google+ community
* [https://github.com/schildbach/bitcoin-wallet/releases] direct download of releases and test versions
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]
[[Category:Android]]

[[de:Bitcoin_Wallet]]

Bitcoin Wallet

2015-06-10T16:12:29Z

Goonie: Update numbers.

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 4.0 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of Juni 2015, it is being used by 800.000 people.

==Key Derivation and Export==

Since version 4.0 Bitcoin Wallet supports HD Wallets<ref>[https://github.com/schildbach/bitcoin-wallet/releases/tag/v4.0 Release notes v4.0]</ref> and derives keys from a master node in the BIP32 format.

Since version 4.18 it provides a simple export functionality<ref>[https://github.com/schildbach/bitcoin-wallet/releases/tag/v4.18 Release notes v4.18]</ref> for the key in the format:

<code>xpub[key]?c=[birthday]&h=bip32</code>

Where the parameter "c" gives the creation date of the key and "h" the hierarchie. The value "key" is the derivation m/0' from the master node according to the [https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Master_key_generation BIP32 derivation scheme].

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://plus.google.com/communities/105515929887248493912] Google+ community
* [https://github.com/schildbach/bitcoin-wallet/releases] direct download of releases and test versions
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]
[[Category:Android]]

[[de:Bitcoin_Wallet]]

Protocol documentation

2014-06-09T12:41:48Z

Goonie: Update links to BIP standards.

Sources:
* [[Original Bitcoin client]] source

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

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

==Common standards==

=== Hashes ===

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

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

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

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

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

=== Merkle Trees ===

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

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

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

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

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

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

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

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

d7 = dhash(d5 concat d6)

where

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

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

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

=== Signatures ===

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

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

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

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

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

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

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

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

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

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

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

=== Addresses ===

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

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

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

== Common structures ==

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

=== Message structure ===

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

Known magic values:

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

=== Variable length integer ===

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

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

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

=== Variable length string ===

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

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

=== Network address ===

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

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

Hexdump example of Network address structure

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

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

=== Inventory Vectors ===

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

Inventory vectors consist of the following data format:

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

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

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

Other Data Type values are considered reserved for future implementations.

=== Block Headers ===

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

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

== Message types ==

=== version ===

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

Payload:

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

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

The following services are currently assigned:

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

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

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

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

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

<pre>

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

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

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

=== verack ===

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

Hexdump of the verack message:

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

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

=== addr ===

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

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

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

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

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

Payload:
01 - 1 address in this message

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

=== inv ===

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

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

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

=== getdata ===

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

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

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

=== notfound ===

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

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

=== getblocks ===

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

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

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

Payload:

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

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

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

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

=== getheaders ===

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

Payload:

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

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

=== tx ===

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

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

|}

TxIn consists of the following fields:

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

The OutPoint structure consists of the following fields:

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

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

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

The TxOut structure consists of the following fields:

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

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

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

Transaction:
01 00 00 00 - version

Inputs:
01 - number of transaction inputs

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

8B - script is 139 bytes long

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

FF FF FF FF - sequence

Outputs:
02 - 2 Output Transactions

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

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

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

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

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

=== block ===

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

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

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

=== headers ===

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

Payload:

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

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

=== getaddr ===

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

No additional data is transmitted with this message.

=== mempool ===

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

No additional data is transmitted with this message.

It is specified in [https://github.com/bitcoin/bips/blob/master/bip-0035.mediawiki BIP 35]. Since [https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki BIP 37], only transactions matching the filter are replied.

=== checkorder ===

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

=== submitorder ===

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

=== reply ===

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

=== ping ===

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

Payload:

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

=== pong ===

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

Payload:

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

=== reject===

The ''reject'' message is sent when messages are rejected.

Payload:

{|class="wikitable"
! Field Size !! Description !! Data type !! Comments
|-
| 1+ || message || var_str || type of message rejected
|-
| 1 || ccode || char || code relating to rejected message
|-
| 1+ || reason || var_str || text version of reason for rejection
|}

CCodes

{|class="wikitable"
! Value !! Name !! Description
|-
| 0x01 || REJECT_MALFORMED||
|-
| 0x10 || REJECT_INVALID ||
|-
| 0x11 || REJECT_OBSOLETE ||
|-
| 0x12 || REJECT_DUPLICATE ||
|-
| 0x40 || REJECT_NONSTANDARD ||
|-
| 0x41 || REJECT_DUST ||
|-
| 0x42 || REJECT_INSUFFICIENTFEE ||
|-
| 0x43 || REJECT_CHECKPOINT ||
|}

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

These messages are related to Bloom filtering of connections and are defined in [https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki BIP 0037].

=== alert ===

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

Alert format:

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

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

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

Note: '''set<''type''>''' in the table above is a [[#Variable length integer | variable length integer]] followed by the number of fields of the given ''type'' (either int32_t or [[#Variable length string | variable length string]])

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

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

== Scripting ==

See [[script]].

==See Also==

* [[Network]]
* [[Protocol rules]]
* [[Hardfork Wishlist]]
* [https://bitcoin.org/en/developer-documentation Developer Documentation on bitcoin.org]
* Bitcoin dissectors for Wireshark: https://github.com/lbotsch/wireshark-bitcoin https://github.com/op-sig/bitcoin-wireshark-dissector

==References==
<references />

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

Template:MainPage Intro

2014-02-09T17:47:37Z

Goonie: Explain why it might make sense to download a quicker wallet than bitcoin-qt.

[[Image:Bitcoin world map.png|left|200px|Bitcoin usage worldwide.]]

'''Bitcoin''' is an experimental, decentralized [[digital currency]] that enables instant payments to anyone, anywhere in the world. [[Bitcoin]] uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network.

The original Bitcoin software by [[Satoshi Nakamoto]] was released under the MIT license.
Most client software, derived or "from scratch", also use open source licensing.

Bitcoin is one of the first successful implementations of a ''distributed crypto-currency'', described in part in 1998 by Wei Dai on the cypherpunks mailing list. Building upon the notion that money is any object, or any sort of record, accepted as payment for goods and services and repayment of debts in a given country or socio-economic context, Bitcoin is designed around the idea of using cryptography to control the creation and transfer of money, rather than relying on central authorities.

:''Sourced from [http://bitcoin.org Bitcoin.org] and [[wikipedia:Bitcoin|Wikipedia]].''

'''Bitcoin-Qt:'''
{|style="background-color: inherit;"
|
* [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/bitcoin-0.8.6-win32-setup.exe/download '''Windows (exe)'''] 10 MB [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/bitcoin-0.8.6-win32.zip/download '''(zip)'''] 14 MB
* [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/bitcoin-0.8.6-linux.tar.gz/download '''GNU/Linux'''] 13 MB
* [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/bitcoin-0.8.6-macosx.dmg/download '''Mac OS X'''] 12 MB
|}

Bitcoin-Qt initial startup can take a very long time to complete. For quicker clients, see [https://bitcoin.org/en/choose-your-wallet this list of Bitcoin wallets].

File:Bitcoin wallet icon.png

2014-02-09T12:26:46Z

Goonie: App icon of Bitcoin Wallet.

== Summary ==
App icon of Bitcoin Wallet.
== Licensing ==
{{Copyrighted free use}}

Mobile Payment Apps

2014-01-08T18:36:07Z

Goonie: Touch last active date for Bitcoin Wallet

List of Mobile apps used for payments.

{| class = "wikitable"|
|-
| App || Android || iPhone || Nokia || BlackBerry || QR-code || NFC || Btc Storage || OpenSource || Last Active || Comments
|-
| [[Bitcoin Wallet|Bitcoin Wallet for Android/BB10]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value Yes}} || {{Table Value Yes}} || On Phone + encrypted backup || [https://github.com/schildbach/bitcoin-wallet Github] [https://code.google.com/p/bitcoin-wallet/ Google] || 2014-Jan-08 || [https://bitcointalk.org/index.php?board=100.0 Forum]
|-
| [[BitcoinApp]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || ? || ? || On Phone || [https://github.com/udibr/bitcoinApp Github] || 2011-May-18
|-
| [[BitPay]] || {{Table Value Yes}} || {{Table Value No}} || ? || ? || {{Table Value Yes}} || {{Table Value No}} || [[Instawallet]] || [https://github.com/warpi/BitPay Github] || 2011-Sep-26
|-
| [[Bitcoin Express]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || ? || ? || ? || [https://github.com/fingster/BTC-Express Github] || 2011-Jul-24 || [http://bitcointalk.org/index.php?topic=31362.0 Forum]
|-
| [[BitcoinSpinner]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, chain on server || [http://code.google.com/p/bitcoinspinner/ Google] || 2011-12-01 || [http://bitcointalk.org/index.php?topic=52674.0 Forum]
|-
| [[BlockChain.info|Blockchain for iPhone]] || {{Table Value No}} || {{Table Value Yes}}<ref>Cydia / Jailbroken only.</ref> || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, encrypted backup on server || [https://github.com/zootreeves/My-Wallet-iPhone GitHub] || 2012-05-12 || [http://bitcointalk.org/index.php?topic=75673.0 Forum]
|-
| [[BlockChain.info|Blockchain for Android]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, encrypted backup on server || [https://github.com/zootreeves/My-Wallet-Android Github] || 2012-05-12 || [http://bitcointalk.org/index.php?topic=74191.0 Forum]
|-
| [[Bridgewalker]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || Not applicable, balance is in Euros || Proprietary || 2013-10-03 || [https://bitcointalk.org/index.php?topic=156943.0 Forum]
|-
| [[Instawallet]] || {{Table Value Yes}} || {{Table Value No}} || ? || ? || {{Table Value No}} || {{Table Value No}} || [[Instawallet]] || Proprietary || 2012-06-18 || [https://bitcointalk.org/index.php?topic=73388.msg972384#msg972384 Forum]
|-
| [[FriendlyPay]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || [[Instawallet]] || Proprietary || 2012-05-12 || [http://bitcointalk.org/index.php?topic=6785.msg869671#msg869671 Forum]
|-
| [[Paytunia]] || {{Table Value Yes}} || {{Table Value Yes}}<ref>Private Beta</ref> || ? || ? || {{Table Value Yes}} || {{Table Value No}} || Server (Hosted) || Proprietary || 2012-05-12 || [http://bitcointalk.org/index.php?topic=75550.0 Forum]
|-
| [[Easywallet.org]] || {{Table Value Yes}} || {{Table Value Yes}} || ? || ? || {{Table Value Yes}} || {{Table Value No}} || Easywallet.org || Proprietary || 2012-05-12 || [https://bitcointalk.org/index.php?topic=75665.0 Forum]
|-
| [[ResponsePay]] || {{Table Value Yes}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || ResponsePay.com || Proprietary || 2012-07-10 || [https://bitcointalk.org/index.php?topic=91431.0 Forum]
|}

==See Also==

* [[Payment methods]]
* [http://dre.tx0.org/compare.htm Open-Source Bitcoin Clients for the Desktop]

==References==
<references />

[[Category:Mobile]]
[[Category:Software]]
[[Category:Clients]]
[[Category:Wallets]]
[[Category:Free Software]]
[[Category:Open Source]]

Clients

2014-01-08T18:32:59Z

Goonie: Update Discussion links for Bitcoin Wallet

==Overview==

This table compares the features of the different clients. All of the listed clients are open-source.

===Feature key===

; Wallet Security : How well the client protects your [[private key]]s from people with access to the machine the wallet is stored on. The private keys can be encrypted, for example. The private keys can also be either stored on your device or on a remote server.
; Network Security : Clients which more fully implement the Bitcoin network protocol are safer -- they can't be as easily tricked by powerful attackers. A client which ''fully'' implements the protocol will always use the correct [[block chain]] and will never allow [[double-spending|double-spends]] or invalid transactions to exist in the block chain under any circumstances. Clients which only ''partially'' implement the protocol typically trust that 50% or more of the network's mining power is honest. Some clients trust one or more ''remote servers'' to protect them from double-spends and other network attacks.
; Setup Time : Some clients require that you download and verify a large amount of data before you can send or receive BTC.
; Maturity : When the project was started.

===Table===


{| class='wikitable' style='text-align: center'
! Client !! Get Started !! Audience !! Wallet Security !! Network Security !! Backups !! Setup Time !! Disk Space !! Maturity !! Multi-user !! Available for
|-
! Armory
|| [http://bitcoinarmory.com/index.php/get-armory Download] || Power users || {{CLGood|Encrypted, on-device}} || Addon || {{CLBest|One-time}} || Varies || {{CLBad|6+ GB}} || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLWin}}
|-
! Bitcoin Wallet
|| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Google Play] [https://appworld.blackberry.com/webstore/content/23952882/ BlackBerry World] || {{CLGood|End-users}} || {{CLGood|Isolated, on-device}} || Partial || Manual || {{CLBest|Instant}} || {{CLGood|15 MB}} || {{CLGood|Mar 2011}} || on JB tablets || {{CLAndroid}} [[file:ico-blackberry.png]]
|-
! {{CLGood|Bitcoin-Qt}}
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|6+ GB}} || {{CLGood|May 2011}} || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! bitcoind
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || Programmers || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|6+ GB}} || {{CLBest|Aug 2009}} || {{CLGood|Virtual accounts}} || {{CLLinux}}{{CLWin}}
|-
! Electrum
|| [http://ecdsa.org/electrum/ Download] || Power users || {{CLGood|Encrypted, on-device}} || Minimal || {{CLBest|Memorized}} || {{CLGood|Minutes}} || {{CLGood|5 MB}} || Nov 2011 || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! MultiBit
|| [https://multibit.org/releases.html Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || Partial || {{CLGood|Automatic (local)}} || {{CLBest|Seconds}} || 50 MB || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! My Wallet
|| [https://blockchain.info/wallet/new Web-based] || {{CLBest|Everyone}} || Encrypted, on a server || {{CLBad|Remote}} || {{CLGood|Automatic}} || {{CLGood|Minutes}} || {{CLBest|None}} || Dec 2011 || {{CLBest|Yes}} || {{CLAndroid}}{{CLiOS}}{{CLLinux}}{{CLMac}}{{CLWin}}
|-
! Gocoin
|| [https://github.com/piotrnar/gocoin Build yourself] || Power users || Designated offline PC || {{CLBest|Full}} || {{CLBest|Memorized}} || {{CLBad|Hours}} || {{CLBad|6+GB}} || May 2013 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|}



==For developers==

This table shows additional information about various Bitcoin clients that may be relevant to developers.

{| class='wikitable' style='text-align: center'
! Client !! Website !! Source Code !! License !! Discussion !! Architecture
|-
! Armory
|| [http://bitcoinarmory.com/ Link] ||[https://github.com/etotheipi/BitcoinArmory/ Github] || AGPLv3 || [https://bitcointalk.org/index.php?board=97.0 Bitcointalk] || Integrated
|-
! Bitcoin Wallet
|| [https://github.com/schildbach/bitcoin-wallet Link] || [https://github.com/schildbach/bitcoin-wallet Github] [https://code.google.com/p/bitcoin-wallet/source/checkout Google Code] || GPLv3 || [https://plus.google.com/b/101256420499771441772/communities/105515929887248493912 Google+ community] / [https://bitcointalk.org/index.php?board=100.0 Bitcointalk] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! Bitcoin-Qt / bitcoind
|| [http://bitcoin.org/ Link] || [https://github.com/bitcoin/bitcoin Github] || MIT || [https://lists.sourceforge.net/lists/listinfo/bitcoin-development Sourceforge] || Integrated
|-
! Electrum
|| [http://ecdsa.org/electrum/ Link] || [https://gitorious.org/electrum Gitorious] || GPLv3 || [https://lists.sourceforge.net/lists/listinfo/electrum-discuss Sourceforge] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]
|-
! MultiBit
|| [http://multibit.org/ Link] || [https://github.com/jim618/multibit Github] || MIT || [https://groups.google.com/forum/?fromgroups#!forum/bitcoin-multibit Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! My Wallet
|| [https://blockchain.info/wallet/ Link] || [https://github.com/blockchain/My-Wallet/ Github] || BSD* || None || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! bits of proof
|| [http://bitsofproof.com Link] || [https://github.com/bitsofproof/supernode Github] || Apache 2.0 || [https://bitcointalk.org/index.php?topic=122013.0 Bitcointalk] || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! Gocoin
|| [http://www.assets-otc.com/gocoin Link] || [https://github.com/piotrnar/gocoin Github] || ? || [https://bitcointalk.org/index.php?topic=199306.0 Bitcointalk] || Integrated
|}

==See Also==
* [[Software#Bitcoin_clients|List of clients]]
* [[Bitcoin Ladder]]

<references/>

Clients

2014-01-08T18:30:59Z

Goonie: Update facts about Bitcoin Wallet

==Overview==

This table compares the features of the different clients. All of the listed clients are open-source.

===Feature key===

; Wallet Security : How well the client protects your [[private key]]s from people with access to the machine the wallet is stored on. The private keys can be encrypted, for example. The private keys can also be either stored on your device or on a remote server.
; Network Security : Clients which more fully implement the Bitcoin network protocol are safer -- they can't be as easily tricked by powerful attackers. A client which ''fully'' implements the protocol will always use the correct [[block chain]] and will never allow [[double-spending|double-spends]] or invalid transactions to exist in the block chain under any circumstances. Clients which only ''partially'' implement the protocol typically trust that 50% or more of the network's mining power is honest. Some clients trust one or more ''remote servers'' to protect them from double-spends and other network attacks.
; Setup Time : Some clients require that you download and verify a large amount of data before you can send or receive BTC.
; Maturity : When the project was started.

===Table===


{| class='wikitable' style='text-align: center'
! Client !! Get Started !! Audience !! Wallet Security !! Network Security !! Backups !! Setup Time !! Disk Space !! Maturity !! Multi-user !! Available for
|-
! Armory
|| [http://bitcoinarmory.com/index.php/get-armory Download] || Power users || {{CLGood|Encrypted, on-device}} || Addon || {{CLBest|One-time}} || Varies || {{CLBad|6+ GB}} || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLWin}}
|-
! Bitcoin Wallet
|| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Google Play] [https://appworld.blackberry.com/webstore/content/23952882/ BlackBerry World] || {{CLGood|End-users}} || {{CLGood|Isolated, on-device}} || Partial || Manual || {{CLBest|Instant}} || {{CLGood|15 MB}} || {{CLGood|Mar 2011}} || on JB tablets || {{CLAndroid}} [[file:ico-blackberry.png]]
|-
! {{CLGood|Bitcoin-Qt}}
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|6+ GB}} || {{CLGood|May 2011}} || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! bitcoind
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || Programmers || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|6+ GB}} || {{CLBest|Aug 2009}} || {{CLGood|Virtual accounts}} || {{CLLinux}}{{CLWin}}
|-
! Electrum
|| [http://ecdsa.org/electrum/ Download] || Power users || {{CLGood|Encrypted, on-device}} || Minimal || {{CLBest|Memorized}} || {{CLGood|Minutes}} || {{CLGood|5 MB}} || Nov 2011 || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! MultiBit
|| [https://multibit.org/releases.html Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || Partial || {{CLGood|Automatic (local)}} || {{CLBest|Seconds}} || 50 MB || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! My Wallet
|| [https://blockchain.info/wallet/new Web-based] || {{CLBest|Everyone}} || Encrypted, on a server || {{CLBad|Remote}} || {{CLGood|Automatic}} || {{CLGood|Minutes}} || {{CLBest|None}} || Dec 2011 || {{CLBest|Yes}} || {{CLAndroid}}{{CLiOS}}{{CLLinux}}{{CLMac}}{{CLWin}}
|-
! Gocoin
|| [https://github.com/piotrnar/gocoin Build yourself] || Power users || Designated offline PC || {{CLBest|Full}} || {{CLBest|Memorized}} || {{CLBad|Hours}} || {{CLBad|6+GB}} || May 2013 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|}



==For developers==

This table shows additional information about various Bitcoin clients that may be relevant to developers.

{| class='wikitable' style='text-align: center'
! Client !! Website !! Source Code !! License !! Discussion !! Architecture
|-
! Armory
|| [http://bitcoinarmory.com/ Link] ||[https://github.com/etotheipi/BitcoinArmory/ Github] || AGPLv3 || [https://bitcointalk.org/index.php?board=97.0 Bitcointalk] || Integrated
|-
! Bitcoin Wallet
|| [https://github.com/schildbach/bitcoin-wallet Link] || [https://github.com/schildbach/bitcoin-wallet Github] [https://code.google.com/p/bitcoin-wallet/source/checkout Google Code] || GPLv3 || [https://bitcointalk.org/index.php?board=100.0 Bitcointalk] / [https://groups.google.com/forum/?fromgroups#!forum/bitcoinj Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! Bitcoin-Qt / bitcoind
|| [http://bitcoin.org/ Link] || [https://github.com/bitcoin/bitcoin Github] || MIT || [https://lists.sourceforge.net/lists/listinfo/bitcoin-development Sourceforge] || Integrated
|-
! Electrum
|| [http://ecdsa.org/electrum/ Link] || [https://gitorious.org/electrum Gitorious] || GPLv3 || [https://lists.sourceforge.net/lists/listinfo/electrum-discuss Sourceforge] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]
|-
! MultiBit
|| [http://multibit.org/ Link] || [https://github.com/jim618/multibit Github] || MIT || [https://groups.google.com/forum/?fromgroups#!forum/bitcoin-multibit Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! My Wallet
|| [https://blockchain.info/wallet/ Link] || [https://github.com/blockchain/My-Wallet/ Github] || BSD* || None || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! bits of proof
|| [http://bitsofproof.com Link] || [https://github.com/bitsofproof/supernode Github] || Apache 2.0 || [https://bitcointalk.org/index.php?topic=122013.0 Bitcointalk] || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! Gocoin
|| [http://www.assets-otc.com/gocoin Link] || [https://github.com/piotrnar/gocoin Github] || ? || [https://bitcointalk.org/index.php?topic=199306.0 Bitcointalk] || Integrated
|}

==See Also==
* [[Software#Bitcoin_clients|List of clients]]
* [[Bitcoin Ladder]]

<references/>

Clients

2014-01-08T18:28:12Z

Goonie: Prefer GitHub URLs for Bitcoin Wallet

==Overview==

This table compares the features of the different clients. All of the listed clients are open-source.

===Feature key===

; Wallet Security : How well the client protects your [[private key]]s from people with access to the machine the wallet is stored on. The private keys can be encrypted, for example. The private keys can also be either stored on your device or on a remote server.
; Network Security : Clients which more fully implement the Bitcoin network protocol are safer -- they can't be as easily tricked by powerful attackers. A client which ''fully'' implements the protocol will always use the correct [[block chain]] and will never allow [[double-spending|double-spends]] or invalid transactions to exist in the block chain under any circumstances. Clients which only ''partially'' implement the protocol typically trust that 50% or more of the network's mining power is honest. Some clients trust one or more ''remote servers'' to protect them from double-spends and other network attacks.
; Setup Time : Some clients require that you download and verify a large amount of data before you can send or receive BTC.
; Maturity : When the project was started.

===Table===


{| class='wikitable' style='text-align: center'
! Client !! Get Started !! Audience !! Wallet Security !! Network Security !! Backups !! Setup Time !! Disk Space !! Maturity !! Multi-user !! Available for
|-
! Armory
|| [http://bitcoinarmory.com/index.php/get-armory Download] || Power users || {{CLGood|Encrypted, on-device}} || Addon || {{CLBest|One-time}} || Varies || {{CLBad|6+ GB}} || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLWin}}
|-
! Bitcoin Wallet
|| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Google Play] [https://appworld.blackberry.com/webstore/content/23952882/ BlackBerry World] || {{CLGood|End-users}} || {{CLGood|Isolated, on-device}} || Partial || Manual || 1 hour || 30 MB || {{CLGood|Mar 2011}} || on JB tablets || {{CLAndroid}} [[file:ico-blackberry.png]]
|-
! {{CLGood|Bitcoin-Qt}}
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|6+ GB}} || {{CLGood|May 2011}} || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! bitcoind
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || Programmers || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|6+ GB}} || {{CLBest|Aug 2009}} || {{CLGood|Virtual accounts}} || {{CLLinux}}{{CLWin}}
|-
! Electrum
|| [http://ecdsa.org/electrum/ Download] || Power users || {{CLGood|Encrypted, on-device}} || Minimal || {{CLBest|Memorized}} || {{CLGood|Minutes}} || {{CLGood|5 MB}} || Nov 2011 || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! MultiBit
|| [https://multibit.org/releases.html Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || Partial || {{CLGood|Automatic (local)}} || {{CLBest|Seconds}} || 50 MB || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! My Wallet
|| [https://blockchain.info/wallet/new Web-based] || {{CLBest|Everyone}} || Encrypted, on a server || {{CLBad|Remote}} || {{CLGood|Automatic}} || {{CLGood|Minutes}} || {{CLBest|None}} || Dec 2011 || {{CLBest|Yes}} || {{CLAndroid}}{{CLiOS}}{{CLLinux}}{{CLMac}}{{CLWin}}
|-
! Gocoin
|| [https://github.com/piotrnar/gocoin Build yourself] || Power users || Designated offline PC || {{CLBest|Full}} || {{CLBest|Memorized}} || {{CLBad|Hours}} || {{CLBad|6+GB}} || May 2013 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|}



==For developers==

This table shows additional information about various Bitcoin clients that may be relevant to developers.

{| class='wikitable' style='text-align: center'
! Client !! Website !! Source Code !! License !! Discussion !! Architecture
|-
! Armory
|| [http://bitcoinarmory.com/ Link] ||[https://github.com/etotheipi/BitcoinArmory/ Github] || AGPLv3 || [https://bitcointalk.org/index.php?board=97.0 Bitcointalk] || Integrated
|-
! Bitcoin Wallet
|| [https://github.com/schildbach/bitcoin-wallet Link] || [https://github.com/schildbach/bitcoin-wallet Github] [https://code.google.com/p/bitcoin-wallet/source/checkout Google Code] || GPLv3 || [https://bitcointalk.org/index.php?board=100.0 Bitcointalk] / [https://groups.google.com/forum/?fromgroups#!forum/bitcoinj Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! Bitcoin-Qt / bitcoind
|| [http://bitcoin.org/ Link] || [https://github.com/bitcoin/bitcoin Github] || MIT || [https://lists.sourceforge.net/lists/listinfo/bitcoin-development Sourceforge] || Integrated
|-
! Electrum
|| [http://ecdsa.org/electrum/ Link] || [https://gitorious.org/electrum Gitorious] || GPLv3 || [https://lists.sourceforge.net/lists/listinfo/electrum-discuss Sourceforge] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]
|-
! MultiBit
|| [http://multibit.org/ Link] || [https://github.com/jim618/multibit Github] || MIT || [https://groups.google.com/forum/?fromgroups#!forum/bitcoin-multibit Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! My Wallet
|| [https://blockchain.info/wallet/ Link] || [https://github.com/blockchain/My-Wallet/ Github] || BSD* || None || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! bits of proof
|| [http://bitsofproof.com Link] || [https://github.com/bitsofproof/supernode Github] || Apache 2.0 || [https://bitcointalk.org/index.php?topic=122013.0 Bitcointalk] || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! Gocoin
|| [http://www.assets-otc.com/gocoin Link] || [https://github.com/piotrnar/gocoin Github] || ? || [https://bitcointalk.org/index.php?topic=199306.0 Bitcointalk] || Integrated
|}

==See Also==
* [[Software#Bitcoin_clients|List of clients]]
* [[Bitcoin Ladder]]

<references/>

Bitcoin Wallet

2014-01-08T18:25:39Z

Goonie: Move direct download URL to GitHub

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 2.3 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of January 2014, it is being used by 400.000 people.

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://plus.google.com/communities/105515929887248493912] Google+ community
* [https://github.com/schildbach/bitcoin-wallet/releases] direct download of releases and test versions
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]
[[Category:Android]]

[[de:Bitcoin_Wallet]]

Bitcoin Wallet

2014-01-08T18:13:41Z

Goonie: Update usage stats

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 2.3 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of January 2014, it is being used by 400.000 people.

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://plus.google.com/communities/105515929887248493912] Google+ community
* [https://code.google.com/p/bitcoin-wallet/downloads/list] direct download of releases and test versions
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]
[[Category:Android]]

[[de:Bitcoin_Wallet]]

Bitcoin Wallet

2014-01-08T18:13:03Z

Goonie: Refresh of external links

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 2.3 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of April 2013, it is being used by 50.000 people.

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://plus.google.com/communities/105515929887248493912] Google+ community
* [https://code.google.com/p/bitcoin-wallet/downloads/list] direct download of releases and test versions
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]
[[Category:Android]]

[[de:Bitcoin_Wallet]]

Meetups

2013-08-15T19:35:01Z

Goonie:

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
|-
| [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/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://groups.google.com/d/forum/bitcoin-switzerland Zurich/Geneva Switzerland]
| Semi-regular, about once a month
| Oliver Twist 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]]

Talk:Units

2013-04-05T16:37:53Z

Goonie: /* Bugs */ new section

=="only a proposal"==
"Please note that the contents of this page is only a proposal, and in no way an official standard; at the time of writing it's not even all that popular."
* Units are an objective measure; the cyan units are defined by SI, and the green by Tonal
* As far as application to BitCoin, there is no such thing as "official", as it is an authorityless system
--[[User:Luke-jr|Luke-jr]] 01:03, 8 March 2011 (GMT)

Until tonal system is not widely used (at least it will be used by more than 1 person), it is rather confusing than useful to mention such units (even as proposal). So I simplify page to only units that is used.
[[User:Aleš Janda|Aleš Janda]] ([[User talk:Aleš Janda|talk]]) 23:59, 26 August 2012 (GMT)

Perhaps two pages are necessary, a Units_SI and a Units_Tonal and then a Units disambiguation page? - [[User:Sgornick|Sgornick]] ([[User talk:Sgornick|talk]]) 04:36, 13 November 2012 (GMT)
* The colours work just fine for that. [[User:Aleš Janda|Aleš Janda]] doesn't seem to do anything but vandalise. --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 02:24, 25 November 2012 (GMT)

== Bugs ==

The tonal column contains many unprintable characters (Firefox on Ubuntu 12.10). What are they supposed to mean?

[[User:Goonie|Goonie]] ([[User talk:Goonie|talk]]) 16:37, 5 April 2013 (GMT)

Yazılım

2013-03-31T12:49:09Z

Goonie: /* Android */

Bitcoin ile alakalı yazılımlar. Ayrıca bakınız [[:Category:Software|Category:Software]].

Be sure to keep on top of the latest [[CVEs|security vulnerabilities]]!

==Bitcoin yazılımları==
===Bitcoin clients===
*[[Bitcoin-Qt]] - C++/Qt based tabbed UI for Bitcoin, Linux/MacOSX/Windows, full-featured
*[[bitcoind]] - GUI-less version of the standard Bitcoin client, providing [[API reference (JSON-RPC)|JSON-RPC]] interface
*[[Bitcoin-js-remote]] - JavaScript RPC client, support for QR codes
*[https://github.com/TheSeven/Bitcoin-WebUI Bitcoin WebUI] - JavaScript RPC client
*[https://github.com/zamgo/bitcoin-webskin Bitcoin Webskin] - PHP web interface to bitcoind and namecoind
* [https://bitcointalk.org/index.php?topic=50721.0 subvertx] - Command line bitcoin tools
*[[Electrum]] - A blazing fast, open-source, multi-OS Bitcoin client/wallet with a very active community
*[[MultiBit]] - a secure, lightweight, international Bitcoin wallet for Windows, MacOS and Linux
*[[Bitcoiner]] - Java RPC client (Android)
*[[Spesmilo]] - Python/PySide RPC client (abandoned)
*[[Armory]] - Python-based client currently an alpha-level release, the beta version is being crowdfunded

====Frontends to eWallet====
*[[BitPay]] - Android application
*[https://blockchain.info/wallet Blockchain] - Javascript bitcoin client with client side encryption.

====Experimental====
*[[Freecoin]] - C++ client, supports alternative currencies like [[Beertoken]]
*[[BitDroid]] - Java client
*[[Bitdollar]] - C++/Qt client, unstable beta version

===Libraries===
*[https://bitcointalk.org/index.php?topic=30646.0 libbitcoin]
*[[BitCoinJ|bitcoinj]] - Java client library, early development stage but used in live projects already
*[[BCCAPI]] (Bitcoin Client API) - a java library designed for making secure light-weight bitcoin clients.

==Bitcoin Trade Data==
*[[Bitcoin Charts]] – Prices, volume, and extensive charting on virtually all Bitcoin markets.
*[[MtGox Live]] - An innovative chart showing a live feed of [[MtGox]] trades and market depth. (Must Use Chrome)
*[http://btccharts.com BTCCharts] - An innovative chart showing a live feed of multiple markets, currencies and timeframes.
*[http://BitcoinExchangeRate.org BitcoinExchangeRate.org] - Bitcoin and USD converter with convenient URL scheme and Auto-updating Portfolio Spreadsheet.
*[[Bitcoin Sentiment Index]] - A financial index that collects and disseminates sentiment data about bitcoin.
*[[Preev]] - Bitcoin converter with live exchange rates.

==Bitcoin software==

===Web interfaces for merchants===
*[[Bitcoin Evolution]] - Non wallet-based Buy Now button to insert into websites (handles sales tracking; client must be used for actual transaction)
*[[BitPay]] - Buy Now buttons, Checkout posts/callbacks, Mobile Checkout, JSON API
*[[Btceconomy]] - a JavaScript widget listing items for sale
*[[Javascript Bitcoin Converter]] - currency conversion
*[[WalletBit]] - Easy JavaScript Buy Now buttons, Instant Payment Notification, Application Programming Interface (JSON API), Mobile Checkout, QR-Code
*[[BitUtils Merchant]] - Customizable Buy Now buttons with hosted checkout interface. No programming skills required to set up.

===Shopping Cart Integration in eCommerce-Systems===
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart.
*[[Karsha Shopping Cart Interface]] - is a mobile payment-interface which enables its users to accept payments.
*[[Bitcoin-Cash]] - an easy to use payment module for xt:Commerce
*[[BitPay]] - bitcoin plugins for Magento, Opencart, Zencart, PHP, JSON API
*[[WalletBit]] - Plugins for PrestaShop, OpenCart, PHP, JSON API
*[[OpenCart Bitcoin]] - An OpenCart payment module that communicates with a bitcoin client using JSON RPC.
*[[OsCommerce_Bitcoin_Payment_Module|OsCommerce Bitcoin Payment Module]] - a payment module that uses a python monitoring script to interact with bitcoind for OsCommerce
* [http://drupal.org/project/uc_bitcoin Drupal Ubercart Bitcoin payment method] enables you to accept Bitcoin as payment for your Drupal/Ubercart enabled website product/services.

===Web apps (opensource)===
*[[Bitcoin Central]] - currency exchange
*[[Bitcoin Poker Room]] - poker site
*[[Abe]] - block chain viewer
*[[Simplecoin]] - PHP web frontend for a pool
*[[bitcoin_simple_php_tools]] simple php tools for webmasters

===Browser extensions===
*[[Bitcoin Extension]] - check balance and send bitcoins (Chrome)
*[[Bitcoin Prices (extension)]] - monitoring price (Firefox)
*[[Bitcoin Ticker]] - monitoring price (Chrome)
*[[Biticker]] - Bitcoin ticker, currency converter and history price graph (Chrome)

===PC apps===
*[[http://www.mybtc-trader.com MyBTC-Trader.com]] - a MtGox Bitcoin trading client for windows with GUI
*[[Mining Explorer]] - monitoring tool for bitcoin mining
*[[Bitcoin SMS Alert]] - sends SMS text alerts to a user's phone based on BTC price / percent thresholds.
*[[BTConvert]] - currency conversion
*[[Sierra Chart MtGox Bridge]] - real-time charting
*[[BitTicker]] - monitoring price (Mac OS X)
*[[ToyTrader]] - a command line trading tool for [[MtGox]]
*[[goxsh]] - a command-line frontend to the [[MtGox|Mt. Gox Bitcoin Exchange]] (Python)
*[[MyBitcoins gadget]] - monitoring pool earnings / price (Windows gadget)
*[[Bitcoin QR Popup]] - streamlined interface to bitcoin for POS systems (Windows)
*[http://gnome-help.org/content/show.php/Bitcoin+Rate?content=138572 Bitcoin Rate] - Desktop widget with BTC exchange rate (KDE)
*[http://kde-apps.org/content/show.php?content=142344 Bitcoin Monitor] - Desktop widget to monitor status of your Bitcoin miners on mining pools (KDE)

===Mobile apps===
==== iPhone / iPad ====
*[https://blockchain.info/wallet/iphone-app Blockchain] - Fully featured iphone bitcoin app.
*[[Bitcoin Ticker (iPhone)]] - monitoring price w/push notifications
*[[BitCoins Mobile]] - First iPad native app! Live market data, news feeds, mining pool statistics, full screen exchange price charts, bitcoin network statistical charts. (iPad only, iPhone/iPod Touch coming soon!)
*[https://github.com/teeman/BitcoinTrader BitcoinTrader] - Spend/receive BTC via QR codes, trade, deposit/withdraw, etc. Supports Mt. Gox, TradeHill, ExchB, CampBX, and InstaWallet.
*[[Bit-pay]] - Mobile Checkout, set prices in any currency and receive mobile-to-mobile payment
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on iPhone/iPad/iPod touch

==== Android ====
* Direct link to Android Market bitcoin apps. https://play.google.com/store/search?q=bitcoin
*[[BitCare]] - Track bitcoin wallet balance, trade on Mt.Gox, monitor mining pool hashrate, balance, worker status.
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Bitcoin Alert]] - monitoring price (Android)
*[[Bitcoin-android]] - Does not appear to be being maitained anymore. https://market.android.com/details?id=com.bitcoinandroid
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone
*[[Bitcoin Wallet]] - This is the most functional Android bitcoin wallet application. https://market.android.com/details?id=de.schildbach.wallet
*[[BitcoinSpinner]] - Single address, easy to use, lightweight and open source client. Keys stored on device.
*[[BitcoinX]] - monitoring price (Android)
*[[BitPay]] - https://market.android.com/details?id=com.bitcoin.bitpay (Is not related to the bit-pay.com online payment processor.)
*[https://blockchain.info/wallet/android-app Blockchain] - Lightweight Android Bitcoin Client - Also works with blockchain.info web interface and iphone app.
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on Android devices
*[[Miner Status]] - monitoring miner status (Android)
*[[SMS Bitcoins]] - transactions by SMS

==== Windows Phone 7 ====
*Direct link to Windows Phone Marketplace Bitcoin apps: [http://www.windowsphone.com/en-us/store/search?q=bitcoin]

see also [[Bitcoin Payment Apps]]

===Operating systems===
*[[BAMT]]
*[[LinuxCoin]] - a lightweight Debian-based OS, with the Bitcoin client and GPU mining software

===Mining apps===
*[[50Miner]] - A GUI frontend for Windows(Poclbm, Phoenix, DiabloMiner)
*[[BFGMiner]] - Modular FPGA/GPU miner in C
*[[BTCMiner]] - Bitcoin Miner for ZTEX FPGA Boards
*[[Bit Moose]] - Run Miners as a Windows Service.
*[[Poclbm]] - Python/OpenCL GPU miner ([[Poclbm-gui|GUI(Windows & MacOS X)]])
*[[Poclbm-mod]] - more efficient version of [[Poclbm]] ([[Poclbm-mod-gui|GUI]])
*[[DiabloMiner]] - Java/OpenCL GPU miner ([[DiabloMiner.app|MAC OS X GUI]])
*[[RPC Miner]] - remote RPC miner ([[RPCminer.app|MAC OS X GUI]])
*[[Phoenix miner]] - miner
*[[Cpu Miner]] - miner
*[[Ufasoft miner]] - miner
*[[Pyminer]] - Python miner, reference implementation
*[[Remote miner]] - mining pool software
*[[Open Source FGPA Bitcoin Miner]] - a miner that makes use of an FPGA Board
*[https://github.com/mkburza/Flash-Player-Bitcoin-Miner Flash Player Bitcoin Miner] - A proof of concept Adobe Flash Player miner

===Mining Pool Servers (backend)===
Main page: [[Poolservers]]

*[[ecoinpool]] - Erlang poolserver
*[[Eloipool]] - Fast Python3 poolserver
*[[Pushpoold]] - Old mining poolserver in C (not maintained)
*[[Poold]] - Old Python mining poolserver (not maintained)
*[[PoolServerJ]] - Java mining poolserver (not maintained)

===Utilities, libraries, and interfaces:===
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API
*[[libblkmaker]] - C library implementation of [[getblocktemplate]] decentralized mining protocol
*[[python-blkmaker]] - Python module implementation of [[getblocktemplate]] decentralized mining protocol

===Lists of software===
*[[BitGit]] - list of Bitcoin-related opensource projects hosted at Git

===Developer resources===
*[[:Category:Developer|Category:Developer]]
*[[:Category:Technical|Category:Technical]]
*[[Original Bitcoin client/API calls list]]
*[[API reference (JSON-RPC)]]
*[[PHP_developer_intro|PHP Developer Introduction]]

===Other===
*[[Namecoin]] - a distributed naming system based on Bitcoin technology
*[[Bitcoin Consultancy]] - an organization providing open source software and Bitcoin-related consulting
*[[Open Transactions]] - a financial crypto and digital cash software library, complementary to Bitcoin
*[[Moneychanger]] - Java-based GUI for [[Open Transactions]]
*[http://btcnames.org/ BTCnames] - a webbased aliasing service which allows to handle unlimited names for your BTC deposit hashes
*[[Devcoin]] - the open source developer coin

Yazılım

2013-03-31T12:48:39Z

Goonie: /* Libraries */

Bitcoin ile alakalı yazılımlar. Ayrıca bakınız [[:Category:Software|Category:Software]].

Be sure to keep on top of the latest [[CVEs|security vulnerabilities]]!

==Bitcoin yazılımları==
===Bitcoin clients===
*[[Bitcoin-Qt]] - C++/Qt based tabbed UI for Bitcoin, Linux/MacOSX/Windows, full-featured
*[[bitcoind]] - GUI-less version of the standard Bitcoin client, providing [[API reference (JSON-RPC)|JSON-RPC]] interface
*[[Bitcoin-js-remote]] - JavaScript RPC client, support for QR codes
*[https://github.com/TheSeven/Bitcoin-WebUI Bitcoin WebUI] - JavaScript RPC client
*[https://github.com/zamgo/bitcoin-webskin Bitcoin Webskin] - PHP web interface to bitcoind and namecoind
* [https://bitcointalk.org/index.php?topic=50721.0 subvertx] - Command line bitcoin tools
*[[Electrum]] - A blazing fast, open-source, multi-OS Bitcoin client/wallet with a very active community
*[[MultiBit]] - a secure, lightweight, international Bitcoin wallet for Windows, MacOS and Linux
*[[Bitcoiner]] - Java RPC client (Android)
*[[Spesmilo]] - Python/PySide RPC client (abandoned)
*[[Armory]] - Python-based client currently an alpha-level release, the beta version is being crowdfunded

====Frontends to eWallet====
*[[BitPay]] - Android application
*[https://blockchain.info/wallet Blockchain] - Javascript bitcoin client with client side encryption.

====Experimental====
*[[Freecoin]] - C++ client, supports alternative currencies like [[Beertoken]]
*[[BitDroid]] - Java client
*[[Bitdollar]] - C++/Qt client, unstable beta version

===Libraries===
*[https://bitcointalk.org/index.php?topic=30646.0 libbitcoin]
*[[BitCoinJ|bitcoinj]] - Java client library, early development stage but used in live projects already
*[[BCCAPI]] (Bitcoin Client API) - a java library designed for making secure light-weight bitcoin clients.

==Bitcoin Trade Data==
*[[Bitcoin Charts]] – Prices, volume, and extensive charting on virtually all Bitcoin markets.
*[[MtGox Live]] - An innovative chart showing a live feed of [[MtGox]] trades and market depth. (Must Use Chrome)
*[http://btccharts.com BTCCharts] - An innovative chart showing a live feed of multiple markets, currencies and timeframes.
*[http://BitcoinExchangeRate.org BitcoinExchangeRate.org] - Bitcoin and USD converter with convenient URL scheme and Auto-updating Portfolio Spreadsheet.
*[[Bitcoin Sentiment Index]] - A financial index that collects and disseminates sentiment data about bitcoin.
*[[Preev]] - Bitcoin converter with live exchange rates.

==Bitcoin software==

===Web interfaces for merchants===
*[[Bitcoin Evolution]] - Non wallet-based Buy Now button to insert into websites (handles sales tracking; client must be used for actual transaction)
*[[BitPay]] - Buy Now buttons, Checkout posts/callbacks, Mobile Checkout, JSON API
*[[Btceconomy]] - a JavaScript widget listing items for sale
*[[Javascript Bitcoin Converter]] - currency conversion
*[[WalletBit]] - Easy JavaScript Buy Now buttons, Instant Payment Notification, Application Programming Interface (JSON API), Mobile Checkout, QR-Code
*[[BitUtils Merchant]] - Customizable Buy Now buttons with hosted checkout interface. No programming skills required to set up.

===Shopping Cart Integration in eCommerce-Systems===
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart.
*[[Karsha Shopping Cart Interface]] - is a mobile payment-interface which enables its users to accept payments.
*[[Bitcoin-Cash]] - an easy to use payment module for xt:Commerce
*[[BitPay]] - bitcoin plugins for Magento, Opencart, Zencart, PHP, JSON API
*[[WalletBit]] - Plugins for PrestaShop, OpenCart, PHP, JSON API
*[[OpenCart Bitcoin]] - An OpenCart payment module that communicates with a bitcoin client using JSON RPC.
*[[OsCommerce_Bitcoin_Payment_Module|OsCommerce Bitcoin Payment Module]] - a payment module that uses a python monitoring script to interact with bitcoind for OsCommerce
* [http://drupal.org/project/uc_bitcoin Drupal Ubercart Bitcoin payment method] enables you to accept Bitcoin as payment for your Drupal/Ubercart enabled website product/services.

===Web apps (opensource)===
*[[Bitcoin Central]] - currency exchange
*[[Bitcoin Poker Room]] - poker site
*[[Abe]] - block chain viewer
*[[Simplecoin]] - PHP web frontend for a pool
*[[bitcoin_simple_php_tools]] simple php tools for webmasters

===Browser extensions===
*[[Bitcoin Extension]] - check balance and send bitcoins (Chrome)
*[[Bitcoin Prices (extension)]] - monitoring price (Firefox)
*[[Bitcoin Ticker]] - monitoring price (Chrome)
*[[Biticker]] - Bitcoin ticker, currency converter and history price graph (Chrome)

===PC apps===
*[[http://www.mybtc-trader.com MyBTC-Trader.com]] - a MtGox Bitcoin trading client for windows with GUI
*[[Mining Explorer]] - monitoring tool for bitcoin mining
*[[Bitcoin SMS Alert]] - sends SMS text alerts to a user's phone based on BTC price / percent thresholds.
*[[BTConvert]] - currency conversion
*[[Sierra Chart MtGox Bridge]] - real-time charting
*[[BitTicker]] - monitoring price (Mac OS X)
*[[ToyTrader]] - a command line trading tool for [[MtGox]]
*[[goxsh]] - a command-line frontend to the [[MtGox|Mt. Gox Bitcoin Exchange]] (Python)
*[[MyBitcoins gadget]] - monitoring pool earnings / price (Windows gadget)
*[[Bitcoin QR Popup]] - streamlined interface to bitcoin for POS systems (Windows)
*[http://gnome-help.org/content/show.php/Bitcoin+Rate?content=138572 Bitcoin Rate] - Desktop widget with BTC exchange rate (KDE)
*[http://kde-apps.org/content/show.php?content=142344 Bitcoin Monitor] - Desktop widget to monitor status of your Bitcoin miners on mining pools (KDE)

===Mobile apps===
==== iPhone / iPad ====
*[https://blockchain.info/wallet/iphone-app Blockchain] - Fully featured iphone bitcoin app.
*[[Bitcoin Ticker (iPhone)]] - monitoring price w/push notifications
*[[BitCoins Mobile]] - First iPad native app! Live market data, news feeds, mining pool statistics, full screen exchange price charts, bitcoin network statistical charts. (iPad only, iPhone/iPod Touch coming soon!)
*[https://github.com/teeman/BitcoinTrader BitcoinTrader] - Spend/receive BTC via QR codes, trade, deposit/withdraw, etc. Supports Mt. Gox, TradeHill, ExchB, CampBX, and InstaWallet.
*[[Bit-pay]] - Mobile Checkout, set prices in any currency and receive mobile-to-mobile payment
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on iPhone/iPad/iPod touch

==== Android ====
* Direct link to Android Market bitcoin apps. https://play.google.com/store/search?q=bitcoin
*[[BitCare]] - Track bitcoin wallet balance, trade on Mt.Gox, monitor mining pool hashrate, balance, worker status.
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Bitcoin Alert]] - monitoring price (Android)
*[[Bitcoin-android]] - Does not appear to be being maitained anymore. https://market.android.com/details?id=com.bitcoinandroid
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone
*[[Bitcoin Wallet for Android]] - This is the most functional android bitcoin wallet application. https://market.android.com/details?id=de.schildbach.wallet
*[[BitcoinSpinner]] - Single address, easy to use, lightweight and open source client. Keys stored on device.
*[[BitcoinX]] - monitoring price (Android)
*[[BitPay]] - https://market.android.com/details?id=com.bitcoin.bitpay (Is not related to the bit-pay.com online payment processor.)
*[https://blockchain.info/wallet/android-app Blockchain] - Lightweight Android Bitcoin Client - Also works with blockchain.info web interface and iphone app.
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on Android devices
*[[Miner Status]] - monitoring miner status (Android)
*[[SMS Bitcoins]] - transactions by SMS

==== Windows Phone 7 ====
*Direct link to Windows Phone Marketplace Bitcoin apps: [http://www.windowsphone.com/en-us/store/search?q=bitcoin]

see also [[Bitcoin Payment Apps]]

===Operating systems===
*[[BAMT]]
*[[LinuxCoin]] - a lightweight Debian-based OS, with the Bitcoin client and GPU mining software

===Mining apps===
*[[50Miner]] - A GUI frontend for Windows(Poclbm, Phoenix, DiabloMiner)
*[[BFGMiner]] - Modular FPGA/GPU miner in C
*[[BTCMiner]] - Bitcoin Miner for ZTEX FPGA Boards
*[[Bit Moose]] - Run Miners as a Windows Service.
*[[Poclbm]] - Python/OpenCL GPU miner ([[Poclbm-gui|GUI(Windows & MacOS X)]])
*[[Poclbm-mod]] - more efficient version of [[Poclbm]] ([[Poclbm-mod-gui|GUI]])
*[[DiabloMiner]] - Java/OpenCL GPU miner ([[DiabloMiner.app|MAC OS X GUI]])
*[[RPC Miner]] - remote RPC miner ([[RPCminer.app|MAC OS X GUI]])
*[[Phoenix miner]] - miner
*[[Cpu Miner]] - miner
*[[Ufasoft miner]] - miner
*[[Pyminer]] - Python miner, reference implementation
*[[Remote miner]] - mining pool software
*[[Open Source FGPA Bitcoin Miner]] - a miner that makes use of an FPGA Board
*[https://github.com/mkburza/Flash-Player-Bitcoin-Miner Flash Player Bitcoin Miner] - A proof of concept Adobe Flash Player miner

===Mining Pool Servers (backend)===
Main page: [[Poolservers]]

*[[ecoinpool]] - Erlang poolserver
*[[Eloipool]] - Fast Python3 poolserver
*[[Pushpoold]] - Old mining poolserver in C (not maintained)
*[[Poold]] - Old Python mining poolserver (not maintained)
*[[PoolServerJ]] - Java mining poolserver (not maintained)

===Utilities, libraries, and interfaces:===
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API
*[[libblkmaker]] - C library implementation of [[getblocktemplate]] decentralized mining protocol
*[[python-blkmaker]] - Python module implementation of [[getblocktemplate]] decentralized mining protocol

===Lists of software===
*[[BitGit]] - list of Bitcoin-related opensource projects hosted at Git

===Developer resources===
*[[:Category:Developer|Category:Developer]]
*[[:Category:Technical|Category:Technical]]
*[[Original Bitcoin client/API calls list]]
*[[API reference (JSON-RPC)]]
*[[PHP_developer_intro|PHP Developer Introduction]]

===Other===
*[[Namecoin]] - a distributed naming system based on Bitcoin technology
*[[Bitcoin Consultancy]] - an organization providing open source software and Bitcoin-related consulting
*[[Open Transactions]] - a financial crypto and digital cash software library, complementary to Bitcoin
*[[Moneychanger]] - Java-based GUI for [[Open Transactions]]
*[http://btcnames.org/ BTCnames] - a webbased aliasing service which allows to handle unlimited names for your BTC deposit hashes
*[[Devcoin]] - the open source developer coin

Mobile Payment Apps

2013-03-31T12:47:13Z

Goonie:

List of Mobile apps used for payments.

{| class = "wikitable"|
|-
| App || Android || iPhone || Nokia || BlackBerry || QR-code || NFC || Btc Storage || OpenSource || Last Active || Comments
|-
| [[Bitcoin Wallet|Bitcoin Wallet for Android/BB10]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value Yes}} || {{Table Value Yes}} || On Phone + encrypted backup || [https://github.com/schildbach/bitcoin-wallet Github] [https://code.google.com/p/bitcoin-wallet/ Google] || 2013-Jan-28 || [https://bitcointalk.org/index.php?board=100.0 Forum]
|-
| [[BitcoinApp]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || ? || ? || On Phone || [https://github.com/udibr/bitcoinApp Github] || 2011-May-18
|-
| [[BitPay]] || {{Table Value Yes}} || {{Table Value No}} || ? || ? || {{Table Value Yes}} || {{Table Value No}} || [[Instawallet]] || [https://github.com/warpi/BitPay Github] || 2011-Sep-26
|-
| [[Bitcoin Express]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || ? || ? || ? || [https://github.com/fingster/BTC-Express Github] || 2011-Jul-24 || [http://bitcointalk.org/index.php?topic=31362.0 Forum]
|-
| [[BitcoinSpinner]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, chain on server || [http://code.google.com/p/bitcoinspinner/ Google] || 2011-12-01 || [http://bitcointalk.org/index.php?topic=52674.0 Forum]
|-
| [[BlockChain.info|Blockchain for iPhone]] || {{Table Value No}} || {{Table Value Yes}}<ref>Cydia / Jailbroken only.</ref> || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, encrypted backup on server || [https://github.com/zootreeves/My-Wallet-iPhone GitHub] || 2012-05-12 || [http://bitcointalk.org/index.php?topic=75673.0 Forum]
|-
| [[BlockChain.info|Blockchain for Android]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, encrypted backup on server || [https://github.com/zootreeves/My-Wallet-Android Github] || 2012-05-12 || [http://bitcointalk.org/index.php?topic=74191.0 Forum]
|-
| [[Instawallet]] || {{Table Value Yes}} || {{Table Value No}} || ? || ? || {{Table Value No}} || {{Table Value No}} || [[Instawallet]] || Proprietary || 2012-06-18 || [https://bitcointalk.org/index.php?topic=73388.msg972384#msg972384 Forum]
|-
| [[FriendlyPay]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || [[Instawallet]] || Proprietary || 2012-05-12 || [http://bitcointalk.org/index.php?topic=6785.msg869671#msg869671 Forum]
|-
| [[Paytunia]] || {{Table Value Yes}} || {{Table Value Yes}}<ref>Private Beta</ref> || ? || ? || {{Table Value Yes}} || {{Table Value No}} || Server (Hosted) || Proprietary || 2012-05-12 || [http://bitcointalk.org/index.php?topic=75550.0 Forum]
|-
| [[Easywallet.org]] || {{Table Value Yes}} || {{Table Value Yes}} || ? || ? || {{Table Value Yes}} || {{Table Value No}} || Easywallet.org || Proprietary || 2012-05-12 || [https://bitcointalk.org/index.php?topic=75665.0 Forum]
|-
| [[ResponsePay]] || {{Table Value Yes}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || ResponsePay.com || Proprietary || 2012-07-10 || [https://bitcointalk.org/index.php?topic=91431.0 Forum]
|}

==See Also==

* [[Payment methods]]
* [http://dre.tx0.org/compare.htm Open-Source Bitcoin Clients for the Desktop]

==References==
<references />

[[Category:Mobile]]
[[Category:Software]]
[[Category:Clients]]
[[Category:Wallets]]
[[Category:Free Software]]
[[Category:Open Source]]

Software

2013-03-31T12:45:08Z

Goonie: /* Android */

List of Bitcoin-related software. See also [[:Category:Software|Category:Software]].

Be sure to keep on top of the latest [[CVEs|security vulnerabilities]]!

==Bitcoin clients==
===Bitcoin clients===
::''Main article and feature comparison: [[Clients]]''
*[[Bitcoin-Qt]] - C++/Qt based tabbed UI. Linux/MacOSX/Windows. Full-featured [[Thin Client Security|thick client]] that downloads the entire [[block chain]], using code from the original Bitcoin client.
*[[bitcoind]] - GUI-less version of the original Bitcoin client, providing a [[API reference (JSON-RPC)|JSON-RPC]] interface
*[[MultiBit]] - lightweight [[Thin Client Security|thin client]] for Windows, MacOS and Linux with support for opening multiple wallets simultaneously
*[[Electrum]] - a "blazing fast, open-source, multi-OS Bitcoin client/wallet with a very active community"
*[[Bitcoin-js-remote]] - JavaScript RPC client, support for QR codes
*[https://github.com/TheSeven/Bitcoin-WebUI Bitcoin WebUI] - JavaScript RPC client
*[https://github.com/zamgo/bitcoin-webskin Bitcoin Webskin] - PHP web interface to bitcoind and namecoind
*[https://bitcointalk.org/index.php?topic=50721.0 subvertx] - command line bitcoin tools
*[[Bitcoiner]] - Java RPC client (Android)
*[[Armory]] - Python-based client currently an alpha-level release, the beta version is being crowdfunded
*[[Spesmilo]] - Python/PySide RPC client (abandoned)

====Frontends to eWallet====
*[[BitPay]] - Android application
*[https://blockchain.info/wallet Blockchain] - Javascript bitcoin client with client side encryption.

====Experimental====
*[[Freecoin]] - C++ client, supports alternative currencies like [[Beertoken]]
*[[BitDroid]] - Java client
*[[Bitdollar]] - C++/Qt client, unstable beta version

===Libraries===
*[https://bitcointalk.org/index.php?topic=30646.0 libbitcoin]
*[[BitCoinJ]] - Java client library, early development stage but used in live projects already
*[[BCCAPI]] (Bitcoin Client API) - a java library designed for making secure light-weight bitcoin clients.

==Bitcoin Trade Data==
*[[Bitcoin Charts]] – Prices, volume, and extensive charting on virtually all Bitcoin markets.
*[[MtGox Live]] - An innovative chart showing a live feed of [[MtGox]] trades and market depth. (Must Use Chrome)
*[http://btccharts.com BTCCharts] - An innovative chart showing a live feed of multiple markets, currencies and timeframes.
*[http://BitcoinExchangeRate.org BitcoinExchangeRate.org] - Bitcoin and USD converter with convenient URL scheme and Auto-updating Portfolio Spreadsheet.
*[[Bitcoin Sentiment Index]] - A financial index that collects and disseminates sentiment data about bitcoin.
*[[Preev]] - Bitcoin converter with live exchange rates.
*[[Skami]] - Bitcoin Market Exchange comparison charts.
*[[BitcoinSentiment]] - Crowdvoting site offering means of voting and viewing voters sentiment towards bitcoin.

==Bitcoin software==

===Web interfaces for merchants===
*[[Bitcoin Evolution]] - Non wallet-based Buy Now button to insert into websites (handles sales tracking; client must be used for actual transaction)
*[[BitPay]] - Buy Now buttons, Checkout posts/callbacks, Mobile Checkout, JSON API
*[[Btceconomy]] - a JavaScript widget listing items for sale
*[[Javascript Bitcoin Converter]] - currency conversion
*[[WalletBit]] - Easy JavaScript Buy Now buttons, Instant Payment Notification, Application Programming Interface (JSON API), Mobile Checkout, QR-Code
*[[BitUtils Merchant]] - Customizable Buy Now buttons with hosted checkout interface. No programming skills required to set up.

===Shopping Cart Integration in eCommerce-Systems===
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart.
*[[Karsha Shopping Cart Interface]] - is a mobile payment-interface which enables its users to accept payments.
*[[Bitcoin-Cash]] - an easy to use payment module for xt:Commerce
*[[BitPay]] - bitcoin plugins for Magento, Opencart, Zencart, PHP, JSON API
*[[WalletBit]] - Plugins for PrestaShop, OpenCart, PHP, JSON API
*[[OpenCart Bitcoin]] - An OpenCart payment module that communicates with a bitcoin client using JSON RPC.
*[[OsCommerce_Bitcoin_Payment_Module|OsCommerce Bitcoin Payment Module]] - a payment module that uses a python monitoring script to interact with bitcoind for OsCommerce
* [http://drupal.org/project/uc_bitcoin Drupal Ubercart Bitcoin payment method] enables you to accept Bitcoin as payment for your Drupal/Ubercart enabled website product/services.

===Web apps (opensource)===
*[[Bitcoin Central]] - currency exchange
*[[Bitcoin Poker Room]] - poker site
*[[Abe]] - block chain viewer
*[[Simplecoin]] - PHP web frontend for a pool
*[[bitcoin_simple_php_tools]] simple php tools for webmasters

===Browser extensions===
*[[Bitcoin Extension]] - check balance and send bitcoins (Chrome)
*[[Bitcoin Prices (extension)]] - monitoring price (Firefox)
*[[Bitcoin Ticker]] - monitoring price (Chrome)
*[[Biticker]] - Bitcoin ticker, currency converter and history price graph (Chrome)
*[https://chrome.google.com/webstore/detail/bitcoin-microformats/bkanicejfbhlidgjkpenmddnacjengld?hl=en Bitcoin Microformats] Show bitcoin address metadata embedded in a page (Chrome)
*[https://chrome.google.com/webstore/detail/bitcoin-address-lookup/pmlblkdmadbidammhjiponepngbfcpge?hl=en Bitcoin Address Lookup] Right click an address to view its value. (Chrome)

===PC apps===
*[[http://www.mybtc-trader.com MyBTC-Trader.com]] - a MtGox Bitcoin trading client for windows with GUI
*[[Mining Explorer]] - monitoring tool for bitcoin mining
*[[Bitcoin SMS Alert]] - sends SMS text alerts to a user's phone based on BTC price / percent thresholds.
*[[BTConvert]] - currency conversion
*[[Sierra Chart MtGox Bridge]] - real-time charting
*[[BitTicker]] - monitoring price (Mac OS X)
*[[ToyTrader]] - a command line trading tool for [[MtGox]]
*[[goxsh]] - a command-line frontend to the [[MtGox|Mt. Gox Bitcoin Exchange]] (Python)
*[[MyBitcoins gadget]] - monitoring pool earnings / price (Windows gadget)
*[[Bitcoin QR Popup]] - streamlined interface to bitcoin for POS systems (Windows)
*[http://gnome-help.org/content/show.php/Bitcoin+Rate?content=138572 Bitcoin Rate] - Desktop widget with BTC exchange rate (KDE)
*[http://kde-apps.org/content/show.php?content=142344 Bitcoin Monitor] - Desktop widget to monitor status of your Bitcoin miners on mining pools (KDE)

===Mobile apps===
==== iPhone / iPad ====
*[https://blockchain.info/wallet/iphone-app Blockchain] - Fully featured iphone bitcoin app.
*[[Bitcoin Ticker (iPhone)]] - monitoring price w/push notifications
*[[BitCoins Mobile]] - First iPad native app! Live market data, news feeds, mining pool statistics, full screen exchange price charts, bitcoin network statistical charts. (iPad only, iPhone/iPod Touch coming soon!)
*[https://github.com/teeman/BitcoinTrader BitcoinTrader] - Spend/receive BTC via QR codes, trade, deposit/withdraw, etc. Supports Mt. Gox, TradeHill, ExchB, CampBX, and InstaWallet.
*[[Bit-pay]] - Mobile Checkout, set prices in any currency and receive mobile-to-mobile payment
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on iPhone/iPad/iPod touch

==== Android ====
* Direct link to Android Market bitcoin apps. https://play.google.com/store/search?q=bitcoin
*[[BitCare]] - Track bitcoin wallet balance, trade on Mt.Gox, monitor mining pool hashrate, balance, worker status.
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Bitcoin Alert]] - monitoring price (Android)
*[[Bitcoin-android]] - Does not appear to be being maitained anymore. https://market.android.com/details?id=com.bitcoinandroid
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone
*[[Bitcoin Wallet]] - This is the most functional Android bitcoin wallet application. https://market.android.com/details?id=de.schildbach.wallet
*[[BitcoinSpinner]] - Single address, easy to use, lightweight and open source client. Keys stored on device.
*[[BitcoinX]] - monitoring price (Android)
*[[BitPay]] - https://market.android.com/details?id=com.bitcoin.bitpay (Is not related to the bit-pay.com online payment processor.)
*[https://blockchain.info/wallet/android-app Blockchain] - Lightweight Android Bitcoin Client - Also works with blockchain.info web interface and iphone app.
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on Android devices
*[[Miner Status]] - monitoring miner status (Android)
*[[SMS Bitcoins]] - transactions by SMS

==== Windows Phone 7 ====
*Direct link to Windows Phone Marketplace Bitcoin apps: [http://www.windowsphone.com/en-us/store/search?q=bitcoin]

see also [[Bitcoin Payment Apps]]

===Operating systems===
*[[BAMT]]
*[[LinuxCoin]] - a lightweight Debian-based OS, with the Bitcoin client and GPU mining software

===Mining apps===
Main page: [[Mining software]]
*[[50Miner]] - A GUI frontend for Windows(Poclbm, Phoenix, DiabloMiner, cgminer)
*[[BFGMiner]] - Modular FPGA/GPU miner in C
*[[BTCMiner]] - Bitcoin Miner for ZTEX FPGA Boards
*[[Bit Moose]] - Run Miners as a Windows Service.
*[[Poclbm]] - Python/OpenCL GPU miner ([[Poclbm-gui|GUI(Windows & MacOS X)]])
*[[Poclbm-mod]] - more efficient version of [[Poclbm]] ([[Poclbm-mod-gui|GUI]])
*[[DiabloMiner]] - Java/OpenCL GPU miner ([[DiabloMiner.app|MAC OS X GUI]])
*[[RPC Miner]] - remote RPC miner ([[RPCminer.app|MAC OS X GUI]])
*[[Phoenix miner]] - miner
*[[Cpu Miner]] - miner
*[[Ufasoft miner]] - miner
*[[Pyminer]] - Python miner, reference implementation
*[[Remote miner]] - mining pool software
*[[Open Source FGPA Bitcoin Miner]] - a miner that makes use of an FPGA Board
*[https://github.com/mkburza/Flash-Player-Bitcoin-Miner Flash Player Bitcoin Miner] - A proof of concept Adobe Flash Player miner

===Mining Pool Servers (backend)===
Main page: [[Poolservers]]

*[[ecoinpool]] - Erlang poolserver
*[[Eloipool]] - Fast Python3 poolserver
*[[Pushpoold]] - Old mining poolserver in C (not maintained)
*[[Poold]] - Old Python mining poolserver (not maintained)
*[[PoolServerJ]] - Java mining poolserver (not maintained)

===Utilities, libraries, and interfaces:===
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API
*[[libblkmaker]] - C library implementation of [[getblocktemplate]] decentralized mining protocol
*[[python-blkmaker]] - Python module implementation of [[getblocktemplate]] decentralized mining protocol

===Lists of software===
*[[BitGit]] - list of Bitcoin-related opensource projects hosted at Git

===Developer resources===
*[[:Category:Developer|Category:Developer]]
*[[:Category:Technical|Category:Technical]]
*[[Original Bitcoin client/API calls list]]
*[[API reference (JSON-RPC)]]
*[[PHP_developer_intro|PHP Developer Introduction]]

===Other===
*[[Namecoin]] - a distributed naming system based on Bitcoin technology
*[[Bitcoin Consultancy]] - an organization providing open source software and Bitcoin-related consulting
*[[Open Transactions]] - a financial crypto and digital cash software library, complementary to Bitcoin
*[[Moneychanger]] - Java-based GUI for [[Open Transactions]]
*[http://btcnames.org/ BTCnames] - a webbased aliasing service which allows to handle unlimited names for your BTC deposit hashes
*[[Devcoin]] - the open source developer coin

Bitcoinj

2013-03-31T12:44:01Z

Goonie: /* See Also */

An open source Bitcoin client library built using Java and implements the Bitcoin network protocol. With version 0.7, it was renamed to '''bitcoinj'''.

The project was announced on March 7, 2011<ref>[http://www.bitcoin.org/smf/index.php?topic=4236.msg61438#msg61438 ANNOUNCE - BitCoinJ v0.1, a client-mode implementation in Java]</ref>. The project was built by a Google employee as a "20 percent time" project<ref>[http://news.ycombinator.com/item?id=2297686 Comment by Google's Chris Dibona on Hacker News]</ref>.

==See Also==

* [[Bitcoin Wallet]] - a standalone wallet for Android and BlackBerry devices
* [[MultiBit]]

== Security ==
* [[Thin_Client_Security#BitCoinJ]]
* [http://code.google.com/p/bitcoinj/wiki/SecurityModel Security Model]

==External Links==

* [http://code.google.com/p/bitcoinj bitcoinj] project page on Google Code.

==References==
<references />
[[Category:API Bindings]]
[[Category:Nodes]]
[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/Apache2]]
[[Category:Open Source]]

Wallet

2013-03-31T12:43:00Z

Goonie: /* Bitcoin Wallet */

A Bitcoin '''wallet''' is a file that contains a collection of private keys.

=== Bitcoin Qt ===

The original Bitcoin client wallet file is named '''wallet.dat''' and contains<ref>[https://bitcointalk.org/index.php?topic=4448.0 Wallet import/export: bitkeys format]</ref>:

* keypairs for each of your [[address|addresses]]
* transactions done from/to your addresses
* user preferences
* default key
* reserve keys
* [[Accounts_explained|accounts]]
* a version number
* [[Key pool]]
* Since 0.3.21: information about the current best chain, to be able to rescan automatically when restoring from a backup.

The data file for the wallet is wallet.dat and is located in the [[data directory|Bitcoin data directory]].

It is intended that a wallet be used on only one installation of Bitcoin at a time. Attempting to clone a wallet for use on multiple computers will result in "weird behavior"<ref>[http://forum.bitcoin.org/index.php?topic=5324.msg77896#msg77896 Multiple instance of bitcoin with the same wallet]</ref>.

The format of this file is Berkeley DB. Tools that can manipulate wallet files include [[pywallet]].

=== Armory ===

The Armory client uses a custom [http://bitcoinarmory.com/index.php/armory-wallet-files binary wallet format].

=== Blockchain.info ===

Blockchain.info use a plain text JSON wallet format documented [https://blockchain.info/wallet/wallet-format here]. Private keys Keys are stored in base58.

=== Multibit ===

Multibit uses the bitcoinj [http://code.google.com/p/protobuf/ protobuf] wallet file.

=== [[Bitcoin Wallet]] ===

Bitcoin Wallet uses the bitcoinj [http://code.google.com/p/protobuf/ protobuf] format for its wallet file. However, due to Android isolation of applications, it is impossible to access the wallet file as a non-root user.

==See Also==

* [[Securing your wallet]]
* [[EWallet]]
* [[Deterministic Wallet]]
==References==
<references />

Bitcoin Wallet for Android

2013-03-31T12:41:07Z

Goonie: Goonie moved page Bitcoin Wallet for Android to Bitcoin Wallet: It's available for BlackBerry OS as well

#REDIRECT [[Bitcoin Wallet]]

Bitcoin Wallet

2013-03-31T12:41:07Z

Goonie: Goonie moved page Bitcoin Wallet for Android to Bitcoin Wallet: It's available for BlackBerry OS as well

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 2.3 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of April 2013, it is being used by 50.000 people.

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://code.google.com/p/bitcoin-wallet/downloads/list] direct download of releases and test versions
* [https://code.google.com/p/bitcoin-wallet/] project page on Google Code.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]

[[de:Bitcoin_Wallet]]

Developers

2013-03-31T12:37:23Z

Goonie:

* '''This list is not complete.''' Please make updates/corrections as needed.
* Attempt to sort by contribution
* Legend:
** "Author" = original author; "Lead" = current project lead
{|
| style="background:#90ff90" | active maintainer
| style="background:#ffffaa" | has made contributions
| style="background:#ff9090" | no involvement
|}

{|
! Name !! Reference !! bitcoinj !! BFGMiner !! Tools !! Spesmilo !! Gentoo !! Supybot !! Other
|-
| Satoshi Nakamoto
|style="background:#90ff90"|Author/Retired
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| Bitcoin original designer
|-
| [[Gavin Andresen]]
|style="background:#90ff90"|Lead
| {{Table Value No}}
| {{Table Value No}}
|style="background:#90ff90"|Author
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| sirius-m
|style="background:#90ff90"|Retired
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| tcatm
| {{Table Value Yes}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
|-
| Jeff Garzik
| {{Table Value Yes}}
| {{Table Value No}}
|style="background:#90ff90"|Retired
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|style="background:#90ff90"|pushpool
|-
| TD
| {{Table Value No}}
|style="background:#90ff90"|Author
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Daniel Folkinshteyn
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
|-
| Luke Dashjr
| {{Table Value Yes}}
| {{Table Value No}}
|style="background:#90ff90"|Maintainer
| {{Table Value No}}
| {{Table Value Yes}}
| {{Table Value Yes}}
| {{Table Value Yes}}
|style="background:#90ff90"|URI, Wallet protocols, Eloipool
|-
| genjix
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|style="background:#90ff90"|Author
| {{Table Value No}}
| {{Table Value No}}
| https://bitcoinconsultancy.com/wiki/index.php/Libbitcoin
|-
| Matt Giuca
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Con Kolivas
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Mizery De Aria
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|style="background:#90ff90"|Author
| {{Table Value No}}
|-
| Laurent Bachelier
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
| {{Table Value No}}
|-
| Florian Schmaus
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
| {{Table Value No}}
|-
| BioMike
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value Yes}}
| {{Table Value No}}
|-
| Chris Moore
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Matt Corallo
| {{Table Value Yes}}
| {{Table Value Yes}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Pieter Wuille
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Marius Hanne
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| David FRANCOIS
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Nils Schneider
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Giel van Schijndel
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Fabian H jr.
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| ovdeathiam
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Dev Random
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Michal Zima
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Venkatesh Srinivas
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Vegard Nossum
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| JoelKatz
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Joerie de Gram
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Johannes Henninger
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Jeroenz0r
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Han Lin Yap
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Wladimir J. van der Laan
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Abraham Jewowich
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Michael Bemmerl
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Eric Hosmer
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Dawid Spiechowicz
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Stéphane Gimenez
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Patrick Varilly
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Jay Weisskopf
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Dylan Noblesmith
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| James Burkle
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Jordan Lewis
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Dean Lee
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| xHire
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| HostFat
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Jakob Kramer
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| ariel
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| dabaopku
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Federico Faggiano
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| m0ray
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Danube
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Carlos Pizarro
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Blitzboom
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Daniel Holbert
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Jaromil
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Carlo Alberto Ferraris
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Forrest Voight
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Amir Yalon
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| John Maguire
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Ricardo M. Correia
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Dan Helfman
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| gjs278
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Dan Loewenherz
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Eric Swanson
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Santiago M. Mola
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Shane Wegner
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Sven Slootweg
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| ojab
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| sandos
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| Witchspace
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|-
| laszloh
|style="background:#ffffaa"|
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
| {{Table Value No}}
|}

==See Also==

* [[Original client developers]]
* [[People]]

[[Category:Developer]]

Infrastructure

2013-03-31T12:36:10Z

Goonie: /* User Interface */

== Overview ==

=== Components ===
*Peer/Node -- Maintains connections with the BitCoin network, and relays BitCoin traffic based on policies.
*Wallet -- Maintains private key database, and controls balances for the user.
*UI -- End-user interface. Could be a wx/Qt/GTK GUI, CLI, Android app, iPhone app, etc...
*Miner -- Tries to solve blocks for the wallet.

=== Protocols ===
*p2p -- Used for communication between Peers/Nodes, and also between your personal Peer/Node and your Wallet(s)
*JSON-RPC -- Old wallet-control protocol; suitable for web integration
*wallet -- Used for communication between your Wallet(s) and your Miner(s) and User Interface(s)

=== Diagram ===
___________
| |--(p2p protocol)---ooooooooooooooo
| Peer/Node |--(p2p protocol)--o Other Peers o
|___________|--(p2p protocol)---ooooooooooooooo
|
(p2p protocol)
_____|_____ _________
| | | |
| Wallet |--(wallet protocol)--| Miner |
|___________| |_________|
|
(wallet protocol)
_____|__________
| |
| User Interface |
|________________|

== Implementations ==
=== Peer/Node ===
{| class="wikitable"
|-
! Software
|-
| [[bitcoin.pl]]
|-
| [[bitcoind]]
|-
| [[bitcoin-alt]]
|-
| [[BitCoinJ|bitcoinj]]
|-
| [[Pycoin]]
|-
| [[wxBitcoin]]
|-
| [[QBitcoin|QBitcoin CORE]]
|}

=== Wallet ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[bitcoind]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[BitCoinJ|bitcoinj]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[wxBitcoin]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[QBitcoin Wallet]] || {{Table Value Unknown}} || {{Table Value No}}
|}

=== Miner ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[Cpu_Miner]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[DiabloMiner]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[Poclbm]] || {{Table Value Yes}} || {{Table Value No}}
|}

=== User Interface ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[Bitcoin-js-remote]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[BitCoinJ|bitcoinj]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[BitDroid]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin API Client]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin CLI]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin GUI]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[Java Bitcoin Client]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[Spesmilo]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[wxBitcoin]] || {{Table Value No}} || {{Table Value No}}
|}

Infrastructure

2013-03-31T12:35:30Z

Goonie: /* Wallet */

== Overview ==

=== Components ===
*Peer/Node -- Maintains connections with the BitCoin network, and relays BitCoin traffic based on policies.
*Wallet -- Maintains private key database, and controls balances for the user.
*UI -- End-user interface. Could be a wx/Qt/GTK GUI, CLI, Android app, iPhone app, etc...
*Miner -- Tries to solve blocks for the wallet.

=== Protocols ===
*p2p -- Used for communication between Peers/Nodes, and also between your personal Peer/Node and your Wallet(s)
*JSON-RPC -- Old wallet-control protocol; suitable for web integration
*wallet -- Used for communication between your Wallet(s) and your Miner(s) and User Interface(s)

=== Diagram ===
___________
| |--(p2p protocol)---ooooooooooooooo
| Peer/Node |--(p2p protocol)--o Other Peers o
|___________|--(p2p protocol)---ooooooooooooooo
|
(p2p protocol)
_____|_____ _________
| | | |
| Wallet |--(wallet protocol)--| Miner |
|___________| |_________|
|
(wallet protocol)
_____|__________
| |
| User Interface |
|________________|

== Implementations ==
=== Peer/Node ===
{| class="wikitable"
|-
! Software
|-
| [[bitcoin.pl]]
|-
| [[bitcoind]]
|-
| [[bitcoin-alt]]
|-
| [[BitCoinJ|bitcoinj]]
|-
| [[Pycoin]]
|-
| [[wxBitcoin]]
|-
| [[QBitcoin|QBitcoin CORE]]
|}

=== Wallet ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[bitcoind]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[BitCoinJ|bitcoinj]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[wxBitcoin]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[QBitcoin Wallet]] || {{Table Value Unknown}} || {{Table Value No}}
|}

=== Miner ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[Cpu_Miner]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[DiabloMiner]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[Poclbm]] || {{Table Value Yes}} || {{Table Value No}}
|}

=== User Interface ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[Bitcoin-js-remote]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[BitCoinJ]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[BitDroid]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin API Client]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin CLI]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin GUI]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[Java Bitcoin Client]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[Spesmilo]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[wxBitcoin]] || {{Table Value No}} || {{Table Value No}}
|}

Infrastructure

2013-03-31T12:35:14Z

Goonie: /* Peer/Node */

== Overview ==

=== Components ===
*Peer/Node -- Maintains connections with the BitCoin network, and relays BitCoin traffic based on policies.
*Wallet -- Maintains private key database, and controls balances for the user.
*UI -- End-user interface. Could be a wx/Qt/GTK GUI, CLI, Android app, iPhone app, etc...
*Miner -- Tries to solve blocks for the wallet.

=== Protocols ===
*p2p -- Used for communication between Peers/Nodes, and also between your personal Peer/Node and your Wallet(s)
*JSON-RPC -- Old wallet-control protocol; suitable for web integration
*wallet -- Used for communication between your Wallet(s) and your Miner(s) and User Interface(s)

=== Diagram ===
___________
| |--(p2p protocol)---ooooooooooooooo
| Peer/Node |--(p2p protocol)--o Other Peers o
|___________|--(p2p protocol)---ooooooooooooooo
|
(p2p protocol)
_____|_____ _________
| | | |
| Wallet |--(wallet protocol)--| Miner |
|___________| |_________|
|
(wallet protocol)
_____|__________
| |
| User Interface |
|________________|

== Implementations ==
=== Peer/Node ===
{| class="wikitable"
|-
! Software
|-
| [[bitcoin.pl]]
|-
| [[bitcoind]]
|-
| [[bitcoin-alt]]
|-
| [[BitCoinJ|bitcoinj]]
|-
| [[Pycoin]]
|-
| [[wxBitcoin]]
|-
| [[QBitcoin|QBitcoin CORE]]
|}

=== Wallet ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[bitcoind]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[BitCoinJ]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[wxBitcoin]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[QBitcoin Wallet]] || {{Table Value Unknown}} || {{Table Value No}}
|}

=== Miner ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[Cpu_Miner]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[DiabloMiner]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[Poclbm]] || {{Table Value Yes}} || {{Table Value No}}
|}

=== User Interface ===
{| class="wikitable"
|-
! Software !! Old JSON-RPC !! New [[Wallet protocol]]
|-
| [[Bitcoin-js-remote]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[BitCoinJ]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[BitDroid]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin API Client]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin CLI]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[QBitcoin|QBitcoin GUI]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[Java Bitcoin Client]] || {{Table Value Unknown}} || {{Table Value No}}
|-
| [[Spesmilo]] || {{Table Value Yes}} || {{Table Value No}}
|-
| [[wxBitcoin]] || {{Table Value No}} || {{Table Value No}}
|}

Bitcoin Wallet

2013-03-31T12:33:48Z

Goonie:

[[File:bitcoin_wallet.png|192px]]

An open-source and free wallet implementation for the Android runtime, based on [[BitCoinJ|bitcoinj]]. It requires either Android 2.3 (or newer) or Black Berry OS 10 (or newer). It was first released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. As of April 2013, it is being used by 50.000 people.

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://code.google.com/p/bitcoin-wallet/downloads/list] direct download of releases and test versions
* [https://code.google.com/p/bitcoin-wallet/] project page on Google Code.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]

[[de:Bitcoin_Wallet]]

Wallet

2013-03-31T12:27:57Z

Goonie:

A Bitcoin '''wallet''' is a file that contains a collection of private keys.

=== Bitcoin Qt ===

The original Bitcoin client wallet file is named '''wallet.dat''' and contains<ref>[https://bitcointalk.org/index.php?topic=4448.0 Wallet import/export: bitkeys format]</ref>:

* keypairs for each of your [[address|addresses]]
* transactions done from/to your addresses
* user preferences
* default key
* reserve keys
* [[Accounts_explained|accounts]]
* a version number
* [[Key pool]]
* Since 0.3.21: information about the current best chain, to be able to rescan automatically when restoring from a backup.

The data file for the wallet is wallet.dat and is located in the [[data directory|Bitcoin data directory]].

It is intended that a wallet be used on only one installation of Bitcoin at a time. Attempting to clone a wallet for use on multiple computers will result in "weird behavior"<ref>[http://forum.bitcoin.org/index.php?topic=5324.msg77896#msg77896 Multiple instance of bitcoin with the same wallet]</ref>.

The format of this file is Berkeley DB. Tools that can manipulate wallet files include [[pywallet]].

=== Armory ===

The Armory client uses a custom [http://bitcoinarmory.com/index.php/armory-wallet-files binary wallet format].

=== Blockchain.info ===

Blockchain.info use a plain text JSON wallet format documented [https://blockchain.info/wallet/wallet-format here]. Private keys Keys are stored in base58.

=== Multibit ===

Multibit uses the bitcoinj [http://code.google.com/p/protobuf/ protobuf] wallet file.

=== [[Bitcoin_Wallet_for_Android|Bitcoin Wallet]] ===

Bitcoin Wallet uses the bitcoinj [http://code.google.com/p/protobuf/ protobuf] format for its wallet file. However, due to Android isolation of applications, it is impossible to access the wallet file as a non-root user.

==See Also==

* [[Securing your wallet]]
* [[EWallet]]
* [[Deterministic Wallet]]
==References==
<references />

Wallet

2013-03-31T12:24:26Z

Goonie: /* Multibit */

A Bitcoin '''wallet''' is a file that contains a collection of private keys.

=== Bitcoin Qt ===

The original Bitcoin client wallet file is named '''wallet.dat''' and contains<ref>[https://bitcointalk.org/index.php?topic=4448.0 Wallet import/export: bitkeys format]</ref>:

* keypairs for each of your [[address|addresses]]
* transactions done from/to your addresses
* user preferences
* default key
* reserve keys
* [[Accounts_explained|accounts]]
* a version number
* [[Key pool]]
* Since 0.3.21: information about the current best chain, to be able to rescan automatically when restoring from a backup.

The data file for the wallet is wallet.dat and is located in the [[data directory|Bitcoin data directory]].

It is intended that a wallet be used on only one installation of Bitcoin at a time. Attempting to clone a wallet for use on multiple computers will result in "weird behavior"<ref>[http://forum.bitcoin.org/index.php?topic=5324.msg77896#msg77896 Multiple instance of bitcoin with the same wallet]</ref>.

The format of this file is Berkeley DB. Tools that can manipulate wallet files include [[pywallet]].

=== Armory ===

The Armory client uses a custom [http://bitcoinarmory.com/index.php/armory-wallet-files binary wallet format].

=== Blockchain.info ===

Blockchain.info use a plain text JSON wallet format documented [https://blockchain.info/wallet/wallet-format here]. Private keys Keys are stored in base58.

=== Multibit ===

Multibit uses the bitcoinj [http://code.google.com/p/protobuf/ protobuf] wallet file.

==See Also==

* [[Securing your wallet]]
* [[EWallet]]
* [[Deterministic Wallet]]
==References==
<references />

MultiBit

2013-03-31T12:23:27Z

Goonie:

[[Image:MultiBit_0.4.23_screenshot_WinXP.png|right|800px|screenshot of Multibit with its Windows XP GUI and Metal theme]]
[http://multibit.org MultiBit] is a lightweight "[[Thin Client Security|thin client]]" Bitcoin wallet for Windows, MacOS and Linux based on [[BitCoinJ|bitcoinj]]. Its main advantages over the [[Bitcoin-Qt#Criticism|original Bitcoin client]] include support for opening multiple wallets simultaneously, and not requiring the download of the entire multi-gigabyte [[block chain]] (2.6GB as of July 2012<ref>[http://bitcoin.stackexchange.com/questions/4115/how-big-is-the-blockchain-on-disk-as-of-5th-july-2012 How big is the blockchain on disk as of 5th July 2012?]</ref>). The project is lead by UK developer Jim Burton.<ref>[http://www.youtube.com/watch?v=MnkssdmlaWw European Bitcoin Conference 2012 - Jim Burton - Multibit]</ref>

==Features==
* Multiple wallets can be open at the same time
* Synchronizes with the network in minutes
* Shows the last BTC <--> USD rate from [[MtGox]], [[VirtEx]] and other exchanges
* Import and export your private keys
* Chart of your balance over the last 30 days
* Free and open source (MIT license)
* Localized in a variety of languages

==History==
MultiBit was announced on September 12, 2011.<ref>[http://bitcointalk.org/index.php?topic=43616.0 MultiBit]</ref>

==See Also==
* [[Thin Client Security]]

==External Links==
* [http://multibit.org MultiBit] project website
* [https://github.com/jim618/multibit GitHub repo]
* [https://groups.google.com/forum/?fromgroups=#!forum/bitcoin-multibit Google Group]
* [http://www.youtube.com/user/MultiBitOrg YouTube channel] with "getting started" screencast

==References==
<references />

[[Category:Clients]]
[[Category:Open Source]]

Java Bitcoin Client

2013-03-31T12:22:41Z

Goonie: /* See Also */

{{stub}}
'''Java Bitcoin Client''' is a [[Bitcoin]] frontend / API written in java.

==See Also==

* [[BitCoinJ|bitcoinj]]
* [[Bitcoin-JSON-RPC-Client]]

==External links==

*[http://sourceforge.net/projects/bitcoin-client/ Java Bitcoin Client sourceforge project page]

[[Category:API Bindings]]
[[Category:Frontends]]
[[Category:Free Software]]
[[Category:License/Apache]]
[[Category:Open Source]]

Thin Client Security

2013-03-31T12:21:54Z

Goonie: /* BitCoinJ */

Recently there have been a number of proposals for bitcoin clients which do not store a complete copy of every block in the entire block chain. This page will refer to all such clients as "thin clients". This page is meant to be a place to try to make sense of the security and trust implications of the various schemes.

== Block Height vs. Depth ==

It is important to distinguish between block height verification and block depth verification.

A client verifies the height H of a block by checking that there are H block '''before''' it, all of which are well-formed and obey the maximum-difficulty-adjustment-rate rule. Currently only the Satoshi client and libbitcoin do block height verification. Block height is the fundamental anchor of trustless security in the Bitcoin system.

A client verifies the depth D of a block by checking that there are D blocks '''after''' it (also called "confirmations"), all of which are well-formed. SPV clients substitute block depth for block height as a transaction validity check. All clients use block depth as a measure of the liklihood of a [[Chain_Reorganization|blockchain reorganization]] producing a new longer fork which excludes the transaction (i.e. [[Orphan_Block|orphaning]] its block).

See also [https://bitcointalk.org/index.php?topic=88208.msg987429#msg987429 some comments on probabilistic verification of block height].

== Full-Chain Clients ==

The "thick" bitcoin client downloads a copy of the entire chain, including all transactions (not just headers). It will be used as the reference point for security comparisions below.

=== Block '''Height''' as a Transaction Validity Check ===

A full-chain client trusts the difficultywise-longest [https://en.bitcoin.it/wiki/Protocol_rules#Blocks well-formed] blockchain it can find. Any transaction on the difficultywise-longest well-formed chain is considered valid. Therefore, the validity of a transaction is determined by its height -- i.e. how many blocks come ''before'' it. A transaction's ''depth'' (the number of blocks ''after'' it) is used to determine the likelihood of the transaction being invalidated due to the emergence of a longer fork.

== Header-Only Clients ==

These client downloads a complete copy of the headers for all blocks in the entire blockchain. This means that the download and storage requirements scale linearly with the amount of time since bitcoin was invented; it would be preferable to have the scaling be logarithmic or even constant.

=== Simplified Payment Verification (SPV) ===

This scheme is described in section 8 of the [http://bitcoin.org/bitcoin.pdf original bitcoin whitepaper].

==== Block '''Depth''' as a Transaction Validity Check ====

As Satoshi writes, "[the thin client] can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it." If we take "X" to be the "number of blocks added after it", then SPV essentially trusts that a transaction X blocks deep in the chain does not have inputs which were already spent further back in the chain. Therefore, the validity of a transaction is determined by its depth -- i.e. how many blocks come ''after'' it. Other thin client protocols also include this assumption.

This is very different from the trust model in the "thick" client: the thick client verifies that a transaction's inputs are unspent by actually checking the whole chain up to that point -- there is no "X blocks deep" involved here. The thick client uses "X blocks deep" (aka "confirmations") only once it has already decided that a transaction is valid (i.e. no [[Double-spending|double-spends]]). At that point it uses "X blocks deep" to decide how likely it is that a longer fork in the chain will emerge which excludes that transaction.

It is very important to understand how the same property ("X blocks deep") is used to verify two different properties in the thick client and SPV cases. '''The thick client never uses block depth as a measure of transaction validity; the SPV client does'''.

This is a concern in a situation where an SPV client is subjected to a double-spend attack by somebody who controls its network connection. For example, suppose you are at a wi-fi cafe and are paying for something using your smartphone -- the cafe owner controls your network connection. Satoshi acknowledges this implicitly when he writes that "the verification is reliable as long as honest nodes control the network" -- to be completely pedantic, this means that the verification is reliable as long as honest nodes control '''the part of the network that the SPV client is able to communicate with'''. In an attack-by-ISP scenario this may not be a sufficiently strong security property. The attacker would not need to overpower "the rest of the network" because the client is unable to communicate with it.

==== [[BitCoinJ|bitcoinj]] ====

Simplified Payment Verification is the verification mechanism used in [[BitCoinJ|bitcoinj]].

A security analysis of some of the issues in bitcoinj can be found [http://code.google.com/p/bitcoinj/wiki/SecurityModel here]; however:

* The claim that "picking 10 nodes and requiring all of them to be consistent needs much less trust" overlooks the problem of [https://en.bitcoin.it/wiki/Weaknesses#Cancer_nodes "cancer nodes"] and [http://en.wikipedia.org/wiki/Sybil_attack Sybil attacks].
* Many of the security claims are qualified by some form of "if you don't think an attacker controls your internet connection"; see the previous section for a discussion of why this is problematic.

==== [https://bitcointalk.org/index.php?topic=128055.0 picocoin] ====

Simplified Payment Verification is the verification mechanism used in picocoin.

The library (libccoin) that picocoin is based on includes code for validating scripts and blocks; this could potentially be used to implement a full-chain client.

=== Unused Output Tree in the Blockchain (UOT) ===

There have been several proposals (the first appears to be [https://bitcointalk.org/index.php?topic=21995.0 this one] by gmaxwell, who called it an "open transaction tree", although the term "open" is now taken to mean "not yet mined into the blockchain" rather than "unspent") to form a tree of unused transaction outputs at each block in the chain, hash it as a Merkle tree, and encode the root hash in the block chain (probably as part of the coinbase input). This will be called an Unused Output Tree (UOT). The first detailed proposal so far appears to be [https://en.bitcoin.it/wiki/User:DiThi/MTUT Alberto Torres' proposal]; etotheipi's [https://bitcointalk.org/index.php?topic=88208.0 ultimate blockchain compression] is a variant of this.

If such UOT hashes were included in the blockchain, a client which shipped with a [https://en.bitcoin.it/wiki/Vocabulary checkpoint] block that had a UOT would only need to download blocks after the checkpoint. Moreover, once the client had downloaded those blocks and confirmed their UOTs, it could discard all but the most recent block containing a UOT.

This would also let a thin client reduce the question of "is this output unspent" to the question of "is this block super-well-formed" where "well-formed" means "well-formed according to the normal blockchain rules and additionally has an Unused Output Tree which is accurate and truthful". This is still a long way from the low level of trust involved in the thick client, but it is a major improvement over all existing proposals.

It is unlikely that bitcoin would ever arrive at a state where every single block had a UOT, since this would require upgrading 100% of the miners on the network, or else convincing enough miners to reject blocks which do not contain a UOT. The latter strategy risks creating blockchain forks, which can be expensive (in reward terms) to miners. Therefore, any UOT strategy would need to cope with the fact that not every block contains a UOT.

Hostile miners may insert blocks into the chain which have what claims to be a UOT, but which is actually invalid. It is unlikely that such blocks could be kept out of the chain because, again, this would require adding a new block well-formedness criterion, and miners implementing this new criterion would risk "mining on the wrong side" of a fork, which could cost them a lot of money. Therefore, any UOT strategy would need to cope with the fact that not every block containing a UOT entry can be trusted.

Note that at the present moment no standard format for such Unused Output Tree hashes has been agreed upon, nor do any of the blocks in the chain contain them. The [https://bitcointalk.org/index.php?topic=91954 ultraprune] feature added to bitcoind-0.8 maintains a similar data structure on the client's disk. It does not put this data structure or its hash anywhere in the blockchain.

== Server-Trusting Clients ==

These clients involve some (usually low) level of trust in the server they rely upon. Mechanisms for authenticating the server, and for confirming that the server has not been compromised, are usually not explained.

All thin clients listed below currently connect to a single server, and are vulnerable to an attack similar to a double-spend. The attack can be run by that single server - the server can just lie to them that they received a Bitcoin transaction, and they, assuming the server does not lie, perform some service, transfer funds or send goods without actually receiving any Bitcoin in exchange. Therefore, they are implicitly trusting it.

Future enhancements have been suggested that will have the client talk to multiple servers and broadcast transactions and query all of them. Unfortunately it is well known to security researchers that this does not actually increase security; it simply makes the exploits more complicated and difficult to find. Security researchers have a name for this phenomenon: it is called a "Sybil attack"<ref>http://en.wikipedia.org/wiki/Sybil_attack</ref>. [https://bitcointalk.org/index.php?topic=88208.msg975201#msg975201 This post] on bitcointalk explains how some governments (notably Iran and China) already perform these sorts of attacks on their own citizens, with the coerced assistance of SSL certificate authorities.

Clients with a checkpoint (even a very old one) that download and validate the headers for the whole blockchain are [http://bitcoinmedia.com/the-irc-bootstrap-method-is-flawed/#comment-4243 not vulnerable] to Sybil attacks in the following sense: they can always ensure that an attack would cost more than the amount being stolen.

=== [[BCCAPI]] ===

=== [[Electrum]] ===

== Other ==

* A [http://sourceforge.net/mailarchive/message.php?msg_id=28633866 thread] on bitcoin-dev
* A [http://bitcoin.stackexchange.com/questions/2584/is-reclaiming-disk-space-already-implemented-how-effective-will-it-be/2589 question] on bitcoin.stackexchange.com
* The [https://en.bitcoin.it/wiki/Weaknesses#Cancer_nodes "cancer nodes"] paragraph explains some of the issues with thin clients that base security on trusting whatever "a majority of the IP addresses I can see" say.
* [http://bitcoin.stackexchange.com/questions/2613/how-secure-are-various-models-of-bitcoin-clients related discussion on Stack Exchange]
* A hypothesized [https://bitcointalk.org/index.php?topic=134318.msg1441171#msg1441171 intermediate security class] between SPV and full-chain validation.

<references>

[[Category:Technical]]
[[category:Clients]]
[[Category:Security]]

Bitcoinj

2013-03-31T12:20:55Z

Goonie: /* External Links */

An open source Bitcoin client library built using Java and implements the Bitcoin network protocol. With version 0.7, it was renamed to '''bitcoinj'''.

The project was announced on March 7, 2011<ref>[http://www.bitcoin.org/smf/index.php?topic=4236.msg61438#msg61438 ANNOUNCE - BitCoinJ v0.1, a client-mode implementation in Java]</ref>. The project was built by a Google employee as a "20 percent time" project<ref>[http://news.ycombinator.com/item?id=2297686 Comment by Google's Chris Dibona on Hacker News]</ref>.

==See Also==

* [[Bitcoin Wallet for Android]] - a standalone wallet for Android devices
* [[MultiBit]]

== Security ==
* [[Thin_Client_Security#BitCoinJ]]
* [http://code.google.com/p/bitcoinj/wiki/SecurityModel Security Model]

==External Links==

* [http://code.google.com/p/bitcoinj bitcoinj] project page on Google Code.

==References==
<references />
[[Category:API Bindings]]
[[Category:Nodes]]
[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/Apache2]]
[[Category:Open Source]]

Bitcoinj

2013-03-31T12:20:23Z

Goonie:

An open source Bitcoin client library built using Java and implements the Bitcoin network protocol. With version 0.7, it was renamed to '''bitcoinj'''.

The project was announced on March 7, 2011<ref>[http://www.bitcoin.org/smf/index.php?topic=4236.msg61438#msg61438 ANNOUNCE - BitCoinJ v0.1, a client-mode implementation in Java]</ref>. The project was built by a Google employee as a "20 percent time" project<ref>[http://news.ycombinator.com/item?id=2297686 Comment by Google's Chris Dibona on Hacker News]</ref>.

==See Also==

* [[Bitcoin Wallet for Android]] - a standalone wallet for Android devices
* [[MultiBit]]

== Security ==
* [[Thin_Client_Security#BitCoinJ]]
* [http://code.google.com/p/bitcoinj/wiki/SecurityModel Security Model]

==External Links==

* [http://code.google.com/p/bitcoinj BitCoinJ] project page on Google Code.

==References==
<references />
[[Category:API Bindings]]
[[Category:Nodes]]
[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/Apache2]]
[[Category:Open Source]]

Bitcoin

2013-03-31T12:16:29Z

Goonie: /* Node operation */

'''Bitcoin''' is a decentralized [[digital currency]] created by developer [[Satoshi Nakamoto]]. It does not rely on a central server to process transactions or store funds. There are a maximum of 2,100,000,000,000,000 Bitcoin elements (called satoshis), currently most commonly measured in units of 100,000,000 known as BTC.

It is the most widely used alternative currency,<ref name="Quantitative Analysis of the Full Bitcoin Transaction Graph">{{cite web|title=Quantitative Analysis of the Full Bitcoin Transaction Graph|url=http://eprint.iacr.org/2012/584.pdf|publisher=Cryptology ePrint Archive|accessdate=18 October 2012|author=Ron Dorit|coauthors=Adi Shamir|page=17|quote=The Bitcoin system is the best known and most widely used alternative payment scheme,...}}</ref> with the total market cap at over 100 million US dollars.<ref>{{cite web|last=Koch|first=Rüdiger|title=Bitcoin - a Means for Redistribution of Wealth|url=http://ieet.org/index.php/IEET/more/koch20120927|publisher=Institute for Ethics & Emerging Technologies|accessdate=27 October 2012|quote=We’re currently at 50,000 users and a market cap of $100 Million.}}</ref><ref>{{cite web|title=Market Capitalization|url=http://blockchain.info/charts/market-cap|publisher=Blockchain.info|accessdate=28 October 2012}}</ref><ref name="Mt.Gox data">{{Cite web|title=Mt.Gox data|url=http://bitcoincharts.com/markets/mtgoxUSD.html|publisher=Bitcoincharts}}</ref>

Bitcoin has no central issuer; instead, the peer-to-peer network regulates Bitcoins, transactions and issuance according to consensus in network software.
Bitcoins are issued to various nodes that verify transactions through computing power;
it is established that there will be a limited and scheduled release of no more than 21 million BTC worth of coins, which will be fully issued by the year 2140.

Internationally, Bitcoins can be exchanged and managed through various websites and [[software]] along with physical banknotes and coins.<ref>{{Cite web|title=Physical Bitcoins by Casascius|url=https://www.casascius.com/|publisher=Casascius Coins|accessdate=29 September 2012}}</ref><ref>{{Cite web|title=Bitbills|url=http://www.bitbills.com/|publisher=Bitbills|accessdate=29 September 2012}}</ref>

==History==
:Main article: [[History]]

A cryptographic system for untraceable payments was first described by David Chaum in 1982.<ref>[http://blog.koehntopp.de/uploads/Chaum.BlindSigForPayment.1982.PDF David Chaum, Blind signatures for untraceable payments], Advances in Cryptology - Crypto '82, Springer-Verlag (1983), 199–203.</ref> In 1990 Chaum extended this system to create the first cryptographic anonymous electronic cash system.,<ref>{{cite journal|journal=Lecture Notes in Computer Science|last1=Chaum|first1=David|last2=Fiat|first2=Amos|last3=Naor|first3=Moni|title=Untraceable Electronic Cash|url=http://blog.koehntopp.de/uploads/chaum_fiat_naor_ecash.pdf}}</ref> which became known as ecash.
<ref>{{cite web|url=http://www.wired.com/wired/archive/2.12/emoney.html|publisher=Wired|title=E-Money (That's What I Want)|date=1994–2012|author=Steven Levy}}</ref> In 1998 Wei Dai published a description of an anonymous, distributed electronic cash system which he called "b-money".<ref>{{cite web|title=B-Money|url=http://www.weidai.com/bmoney.txt|author=Wei Dai|year=1998}}</ref> Around the same time, Nick Szabo created ''bit gold''.<ref>{{cite web|url=http://spectrum.ieee.org/computing/software/bitcoin-the-cryptoanarchists-answer-to-cash/0|title=Bitcoin: The Cryptoanarchists’ Answer to Cash|publisher=IEEE Spectrum|quote=Around the same time, Nick Szabo, a computer scientist who now blogs about law and the history of money, was one of the first to imagine a new digital currency from the ground up. Although many consider his scheme, which he calls “bit gold,” to be a precursor to Bitcoin}}</ref><ref name="bitgold">{{cite web|title=Bit gold|url=http://unenumerated.blogspot.co.uk/2005/12/bit-gold.html|author=Nick Szabo|quote=My proposal for bit gold is based on computing a string of bits from a string of challenge bits, using functions called variously "client puzzle function," "proof of work function," or "secure benchmark function.". The resulting string of bits is the proof of work.... The last-created string of bit gold provides the challenge bits for the next-created string.}}</ref> Like Bitcoin, ''Bit gold'' was a currency system where users would compete to solve a [[proof of work]] function, with solutions being cryptographically chained together and published via a distributed property title registry. A variant of ''Bit gold'', called ''Reusable Proofs of Work'', was implemented by Hal Finney.<ref name="bitgold"/>

In 2008, Satoshi Nakamoto published a paper<ref name="whitepaper">{{cite web
|last= Nakamoto
|first= Satoshi
|title= Bitcoin: A Peer-to-Peer Electronic Cash System
|url= http://www.cs.kent.edu/~JAVED/class-P2P12F/papers-2012/PAPER2012-p2p-bitcoin-satoshinakamoto.pdf
|accessdate = 14 December 2010
|date= 24 May 2009
|postscript=
}}</ref><ref>{{cite web
|url= http://article.gmane.org/gmane.comp.encryption.general/12588/
|title= Bitcoin P2P e-cash paper
}}</ref> on The Cryptography Mailing list at metzdowd.com<ref>[http://www.mail-archive.com/search?l=cryptography@metzdowd.com&q=from:%22Satoshi+Nakamoto%22 Satoshi's posts to Cryptography mailing list]</ref> describing the Bitcoin protocol.

The Bitcoin network came into existence on 3 January 2009 with the release of the first Bitcoin client, [[wxBitcoin]], and the issuance of the first Bitcoins.<ref>{{cite web |title=Block 0 – Bitcoin Block Explorer |url=http://blockexplorer.com/block/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f }}</ref><ref>{{cite web |url=http://www.mail-archive.com/cryptography@metzdowd.com/msg10142.html |title=Bitcoin v0.1 released}}</ref><ref>{{cite web |url=http://sourceforge.net/news/?group_id=244765 |title=SourceForge.net: Bitcoin}}</ref>
A year after, the initial exchange rates for Bitcoin were set by individuals on the bitcointalk forums.{{Citation needed|date=October 2012}} The most significant transaction involved a 10,000 BTC pizza.<ref>{{cite web|title=The Rise and Fall of Bitcoin|url=http://www.wired.com/magazine/2011/11/mf_bitcoin/|publisher=Wired|accessdate=13 October 2012}}</ref>
Today, the majority of Bitcoin exchanges occur on the [[MtGox]] Bitcoin exchange.

In 2011, Wikileaks,<ref>{{cite news
|last= Greenberg
|first= Andy
|url= http://blogs.forbes.com/andygreenberg/2011/06/14/wikileaks-asks-for-anonymous-bitcoin-donations/
|title= WikiLeaks Asks For Anonymous Bitcoin Donations – Andy Greenberg – The Firewall – Forbes
|publisher= Blogs.forbes.com
|date= 2011-06-14
|accessdate = 2011-06-22
}}</ref> [[Freenet]],<ref>{{cite web
|url= https://freenetproject.org/donate.html
|title= /donate
|publisher= The Freenet Project
|date=
|accessdate = 2011-06-22
}}</ref> Singularity Institute,<ref>[http://singinst.org/donate/ SIAI donation page]</ref> Internet Archive,<ref>[http://www.archive.org/donate/index.php Internet Archive donation page]</ref> Free Software Foundation<ref>[https://my.fsf.org/donate/other/ Other ways to donate]</ref> and others, began to accept donations in Bitcoin. The Electronic Frontier Foundation did so for a while but has since stopped, citing concerns about a lack of legal precedent about new currency systems, and because they "generally don't endorse any type of product or service."<ref>{{cite web
|url= https://www.eff.org/deeplinks/2011/06/eff-and-bitcoin
|title= EFF and Bitcoin | Electronic Frontier Foundation
|publisher= Eff.org
|date= 2011-06-14
|accessdate = 2011-06-22
}}</ref> Some small businesses had started to adopt Bitcoin. LaCie, a public company, accepts Bitcoin for its Wuala service.<ref>{{Cite web|url=http://www.wuala.com/en/bitcoin |title=Secure Online Storage – Backup. Sync. Share. Access Everywhere |publisher=Wuala |date= |accessdate = 2012-01-24}}</ref>

In 2012, BitPay reports of having over 1000 merchants accepting Bitcoin under its payment processing service.<ref>{{cite web|title=BitPay Signs 1,000 Merchants to Accept Bitcoin Payments|url=http://www.americanbanker.com/issues/177_176/bitpay-signs-1000-merchants-to-accept-bitcoin-payments-1052538-1.html|publisher=American Banker|accessdate=12 October 2012}}</ref>

==Administration==
Bitcoin is administered through a decentralized peer-to-peer network.<ref name="whitepaper"/> Cryptographic technologies and the peer-to-peer network of computing power enables users to make and verify irreversible, instant online Bitcoin payments, without an obligation to trust and use centralized banking institutions and authorities. Dispute resolution services are not made directly available. Instead it is left to the users to verify and trust the parties they are sending money to through their choice of methods.

Bitcoins are issued according to rules agreed to by the majority of the computing power within the Bitcoin network. The core rules describing the predictable issuance of Bitcoins to its verifying servers, a voluntary and competitive transaction fee system and the hard limit of no more than 21 million BTC issued in total.<ref name="whitepaper"/>

Bitcoin does not require a central bank, State,<ref>{{cite web
|url= http://spectrum.ieee.org/computing/software/bitcoin-the-cryptoanarchists-answer-to-cash/3
|title= Bitcoin: The Cryptoanarchists' Answer to Cash
|publisher= IEEE.org
|date= June 2012
|accessdate = 2012-06-05
}}</ref> or incorporated backers.

==Services==
:Main article: [[Wallet]]

Bitcoins are sent and received through software and websites called wallets. They send and confirm transactions to the network through Bitcoin addresses, the identifiers for users' Bitcoin wallets within the network.<ref name="whitepaper"/>

===Bitcoin addresses===
:Main article: [[Address]]

Payments are made to Bitcoin "addresses": human-readable strings of numbers and letters around 33 characters in length, always beginning with the digit 1 or 3, as in the example of ''31uEbMgunupShBVTewXjtqbBv5MndwfXhb''.

Users obtain new Bitcoin addresses from their Bitcoin software. Creating a new address can be a completely offline process and require no communication with the Bitcoin network.

===Transaction fees===
:Main article: [[Transaction fees]]
Transaction fees may be included with any transfer of Bitcoins. {{As of|2012}} many transactions are processed in a way which makes no charge for the transaction. For transactions which consume or produce many coins (and therefore have a large data size), a small transaction fee is usually expected.

===Confirmations===
:Main article: [[Confirmation]]

The network's software confirms a transaction when it records it in a block. Further blocks of transactions confirm it even further. After six confirmations/blocks, a transaction is confirmed beyond reasonable doubt.

The network must store the whole transaction history inside the blockchain, which grows constantly as new records are added and never removed. Nakamoto conceived that as the database became larger, users would desire applications for Bitcoin that didn't store the entire database on their computer. To enable this, the blockchain uses a [[merkle tree]] to organize the transaction records in such a way that client software can locally delete portions of its own database it knows it will never need, such as earlier transaction records of Bitcoins that have changed ownership multiple times.

==Economics==

===Initial distribution===

Bitcoin has no centralized issuing authority.<ref name="ars-06-08-11">
{{Cite news
|first= Thomas
|last= Lowenthal
|title= Bitcoin: inside the encrypted, peer-to-peer digital currency
|newspaper= Ars Technica
|date= 8 June 2011
|url= http://arstechnica.com/tech-policy/news/2011/06/bitcoin-inside-the-encrypted-peer-to-peer-currency.ars
}}</ref><ref>{{cite news
|author= Sponsored by
|url= http://www.economist.com/blogs/babbage/2011/06/virtual-currency
|title= Virtual currency: Bits and bob
|publisher= The Economist
|date=
|accessdate = 2011-06-22
}}</ref><ref>{{cite web
|last= Geere
|first= Duncan
|url= http://www.wired.co.uk/news/archive/2011-05/16/bitcoin-p2p-currency
|title= Peer-to-peer currency Bitcoin sidesteps financial institutions (Wired UK)
|publisher= Wired.co.uk
|date=
|accessdate = 2011-06-22
}}</ref> The network is programmed to increase the money supply as a geometric series until the total number of Bitcoins reaches 21 million BTC.<ref name="Quantitative Analysis of the Full Bitcoin Transaction Graph"/> {{As of|2012|10}} slightly over 10 million of the total 21 million BTC had been created; the current total number created is available online.<ref>{{cite web
|title= Total Number of Bitcoins in Existence
|url= http://blockexplorer.com/q/totalbc
|work= Bitcoin Block Explorer
|accessdate = 2012-10-03
}}</ref> By 2013 half of the total supply will have been generated, and by 2017, three-quarters will have been generated. To ensure sufficient granularity of the [[money supply]], clients can divide each BTC unit down to eight decimal places (a total of 2.1 × 10<sup>15</sup> or 2.1 quadrillion units).<ref name="lwn">{{Cite news
|author= Nathan Willis
|date= 2010-11-10
|title= Bitcoin: Virtual money created by CPU cycles
|publisher= LWN.net
|url= http://lwn.net/Articles/414452/
}}</ref>

The network {{As of|2012|lc=on}} required over one million times more work for confirming a block and receiving an award (25 BTC {{As of|2012|2|lc=on}}) than when the first blocks were confirmed.
The difficulty is automatically adjusted every 2016 blocks based on the time taken to find the previous 2016 blocks such that one block is created roughly every 10 minutes.

Those who chose to put computational and electrical resources toward mining early on had a greater chance at receiving awards for block generations. This served to make available enough processing power to process blocks. Indeed, without miners there are no transactions and the Bitcoin economy comes to a halt.

===Exchange rate===
Prices fluctuate relative to goods and services more than more widely accepted currencies;
the price of a Bitcoin is not static.

In August 2012, 1 BTC traded at around $10.00 USD. Taking into account the total number of Bitcoins mined, the monetary base of the Bitcoin network stands at over 110 million USD.<ref>[http://www.bitcoinwatch.com/ http://www.bitcoinwatch.com/] Bitcoin statistics</ref>

== Security ==
:Main article: [[Weaknesses]]

In the history of bitcoin, there have been a few [[incidents]], caused by problematic as well as malicious transactions. In the worst such incident, and the only one of its type, a person was able to pretend that he had a practically infinite supply of bitcoins, for almost 9 hours.

Bitcoin relies, among other things, on [http://en.wikipedia.org/wiki/Public-key_cryptography public key cryptography] and thus may be vulnerable to [http://en.wikipedia.org/wiki/Elliptic_curve_cryptography#Quantum_computing_attacks quantum computing attacks] if and when practical quantum computers can be constructed.

If multiple different software packages, whose usage becomes widespread on the Bitcoin network, disagree on the protocol and the rules for transactions, this could potentially cause a fork in the block chain, with each faction of users being able to accept only their own version of the history of transactions. This could influence the price of bitcoins.

A global, organized campaign against the currency or the software could also influence the demand for bitcoins, and thus the exchange price.

==Bitcoin mining==
:Main article: [[Mining]]

Bitcoin mining nodes are responsible for managing the Bitcoin network.

Bitcoins are awarded to Bitcoin nodes known as "miners" for the solution to a difficult [[proof-of-work]] problem which confirms transactions and prevents double-spending. This incentive, as the Nakamoto white paper describes it, encourages "nodes to support the network, and provides a way to initially distribute coins into circulation, since no central authority issues them."<ref name="whitepaper" />

Nakamoto compared the generation of new coins by expending CPU time and electricity to gold miners expending resources to add gold to circulation.<ref name="whitepaper"/>

===Node operation===

The node software for the Bitcoin network is based on peer-to-peer networking, digital signatures and cryptographic proof to make and verify transactions. Nodes broadcast transactions to the network, which records them in a public record of all transactions, called the ''blockchain'', after validating them with a [[proof-of-work|proof-of-work system]].

Satoshi Nakamoto designed the first Bitcoin node and mining software<ref name="processors">{{Cite news
|last= Davis
|first= Joshua
|title= The Crypto-Currency
|url= http://www.wired.com/magazine/2011/11/mf_bitcoin/all
|accessdate = 11 November 2011
|newspaper= Wired Magazine
|date= 10 November 2011
}}</ref> and developed the majority of the first implementation, Bitcoind, from 2007 to mid-2010.<ref name="code_start">{{cite web
|url= https://bitcointalk.org/index.php?topic=13.msg46#msg46
|title= Questions about Bitcoin
|publisher= Bitcoin forum
|date= 2009-12-10
}}</ref>

Node implementations include core software such as Bitcoind/Bitcoin-Qt, [[libbitcoin]], [[cbitcoin]]<ref>{{Cite web|title=cbitcoin|url=https://github.com/MatthewLM/cbitcoin|accessdate=3 October 2012}}</ref> and [[BitCoinJ|bitcoinj]].<ref>{{cite web
|url= http://news.slashdot.org/story/11/03/23/0210207/Google-Engineer-Releases-Open-Source-Bitcoin-Client
|title= Google Engineer Releases Open Source Bitcoin Client
|author= angry tapir, timothy
|date= 23 March 2011
|publisher= Slashdot
|accessdate = 2011-05-18
}}</ref><ref>{{cite web
|url= http://www.javaworld.com/javaworld/jw-01-2012/120110-bitcoin-for-beginners-3.html?page=1
|title= Bitcoin for beginners: The BitcoinJ API
|author= Dirk Merkel
|date= 10 January 2012
|publisher= JavaWorld
|accessdate = 2012-08-03
}}</ref>

Every node in the Bitcoin network collects all the unacknowledged transactions it knows of in a file called a ''block'', which also contains a reference to the previous valid block known to that node. It then appends a [[nonce]] value to this previous block and computes the SHA-256 cryptographic hash of the block and the appended nonce value. The node repeats this process until it adds a nonce that allows for the generation of a hash with a value lower than a specified ''target''. Because computers cannot practically reverse the hash function, finding such a nonce is hard and requires on average a predictable amount of repetitious trial and error. This is where the ''[[proof-of-work]]'' concept comes in to play. When a node finds such a solution, it announces it to the rest of the network. Peers receiving the new solved block validate it by computing the hash and checking that it really starts with the given number of zero bits (i.e., that the hash is within the target). Then they accept it and add it to the chain.

===Mining rewards===
In addition to receiving the pending transactions confirmed in the block, a generating node adds a ''generate'' transaction, which awards new Bitcoins to the operator of the node that generated the block. The system sets the payout of this generated transaction according to its defined inflation schedule. The miner that generates a block also receives the fees that users have paid as an incentive to give particular transactions priority for faster confirmation.

The network never creates more than a 50 BTC reward per block and this amount will decrease over time towards zero, such that no more than 21 million BTC will ever exist.<ref name="lwn" /> As this payout decreases, the incentive for users to run block-generating nodes is intended to change to earning [[#Transaction fees|transaction fees]].

===Mining pools===
:Main article: [[Pooled mining]]

Bitcoin users often pool computational effort to increase the stability of the collected fees and subsidy they receive.<ref name="We Use Coins Mining">{{cite web|title=About Bitcoin Mining|url=http://www.weusecoins.com/mining-guide.php|publisher=We Use Coins|accessdate=18 October 2012}}</ref>

===Mining difficulty===
:Main article: [[Difficulty]]

In order to throttle the creation of blocks, the difficulty of generating new blocks is adjusted over time. If mining output increases or decreases, the difficulty increases or decreases accordingly.

The adjustment is done by changing the threshold that a hash is required to be less than. A lower threshold means fewer possible hashes can be accepted, and thus a higher degree of difficulty. The target rate of block generation is one block every 10 minutes, or 2016 blocks every two weeks. Bitcoin changes the difficulty of finding a valid block every 2016 blocks, using the difficulty that would have been most likely to cause the prior 2016 blocks to have taken two weeks to generate, according to the timestamps on the blocks. Technically, this is done by modeling the generation of Bitcoins as Poisson process. All nodes perform and enforce the same difficulty calculation.

Difficulty is intended as an automatic stabilizer allowing mining for Bitcoins to remain profitable in the long run for the most efficient miners, independently of the fluctuations in demand of Bitcoin in relation to other currencies.

===Mining hardware===
:Main article: [[Mining Hardware Comparison]]

Bitcoins used to be mined through Intel/AMD CPUs. {{As of | 2012}}, mining has gradually moved to [[GPU]] and [[FPGA]] hardware.<ref name="bitcoinmag-butterfly" /> [[Application-specific integrated circuit|ASIC]]-based hardware for Bitcoin mining has been announced by several manufacturers who intend to ship products from late 2012 to early 2013.<ref name="bitcoinmag-butterfly">{{Cite web|title=Bitpay Breaks Daily Volume Record with Butterfly ASIC mining release|url=http://bitcoinmagazine.net/bitpay-breaks-daily-volume-record-with-butterfly-asic-mining-release/|publisher=Bitcoin Magazine}}</ref>

==Concerns==

===As an investment===
Bitcoin describes itself as an experimental digital currency. Reuben Grinberg has noted that Bitcoin's supporters have argued that Bitcoin is neither a security or an investment because it fails to meet the criteria for either category.<ref name="grinberg">{{cite web | url=http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1817857 | title=Bitcoin: An Innovative Alternative Digital Currency | publisher=SSRN | date=9 December 2011 | accessdate=4 December 2012 | author=Grinberg, Reuben}}</ref> Although it is a virtual currency, some people see it as an investment<ref name="cnbc">{{cite web | url=http://www.cnbc.com/id/45030812/The_Pros_And_Cons_Of_Biting_on_Bitcoins | title=The Pros And Cons Of Biting on Bitcoins | publisher=CNBC | date=23 November 2011 | accessdate=4 December 2012 | author=Gustke, Constance}}</ref> or accuse it of being a form of investment fraud known as a Ponzi scheme.<ref>{{cite web |url=http://www.theregister.co.uk/2011/06/08/bitcoin_under_attack/ |title=US senators draw a bead on Bitcoin |last1=Chirgwin |first1=Richard |date=8 June 2011 |publisher=The Register |accessdate=14 November 2012}}</ref><ref>{{cite web |url=http://uk.reuters.com/article/2012/04/01/uk-traders-bitcoin-idUKBRE8300JL20120401 |title=Bitcoin, the City traders' anarchic new toy |last1=O'Leary |first1=Naomi |date=2 April 2012 |publisher=Reuters |accessdate=14 November 2012}}</ref> A report by the European Central Bank, using the U.S. Securities and Exchange Commission's definition of a Ponzi scheme, found that the use of bitcoins shares some characteristics with Ponzi schemes, but also has characteristics of its own which contradict several common aspects of Ponzi schemes.<ref name="ecbreport">{{cite web | url=http://www.ecb.europa.eu/pub/pdf/other/virtualcurrencyschemes201210en.pdf | title=Virtual Currency Schemes | publisher=European Central Bank | date=October 2012 | accessdate=4 December 2012}}</ref>

===Privacy===
Because transactions are broadcast to the entire network, they are inherently public. Unlike regular banking,<ref>{{cite web
|url= http://spectrum.ieee.org/computing/software/bitcoin-the-cryptoanarchists-answer-to-cash/0
|title= Bitcoin: The Cryptoanarchists' Answer to Cash
|publisher= IEEE.org
|date= June 2012
|accessdate = 2012-06-05
}}</ref> which preserves customer privacy by keeping transaction records private, loose transactional privacy is accomplished in Bitcoin by using many unique addresses for every wallet, while at the same time publishing all transactions. As an example, if Alice sends 123.45 BTC to Bob, the network creates a public record that allows anyone to see that 123.45 has been sent from one address to another. However, unless Alice or Bob make their ownership of these addresses known, it is difficult for anyone else to connect the transaction with them. However, if someone connects an address to a user at any point they could follow back a series of transactions as each participant likely knows who paid them and may disclose that information on request or under duress.

It can be difficult to associate Bitcoin identities with real-life identities.<ref name="An Analysis of Anonymity in the Bitcoin System">Fergal Reid and Martin Harrigan (24 July 2011). [http://anonymity-in-bitcoin.blogspot.com/2011/07/bitcoin-is-not-anonymous.html An Analysis of Anonymity in the Bitcoin System]. An Analysis of Anonymity in the Bitcoin System.</ref> This property makes Bitcoin transactions attractive to sellers of illegal products.<ref name="Forbes">Andy Greenberg (20 April 2011). [http://www.forbes.com/forbes/2011/0509/technology-psilocybin-bitcoins-gavin-andresen-crypto-currency.html Crypto Currency]. Forbes Magazine.</ref><ref>{{cite web
|last= Madrigal
|first= Alexis
|title= Libertarian Dream? A Site Where You Buy Drugs With Digital Dollars
|publisher= The Atlantic Monthly
|date= 2011-06-01
|url= http://www.theatlantic.com/technology/archive/2011/06/libertarian-dream-a-site-where-you-buy-drugs-with-digital-dollars/239776/
|accessdate = 2011-06-05
}}</ref>

===Illicit use===

====Cracking====
The cracking organization "LulzSec" accepted donations in Bitcoin, having said that the group "needs Bitcoin donations to continue their hacking efforts".<ref name="CNET">{{cite web
|last= Reisinger
|first= Don
|url= http://news.cnet.com/8301-13506_3-20070268-17/senators-target-bitcoin-currency-citing-drug-sales/
|title= Senators target Bitcoin currency, citing drug sales | The Digital Home – CNET News
|publisher= News.cnet.com
|date= 2011-06-09
|accessdate = 2011-06-22
}}</ref><ref>{{cite news
|last= Olson
|first= Parmy
|url= http://blogs.forbes.com/parmyolson/2011/06/06/lulzsec-hackers-posts-sony-dev-source-code-get-7k-donation/
|title= LulzSec Hackers Post Sony Dev. Source Code, Get $7K Donation – Parmy Olson – Disruptors – Forbes
|publisher= Blogs.forbes.com
|date= 6 June 2011
|accessdate = 2011-06-22
}}</ref>

====Silk Road====
[[Silk Road]] is an anonymous black market that uses only the Bitcoin.<ref name="npr-06-12-11">
{{Cite news
|url= http://www.npr.org/2011/06/12/137138008/silk-road-not-your-fathers-amazon-com
|date= 12 June 2011
|newspaper= NPR
|title= Silk Road: Not Your Father's Amazon.com
|author= Staff
}}</ref>

In a 2011 letter to Attorney General Eric Holder and the Drug Enforcement Administration, senators Charles Schumer of New York and Joe Manchin of West Virginia called for an investigation into Silk Road and the Bitcoin.<ref name="npr-06-12-11"/>
Schumer described the use of Bitcoins at Silk Road as a form of money laundering.<ref name="ars-06-08-11"/>

====Botnet mining====
In June 2011, Symantec warned about the possibility of botnets engaging in covert "mining" of Bitcoins,<ref>{{Cite web|author=Updated: 17 June 2011 | Translations available: 日本語 |url=http://www.symantec.com/connect/blogs/bitcoin-botnet-mining |title=Bitcoin Botnet Mining | Symantec Connect Community |publisher=Symantec.com |date=2011-06-17 |accessdate = 2012-01-24}}</ref><ref>{{Cite web|url=http://www.zdnet.com/blog/security/researchers-find-malware-rigged-with-bitcoin-miner/8934 |title=Researchers find malware rigged with Bitcoin miner |publisher=ZDNet |date=2011-06-29 |accessdate = 2012-01-24}}</ref> consuming computing cycles, using extra electricity and possibly increasing the temperature of the computer. Later that month, the Australian Broadcasting Corporation caught an employee using the company's servers to generate Bitcoins without permission.<ref>{{Cite web|url=http://thenextweb.com/au/2011/06/23/abc-employee-caught-mining-for-bitcoins-on-company-servers/ |title=ABC employee caught mining for Bitcoins on company servers |publisher=The Next Web |date=2011-06-23 |accessdate = 2012-01-24}}</ref> Some malware also uses the parallel processing capabilities of the GPUs built into many modern-day video cards.<ref>{{Cite news |url=http://www.theregister.co.uk/2011/08/16/gpu_bitcoin_brute_forcing/ |title=Malware mints virtual currency using victim's GPU |date=16 August 2011|first=Dan |last=Goodin }}</ref> In mid August 2011, Bitcoin miner botnets were found;<ref>{{Cite web|url=http://www.infosecurity-magazine.com/view/20211/researcher-discovers-distributed-bitcoin-cracking-trojan-malware/ |title=Infosecurity – Researcher discovers distributed bitcoin cracking trojan malware |publisher=Infosecurity-magazine.com |date=2011-08-19 |accessdate = 2012-01-24}}</ref> trojans infecting Mac OS X have also been uncovered.<ref>{{Cite web|url=http://www.techworld.com.au/article/405849/mac_os_x_trojan_steals_processing_power_produce_bitcoins |title=Mac OS X Trojan steals processing power to produce Bitcoins – sophos, security, malware, Intego – Vulnerabilities – Security |publisher=Techworld |date=2011-11-01 |accessdate = 2012-01-24}}</ref>

===Theft and fraud===
On 19 June 2011, a security breach of the Mt.Gox (an acronym for ''M''agic: ''T''he ''G''athering ''O''nline E''x''change, its original purpose) Bitcoin Exchange caused the price of a Bitcoin to briefly drop to US$0.01 on the Mt.Gox exchange (though it remained unaffected on other exchanges) after a hacker allegedly used credentials from a Mt.Gox auditor's compromised computer to illegally transfer a large number of Bitcoins to him- or herself and sell them all, creating a massive "ask" order at any price. Within minutes the price rebounded to over $15 before Mt.Gox shut down their exchange and canceled all trades that happened during the hacking period.<ref>[https://mtgox.com/press_release_20110630.html Clarification of Mt Gox Compromised Accounts and Major Bitcoin Sell-Off]</ref><ref>[http://www.youtube.com/watch?v=T1X6qQt9ONg YouTube. Bitcoin Report]</ref> The exchange rate of Bitcoins quickly returned to near pre-crash values.<ref name="mick">Jason Mick, 19 June 2011, [http://www.dailytech.com/Inside+the+MegaHack+of+Bitcoin+the+Full+Story/article21942.htm Inside the Mega-Hack of Bitcoin: the Full Story], DailyTech</ref><ref>Timothy B. Lee, 19 June 2011, [http://arstechnica.com/tech-policy/news/2011/06/bitcoin-price-plummets-on-compromised-exchange.ars Bitcoin prices plummet on hacked exchange], Ars Technica</ref><ref>Mark Karpeles, 20 June 2011, [https://support.mtgox.com/entries/20208066-huge-bitcoin-sell-off-due-to-a-compromised-account-rollback Huge Bitcoin sell off due to a compromised account – rollback], Mt.Gox Support</ref><ref name="register1">{{Cite news
|title= Bitcoin collapses on malicious trade – Mt Gox scrambling to raise the Titanic
|url= http://www.theregister.co.uk/2011/06/19/bitcoin_values_collapse_again/
|date= 2011-06-19
|author= Chirgwin, Richard
|publisher= The Register
}}</ref> Accounts with the equivalent of more than USD 8,750,000 were affected.<ref name="mick" />

In July 2011, The operator of Bitomat, the third largest Bitcoin exchange, announced that he lost access to his wallet.dat file with about 17,000 BitCoins (roughly equivalent to 220,000 USD at that time). He announced that he would sell the service for the missing amount, aiming to use funds from the sale to refund his customers.<ref>[http://siliconangle.com/blog/2011/08/01/third-largest-bitcoin-exchange-bitomat-lost-their-wallet-over-17000-bitcoins-missing/ Third Largest Bitcoin Exchange Bitomat Lost Their Wallet, Over 17,000 Bitcoins Missing]. SiliconAngle</ref>

In August 2011, MyBitcoin, one of popular Bitcoin transaction processors, declared that it was hacked, which resulted in it being shut down, with paying 49% on customer deposits, leaving more than 78,000 BitCoins (roughly equivalent to 800,000 USD at that time) unaccounted for.<ref>[http://betabeat.com/2011/08/mybitcoin-spokesman-finally-comes-forward-what-did-you-think-we-did-after-the-hack-we-got-shitfaced/ MyBitcoin Spokesman Finally Comes Forward: “What Did You Think We Did After the Hack? We Got Shitfaced”]. BetaBeat</ref><ref>[http://betabeat.com/2011/08/search-for-owners-of-mybitcoin-loses-steam/ Search for Owners of MyBitcoin Loses Steam]. BetaBeat</ref>

In early August 2012, a lawsuit was filed in San Francisco court against Bitcoinica, claiming about 460,000 USD from the company. Bitcoinica was hacked twice in 2012, which led to allegations of neglecting the safety of customers' money and cheating them out of withdrawal requests.<ref>[http://arstechnica.com/tech-policy/2012/08/bitcoinica-users-sue-for-460k-in-lost-bitcoins/ Bitcoinica users sue for $460k in lost Bitcoins]. Arstechnica</ref><ref>[http://spectrum.ieee.org/tech-talk/computing/networks/first-bitcoin-lawsuit-filed-in-san-francisco First Bitcoin Lawsuit Filed In San Francisco]. IEEE Spectrum</ref>

In late August 2012, Bitcoin Savings and Trust was shut down by the owner, allegedly leaving around $5.6 million in debts; this led to allegations of the operation being a Ponzi scheme.<ref>{{Cite web|title=Bitcoin ponzi scheme – investors lose $5 million USD in online hedge fund|url=http://rt.com/usa/news/investors-currency-digital-fund-868/|publisher=RT}}</ref><ref>{{Cite web|last=Jeffries|first=Adrianne|title=Suspected multi-million dollar Bitcoin pyramid scheme shuts down, investors revolt|url=http://www.theverge.com/2012/8/27/3271637/bitcoin-savings-trust-pyramid-scheme-shuts-down|publisher=The Verge}}</ref><ref>{{Cite web|last=Mick|first=Jason|title="Pirateat40" Makes Off $5.6M USD in BitCoins From Pyramid Scheme|url=http://www.dailytech.com/Pirateat40+Makes+Off+56M+USD+in+BitCoins+From+Pyramid+Scheme/article25538.htm|publisher=DailyTech}}</ref><ref>[http://pandodaily.com/2012/08/31/bitcoin-how-a-virtual-currency-became-real-with-a-5-6m-fraud/ Bitcoin: How a Virtual Currency Became Real with a $5.6M Fraud]. PandoDaily</ref> In September 2012, it was reported that U.S. Securities and Exchange Commission has started an investigation on the case.<ref>[http://blogs.telegraph.co.uk/technology/willardfoxton2/100007836/bitcoin-pirate-scandal-sec-steps-in-amid-allegations-that-the-whole-thing-was-a-ponzi-scheme/ Bitcoin 'Pirate' scandal: SEC steps in amid allegations that the whole thing was a Ponzi scheme ]. The Telegraph</ref>

In September 2012, Bitfloor Bitcoin exchange also reported being hacked, with 24,000 BitCoins (roughly equivalent to 250,000 USD) stolen. As a result, Bitfloor suspended operations.<ref>[http://www.bbc.co.uk/news/technology-19486695 Bitcoin theft causes Bitfloor exchange to go offline]. BBC</ref><ref>[http://www.theverge.com/2012/9/5/3293375/bitfloor-bitcoin-exchange-suspended-theft Bitcoin exchange BitFloor suspends operations after $250,000 theft Bitcoin exchange BitFloor suspends operations after $250,000 theft]. The Verge</ref> The same month, Bitfloor resumed operations, with its founder saying that he reported the theft to FBI, and that he is planning to repay the victims, though the time frame for such repayment is unclear.<ref>[http://www.pcworld.com/article/2010586/bitcoin-exchange-back-online-after-hack.html?tk=rel_news Bitcoin exchange back online after hack]. PCWorld</ref>

===Taxation===
In September 2012, the Intra-European Organization of Tax Administrations (IOTA), in Tbilisi, Georgia, held a workshop titled "Auditing Individuals and Legal Entities in the Use of e-Money." The workshop was attended by representatives from 23 countries.<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Jerry Taylor, IOTA's technical taxation expert, said, "There's an awful lot happening on the Internet environment which is fascinating at the moment and introducing new challenges for auditors when it comes to virtual currency."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Bitcoin was mentioned during the workshop.<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref>

Matthew Elias, founder of the [[Cryptocurrency Legal Advocacy Group]] (CLAG) published "Staying Between the Lines: A Survey of U.S. Income Taxation and its Ramifications on Cryptocurrencies", which discusses "the taxability of cryptocurrencies such as bitcoin."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> CLAG "stressed the importance for taxpayers to determine on their own whether taxes are due on a bitcoin-related transaction based on whether one has "experienced a realization event."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Such examples are "when a taxpayer has provided a service in exchange for bitcoins, a realization event has probably occurred, and any gain or loss would likely be calculated using fair market values for the service provided."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref>

[[Peter Vessenes]], [[Bitcoin Foundation|Bitcoin Foundation's]] executive director, said, since the foundation is trying to pay for everything in bitcoin, including salaries, "How do we W-2 someone for their bitcoins? Do we mark-to-market every time a transfer happens? Payroll companies cringe."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> The Bitcoin Foundation hopes "to push for solid guidance about its legal and tax treatment." [[Patrick Murck]], legal counsel for the Bitcoin Foundation, said he would like "to help regulators understand the technology better so they can make better decisions."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Murck said, "Bitcoin has the potential to become much more than a niche currency, but it needs the guidance and understanding of regulators." and "The full potential of bitcoin could be realized through clearer guidelines and a better understanding by financial and tax regulators." and "Part of making that happen is to talk to regulators, the IRS, and tax professionals and helping them understand that bitcoin is not this nefarious thing, it's just software, it's a community, and there's nothing inherently nefarious about either of those things."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref>

==See Also==
* [[Introduction]]
* [[Getting started]]
* [[Using_Bitcoin|Detailed tutorial]]
* [[FAQ]]

==References==
<references />

[[Category:Digital currencies]]

Scalability

2013-03-31T12:14:55Z

Goonie:

The core Bitcoin network can scale to much higher transaction rates than are seen today, assuming that nodes in the network are primarily running on high end servers rather than desktops. Bitcoin was designed to support lightweight clients that only process small parts of the block chain (see ''simplified payment verification'' below for more details on this). A configuration in which the vast majority of users sync lightweight clients to more powerful backbone nodes is capable of scaling to millions of users and tens of thousands of transactions per second.

==Scalability targets==

VISA handles on average around 2,000 transactions per second (tps), so call it a daily peak rate of 4,000 tps. They have burst capacity for over 10,000 tps which they need to handle the busiest points of the holiday period (~8,500 tps). [http://investor.visa.com/phoenix.zhtml?c=215693&p=irol-newsArticle_print&ID=1355716]

PayPal, in contrast, handles around 4 million transactions per day for an average of 46 tps or a probably peak rate of 100 tps.

Let's take 4,000 tps as starting goal. Obviously if we want Bitcoin to scale to all economic transactions worldwide, including cash, it'd be a lot higher than that, perhaps more in the region of a few hundred thousand tps. And the need to be able to withstand DoS attacks (which VISA does not have to deal with) implies we would want to scale far beyond the standard peak rates. Still, picking a target let us do some basic calculations even if it's a little arbitrary.

==Current bottlenecks==

Today the Bitcoin network is restricted to a sustained rate of 7 tps by some artificial limits. These were put in place to stop people from ballooning the size of the block chain before the network and community was ready for it. Once those limits are lifted, the maximum transaction rate will go up significantly.

==CPU==

The protocol has two parts. Nodes send "inv" messages to other nodes telling them they have a new transaction. If the receiving node doesn't have that transaction it requests it with a getdata.

The big cost is the crypto and block chain lookups involved with verifying the transaction. Verifying a transaction means some hashing and some ECDSA signature verifications. RIPEMD-160 runs at 106 megabytes/sec (call it 100 for simplicity) and SHA256 is about the same. So hashing 1 megabyte should take around 10 milliseconds and hashing 1 kilobyte would take 0.01 milliseconds - fast enough that we can ignore it.

Bitcoin is currently able (with a couple of simple optimizations that are prototyped but not merged yet) to perform around 8000 signature verifications per second on an quad core [http://ark.intel.com/products/53469 Intel Core i7-2670QM 2.2Ghz processor]. The average number of inputs per transaction is around 2, so we must halve the rate. This means 4000 tps is easily achievable CPU-wise with a single fairly mainstream CPU.

As we can see, this means as long as Bitcoin nodes are allowed to max out at least 4 cores of the machines they run on, we will not run out of CPU capacity unless Bitcoin is handling 100 times as much traffic as PayPal. As of late 2012 the network is handling 0.5 transactions/second, so even assuming enormous growth in popularity we will not reach this level for a long time.

==Network==

Let's assume an average rate of 2000tps, so just VISA. Transactions vary in size from about 0.2 kilobytes to over 1 kilobyte, but it's averaging half a kilobyte today.

That means that you need to keep up with around 8 megabits/second of transaction data (2000tps * 512 bytes) / 1024 bytes in a kilobyte / 1024 kilobytes in a megabyte = 0.97 megabytes per second * 8 = 7.8 megabits/second.

This sort of bandwidth is already common for even residential connections today, and is certainly at the low end of what colocation providers would expect to provide you with.

When blocks are solved, the current protocol will send the transactions again, even if a peer has already seen it at broadcast time. Fixing this to make blocks just list of hashes would resolve the issue and make the bandwidth needed for block broadcast negligable. So whilst this optimization isn't fully implemented today, we do not consider block transmission bandwidth here.

==Storage==

At very high transaction rates each block can be over half a gigabyte in size.

It is not required for most fully validating nodes to store the entire chain. In Satoshi's paper he describes "pruning", a way to delete unnecessary data about transactions that are fully spent. This reduces the amount of data that is needed for a fully validating node to be only the size of the current unspent output size, plus some additional data that is needed to handle re-orgs. As of October 2012 (block 203258) there have been 7,979,231 transactions, however the size of the unspent output set is less than 100MiB, which is small enough to easily fit in RAM for even quite old computers.

Only a small number of archival nodes need to store the full chain going back to the genesis block. These nodes can be used to bootstrap new fully validating nodes from scratch but are otherwise unnecessary.

The primary limiting factor in Bitcoin's performance is disk seeks once the unspent transaction output set stops fitting in memory. It is quite possible that the set will always fit in memory on dedicated server class machines, if hardware advances faster than Bitcoin usage does.

==Optimizations==

The description above applies to the current software with only minor optimizations assumed (the type that can and have been done by one man in a few weeks).

However there is potential for even greater optimizations to be made in future, at the cost of some additional complexity.

===CPU===

Pieter Wuille has implemented a custom verifier tuned for secp256k1 that can go beyond 20,000 signature verifications per second. It would require careful review by professional cryptographers to gain as much confidence as OpenSSL, but this can easily halve CPU load.

Newly developed digital signature algorithms, like [http://ed25519.cr.yp.to/ed25519-20110705.pdf ed25519] have extremely efficient software implementations that can reach speeds of nearly 80,000 verifications per second, even on an old Westmere CPU. That is a 10x improvement over secp256k1, and most likely is even higher on more modern CPUs. Supporting this in Bitcoin would mean a "soft fork" like the one done recently for pay-to-script-hash support.

Algorithms exist to accelerate batch verification over elliptic curve signatures. This means if there are several inputs that are signing with the same key, it's possible to check their signatures simultaneously for another 9x speedup. This is a somewhat more complex implementation, however, it can work with existing signatures (clients don't need upgrading).

Assuming no upgrades to lightweight/SPV clients, so just batch verification, we can reach 40,000 transactions per second which is far beyond the traffic levels of the entire credit card system. And with ed25519 we could go up to nearly half a million transactions per second - with todays hardware! At these speeds it is likely that bandwidth to disk would become the primary limiting factor.

===Simplified payment verification===

It's possible to build a Bitcoin implementation that does not verify everything, but instead relies on either connecting to a trusted node, or puts its faith in high difficulty as a proxy for proof of validity. [[BitCoinJ|Bitcoinj]] is an implementation of this mode.

In Simplified Payment Verification (SPV) mode, named after the section of Satoshi's paper that describes it, clients connect to an arbitrary full node and download only the block headers. They verify the chain headers connect together correctly and that the difficulty is high enough. They then request transactions matching particular patterns from the remote node (ie, payments to your addresses), which provides copies of those transactions along with a Merkle branch linking them to the block in which they appeared. This exploits the Merkle tree structure to allow proof of inclusion without needing the full contents of the block.

As a further optimization, block headers that are buried sufficiently deep can be thrown away after some time (eg, you only really need to store say 5000 blocks).

The level of difficulty required to obtain confidence the remote node is not feeding you fictional transactions depends on your threat model. If you are connecting to a node that is known to be reliable, the difficulty doesn't matter. If you want to pick a random node, the cost for an attacker to mine a block sequence containing a bogus transaction should be higher than the value to be obtained by defrauding you. By changing how deeply buried the block must be, you can trade off confirmation time vs cost of an attack.

Programs implementing this approach can have fixed storage/network overhead in the null case of no usage, and resource usage proportional to received/sent transactions.

See also: [[Thin Client Security]].

[[Category:Technical]]

Clients

2013-03-21T08:01:07Z

Goonie: /* Table */

==Overview==

This table compares the features of the different clients. All of the listed clients are open-source.

===Feature key===

; Wallet Security : How well the client protects your [[private key]]s from people with access to the machine the wallet is stored on. The private keys can be encrypted, for example. The private keys can also be either stored on your device or on a remote server.
; Network Security : Clients which more fully implement the Bitcoin network protocol are safer -- they can't be as easily tricked by powerful attackers. A client which ''fully'' implements the protocol will always use the correct [[block chain]] and will never allow [[double-spending|double-spends]] or invalid transactions to exist in the block chain under any circumstances. Clients which only ''partially'' implement the protocol typically trust that 50% or more of the network's mining power is honest. Some clients trust one or more ''remote servers'' to protect them from double-spends and other network attacks.
; Setup Time : Some clients require that you download and verify a large amount of data before you can send or receive BTC.
; Maturity : When the project was started.

===Table===


{| class='wikitable' style='text-align: center'
! Client !! Get Started !! Audience !! Wallet Security !! Network Security !! Backups !! Setup Time !! Disk Space !! Maturity !! Multi-user !! Available for
|-
! Armory
|| [http://bitcoinarmory.com/index.php/get-armory Download] || Power users || {{CLGood|Encrypted, on-device}} || Addon || {{CLBest|One-time}} || Varies || {{CLBad|2+ GB}} || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLWin}}
|-
! Bitcoin Wallet
|| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Google Play] [https://appworld.blackberry.com/webstore/content/23952882/ BlackBerry World] || {{CLBest|Everyone}} || {{CLGood|Isolated, on-device}} || Partial || Manual || 1 hour || 30 MB || {{CLGood|Mar 2011}} || on JB tablets || {{CLAndroid}} [[file:ico-blackberry.png]]
|-
! {{CLGood|Bitcoin-Qt}}
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|2+ GB}} || {{CLGood|May 2011}} || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! bitcoind
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || Programmers || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|2+ GB}} || {{CLBest|Aug 2009}} || {{CLGood|Virtual accounts}} || {{CLLinux}}{{CLWin}}
|-
! Electrum
|| [http://ecdsa.org/electrum/ Download] || Power users || {{CLGood|Encrypted, on-device}} || Minimal || {{CLBest|Memorized}} || {{CLGood|Minutes}} || {{CLGood|5 MB}} || Nov 2011 || No || {{CLLinux}}{{CLWin}}
|-
! MultiBit
|| [http://multibit.org/releases.html Download] || {{CLGood|End-users}} || {{CLBad|None, on-device}} || Partial || {{CLBad|No}} || 1 hour || 50 MB || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! My Wallet
|| [https://blockchain.info/wallet/new Web-based] || {{CLBest|Everyone}} || Encrypted, on a server || {{CLBad|Remote}} || {{CLGood|Automatic}} || {{CLGood|Minutes}} || {{CLBest|None}} || Dec 2011 || {{CLBest|Yes}} || {{CLAndroid}}{{CLiOS}}{{CLLinux}}{{CLMac}}{{CLWin}}
|}



==For developers==

This table shows additional information about various Bitcoin clients that may be relevant to developers.

{| class='wikitable' style='text-align: center'
! Client !! Website !! Source Code !! License !! Discussion !! Architecture
|-
! Armory
|| [http://bitcoinarmory.com/ Link] ||[https://github.com/etotheipi/BitcoinArmory/ Github] || AGPLv3 || [https://bitcointalk.org/index.php?board=97.0 Bitcointalk] || Integrated
|-
! Bitcoin Wallet
|| [https://code.google.com/p/bitcoin-wallet/ Link] || [https://code.google.com/p/bitcoin-wallet/source/checkout Google Code] [https://github.com/schildbach/bitcoin-wallet Github] || GPLv3 || [https://bitcointalk.org/index.php?board=100.0 Bitcointalk] / [https://groups.google.com/forum/?fromgroups#!forum/bitcoinj Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! Bitcoin-Qt / bitcoind
|| [http://bitcoin.org/ Link] || [https://github.com/bitcoin/bitcoin Github] || MIT || [https://lists.sourceforge.net/lists/listinfo/bitcoin-development Sourceforge] || Integrated
|-
! Electrum
|| [http://ecdsa.org/electrum/ Link] || [https://gitorious.org/electrum Gitorious] || GPLv3 || [https://lists.sourceforge.net/lists/listinfo/electrum-discuss Sourceforge] || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! MultiBit
|| [http://multibit.org/ Link] || [https://github.com/jim618/multibit Github] || MIT || [https://groups.google.com/forum/?fromgroups#!forum/bitcoin-multibit Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! My Wallet
|| [https://blockchain.info/wallet/ Link] || [https://github.com/blockchain/My-Wallet/ Github] || BSD* || None || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|}

==See Also==
[[Bitcoin Ladder]]

<references/>

Clients

2013-03-21T07:55:33Z

Goonie: /* Table */

==Overview==

This table compares the features of the different clients. All of the listed clients are open-source.

===Feature key===

; Wallet Security : How well the client protects your [[private key]]s from people with access to the machine the wallet is stored on. The private keys can be encrypted, for example. The private keys can also be either stored on your device or on a remote server.
; Network Security : Clients which more fully implement the Bitcoin network protocol are safer -- they can't be as easily tricked by powerful attackers. A client which ''fully'' implements the protocol will always use the correct [[block chain]] and will never allow [[double-spending|double-spends]] or invalid transactions to exist in the block chain under any circumstances. Clients which only ''partially'' implement the protocol typically trust that 50% or more of the network's mining power is honest. Some clients trust one or more ''remote servers'' to protect them from double-spends and other network attacks.
; Setup Time : Some clients require that you download and verify a large amount of data before you can send or receive BTC.
; Maturity : When the project was started.

===Table===


{| class='wikitable' style='text-align: center'
! Client !! Get Started !! Audience !! Wallet Security !! Network Security !! Backups !! Setup Time !! Disk Space !! Maturity !! Multi-user !! Available for
|-
! Armory
|| [http://bitcoinarmory.com/index.php/get-armory Download] || Power users || {{CLGood|Encrypted, on-device}} || Addon || {{CLBest|One-time}} || Varies || {{CLBad|2+ GB}} || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLWin}}
|-
! Bitcoin Wallet
|| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Download] || {{CLBest|Everyone}} || {{CLGood|Isolated, on-device}} || Partial || Manual || 1 hour || 30 MB || {{CLGood|Mar 2011}} || on JB tablets || {{CLAndroid}} [[file:ico-blackberry.png]]
|-
! {{CLGood|Bitcoin-Qt}}
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|2+ GB}} || {{CLGood|May 2011}} || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! bitcoind
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || Programmers || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|2+ GB}} || {{CLBest|Aug 2009}} || {{CLGood|Virtual accounts}} || {{CLLinux}}{{CLWin}}
|-
! Electrum
|| [http://ecdsa.org/electrum/ Download] || Power users || {{CLGood|Encrypted, on-device}} || Minimal || {{CLBest|Memorized}} || {{CLGood|Minutes}} || {{CLGood|5 MB}} || Nov 2011 || No || {{CLLinux}}{{CLWin}}
|-
! MultiBit
|| [http://multibit.org/releases.html Download] || {{CLGood|End-users}} || {{CLBad|None, on-device}} || Partial || {{CLBad|No}} || 1 hour || 50 MB || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! My Wallet
|| [https://blockchain.info/wallet/new Web-based] || {{CLBest|Everyone}} || Encrypted, on a server || {{CLBad|Remote}} || {{CLGood|Automatic}} || {{CLGood|Minutes}} || {{CLBest|None}} || Dec 2011 || {{CLBest|Yes}} || {{CLAndroid}}{{CLiOS}}{{CLLinux}}{{CLMac}}{{CLWin}}
|}



==For developers==

This table shows additional information about various Bitcoin clients that may be relevant to developers.

{| class='wikitable' style='text-align: center'
! Client !! Website !! Source Code !! License !! Discussion !! Architecture
|-
! Armory
|| [http://bitcoinarmory.com/ Link] ||[https://github.com/etotheipi/BitcoinArmory/ Github] || AGPLv3 || [https://bitcointalk.org/index.php?board=97.0 Bitcointalk] || Integrated
|-
! Bitcoin Wallet
|| [https://code.google.com/p/bitcoin-wallet/ Link] || [https://code.google.com/p/bitcoin-wallet/source/checkout Google Code] [https://github.com/schildbach/bitcoin-wallet Github] || GPLv3 || [https://bitcointalk.org/index.php?board=100.0 Bitcointalk] / [https://groups.google.com/forum/?fromgroups#!forum/bitcoinj Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! Bitcoin-Qt / bitcoind
|| [http://bitcoin.org/ Link] || [https://github.com/bitcoin/bitcoin Github] || MIT || [https://lists.sourceforge.net/lists/listinfo/bitcoin-development Sourceforge] || Integrated
|-
! Electrum
|| [http://ecdsa.org/electrum/ Link] || [https://gitorious.org/electrum Gitorious] || GPLv3 || [https://lists.sourceforge.net/lists/listinfo/electrum-discuss Sourceforge] || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! MultiBit
|| [http://multibit.org/ Link] || [https://github.com/jim618/multibit Github] || MIT || [https://groups.google.com/forum/?fromgroups#!forum/bitcoin-multibit Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! My Wallet
|| [https://blockchain.info/wallet/ Link] || [https://github.com/blockchain/My-Wallet/ Github] || BSD* || None || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|}

==See Also==
[[Bitcoin Ladder]]

<references/>

File:Ico-blackberry.png

2013-03-21T07:49:53Z

Goonie:

Bitcoin Wallet

2013-03-21T07:30:49Z

Goonie:

[[File:bitcoin_wallet.png|192px]]

An open-source and free Android implementation of a Bitcoin Wallet, based on [[BitCoinJ|bitcoinj]]. It was released on March 7, 2011<ref>[http://groups.google.com/d/msg/bitcoinj/fqUw1AKsxWI/pl6rzUSmUH4J Release announcement to the BitCoinJ mailing list]</ref>. A build for BlackBerry OS is available, too.

==External Links==

* [https://play.google.com/store/apps/details?id=de.schildbach.wallet] Bitcoin Wallet on Google Play.
* [https://appworld.blackberry.com/webstore/content/23952882/] Bitcoin Wallet on BlackBerry World.
* [https://code.google.com/p/bitcoin-wallet/downloads/list] direct download of test versions
* [https://code.google.com/p/bitcoin-wallet/] project page on Google Code.
* [https://github.com/schildbach/bitcoin-wallet] project page on Github.
* [https://bitcointalk.org/index.php?board=100.0] discussion forum on Bitcointalk

==References==
<references />

[[Category:Wallets]]
[[Category:Clients]]
[[Category:Free Software]]
[[Category:License/GPLv3]]
[[Category:Open Source]]
[[Category:Mobile]]

[[de:Bitcoin_Wallet]]

Clients

2013-01-29T23:33:38Z

Goonie: /* For developers */

==Overview==

This table compares the features of the different clients. All of the listed clients are open-source.

===Feature key===

; Wallet Security : How well the client protects your [[private key]]s from people with access to the machine the wallet is stored on. The private keys can be encrypted, for example. The private keys can also be either stored on your device or on a remote server.
; Network Security : Clients which more fully implement the Bitcoin network protocol are safer -- they can't be as easily tricked by powerful attackers. A client which ''fully'' implements the protocol will always use the correct [[block chain]] and will never allow [[double-spending|double-spends]] or invalid transactions to exist in the block chain under any circumstances. Clients which only ''partially'' implement the protocol typically trust that 50% or more of the network's mining power is honest. Some clients trust one or more ''remote servers'' to protect them from double-spends and other network attacks.
; Setup Time : Some clients require that you download and verify a large amount of data before you can send or receive BTC.
; Maturity : When the project was started.

===Table===


{| class='wikitable' style='text-align: center'
! Client !! Get Started !! Audience !! Wallet Security !! Network Security !! Backups !! Setup Time !! Disk Space !! Maturity !! Multi-user !! Available for
|-
! Armory
|| [http://bitcoinarmory.com/index.php/get-armory Download] || Power users || {{CLGood|Encrypted, on-device}} || Addon || {{CLBest|One-time}} || Varies || {{CLBad|2+ GB}} || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLWin}}
|-
! Bitcoin Wallet
|| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Download] || {{CLBest|Everyone}} || {{CLGood|Isolated, on-device}} || Partial || Manual || 1 hour || 30 MB || {{CLGood|Mar 2011}} || on JB tablets || {{CLAndroid}} & BB
|-
! {{CLGood|Bitcoin-Qt}}
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || {{CLGood|End-users}} || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|2+ GB}} || {{CLGood|May 2011}} || No || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! bitcoind
|| [http://sourceforge.net/projects/bitcoin/files/Bitcoin/ Download] || Programmers || {{CLGood|Encrypted, on-device}} || {{CLBest|Full}} || Manual || {{CLBad|Hours}} || {{CLBad|2+ GB}} || {{CLBest|Aug 2009}} || {{CLGood|Virtual accounts}} || {{CLLinux}}{{CLWin}}
|-
! Electrum
|| [http://ecdsa.org/electrum/ Download] || Power users || {{CLGood|Encrypted, on-device}} || Minimal || {{CLBest|Memorized}} || {{CLGood|Minutes}} || {{CLGood|5 MB}} || Nov 2011 || No || {{CLLinux}}{{CLWin}}
|-
! MultiBit
|| [http://multibit.org/releases.html Download] || {{CLGood|End-users}} || {{CLBad|None, on-device}} || Partial || {{CLBad|No}} || 1 hour || 50 MB || Jul 2011 || {{CLBest|Multi-wallet}} || {{CLLinux}}{{CLMac}}{{CLWin}}
|-
! My Wallet
|| [https://blockchain.info/wallet/new Web-based] || {{CLBest|Everyone}} || Encrypted, on a server || {{CLBad|Remote}} || {{CLGood|Automatic}} || {{CLGood|Minutes}} || {{CLBest|None}} || Dec 2011 || {{CLBest|Yes}} || {{CLAndroid}}{{CLiOS}}{{CLLinux}}{{CLMac}}{{CLWin}}
|}



==For developers==

This table shows additional information about various Bitcoin clients that may be relevant to developers.

{| class='wikitable' style='text-align: center'
! Client !! Website !! Source Code !! License !! Discussion !! Architecture
|-
! Armory
|| [http://bitcoinarmory.com/ Link] ||[https://github.com/etotheipi/BitcoinArmory/ Github] || AGPLv3 || [https://bitcointalk.org/index.php?board=97.0 Bitcointalk] || Integrated
|-
! Bitcoin Wallet
|| [https://code.google.com/p/bitcoin-wallet/ Link] || [https://code.google.com/p/bitcoin-wallet/source/checkout Google Code] [https://github.com/schildbach/bitcoin-wallet Github] || GPLv3 || [https://bitcointalk.org/index.php?board=100.0 Bitcointalk] / [https://groups.google.com/forum/?fromgroups#!forum/bitcoinj Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! Bitcoin-Qt / bitcoind
|| [http://bitcoin.org/ Link] || [https://github.com/bitcoin/bitcoin Github] || MIT || [https://lists.sourceforge.net/lists/listinfo/bitcoin-development Sourceforge] || Integrated
|-
! Electrum
|| [http://ecdsa.org/electrum/ Link] || [https://gitorious.org/electrum Gitorious] || GPLv3 || [https://lists.sourceforge.net/lists/listinfo/electrum-discuss Sourceforge] || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|-
! MultiBit
|| [http://multibit.org/ Link] || [https://github.com/jim618/multibit Github] || MIT || [https://groups.google.com/forum/?fromgroups#!forum/bitcoin-multibit Google Groups] || [[Thin Client Security#Simplified Payment Verification (SPV)|SPV]]
|-
! My Wallet
|| [https://blockchain.info/wallet/ Link] || [https://github.com/blockchain/My-Wallet/ Github] || BSD* || None || [[Thin Client Security#Server-Trusting Clients|Server-Client]]
|}

==See Also==
[[Bitcoin Ladder]]

<references/>

Mobile Payment Apps

2013-01-29T23:31:12Z

Goonie:

List of Mobile apps used for payments.

{| class = "wikitable"|
|-
| App || Android || iPhone || Nokia || Blackberry || QR-code || NFC || Btc Storage || OpenSource || Last Active || Comments
|-
| [[Bitcoin Wallet for Android]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value Yes}} || {{Table Value Yes}} || On Phone + encrypted backup || [https://github.com/schildbach/bitcoin-wallet Github] [https://code.google.com/p/bitcoin-wallet/ Google] || 2013-Jan-28 || [https://bitcointalk.org/index.php?board=100.0 Forum]
|-
| [[BitcoinApp]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || ? || ? || On Phone || [https://github.com/udibr/bitcoinApp Github] || 2011-May-18
|-
| [[BitPay]] || {{Table Value Yes}} || {{Table Value No}} || ? || ? || {{Table Value Yes}} || {{Table Value No}} || [[Instawallet]] || [https://github.com/warpi/BitPay Github] || 2011-Sep-26
|-
| [[Bitcoin Express]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || ? || ? || ? || [https://github.com/fingster/BTC-Express Github] || 2011-Jul-24 || [http://bitcointalk.org/index.php?topic=31362.0 Forum]
|-
| [[BitcoinSpinner]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, chain on server || [http://code.google.com/p/bitcoinspinner/ Google] || 2011-12-01 || [http://bitcointalk.org/index.php?topic=52674.0 Forum]
|-
| [[BlockChain.info|Blockchain for iPhone]] || {{Table Value No}} || {{Table Value Yes}}<ref>Cydia / Jailbroken only.</ref> || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, encrypted backup on server || [https://github.com/zootreeves/My-Wallet-iPhone GitHub] || 2012-05-12 || [http://bitcointalk.org/index.php?topic=75673.0 Forum]
|-
| [[BlockChain.info|Blockchain for Android]] || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || On Phone, encrypted backup on server || [https://github.com/zootreeves/My-Wallet-Android Github] || 2012-05-12 || [http://bitcointalk.org/index.php?topic=74191.0 Forum]
|-
| [[Instawallet]] || {{Table Value Yes}} || {{Table Value No}} || ? || ? || {{Table Value No}} || {{Table Value No}} || [[Instawallet]] || Proprietary || 2012-06-18 || [https://bitcointalk.org/index.php?topic=73388.msg972384#msg972384 Forum]
|-
| [[FriendlyPay]] || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || [[Instawallet]] || Proprietary || 2012-05-12 || [http://bitcointalk.org/index.php?topic=6785.msg869671#msg869671 Forum]
|-
| [[Paytunia]] || {{Table Value Yes}} || {{Table Value Yes}}<ref>Private Beta</ref> || ? || ? || {{Table Value Yes}} || {{Table Value No}} || Server (Hosted) || Proprietary || 2012-05-12 || [http://bitcointalk.org/index.php?topic=75550.0 Forum]
|-
| [[Easywallet.org]] || {{Table Value Yes}} || {{Table Value Yes}} || ? || ? || {{Table Value Yes}} || {{Table Value No}} || Easywallet.org || Proprietary || 2012-05-12 || [https://bitcointalk.org/index.php?topic=75665.0 Forum]
|-
| [[ResponsePay]] || {{Table Value Yes}} || {{Table Value Yes}} || {{Table Value No}} || {{Table Value No}} || {{Table Value Yes}} || {{Table Value No}} || ResponsePay.com || Proprietary || 2012-07-10 || [https://bitcointalk.org/index.php?topic=91431.0 Forum]
|}

==See Also==

* [[Payment methods]]
* [http://dre.tx0.org/compare.htm Open-Source Bitcoin Clients for the Desktop]

==References==
<references />

[[Category:Mobile]]
[[Category:Software]]
[[Category:Clients]]
[[Category:Wallets]]
[[Category:Free Software]]
[[Category:Open Source]]