Get artem moskaluk’s stories in your inbox
Join Medium for free to get updates from this writer.
Distribution between the worker and delegators
Clone this wiki locally
Subsquid Network
Ethereum’s limited block space and transaction throughput have emerged as a significant bottleneck. A promising solution for scalability, initially spearheaded by Polkadot and Cosmos, involves migrating escalating application logic into a distinct chain. This strategy, coined the "appchain thesis", has since been validated, with all major EVM chains, including Polygon, Arbitrum, Optimism, Avalanche, and BNB Chain now developing tools to launch applications on a dedicated chain. Presently, hundreds of standalone and rollup-based chains exist, and if this trend continues, we can anticipate exponential growth of app chains in the Web3 space into the tens of thousands.
This shift towards the appchain design necessitates a complete transformation of the infrastructure stack. At the bare minimum, an app chain requires:
RPC infrastructure to manage user data
An indexing/caching layer to present app data
Integration with popular wallets (e.g. Metamask, Zerion)
A block explorer (e.g. Etherscan, Avascan, Calamar.app)
Integration with aggregators (e.g. DefiLlama)
Integration with analytics tools (e.g. Dune Analytics)
The initial element, RPC for submitting transactions, is the only component that demands a (non-archival) node infrastructure. Elements 2 through 6 rely entirely on read-only data. Unfortunately, extracting historical on-chain data, event logs, and replaying transactions can account for up to 95% of the total infrastructure costs that needs to be paid by third-party integrators. As a result, only popular chains become economically viable for integration, resulting in smaller, less popular chains subsidizing a full suite of services just to launch a minimal viable product. For reference, the price of running a single dedicated RPC node starts at 500$/mo. This means that running a healthy network of 20 nodes requires an expenditure of $10,000 at a minimum. An explorer integration starts at $15,000/mo.
The Subsquid Network seeks to democratize data access, regardless of scale. State-of-the art data compression and lightweight quering engine based on local DuckDB enables very cost-efficient access to on-chain data even at a petabyte scale combined. Thus, the business model of offering the data for free to consumers while charging fixed subscription fees to the chains providing the data becomes viable.
At future stages, an on-chain Spotify-like subscription model will be introduced. Premium users will be able to access additional datasets and subscription fees will be funneled to reward third-party data-providers. For example, high-quality data could be provided by Chainlink oracle providers.
For data providers (e.g. appchains) onboarding to the Subsquid Network lowers by up to 90%[2] the infrastructure costs for data-heavy integrations, such as:
indexers
explorers
*analytic platforms and *multi-chain aggregators
*real-time APIs
*dApp backends
Data Providers produce data to be served by Subsquid Network. Currently, the focus is on on-chain data, and the data providers are chains. Currently, only EVM- and Substrate-based chains are supported, while plans exist to support Cosmos chains and Solana.









