Skip to content

Run a fast node

Note

A fast node does not generate trie data while syncing. Once a fast node is running, there is no way to switch it back to a full node — you need to re-download the snapshot data to restore full-node behaviour.

What a fast node does

  • Stores the full blockchain history on disk and answers data requests from the network.
  • Receives and validates new blocks and transactions.
  • Verifies account state with --tries-verify-mode none.

Steps

1. Obtain the node binary and config files

Download the Bitgold node binary, genesis.json, and config.toml from the official Bitgold Network distribution channel, then place them in your working directory.

2. Obtain a snapshot

Download the latest chaindata snapshot published by the Bitgold team and extract it. Your --datadir flag must point to the extracted chaindata folder.

3. Remove trie data

A fast node does not need trie data. Delete the trie state with:

./geth db delete-trie-state --datadir ./node

4. Start the fast node

./geth --tries-verify-mode none --rpc.allow-unprotected-txs \
  --cache 10000 --history.transactions 360000 \
  --datadir <datadir> --http.corsdomain '*' \
  --config ./config.toml --history.logs 576000

Note: Consider adding --history.logs.disable for better performance, but eth_getLogs will be slower.