Prevent malleable transactions for services that operate with 0 confirmations
-
Check the Edit: of the http://forum.feathercoin.com/index.php?topic=6356.0 It has PoC PHP code that communicate with feathercoind.
-
Is this related to the Gox problem?
-
No, it has no relation with MtGox but have relation due to “issue” of malleable transactions and it’s possible impact on services that operate with 0 confirmations transactions that use incoming transaction id as identification of the payment or play round. I had that issue in my code and fix it. Press release of MtGox and all the responses from bitcoin dev. community just give all of us valuable lesson about implementation of bitcoin protocol based payment systems :)