4 ms·
> (1) Find all confirmed transactions that have a signature that appears in non-canonical form (and thus likely confirmed under an unexpected TXID); Unfortunat
by nullc 13y ago
> (1) Find all confirmed transactions that have a signature that appears in non-canonical form (and thus likely confirmed under an unexpected TXID);
Unfortunately, you can't— MtGox had a long standing bug where they would author transactions which were themselves non-canonical form (they encoded the variable length values in DER as fixed length with excessive padding). This is one of the reasons their transactions were getting stuck.
People mutating their transactions removed the padding, making them canonical.
- gojomo 13y agoAha, interesting. Seems someone could still run a similar process in reverse: if MtGox's successful make-up transactions are non-canonical, find those first, then look for canonical precursors, within the suspected-exploitation timeframe. That seems more prone to false-positives, though, and perhaps after some point the flood of copycat non-canonicals becomes a problem. (On the other hand, if MtGox was fairly unique for a while in issuing a particular kind of non-canonical transaction, it could make mapping their affiliated addresses by some larger effort easier.) Some researchers might have records of most of the alternate transactions that were circulating without being confirmed. For example, I don't know how comprehensive Blockchain.info's double-spend report – https://blockchain.info/double-spends https://blockchain.info/double-spends – is, but I imagine TXID-mutated variations might appear as double-spends there. It's currently reporting 1126 detected double-spends - over 1000 in the last 3 days, but before then, quite rare.)