Bitcoin 0.11.1 log

… is efficiently dealing with the malleability crap. Game over, scammers!

2015-10-26 18:57:10 UpdateTip: new best=00000000000018b239b6b746abb28e72542bfe297a395a188b6e36896f08828b  height=580086  log2_work=66.581085  tx=6317677  date=2015-10-26 18:54:53 progress=1.000000  cache=0.5MiB(2663tx)
2015-10-26 18:57:10 UpdateTip: 23 of last 100 blocks above version 3
2015-10-26 18:57:52 ERROR: AcceptToMemoryPool: inputs already spent
2015-10-26 18:58:59 ERROR: CScriptCheck(): 8babdcc397ee10dee940e04fd8edb6f8718498853bfe510db9c4fd11914cc650:0 VerifySignature failed: Non-canonical signature: S value is unnecessarily high
2015-10-26 18:58:59 ERROR: AcceptToMemoryPool: ConnectInputs failed 8babdcc397ee10dee940e04fd8edb6f8718498853bfe510db9c4fd11914cc650

Any chance of an explanation of what this means? Some background perhaps. I don’t know what the “game” was that is now over

Are you saying that bitcoin no longer has a “TransactionID”?

I mentioned it’s about transaction malleability, the years old annoyance that MtGox famously blamed their issues on, and that started being more attempted in recent weeks.
Finally they fixed it in 0.11.1 released very recently, because it became too annoying to everyone. The last 3 lines show how the scumbags are now dealt with: their attempts to create malleable transactions are recognized and rejected. I spotted the lines in my log after I updated earlier today.
So it’s game over for those who tried to exploit that, although it was never a huge problem.

It does, but if you transmit a tx with a fake ID (in the sense that it is txid that belongs to another transaction), it gets recognized and dealt with.

2 Likes

Wow WTF @janitor your really a codedigger. That’s indeed good news… Too bad that I took so long

1 Like