https://np.reddit.com/r/ethereum/comments/4pc6yh/white_hat_siphoning_has_occurred_what_now/
eze111 7 points 33 minutes ago
Hard Fork recovery:
"The timeline for such a scenario would be relatively short; 12 weeks to implement and test the hard fork code and then another week for the community to update their clients. So after 3 weeks the refund process for all DTHs could start and everyone would get 100% of their ETH back in a guaranteed fashion."
Targeted Soft Fork recovery:
White Hat DAOs (7,630,479 ETH) in 38 days
Dark DAO (3.64 mil ETH) in 71 days
Small Dark DAOs (
ETH) in 71 days
Extra Balance (344,907 ETH) in 14 days
Im not sure on the accuracy of these dates.
I have been reading alot and i think its now time to hardfork and end all this.
The hardfork will bring many updates which will make ETH much stronger than it has ever been.
is there a link that shows what the hf or sf will implement? eze111 7 points 33 minutes ago
Hard Fork recovery:
"The timeline for such a scenario would be relatively short; 12 weeks to implement and test the hard fork code and then another week for the community to update their clients. So after 3 weeks the refund process for all DTHs could start and everyone would get 100% of their ETH back in a guaranteed fashion."
Targeted Soft Fork recovery:
White Hat DAOs (7,630,479 ETH) in 38 days
Dark DAO (3.64 mil ETH) in 71 days
Small Dark DAOs (
ETH) in 71 daysExtra Balance (344,907 ETH) in 14 days
Im not sure on the accuracy of these dates.
I have been reading alot and i think its now time to hardfork and end all this.
The hardfork will bring many updates which will make ETH much stronger than it has ever been.
and do we know who will code this now ?
I believe this is the soft-fork implementation
https://github.com/ethereum/go-ethereum/pull/2715/commits/0bab00ab697b3a37af52d5908ebe799c9fbdbb9e
They added a generic blacklist, so they can add more transactions that they deem unwanted or suspicious in the future, so at any point they could decide you contract is unwanted and block miners from processing it.
Code:
IllegalCodeHashesFlag = cli.StringFlag{
Name: "illegal-code-hashes",
Usage: "Comma separated list of code-hashes to ignore any interaction from",
}
Name: "illegal-code-hashes",
Usage: "Comma separated list of code-hashes to ignore any interaction from",
}
but its ok, cause the called it a whitelist in code, so its no longer a blacklist, right?
Code:
daoHash = common.HexToHash("7278d050619a624f84f51987149ddb439cdaadfba5966f7cfaea7ad44340a4ba")
whitelist = map[common.Address]bool{
common.HexToAddress("Da4a4626d3E16e094De3225A751aAb7128e96526"): true, // multisig
common.HexToAddress("2ba9D006C1D72E67A70b5526Fc6b4b0C0fd6D334"): true, // attack contract
}
whitelist = map[common.Address]bool{
common.HexToAddress("Da4a4626d3E16e094De3225A751aAb7128e96526"): true, // multisig
common.HexToAddress("2ba9D006C1D72E67A70b5526Fc6b4b0C0fd6D334"): true, // attack contract
}
LMAO
is slockit involved in the coding ?
and why do we not ask who is the so called attacker ?