Sounds like a suboptimal solution to me.

https://www.reddit.com/r/ethereum/comments/4r9yud/the_current_hf_status/

1) The implementation has been largely spec-frozen to the following python:

# call before running transactions
def initialize():
    if state.block_number == DAO_HARDFORK_BLKNUM:
        for acct in HARDFORK_DAO_LIST:
            state.set_balance(HARDFORK_DEST, state.get_balance(acct) + state.get_balance(HARDFORK_DEST))
            state.set_balance(acct, 0)

However, the dev community is debating the simplest way to minimize risks of issues related to light client syncing. The actual logic that allows DAO token holders to claim their ether would be implemented in HARDFORK_DEST.

2) The ether claiming logic is largely a simple withdrawable token contract, but small details are being debated regarding how to deal with secondary daos, legit splits, etc. Note that this can proceed in parallel to (1), there are no sequential dependencies. Simplicity of the ether claiming contract is understood to be a very important concern.

3) Note that the above should absolutely not be taken as an official endorsement of hardforking by either the foundation, or ethcore/slock/string, or the individual devs involved; some of the devs involved are pro-fork and some are anti-fork, the goal is to give the community a choice.

 

Sounds like a suboptimal solution to me.