Parity and Geth, Ethereum’s dual categorical clients, went out of synch during around 3PM London time today, incidentally formulating dual bondage handling in parallel. As such, Ethereum’s blockchain now is not in consensus. Users, generally exchanges, are strongly urged to refrain from transacting or to wait for a really high series of confirmations until a matter is resolved.
Developers are now operative as a matter of coercion to solve a emanate with a resolution to be approaching within hours.
Nick Johnson, one of a categorical developers of a Geth client, settled to CCN:
“The base means is an corner box around a state clearing; if an dull comment is ‘touched’ so that it would routinely be removed, though a call that ‘touched’ it goes out of gas, Geth will still mislay that comment from a state, while Parity will not.
The EIP doesn’t categorically state one or a other is correct, though everyone’s concluded that Parity’s doing creates some-more sense. Not categorically spelling this out in a standard, and not essay a accord exam for this edge-case