Blockchain Network Bethereum’s founder Vitalik Buterin has released a plan for the first hard fork of the Beacon Chain ever (Ethereum 2.0).
Blockchain network Ethereum founder Vitalik Buterin released yesterday a plan for the first hard fork of the Beacon Chain (Ethereum 2.0). The preliminary name of the code is HF1. The main objectives of HF1 are to add support to the light-client and to fix some vulnerabilities in the Beacon Chain that have been discovered too late to be addressed in Genesis. In addition, the hard forking mechanism should be tested with a relatively small change before major changes such as sharding and merging need to be made. The plan also proposes a number of consensus changes with HF1.
Support for low clients will be created by a randomly selected sync committee.”
According to Vitalik Buterin‘s announcement, support for Light Clients – nodes with minimal resource requirements and which could run on mobile devices – will be created by a randomly selected “Sync Committee.” The purpose of this is to allow Light Clients to determine a chain header with a low overhead (~20 kB per day minimum to keep up, and ~500 bytes to verify a single block). This would make it possible for light clients to be viable for mobile devices, using cases such as the beacon chain in the browser.
The aim of HF1 is to mitigate the highly debated issue of slashing.
HF1 of Ethereum is intended to mitigate the issue that has been hotly debated for months, ‘slashing.’ Until now, it is the case on the Beacon Chain that validators may lose some of their ETH stakes in the event of inactivity, which has made them dangerous, especially for smaller ‘home players,’ as they are penalized for events that were not their fault, such as the internet or power outage. The aim of HF1 is further to mitigate this by distinguishing between intermittent and continuous inactivity. The objective of the hard fork is to mitigate this by distinguishing between intermittent and continuous inactivity.