**Proponent:** Db4xRxFBsvMSBN5qWmmt9CWQdHt6gXSGuroh8JhU1q6ys45

**Date:** 6 March 2023

**Requested KSM:** 1012.9419

**Short description:** Ongoing costs for 2022, for the running of public-good SubQuery Dictionary Projects which serve pre-computed indexes of each block for most Polkadot and Kusama parachains. These public projects enable the parachain teams and teams within their ecosystem to increase the data indexing speed of their SubQuery projects by up to 10 times.

**Raw Data:** <https://docs.google.com/spreadsheets/d/17829KgXp5aXKXkaPw7A7oCgjMBB8vEuCg2Pyk1MGQnY/edit#gid=0>

**Full Proposal:** [https://docs.google.com/document/d/18lOrE_O8C6oDswYamIYHDUAw2V-R-HwoW9YnujQxFfw/edit?usp=sharing](https://docs.google.com/document/d/18lOrE_O8C6oDswYamIYHDUAw2V-R-HwoW9YnujQxFfw/edit?usp=sharing)

Original Motivation
===================================

SubQuery is the universal data indexing toolkit facilitating the construction of Web3 applications of the future. A SubQuery project is a complete API to organise and query data from Layer-1 chains. Currently servicing Polkadot, Kusama, and other layer-1 chains in Substrate, Avalanche, Algorand, Terra, NEAR, and Cosmos projects, we provide data for developers to use for a wide array of projects (wallets, explorers, custom chains, or any other decentralised app). In the future, the SubQuery Network intends to replicate this scalable and reliable solution in a completely decentralised manner.

Throughout the whole of 2022 (01/01/2022 - 31/12/2022) we've provided public SubQuery Projects, termed Dictionaries, for most parachains in the Polkadot and Kusama ecosystem to dramatically increase indexing performance (up to 10x faster) and so far these dictionaries have served over 1 billion requests.

A SubQuery dictionary is a special SubQuery Project which scans over the network, and records metadata of every event and extrinsic on each block. When other SubQuery projects index data on any of these chains, they can ask the dictionary what blocks a filtered list of events/intrinsics appear on. Rather than having to search through each block, dictionaries reduce the amount of data that the indexer obtains from the chain, reduces load on free RPC endpoints across the ecosystem, and reduces the number of "unwanted" blocks stored in the local buffer. For example, instead of SubQuery inspecting each block of Polkadot's massive chain (600GB of unstructured data on over 12 million blocks) which can take many hours, dictionaries skip through to the exact right blocks.

Adding the dictionary  to optimise indexing performance is as easy as adding the relevant network dictionary endpoint to your SubQuery Project. This has been added by default to all of our starter projects to make it default to use.

Here you can find detailed documentation on how dictionaries work: <https://academy.subquery.network/academy/tutorials_examples/dictionary.html#>

SubQuery Dictionaries have been created for most parachains to the public here <https://github.com/subquery/subql-dictionary> and have been deployed to our Managed Service. If any other team would like a dictionary created - we are more than happy to help out.

Future Targets for Our Dictionaries
===================================

-   We're proud of our record on stability and reliability. One of our core values is to be blockchain's most reliable indexer, and we don't intend to lose sight of this as we onboard more chains and expand the number of customers relying on our hosted service for their production applications. Our goal for 2023 is 99.99% uptime, we're starting off strong with 100% so far as seen [here](https://status.subquery.network/uptime/f3j5qtmn4rhd).

-   Through 2022 we ran 24 dictionaries for the in-demand parachains that we believed would add most value to the dApp developers in the Polkadot and Kusama ecosystems. Moving forward we want to be able to offer the increased indexing performance to all active block-producing parachains, our goal will be to add 20 more dictionaries to our suite of tools in 2023.

-   Being on the cusp of 1 billion requests to our dictionaries in 2022 has left us hungry to smash records in 2023. This year, with the launch of our decentralised SubQuery Network and ongoing Business Development efforts, we are looking to hit (and surpass) a target of 10 billion requests to our dictionaries.

Github Contributors. Our [dictionaries are completely open source](https://github.com/subquery/subql-dictionary), and SubQuery is a community project with a goal of complete decentralisation. Already last year, we welcomed contributions to our dictionaries from developers at Nodle and Subscan. We are working on making it easier for new parachains to assist us with creating dictionaries.

--

**Full Proposal Found Here:** [https://docs.google.com/document/d/18lOrE_O8C6oDswYamIYHDUAw2V-R-HwoW9YnujQxFfw/edit?usp=sharing](https://docs.google.com/document/d/18lOrE_O8C6oDswYamIYHDUAw2V-R-HwoW9YnujQxFfw/edit?usp=sharing)

Propose and approve a spend of treasury funds.

- `origin`: Must be `SpendOrigin` with the `Success` value being at least `amount`.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.

- The proposal is about funding ongoing costs for SubQuery Dictionary Projects.
- These projects help increase the speed of data indexing for Polkadot and Kusama parachains.
- The dictionaries have served over 1 billion requests so far.
- The goal is to have 99.99% uptime and add 20 more dictionaries in 2023.
- They want to reach a target of 10 billion requests to the dictionaries.

Requested: 0.10 undefined

#137 High Performance Data Indexing Tool (2022)