Bitcoin Wiki - User contributions [en]

Software

2020-04-28T06:53:38Z

Coinx: /* Bitcoin clients */ Remove Webskin since project was removed from github

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 Core]] - 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" - also a [[Thin Client Security|thin client]].
*[https://bither.net/ Bither] - open source wallet for Android, iPhone and Desktop with cold storage support.
*[[Bitcoin-js-remote]] - JavaScript RPC client, support for QR codes
*[https://github.com/TheSeven/Bitcoin-WebUI Bitcoin WebUI] - JavaScript RPC client
*[[Bitcoin_Explorer|Bitcoin Explorer]] - Bitcoin command line tools for Linux, OSX and Windows, part of [[Libbitcoin]] SDK.
*[[Bitcoiner]] - Java RPC client (Android)
*[[Armory]] - Enterprise grade Python-based client
*[[Spesmilo]] - Python/PySide RPC client (abandoned)
*[[Gocoin bitcoin software|Gocoin]] - WebUI client written in Go language, with a cold deterministic brain-wallet.
*[https://github.com/conformal/btcd btcd] An alternative full node bitcoin implementation written in Go (golang).
*[http://www.blockcypher.com BlockCypher] Full node bitcoin client built for scale and data centers, exposed through web APIs.
*[[Mycelium]] Awarded the prestigious "Best Mobile App" award by Blockchain.info in 2014, the Mycelium wallet for Android provides several security features.

====Frontends to eWallet====
*[https://blockchain.info/wallet Blockchain] - Javascript bitcoin client with client side encryption.
*[https://en.bitcoin.it/wiki/Xcoinmoney xCoinMoney] Advanced API to create invoices for subscription.
*[https://cancoin.co/wallet Cancoin] - HSM multi-sig wallet using libbitcoin. Client side encryption.
====Experimental====
*[[Freecoin]] - C++ client, supports alternative currencies like [https://bitcointalk.org/index.php?topic=9493.0 Beertoken]
*[[BitDroid]] - Java client
*[[Bitdollar]] - C++/Qt client, unstable beta version

==Bitcoin software==

===Live operating systems===

A [https://en.wikipedia.org/wiki/Live_USB live operating system] can start on almost any computer from a DVD, USB stick, or SD card, without installation.

* [[BitKey]] - Live OS Bitcoin Swiss Army Knife, supports cold storage and air-gapped transactions
* [https://tails.boum.org/ Tails] Privacy oriented Live OS, bundled with Tor and Electrum.

===Exchange Platform Software===
*[https://www.alphapoint.com/ Alphapoint] - Bitcoin Exchange Software. Full system to run a digital currency exchange. Customize and launch your own digital currency and Bitcoin exchange in less than 20 days with AlphaPoint. Also supports automatic market-making on your exchange using 3rd party exchanges such as Bitfinex, BTCChina, and others. Supports many exchanges and smart routing, with automated account management.
*[http://www.merkeleon.at/ex%D1%81hange/ Merkeleon] - Bitcoin Exchange Software. A fully online software solution to launch a secure and reliable platform for crypto- and main world fiat currencies sale and purchase. Supports any currency integration, provides wide monetization opportunity for the owner.
*[https://exknox.com/ ExKnox] - Open Source Exchange Software Development Team. Custom solutions built upon the world's most trusted matching engine.
*[https://www.sellbitbuy.net/ Sellbitbuy] - Local bitcoin clone script. Complete solution for launching an exchange platform like remitano, bitsquare and paxful.
*[https://www.cryptoexchangescript.com Cryptoexchangescript.com]-Cryptocurrency/bitcoin exchange script software.A complete solution to start your own bitcoin trading or exchange platform instantly.The website provides demo with 100% source code, go to market options and easy setup.

===Shopping Cart Integration in eCommerce-Systems===
*[[File:Ms-icon-310x310.png|20px]] [https://apirone.com/integrations/ Apirone.com] - Magento 2, WooCommerce, OpenCart 3.x & 2.3, ocStore and VirtueMart plugins, PHP, Rest API. Accept Bitcoins directly to specified wallet. SegWit support.
*[[GoCoin]] - Plugin for WooCommerce support and coming soon Magento
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart.
*[https://coinbase.com/docs/merchant_tools/shopping_cart_plugins Coinbase Shopping Cart Plugins] - Supports Wordpress, WooCommerce, Magento, Zencart, WP e-commerce, and more.
*[[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
* [https://www.xcoinmoney.com/info/api-general-info xCoinMoney] Advanced API for instant payment and subscriptions
*[[OpenCart Bitcoin]] - An OpenCart payment module that communicates with a bitcoin client using JSON RPC.
* [[File:MCS_200by200_logo-01.png|20px|link=http://www.mycoinsolution.com]][http://www.mycoinsolution.com My Coin Solution] - Bitcoin consulting services and solutions; custom payment integrations
*[[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.

=== Enterprise server ===
*[https://apicoin.io Apicoin] First bitcoin PaaS (Platform as a Service)
*[http://bitsofproof.com Bits of Proof] - a modular enterprise-ready implementation of the Bitcoin protocol.
*[http://www.blockcypher.com BlockCypher] Full node bitcoin client built for scale and data center environments.

===Web apps===
*[[Cryptopay]] — hosted wallet, exchange and bitcoin debit card provider
*[[Abe]] — block chain viewer
*[[Bitcoin Central]] — currency exchange
*[https://github.com/Mirobit/bitcoin-node-manager Bitcoin Node Manager] — Open source PHP dashboard for Bitcoin nodes.
*[[Bitcoin Poker Room]] — poker site
*[[bitcoin_simple_php_tools]] — simple php tools for webmasters
*[[Blockonomics]] - Easy to use bitcoin financial tracker
*[[Blockpath]] - Wallet tracker with a graphical block explorer, QuickBooks integration, and blockchain discussion platform
*[[Blocktrail]] - Web wallet with high level security. Syncs seamlessly with your iphone and android Blocktrail wallet.
*[https://en.bitcoin.it/wiki/Coinbase_(business) Coinbase] — an international digital wallet that allows you to securely buy, use, and accept bitcoin currency
*[[Coinnext]] — Cryptocurrency Exchange
*[http://www.coinsummary.com/ CoinSummary] — multi-coin wallet manager with built-in valuation in Bitcoin and major world currencies.
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Accept Bitcoin and Sell bitcoin on Peer to peer market.
*[[Pocket Dice]] — First realistic bitcoin dice game.
*[[Simplecoin]] — PHP web frontend for a pool
*[[Coinbase Exchange]] - Bitcoin exchange with complete API for traders.
*[https://cancoin.co/wallet Cancoin] - HSM Multi-sig wallet and p2p exchange* *coming soon

===White label software===
*[https://www.alphapoint.com/ Alphapoint] - Bitcoin Exchange Software. Full system to run a digital currency exchange. Customize and launch your own digital currency and Bitcoin exchange in less than 20 days with AlphaPoint. Also supports automatic market-making on your exchange using 3rd party exchanges such as Bitstamp and others. Supports many exchanges and smart routing, with automated account management.

*[https://www.draglet.com/ draglet] - Bitcoin Exchange Software / white label solution

*[https://www.casinoevolution.com/ '''Casino Evolution'''] gaming software developed by '''www.SoftSwiss.com'''
*[http://www.infraexdev.com/ InfraEx Development] - Open Source Exchange Software Development Team. Custom solutions built upon the world's most trusted matching engine.

===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===
*[https://centrabit.com/downloads/ Qt Bitcoin Trader] - Open Source Multi exchange trading client for Windows, Mac OS X and Linux
*[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)
*[https://www.cortex7.net Cortex7] - Multi exchange charting and trading application for Windows, Mac and Linux.
*[[Bitcoin_Explorer|Bitcoin Explorer]] - A command line client and tools for Windows, Mac and Linux. Single file binary download. Part of [[Libbitcoin]] SDK.
*[[Bitcoin_Server|Bitcoin Server]] - A full node for Windows, Mac and Linux. Single file binary download. Part of [[Libbitcoin]] SDK.

===Mobile apps===
==== iPhone / iPad ====
*[https://airbitz.co/bitcoin-wallet Airbitz Bitcoin Wallet] - Full featured iPhone bitcoin wallet & directory map (finds businesses that accept bitcoin near you). Airbitz wallet also automatically implements encryption, backup, and multidevice synchronization.
*[https://blockchain.info/wallet/iphone-app Blockchain] - Fully featured iphone bitcoin app.
*[https://blocktrail.com/ Blocktrail] - A powerful iphone bitcoin wallet, keeps you in control of your bitcoin. Highly secure. Syncs with the web wallet and android app seamlessly.
*[[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
*[http://blog.coinbase.com/post/64824441934/the-coinbase-ios-app-has-launched Coinbase iPhone App]
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on iPhone/iPad/iPod touch
*[https://itunes.apple.com/us/app/btc-miner/id648411895?ls=1&mt=8 BTC Miner (iPhone)] - monitor mining results from various mining pools on iPhone/iPad/iPod touch
*[[BitStore]] - Simple and secure native iOS wallet
*[[BitTick]] - Real-time Bitcoin ticker. Real-time currency convert(support 50+ currency. USD, GBP, EUR, CNY, JPY, CAD, RUB, AUD, BRL, NZD, PLN, KRW…)
*[https://itunes.apple.com/us/app/twizbits-bitcoin-price-ticker/id1041790847?mt=8- Twizbits Bitcoin price ticker] - Real-time Bitcoin price ticker for Coinbase Exchange (support USD, GBP, EUR, CAD)
*[https://itunes.apple.com/us/app/cold-storage-coins/id1352363663?mt=8 Cold Storage Coins iPhone app]. Pairs with Cold Storage Coins hard wallets, works with QR Code scanner on iPhone/iPad/ etc.

==== Android ====
* Direct link to Android Market bitcoin apps. https://play.google.com/store/search?q=bitcoin
*[https://play.google.com/store/apps/details?id=net.bither Bither] - open source Android wallet with support for offline cold storage.
*[[Mycelium]] - Leading SPV Android wallet with many advanced features.
*[https://airbitz.co/bitcoin-wallet Airbitz Bitcoin Wallet] - Full featured Android bitcoin wallet & directory map (finds businesses that accept bitcoin near you). Airbitz wallet also automatically implements encryption, backup, and multidevice synchronization.
*[[Bitcoin Alert]] - monitoring price (Android)
*[https://play.google.com/store/apps/details?id=com.mobnetic.coinguardian&hl=pl Bitcoin Checker] - Monitors the prices of cryptocurrencies on over 70 exchanges
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone
*[[Bitcoin Wallet]] - Functional Android bitcoin wallet application.
*[[BitPay]] - https://market.android.com/details?id=com.bitcoin.bitpay (Is not related to the bit-pay.com online payment processor.)
*[https://play.google.com/store/apps/details?id=st.brothas.mtgoxwidget&hl=pl Bitcoin Ticker Widget] - displays and monitors the current BTC and LTC exchange rates.
*[[Bridgewalker]] - euro-denominated wallet for the Bitcoin economy
*[https://blockchain.info/wallet/android-app Blockchain] - Lightweight Android Bitcoin Client - Also works with blockchain.info web interface and iphone app.
*[https://blocktrail.com/ Blocktrail] - A powerful android bitcoin wallet, keeps you in control of your bitcoin. Highly secure. Syncs with the web wallet and iphone app seamlessly.
*[https://play.google.com/store/apps/details?id=com.coinbase.android&hl=en Coinbase Wallet] - supports buying, selling, sending, requesting, and more.
*[https://play.google.com/store/apps/details?id=com.coinbase.android.merchant&hl=en Coinbase Merchant] - makes it easy to accept bitcoin at a retail location
*[http://coincliff.com CoinCliff] - Monitors price and fires alarms to wake you up, or notifications, as in text messages (Android)
*[http://coinomi.com/ Coinomi] - Coinomi is a very secure and lightweight, universal, open-source HD wallet for Bitcoin and many altcoins. ([https://play.google.com/store/apps/details?id=com.coinomi.wallet Android])
*[https://www.cortex7.net Cortex7] - Multi exchange charting and trading application for 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
*[http://tab-trader.com/ TabTrader] - monitoring and trading(Android)

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

==== Windows Phone 8 ====
*[[Bitcoin Can]] - Monitoring prices, account balances and mobile trading on multiple exchanges including Coinbase, BTC-E, CampBX, and MtGox. http://www.windowsphone.com/en-us/store/app/bitcoin-can/57fcf4d6-497a-4663-8da3-93cb26c83b11

see also [[Bitcoin Payment Apps]]

===Mining apps===
Main page: [[Mining software]]

*[[BFGMiner]] - Modular ASIC/FPGA/GPU miner in C
*[http://www.groupfabric.com/bitcoin-miner/ Bitcoin Miner by GroupFabric] - Free easy-to-use DirectX GPU miner on the Windows Store
*[[CGMiner]] - ASIC/FPGA/GPU miner in C
*[http://fabulouspanda.co.uk/macminer/ MacMiner] - A native Mac OS X Bitcoin miner based on cgminer, bfgminer, cpuminer and poclbm
*[[Asteroid]] - Mac-specific GUI based on cgminer
*[[MultiMiner]] - GUI based on cgminer/bfgminer for Windows, OS X and Linux, allows switching between currencies based on profitability

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

*[[CoiniumServ]] - High performance C# Mono/.Net poolserver.
*[[ecoinpool]] - Erlang poolserver (not maintained)
*[[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)
*[[Remote miner]] - mining pool software
*[[ckpool]] - Open source pool/database/proxy/passthrough/library in c for Linux

===Libraries===

=====C=====
*[https://github.com/libbtc/libbtc libbtc] - A fast, clean and small bitcoin C library
*[https://github.com/jgarzik/picocoin picocoin] - Tiny bitcoin library, with lightweight client and utils
*[https://github.com/luke-jr/libbase58 libbase58] - C library implementation of [[Base58]] and [[Base58Check]] encodings
*[[libblkmaker]] - C library implementation of [[getblocktemplate]] decentralized mining protocol

=====C++=====
*[[Libbitcoin]] - Comprehensive set of C++ libraries: key formats, crypto, math, encodings, urls, mnemonics, blockchain, full node, client-server, etc. Linux and OSX Autotools builds. Visual Studio solutions for Windows, with Unicode support. Extensive test suite and [https://travis-ci.org/libbitcoin continuous integration builds]. Core dependencies limited to [http://www.boost.org Boost] and [https://github.com/bitcoin/secp256k1 Libsecp256k1] with [http://zeromq.org ZeroMQ] required for client-server API.

====C / C++====
*[https://airbitz.co/bitcoin-wallet-api-library Bitcoin Wallet API Library] - Airbitz Core (ABC) C/C++ Library implements user authentication, account wallet creation, multi device synchronization and backup, transaction meta data management, Bitcoin address generation, key management, decentralized access to bitcoin network, shared wallets w/multisig (Q1 2015)

====Java====
*[[bitcoinj]] - popular client library for Java, currently used in several desktop/mobile applications.
*[[BCCAPI]] (BitCoin Client API) - a java library designed for making secure light-weight bitcoin clients.
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android.

====Objective-C====
*[https://github.com/keeshux/BitcoinSPV BitcoinSPV] - A native Bitcoin SPV client library for iOS with BIP32 support.

====Perl====
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API

====Python====
[https://pybtc.readthedocs.io/ PYBTC] Python library for Bitcoin.
*[[python-blkmaker]] - Python module implementation of [[getblocktemplate]] decentralized mining protocol

===Development utilities===
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol
*[[Bitcoin Explorer]] - an advanced command line tool for working with bitcoin
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet
*[https://github.com/straumat/blockchain2graph Blockchain2graph] - a tool to import bitcoin blockchain into neo4j

===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===
*[http://www.phyramid.com/ Phyramid] Digital Agency offering software development and design services for Bitcoin businesses.
*[[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
* [http://www.bitcoinmining.com/bitcoin-mining-software/ Bitcoin Mining Software] - A helpful list of various Bitcoin software options

== Webservices / APIs ==

===Bitcoin Infrastructure===
* [[BlockTrail.com]] - Bitcoin API and platform for developers, complete with SDKs for PHP, Python, NodeJS and more
* [http://www.blockcypher.com BlockCypher] - High reliability Bitcoin Web Services, including web hooks, double spend detection and many SDKs.

===Bitcoin Trade Data===
*[[Bitcoin Charts]] – Prices, volume, and extensive charting on virtually all Bitcoin markets.
*[https://bitcoinchain.com BitcoinChain] - Bitcoin block explorer, exchange markets and mining pools.
*[[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://MY-BTC.info MY-BTC.INFO] - A free profit/loss portfolio manager for Bitcoins and other digital currencies including many charts.
*[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.
*[[TradingView]] – network where traders exchange ideas about Bitcoin using advanced free online charts

===Web interfaces for merchants===
*[[File:Ms-icon-310x310.png|20px]] [https://apirone.com/docs/ Apirone.com] - CMS plugins, RESTful API, Bitcoin Forwarding and wallet API, native SegWit support.
*[https://developer.bitaps.com/ bitaps.com] - Blockchian API, Wallet API, Payment forwarding API, Market API, TOR network endpoint and TOR callbacks.
*[[BitMerch]] - Embeddable HTML buttons, instant sign-up, instant payouts, automatic price adjustment for other currencies. No programming skills required to set up.
*[[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
*[https://coinbase.com/merchants Coinbase] - Provides bitcoin payment processing for Overstock.com, Reddit, Khan Academy, OkCupid, and more.
*[[File:Easybitz.png|20px|link=https://github.com/goethewins/EzBitcoin-Api-Wallet]] Simplest Web API for processing transactions with your own server. php code igniter, database and logging auth system included. Same as block chain.info api
*[[BTCMerch]] - Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
*[[GoCoin]] - Payment gateway for bitcoin. Supports JavaScript, PHP, Java, Ruby, and .NET
*[[WalletBit]] - Easy JavaScript Buy Now buttons, Instant Payment Notification, Application Programming Interface (JSON API), Mobile Checkout, QR-Code
* [https://www.PikaPay.com PikaPay] ([[PikaPay|info]]) The PikaPay service will be retiring as of March 1st, 2015

[[Category:Software|*]]

Software

2020-04-28T06:41:34Z

Coinx: /* Web apps */ Add Bitcoin node manager

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 Core]] - 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" - also a [[Thin Client Security|thin client]].
*[https://bither.net/ Bither] - open source wallet for Android, iPhone and Desktop with cold storage support.
*[[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
*[[Bitcoin_Explorer|Bitcoin Explorer]] - Bitcoin command line tools for Linux, OSX and Windows, part of [[Libbitcoin]] SDK.
*[[Bitcoiner]] - Java RPC client (Android)
*[[Armory]] - Enterprise grade Python-based client
*[[Spesmilo]] - Python/PySide RPC client (abandoned)
*[[Gocoin bitcoin software|Gocoin]] - WebUI client written in Go language, with a cold deterministic brain-wallet.
*[https://github.com/conformal/btcd btcd] An alternative full node bitcoin implementation written in Go (golang).
*[http://www.blockcypher.com BlockCypher] Full node bitcoin client built for scale and data centers, exposed through web APIs.
*[[Mycelium]] Awarded the prestigious "Best Mobile App" award by Blockchain.info in 2014, the Mycelium wallet for Android provides several security features.

====Frontends to eWallet====
*[https://blockchain.info/wallet Blockchain] - Javascript bitcoin client with client side encryption.
*[https://en.bitcoin.it/wiki/Xcoinmoney xCoinMoney] Advanced API to create invoices for subscription.
*[https://cancoin.co/wallet Cancoin] - HSM multi-sig wallet using libbitcoin. Client side encryption.
====Experimental====
*[[Freecoin]] - C++ client, supports alternative currencies like [https://bitcointalk.org/index.php?topic=9493.0 Beertoken]
*[[BitDroid]] - Java client
*[[Bitdollar]] - C++/Qt client, unstable beta version

==Bitcoin software==

===Live operating systems===

A [https://en.wikipedia.org/wiki/Live_USB live operating system] can start on almost any computer from a DVD, USB stick, or SD card, without installation.

* [[BitKey]] - Live OS Bitcoin Swiss Army Knife, supports cold storage and air-gapped transactions
* [https://tails.boum.org/ Tails] Privacy oriented Live OS, bundled with Tor and Electrum.

===Exchange Platform Software===
*[https://www.alphapoint.com/ Alphapoint] - Bitcoin Exchange Software. Full system to run a digital currency exchange. Customize and launch your own digital currency and Bitcoin exchange in less than 20 days with AlphaPoint. Also supports automatic market-making on your exchange using 3rd party exchanges such as Bitfinex, BTCChina, and others. Supports many exchanges and smart routing, with automated account management.
*[http://www.merkeleon.at/ex%D1%81hange/ Merkeleon] - Bitcoin Exchange Software. A fully online software solution to launch a secure and reliable platform for crypto- and main world fiat currencies sale and purchase. Supports any currency integration, provides wide monetization opportunity for the owner.
*[https://exknox.com/ ExKnox] - Open Source Exchange Software Development Team. Custom solutions built upon the world's most trusted matching engine.
*[https://www.sellbitbuy.net/ Sellbitbuy] - Local bitcoin clone script. Complete solution for launching an exchange platform like remitano, bitsquare and paxful.
*[https://www.cryptoexchangescript.com Cryptoexchangescript.com]-Cryptocurrency/bitcoin exchange script software.A complete solution to start your own bitcoin trading or exchange platform instantly.The website provides demo with 100% source code, go to market options and easy setup.

===Shopping Cart Integration in eCommerce-Systems===
*[[File:Ms-icon-310x310.png|20px]] [https://apirone.com/integrations/ Apirone.com] - Magento 2, WooCommerce, OpenCart 3.x & 2.3, ocStore and VirtueMart plugins, PHP, Rest API. Accept Bitcoins directly to specified wallet. SegWit support.
*[[GoCoin]] - Plugin for WooCommerce support and coming soon Magento
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart.
*[https://coinbase.com/docs/merchant_tools/shopping_cart_plugins Coinbase Shopping Cart Plugins] - Supports Wordpress, WooCommerce, Magento, Zencart, WP e-commerce, and more.
*[[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
* [https://www.xcoinmoney.com/info/api-general-info xCoinMoney] Advanced API for instant payment and subscriptions
*[[OpenCart Bitcoin]] - An OpenCart payment module that communicates with a bitcoin client using JSON RPC.
* [[File:MCS_200by200_logo-01.png|20px|link=http://www.mycoinsolution.com]][http://www.mycoinsolution.com My Coin Solution] - Bitcoin consulting services and solutions; custom payment integrations
*[[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.

=== Enterprise server ===
*[https://apicoin.io Apicoin] First bitcoin PaaS (Platform as a Service)
*[http://bitsofproof.com Bits of Proof] - a modular enterprise-ready implementation of the Bitcoin protocol.
*[http://www.blockcypher.com BlockCypher] Full node bitcoin client built for scale and data center environments.

===Web apps===
*[[Cryptopay]] — hosted wallet, exchange and bitcoin debit card provider
*[[Abe]] — block chain viewer
*[[Bitcoin Central]] — currency exchange
*[https://github.com/Mirobit/bitcoin-node-manager Bitcoin Node Manager] — Open source PHP dashboard for Bitcoin nodes.
*[[Bitcoin Poker Room]] — poker site
*[[bitcoin_simple_php_tools]] — simple php tools for webmasters
*[[Blockonomics]] - Easy to use bitcoin financial tracker
*[[Blockpath]] - Wallet tracker with a graphical block explorer, QuickBooks integration, and blockchain discussion platform
*[[Blocktrail]] - Web wallet with high level security. Syncs seamlessly with your iphone and android Blocktrail wallet.
*[https://en.bitcoin.it/wiki/Coinbase_(business) Coinbase] — an international digital wallet that allows you to securely buy, use, and accept bitcoin currency
*[[Coinnext]] — Cryptocurrency Exchange
*[http://www.coinsummary.com/ CoinSummary] — multi-coin wallet manager with built-in valuation in Bitcoin and major world currencies.
* [[File:Paxful_how-to-buy-bitcoin.png |20px|link=https://paxful.com]] [https://paxful.com Paxful] Accept Bitcoin and Sell bitcoin on Peer to peer market.
*[[Pocket Dice]] — First realistic bitcoin dice game.
*[[Simplecoin]] — PHP web frontend for a pool
*[[Coinbase Exchange]] - Bitcoin exchange with complete API for traders.
*[https://cancoin.co/wallet Cancoin] - HSM Multi-sig wallet and p2p exchange* *coming soon

===White label software===
*[https://www.alphapoint.com/ Alphapoint] - Bitcoin Exchange Software. Full system to run a digital currency exchange. Customize and launch your own digital currency and Bitcoin exchange in less than 20 days with AlphaPoint. Also supports automatic market-making on your exchange using 3rd party exchanges such as Bitstamp and others. Supports many exchanges and smart routing, with automated account management.

*[https://www.draglet.com/ draglet] - Bitcoin Exchange Software / white label solution

*[https://www.casinoevolution.com/ '''Casino Evolution'''] gaming software developed by '''www.SoftSwiss.com'''
*[http://www.infraexdev.com/ InfraEx Development] - Open Source Exchange Software Development Team. Custom solutions built upon the world's most trusted matching engine.

===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===
*[https://centrabit.com/downloads/ Qt Bitcoin Trader] - Open Source Multi exchange trading client for Windows, Mac OS X and Linux
*[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)
*[https://www.cortex7.net Cortex7] - Multi exchange charting and trading application for Windows, Mac and Linux.
*[[Bitcoin_Explorer|Bitcoin Explorer]] - A command line client and tools for Windows, Mac and Linux. Single file binary download. Part of [[Libbitcoin]] SDK.
*[[Bitcoin_Server|Bitcoin Server]] - A full node for Windows, Mac and Linux. Single file binary download. Part of [[Libbitcoin]] SDK.

===Mobile apps===
==== iPhone / iPad ====
*[https://airbitz.co/bitcoin-wallet Airbitz Bitcoin Wallet] - Full featured iPhone bitcoin wallet & directory map (finds businesses that accept bitcoin near you). Airbitz wallet also automatically implements encryption, backup, and multidevice synchronization.
*[https://blockchain.info/wallet/iphone-app Blockchain] - Fully featured iphone bitcoin app.
*[https://blocktrail.com/ Blocktrail] - A powerful iphone bitcoin wallet, keeps you in control of your bitcoin. Highly secure. Syncs with the web wallet and android app seamlessly.
*[[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
*[http://blog.coinbase.com/post/64824441934/the-coinbase-ios-app-has-launched Coinbase iPhone App]
*[[Easywallet.org]] - Web based wallet, works with QR Code scanner on iPhone/iPad/iPod touch
*[https://itunes.apple.com/us/app/btc-miner/id648411895?ls=1&mt=8 BTC Miner (iPhone)] - monitor mining results from various mining pools on iPhone/iPad/iPod touch
*[[BitStore]] - Simple and secure native iOS wallet
*[[BitTick]] - Real-time Bitcoin ticker. Real-time currency convert(support 50+ currency. USD, GBP, EUR, CNY, JPY, CAD, RUB, AUD, BRL, NZD, PLN, KRW…)
*[https://itunes.apple.com/us/app/twizbits-bitcoin-price-ticker/id1041790847?mt=8- Twizbits Bitcoin price ticker] - Real-time Bitcoin price ticker for Coinbase Exchange (support USD, GBP, EUR, CAD)
*[https://itunes.apple.com/us/app/cold-storage-coins/id1352363663?mt=8 Cold Storage Coins iPhone app]. Pairs with Cold Storage Coins hard wallets, works with QR Code scanner on iPhone/iPad/ etc.

==== Android ====
* Direct link to Android Market bitcoin apps. https://play.google.com/store/search?q=bitcoin
*[https://play.google.com/store/apps/details?id=net.bither Bither] - open source Android wallet with support for offline cold storage.
*[[Mycelium]] - Leading SPV Android wallet with many advanced features.
*[https://airbitz.co/bitcoin-wallet Airbitz Bitcoin Wallet] - Full featured Android bitcoin wallet & directory map (finds businesses that accept bitcoin near you). Airbitz wallet also automatically implements encryption, backup, and multidevice synchronization.
*[[Bitcoin Alert]] - monitoring price (Android)
*[https://play.google.com/store/apps/details?id=com.mobnetic.coinguardian&hl=pl Bitcoin Checker] - Monitors the prices of cryptocurrencies on over 70 exchanges
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone
*[[Bitcoin Wallet]] - Functional Android bitcoin wallet application.
*[[BitPay]] - https://market.android.com/details?id=com.bitcoin.bitpay (Is not related to the bit-pay.com online payment processor.)
*[https://play.google.com/store/apps/details?id=st.brothas.mtgoxwidget&hl=pl Bitcoin Ticker Widget] - displays and monitors the current BTC and LTC exchange rates.
*[[Bridgewalker]] - euro-denominated wallet for the Bitcoin economy
*[https://blockchain.info/wallet/android-app Blockchain] - Lightweight Android Bitcoin Client - Also works with blockchain.info web interface and iphone app.
*[https://blocktrail.com/ Blocktrail] - A powerful android bitcoin wallet, keeps you in control of your bitcoin. Highly secure. Syncs with the web wallet and iphone app seamlessly.
*[https://play.google.com/store/apps/details?id=com.coinbase.android&hl=en Coinbase Wallet] - supports buying, selling, sending, requesting, and more.
*[https://play.google.com/store/apps/details?id=com.coinbase.android.merchant&hl=en Coinbase Merchant] - makes it easy to accept bitcoin at a retail location
*[http://coincliff.com CoinCliff] - Monitors price and fires alarms to wake you up, or notifications, as in text messages (Android)
*[http://coinomi.com/ Coinomi] - Coinomi is a very secure and lightweight, universal, open-source HD wallet for Bitcoin and many altcoins. ([https://play.google.com/store/apps/details?id=com.coinomi.wallet Android])
*[https://www.cortex7.net Cortex7] - Multi exchange charting and trading application for 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
*[http://tab-trader.com/ TabTrader] - monitoring and trading(Android)

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

==== Windows Phone 8 ====
*[[Bitcoin Can]] - Monitoring prices, account balances and mobile trading on multiple exchanges including Coinbase, BTC-E, CampBX, and MtGox. http://www.windowsphone.com/en-us/store/app/bitcoin-can/57fcf4d6-497a-4663-8da3-93cb26c83b11

see also [[Bitcoin Payment Apps]]

===Mining apps===
Main page: [[Mining software]]

*[[BFGMiner]] - Modular ASIC/FPGA/GPU miner in C
*[http://www.groupfabric.com/bitcoin-miner/ Bitcoin Miner by GroupFabric] - Free easy-to-use DirectX GPU miner on the Windows Store
*[[CGMiner]] - ASIC/FPGA/GPU miner in C
*[http://fabulouspanda.co.uk/macminer/ MacMiner] - A native Mac OS X Bitcoin miner based on cgminer, bfgminer, cpuminer and poclbm
*[[Asteroid]] - Mac-specific GUI based on cgminer
*[[MultiMiner]] - GUI based on cgminer/bfgminer for Windows, OS X and Linux, allows switching between currencies based on profitability

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

*[[CoiniumServ]] - High performance C# Mono/.Net poolserver.
*[[ecoinpool]] - Erlang poolserver (not maintained)
*[[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)
*[[Remote miner]] - mining pool software
*[[ckpool]] - Open source pool/database/proxy/passthrough/library in c for Linux

===Libraries===

=====C=====
*[https://github.com/libbtc/libbtc libbtc] - A fast, clean and small bitcoin C library
*[https://github.com/jgarzik/picocoin picocoin] - Tiny bitcoin library, with lightweight client and utils
*[https://github.com/luke-jr/libbase58 libbase58] - C library implementation of [[Base58]] and [[Base58Check]] encodings
*[[libblkmaker]] - C library implementation of [[getblocktemplate]] decentralized mining protocol

=====C++=====
*[[Libbitcoin]] - Comprehensive set of C++ libraries: key formats, crypto, math, encodings, urls, mnemonics, blockchain, full node, client-server, etc. Linux and OSX Autotools builds. Visual Studio solutions for Windows, with Unicode support. Extensive test suite and [https://travis-ci.org/libbitcoin continuous integration builds]. Core dependencies limited to [http://www.boost.org Boost] and [https://github.com/bitcoin/secp256k1 Libsecp256k1] with [http://zeromq.org ZeroMQ] required for client-server API.

====C / C++====
*[https://airbitz.co/bitcoin-wallet-api-library Bitcoin Wallet API Library] - Airbitz Core (ABC) C/C++ Library implements user authentication, account wallet creation, multi device synchronization and backup, transaction meta data management, Bitcoin address generation, key management, decentralized access to bitcoin network, shared wallets w/multisig (Q1 2015)

====Java====
*[[bitcoinj]] - popular client library for Java, currently used in several desktop/mobile applications.
*[[BCCAPI]] (BitCoin Client API) - a java library designed for making secure light-weight bitcoin clients.
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android.

====Objective-C====
*[https://github.com/keeshux/BitcoinSPV BitcoinSPV] - A native Bitcoin SPV client library for iOS with BIP32 support.

====Perl====
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API

====Python====
[https://pybtc.readthedocs.io/ PYBTC] Python library for Bitcoin.
*[[python-blkmaker]] - Python module implementation of [[getblocktemplate]] decentralized mining protocol

===Development utilities===
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol
*[[Bitcoin Explorer]] - an advanced command line tool for working with bitcoin
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet
*[https://github.com/straumat/blockchain2graph Blockchain2graph] - a tool to import bitcoin blockchain into neo4j

===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===
*[http://www.phyramid.com/ Phyramid] Digital Agency offering software development and design services for Bitcoin businesses.
*[[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
* [http://www.bitcoinmining.com/bitcoin-mining-software/ Bitcoin Mining Software] - A helpful list of various Bitcoin software options

== Webservices / APIs ==

===Bitcoin Infrastructure===
* [[BlockTrail.com]] - Bitcoin API and platform for developers, complete with SDKs for PHP, Python, NodeJS and more
* [http://www.blockcypher.com BlockCypher] - High reliability Bitcoin Web Services, including web hooks, double spend detection and many SDKs.

===Bitcoin Trade Data===
*[[Bitcoin Charts]] – Prices, volume, and extensive charting on virtually all Bitcoin markets.
*[https://bitcoinchain.com BitcoinChain] - Bitcoin block explorer, exchange markets and mining pools.
*[[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://MY-BTC.info MY-BTC.INFO] - A free profit/loss portfolio manager for Bitcoins and other digital currencies including many charts.
*[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.
*[[TradingView]] – network where traders exchange ideas about Bitcoin using advanced free online charts

===Web interfaces for merchants===
*[[File:Ms-icon-310x310.png|20px]] [https://apirone.com/docs/ Apirone.com] - CMS plugins, RESTful API, Bitcoin Forwarding and wallet API, native SegWit support.
*[https://developer.bitaps.com/ bitaps.com] - Blockchian API, Wallet API, Payment forwarding API, Market API, TOR network endpoint and TOR callbacks.
*[[BitMerch]] - Embeddable HTML buttons, instant sign-up, instant payouts, automatic price adjustment for other currencies. No programming skills required to set up.
*[[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
*[https://coinbase.com/merchants Coinbase] - Provides bitcoin payment processing for Overstock.com, Reddit, Khan Academy, OkCupid, and more.
*[[File:Easybitz.png|20px|link=https://github.com/goethewins/EzBitcoin-Api-Wallet]] Simplest Web API for processing transactions with your own server. php code igniter, database and logging auth system included. Same as block chain.info api
*[[BTCMerch]] - Payment processor for bitcoins and other cryptocurrencies. 0.5% transaction fee. Sandbox is available.
*[[GoCoin]] - Payment gateway for bitcoin. Supports JavaScript, PHP, Java, Ruby, and .NET
*[[WalletBit]] - Easy JavaScript Buy Now buttons, Instant Payment Notification, Application Programming Interface (JSON API), Mobile Checkout, QR-Code
* [https://www.PikaPay.com PikaPay] ([[PikaPay|info]]) The PikaPay service will be retiring as of March 1st, 2015

[[Category:Software|*]]

Running Bitcoin

2016-06-14T17:32:55Z

Coinx: /* Command-line arguments */ Add relay options

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

__TOC__

==Linux Quickstart==

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

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

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

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

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

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

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

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

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

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

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

# Network-related settings:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Miscellaneous options

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

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

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

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

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

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

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

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

Settings -> Options

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

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

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

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

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

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

{{Bitcoin Core documentation}}

Running Bitcoin

2015-09-19T23:38:40Z

Coinx: /* Command-line arguments */

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

__TOC__

==Linux Quickstart==

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

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

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

Bitcoin Core Daemon version v0.10.2

Usage:
bitcoind [options] Start Bitcoin Core Daemon

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Network-related settings:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Miscellaneous options

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

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

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

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

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

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

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

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

Settings -> Options

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

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

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

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

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

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

{{Bitcoin Core documentation}}

Running Bitcoin

2015-09-19T22:00:26Z

Coinx: /* Command-line arguments */

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

__TOC__

==Linux Quickstart==

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

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

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

Bitcoin Core Daemon version v0.10.2

Usage:
bitcoind [options] Start Bitcoin Core Daemon

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Network-related settings:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Miscellaneous options

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

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

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

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

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

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

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

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

Settings -> Options

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

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

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

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

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

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

{{Bitcoin Core documentation}}

Running Bitcoin

2015-07-28T14:29:01Z

Coinx:

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

__TOC__

==Linux Quickstart==

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

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

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

Bitcoin Core Daemon version v0.10.2

Usage:
bitcoind [options] Start Bitcoin Core Daemon

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Network-related settings:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Miscellaneous options

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

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

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

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

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

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

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

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

Settings -> Options

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

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

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

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

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

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

Miner fees

2015-06-06T01:50:46Z

Coinx: /* Reference Implementation */

[[File:fee.png|thumb|Receiving the fees from hundreds of transactions (0.44 BTC)]]
'''Transaction fees''' may be included with any transfer of bitcoins from one address to another. At the moment, many [[transactions]] are typically processed in a way where no fee is expected at all, but for transactions which draw coins from many bitcoin addresses and therefore have a large data size, a small transaction fee is usually expected.

The transaction fee is processed by and received by the bitcoin miner. When a new bitcoin block is generated with a successful hash, the information for all of the transactions is included with the block and all transaction fees are collected by that user creating the block, who is free to assign those fees to himself.

Transaction fees are voluntary on the part of the person making the bitcoin transaction, as the person attempting to make a transaction can include any fee or none at all in the transaction. On the other hand, nobody mining new bitcoins necessarily needs to accept the transactions and include them in the new block being created. The transaction fee is therefore an incentive on the part of the bitcoin user to make sure that a particular transaction will get included into the next block which is generated.

It is envisioned that over time the cumulative effect of collecting transaction fees will allow somebody creating new blocks to "earn" more bitcoins than will be mined from new bitcoins created by the new block itself. This is also an incentive to keep trying to create new blocks even if the value of the newly created block from the mining activity is zero in the far future.

==Reference Implementation==

The following sections describe the behavior of the [[Original Bitcoin client|reference implementation]] as of version 0.10.0. Earlier versions treated fees differently, as do other popular implementations (including possible later versions).

===Sending===

A transaction may be safely sent without fees if these conditions are met:

* It is smaller than 1,000 bytes.
* All outputs are 0.01 BTC or larger.
* Its priority is large enough (see the Technical Info section below)

Otherwise, the reference implementation will round up the transaction size to the next thousand bytes and add a fee of 0.1 mBTC (0.0001 BTC) per thousand bytes<ref>[http://bitcointalk.org/index.php?topic=219504.0 Default fee dropped in v0.8.2]</ref>. As an example, a fee of 0.1 mBTC (0.0001 BTC) would be added to a 746 byte transaction, and a fee of 0.2 mBTC (0.0002 BTC) would be added to a 1001 byte transaction.
Users may increase the default 0.0001 BTC/kB fee setting, but cannot control transaction fees for each transaction. Bitcoin-Qt does prompt the user to accept the fee before the transaction is sent (they may cancel the transaction if they are not willing to pay the fee).

Note that a typical transaction is 500 bytes, so the typical transaction fee for low-priority transactions is 0.1 mBTC (0.0001 BTC), regardless of the number of bitcoins sent.

===Including in Blocks===

This section describes how the reference implementation selects which transactions to put into new blocks, with default settings. All of the settings may be changed if a miner wants to create larger or smaller blocks containing more or fewer free transactions.

50,000 bytes in the block are set aside for the highest-priority transactions, regardless of transaction fee. Transactions are added highest-priority-first to this section of the block.

Then transactions that pay a fee of at least 0.00001 BTC/kb are added to the block, highest-fee-per-kilobyte transactions first, until the block is not more than 750,000 bytes big.

The remaining transactions remain in the miner's "memory pool", and may be included in later blocks if their priority or fee is large enough.

===Relaying===

The reference implementation's rules for relaying transactions across the peer-to-peer network are very similar to the rules for sending transactions, as a value of 0.00001 BTC is used to determine whether or not a transaction is considered "Free". However, the rule that all outputs must be 0.01 BTC or larger does not apply. To prevent "penny-flooding" denial-of-service attacks on the network, the reference implementation caps the number of free transactions it will relay to other nodes to (by default) 15 thousand bytes per minute.

===Settings===

{| class="wikitable"
|-
! Setting !! Default Value (units)
|-
| paytxfee || 0.0000 (BTC)
|-
| mintxfee || 0.0001 (BTC)
|-
| limitfreerelay || 15 (thousand bytes per minute)
|-
| minrelaytxfee || 0.00001 (BTC)
|-
| blockmaxsize || 750000 (bytes)
|-
| blockminsize || 0 (bytes)
|-
| blockprioritysize || 50000 (bytes)
|}

==Technical info==

Transaction priority is calculated as a value-weighted sum of input age, divided by transaction size in bytes:
priority = sum(input_value_in_base_units * input_age)/size_in_bytes
Transactions need to have a priority above 57,600,000 to avoid the enforced limit (as of client version 0.3.21). This threshold is written in the code as COIN * 144 / 250, suggesting that the threshold represents a one day old, 1 btc coin (144 is the expected number of blocks per day) and a transaction size of 250 bytes.

So, for example, a transaction that has 2 inputs, one of 5 btc with 10 confirmations, and one of 2 btc with 3 confirmations, and has a size of 500bytes, will have a priority of
(500000000 * 10 + 200000000 * 3) / 500 = 11,200,000

==See Also==

* [[Free transaction relay policy]]
* [http://blockchain.info/charts/transaction-fees Transaction fee chart]

==References==
<references />

[[Category:Technical]]
[[Category:Vocabulary]]
[[Category:Mining]]
[[de:Transaktionsgebühren]]

Running Bitcoin

2015-06-06T01:47:49Z

Coinx: /* Command-line arguments */

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

__TOC__

==Linux Quickstart==

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

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

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

Usage:
bitcoin-qt [command-line options]

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

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

Relay options
-minrelaytxfee=<amt> Fees smaller than this (in satoshi) are considered zero fee (relaying and mining) (default:1000)
-limitfreerelay=<n> Rate-limit free transactions to <n>*1000 bytes per minute (default: 15)

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

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

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

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

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

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

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

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

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

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

# Network-related settings:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Miscellaneous options

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

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

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

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

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

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

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

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

Settings -> Options

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

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

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

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

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

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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

Running Bitcoin

2015-06-06T01:36:23Z

Coinx:

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

__TOC__

==Linux Quickstart==

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

./bitcoind

To run with the standard GUI interface:

./bitcoin-qt

==Command-line arguments==

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

Usage:
bitcoin-qt [command-line options]

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

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

Relay policy
-minrelaytxfee=<amt> Fees smaller than this (in satoshi) are considered zero fee (relaying and mining) (default:1000)
-limitfreerelay=<n> Rate-limit free transactions to <n>*1000 bytes per minute (default: 15)

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

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

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

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

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

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

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

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

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

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

# Network-related settings:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# Miscellaneous options

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

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

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

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

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

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

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

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

Settings -> Options

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

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

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

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

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

==See Also==

* [[Data directory]]

[[es:Ejecución de Bitcoin]]

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