Get your network set up with a managed OpenScan.AI explorer.
This guide walks through the onboarding process for Explorer-as-a-Service, from requirements to launch.
Launching a new network
For networks that haven’t launched yet, we recommend onboarding in parallel with your launch preparation:
- Weeks before launch: share chain specs — chain ID, genesis configuration, native currency details, and a reachable bootnode or RPC endpoint.
- Testnet first: we deploy a testnet explorer as soon as your testnet is live. Your developers get a working explorer and API from day one of public testing.
- Launch day: the mainnet explorer goes live alongside your network, pre-configured and synced from genesis.
Launching with an explorer at genesis means zero reindexing later and a complete chain history from block 0.
Migrating an existing network
For live networks, onboarding starts with a full historical sync:
- Provide an archive RPC endpoint — full history including traces is required to index internal transactions. If you don’t run archive infrastructure, we can advise on node setup.
- Initial sync — historical indexing takes days to weeks depending on chain size and activity. The explorer comes online progressively and is usable while historical data backfills.
- Parallel run — if you’re replacing another explorer, both can run side by side while your ecosystem migrates links and API integrations. The Blockscout-compatible API makes most migrations a base-URL change.
- Cutover — point your domain and canonical links at the OpenScan.AI instance.
Private and permissioned chains
Enterprise and consortium chains can be onboarded with network-level isolation:
- Deployments into your cloud account or VPC, or managed hosting with VPN/IP-restricted access.
- Authentication in front of the explorer UI and API when the chain data isn’t public.
- Custom data-retention and compliance configurations.
Requirements are the same (chain ID, RPC endpoints with trace support, native currency details) plus your network access constraints. Contact the team through GitHub or X to scope a private deployment.
Requirements checklist
Regardless of path, have these ready:
- Chain ID and network name
- RPC endpoint(s) — HTTP with
eth_*and trace (trace_*/debug_*) methods; WebSocket preferred - Native currency — symbol, name, decimals
- Brand assets — logo (SVG preferred), brand colors, favicon
- Domain — the hostname your explorer will live on (we can provide one under our domain to start)
- Launch timeline — testnet and mainnet target dates
After onboarding
- Branding & Customization — apply your identity
- Managing Your Explorer — day-to-day administration
- Supported Networks — networks already running OpenScan.AI