51 large

关于硬分叉的最新进展

rubyu2 · 于 发布 · 最后由 blueboy回复 · 4868 次阅读

Digix对硬分叉保持中立态度

https://medium.com/@Digix/soft-hard-no-fork-and-will-it-affect-digix-7cdcebf495c#.5apfzgu4a

DigixGlobal 对硬分叉或不分叉保持中立态度,希望问题得到尽快解决,这样对整个生态系统都有益处。


最新的 1.4.9 go-ethereum 客户端已经回滚了原来的软分叉代码

https://github.com/ethereum/go-ethereum/releases/tag/v1.4.9


官方pyethereum代码库已经出现硬分叉的代码
https://github.com/ethereum/pyethereum/commit/611252b630981a93bd348cc3ed155a75ad71158b


ethcore表示将在下周新版的Parity客户端出现硬分叉的选项
https://blog.ethcore.io/the-dos-vector-and-the-soft-fork-for-miners/

https://github.com/ethcore/parity/pull/1483/files

持续更新中...

  • 5 large
  • 5 large
    shaoping

    https://twitter.com/VitalikButerin/status/748152656732921856

    安全重要。匆忙硬分叉,如果搞砸了,后果会很坏。

  • 5 large
  • 51 large
  • 87 large
  • 5 large
    shaoping

    THE DAO发布官方博客:https://blog.daohub.org/the-next-steps-part-3-6ddaf96962dc

    In short, the proposed hard fork solution will replace the code of The DAO and any child DAOs with a simple withdraw only contract; allowing DAO token holders to withdraw their relative portion of the ether held by The DAO into their ethereum address. There is, however, some ongoing discussion regarding how to deal with legitimate split DAOs, other DAOs created using the same code, etc.
    In order to avoid unnecessary complexity, the hard fork needs to be implemented prior to July 15th (the earliest date at which the attacker could begin withdrawing ether from the DarkDAO).

  • 5 large
    shaoping

    Slock.it在最新博客(https://blog.slock.it/options-in-the-hard-fork-90e467483c0
    )中指出,硬分叉方案中还有三个主要问题尚未达成共识:

    1、处理所有的DAO(母DAO、黑客DAO、所有其它合法子DAO)合约中的以太币还是只处理母DAO、黑客DAO中的以太币。

    2、如何处理extraBalance中的以太币

    3、是否搁置以太币提取机制细节,将所有的以太币都放到一个多重签名地址,然后通过第二次硬分叉解决。

    针对第一个问题,有以下两个选择:

    a) 处理所有的DAO合约中的以太币

    b)只处理母DAO和黑客DAO中的以太币。

    针对第二个问题,有以下四个选择:

    a) 将extraBlance账户中的以太币平分给所有的DAO代币持有者。

    b) 允许DAO代币持有者将他们的extraBalance份额捐赠给“某个账户”。

    c) 将extraBalance中的以太币放到一个多重签名地址,以后再处理,但是需要某人或者组织出面承担处理这笔以太币的责任,现在没人出面。

    d) 为了争取更多的时间分析如何重新通过另一次硬分叉分配extraBalance中的以太币,将extraBalance中的以太币放到一个没人可以控制的合约中,以后再处理。

    针对第三个问题,有以下三个选择:

    a) 将以太币放到一个可信的多重签名地址中,然后由这个地址管理以太币赎回。问题是:谁应该拥有该多重签名地址的私钥?

    b)将所有的以太币放到一个没人可以控制的合约中,然后再进行一次硬分叉。

    c)现在就就解决所有问题,不要再搁置。

  • 128
    dodo333

    c)现在就就解决所有问题,不要再搁置。

  • 51 large
    rubyu2

    最早在软分叉的时候,就有人提过关于extraBalance如何处理的问题。

  • 5 large
    shaoping

    Ethcore发表博客,支持硬分叉:https://blog.ethcore.io/in-support-of-a-hard-fork/

  • 5 large
    shaoping

    @shaoping 根据Slock再次更新的博客 https://blog.slock.it/dao-token-holder-update-ed12de7adec4 , 第一个问题很可能选择b选项,第二个问题还没有有定论,第三个问题很可能选择c选项。如果硬分叉实施,并成功,DAO持有者可以将DAO代币换成ETH,兑换比例:100DAO = 1ETH

    如果你在黑客攻击前合法地分割了DAO,形成了自己的子DAO(childDAO),你最好的做法是将你个人的以太币地址添加到白名单,然后提交一个提案,将子合约中的以太币发到自己的白名单地址。如果没人在你的子合约中创建一个新的监管者提议(curator proposal),你的币就可能是安全的。

    以上为博客核心内容摘要,细节问题,请阅读原文。

  • 5 large
    shaoping

    Slock.it开发者在reddit上回帖说,如果实行硬分叉,最有可能的时间是7月21号。
    https://www.reddit.com/r/ethereum/comments/4sp9p4/8_days_remaining_requesting_an_update_on_hf/d5b542t?st=iqlmup2j&sh=f15cfe93

    分叉客户端已经开发完成,正在测试。同时,开发者也在分析区块链,以确保所有的攻击者DAO都在将要被硬分叉的列表中。白帽小组罗宾汉团队也在构建安全网络中。

  • 5 large
    shaoping

    硬分叉将在第1920000个区块上进行,即7月20日。

    支持硬分叉的客户端应该很快就会发布。

    https://www.reddit.com/r/ethereum/comments/4stiuh/dao_hardfork_implementations_almost_ready/

  • 5 large
    shaoping

    以太坊官方发布博客(https://blog.ethereum.org/2016/07/15/to-fork-or-not-to-fork/ ),将以CarbonVote(http://carbonvote.com/ )在第1894000个区块的统计结果作为客户端是否默认硬分叉的依据。

    目前有80%投票支持硬分叉。关于如何参与CarbonVote投票,请看这个帖子:http://ethfans.org/topics/431

  • 5 large
    shaoping

    第1894000区块时87%投票同意主持硬分叉,所以Geth硬分叉客户端将把硬分叉设为默认值。

  • 51 large
    rubyu2

    最新版的go-ethereum昨天晚上已经发布,默认是支持硬分叉的。


    https://github.com/ethereum/go-ethereum/releases/tag/v1.4.10

    Geth 1.4.10 "Return of the ETH" is the go-ethereum team's DAO hard-fork implementation. It enables anyone to choose whether they would like to support the DAO hard-fork or oppose it, and take them to their blockchain of choice.

    To support the DAO hard-fork, start Geth with --support-dao-fork
    To oppose the DAO hard-fork, start Geth with --oppose-dao-fork
    On startup (on the main network) Geth will print the currently configured choice, which you can freely change with the appropriate flag at any time. If neither of the above flags is specified, the previous configuration is used. If no fork choice was ever provided, Geth will default to supporting the fork per the majority vote.

  • 5 large
    shaoping

    如果你从官方下载速度慢或者下载不了(国内防火墙原因),可以从国内镜像下载:http://ethfans.org/wikis/Ethereum-Geth-%E5%9B%BD%E5%86%85%E9%95%9C%E5%83%8F%E4%B8%8B%E8%BD%BD

  • 51 large
    rubyu2

    硬分叉如果出现两个并行链可能会导致重放攻击,建议大家紧跟 winning chain!!

  • 51 large
    rubyu2

    FOR IMMEDIATE RELEASE

    THE UPCOMING ETHEREUM HARD FORK

    The Ethereum Foundation has proposed a hard fork in response to the DAO exploit, and the community has given this decision the green light. The hard fork will occur at block 1,920,000 on or around Wednesday, July 20th.

    Since the selection of the winning blockchain is ultimately up to the miners, we will follow the path determined by the miners and the community and make plans to deprecate the losing blockchain.

    As a Poloniex customer, you do not need to do anything. The migration will occur automatically, and your full balance of Ethereum will be transferred to the winning chain. Keep in mind that as we near the fork, we will be temporarily disabling deposits and withdrawals in preparation for the migration process. Trading will continue to operate as normal during this period. Once the network is stable and the migration is complete, we will enable deposits and withdrawals.

    In addition, for those interested in keeping their tokens from the losing blockchain as a keepsake, we will support a one-time withdrawal of the deprecated tokens, provided that the losing chain is still functional when you attempt a withdrawal. Specific instructions on how to access your tokens on the old chain to follow.

    For More Information

    Statement from the Ethereum Foundation
    Ethereum Hard Fork Countdown

    ===
    P网发声明,在分叉阶段临时停止deposits and withdrawals

  • 51 large
    rubyu2

    The current implementation relies on the integrity of the old DAO's token management. I find this quite dangerous. Philosophically, if we were unrolling the hard fork solely because "a hacker took advantage of a small reentrancy bug," then it would make sense to rely on the old token accounting -- after all, the old DAO would be perfectly fine, save for one minor glitch, and we'd be fixing just that one minor glitch. But that's not true and that's not why I advocated a hard fork. In fact, this kind of case-by-case, narrow thinking is precisely what got us into trouble. I believe the hard fork is called for because the old DAO is bug-ridden at multiple levels. Consequently, my starting assumption, that we treat the entirety of the old DAO as untrustworthy, motivates a different strategy.


    有人指出,提款合约依赖于原有的DAO token管理,可能存在隐患。

    http://hackingdistributed.com/2016/07/19/how-ethereum-hard-fork-can-fail/

  • 378 large
    blueboy

    @rubyu2 不用担心,万一丢了,再来一次硬分叉就好了,完美解决。

  • 128
    khorkoko

    其实我还是不懂硬分叉软分叉是什么。 有谁可以解释一下吗?
    我之前持有的DAO现在要做什么动作吗?

  • 378 large
    blueboy

    http://carbonvote.com/ 刚回顾了一下这个网站,总投票币才453万,弃权率极高,闭着眼算也是90%以上,居然就说有效投票,匆匆分叉了。。。。。怎么说呢。。。。能不分裂吗。。。。