For the complete documentation index, see llms.txt. This page is also available as Markdown.

Updating reporterd

Steps for updating your reporter daemon.

1. Stop your reporter.

2. Remove the old reporterd binary and Configs:

Your file paths may be different. Remember to adjust as needed to remove the files:

rm -rf ~/layer/binaries/reporter/reporterd
rm -rf ~/layer/binaries/reporter/README.md
rm ~/.layer/config/market_params.toml
rm ~/.layer/config/custom_query_config.toml
rm ~/.layer/config/pricefeed_exchange_config.toml

3. Update your .env or service file

If you are upgrading from a version before v0.2.5, update your environment variables to match the current format. Key changes:

  • ETH_RPC_URL_PRIMARY / ETH_RPC_URL_FALLBACKBRIDGE_CHAIN_RPC_NODES (comma-separated list)

  • TOKEN_BRIDGE_CONTRACT → removed; use TOKEN_BRIDGE_TEST_CONTRACT only if you need a custom bridge contract override

  • Layer connectivity → RPC_NODES and GRPC_NODES (comma-separated primary and fallbacks)

  • Reporter identity → LAYER_HOME, FROM, KEYRING_BACKEND (and KEYRING_PASSWORD_FILE when using file keyring)

  • On testnet with a non-mainnet bridge chain → add ETH_MAINNET_RPC_NODES

Compare your .env against the layer-daemons env.example for the current variable names and defaults.

Compare your .service file against the example reporterd service file and update your Environment settings to match the current variable names and defaults.

4. Download the latest reporterd release

Download reporterd v0.2.5:

5. Restart your reporter

Note: As of v0.2.5, the --chain-id flag has been removed. All other CLI flags are optional when configuration is provided via your .env or service file.

Last updated

Was this helpful?