4 ms·
ok, but please read the related pull requests https://github.com/bitcoin/bitcoin/pull/2131 https://github.com/bitcoin/bitcoin/pull/2131 https://github.com/bit
by rjzzleep 13y ago
ok, but please read the related pull requests
https://github.com/bitcoin/bitcoin/pull/2131 https://github.com/bitcoin/bitcoin/pull/2131
https://github.com/bitcoin/bitcoin/pull/3637 https://github.com/bitcoin/bitcoin/pull/3637
https://github.com/bitcoin/bitcoin/pull/3016 https://github.com/bitcoin/bitcoin/pull/3016
https://github.com/bitcoin/bitcoin/pull/3025 https://github.com/bitcoin/bitcoin/pull/3025
- nullc 13y agoThese are not all that directly related— they're the start of a set of changes which will probably take us one to three years to fully deploy... what mtgox was talking about in their press releases was just some simple standard way of generating a stable ID, this wouldn't be a protocol change at all... and is only a few lines of code: https://github.com/sipa/bitcoin/commits/normtxid https://github.com/sipa/bitcoin/commits/normtxid But whats more important is that this malleability stuff is not very much related to fraud risk, I explained more here: http://sourceforge.net/mailarchive/message.php?msg_id=31956576 http://sourceforge.net/mailarchive/message.php?msg_id=319565...