Back to treasury proposals
Open Gov Referendum#137 >> Treasury Proposal#289
Awarded
Requested: 1.01K KSM

#289 High Performance Data Indexing Tool (2022)

Proposer:
Db4x...ys45
 
in Democracy
6th Apr '23

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

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.

  • 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, 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

Show More

Deadline: Not Set
Please Log In to comment

4Comments
0%
0%
100%
0%
0%
HBtJ...1hJs
 
 
24th Mar '23
(Edited)

Hey Subquery team,

Thank you for the proposal.

Here's the referendum audit for this treasury proposal.

Notes

  • This audit was not influenced by previous audits.
  • This audit reflects only the quality of information presented in the proposal and not the Quality of the project/idea itself.

Subquery Kusama dictionary

The following proposal Audit is created as a part of the extension for Proposal#67. More information about the Treasury proposal template and the Audit process can be found on the link above. All templates are free for everyone to use. For any questions or feedback regarding the Audit templates use the discussion link from above.

FLKB...svZR
 
 
31st Mar '23

Hi guys, I've recently looked through your project to do a review on one of my channels and I know you received funding from Arrington Capital and Hypersphere which are large VC firms + you are meant to release a coin which means you have a plan with a roadmap. Is there any reason why you can't follow that and you have to reach out to the treasury?

Thanks in advance,

Claudio

EPEk...e58C
 
 
2nd Apr '23
(Edited)

Hey SubQuery,

Thank you for updating the proposal.

Please note the Referendum Audit is reflecting only the quality of information presented in the proposal and not the Quality of the project/idea itself. I will create another report when the proposal goes onchain. Please remember to use the latest price and update budget before going onchain.

SubQuery

The following proposal Audit is created as a part of Proposal#67. More information about the Treasury proposal template and the Audit process can be found on the link above. All templates are free for everyone to use. For any questions or feedback regarding the Audit templates use the discussion link from above.

Please note that views and opinions presented in the Audit report are my personal and they do not represent general community opinion.

I have also made a video for the Spanish-speaking community that I leave in case anyone is interested in seeing it: Análisis Referéndum 137 - Español

HUj6...GLD6
 
 
13th Aug '23

Hello,

We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79

Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.

For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist


Discover similar proposals


Empty Icon

No Active Proposals