Caution
Archive Registry is now deprecated:
squid-archive-registryexecutable is replaced bysqd gateways lsand Subsquid Network documentation pages.lookupArchive()calls should be replaced by direct gateway URLs.
A community-owned registry of Squid archives in a json format.
The registry is available as an npm package @subsquid/archive-registry. It can be used to conveniently access registry files and e.g. lookup a Squid Archive or EVM Squid Archive by network name.
Use the included squid-archive-registry executable to list supported networks:
$ squid-archive-registry --help
Usage: run [options]
Display list of available archives
Options:
-t --type <type> Network type (choices: "evm", "substrate")
-h, --help display help for commandThe first argument is the name of the network. The second argument is set of lookup filters of type LookupOptionsSubstrate.
import { lookupArchive } from '@subsquid/archive-registry'
const processor = new SubstrateProcessor()
.setDataSource({
archive: lookupArchive("kusama"),
});More accurate way to choose from Substrate networks is to specify type parameter inside options for the function. By default type is set to Substrate.
const processor = new SubstrateProcessor()
.setDataSource({
archive: lookupArchive("kusama", { type: "Substrate" }),
});LookupOptionsSubstrate supports additional filtering by genesis hash, archive version (semver range) and docker image names (of archive and archive gateway).
There is also a convenience method to get network information by its name:
// ...
.setDataSource({
archive: lookupArchive("kusama", { genesis: "0xb0a8d493285c2df73290dfb7e61f870f17b41801197a149ca93654499ea3dafe" }),
});Similar to Substrate archive: first argument is the name of the network, second one is a set of lookup filters of type LookupOptionsEVM.
import { lookupArchive } from '@subsquid/archive-registry'
const processor = new EvmBatchProcessor()
.setDataSource({
archive: lookupArchive("avalanche"),
});LookupOptionsEVM supports additional filtering by release type:
There is also a convenience method to get network information by its name:
// ...
.setDataSource({
archive: lookupArchive("avalanche", { type: "EVM", release: "FireSquid" }),
});Squid Archive provides easy access to the historical on-chain data with little modifications. It is essential for Substrate Squid pipelines or EVM Squid pipelines. It can also be used on its own as a GraphQL-based block explorer with powerful filtering and search capabilities over historical events and transactions.
The primary use case of a Squid Archive is to serve data to a Substrate Squid Processor or EVM Squid Processor.
The urls are not supposed to be accessed with a browser. To explore the endpoint with an interactive and human-friendly console, use explorerUrl field in archives.json (only for substrate archives).
For example, for exploring Kusama historical data, one can inspect archives.json and local Kusama explorer at https://kusama.explorer.subsquid.io/graphql. One can open the GraphQL playground by navigating to this url and use the pane on right hand side to filter (where:) and pick the fields of interest.
For example, the following query will return details on the last 10 transfers:
query RecentBalancesTransfers {
events(orderBy: block_height_DESC, where: {name_eq: "Balances.Transfer"}, limit: 10) {
args
name
call {
name
args
}
block {
timestamp
height
}
}
}
To contribute a new archive, make a PR updating archives.json or archives-evm.json specifying the network name and the url. Further, one has to regenerate types in src/chains.ts by running npm run gen-types. This will update the list of supported chain names and makes it easier to developers to discover which lookups will succeed at compile time.
