user14316: Here's the pushed/broacast-ed tx http://tbtc.blockr.io/tx/info/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080
txid was malleated 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 and testnet3 frequent tx malleability

user2306: 
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.)

14316: <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>
 2306: <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>
