P2Pool - Bitcoin Wiki P2pool bitcoin.conf

Содержание статьи

Setting up a working P2Pool mostly consists of:

  • Running a Bitcoin node (Bitcoin-Qt or bitcoind).
  • Running P2Pool on the same machine (will fetch blocks data from bitcoind).
  • Running Bitcoin miners (will fetch work from P2Pool).

1. Setup Bitcoin-Qt or bitcoind

Download and install Bitcoin-Qt or bitcoind. Initial synchronization will likely take more than a day to complete. For this reason, it is generally a good idea to complete this step in advance.

Insert the following text into bitcoin.conf and restart Bitcoin-Qt or bitcoind:

rpcpassword=(random data)

bitcoin.conf can be found in the following folder: %AppData%\Bitcoin

bitcoin.conf can be found in the following folder: ~/.bitcoin

2. Run P2Pool

Download P2Pool and execute run_p2pool.exe (Windows) or 'python' (Linux/OS X/source).

P2Pool will start downloading the sharechain, displaying sections like this occasionally:

2014-01-09 17:15:45.075550 P2Pool: 0 shares in chain (0 verified/3133 total) Peers: 5 (0 incoming)
2014-01-09 17:15:45.075662 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???

Within a few minutes, it should start showing sections like this (notice the pool hashrate - Pool: 115TH/s - is now shown), indicating that the sharechain has finished downloading. As you can see from the timestamps, here it took about one and a half minutes. It will vary depending on your CPU speed and Internet bandwidth.

2014-01-09 17:16:49.525335 P2Pool: 8698 shares in chain (57 verified/8698 total) Peers: 5 (0 incoming)
2014-01-09 17:16:49.525422 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-01-09 17:16:49.525476 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2014-01-09 17:16:49.525510 Pool: 115TH/s Stale rate: 12.4% Expected time to block: 14.7 hours

3. Run miners

Just point miners to http://HOST:9332/ with HOST being the IP address of the computer running P2Pool. The username can be your payout Bitcoin address or anything that describes the miner if you prefer to mine into your Bitcoin-Qt/bitcoind wallet. Use any password; it is ignored by P2Pool. When mining on the same machine, you can use as the P2Pool host.

Easyminer can be downloaded here.

Downloading and building bfgminer from the terminal:

sudo apt-get install git build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev
git clone git://
cd bfgminer

Running bfgminer from the terminal:

./bfgminer -o -u user -p password

Binaries for Windows (32bit and 64bit) can be downloaded here.

You can run bfgminer from the command line:

bfgminer.exe -o -u user -p password

Or you can create a preconfigured shortcut on the desktop:

cgminer --url --userpass cgminer:password

See the last question of this FAQ.

4. Watch

Unless your miners have Bitcoin addresses as usernames, payouts will go to Bitcoin-Qt/bitcoind's wallet. You can look at P2Pool's web interface, which has statistics and graphs, by going to http://YOUR_P2POOL_HOST:9332/ in a browser - if you're looking at this tutorial on the same host that P2Pool is running.

Once your P2Pool setup is working, make sure to subscribe to the P2Pool notifications mailing list to receive urgent pool status updates.

Это интересно:

Summary in Bitcoin Mine Exploration - Jaeger - Google Sites

From Bitcoin Wiki

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).

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:


To run with the standard GUI interface:


Command-line arguments

These commands are accurate as of Bitcoin Core version v0.14.0.

