kyvenetwork / kyvejs

Tools for building applications on KYVE

@kyvejs

Tools for building applications on KYVE

KYVE, the Web3 data lake solution, is a protocol that enables data providers to standardize, validate, and permanently store blockchain data streams. By leveraging permanent data storage solutions like Arweave, KYVE’s Cosmos SDK chain creates permanent backups and ensures the scalability, immutability, and availability of these resources over time.

Project Overview

Common:

• @kyvejs/types - holds all types for the KYVE application in typescript
• @kyvejs/sdk - development kit for communicating with the KYVE blockchain
• @kyvejs/protocol - core functionality for running validators on the KYVE network

Tools:

• @kyvejs/kysor - The Cosmovisor of KYVE

Integrations:

• @kyvejs/tendermint - The official KYVE Tendermint sync integration
• @kyvejs/tendermint-ssync - The official KYVE Tendermint state-sync integration
• @kyvejs/tendermint-bsync - The official KYVE Tendermint block sync integration

Build Integration Binaries

Clone and checkout repository:

git clone [email protected]:KYVENetwork/kyvejs.git
cd kyvejs

Checkout desired version:

git checkout tags/@kyvejs/<integration>@x.x.x -b @kyvejs/<integration>@x.x.x

Example: git checkout tags/@kyvejs/[email protected] -b @kyvejs/[email protected]

Install dependencies and setup project:

yarn setup

Checkout integration and build binaries:

cd integrations/<integration>
yarn build:binaries

The binaries can then be found in the /out folder

How to contribute

Checkout new branch to implement new features/fixes there

git checkout -b [feat/fix]/[my-branch-name]

Install dependencies and setup project:

yarn setup

Apply your changes and create a Pull Request to main. Once the team has reviewed and approved your PR it can be merged and used.

NOTE: The usage of Conventional Commits is required when creating PRs and committing to this repository

How to release

In order to release new changes which got merged into main lerna can be used. Lerna will look into every change and create a new release tag if necessary. After the user has approved the new version tags (bumped according to Semantic Versioning) lerna will push those new tags to main, starting the CI/CD pipeline and creating the releases.

Release with lerna:

yarn lerna version

kyvejs's Issues

Proposal for Adding New Metrics to Improve Node Monitoring

Hi. My experience has shown that it would be great to add new metrics that can provide valuable insights into node health. Currently, the accumulation of points serves as an indication of issues with nodes, such as missed voting, RPC problems, etc. By incorporating additional metrics, we can create notifications to prevent slashing incidents.

Here you can find an example demonstrating how metrics can be displayed. I hope this example will be helpful for implementation.

Example: https://github.com/alexandrglaznyov/kyve-points-exporter

🌌 Debunking the Myth: Perpetual Storage of NFTs 🚀

https://www.youtube.com/watch?v=nJak9zdEY-k

Introducing Pixa, the world's first and greatest platform for creating and storing lightweight, scalable pixel art. With our advanced technology, anyone can turn HD pictures into pixel art with an editable color palette and painting-style effects.

But that's not all. Our platform DOESN'T offers a long-term storage solution that guarantees your pixel art will stay the same for 1000 years. And with our AAA web interface, creating and showcasing your pixel art has never been easier.

But now, we're looking for a unique buyer to take Pixa to the next level. And we're willing to offer a reward of $ **** to anyone who can make the match between Pixa and a successful buyer.

So if you know someone who would be interested in acquiring Pixa and taking it to new heights, now is the time to act. Don't let this opportunity pass you by, we are trusting the universe.

kyvejs incorrect typings on LCD client responses

With queries for the lcdClient

await this.lcdClient.kyve.query.v1beta1.finalizedBundle({
  pool_id: this.poolId,
  id: bundleId.toString(),
});

kyvejs/common/types/src/client/kyve/query/v1beta1/bundles.ts

Line 96 in 38ea7c7

export interface QueryFinalizedBundleResponse {

the response type is this, but my reponse i would get is of type FinalizedBundle

kyvejs/common/types/src/client/kyve/query/v1beta1/bundles.ts

Line 9 in 38ea7c7

export interface FinalizedBundle {

potential issue with generated ts types.