Skip to main content


This data pool validates and archives all blocks from Cosmos Hub and makes them permanently available with Arweave and Bundlr.


  • Runtime: @kyvejs/tendermint-bsync
  • Data Source: Self hosted Gaia full node (cosmoshub-4)
  • Data: Blocks from height 5,200,791 ongoing
  • Storage Provider: Bundlr
  • Networks
  • Min Hardware Requirements
    • 2 or more physical CPU cores
    • 16 GB RAM
    • 512 GB DISK
    • 50mbps network bandwidth

General Setup

If you want to participate in the Cosmos Hub pool you will have to run a Gaia Full node which will act as the data source for the KYVE protocol validator.

This ensures that the data which is getting proposed and validated actually comes from decentralized sources. Furthermore, since the gaia blockconsensus validator only serves valid blocks we further increase the validation of this data. With that setup a user who wants to join this pool first has to sync his gaia node to the current height the pool has already archived the blocks and then start the actual KYVE protocol validator.

This architecture diagram summarizes the setup of the Cosmos Hub integration on KYVE:

Here the tendermint-bsync runtime is responsible for communicating with the tendermint application (purple) - in this case gaia, and forwarding the data to the KYVE core protocol. The KYVE core then handles the communication with the pool. This entire process (yellow) is the KYVE protocol validator. The resulting data are the blocks from the tendermint application - validated and permanently stored on a storage provider like Arweave.


The goal of this pool is to validate and archive all blocks from Cosmos Hub permanently and decentralized. With this data we want to make it possible for other nodes to block sync the data from KYVE, making expensive archival nodes on Cosmos obsolete in the long run. More information on how to perform block sync with KYVE visit the documention about KSYNC here.