Your explorer should look like your chain. This page covers the configuration surface of an OpenScan.AI deployment: chain parameters, visual branding, domains, and feature flags.
Chain Parameters
The essentials, typically set in the deployment .env:
CHAIN_ID=50 # your chain's numeric IDNEXT_PUBLIC_NETWORK_NAME="Your Chain" # display nameNEXT_PUBLIC_NETWORK_COIN=XYZ # native coin symbolNEXT_PUBLIC_NETWORK_COIN_DECIMALS=18ETHEREUM_JSONRPC_HTTP_URL=http://chain-node:8545ETHEREUM_JSONRPC_TRACE_URL=http://chain-node:8545Get CHAIN_ID and the RPC URLs right — a mismatch here produces a silently wrong explorer. The Configuration Service validates them at startup.
Visual Branding
| Setting | Purpose |
|---|---|
| Logo (light/dark) | Header, footer, and favicon |
| Primary color | Links, buttons, chart accents |
| Theme defaults | Light, dark, or user-selected |
| Social preview image | Link unfurls on X/Twitter and messengers |
| Footer links | Your chain’s site, docs, and community channels |
Branding assets live in the deployment’s asset directory and are referenced from the branding config. Keep source assets in version control alongside your configuration.
Domain Configuration
Point your custom domain at the deployment and register it — see Custom Domain Service for hosted instances, or TLS / HTTPS Setup for self-hosted.
Feature Flags
Commonly toggled features:
- AI insights — transaction summaries and contract explanations
- Contract verification — accept source submissions through the UI and API
- Token metadata enrichment — icons and project links for known tokens
- Advertising / banners — optional promotional slots
Applying Changes
- Configuration changes require a service restart: frontend → backend → indexer.
- Verify branding on desktop and mobile after every change.
- Use Explorer Verification after any restart.
Hosted Instances
For hosted EaaS, send branding assets and configuration requests through the contact form — the team applies them for you.