The DAO, although not a creation of the Ethereum Foundation, has emerged as a prominent subject recently, both within the organization and among our community. The Hard Fork is a sensitive subject and in our perspective, there is no definitive right choice. Since this is not a resolution that can be determined by the foundation or any solitary entity, we once more appeal to the community to gauge its preferences to deliver the most suitable protocol modification.
The configuration suggested for the hard fork that is being rolled out in the Geth client is as follows:
The DAO (0xbb9bc244d798123fde783fcc1c72d3bb8c189413), its additionalBalance (0x807640a13483f8ac783c557fcdf27be11ea4ac7a), all offspring of the DAO creator (0x4a574510c7014e4ae985403536074abe582adfc8) and the additional balance of each offspring are stored in a list L at block 1880000. The details of L can be observed here. At the commencement of block X (X = 1920000, on July 20 or 21 depending on your region), all ether across all accounts in L will be moved to contract account C, located at (0xbf4ed7b27f1d666546e30d74d50d173d20bca754). You can verify the solidity source code of C on etherscan. From this contract, DAO token holders can submit their DAO in order to withdraw ETH at a rate of 1 ETH = 100 DAO. The additional balance, along with some leftover ether resulting from issues in the interactions between the re-entrancy exploit and the division mechanism, will be retrievable by the DAO curator to be allocated accordingly to address all edge cases.
Further details to aid in confirming the fork specs and execution are anticipated to be published separately by the community; consensus code in Geth that enacts the fork logic is encompassed by the bug bounty program.
Regrettably, time constraints necessitate quick acceptance before any protocol change becomes unfeasible. The community tool carbonvote will be utilized to establish the default fork choice for Geth. At block number 1894000 the votes will be counted, and the result will dictate whether the default is set to fork or not to fork. Following that, combining the DAO fork PRs will commence, soon to be followed by a release for both Geth and Mist. Users with crucial business applications who must update swiftly should regularly monitor the blog and social media for continuing updates.
