unconfirmed transactions

[yakuza699]

Oh there you go the transaction has been dropped https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 it says "Transaction not found" I recommend you to resend the coins now with a fee as some nodes might rebroadcast it(it happened once with me transaction got dropped and I decided to not resend it next day it was rebroadcast even though I have never opened my client)

[Centaurus]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

[OnkelPaul]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.

Onkel Paul

[ranochigo]

Oh there you go the transaction has been dropped https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 it says "Transaction not found" I recommend you to resend the coins now with a fee as some nodes might rebroadcast it(it happened once with me transaction got dropped and I decided to not resend it next day it was rebroadcast even though I have never opened my client)

It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.

[TonyT]

It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.

Here's a question that's not too far off-topic:  what if you suggest an amount *greater than* the 0.0001 or so BTC that's recommended?  Does it mean instead of waiting say 1 hour you would wait a lot less, if your reward for confirm is greater?  And how much faster would the confirm be?  Double the amount means half the time to confirm?  Or I guess it varies on the network congestion at any give time?

[Muhammed Zakir]

It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.

Here's a question that's not too far off-topic:  what if you suggest an amount *greater than* the 0.0001 or so BTC that's recommended?  Does it mean instead of waiting say 1 hour you would wait a lot less, if your reward for confirm is greater?  And how much faster would the confirm be?  Double the amount means half the time to confirm?  Or I guess it varies on the network congestion at any give time?

It isn't really like that. But the priority will be higher, so it will be confirmed faster but we can't say the correct time.

   ~~MZ~~

[graves]

i dont think theres anything to worry, since its already sent.

[yakuza699]

It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.

Here's a question that's not too far off-topic:  what if you suggest an amount *greater than* the 0.0001 or so BTC that's recommended?  Does it mean instead of waiting say 1 hour you would wait a lot less, if your reward for confirm is greater?  And how much faster would the confirm be?  Double the amount means half the time to confirm?  Or I guess it varies on the network congestion at any give time?

If you put 0.0001 on 1000 bytes transaction it will be confirmed in the next block and there is no need to put the fee higher unless you want to donate that to the pool or the transaction is higher than 1000 bytes.

[yakuza699]

i dont think theres anything to worry, since its already sent.

