Look at this, for example:
https://blockchain.info/tx/abc23f94572a7287a5f0acaab2e7e4bbef803e17b24508b2e780266d842a5521
Where it says Included In Blocks 482378 ( 2017-08-28 18:09:20 + 0 minutes )
+0 minutes, means, blockchain.info did not see the transaction until in confirmed.
Topic: Propagation of unconfirmed transactions (Read 262 times)
I'm not aware of any propagation issues.
Perhaps you are misunderstanding something you are seeing?
Perhaps you are misunderstanding something you are seeing?
Maybe the Bitcoin payment URL standard can be updated to include an optional parameter to a list listening nodes monitored by particular payment processors... So that supporting wallets could try to broadcast transactions to those nodes first.
Guys, this is a big problem. Inconsistency with propagation of unconfirmed transactions makes payment timeout mechanisms, so popular with Bitcoin merchants, horribly unreliable... Think of 15 minute timeout, the payment processor gives you to see the transaction on the network.
Something needs to be done. I am not sure, raising the number of nodes wallets broadcast through, maybe.
Something needs to be done. I am not sure, raising the number of nodes wallets broadcast through, maybe.
Jump to: