Skip to content

Hyperion Setup

1. Clone & Install packages

git clone
cd hyperion-history-api
npm install


if you came from the script section, you can skip this step and go directly to the Edit configs step below.

2. Edit configs

cp example-ecosystem.config.js ecosystem.config.js
nano ecosystem.config.js

# Enter connection details here (chain name must match on the ecosystem file)
cp example-connections.json connections.json
nano connections.json
connections.json Reference

         "name":"EOS Mainnet",
For more details, refer to the connections section

ecosystem.config.js Reference

module.exports = {
    apps: [
        addApiServer('eos', 1)
For more details, refer to the ecosystem section

3. Setup

cp chains/example.config.json chains/CHAIN_NAME.config.json

cp chains/example.config.json chains/eos.config.json
The default config.json file is ready to run. The parameter abi_scan_mode is true to perform an abi scan on the first run.

For more details, refer to the chain section

4. Start and Stop

We provide scripts to simplify the process of starting and stopping your Hyperion Indexer or API instance. But, you can also do it manually if you prefer. This section will cover both ways:

Option 1: Using run / stop script

run script

You can use run script to start the Indexer or the API.

./ chain-indexer

./ chain-api


Start indexing EOS mainnet:

./ eos-indexer
Start EOS API:
./ eos-api

Remember that the chain name was previously defined in the setup step.

stop script


Stop the EOS mainnet indexer:

./ eos-indexer


The stop script won't stop Hyperion Indexer immediately, it will first flush the queues. This operation could take some time. If you want to stop immediately, you need to run the "force stop command" explained below.

Option 2: Commands

Start indexing
pm2 start --only chain-indexer --update-env
pm2 logs chain-indexer
Stop reading and wait for queues to flush
pm2 trigger chain-indexer stop
Force stop
pm2 stop chain-indexer
Starting the API node
pm2 start --only chain-api --update-env
pm2 logs chain-api

5. Indexer

As mentioned before on Setup, the Hyperion Indexer is configured to perform an abi scan ("abi_scan_mode": true) as default. So, on your first run, you'll probably see something like this:


This an example of an ABI SCAN on the WAX chain.


  • W (Workers): Number of workers.
  • R (Read): Blocks read from state history and pushing into the blocks queue.
  • C (Consumed): Blocks consumed from blocks queue.
  • A (Actions): Actions being read out of processed blocks.
  • D (Deserialized): Deserializations of the actions.
  • I (Indexed): Indexing of all of the docs.

6. API

After running the api, you should see a log like this:


Now, it's time to play around making some queries.

API Reference

API Reference: API section: v2

Example: OpenAPI Docs