Command Description
-? Print this help message and exit
-version Print version and exit
-alertnotify= Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
-blocknotify= Execute command when the best block changes (%s in cmd is replaced by block hash)
-assumevalid= If this block is in the chain assume that it and its ancestors are valid and potentially skip their script verification (0 to verify all, default: 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90, testnet: 00000000000128796ee387cf110ccb9d2f36cffaf7f73079c995377c65ac0dcc)
-conf= Specify configuration file (default: bitcoin.conf)
-datadir= Specify data directory
-dbcache= Set database cache size in megabytes (4 to 16384, default: 300)
-loadblock= Imports blocks from external blk000??.dat file on startup
-maxorphantx= Keep at most unconnectable transactions in memory (default: 100)
-maxmempool= Keep the transaction memory pool below megabytes (default: 300)
-mempoolexpiry= Do not keep transactions in the mempool longer than hours (default: 336)
-blockreconstructionextratxn= Extra transactions to keep in memory for compact block reconstructions (default: 100)
-par= Set the number of script verification threads (-2 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
-pid= Specify pid file (default:
-prune= Reduce storage requirements by enabling pruning (deleting) of old blocks. This allows the pruneblockchain RPC to be called to delete specific blocks, and enables automatic pruning of old blocks if a target size in MiB is provided. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, >550 = automatically prune block files to stay under the specified target size in MiB)
-reindex-chainstate Rebuild chain state from the currently indexed blocks
-reindex Rebuild chain state and block index from the blk*.dat files on disk
-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= Add a node to connect to and attempt to keep the connection open
-banscore= Threshold for disconnecting misbehaving peers (default: 100)
-bantime= Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
-bind= Bind to given address and always listen on it. Use [host]:port notation for IPv6
-connect= Connect only to the specified node(s); -noconnect or -connect=0 alone to disable automatic connections
-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/-noconnect)
-externalip= 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/-noconnect)
-listenonion Automatically create Tor hidden service (default: 1)
-maxconnections= Maintain at most connections to peers (default: 125)
-maxreceivebuffer= Maximum per-connection receive buffer, *1000 bytes (default: 5000)
-maxsendbuffer= Maximum per-connection send buffer, *1000 bytes (default: 1000)
-maxtimeadjustment Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: 4200 seconds)
-onion= Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
-onlynet= Only connect to nodes in network (ipv4, ipv6 or onion)
-permitbaremultisig Relay non-P2SH multisig (default: 1)
-peerbloomfilters Support filtering of blocks and transaction with bloom filters (default: 1)
-port= Listen for connections on (default: 8333 or testnet: 18333)
-proxy= Connect through SOCKS5 proxy
-proxyrandomize Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1)
-rpcserialversion Sets the serialization of raw transaction or block hex returned in non-verbose mode, non-segwit(0) or segwit(1) (default: 1)
-seednode= Connect to a node to retrieve peer addresses, and disconnect
-timeout= Specify connection timeout in milliseconds (minimum: 1, default: 5000)
-torcontrol=: Tor control port to use if onion listening enabled (default:
-torpassword= Tor control port password (default: empty)
-upnp= Use UPnP to map the listening port (default: 0)
-whitebind= Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
-whitelist= Whitelist peers connecting from the given IP address (e.g. or CIDR notated network (e.g. 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
-whitelistrelay Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: 1)
-whitelistforcerelay Force relay of transactions from whitelisted peers even if they violate local relay policy (default: 1)
-maxuploadtarget= Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)

Wallet options:
-disablewallet Do not load the wallet and disable wallet RPC calls
-keypool= Set key pool size to (default: 100)
-fallbackfee= A fee rate (in BTC/kB) that will be used when fee estimation has insufficient data (default: 0.0002)
-mintxfee= Fees (in BTC/kB) smaller than this are considered zero fee for transaction creation (default: 0.00001)
-paytxfee= 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 on startup
-spendzeroconfchange Spend unconfirmed change when sending transactions (default: 1)
-txconfirmtarget= If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 6)
-usehd Use hierarchical deterministic key generation (HD) after BIP32. Only has effect during wallet creation/first start (default: 1)
-walletrbf Send transactions with full-RBF opt-in enabled (default: 0)
-upgradewallet Upgrade wallet to latest format on startup
-wallet= Specify wallet file (within data directory) (default: wallet.dat)
-walletbroadcast Make the wallet broadcast transactions (default: 1)
-walletnotify= Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
-zapwallettxes= 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)

