Every OpenScan.AI explorer depends on a healthy EVM node. This section covers running the chain infrastructure your indexer reads from.
Why the Node Matters
The explorer is only as good as its data source. A node that is behind, pruned, or missing tracing support directly degrades the explorer: stale blocks, missing internal transactions, incomplete history.
In This Section
Running an Archive Node
Set up and maintain an archive EVM node suitable for full explorer indexing.
High-Availability Node Setup
Placeholder — content under development (see the HA setup page in this section).
Remote Signing & Node Security
Placeholder — content under development.
What the Indexer Needs
- Archive mode — full historical state for balance-at-block queries.
- Tracing APIs —
debug_traceTransaction/trace_*for internal transactions. - Low latency — the indexer issues thousands of RPC calls per range.
- Stability — monitor sync status and disk growth continuously.
See Chain Node Layer for architectural detail.
Supported Networks
OpenScan.AI runs in production on XDC Network (xdcscan.io) and supports EVS, Wanchain, and Velas. Any EVM-compatible chain with standard JSON-RPC and tracing can be indexed.