uncofirmed tr

[zebn]

hey guys, why this trans got unconf status for almost a 24h?

last times all was ok, but now they are not confirming

client multibit classic 0.5.19

i already do reset blocks


https://blockchain.info/tx-index/94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566
https://blockchain.info/tx-index/82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e

how can I cancel them, or wtf?

[mocacinno]

This one:
https://blockchain.info/tx-index/94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566

uses an unconfirmed input... So it cannot be confirmed before the input is confirmed i'm afraid...

Actually, after further investigation:
the output of 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e is used as input for 94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566

So, there's a problem with 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e
This tx is 518 bytes and has a fee of 0.0001 BTC = 10.000 satoshi's... This is less than 20 satoshi's per byte, and is not enough

https://bitcoinfees.21.co/ recommands a fee of 80 satoshi's per byte at this moment... A 20 satoshi per byte fee currently has an AVERAGE waiting time of 30-1080 minutes.

About your second question: there are options to "fix" this problem:
1) wait untill the transaction is "forgotten" by the nodes, make sure multibit doesn't re-broadcast the transaction (don't know if classic does this or not, you might have to inquire in the correct subforum)
2) double-spend the inputs of the first transaction, completely re-create the second one (i don't think multibit can do this by default, so it might be rather challenging to export the private keys needed to create a transaction doublespending the inputs)
3) CPFP or RBF might also work

[jacee]

I don't know if you can cancel a transaction but transaction confirmation has been really slow ever since yesterday for me as well. It takes about 8 hours for my last trasaction to get confirmed. I don't know why it takes 24hours for you tho.

[zebn]

This one:
https://blockchain.info/tx-index/94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566

uses an unconfirmed input... So it cannot be confirmed before the input is confirmed i'm afraid...

Actually, after further investigation:
the output of 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e is used as input for 94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566

So, there's a problem with 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e
This tx is 518 bytes and has a fee of 0.0001 BTC = 10.000 satoshi's... This is less than 20 satoshi's per byte, and is not enough

https://bitcoinfees.21.co/ recommands a fee of 80 satoshi's per byte at this moment... A 20 satoshi per byte fee currently has an AVERAGE waiting time of 30-1080 minutes

oh i got it, my fee for 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e was too small

thanks

[mocacinno]

This one:
https://blockchain.info/tx-index/94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566

uses an unconfirmed input... So it cannot be confirmed before the input is confirmed i'm afraid...

Actually, after further investigation:
the output of 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e is used as input for 94fc3abe8d3f1df56925d19dc006540f424e45e2188c99fddba78397c0772566

So, there's a problem with 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e
This tx is 518 bytes and has a fee of 0.0001 BTC = 10.000 satoshi's... This is less than 20 satoshi's per byte, and is not enough

https://bitcoinfees.21.co/ recommands a fee of 80 satoshi's per byte at this moment... A 20 satoshi per byte fee currently has an AVERAGE waiting time of 30-1080 minutes

oh i got it, my fee for 82f2af56de26a74b171d0af12ea3f84345f23214163df2818fc2b26beee7de2e was too small

thanks

That is correct, and the second transaction uses the output of this transaction as an input... So it cannot be confirmed if the first one isn't...

The second one is 225 bytes and has a fee of 10.000 satoshi's, that's 44 satoshi's per byte... Even this fee is rather "problematic", but it's better than the first one.

[zebn]

so, probably, for the next hours it will be confirmed?

1080 min = 18 hrs

[mocacinno]

so, probably, for the next hours it will be confirmed?

1080 min = 18 hrs

Not really, those numbers are averages... With a 20 satoshi per byte fee, you'll need to wait 30 to 1080 minutes on average (at this moment)... The miners are completely free to include transactions in their block, they do not have to include the oldest transactions first or something.

It's possible to add 20 satoshi's per byte and get added to the very next block 5 minutes later (on average roughly 10 minutes between blocks)... It's also possible you'll have to wait forever, and see your transaction dropped.

[zebn]

ok thank you

and one more question, when it drops? for 3 days, or smth like that? or my client will try to send this trans forever?

[mocacinno]

ok thank you

and one more question, when it drops? for 3 days, or smth like that? or my client will try to send this trans forever?

Can't answer you this either. There is no predefined timeframe for a node to forget about a transaction (altough i think there might be a default of 3 days. EDIT: https://github.com/gavinandresen/bitcoin-git/blob/master/src/main.h#L68), when the node restarts, the unconfirmed transactions will be gone from its memory. The node's owner can also set the maximum memory for the mempool, so i guess a transaction will also be forgotten when the node's memory is full.

Can't answer the question about the rebroadcasting either, not because there is no answer, but because i'm not familiar with multibit classic 0.5.19. For example, bitcoin core keeps rebroadcasting the transaction unless you keep your client off, abandon the transactor or zap your wallet. On the other hand, electrum for example, only broadcasts a transaction once (iirc)

If nobody can help you here (in this topic), you can ask this specific question (wether or not multibit classic 0.5.19 keeps rebroadcasting) in this subforum: https://bitcointalk.org/index.php?board=99.0