ZeroMQ notification options:
-zmqpubhashblock= Enable publish hash block in
-zmqpubhashtx= Enable publish hash transaction in
-zmqpubrawblock= Enable publish raw block in
-zmqpubrawtx= Enable publish raw transaction in

Debugging/Testing options:
-uacomment= Append comment to the user agent string
-debug= Output debugging information (default: 0, supplying is optional). If is not supplied or if = 1, output all debugging information. can be: addrman, alert, bench, cmpctblock, coindb, db, http, libevent, lock, mempool, mempoolrej, net, proxy, prune, rand, reindex, rpc, selectcoins, tor, zmq, qt.
-help-debug Show all debugging options (usage: --help -help-debug)
-logips Include IP addresses in debug output (default: 0)
-logtimestamps Prepend debug output with timestamp (default: 1)
-minrelaytxfee= Fees (in BTC/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.00001)
-maxtxfee= Maximum total fees (in BTC) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: 0.10)
-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)

Chain selection options:
-testnet Use the test chain

Node relay options:
-bytespersigop Equivalent bytes per sigop in transactions for relay and mining (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)
-mempoolreplacement Enable transaction replacement in the memory pool (default: 1)

Block creation options:
-blockmaxweight= Set maximum BIP141 block weight (default: 3000000)
-blockmaxsize= Set maximum block size in bytes (default: 750000)
-blockprioritysize= Set maximum size of high-priority/low-fee transactions in bytes (default: 0)
-blockmintxfee= Set lowest fee rate (in BTC/kB) for transactions to be included in block creation. (default: 0.00001)

