<blockquote>
  <p>I did not see <code>a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec</code> broadcast-ed I only saw <code>d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080</code></p>
</blockquote>

<p>That might not be meaningful. Bitcoin is a gossip network, so it's possible for a different node to see a transaction that you didn't see, particularly if it contradicts a transaction you have.</p>

<p>If you're connected to 8 nodes, and each of those has transaction TX1 in their memory pool, none of them will send you TX2 if it contradicts TX1. (Assuming they're running Bitcoin Core, of course.)</p>

CC BY-SA 3.0
2017-04-04T22:11:08.273Z
so i need to 'pool' (https://github.com/bitpay/bitcore-p2p/blob/master/docs/pool.md) more nodes to have a greater chance of seeing it?
Ben Muircroft
CC BY-SA 3.0
2017-04-04T22:13:04.670Z
'particularly if it contradicts a transaction you have' - please elaborate!
Ben Muircroft
CC BY-SA 3.0
2017-04-04T22:13:59.067Z
@BenMuircroft If two transactions spend the same outpoint, they cannot both succeed. One or more must not get into the chain.
Nick ODell
CC BY-SA 3.0
2017-04-04T22:17:00.223Z
'none of them will send you TX2 if it contradicts TX1' - but if TX2 was the malleated transaction altered and included in the block by the miner then *race conditions don't matter* so; the none of them sending TX2 is retarded because the logic will always be ignored by the miners choice of what inevitably goes in!
Ben Muircroft
CC BY-SA 3.0
2017-04-04T22:17:55.440Z
@BenMuircroft Yes, that's correct.
Nick ODell
CC BY-SA 3.0
2017-04-04T22:18:59.773Z
wow that is a major exception! it is occuring like mad frequently right now on testnet3!
Ben Muircroft
CC BY-SA 3.0
2017-04-04T22:22:27.680Z
If a wallet sends raw tx 
[4d]49[00]3046....
without [in brackets unnecessary bytes] do you think some miners might be resigning the tx with the unnecessary bytes? therefore changing the txid?!
Ben Muircroft
CC BY-SA 3.0
2017-04-04T22:30:04.787Z
related: http://bitcoin.stackexchange.com/a/22058/14316
Ben Muircroft
CC BY-SA 3.0
2017-04-04T22:04:39.880Z
2017-04-04T22:04:39.880Z
Nick ODell
<p>Here's the pushed/broacast-ed tx <a href="http://tbtc.blockr.io/tx/info/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080" rel="nofollow noreferrer">http://tbtc.blockr.io/tx/info/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080</a></p>

<p>txid was <a href="https://bitcoin.org/en/glossary/malleability" rel="nofollow noreferrer">malleated</a> to txid (when the tx was added into the block):</p>

<p><a href="http://tbtc.blockr.io/tx/info/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec" rel="nofollow noreferrer">http://tbtc.blockr.io/tx/info/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec</a></p>

<p>I am watching all utx broadcasted on the testnet3 network using <a href="https://github.com/bitpay/bitcore-p2p" rel="nofollow noreferrer">https://github.com/bitpay/bitcore-p2p</a></p>

<p>I did not see <code>a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec</code> broadcast-ed I only saw <code>d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080</code></p>

<p>How the hell did blockr.io see both the original broadcasted tx <em>and</em> the altered tx <em>when it never was seen on the network?</em></p>

<p>What voo-doo magic is this?</p>

<p>Look, blockcypher didn't store the original broadcasted txid:
<a href="https://api.blockcypher.com/v1/btc/test3/txs/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080" rel="nofollow noreferrer">https://api.blockcypher.com/v1/btc/test3/txs/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080</a></p>

<p>but they did store the malleated version:</p>

<p><a href="https://api.blockcypher.com/v1/btc/test3/txs/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec" rel="nofollow noreferrer">https://api.blockcypher.com/v1/btc/test3/txs/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec</a></p>

<p>HOW?</p>

<p>related: <a href="https://bitcoin.stackexchange.com/questions/52539/how-confirm-my-own-doublespend-transaction-got-confirmed">How confirm my own doublespend transaction got confirmed</a> and <a href="https://bitcoin.stackexchange.com/questions/52571/testnet3-frequent-tx-malleability">testnet3 frequent tx malleability</a></p>

<transaction-malleability><blockexplorer>
How did blockr.io see this?
Ben Muircroft
# How did blockr.io see this?

(Asked by: username_0 on 2017-04-04)

Here's the pushed/broacast-ed tx <http://tbtc.blockr.io/tx/info/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080>

txid was [malleated](https://bitcoin.org/en/glossary/malleability) to txid (when the tx was added into the block):

<http://tbtc.blockr.io/tx/info/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec>

I am watching all utx broadcasted on the testnet3 network using <https://github.com/bitpay/bitcore-p2p>

I did not see `a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec` broadcast-ed I only saw `d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080`

How the hell did blockr.io see both the original broadcasted tx *and* the altered tx *when it never was seen on the network?*

What voo-doo magic is this?

Look, blockcypher didn't store the original broadcasted txid:
<https://api.blockcypher.com/v1/btc/test3/txs/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080>

but they did store the malleated version:

<https://api.blockcypher.com/v1/btc/test3/txs/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec>

HOW?

related: [How confirm my own doublespend transaction got confirmed](https://bitcoin.stackexchange.com/questions/52539/how-confirm-my-own-doublespend-transaction-got-confirmed) and [testnet3 frequent tx malleability](https://bitcoin.stackexchange.com/questions/52571/testnet3-frequent-tx-malleability)

**Tags:** transaction-malleability, blockexplorer


---

## 1 answers

### Answer by username_1 on 2017-04-04. Score: 1

> I did not see `a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec` broadcast-ed I only saw `d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080`

That might not be meaningful. Bitcoin is a gossip network, so it's possible for a different node to see a transaction that you didn't see, particularly if it contradicts a transaction you have.

If you're connected to 8 nodes, and each of those has transaction TX1 in their memory pool, none of them will send you TX2 if it contradicts TX1. (Assuming they're running Bitcoin Core, of course.)

> **Comments:**
> **username_0**: so i need to 'pool' (https://github.com/bitpay/bitcore-p2p/blob/master/docs/pool.md) more nodes to have a greater chance of seeing it?  
> **username_0**: 'particularly if it contradicts a transaction you have' - please elaborate!  
> **username_1**: @BenMuircroft If two transactions spend the same outpoint, they cannot both succeed. One or more must not get into the chain.  
> **username_0**: 'none of them will send you TX2 if it contradicts TX1' - but if TX2 was the malleated transaction altered and included in the block by the miner then *race conditions don't matter* so; the none of them sending TX2 is retarded because the logic will always be ignored by the miners choice of what inevitably goes in!  
> **username_1**: @BenMuircroft Yes, that's correct.  
> **username_0**: wow that is a major exception! it is occuring like mad frequently right now on testnet3!  
> **username_0**: If a wallet sends raw tx  [4d]49[00]3046.... without [in brackets unnecessary bytes] do you think some miners might be resigning the tx with the unnecessary bytes? therefore changing the txid?!  
> **username_0**: related: http://bitcoin.stackexchange.com/a/22058/14316  

---

