Quote from: DeathAndTaxes on June 04, 2014, 09:49:35 PM

https://blockchain.info/tx/7945140310e5e22e2d38f41eba3422e11e92719aad527e6e4a4d7b660ac5cda7?show_adv=true

The tx is large (17K) but it includes >0.1mBTC per KB in fees, it has no double spent or unconfirmed inputs, and it has no dust outputs. The interesting thing is that the tx was sent from Bitcoin Core (v0.91). That node does not have direct connectivity to blockchain.info so it must have been relayed by at least one peer. The recipient node is also using Bitcoin Core v0.91 but the tx is not in the memory pool and my assumption is that the recipients peers are dropping it. The question is why? Possibly a difference in relaying rules on older nodes (and the recipient is unlucky enough to have all older nodes as peers? As of the time of the post it hasn't been included in a block but I am more concerned with what would keep it from being seen as an unconfirmed tx by the recipient node.

On edit: ok it was just included in a block and the recipient node instantly recognized and reported the confirmed tx but why wasn't it relayed prior to being confirmed.

In my understanding Input and Output rule should not be different, and same will definitely work.

Thanks