Rescanner

The rescanner fills in block gaps — blocks that were missed during normal indexing due to RPC downtime, rate limiting, or service restarts. It's configured via config.rescanner.yaml.

When Is It Needed?

The rescanner is primarily used for Solana, where the high block production rate makes it likely that some blocks are missed during indexing. It can also be used for any chain where you need to ensure complete data coverage.

Configuration

redis:
  address: "redis:6379"
  password: "6s9H5G9o4p5Fz25K9RyWd6eOryU8nQ"

nats:
  url: nats://nats-server_fystack:4222

consul:
  address: consul:8500

networks:
  SOL_DEVNET:
    enabled: true
    id: "2e89cd02-8585-47b3-90e3-a92185f6ca5f"
    name: "Solana devnet"
    rpcnodes:
      - url: "https://api.devnet.solana.com"

  SOL_MAINNET:
    enabled: false
    id: "4b5bf0f9-5b89-45fb-8166-784ff1326b59"
    name: "Solana mainnet"
    rpcnodes:
      - url: "https://api.mainnet-beta.solana.com"

Key Fields

Field	Description
networks.*.enabled	Whether to rescan this network
networks.*.id	Must match the network UUID from the Fystack UI
networks.*.rpcnodes	RPC endpoints to use for rescanning

info

The network key (e.g., SOL_DEVNET) must match the internal_code used in config.yaml and config.indexer.yaml.