Question 1

How to deploy Subscan Essentials on Kubernetes?

Accepted Answer

Use the official Helm Chart from the subscan-essentials-chart repository: add the repo, configure values.yaml with your database and Redis details, then install or upgrade the chart. It supports multi-network setups and custom resources.

Question 2

Subscan Essentials vs Polkascan: which should I use?

Accepted Answer

Subscan Essentials is a self-hostable backend focused on extensibility and production use, powering subscan.io. Polkascan is another explorer framework; choose Subscan Essentials if you need proven Substrate integration and custom plugins, but expect more setup work.

Question 3

Can I use Subscan Essentials for EVM-only chains?

Accepted Answer

No, it's specifically designed for Substrate-based blockchains, though it can index EVM data within Substrate parachains that support it, like Moonbeam. For pure EVM chains, other explorers are better suited.

Question 4

How to add custom data plugins?

Accepted Answer

Utilize the plugin framework with auto-generated templates from the gen tool in the subscan-plugin repository. Follow the plugins documentation to build and integrate custom parsers for unique on-chain data.

Question 5

What are the system requirements for running this?

Accepted Answer

Requires Linux/macOS, Go 1.23+, Redis 3.0.4+, and MySQL 8.0+ or PostgreSQL 16+. Adequate CPU and memory are needed for indexing large chains, as worker goroutines handle data processing.

Question 6

Is there a hosted version available?

Accepted Answer

Not for the open-source project; it's designed for self-hosting. The team behind subscan.io may offer commercial services, but you must deploy and manage the infrastructure yourself using Docker or Kubernetes.

Subscan Go Utilities

What is Subscan Go Utilities?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions