| api | ||
| config | ||
| lib | ||
| test | ||
| .coveralls.yml | ||
| .gitignore | ||
| .jshintrc | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| gulpfile.js | ||
| index.js | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
Prerequisites
-
Node.js v0.10.0-v0.12.x - Download and Install Node.js.
-
NPM - Node.js package manager, should be automatically installed when you get node.js.
-
Fully-synced Bitcoin Core - Download and Install Bitcoin Core
bitcore-node needs a trusted Bitcoin Core instance to run. It will connect to it
through the RPC API and bitcoin peer-to-peer protocol.
Configure Bitcoin Core to listen to RPC calls and set txindex to true.
The easiest way to do this is by copying ./config/bitcoin.conf to your
bitcoin data directory (usually ~/.bitcoin on Linux, %appdata%\Bitcoin\ on Windows,
or ~/Library/Application Support/Bitcoin on Mac OS X).
Bitcoin Core must be running and fully synced before running bitcore-node. We're planning
to remove the need of running Bitcoin Core separately. More info.
Quick Install
Check the Prerequisites section above before installing.
To install bitcore-node, clone the main repository:
$ git clone https://github.com/bitpay/bitcore-node && cd bitcore-node
Install dependencies:
$ npm install
Run the main application:
$ npm start
Then open a browser and go to:
http://localhost:8080
Please note that the app will need to sync its internal database
with the blockchain state, which will take some time. You can check
sync progress at http://localhost:8080/v1/node.
Configuration
bitcore-node is configured using yaml files.
The application defaults are in the api/config/ folder.
To run the app with different configurations, simply do:
# to start a testnet instance
NODE_ENV=testnet npm start
# to start a livenet instance
NODE_ENV=livenet npm start
# start a custom configuration instance (will usee foo.yml)
NODE_ENV=foo npm start
$
A sample configuration file would contain:
# Sample configuration file with defaults for livenet
BitcoreHTTP:
port: 8080 # http api port
logging: true # enables request logging
BitcoreNode:
LevelUp: ./db # path to database location
network: livenet # bitcoin network (livenet, testnet)
NetworkMonitor:
host: localhost # p2p host
port: 8333 # p2p port
RPC:
host: 127.0.0.1 # rpc ip
port: 8332 # rpc port
user: user # rpc username
pass: password # rpc password
protocol: http #http, https
#rejectUnauthorized: false
#disableAgent: true
Synchronization
The initial synchronization process scans the blockchain from Bitcoin Core
to update addresses and balances. bitcore-node needs exactly one
trusted bitcoind node to function.
There are plans to expand this to more than one.
Bitcoin core must have finished downloading the blockchain before running bitcore-node.
While bitcore-node is synchronizing the web API can be queried
(the sync process is embedded in the webserver), but there will be missing data
and incorrect balances for addresses. The 'sync' status is shown at the /v1/node endpoint.
While synchronizing the blockchain, bitcore-node listens for new blocks and
transactions relayed by the bitcoin network. Those are also stored on bitcore-node's database.
In case bitcore-node is turned off for a period of time, it will automatically catch up on restart.
Database
To store the blockchain and address information indexes, LevelDB is used.
By default these are stored on the project's root folder, under the name db/ for livenet and
tesnet-db for testnet. This can be changed using the configuration files.
Development
To run bitcore-node in development:
$ NODE_ENV=development gulp
To run the tests
$ gulp test
API
By default, bitcore-node provides a REST API at /v1.
The end-points are detailed in the following document (please review and comment):
https://docs.google.com/document/d/1rXQdfr8VDBSzheEn0KynnCKCMB0oAsMunkjdG4aY-18
License
(The MIT License)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
