Exonum Anchoring Service to Bitcoin

This crate implements a service for Exonum blockchain that provides
a protocol for anchoring onto the Bitcoin blockchain that utilizes the
native Bitcoin capabilities of creating multisig transactions.

For correct work of the service, the bitcoind configuration file
should contain the following settings:

# Run the node in the test network instead of the real Bitcoin network.# If you want to use the main network comment the line bellow:
testnet=1
# server=1 tells `Bitcoin-Qt` and `bitcoind` to accept JSON-RPC commands.
server=1
# Maintain a full transaction index, used by the `getrawtransaction` RPC call.# An arbitrary `bitcoind` daemon is not required to respond to a request for# information about an arbitrary transaction, thus you should uncomment the# line bellow if you want to use the daemon in an existing Exonum network.# txindex=1# Bind to the given address to listen to JSON-RPC connections.# Use [host]:port notation for IPv6.# This option can be specified multiple times (default: bind to all interfaces)#rpcbind=<addr># You must specify `rpcuser` and `rpcpassword` to secure the JSON-RPC API#rpcuser=<username>#rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593

This command generates configuration of the node and returns transaction
identifier of the generated funding_transaction.

Note!bitcoind node should have a certain amount of Bitcoins, since the initial funding
transaction will be created during the Exonum network generation.
For the testnet you may use a faucet to get some coins.

Add the lines with the new address and the corresponding private key for it. If the
public key of the node is not changed, you must use the old key for the new address.
Otherwise use a new key. After modifying the configuration file you need to
restart the node for the changes to take effect.

Note! If the transferring transaction has been lost, you need to establish a
new anchoring chain by a new funding transaction.

Licence

Exonum core library is licensed under the Apache License (Version 2.0).
See LICENSE for details.