The Ethereum network will undergo a last fork in block number 2 675,000, which will probably occur between 3:00 p.m. and 4:00 p.m. UTC on Tuesday, November 22, 2016. A timing timer can be seen in https://fork.codestract.io/. The Morden test network will undergo a last fork in the number 1,885,000 block.
As a user, what should I do?
Download the latest version of your Ethereum client:
What’s going on if I don’t update my client?
If you use an Ethereum customer who is not updated for the next fork, your customer will synchronize with the blockchain before the sheath once the fork is. You will be stuck on an incompatible channel by following the old rules and you will not be able to send ether or operate on the Ethereum post-Fourré network.
Above all, if your customer is not updated, this also means that all the transactions you make will always be likely to replay the attacks.
What if I use an Ethereum web or mobile portfolio like Myetherwallet or Jaxx?
Ethereum websites and mobile applications that allow you to store Ether and / or make transactions run their own Ethereum customer infrastructure to facilitate their services. Generally, you have nothing to do if you are using an Ethereum web and mobile portfolio based on a third party. However, you should always check with your Ethereum web or mobile portfolio provider to see what actions they take to update for the hard fork and if they ask their users to take other measures.
In particular, you should make sure that transactions are generated with the new EIP 155 diagram protected by rereading.
What should I do if my Ethereum client has trouble synchronizing with the blockchain?
Make sure you have downloaded the latest version of your Ethereum client.
Why do we offer Frark Hid on the network?
“SPDINGIY DRAGON” is the second last fork of the response to two laps of the hard fork to the back attacks against the Ethereum network in September and October. The previous hard fork (alias “Tangerine Whistle”) addressed health problems of the immediate network due to the attacks. The next last fork deals with important but less pressing questions such as the adjustment of OPCODE pricing to prevent future attacks against the network, allowing the “unlocking” of the blockchain state and the addition of the protection of rereading attacks.
What changes are part of this hard fork?
What follows Ethereum improvement proposals (EIPS) Describe the changes in the protocol implemented in this hard fork.
- EIP 155: Replay Attack Protection – prevents transactions from an Ethereum chain from being criticized on an alternative chain. For example: if you send 150 ether tests to someone from the Morden Testnet, this same transaction cannot be replayed on the main Ethereum chain. Important note: EIP 155 is compatibleSo the transactions generated with the “pre-spurious-dragon” format will always be accepted. However, to ensure that you are protected against rereading attacks, you will always have to use a wallet solution that implements EIP 155. Know that this rear compatibility also means that transactions created from alternative blockchains based on Ethereum which have not implemented EIP 155 (like Ethereum Classic) can always be replayed on the main ethereum chain.
- EIP 160: Increase in Exp – Adjusts the price of the Opcode `Expi ‘so that it balances the price of Expi’ with the complexity of calculating the operation, which makes it essentially more difficult to slow down the network via expensive contract operations.
- EIP 161: Claimage of the state sorting – allows you to remove a large number of empty accounts that have been placed in the state at very low cost due to the front back attacks. With this EIP, the “empty” accounts are deleted from the state whenever “touched” by another transaction. The elimination of empty accounts considerably reduces the size of the blockchain state, which will provide customer optimizations such as faster synchronization times. The real withdrawal process will start after the fork by systematically “call” empty accounts that have been created by attacks.
- EIP 170: size of the contract code limit – Changes the maximum size of the code that a blockchain contract can have. This update prevents an attack scenario where major elements of account code are available on several occasions at a fixed gas cost. The maximum size has been set at 24576 bytes, which is larger than any contract currently deployed.
Non-liability clause
It is a highly technical and evolving highly technical space. If you choose to implement the recommendations in this article and continue to participate, you must make sure to understand how it has an impact. You must understand that there are risks involved, including, but without limiting themselves, risks like unexpected bugs. By choosing to implement these recommendations, only you assume the risks of the consequences.
