Environment Variables Overview

Hosted option: Skip ENV management entirely with Explorer-as-a-Service from OpenScan.AI — reach out via the contact form to discuss a managed deployment.

OpenScan.AI uses ENVs for setting hundreds of different parameters. See the reference section for ENV names, descriptions, default values, and versioning:

• Backend ENVs: Common — database, JSON RPC, indexer, market data, API rate limits, and more

Set ENV Variables with CLI

Use the export command to set variables. For example, for an XDC Network instance:

export ETHEREUM_JSONRPC_VARIANT=geth
export COIN=XDC
export NETWORK=XDC
export CHAIN_ID=50

Required ENV variables

Please see the Backend ENVs page for details. Required variables are located in the General Management section and marked with a ✅.

Time format

Time values can be set in the format 1h for 1 hour, 1m for 1 minute, 1s or 1 for 1 second, 1ms for 1 millisecond. If no unit is provided, the value is interpreted as seconds.

Note: Before release 5.1.2, all environment variables of time format supported only integers in seconds (without dimensions) as values.