POCKET CHANGELOG V0.2.1

Jeremy Beal
Pocket Network

--

OVERVIEW:

The Pocket team is pleased to announce that we have successfully completed a protocol update making the network as stable as ever, as well as, making updates to our Pocket-js library, web3 provider, and others!

Last, but not least, we have pushed the long-awaited integration with the ICON network!

On March 31st, we rolled out the following fixes and enhancements:

RC-0.2.1:

Though the network is now on RC-0.2.1, this section is to highlight both releases to see what has been updated and enhanced.

RC-0.2.0 has a suite of updates that can be found here, but one of the most noticeable features is the challenge request. This will allow the client(applications) to challenge a node if it returns bad data, thus keeping the nodes accountable and slashing the misbehaved node.

RC-0.2.1 is to fix a bug that allowed nodes to double sign for invalid relays/operations which caused a consensus break on the network. This update also contains an enhancement to improve the user experience by adding protocol versioning to the CLI and an RPC call.

POCKET-JS:

You can find the whole list of updates here, but two of the biggest milestones that were accomplished were adding challenge transactions and local consensus.

If a Node returns a bad/ incorrect data, the client(application) can create a challenge transaction which will slash the node’s stake if it is being a bad actor.

Last is the local consensus. Developers can now choose the number of nodes to query with each relay to ensure data integrity.

DOCKER AND HOMEBREW DEPLOYMENTS:

Docker and Homebrew deployments have gone through an update to ensure every container and installation will be pointing at the correct network for RC-0.2.1.

CONCLUSION:

As we continue to increase the stability and reliability of the Pocket protocol, we will be keeping you up to date with the latest information on our Discord, Telegram, and blog.

If you are a node operator, developer, or both feel free to contact me @Germany#9861 in the #support channel on discord, and I will make myself available to help in any way possible.

--

--