The Ethereum community might be present process a tough fork at block quantity 2,675,000, which can probably happen between 15:00 and 16:00 UTC on Tuesday, November 22, 2016. A countdown timer will be seen at https://fork.codetract.io/. The Morden check community might be present process a tough fork at block number one,885,000.
As a person, what do I have to do?
Obtain the most recent model of your Ethereum consumer:
What occurs if I don’t replace my consumer?
If you’re utilizing an Ethereum consumer that isn’t up to date for the upcoming arduous fork, your consumer will sync to the pre-fork blockchain as soon as the fork happens. You’ll be caught on an incompatible chain following the previous guidelines and you’ll be unable to ship ether or function on the post-fork Ethereum community.
Importantly, in case your consumer is just not up to date, it additionally signifies that any transactions you make will nonetheless be vulnerable to replay assaults.
What if I’m utilizing an online or cellular Ethereum pockets like MyEtherWallet or Jaxx?
Ethereum web sites and cellular functions that help you retailer ether and/or make transactions are working their very own Ethereum consumer infrastructure to facilitate their companies. Typically, you don’t want to do something in the event you use a 3rd get together net primarily based or cellular Ethereum pockets. Nevertheless, it is best to nonetheless examine along with your net or cellular Ethereum pockets supplier to see what actions they’re taking to replace for the arduous fork and if they’re asking their customers to take different steps.
Particularly, it is best to be sure that transactions are generated with the brand new replay-protected EIP 155 scheme.
What do I do if my Ethereum consumer is having bother syncing to the blockchain?
Be sure you have downloaded the most recent model of your Ethereum consumer.
Why are we proposing to arduous fork the community?
“Spurious Dragon” is the second arduous fork of the two-round arduous fork response to the DoS assaults on the Ethereum community in September and October. The earlier arduous fork (a.ok.a “Tangerine Whistle”) addressed immediate network health issues due to the attacks. The upcoming arduous fork addresses essential however much less urgent issues reminiscent of additional tuning opcode pricing to stop future assaults on the community, enabling “debloat” of the blockchain state, and including replay assault safety.
What adjustments are part of this tough fork?
The next Ethereum Improvement Proposals (EIPs) describe the protocol adjustments applied on this arduous fork.
- EIP 155: Replay attack protection – prevents transactions from one Ethereum chain from being rebroadcasted on an alternate chain. For instance: In case you ship 150 check ether to somebody from the Morden testnet, that very same transaction can’t be replayed on the principle Ethereum chain. Essential notice: EIP 155 is backwards suitable, so transactions generated with the “pre-Spurious-Dragon” format will nonetheless be accepted. Nevertheless, to make sure you are protected towards replay assaults, you’ll nonetheless want to make use of a pockets answer that implements EIP 155.
Bear in mind that this backwards compatibility additionally signifies that transactions created from different Ethereum primarily based blockchains that haven’t applied EIP 155 (reminiscent of Ethereum Traditional) can nonetheless be replayed on the principle Ethereum chain. - EIP 160: EXP cost increase – adjusts the worth of `EXP` opcode so it balances the worth of `EXP` with the computational complexity of the operation, primarily making it tougher to decelerate the community by way of computationally costly contract operations.
- EIP 161: State trie clearing – makes it potential to take away numerous empty accounts that had been put within the state at very low price because of earlier DoS assaults. With this EIP, ’empty’ accounts are faraway from the state every time ‘touched’ by one other transaction. Elimination of the empty accounts significantly reduces blockchain state measurement, which can present consumer optimizations reminiscent of sooner sync instances. The precise elimination course of will start after the fork by systematically performing `CALL` to the empty accounts that had been created by the assaults.
- EIP 170: Contract code size limit – adjustments the utmost code measurement {that a} contract on the blockchain can have. This replace prevents an assault situation the place giant items of account code will be accessed repeatedly at a hard and fast fuel price. The utmost measurement has been set to 24576 bytes, which is bigger than any at the moment deployed contract.
DISCLAIMER
That is an emergent and evolving extremely technical house. In case you select to implement the suggestions on this put up and proceed to take part, it is best to ensure you perceive the way it impacts you. You must perceive that there are dangers concerned together with however not restricted to dangers like sudden bugs. By selecting to implement these suggestions, you alone assume the dangers of the results.
