Indexes all blocks, state, and extrinsic data from Substrate-based blockchains into PostgreSQL.
Substrate Archive is a blockchain indexing engine that runs alongside Substrate-based chains to capture and store all blockchain data in a PostgreSQL database. It enables efficient querying and analysis of historical blockchain data, which is essential for explorers, analytics platforms, and other data-intensive applications.
Developers and teams building blockchain explorers, analytics platforms, or data-intensive applications on Substrate-based chains like Polkadot, Kusama, or Westend.
It provides a reliable, performant indexing solution that operates as a secondary service to Substrate nodes, ensuring data availability without compromising chain performance, using PostgreSQL for structured storage and RocksDB's secondary instance for non-disruptive data reading.
Blockchain Indexing Engine
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses RocksDB's secondary instance feature to read chain data without interrupting node operation, ensuring high availability as noted in the troubleshooting section for ulimit adjustments.
Stores all indexed blockchain data in PostgreSQL, enabling complex SQL queries for analytics, with the schema detailed in a PDF file at the project root.
Provides a batteries-included command-line interface that simplifies configuration without writing Rust code, as highlighted in the wiki for quick starts.
Works with Polkadot, Kusama, Westend, and other Substrate-based chains, making it versatile for various ecosystems, per the chain parameter in usage examples.
The README states it is currently unmaintained, leading to potential bugs, security vulnerabilities, and lack of support for new chain updates.
Requires adjusting system ulimits (e.g., raising max open files to 90000) and specific PostgreSQL setups, which can be error-prone and time-consuming.
Needs approximately 60GB of free space per chain and runs alongside a full node with pruning=archive, making it resource-intensive for smaller deployments.
Relies on a wiki and scattered examples, but with the project unmaintained, documentation may be outdated or incomplete, increasing the learning curve.