AN

KYVE Boosts Protocol’s Security, Adds New Feature In Seventh Protocol Update

0 249

The KYVE Protocol has taken a new look following the latest update which integrates the latest Cosmos SDK and restructured codes to make the protocol more secure with feature-filled user interface, the firm announced on Monday stating that the update is the last component to officially set a feature freeze.

KYVE, a Web3 data lake solution and protocol enabling data providers to standardise, validate and store blockchain data streams, said the upgrade which is on testnet, is a product of months of hardwork involving its engineers and beta testers who helped the team to identify bottlenecks and perfect the release.

Fabian Riewe, co-founder of KYVE, told Arweave news that KYVE’s solution is customisable and once it is mainnet, it will be able to handle both Web2 and Web3 data and any developer would be able to use the project’s Data Pipeline product to access and incorporate KYVE data into their project, research and analyses. He said that the firm was in talks with several companies to provide them its solution.

We are already speaking with several Web2 companies and really looking forward to providing this solution to their users and partners very soon, Riewe said.

The protocol said its engineering team integrated the latest Cosmos SDK version 0.46 and IBC version 5.x.x for security and functionality reasons. Before it upgraded to the latest Cosmos SDK, only one transaction could take place per governance proposal, KYVE said, adding that the update makes multiple transactions possible in one proposal by putting in place a streamlined proposal process. Gas price feature which was existing in version 45 was also implemented.

KYVE was one of the first projects to upgrade to the latest Cosmos SDK version… integrating these new releases brought on a few new exciting opportunities for KYVE, and shows our proactivity in the Cosmos ecosystem, it said.

The protocol took the decision to split the only module for managing all its major features because it had grown and become “overbearing for the chain’s and protocol’s workflow”. This resulted in the team implementing what it called module refactoring to improve the management of features and maintain code and ensure scalability.

The goal (of refactoring) was to enable KYVE’s features to be self-contained within specific modules, only exporting a fixed set of clearly defined functions to be used between each other, KYVE said.

The restructuring effort resulted in KYVE been divided into modules including, pools, which manages funders, pool configurations, alongside KYSOR upgrades; Stakers, which manages stakers with configurations such as moniker and logo; delegation, which manages delegation-related activities including rewards payouts and slashing; bundles, which coordinates bundle activities such as voting; X/group, which allows multi-sigs to exist on-chain in a very transparent way.

The protocol’s security also got some attention with the creation of inter-pool security. This feature allows every staker to join multiple pools simultaneously but are required to specify valaddress or address for the node which will be allowed to vote in favour of the actual staker. The staker has their private key kept safe in case the server gets compromised. The security feature comes with a check on delegators which subjects them to slashing.

“This not only streamlines the usability for validators and increases their opportunities for rewards, but also increases the overall network stability and security,” Riewe said about the inter-pool security and added that the user interface on the KYVE app has been updated to accompany this feature now allowing users to have a full overview of all validators on the app making it easier to navigate through.


Join our

Telegram / Discord / Twitter

Leave A Reply

Your email address will not be published.