RPC server options:
-server Accept command line and JSON-RPC commands
-rest Accept public REST requests (default: 0)
-rpcbind= 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)
-rpccookiefile= Location of the auth cookie (default: data dir)
-rpcuser= Username for JSON-RPC connections
-rpcpassword= Password for JSON-RPC connections
-rpcauth= Username and hashed password for JSON-RPC connections. The field comes in the format: :$. A canonical python script is included in share/rpcuser. The client then connects normally using the rpcuser=/rpcpassword= pair of arguments. This option can be specified multiple times
-rpcport= Listen for JSON-RPC connections on (default: 8332 or testnet: 18332)
-rpcallowip= Allow JSON-RPC connections from specified source. Valid for are a single IP (e.g., a network/netmask (e.g. or a network/CIDR (e.g. This option can be specified multiple times
-rpcthreads= Set the number of threads to service RPC calls (default: 4)

UI Options:
-choosedatadir Choose data directory on startup (default: 0)
-lang= Set language, for example "de_DE" (default: system locale)
-min Start minimized
-rootcertificates= Set SSL root certificates for payment request (default: -system-)
-splash Show splash screen on startup (default: 1)
-resetguisettings Reset all settings changed in 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. A user-friendly configuration file generator is available here. 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

Copied from

## 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 # Run a regression test network
#regtest=0 # Connect via a SOCKS5 proxy
#proxy= # Bind to given address and always listen on it. Use [host]:port notation for IPv6
#bind= # Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
#whitebind= ##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode= ##
## addnode will connect you to and tell you about the ##
## nodes connected to 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 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= # Alternatively use as many connect= settings as you like to connect ONLY to specific peers
#connect= # Listening mode, enabled by default except when 'connect' is being used
#listen=1 # Maximum number of inbound+outbound connections.
#maxconnections= #
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
# # server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands
#server=0 # 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)
#rpcbind= # If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
# is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used
# when the server and client are run as the same user.
# If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
# method(DEPRECATED) is to set this pair for the server and client:
# The second method `rpcauth` can be added to server startup argument. It is set at intialization time
# using the output from the script in share/rpcuser/ after providing a username:
# ./share/rpcuser/ alice
# String to be appended to bitcoin.conf:
# rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
# Your password:
# On client-side, you add the normal user/password pair to send commands:
# You can even add multiple entries of these to the server conf file, and client can use any of them:
# rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99 # How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established. #rpcclienttimeout=30 # By default, only RPC connections from localhost are allowed.
# Specify as many rpcallowip= settings as you like to allow connections from other hosts,
# either as a single IPv4/IPv6 or with a subnet specification. # 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. # server=1 tells Bitcoin-Qt to accept JSON-RPC commands.
# it is also read by bitcoind to determine if RPC should be enabled #rpcallowip=
#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96 # 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= # Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).
# This setting is over-ridden by the -paytxfee option.
#txconfirmtarget=n # Miscellaneous options # 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 # Enable pruning to reduce storage requirements by deleting old blocks. # This mode is incompatible with -txindex and -rescan.
# 0 = default (no pruning).
# 1 = allows manual pruning via RPC.
# >=550 = target to stay under in MiB. #prune=550 # User interface options # Start Bitcoin minimized
#min=1 # Minimize to the system tray



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

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.



See Also

обмен биткоин на вебмани.

Blah: trying p2pool soon p2pool windows setup

Provided by: bitcoind_0.3.24~dfsg-1_i386
 bitcoin.conf - bitcoin configuration file 
 All command-line options (except for '-datadir' and '-conf') may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file. The configuration file is a list of 'setting=value' pairs, one per line, with optional comments starting with the '#' character. The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, bitcoind(1) will look for a file named bitcoin.conf(5) 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. 
 bitcoin.conf should be located in $HOME/.bitcoin 
 testnet=['1'|'0'] Enable or disable run on the test network instead of the real *bitcoin* network. proxy='' Connect via a socks4 proxy. addnode='' Use as many *addnode=* settings as you like to connect to specific peers. connect='' Use as many *connect=* settings as you like to connect ONLY to specific peers. noirc=['1'|'0'] Use or Do not use Internet Relay Chat ( #bitcoin channel) to find other peers. maxconnections='value' Maximum number of inbound+outbound connections. 
 server=['1'|'0'] Tells *bitcoin* to accept or not accept JSON-RPC commands. rpcuser='username' You must set *rpcuser* to secure the JSON-RPC api. rpcpassword='password' You must set *rpcpassword* to secure the JSON-RPC api. rpctimeout='30' How many seconds *bitcoin* will wait for a complete RPC HTTP request, after the HTTP connection is established. rpcallowip='192.168.1.*' By default, only RPC connections from localhost are allowed. Specify as many *rpcallowip=* settings as you like to allow connections from other hosts (and you may use * as a wildcard character). rpcport='8332' Listen for RPC connections on this TCP port. rpcconnect='' You can use *bitcoin* or *bitcoind(1)* to send commands to *bitcoin*/*bitcoind(1)* running on another host using this option. rpcssl='1' Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate with *bitcoin* '-server' or *bitcoind(1)*. Example of OpenSSL settings used when *rpcssl*='1': rpcsslciphers='TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH' rpcsslcertificatechainfile='server.cert' rpcsslprivatekeyfile='server.pem' MISCELLANEOUS OPTIONS gen=['0'|'1'] Enable or disable attempt to generate bitcoins. 4way=['0'|'1'] Enable or disable use SSE instructions to try to generate bitcoins faster. keypool='100' Pre-generate this many public/private key pairs, so wallet backups will be valid for both prior transactions and several dozen future transactions. paytxfee='0.00' 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. allowreceivebyip='1' Allow direct connections for the 'pay via IP address' feature. USER INTERFACE OPTIONS min=['0'|'1'] Enable or disable start bitcoind minimized. minimizetotray=['0'|'1'] Enable or disable minimize to the system tray. 
 This manual page was written by Micah Anderson  for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.
обмен биткоин кэш на рубли.

P2Pool - The official homepage of the P2Pool software

Bitcoin Core initial synchronization will take time and download a lot of data. You should make sure that you have enough bandwidth and storage for the full block chain size (over 145GB). If you have a good Internet connection, you can help strengthen the network by keeping your PC running with Bitcoin Core and port 8333 open. Read the full node guide for details.

Bitcoin Core is a community-driven free software project, released under the MIT license.

сколько в биткоине нулей.

Global Bitcoin Nodes Distribution - Bitnodes

С момента появления технологии группового майнинга прошло уже более четырех лет. За это время появлялись и закрывались сотни пулов по добыче Bitcoin и других криптовалют, изобретались новые системы распределения награды, совершенствовались протоколы связи и переключение между форками. Несколько раз возникали ситуации, когда один пул или организация приближались к пределу в 50% общего хэшрейта сети и даже преодолевали его.

На сегодня ситуация выглядит более стабильно, и ни один из крупных игроков рынка майнинга не имеет решающего преимущества. Ниже представлен список крупнейших пулов для Биткоина.

Китайская четверка

В добыче самой популярной криптовалюты самая жесткая конкуренция, в которой неоспоримое превосходство уже долго удерживают китайские пулы. С большим отрывом рейтинг возглавляет пятерка самых крупных "шахт", причем четыре из них находятся в Китае:

F2Pool (Discus fish)

F2Pool, также известный как Discus Fish (аквариумная рыбка дискус, 七彩神仙魚). В среднем удерживает около 20% хэшрейта сети. Основан 5 мая 2013 года. Единственный из лидеров, у которого основной системой оплаты выбрана PPS с комиссией 4%. Для пользователей, находящихся за фаерволлами, включен майнинговый протокол Stratum по наиболее массовым портам TCP – 80 и 25. Стандартный порт подключения – 3333.

На этом пуле можно майнить Litecoin и действует merged mining некоторых альткоинов.

Еще одна особенность F2Pool в том, что он настойчиво рекомендует выводить средства как можно быстрее. Монеты, задержавшиеся на балансе дольше 90 дней, считаются "пожертвованиями" в пользу пула и могут быть списаны без дальнейших предупреждений.


За первое место с переменным успехом борется AntPool. Сейчас у него в среднем 18% майнинговых мощностей. Пул принадлежит Bitmaintech, крупнейшему китайскому производителю оборудования для майнинга. На нем работает сервис облачного майнинга Hashnest и тестируются продукты компании. Основной метод начисления награды – PPLNS без комиссии, также имеется PPS с 2.5%.

У Antpool есть и оригинальные услуги – это соло-майнинг для любителей играть на удачу, а также узел P2Pool – для тех, кто хочет поддержать децентрализацию сети.

Присутствует интерфейс на русском языке, но пока он оставляет желать лучшего. Подключиться к пулу можно по стандартному порту: или по общеизвестным портам 443 или 25.

BTC China

Пул BTCChina с 10-12% сети занимает четвертое место в общем рейтинге и третье в Китае. Этот Биткоин пул принадлежит одноименной китайской бирже, одной из крупнейших в мире. Таким образом она расширяет спектр своих услуг, а также проводит собственные транзакции, не полагаясь на сторонние сервисы. Пул открыт только для клиентов биржи, кроме того располагает значительными собственными мощностями. К сожалению, его интерфейс очень слабо переведен даже на английский, не говоря уже о других языках. Поэтому, информация по нему крайне ограничена.

BW pool

Замыкает четверку с 7-9% мощностей. Есть частичный перевод на русский язык, гораздо более корявый, чем у Antpool. Основная система начисления – PPLNS без комиссии.

Строка для подключения по стандартному порту - stratum+tcp://

В итоге, четыре крупнейших китайских пула "держат" 55-60% хэшрейта сети, что не может не вызывать беспокойства в сообществе.

Другие интересные пулы

Дальнейшее "ранжирование" пулов бесполезно, так как ни один из них, как правило, не выходит за 5% от мощности сети. Влияние фактора удачи и миграция пользователей постоянно перетасовывают позиции. Но эти пулы не менее известны и надежны, а по удобству и предлагаемым наборам услуг ничем не уступают лидерам.

Slush, он же Slush - чешский пул, первый на рынке – он работает с декабря 2010 года! Так как Slush не старался сделать проект коммерчески выгодным, за прошедшие годы его доля значительно сократилась. Но пул никогда не подводил пользователей и сохраняет отличную репутацию. Сейчас его доля – около 5%.

Этот пул применяет собственную систему вознаграждения - Scoring Hash Rate, которая имеет свойства Пропорциональной и PPLNS. Комиссия для майнеров очень долго остается неизменной и составляет 2%.


Eligius контролирует 3-5% мощностей. Пул назван в честь католического святого Элигия, ответственного за чеканку монет. Единственный крупный пул, который не требует никакой идентификации пользователя и создания аккаунта – в качестве логина для подключения "рабочих" используется адрес Биткоин, на который и отправляются выплаты. Мониторинг также доступен по адресу.

Для расчета выплаты майнерам используется система CPPSRB – модификация PPS, снимающая риски с оператора пула, поэтому комиссии нет. Доступен также совместный майнинг NMC, для которого требуется дополнительная настройка. Несколько устаревшая статья об этом пуле.

Строка для подключения stratum+tcp:// – всего год назад безусловный лидер майнинга Биткоина, неоднократно бравший планку в 50% хэшрейта сети, сегодня довольствуется скромными 2-3%. Принадлежит бирже Ранее на этом пуле работал одноименный сервис облачного майнинга, остановленный в начале года. Практически все собственное оборудование состояло из майнеров от Bitfury, теперь уже устаревших. Этого гиганта подкосила как остановка облака, так и создание Bitfury собственного пула - теперь новое оборудование уходит туда.

Однако, пул продолжает работу. На нем действует merged mining NMC и мультипул, предлагающий большой выбор цифровых валют на алгоритме Scrypt. Основная система начисления награды – PPLNS без комиссии.


Все остальные пулы обычно добывают в сутки не более 1-2 блоков. Из них можно отметить Bitminter – старый стабильный пул с хорошей репутацией, работает с 2011 года. В основном, держится на старых майнерах, также многие используют его в качестве резервного. На нем применяется аутентификация пользователей по OpenID. Основная система начисления – PPLNS с комиссией 1%. Есть совместный майнинг Namecoin. Используется стандартный порт Стратума 3333, а также 443 и 5050.

На публику не работаем

Несколько крупных пулов, имеющих суммарную мощность около 25% от общего хэшрейта сети Биткоина, недоступны для обычных майнеров. Они работают только на узкий круг инвесторов.


Первым из них, и третьим в общем рейтинге, идет Bitfury – единственный пул в пятерке лидеров, не находящийся в Китае. Он держит 15-17% сети только за счет собственных мощностей – для майнеров "со стороны" подключение закрыто. Пул принадлежит крупному производителю оборудования – компании Bitfury, которая в основном изготавливает его для собственных датацентров, расположенных в Исландии и Грузии. Кроме того, Bitfury – один из лидеров по объему полученных в течение года инвестиций, превышающих 60 миллионов долларов. Все эти средства направляются на новые разработки, а также строительство и поддержку датацентров.

KnC pool

Пул KnCMiner принадлежит одноименному шведскому производителю ASIC. Большая часть его мощностей находится в Европе. Работу пула обеспечивает собственное оборудование компании и ее сервис облачного майнинга. Публичного доступа к пулу нет. Средний хэшрейт около 5% сети.

21 Inc

Еще один таинственный пул принадлежит компании 21 Inc, которая, по слухам, финансировалась крупными американскими венчурными фондами и располагается в Кремниевой долине, со всеми вытекающими. Сейчас ее пулу принадлежит около 4% сети. Компания и пул не публичны, работают только на своих инвесторов.

bitcoinaliens регистрация.

<< Go back to the previous page

Похожие статьи