Topic: 比特币核心开发者GMAXWELL 对MTGOX问题的回应 (Read 527 times)

http://www.yibite.com/portal.php?mod=view&aid=1830

 比特币核心开发人员Greg Maxwell对Mtgox的事故做出了回应，Maxwell称此次事故是Mtgox自己内部系统的失误所引起的，而Mtgox却将次归咎为一个早在2011年就发现的问题。

The challenge for me in offering something here is that this isn’t news to me – for years – and it’s never been a particularly large concern. This wouldn’t make the top ten list of dangers in the Bitcoin technology.
      Greg Maxwell解释称，比特币钱包客户端的一些旧版本在处理未确认的交易时存在问题，但这个问题在2011年就已经发现了。这次的事故完全由Mtgox自己的内部系统造成。

      下面是Maxwell的回应原文。

      Greg Maxwell Responds

      I spoke with Bitcoin core developer, Greg Maxwell, about this highly technical issue. Greg Maxwell and Peter Wuille are the core developers in consultation with Mt. Gox, as per their press release.

      gmaxwell I am very unhappy with the ‘spin’ used in the Gox press release. They portray characteristics of the Bitcoin system well known since at least 2011 (which even have their own wiki page ) as something new. These characteristics are annoying but don’t inhibit basic operation, they are slowly being fixed – but fixing them completely will likely take years as they require changing all wallet software. Correctly written wallet software can cope with the consequences, and I cannot understand why they would gate their withdraws on external changes.

      GG Andreas Antonopolous has examined Gox’s code to some degree, and remarked that they are using a strange hodgepodge of methods to process transactions. Do you believe the problem lies in their code rather than the Bitcoin protocol?

      gmaxwell Oh there is a “problem” in the Bitcoin protocol, known since at least 2011 (see the link I gave). But for normal applications, not involving unconfirmed transactions, it shouldn’t cause any severe problems because wallets can handle it locally.

      Basically, third parties can change the transaction IDs of transactions. This means what wallet software must be written to accomodate that and still recognize them when that happens.

      What the press release talks about is adding a second kind of transaction ID, which is robust against changes, which would be helpful for tech support purposes. Though it doesn’t resolve all of the issues that being able to modify transactions presents.

      GG So in other words, Gox should be able to account for this known problem by modifying their internal systems?

      gmaxwell Yes, internal only changes should account for it. The only remaining issue for Mt. Gox’s application would be some tech support problems where if a users transaction is mutated by a malicious party the txid Mt. Gox told them to expect wouldn’t be the one that ultimately showed up in the blockchain.

      GG It seems the market is reacting very negatively to the news. What advice would you give to the average Bitcoiner regarding this situation?

      gmaxwell The challenge for me in offering something here is that this isn’t news to me – for years – and it’s never been a particularly large concern. This wouldn’t make the top ten list of dangers in the Bitcoin technology.