Skip to content
Thyme Docs

Networks and manifest support

Atlas validates the manifest when you deploy. Graph CLI uploads the schema, ABIs and mappings first and the manifest last, so Atlas sees the network only after the upload. Check this page before deploying to avoid a wasted upload.

Networks

Use one of these names as network in every data source and template.

networkChainChain IDNotes
mainnetEthereum1
sepoliaEthereum Sepolia11155111
maticPolygon PoS137Also accepted as polygon or matic-mainnet
polygon-amoyPolygon Amoy80002
optimismOP Mainnet10startBlock must be at least 105,235,064 (Bedrock)
bscBNB Smart Chain56
unichain-testnetUnichain Sepolia1301

The names follow The Graph's networks registry. Aliases are recorded under the main name (for example, a polygon subgraph is listed as Polygon on matic), while your manifest, deployment ID and dataSource.network() keep the name you wrote. A subgraph indexes exactly one network.

Versions and data sources

ItemSupported
specVersionup to 1.5.0
Mapping apiVersionup to 0.0.10
Data source and template kindethereum (or the older ethereum/contract)
Event, block and call handlersYes. Call handlers need traces; Atlas warns when a manifest uses them.
Templates (dynamic data sources)Yes
GraftingNo
File data sources, ipfsOnEthereumContracts, SubstreamsNo

History pruning

indexerHints.prune controls how many blocks of entity history Atlas keeps. Time-travel queries (block: { number: … }) work within that window.

indexerHints.pruneHistory kept
A number up to 300000That many blocks
autoThe minimum Graph Node allows (500 blocks)
Not setThe most recent 300,000 blocks
never, or a number above 300,000Rejected at deploy

Size limits

LimitValue
Data sources1 to 128
Templatesup to 128
Files referenced by one deploymentup to 256
Manifest1 MiB
Any single file25 MiB
Whole deployment100 MiB