There are few things to worry about 1.It could be rebroadcast over and over again thus taking months to confirm. 2.It could never confirm(drops from memory pool(applies only for the receiver).

[Centaurus]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.

Onkel Paul

currently is ok to use 1 satoshi

[ClownHunter]

i dont think theres anything to worry, since its already sent.

There are few things to worry about 1.It could be rebroadcast over and over again thus taking months to confirm. 2.It could never confirm(drops from memory pool(applies only for the receiver).

The longer an input has been unspent, the higher priority it will have for the miners to confirm any TX that it contains. So *if* a TX was rebroadcast over and over again then it would have an ever-increasing level of priority.

[ranochigo]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.

Onkel Paul

currently is ok to use 1 satoshi

No it isn't. 9999 satoshi or anything less than that is considered non standard fee. 1 satoshi won't even increase your priority by a bit and most nodes would consider it as a dust transaction and refuse to relay it. Most mining pool also wouldn't include it in their blocks unless your coin age is high and outputs are more than 0.01 BTC.

[Salmon1989]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.

Onkel Paul

currently is ok to use 1 satoshi

No it isn't. 9999 satoshi or anything less than that is considered non standard fee. 1 satoshi won't even increase your priority by a bit and most nodes would consider it as a dust transaction and refuse to relay it. Most mining pool also wouldn't include it in their blocks unless your coin age is high and outputs are more than 0.01 BTC.

Yup ranochigo and Onkel is right.

AFAIK, transactions with at least min fee are ranked by pools by tx fee per byte.
And for transaction with less than min fee, they are ranked by the priority:

Code:

priority = sum(input_value_in_base_units * input_age)/size_in_bytes

[Salmon1989]

Oh there you go the transaction has been dropped https://blockchain.info/en/tx/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9 it says "Transaction not found" I recommend you to resend the coins now with a fee as some nodes might rebroadcast it(it happened once with me transaction got dropped and I decided to not resend it next day it was rebroadcast even though I have never opened my client)

It appears to be rebroadcasted again. Even if you don't open the client but the client behaviour is to rebroadcast after the transaction falls out of the mempool, it will still automatically broadcast. In this case, even though no node is relaying it right now due to its low fee (https://blockchain.info/inv/f24ff339fc651b0b28cdfc0e67bb4c2f91b46cbd39935ff4d70c95bb5c33b0e9) the transaction appeared to have been stored in Blockchain.info's mempool again. The only way now is to either doublespend it or just wait for it to confirm, it will confirm eventually but it takes a long time.

OP, you should also contact the receiver (if you are just the sender) and ask him not to rebroadcast the transaction. Otherwise, the receiver may keep rebroadcasting it again and again.

[fa]

It will take very long time to confirm a tx like this.
No tx fee... no miner is willing to pack your transaction in their mined block.
You should always add a small fee, man

[yakuza699]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.

Onkel Paul

currently is ok to use 1 satoshi

No it isn't. 9999 satoshi or anything less than that is considered non standard fee. 1 satoshi won't even increase your priority by a bit and most nodes would consider it as a dust transaction and refuse to relay it. Most mining pool also wouldn't include it in their blocks unless your coin age is high and outputs are more than 0.01 BTC.

That is not absolutely right. First of all there is no such thing as non standard fee(unless it has negative value) every transaction fee included(or not) is considered standard.Secondly you should know that there are 0.9.x miners who mines transaction which put 0.00001(1000 sat) per 1000 bytes so 9999 satoshi fee is 9.999 times higher than they require.

[ranochigo]

Consider to send your transactions with a fee of 0.00000001 (one satoshi) instead of none fee.

Sorry, that's nonsense. Either leave out the fee (and risk that the transaction won't be processed) or add the standard fee of 0.0001 BTC to ensure that everything works as it should.
Miners that refuse to process no-fee transactions would most likely refuse one-satoshi transations as well.

Onkel Paul

currently is ok to use 1 satoshi

No it isn't. 9999 satoshi or anything less than that is considered non standard fee. 1 satoshi won't even increase your priority by a bit and most nodes would consider it as a dust transaction and refuse to relay it. Most mining pool also wouldn't include it in their blocks unless your coin age is high and outputs are more than 0.01 BTC.

That is not absolutely right. First of all there is no such thing as non standard fee(unless it has negative value) every transaction fee included(or not) is considered standard.Secondly you should know that there are 0.9.x miners who mines transaction which put 0.00001(1000 sat) per 1000 bytes so 9999 satoshi fee is 9.999 times higher than they require.

This is what bitcoin wiki tells me

Note that a typical transaction is 500 bytes, so the typical transaction fee for low-priority transactions is 0.1 mBTC (0.0001 BTC), regardless of the number of bitcoins sent.

By standard transaction fee, I meant the fee for the transaction to be accepted ASAP. Obviously, you don't have to put one if your coin is old enough and have outputs of more than 0.01BTC.
That don't happen with majority of the pools/miners. Most of them require a 0.0001BTC fee at least. Obviously, that depends on the kind of software client they are running, different ones have different behaviour.

[Salmon1989]

AFAIK, the min tx fee is unchanged for the upgrade from 0.8.x to 0.9.x and remain as 0.0001 btc per KB.
The one lowered to 0.00001 btc per KB is the relay fee.

For the meaning of relay fee, you may refer to https://bitcointalk.org/index.php?topic=579460.0

[Centaurus]

Has anyone ever tried to send a transaction with .00000001 fee?
I did various;

• 83 minutes: 5457c17730a26da278ddf205246d05fc37f1219a790d929345752d3aeb867ce6
• 22 minutes: 6b24f6dd17f144fd90b1fc198c83a61b9f8f9ea04b0b3341e9cc0b9ade4a8446
• 3 minutes: 60ed62cc99fbccda0414f703b5833d5d43fc19000de4576e7eb412b3e373c270
• 39 minutes: 4a37a422c88bc18097cd0525b8c8e14132f5ce7bdde912d2904df9d396b298d2
• 137 minutes: 38c14c2390344611d85750fd58183fda9e8e6cb5b8d4202bb6442e6888a5ed19
• 8 minutes: 7427640b18d909dcb6974b8d83ef0ced4fd18519a3a16d1c2db284416dc397f1
• 11 minutes: 1b1cc2964d4fa94320de0df1db04883cffd18af3e98843b427b743e9bf0eead2
• 56 minutes: a9ff214c644d43409726fae423e24a36492ca315745428928260761d3434e20f
• continue...

It took an average of 20 minutes to confirm.

[Muhammed Zakir]

Has anyone ever tried to send a transaction with .00000001 fee?
I did various;

• 83 minutes: 5457c17730a26da278ddf205246d05fc37f1219a790d929345752d3aeb867ce6
• 22 minutes: 6b24f6dd17f144fd90b1fc198c83a61b9f8f9ea04b0b3341e9cc0b9ade4a8446
• 3 minutes: 60ed62cc99fbccda0414f703b5833d5d43fc19000de4576e7eb412b3e373c270
• 39 minutes: 4a37a422c88bc18097cd0525b8c8e14132f5ce7bdde912d2904df9d396b298d2
• 137 minutes: 38c14c2390344611d85750fd58183fda9e8e6cb5b8d4202bb6442e6888a5ed19
• 8 minutes: 7427640b18d909dcb6974b8d83ef0ced4fd18519a3a16d1c2db284416dc397f1
• 11 minutes: 1b1cc2964d4fa94320de0df1db04883cffd18af3e98843b427b743e9bf0eead2
• 56 minutes: a9ff214c644d43409726fae423e24a36492ca315745428928260761d3434e20f
• continue...

It took an average of 20 minutes to confirm.

The lowest amount I use is 1 uBTC. We can save our BTC, but because of miners, TXs are confirming, so it is better to send atleast 1 uBTC and if you can 0.1 mBTC.

P.S. When I looked the TX, all the tx were above 0.01BTC, so it has more chance to get confirmed even if you didn't send any fees. I think that is why, it confirmed in a short period.

   ~~MZ~~