Skip to content

Security Alert: Ethereum Constantinople Moratorium

Ethereum Core builders and the Ethereum safety neighborhood have been made conscious of potential points associated to Constantinople chain safety on January 15, 2019. We’re investigating any potential vulnerabilities and can present updates on this weblog put up and on social media channels.

Utilizing excessive warning, key stakeholders within the Ethereum neighborhood have decided that the very best plan of action can be to delay the deliberate Constantinople Fork which can happen on January sixteenth, 2019 at block 7,080,000.

This may require anybody working a node (node ​​operators, exchanges, miners, pockets providers, and so forth…) to replace to a more recent model of Geth or Parity earlier than block 7,080,000. Block 7,080,000 will happen in roughly 32 hours from the time of this publication, or roughly January sixteenth, 8:00PM PT / January sixteenth, 11:00PM ET / January seventeenth, 4:00AM GMT.

what you might want to do

If you’re somebody who solely interacts with Ethereum (you do not run a node), you needn’t do something,

Miners, Exchanges, Node Operators:

  • Replace your Geth and/or Parity situations as they’re launched.

  • These releases aren’t but launched. We’ll replace this put up once they grow to be accessible.

  • Hyperlinks and model numbers and directions will probably be offered right here once they grow to be accessible.

  • We count on the up to date releases to be out inside 3-4 hours of this weblog being revealed.


  • improve to 1.8.21 Or

  • downgrade geth 1.8.19Or

  • Keep on 1.8.20, however use the ‘–override.constantinople=9999999’ swap to postpone the Constantinople fork indefinitely.


everybody else:

Ledger, Trezor, Protected-T, ParitySigner, WallEth, PaperWallet, MyCrypto, MyEtherWallet and different customers or token holders who don’t take part within the community by syncing and working a node.

  • You should not have to do something.

contract proprietor

  • You should not have to do something.

  • It’s possible you’ll select to look at the evaluation of potential vulnerabilities and look at your contracts.

  • Nevertheless, you do not want to do something as a result of the change that will introduce this potential vulnerability is not going to be enabled.


by article chain safety An in-depth examination of how sensible contracts could be checked for potential vulnerabilities and vulnerabilities. very briefly:

  • EIP-1283 Cheaper gasoline value launched for SSTORE operations

  • Some sensible contracts (these which are already on chain) could use code patterns that can make them susceptible to re-entry assaults after the Constantinople improve.

  • These sensible contracts could not have been susceptible earlier than the Constantinople improve

Contracts which are most probably to be susceptible are contracts that use the switch() or ship() features after a state-change operation. An instance of such a contract can be one the place two events collectively obtain cash, resolve the right way to divide mentioned cash, and start paying these funds.

How was the choice to postpone the Constantinople fork come about?

Safety researchers like ChainSecurity and TrailOfBits ran (and are nonetheless working) evaluation on all the blockchain. They did not discover any instances of this vulnerability within the wild. Nevertheless, there may be nonetheless a non-zero threat that some contracts could also be affected.

As a result of the chance is non-zero and the time required to find out the chance with confidence exceeds the period of time accessible earlier than the deliberate Constantinople improve, out of an abundance of warning it was determined to postpone the fork.

The events concerned within the dialogue included, however weren’t restricted to:

Response Time

3:09 am PT

  • ChainSecurity Responsibly Discloses Potential Vulnerability By means of Ethereum Basis’s Bug Bounty Program

8:09 am PT

  • Ethereum Basis asks ChainSecurity to publicly disclose

8:11am PT

  • Authentic article is revealed by ChainSecurity

8:52 am PT

8:52 AM PT – 10:15 AM PT

  • Numerous channels talk about potential dangers, on-chain evaluation and what steps should be taken

10:15 a.m. PT – 12:40 p.m. PT

  • Dialogue by way of Zoom audio name with key stakeholders. Dialogue continues on gittar and different channels as effectively

12:08 PM Fri

  • It was determined to delay the Constantinople improve

1:30 p.m. PT

  • Public weblog put up launched on numerous channels and social media

This text was put collectively in a collaborative effort by EvanVanNess, Infura, MyCrypto, Parity, standing, The Ethereum Basis, and Ethereum Cat Herders.

Ready to get a best solution for your business?