Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Troy Benjegerdes
Okay, why the everloving FUCK is there not someone on this list with a @mtgox.com address talking about this? I started using bitcoin because I could audit the code, and when the developer cabal does stuff 'off-list' what you do is hand over market manipulation power to the selected cabal of

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Nick Simpson
You must be new here. MtGox very rarely comments on things like this publicly, outside of irc or their website. Second, MtGox problem is a MtGox problem. You have no right to demand access to their private code. If you feel wronged as a customer, sue them. Otherwise, they have no obligation

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Troy Benjegerdes
I cannot judge the competence of code I've never seen, so I have no position on that. What I HAVE seen quite clearly is both overt and covert market manipulation under cover of blame for 'the developers', or 'the exchange' You're doing it yourself with the phrase 'incompetence'. When you run an

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Troy Benjegerdes
A bitcoin problem is not really my problem, and if MtGox's investors can't seem to understand the value of publishing their code, I'll be happy to take their money as it leaves bitcoin for more distributed and transparent cryptocurrency ecosystems. I feel some sort of moral obligation to point

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Oliver Egginger
Am 10.02.2014 13:28, schrieb Pieter Wuille: Hi all, I was a bit surprised to see MtGox's announcement. The malleability of transactions was known for years already (see for example the wiki article on it, https://en.bitcoin.it/wiki/Transaction_Malleability it, or mails on this list from

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Gregory Maxwell
On Mon, Feb 10, 2014 at 11:47 AM, Oliver Egginger bitc...@olivere.de wrote: As I understand this attack someone renames the transaction ID before being confirmed in the blockchain. Not easy but if he is fast enough it should be possible. With a bit of luck for the attacker the new transaction

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Tier Nolan
On Mon, Feb 10, 2014 at 7:47 PM, Oliver Egginger bitc...@olivere.de wrote: As I understand this attack someone renames the transaction ID before being confirmed in the blockchain. Not easy but if he is fast enough it should be possible. With a bit of luck for the attacker the new transaction

Re: [Bitcoin-development] Malleability and MtGox's announcement

2014-02-10 Thread Gregory Maxwell
On Mon, Feb 10, 2014 at 12:47 PM, Tier Nolan tier.no...@gmail.com wrote: If the attacker has a direct connection to MtGox, they can receive the transaction directly. MtGox had a php script that returned base64 data for all their stalled transactions. Not just attackers used that, some people