The concept of modularity, although gaining traction in today’s building trends, has actually been around for years, being the backbone of major chains like Cosmos, Celestia, and even KYVE!
Welcome to our course on the KYVE Use Case: Log Store, A Decentralized Time Series Database! This course will explore Usher Labs’ Alphanet project, Logstore, a unique application built within KYVE’s ecosystem that revolutionizes the way custom data is composed by time and handled in a decentralized manner. By leveraging KYVE’s decentralized data tooling, Log Store provides a powerful solution for delivering time series databases with ease.
By the end of this course, you will have a solid understanding of how LogStore utilizes KYVE as its validation layer, as well as its inspiring features and use cases. Whether you are interested in financial market data, IoT sensor data, data analytics, or exploring the potential of decentralized finance (DeFi), Logstore offers exciting possibilities to leverage time-based data in a decentralized and secure manner.
The problem that sparked Log Store is that when custom data is utilized within Smart Contracts, this data is typically requested from centralized, siloed environments, which exposes security risks associated with data integrity and data availability. Even when Arweave is utilized, centralized APIs that behave as gateways to this immutable data can remain points of compromise. The team behind Log Store experienced this issue first-hand, whereby using custom data to manage the allocation of digital assets required trust in the entity managing the data.
The Log Store Network solves this issue by decentralizing data management from the point of data collection to storage and then to query.
By leveraging the simplicity of data transport over the Streamr Network, consensus-driven data validity managed by KYVE, and guaranteed permanence and immutability of data with Arweave, the Log Store Network achieves its purpose.
Log Store recently released its AlphaNet network for initial testing.
The Log Store Network is comprised of two sub-networks bound by their own Blockchain systems and interlinked via a Streamr stream that behaves as a communication mesh.
The first layer is the Broker Network, where each Node is a Streamr Broker Node that has installed the logStore Plugin. In order to guarantee the operational performance of Log Store’s layers, the second Validator Layer is
required.
The Validator layer builds upon KYVE, a consensus-based data lake comprised of data pools run by validators that collectively fetch, validate, and store data onto decentralized storage platforms.
This Validator Layer not only behaves as an authority over the Broker Layer — determining which Nodes are rewarded, which are penalized, and how digital assets should be consumed from developers interacting with the network but also behaves as the storage mechanism so that Streamr data is uploaded to Arweave in a fully decentralized manner.
Once data is pushed to Arweave, a recursive process takes place, whereby Nodes within the Broker layer are responsible for reading from this decentralized data lake, and then submitting reports to our Polygon Smart Contract. This reporting process draws on inspiration from Chainlink’s Off-Chain Reporting (OCR) strategy for minimizing gas fees.
Other projects can also build using KYVE as their validation layer, either by creating their own data pool, or tapping into our current data sets via REST- API or our no-code data pipeline. We look forward to seeing the KYVE ecosystem
grow!
“It is very exciting to see the first non-KYVE integration operating on our devnet, Korellia. As a data validation and archival solution, we strongly encourage projects like Log Store to bring forward new innovative ways for using KYVE’s decentralized tech to provide secure solutions to Web3. Via this integration, we learned a lot from their development experience and feedback, and want to congratulate Log Store for their successful Alphabet launch!” – Troy, Lead Protocol Developer at KYVE.
Log Store’s AlphaNet enables developers to store and query their Streamr data in a permissionless, decentralized, and fully verifiable manner, but also provides practical solutions for dApps that require reliable, verifiable data storage.
Other use cases range from DeFi protocols leveraging data-driven on-chain token re-allocation, Games rewarding users based on their engagement across Web3, Marketing platforms rewarding users for their interactions and data, archiving and retrieval of data for public ledgers and Web3 infrastructure, and even long-term, easily accessible records, that can aid in decentralized identity verification. These use cases demonstrate how pure and reliable custom data can bridge the divide between heterogeneous systems. Additionally, its time-series capability prevents redundant data ingestion and even makes it an ideal fit for sectors such as financial analysis and IoT data monitoring, where trend tracking and interpretation of data are pivotal.
More use cases are yet to be discovered.
You made it through the KYVE Use Case Logstore course! You are now familiar with a project building in KYVE’s ecosystem, facilitating time-based data queries.
Want to learn more? Check out these resources: