KYVE Reveals Plans To Remove Barriers To Data Pool Creation
A feature that will allow anyone to directly create a data pool of valid data for the public on KYVE infrastructure is being planned, its co-founder Fabian Riewe said on Thursday, an innovation which removes the barrier of having to secure governance approval to create a pool.
Riewe said during an interview with the Open Data Community that governance approval was necessary for curation noting that it could impede the desire of some to explore data but that KYVE was working to make data pool creation easier.
A pool has to go through governance to ensure that the runtime works without problems and will not crash all the time, as well as of course to ensure that governance agrees to launch the pool, Riewe told Permaweb News.
He said that making governance approval a requirement for data pool creation was a decision taken at the early stage of the network to ensure a smooth and secure start for the protocol layer.
Riewe told Permaweb News that the extent to which the idea would go would be decided on and how it is implemented could change.
The protocol layer and the consensus layers make up the KYVE blockchain architecture. The protocol layer is made of data pools with subset of certain data types.
KYVE said that there are 50 validators operating within data pools and performing the role of uploading and validating. While one validator in a pool is randomly selected to source and upload the next block of data, other validators vote whether the data is valid or not. Validators get incentives for the work they do
On KYVE’s token economics, apart from the staking and governance use cases, Riewe said that the funding mechanism of the utility of the token is unique. The mechanism encourages a system where the KYVE token is utilised at different points in its process from data pool creation and constant funding to incentivising validators and streams of data making it to the archive.
Riewe said that KYVE is decentralised to the level of the team being unable to implement some proposals without getting the community’s approval. The question about when in a project’s life should decentralisation take place is divisive in the Web3 space, including Arweave. Riewe said he is a defender of the belief that it is difficult to decentralise over time if a project, especially those that provide infrastructure service, did not start decentralised.
And so I think it’s definitely on our roadmap to decentralise every aspect of KYVE, especially also the marketing and non-tech aspect, he said.
Meanwhile, KYVE announced that blockchain exploration platform, View Block, now supports the protocol. The support will allow users to view real time stats of KYVE’s network, track data pool activity, blocks and data bundles.