As many of you may know the news is that an attacker was able to remove funds to a Child DAO.

Every conceivable option is being widely debated throughout the community, no definitive option has been adopted at this time.
(last update 14.00pm 19/06)

Possible Options At This Time

  1. Develop a method to recover the Ether
  2. Offer a bounty for the return of the Ether
  3. Perform a soft fork
  4. Perform a hard fork
In a Critical Update (17/06) Vitalik Buterin said:-

“..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…”

https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability/

from Vitalik Buterin via Reddit:-

“I personally believe that the soft fork that has been proposed to lock up the ether inside the DAO to block the attack is, on balance, a good idea, and I personally, on balance, support it, and I support the fork being developed and encourage miners to upgrade to a client version that supports the fork.”

Read more

The destination of the Attack
https://etherscan.io/address/0x304a554a310c7e546dfe434669c62820b7d83490

“A Fork in the Road”

Stephan Tual, Slock.it Founder, Former CCO Ethereum.

“The months of hard work and extraordinary goodwill thousands of individuals had poured into building the first large scale Decentralized Autonomous Organization were wiped away in an instant. To me personally, it was unfathomable that we’d have to turn back the clock on an entity designed to give considerable — even transformational — resources Ethereum based startups and projects.”

Read the full article

Ethcore Response on What Can Be Done

https://blog.ethcore.io/our-dao-response-2/

“Ideally, the DAO developers will find a way to extract the stolen funds without any protocol alterations (aka “hard fork”). However, such a plan, if feasible, will take time to design, test and deploy. If not feasible, an alternative approach will have to be found, quite possibly a minor hard-fork of the core protocol. Either way we have to limit the damage being done – the fastest, most effective way of doing this is through a temporary soft-fork.”