Blockwatch Tezos Indexer

© 2020-2022 Blockwatch Data Inc., All rights reserved.

All-in-one zero-conf blockchain indexer for Tezos. A fast, convenient and resource friendly way to gain tactical insights and build dapps on top of Tezos. Supported by Blockwatch Data, Pro version available on request.

For support, talk to us on Twitter or Discord.

Core Features

• indexes and cross-checks full on-chain state
• feature-rich REST API with objects, bulk tables and time-series
• supports protocols up to Jakarta (v013)
• auto-detects and locks Tezos network (never mixes data from different networks)
• indexes all accounts and smart-contracts (including genesis data)
• follows chain reorgs as they are resolved
• can passively monitor for new blocks
• self-heals broken node connections (retries until node RPC comes back up)
• API supports CORS and HTTP caching
• high-performance embedded data-store
• flexible in-memory caching for fast queries
• automatic database backups/snapshots
• configurable HTTP request rate-limiter
• flexible metadata support

Supported indexes and data tables

• blocks: all blocks including orphans, indexed by hash and height
• operations: all on-chain operations including contract call data, indexed by hash ( endorsements are split into separate table, only available in full mode)
• accounts: running account details like most recent balances, indexed by address
• balances: end-of-block balance history for all addresses
• contracts: running smart contract details, code and initial storage
• flows: complete list of balance, freezer and delegation balance updates
• chain: running blockchain totals
• supply: running supply totals
• bigmap: bigmap smart contract storage index
• rights: compact representations of assigned and used baking and endorsing rights
• elections, votes, proposals and ballots capturing all on-chain governance activities
• snapshots: balances of active delegates & delegators at all snapshot blocks
• baker income: per-cycle statistics on baker income, efficiency, etc
• metadata: standardized and custom account/token metadata
• constants: global constants (e.g. smart contract code/type macros to lower contract size and reuse common features)
• storage: separate smart contract storage updates to decrease operation table cache pressure

Starting v12 we are no longer supporting baker rights, snapshots, income and governance data as well as flows (use balances instead).

Operation modes

• Light (default) light-weight mode without consensus and governance data (CLI: --light)
• Full regular operation mode that builds all indexes (CLI: --full)
• Validate state validation mode for checking accounts and balances each block/cycle (CLI: --validate)

Light mode dramatically reduces our maintenance costs for TzIndex and is best suited for dapps where access to baking-related data is not necessary. Light mode saves roughly ~50% storage costs and ~50% indexing time while still keeping all data required for Dapps.

Validate mode works in combination with full and light mode. At each block it checks balances and states of all touched accounts against a Tezos archive node before any change is written to the database. At the end of each cycle, all known accounts in the indexer database are checked as well. This ensures 100% consistency although at the cost of a reduction in indexing speed.

Requirements

• Storage: 38GB (full Mainnet index, June 2022), 32G (light mode)
• RAM: 8-64GB (configurable, use more memory for better query latency)
• CPU: 2+ cores (configurable, use more for better query parallelism)
• Tezos node in archive mode

Runs against any Tezos Archive Node (also full nodes when cycle 0 history is not yet pruned). This can be a local node or one of the public Tezos RPC nodes on the Internet. Note that syncing from public nodes over the Internet works but may be slow.

IMPORTANT: WHEN USING OCTEZ V12+ YOU MUST RUN YOUR ARCHIVE NODE WITH --metadata-size-limit unlimited

Requires access to the following Tezos RPC calls

/chains/main/blocks/{blockid}
/chains/main/blocks/{blockid}/helpers/baking_rights (full mode only)
/chains/main/blocks/{blockid}/helpers/endorsing_rights (full mode only)
/chains/main/blocks/{blockid}/context/selected_snapshot (Ithaca+ full mode only)
/chains/main/blocks/{blockid}/context/raw/json/cycle/{cycle} (full mode only)
/chains/main/blocks/{blockid}/context/constants
/chains/main/blocks/head/header
/monitor/heads/main (optional)
/chains/main/blocks/{blockid}/context/contract/{address} (validate mode only)
/chains/main/blocks/{blockid}/context/delegates/{address} (validate mode only)

How to build

The contained Makefile supports local and Docker builds. For local builds you need a recent Golang distribution installed on your system.

# build a binary for your OS
make build

# or directly with Go
go build tzindex.go

# build docker images
make image

How to run

