Today, we are excited to announce two integrations with KYVE, which will massively enhance the developer experience on both KYVE and the wider Cosmos ecosystem. KYVE, streamlining reliable historical data storage and accessibility, is its own Proof of Stake (PoS) Layer 1 blockchain built with the Cosmos SDK. It has two layers: the Chain Layer and the Protocol Layer, each with its own node infrastructure. SubQuery has recently finished two powerful integrations on both the chain AND protocol level. 

SubQuery Integration with KYVE Protocol

We've recently completed a pioneering integration with KYVE protocol's trustless datasets, solving one of the key issues facing developers in many ecosystems - availability of high-performance archival RPCs. KYVE’s decentralized protocol validates and archives all of the historical data of different blockchains, with its ‘data lake’ keeping track of such data for easy access via custom tooling. The types of data included in KYVE’s data lake includes blocks, block results, state snapshots and even blobs for certain chains.

By harnessing the power of KYVE's data lake, we've eliminated the cumbersome task of hunting down non-pruned or archive RPC providers, streamlining and expediting SubQuery's access to historical on-chain data. This makes a huge difference for developers in Cosmos ecosystems, where non-pruned archive RPC providers are hard to find.

Unlike many RPC providers, particularly archive RPCs, KYVE's service is entirely free to use, making it fully accessible for SubQuery builders. Moreover, our seamless integration with KYVE operates in tandem with RPCs, guaranteeing users real-time access to the latest data from the RPC, while harnessing the enhanced performance offered by KYVE's data lake for archival data.

KYVE sought out to solve the prominent RPC availability problem in Cosmos but has also expanded beyond Cosmos to support more chains. Users of SubQuery can benefit from this integration when indexing data from any network that KYVE supports (Osmosis, Axelar, Ethereum, Avail & more; see the full mainnet support list here). 

“We are excited about our collaboration with KYVE Network where we’ve taken our performance-focused indexing service another step further to solve the RPC availability problems that we often hear from developers. This integration will help further our vision of a web3 world where builders can build groundbreaking products without worrying about infrastructure.”— Sam Zou, Founder and CEO of SubQuery

SubQuery Support for KYVE On-Chain Indexing

KYVE is not just a protocol but also a Cosmos chain itself. The second integration we’ve completed is a standard SubQuery chain support integration. This means developers building on KYVE's network can now use SubQuery to index transactions, blocks, and events from the KYVE chain, and all you need is a public endpoint. 

One SubQuery use case for this might be for a KYVE validator doing their taxes and needs access to all claim reward events - the validator can easily run a SubQuery project to index all of those events. 

SubQuery simplifies the intricacies of backend operations, providing developers with a tailor-made API. This enables them to focus on product development and enhancing user experiences, without the need to allocate resources towards building custom indexing solutions.

“SubQuery's fast and feature-rich indexer provides an intuitive and excellent user experience, which is now a crucial piece of infrastructure for KYVE's developer community. It's great that KYVE's trustless datasets support SubQuery indexers with historical data needs.”

— Fabian Riewe, Co-Founder of KYVE

Why Use SubQuery?

SubQuery makes it easy to build a custom API for your dApp or smart contracts in minutes, providing clean indexed data to any service. The excellent SubQuery developer experience is flexible, with the ability to make external API calls or import external libraries from within your mapping functions, and better controls to run your projects in your own infrastructure with automated DOS (denial of service) mitigation controls. Additionally, we have yet to make plans to sunset our managed service.

SubQuery is designed to be fast. This adds up when you’re indexing millions of ledgers, and is something to consider when choosing your indexer. SubQuery achieves this by using multi-threading and optimisation of the store to reduce costly database writes. With faster sync times, developers can iterate faster and deliver features to market quicker.

SubQuery’s Support for KYVE

About KYVE

The KYVE Network is revolutionizing customized access to on- and off-chain data by providing fast and easy tooling for decentralized data validation, immutability, and retrieval.

With these tools, developers, data engineers, and others can easily and reliably access the trustless data they need to continue building the future of Web3.

KYVE is its own Proof of Stake (PoS) Layer 1 blockchain built with the Cosmos SDK. It has two layers: the Chain Layer, and the Protocol Layer, each with its own node infrastructure. The Chain Layer which is the consensus layer, is the backbone of KYVE and is an entirely sovereign Proof of Stake (PoS) blockchain built with/on Ignite. It’s run by independent nodes, which enable users to support and secure the KYVE blockchain.

Website | Docs | Twitter | Discord | Telegram | GitHub | Medium | YouTube 

About SubQuery

SubQuery Network is innovating web3 infrastructure with tools that empower builders to decentralise the future. Our fast, flexible, and open data indexer supercharges dApps on over 180 networks, enabling a user-focused web3 world. Soon, our Data Node will provide breakthroughs in the RPC industry, and deliver decentralisation without compromise. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era. Let’s shape the future of web3, together.

​​​​Linktree | Website | Discord | Telegram | Twitter | Blog | Medium | LinkedIn | YouTube

Share this post