Note: Due to a vulnerability of security, we postpone Constantinople. Please ignore the instructions for this blog article. Click here for more information.
The Ethereum network will be being upgraded to Block number 7,080,000which should occur on Wednesday January 16, 2019. The exact date is subject to modification according to block times by then and can be activated 1 to 2 days before or after. A countdown can be seen at https://amberdata.io/blocks/7080000. You can monitor the network upgrade in real time to http://forkmon.ethdevops.io/.
What is Constantinople?
Constantinople is the name given to this network upgrade. Previous network upgrades have received other names such as Parasitic dragon And Byzantium.
As an Ethereum user or Ether holder, is there anything I have to do?
If you use an exchange (like Coinbase, Kraken or Binance), a web portfolio service (like Metamask, Mycrypto or Myetherwallet), a mobile portfolio service (such as the Coinbase, Status.im or Trust wallet portfolio) ,, Material portfolio (like Ledger, Trezor or Keepkey), you have nothing to do unless you are informed to take additional measures by your exchange or wallet service.
As a knot or minor operator, what should I do?
Download the latest version of your Ethereum client:
What happens if I am a minor or a node operator and that I do not participate in the upgrade?
If you use an Ethereum customer who is not updated to the latest version (listed above), your customer will synchronize with the blockchain before the scabbard once the upgrade. You will be stuck on an incompatible channel by following the old rules and you will not be able to send an ether or operate on the Ethereum post-up to level.
What is a network upgrade in Ethereum-Land?
An upgrading of the network is a modification of the underlying Ethereum protocol, creating new rules to improve the system. The decentralized nature of blockchain systems makes a network upgrade more difficult. Network upgrades in a blockchain require cooperation and communication with the community, as well as with the developers of the various Ethereum customers so that the transition is going well.
What is happening during a network upgrade?
Once the community has concluded an agreement concerning the modifications which should be included in the upgrade, changes in the protocol are written in different Ethereum customers, such as Geth, Parity and Harmony. The protocol changes are activated to a specific block number. All the nodes that have not been upgraded to the new set of rules will be abandoned on the old chain where the previous rules continue to exist.
What changes go to Constantinople?
The changes implemented in Constantinople are defined using EIP. The proposals for improving ethereum (EIPS) describe standards for the Ethereum platform, including the specifications of the basic protocol, customer APIs and contractual standards. The following EIPs will be implemented in Constantinople.
EIP 145: Deposit instructions to bit in EVM
-
Provides a native discrepancy on the bit with an equal cost with other arithmetic operations.
-
EVM lacks offset operators to the way, but takes care of other logical and arithmetic operators. Deposit operations can be implemented via arithmetic operators, but this has a higher cost and requires more treatment time. The implementation of SHL and SHR using arithmetics costs each 35 gas, while these proposed instructions take 3 gases.
-
In short: this EIP adds native features to the protocol so that it is cheaper and easier to do certain things on the chain.
EIP 1014: Skinny Create2
-
Add a new OPCODE to 0xF5, which takes 4 battery arguments: endowment, memory_start, memory_length, salt. Behaves identically to the creation, except using Keccak256 (0xff ++ Sender_Address ++ Salt ++ Keccak256 (INIT_CODE))) (12 🙂 Instead of Keccak256 (RLP (Sender_Address, Nonce)) (12 🙂 The address of the address of the initialized contract to.
-
This makes it possible to make interactions with addresses which do not yet exist on the chain but which can be invoked to possibly contain only the code which was finally created by a particular initiation code.
-
Important for the use of state channels which involve counterfactual interactions with contracts.
-
In short: this EIP ensures that you can interact with addresses that have not yet been created.
EIP 1052: ExtCodehash Opcode
-
This EIP specifies a new Opcode, which returns Keccak256 hash to the code of a contract.
-
Many contracts must make checks on the Bytecode of a contract, but do not necessarily need the Bytecode itself. For example, a contract may want to verify whether the bytecode of another contract is part of an authorized set of implementations, or if it can carry out analyzes on the code and the white list any contract with corresponding bytecodes if the Analysis passes.
-
Contracts can currently do this using the Opcode of Extcodecopy, but it costs expensive, in particular for important contracts, in cases where only hash is required. Consequently, a new OPCODE is implemented called Extcodehash which returns the Keccak256 hatching of a contract.
-
In short: this EIP makes it cheaper (less gas is necessary) to do certain things on the chain.
EIP 1283: Net gas mixing for sstore without dirty cards
-
This EIP offers changes in net gas measurement for Sstore Opcode, allowing new uses for the storage of contracts and reducing excessive gas costs where it does not correspond to the operation of most of the implementation.
-
In short: this EIP makes it cheaper (less gas is necessary) to do certain things on the chain, especially things that are currently “excessively” costly.
EIP 1234: Constantinople Difficult Bombllay Distage and adjustment of the blocking award
-
The average blocking times increase due to the difficulty of bomb (also known as “the ice age”) accelerating slowly. This EIP proposes to delay the difficulty bomb for about 12 months and to reduce block rewards to adapt to the delay in the ice age.
-
In short: this EIP ensures that we do not freeze blockchain before proof of participation is ready and implemented.
THANKS!
A big thank you to the Ethereum community and to all the Ethereum developers of all the customers and platforms that have met to provide comments, thoughts and contributions. Special thanks to the user of Reddit Campecarlson who let us use His Post Reddit and the Mycrypto Team that let us use their “Ethereum Constantinople: everything you need to know“Average position.
Non-liability clause: It is a highly technical and evolutionary 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. This message and recommendations are not a sale of any kind and do not create any guarantee of any kind, including, but without limiting itself, to the Ethereum network or to Ethereum customers referred here.
