ChildDAO Update

Griff Green
Curator Multisig PHF Official Channel
2 min readAug 13, 2016

The first childDAO withdraw contract that was developed by the community was a work of art put together by Paul Szczesny (@paulsz) and friends on The DAO Slack’s #child_DAO_community channel, Christoph Jentzsch also created a very nice smart contract to refund the childDAOs, however both of these contracts were a little bit complex and required extensive auditing before they could be funded.

Alexey Akhunov (@ledgerwatch) took the heavily audited Hard Fork Withdraw Contract and after a couple iterations determined to do only 1 variable change: exchanging The DAO’s address for the applicable childDAO’s address. He then took it upon himself to deploy a withdraw contract for every pre-attack DAO that did not withdraw it’s ether successfully before the Hard Fork.

There have already been two apparently successful implementations of @ledgerwatch’s simple withdraw contract for pre-attack childDAOs! The Curator multisig sent 5.01 ETH to childDAO # 52’s withdraw contract and 5.01 ETH to childDAO #56’s withdraw contracts and both contracts were successfully used by the childDAO token holders to extract the appropriate amount of ether expected given the number of DAO tokens they burned and the Curator multisig was able to extract the leftover ether above and beyond that, just as in the hard fork contract.

Several other childDAOs have performed independent tests on their Withdraw Contracts and so far every test has been successful!

The next step is to continue to verify that the contracts @ledgerwatch deployed are correct and once they are verified we will send ether to them!

The childDAOs that have performed self-tests will be the next to be verified and sent ether:

Proposal 27’s childDAO and it’s Withdraw Contract

Proposal 29’s childDAO and it’s Withdraw Contract

Proposal 34’s childDAO and it’s Withdraw Contract

Proposal 39’s childDAO and it’s Withdraw Contract

Proposal 63’s childDAO and it’s Withdraw Contract

Proposal 64’s childDAO and it’s Withdraw Contract

If you would like to help verify these contracts are valid you can do very basic blockchain analysis to check for any unique attributes that need to be noted (such as childDAO #29 received a 2 ETH proposal deposit). If you have checked a childDAO Withdraw Contract, please show write a comment in the checker box on the first tab of the ChildDAO Recovery Spreadsheet.

--

--