Tip the author

Why KYVE needs to exist: AMA with Fabian Riewe & John Letey

KYVE is one of the most exciting new permaweb applications because of its huge array of possibilities. With KYVE, it’s possible to archive and verify any kind of data. This AMA finds out more from founders Fabian Riewe and John Letey.

Can you give details about the release time of KYVE tokens? (5YRqJcMghX1aziSNQraNoYZrhjAzwbOxswTS4emgWyU)

As of right now, we’re still on testnet. Hopefully, we can share more about our token as we get closer to our mainnet launch! You can get free testnet tokens here: kyve.network/faucet.

Can you ELI5 KYVE? (9QAp_T36fi-kBIHRl5xdSjMT4KGHyEiWSJs1VLw291c)

You can imagine KYVE as a warehouse. We collect and categorize data to deliver it to our customers better, cheaper, and faster.

What are the most exciting future use cases you see KYVE enabling? (su2ltjJvc62jeVfbw7s-M8yAqDLB1gSlcRL6PkUAfRc)

Each developer and project have their own use cases around the data we’re archiving. However, we’re particularly interested in the cross-chain functionality that KYVE enables! Developers can access data from multiple chains or web3 apps with no problem. We currently see KYVE being used as a safe place to load data from. This helps projects solve scalability problems because they don’t need to store the data themselves.

Can you give some background on what sparked the idea to build KYVE, and why?(bjwmCMqrwiF1Ql9pAVj6AeAGCVHTWQnQWo6CcZswRGM)

Previously, John and Fabian had worked together on ArVerify. One weekend in February, they stumbled upon a Gitcoin bounty to archive Polkadot data on Arweave. They then created a simple script for the bounty. After talking to other major L1s, they realized this was a needed solution and decided to generalize and expand on the script, turning it into an incentivized network of nodes.

KYVE archives historical data from Solana and other chains. What do you see this being used for and what are the benefits to pull it from KYVE vs Solana?(ios0UNtRKai8QW_yn1VowKwAztsEf7qtj9iAsUtH0Ss)

The primary use case is incremental snapshots (expanded upon here). When you pull data from KYVE, you can be sure that it’s permanently stored as well as validated. This allows nodes to catch up faster with the current network state to load in historical data safely. Previously they had to rely on centralized snapshots where they were unsure if other parties might have modified the data.

What are your plans for 2k21 in terms of data science with the data of your backers? (vQNV1F0z-OtCyb6pgnBIZfKwINCCNcekwZrq9E--I5Y)

One thing we’re excited about is delivering customizable GraphQL APIs for the data we are archiving! This will allow developers to access their project’s data more dynamically and allows creative ways to display and work with data that is hard to access without KYVE.

Tagged with In No tags

Sign up for newsletter

Sign up here to get the latest news and updates delivered directly to your inbox.