- 克隆仓库并进入blockbook 目录
git clone https://github.com/trezor/blockbook.git
cd blockbook
-
在configs/coins 目录下找到目标币种的配置文件将币种的下载地址更新为最新版本的地址
-
编辑build/docker/bin/Dockerfile 将基础镜像 debian:9 替换为ubuntu:16.04 并将Dockerfile内 35行到38行 替换如下:
FROM debian:9FROM ubuntu:16.04
35 # install build tools
36 ENV GOPROXY=https://goproxy.cn
37 ENV GO111MODULE=on
38 RUN go get github.com/gobuffalo/packr/...
39
40 ENV GO111MODULE=""
41 # download pre-loaded depencencies
- 在blockbook 目录下执行命令编译可执行文件,以bcashsv为例:
make all-bcashsv
- 等待编译完成后会在build 目录下生成两个可安装deb 文件, 如下:
blockbook-bcashsv_0.3.4_amd64.deb
backend-bcashsv_1.0.1-satoshilabs-1_amd64.deb
- 使用上一步的deb来构建bsv blockbook 镜像 bsv-insight docker镜像
Blockbook is back-end service for Trezor wallet. Main features of Blockbook are:
- index of addresses and address balances of the connected block chain
- fast searches in the indexes
- simple blockchain explorer
- websocket, API and legacy Bitcore Insight compatible socket.io interfaces
- support of multiple coins (Bitcoin and Ethereum type), with easy extensibility for other coins
- scripts for easy creation of debian packages for backend and blockbook
Officially supported platform is Debian Linux and AMD64 architecture.
Memory and disk requirements for initial synchronization of Bitcoin mainnet are around 32 GB RAM and over 180 GB of disk space. After initial synchronization, fully synchronized instance uses about 10 GB RAM. Other coins should have lower requirements, depending on the size of their block chain. Note that fast SSD disks are highly recommended.
User installation guide is here.
Developer build guide is here.
Contribution guide is here.
Blockbook currently supports over 30 coins. The Trezor team implemented
- Bitcoin, Bitcoin Cash, Zcash, Dash, Litecoin, Bitcoin Gold, Ethereum, Ethereum Classic, Dogecoin, Namecoin, Vertcoin, DigiByte, Liquid
the rest of coins were implemented by the community.
Testnets for some coins are also supported, for example:
- Bitcoin Testnet, Bitcoin Cash Testnet, ZCash Testnet, Ethereum Testnet Ropsten
List of all implemented coins is in the registry of ports.
How to reduce memory footprint of the initial sync:
- disable rocksdb cache by parameter
-dbcache=0
, the default size is 500MB - run blockbook with parameter
-workers=1
. This disables bulk import mode, which caches a lot of data in memory (not in rocksdb cache). It will run about twice as slowly but especially for smaller blockchains it is no problem at all.
Please add your experience to this issue.
Blockbook was killed during the initial import, most commonly by OOM killer. By default, Blockbook performs the initial import in bulk import mode, which for performance reasons does not store all the data immediately to the database. If Blockbook is killed during this phase, the database is left in an inconsistent state.
See above how to reduce the memory footprint, delete the database files and run the import again.
Check this or this issue for more info.
This issue discusses how to run Blockbook on Ubuntu. If you have some additional experience with Blockbook on Ubuntu, please add it to this issue.
Your coin's block/transaction data may not be compatible with BitcoinParser
ParseBlock
/ParseTx
, which is used by default. In that case, implement your coin in a similar way we used in case of zcash and some other coins. The principle is not to parse the block/transaction data in Blockbook but instead to get parsed transactions as json from the backend.
Blockbook stores data the key-value store RocksDB. Database format is described here.
Blockbook API is described here.