Skip to main content
This guide will walk you through the process of creating a fleet of nodes that serve archival data and how to stitch them together using a gateway

Architecture

To make serving archival data more accessible we split the data into smaller segments. These segments are stored in s3://injective-snapshots/mainnet/subnode These segments are stitched together via gateway which is an aggregator proxy that routes queries to the appropriate node based on block range Archival Architecture

System Requirements

Each node hosting a slice of archival data should have the following minimum requirements

Setup Steps

On each node hosting an archival segment:

1. Download the archival segments with the history your setup requires using

2. Download or set the appropriate injective binary or image tag based on the table above

3. Generate your config folder

4. Disable pruning in your app.toml file and block p2p and set the log level to error in your config.toml files.

This ensures that the data does not get pruned and the node stays in a halted state. Setting the log level to error lessens disk ops and improves performance.

5. Run your node

Gateway configuration

1. Clone the gateway repository

2. Build gateway

3. Create your config file

4. Run Gateway

Last modified on March 30, 2026