Jump to content
Sign Up To Remove Ads!


This topic is now archived and is closed to further replies. Want this topic removed from the archive?


Cryptocurrency Ethereum to do a Hard Fork on July 20th to resolve DAO exploit

Recommended Posts

 titanic1    244





Hello Community,
Both clients, Parity and Geth have a hard-fork implementation for The DAO now, which is not yet released but can be expected soon.
Both set the date of the hardfork to uuuBlock number 1 922 000.
This will be shortly before the 21.07., which is the date in which the attacker can split (See the important deadlines in this post by Christoph Jentzsch).
What does this mean for other clients?
Other clients like pyethereum, or libethereum already started their implementations of the hard-fork, so it is certain that they will release a new version including the hardfork with the same date.
What does this mean for me as token holder?
The funds of the whitehat DAOs and blackhat DAO will be moved to a withdrawal contract, in which one will be able to withdraw his or her share of Ether.



An attack has been found and exploited in the DAO, and the attacker is currently in the process of draining the ether contained in the DAO into a child DAO. The attack is a recursive calling vulnerability, where an attacker called the “split” function, and then calls the split function recursively inside of the split, thereby collecting ether many times over in a single transaction.

The leaked ether is in a child DAO at https://etherchain.org/account/0x304a554a310c7e546dfe434669c62820b7d83490; even if no action is taken, the attacker will not be able to withdraw any ether at least for another ~27 days (the creation window for the child DAO). This is an issue that affects the DAO specifically; Ethereum itself is perfectly safe.


A software fork has been proposed, (with NO ROLLBACK; no transactions or blocks will be “reversed”) which will make any transactions that make any calls/callcodes/delegatecalls that reduce the balance of an account with code hash 0x7278d050619a624f84f51987149ddb439cdaadfba5966f7cfaea7ad44340a4ba (ie. the DAO and children) lead to the transaction (not just the call, the transaction) being invalid, starting from block 1760000 (precise block number subject to change up until the point the code is released), preventing the ether from being withdrawn by the attacker past the 27-day window.This will provide plenty of time for discussion of potential further steps including to give token holders the ability to recover their ether.

Miners and mining pools should resume allowing transactions as normal, wait for the soft fork code and stand ready to download and run it if they agree with this path forward for the Ethereum ecosystem. DAO token holders and ethereum users should sit tight and remain calm. Exchanges should feel safe in resuming trading ETH.


Share this post

Link to post
Share on other sites