tzindex aims to be zero-conf and comes with sane defaults. All you need to do is point it to the RPC endpoint of a running Tezos node.

tzindex run --rpcurl tezos-node

If you prefer running from docker, check out the docker directory. Official images are available for the indexer and frontend (note the frontend may not support advanced features of new protocols). You can run both, the indexer and the frontend in local Docker containers and have them connect to your Tezos node in a third container. Make sure all containers are connected to the same Docker network or if you choose different networks that they are known. Docker port forwarding on Linux usually works, on OSX its broken.

Configuration

Config file

On start-up tzindex tries loading its config from the config.json file in the current directory. You may override this name either on the command line using -c myconf.json or by setting the environment variable TZ_CONFIG_FILE=/some/path/myconf.json

Config file sections

rpc      - configures RPC connection to the Tezos node
crawler  - configures the blockchain crawl logic
database - configures the embedded database
server   - configures the built-in HTTP API server
logging  - configures logging for all subsystems

See the default config.json in the docker subfolder for a detailed list of all settings.

Environment variables

Env variables allow you to override settings from the config file or even specify all configuration settings in the process environment. This makes it easy to manage configuration in Docker and friends. Env variables are all uppercase, start with TZ and use an underscore _ as separator between sub-topics.

# in config.json
{ "rpc": { "host" : "127.0.0.1" }}

# same as env variable
TZ_RPC_HOST=127.0.0.1

Command line arguments

A few global settings can only be controlled via cli arguments:

Usage:
  tzindex [command]

Available Commands:
  help        Help about any command
  run         Run as service
  version     Print the version number of tzindex

Flags:
  -c, --config string          config file
      --cpus int               max number of logical CPU cores to use (default: all) (default -1)
  -p, --dbpath path            database path
      --gogc int               trigger GC when used mem grows by N percent (default 20)
  -h, --help                   help for tzindex
      --insecure               disable RPC TLS certificate checks (not recommended)
      --norpc                  disable RPC client
      --notls                  disable RPC TLS support (use http)
      --profile-block string   write blocking events to file
      --profile-cpu string     write cpu profile to file
      --profile-mutex string   write mutex contention samples to file
      --profile-rate int       block/mutex profiling rate in fractions of 100 (e.g. 100 == 1%) (default 100)
      --rpcpass string         RPC password
      --rpcurl string          RPC url (default "http://127.0.0.1:8732")
      --rpcuser string         RPC username
  -t, --test                   test configuration and exit
      --v                      be verbose
      --vv                     debug mode
      --vvv                    trace mode

The main tzindex run command has a few additional options

Usage:
  tzindex run [flags]

Flags:
      --enable-cors   enable API CORS support
  -h, --help          help for run
      --noapi         disable API server
      --noindex       disable indexing
      --nomonitor     disable block monitor
      --stop height   stop indexing after height
      --unsafe        disable fsync for fast ingest (DANGEROUS! data will be lost on crashes)
      --validate      validate account balances

Global Flags:
  -c, --config string          config file
      --cpus int               max number of logical CPU cores to use (default: all) (default -1)
  -p, --dbpath path            database path
      --gogc int               trigger GC when used mem grows by N percent (default 20)
      --insecure               disable RPC TLS certificate checks (not recommended)
      --light                  light mode (default, skips endorsement, baker and governance data)
      --full                   full mode (index all data)
      --norpc                  disable RPC client
      --notls                  disable RPC TLS support (use http)
      --profile-block string   write blocking events to file
      --profile-cpu string     write cpu profile to file
      --profile-mutex string   write mutex contention samples to file
      --profile-rate int       block/mutex profiling rate in fractions of 100 (e.g. 100 == 1%) (default 100)
      --rpcpass string         RPC password
      --rpcurl string          RPC url (default "http://127.0.0.1:8732")
      --rpcuser string         RPC username
  -t, --test                   test configuration and exit
      --v                      be verbose
      --vv                     debug mode
      --vvv                    trace mode

License

This Software is available under two different licenses, the open-source MIT license with limited support / best-effort updates and a PRO license with professional support and scheduled updates. The professional license is meant for businesses such as dapps, marketplaces, staking services, wallet providers, exchanges, asset issuers, and auditors who would like to use this software for their internal operations or bundle it with their commercial services.

The PRO licenses helps us pay for software updates and maintenance and operate the free community services on tzstats.com.

The following table may help you pick the right license for your intended use-case. If in doubt, send an email to [email protected] and we'll get back to you.