:blue_book: TREZOR address/account balance backend . https://github.com/trezor/blockbook
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
omotenashicoin-project 2d430aa80b added MTNS 1 month ago
api Alter logging of a possible db inconsitency in addresses column 4 days ago
bchain added MTNS 3 days ago
build Add fiat rates functionality (#316) 2 months ago
common Automatically check for UTXO inconsitencies 4 days ago
configs added MTNS 3 days ago
contrib/scripts Use "#!/usr/bin/env bash" in shebangs instead of "#!/bin/bash" 8 months ago
db Fix packBlockInfo 4 days ago
docs added MTNS 3 days ago
fiat Fix formatting and linting errors 1 month ago
server Insert utxos in the right order in disconnect block 4 days ago
static test-websocket.html: remove debug log :) 1 month ago
tests added MTNS 3 days ago
.gitignore Support Polis (#118) 10 months ago
.gitlab-ci.yml Add backend-deploy-and-test CI job for Namecoin 6 months ago
CONTRIBUTING.md Update documentation to match version 0.2.0 1 year ago
COPYING Add license file 1 year ago
Gopkg.lock Fix litecoin address parsing issue #254 4 months ago
Gopkg.toml Fix go dependencies 1 year ago
Makefile Build makes sure that images are rebuilt after change of docker defs 1 year ago
README.md Update documentation 9 months ago
blockbook.go Automatically check for UTXO inconsitencies 4 days ago


Go Report Card


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

Build and installation instructions

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.

Implemented coins

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.

Common issues when running Blockbook or implementing additional coins

Out of memory when doing initial synchronization

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.

Error internalState: database is in inconsistent state and cannot be used

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.

Running on Ubuntu

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.

My coin implementation is reporting parse errors when importing blockchain

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.

Data storage in RocksDB

Blockbook stores data the key-value store RocksDB. Database format is described here.


Blockbook API is described here.