Deploy Ergo Infrastructure

Deploy pages are for operators running infrastructure: nodes, APIs, wallets, indexers, Rosen watchers, oracle pools, and blockchain-indexing services.

Start with the Deployment Runbook if you are choosing a topology or hardening an existing host.

Deploy Map

Run a Node

Install, configure, sync, monitor, and harden the Ergo reference client.

Node Operations

Operational runbooks for hardening, monitoring, upgrades, backups, reverse proxies, and incidents.

APIs & Indexing

Expose node APIs, use indexed routes, deploy explorer-style stacks, or build a custom indexer.

Rosen & Oracles

Operate Rosen watchers/guards or bootstrap oracle infrastructure.

Next Steps

• New operator: start with the Deployment Runbook.
• Need API details: use Swagger Overview or Technical Lookup.
• Debugging an outage: use Troubleshooting.
• Mining pool operator: go to Mining Pool Operations.

Operator Paths

Need	Start here	Why
Run a validating node	Node install overview	Choose manual, Docker, Raspberry Pi, Android, or source build.
Choose archival, pruned, digest, or light mode	Modes of operation	Pick storage and validation trade-offs before syncing.
Harden config and API access	Node configuration	Set data directory, REST API, P2P, wallet, and network config.
Serve indexed API queries	Indexed Node API	Requires ergo.node.extraIndex = true.
Use Swagger / OpenAPI	Swagger overview	Explore REST endpoints and protected wallet routes.
Run Rosen watchers	Rosen watcher deployment	Docker deployment, local.yaml, chain sources, and health checks.
Operate oracle pools	Oracle Core and Oracle bootstrap	Bootstrap pools, distribute tokens/config, run oracle operators.
Build a custom indexer	Blockchain indexing	Compare explorer API, node API, and custom chain-grabber setups.

Public Services vs Owned Infrastructure

Public nodes and explorers are useful for experiments, but production services should run their own node or indexer where possible.

• Public node APIs can disappear, lag, rate-limit, or expose only a subset of routes.
• Wallet, watcher, oracle, and transaction-submission workflows depend on API availability and correct network view.
• Indexed routes under /blockchain/... require a node with extraIndex = true; not every public node enables this.
• Services that hold secrets should not send wallet API keys, mnemonics, or private operational data to third-party hosts.

Useful public entry points:

• Ergo Explorer: explorer.ergoplatform.com
• Ergo Explorer alternatives: ergexplorer.com, sigmaspace.io
• Public peer list: api.tokenjay.app/peers/list

Baseline Hardening

• Keep node REST API private by default. Use localhost, SSH tunnels, VPN, firewall rules, or HTTPS reverse proxy.
• Change the example apiKeyHash; it is the hash of hello in the default config.
• Put node data, wallet files, PostgreSQL data, and watcher volumes on durable storage.
• Track node sync height and indexed height separately.
• Back up wallet files and mnemonics offline. Do not keep seed phrases in shared config files.
• For Rosen watchers, prefer environment variables for MNEMONIC, API_KEY_HASH, RPC credentials, and API tokens.