DOCSEARCHbyAlgolia
Submit Docs

KYVE Network Documentation

website·Indexed 34 days ago

https://docs.kyve.network

Guides for running and managing KYVE protocol validators and nodes. Includes installation, configuration, and upgrade instructions using KYSOR for various data pools such as Ethereum blobs, Cronos, dYdX, Noble, and Osmosis, as well as hardware requirements and Supervysor setup.

Tokens
71.7K
Snippets
356
Records
550
Agent score
66%

What's inside KYVE

  1. Overview of the Celestia Data Pool on KYVE

    The Celestia data pool validates and archives all blocks and block results from Celestia, making them permanently available via Arweave and Irys. The primary goal is to enable other nodes to perform block sync from KYVE, potentially making expensive Celestia archival nodes obsolete and facilitating decentralized data analysis.

  2. Overview of the Avail Data Pool on KYVE

    The Avail data pool validates and archives all blocks and block results from the Avail Mainnet, making them permanently available via Arweave and Irys. The primary goal is to provide a decentralized archive that allows other nodes to perform block sync via KSYNC, potentially making expensive Avail archival nodes obsolete and enabling advanced data analysis.

  3. Overview of KYVE Data Rollups-as-a-Service (DRaaS)

    KYVE provides Data Rollups-as-a-Service (DRaaS) designed to improve scalability for validators, builders, blockchains, and applications. The platform allows DApp builders to create custom data rollups, while token holders can stake $KYVE to secure the network's two layers and participate in governance.

  4. Overview of the Cronos Data Pool

    The Cronos data pool validates and archives all blocks and block results from the Cronos network, making them permanently available via Arweave and Irys. The primary goal is to enable other nodes to perform block sync from KYVE, reducing the need for expensive Cronos archival nodes and facilitating decentralized data analysis.

  5. Overview of the Trustless API architecture

    The Trustless API consists of two primary independent components: a Crawler and a Server. The Crawler retrieves bundles from the KYVE chain, generates data inclusion proofs for each item, creates indices, and stores them. The Server then handles requests for specific data items by retrieving the item and its associated inclusion proof from the database. The Crawler must be running to ensure the Server has the necessary data to serve.

  6. Overview of the supervysor

    The supervysor manages the data source node process (e.g., CosmosHub, Osmosis) for KYVE data pools. It prevents high storage costs (which can exceed 10TB for some chains) by optimizing the synchronization process, ensuring the node only syncs as much as required by the KYVE pool and continues providing data even when synchronization is paused.

  7. Overview of the Cronos state-sync data pool

    The Cronos state-sync data pool validates and archives state-sync snapshots from Cronos, making them permanently available via Arweave and Irys. The primary goal is to enable other nodes to perform state-sync from KYVE, reducing the need for expensive archival nodes on Cronos. Data is captured as state-sync snapshots every 5,000 blocks.

  8. Overview of Avail node requirements for KYVE

    The Avail Node is a required data source for the KYVE protocol validator. It can be run on the same machine as the KYVE protocol (recommended) or on a separate machine. To prevent slashes and ensure accessibility and validation, it is strongly recommended to run an independent data source node; using third-party API providers is discouraged as it has caused critical problems in the past.

  9. Overview of the Noble state-sync data pool

    The Noble state-sync data pool validates and archives state-sync snapshots from Noble, making them permanently available via Arweave and Irys. The primary goal is to enable other nodes to state-sync data from KYVE, reducing the need for expensive archival nodes on Noble. Data is captured as state-sync snapshots every 3,000 blocks.

  10. Overview of the Noble Data Pool on KYVE

    The Noble data pool validates and archives all blocks and block results from the Noble network, making them permanently available via Arweave and Irys. The primary goal is to enable other nodes to perform block sync from KYVE, reducing the need for expensive archival nodes on Noble and facilitating data analysis.

  11. Overview of SubQuery Indexer for KYVE

    SubQuery is an open-source blockchain data indexer that provides fast, flexible, and decentralized APIs for web3 projects. It allows developers to index rich on-chain data (transaction histories, smart contract states, and event logs) for the KYVE network and over 100 other ecosystems. Key capabilities include aggregating data across multiple blockchains within a single project, multi-worker capabilities, and configurable caching architecture to optimize query performance.

  12. Overview of KYVE Network Architecture

    KYVE is a Proof of Stake (PoS) Layer 1 blockchain built using the Cosmos SDK and Ignite. It is designed as a decentralized data lake for fetching, storing, and validating on- and off-chain data. The architecture consists of two distinct layers:

    1. Chain Layer (Consensus Layer): The sovereign PoS backbone run by independent nodes that secure the blockchain.
    2. Protocol Layer: Sits atop the consensus layer and manages the data lake functionality, including data pools, funding, staking, and delegation. Protocol validators collect data from sources, bundle and upload it to decentralized storage, and validate it for users.