The Ethereum protocol has been going through a lot of changes lately due to the barrage of DoS attacks on the network. However, the community behind the revolutionizing technology sees this as a positive circumstance because all of the changes made are simply more fortifications to make the platform stronger and more secure.
Since the DAO exploit occurred, the Ethereum community has come together to figure out ways to write better and more efficient code. And since the platform is still in development, any bug encountered and corrected, is a step closer to a finished product.
After the DoS attacks started in mid-September during Devcon2, Ethereum developers had to enact counter attacks which finally led up to their ultimate decision to hard fork the network as a final reprieve. Vitalik Buterin suggested that an EIP150 hard fork would be needed to repair the network, with a secondary fork after to shrink the size of the blockchain state. Just before 6:30 a.m. PST on Oct. 18, 2016, the network reached block 2463000, executing the first of two hard forks successfully.
Today, Oct. 28, 2016, the Ethereum team held a meeting that would discuss the secondary fork coming up. Hudson Jameson of the Ethereum Foundation released the following notes from the meeting:
Today core devs from every major client met to discuss the upcoming hard fork. Consensus was reached that the following EIPs will be implemented in the upcoming hard fork.
- EIP 155 - Simple replay attack protection
- EIP 160 - EXP cost increase
- EIP 161 - State trie clearing (invariant-preserving alternative)
The hard fork block number will be decided on Monday based on analysis over the weekend of the time needed to write the code and write/perform tests.
What do I need to do?
Users: Check frequently for updates to your Ethereum client. If you are using a third party to use Ethereum (web wallets, exchanges, etc.) the third parties will be responsible for upgrades on their backend systems and you shouldn't need to perform any actions.
Developers: Please review the specifications defined in the EIPs and the PRs from various clients that are implementing the hard fork.