1bf564d963
In order to avoid prior situations of stalled syncs due to outdated peer height data, we now update block heights up peers in real-time as we learn of their announced blocks. Updates happen when: * A peer sends us an orphan block. We update based on the height embedded in the scriptSig for the coinbase tx * When a peer sends us an inv for a block we already know of * When peers announce new blocks. Subsequent announcements that lost the announcement race are recognized and peer heights are updated accordingly Additionally, the `getpeerinfo` command has been modified to include both the starting height, and current height of connected peers. Docs have been updated with `getpeerinfo` extension. |
||
---|---|---|
.. | ||
code_contribution_guidelines.md | ||
configure_peer_server_listen_interfaces.md | ||
configure_rpc_server_listen_interfaces.md | ||
configuring_tor.md | ||
default_ports.md | ||
json_rpc_api.md | ||
README.md | ||
using_bootstrap_dat.md |
Table of Contents
### 1. About btcd is a full node bitcoin implementation written in [Go](http://golang.org), licensed under the [copyfree](http://www.copyfree.org) ISC License.This project is currently under active development and is in a Beta state. It is extremely stable and has been in production use for over 6 months as of May 2014, however there are still a couple of major features we want to add before we come out of beta.
It currently properly downloads, validates, and serves the block chain using the exact rules (including bugs) for block acceptance as the reference implementation, bitcoind. We have taken great care to avoid btcd causing a fork to the block chain. It passes all of the 'official' block acceptance tests.
It also properly relays newly mined blocks, maintains a transaction pool, and relays individual transactions that have not yet made it into a block. It ensures all individual transactions admitted to the pool follow the rules required into the block chain and also includes the vast majority of the more strict checks which filter transactions based on miner requirements ("standard" transactions).
One key difference between btcd and bitcoind is that btcd does NOT include wallet functionality and this was a very intentional design decision. See the blog entry for more details. This means you can't actually make or receive payments directly with btcd. That functionality is provided by the btcwallet and btcgui projects which are both under active development.
### 2. Getting Started **2.1 Installation**The first step is to install btcd. See one of the following sections for details on how to install on the supported operating systems.
**2.1.1 Windows Installation**- Install the MSI available at: https://github.com/btcsuite/btcd/releases
- Launch btcd from the Start Menu
- Install Go according to the installation instructions here: http://golang.org/doc/install
- Run the following command to ensure your Go version is at least version 1.2:
$ go version
- Run the following command to obtain btcd, its dependencies, and install it:
$ go get github.com/btcsuite/btcd/...
- To upgrade, run the following command:
$ go get -u github.com/btcsuite/btcd/...
- To upgrade, run the following command:
- Run btcd:
$ btcd
btcd has a number of configuration
options, which can be viewed by running: $ btcd --help
.
btcctl is a command line utility that can be used to both control and query btcd via RPC. btcd does not enable its RPC server by default; You must configure at minimum both an RPC username and password:
- btcd.conf configuration file
[Application Options]
rpcuser=myuser
rpcpass=SomeDecentp4ssw0rd
- btcctl.conf configuration file
[Application Options]
rpcuser=myuser
rpcpass=SomeDecentp4ssw0rd
For a list of available options, run: $ btcctl --help
btcd supports both the `getwork` and `getblocktemplate` RPCs although the `getwork` RPC is deprecated and will likely be removed in a future release.
1. Add the payment addresses with the miningaddr
option.
[Application Options]
rpcuser=myuser
rpcpass=SomeDecentp4ssw0rd
miningaddr=12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX
miningaddr=1M83ju3EChKYyysmM2FXtLNftbacagd8FR
2. Add btcd's RPC TLS certificate to system Certificate Authority list.
cgminer
uses curl to fetch data from the RPC server.
Since curl validates the certificate by default, we must install the btcd
RPC
certificate into the default system Certificate Authority list.
Ubuntu
- Copy rpc.cert to /usr/share/ca-certificates:
# cp /home/user/.btcd/rpc.cert /usr/share/ca-certificates/btcd.crt
- Add btcd.crt to /etc/ca-certificates.conf:
# echo btcd.crt >> /etc/ca-certificates.conf
- Update the CA certificate list:
# update-ca-certificates
3. Set your mining software url to use https.
$ cgminer -o https://127.0.0.1:8334 -u rpcuser -p rpcpassword
Typically btcd will run and start downloading the block chain with no extra
configuration necessary, however, there is an optional method to use a
bootstrap.dat
file that may speed up the initial block chain download process.
* [Using bootstrap.dat](https://github.com/btcsuite/btcd/tree/master/docs/using_bootstrap_dat.md) **3.1.2 Network Configuration**
* [What Ports Are Used by Default?](https://github.com/btcsuite/btcd/tree/master/docs/default_ports.md) * [How To Listen on Specific Interfaces](https://github.com/btcsuite/btcd/tree/master/docs/configure_peer_server_listen_interfaces.md) * [How To Configure RPC Server to Listen on Specific Interfaces](https://github.com/btcsuite/btcd/tree/master/docs/configure_rpc_server_listen_interfaces.md) * [Configuring btcd with Tor](https://github.com/btcsuite/btcd/tree/master/docs/configuring_tor.md) **3.1 Wallet**
btcd was intentionally developed without an integrated wallet for security reasons. Please see btcwallet for more information.
### 4. Contact **4.1 IRC*** [irc.conformal.com](irc://irc.conformal.com:+6697), port 6697, tls, channel #btcd **4.2 Mailing Lists**
* btcd: discussion of btcd and its packages. * btcd-commits: readonly mail-out of source code changes. ### 5. Developer Resources * [Code Contribution Guidelines](https://github.com/btcsuite/btcd/tree/master/docs/code_contribution_guidelines.md) * [JSON-RPC Reference](https://github.com/btcsuite/btcd/tree/master/docs/json_rpc_api.md) * [RPC Examples](https://github.com/btcsuite/btcd/tree/master/docs/json_rpc_api.md#ExampleCode) * Conformal Bitcoin-related Go Packages: * [btcrpcclient](https://github.com/btcsuite/btcrpcclient) - Implements a robust and easy to use Websocket-enabled Bitcoin JSON-RPC client * [btcjson](https://github.com/btcsuite/btcjson) - Provides an extensive API for the underlying JSON-RPC command and return values * [btcws](https://github.com/btcsuite/btcws) - Custom types for btcd websocket extension commands (registers the extension commands with [btcjson](https://github.com/btcsuite/btcjson)) * [wire](https://github.com/btcsuite/btcd/tree/master/wire) - Implements the Bitcoin wire protocol * [blockchain](https://github.com/btcsuite/btcd/tree/master/blockchain) - Implements Bitcoin block handling and chain selection rules * [txscript](https://github.com/btcsuite/btcd/tree/master/txscript) - Implements the Bitcoin transaction scripting language * [btcec](https://github.com/btcsuite/btcd/tree/master/btcec) - Implements support for the elliptic curve cryptographic functions needed for the Bitcoin scripts * [database](https://github.com/btcsuite/btcd/tree/master/database) - Provides a database interface for the Bitcoin block chain * [btcutil](https://github.com/btcsuite/btcutil) - Provides Bitcoin-specific convenience functions and types