Bitcoin Forum
May 05, 2024, 06:54:53 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Transaction waiting for confirmation to 3 months. I get a persistent error.  (Read 916 times)
soldierxxi (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
October 18, 2016, 11:05:58 AM
 #1

Hello everyone, I need help with the following problem.
I have a transaction waiting for confirmation to 3 months. I get a repeating error from client debug.
The log of the client BitCoin Core reports the following error:

2016-10-18 10:47:20 UpdateTip: new best=000000000000000001655cd7e4197d5ac2642619ef75c923a9cc289be89eeb8e height=434839 version=0x20000000 log2_work=85.423658 tx=163894748 date='2016-10-18 10:47:07' progress=1.000000 cache=58.0MiB(39951tx) warning='3 of last 100 blocks have unexpected version'
2016-10-18 10:53:30 Relaying wtx a790199ac58a43ef93ed9d00c385260a707927d712c265b289aa4a0a8a513d6c
2016-10-18 10:53:30 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions
1714935293
Hero Member
*
Offline Offline

Posts: 1714935293

View Profile Personal Message (Offline)

Ignore
1714935293
Reply with quote  #2

1714935293
Report to moderator
"You Asked For Change, We Gave You Coins" -- casascius
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714935293
Hero Member
*
Offline Offline

Posts: 1714935293

View Profile Personal Message (Offline)

Ignore
1714935293
Reply with quote  #2

1714935293
Report to moderator
NeuroticFish
Legendary
*
Offline Offline

Activity: 3668
Merit: 6377


Looking for campaign manager? Contact icopress!


View Profile
October 18, 2016, 11:16:25 AM
 #2

Hello everyone, I need help with the following problem.
I have a transaction waiting for confirmation to 3 months. I get a repeating error from client debug.
The log of the client BitCoin Core reports the following error:

2016-10-18 10:47:20 UpdateTip: new best=000000000000000001655cd7e4197d5ac2642619ef75c923a9cc289be89eeb8e height=434839 version=0x20000000 log2_work=85.423658 tx=163894748 date='2016-10-18 10:47:07' progress=1.000000 cache=58.0MiB(39951tx) warning='3 of last 100 blocks have unexpected version'
2016-10-18 10:53:30 Relaying wtx a790199ac58a43ef93ed9d00c385260a707927d712c265b289aa4a0a8a513d6c
2016-10-18 10:53:30 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions

The tx fee is 893 satoshi. That's too small.
In order to stand a chance, you have to set at least 1000 satoshi. If you set under 1000 satoshi it's like you didn't set any fee (like you'd set 0)

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
soldierxxi (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
October 18, 2016, 11:25:13 AM
 #3

There is anything i can do?

I thought to use the "abandon" option, but is disable in this transaction.
MartinL
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
October 18, 2016, 11:30:48 AM
 #4

The tx fee is 893 satoshi. That's too small.
In order to stand a chance, you have to set at least 1000 satoshi. If you set under 1000 satoshi it's like you didn't set any fee (like you'd set 0)

Even 1000 satoshis would not be nearly sufficient for a transaction that size. 21.co currently recommends 70 satoshis/byte in order for the transaction to be included in the next block. For soldierxxi's transaction that would mean a fee of 64820 satoshis or 0.00064820 BTC.
soldierxxi (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
October 18, 2016, 11:44:15 AM
 #5

How can i ajust this fee and send again this transaction?
NeuroticFish
Legendary
*
Offline Offline

Activity: 3668
Merit: 6377


Looking for campaign manager? Contact icopress!


View Profile
October 18, 2016, 11:50:32 AM
 #6

Even 1000 satoshis would not be nearly sufficient for a transaction that size. 21.co currently recommends 70 satoshis/byte in order for the transaction to be included in the next block. For soldierxxi's transaction that would mean a fee of 64820 satoshis or 0.00064820 BTC.

What I said was that under 1k is the same as 0. Over 1k it has a tiny chance.... But I agree, the realistic numbers are at least 10x higher.

But I think that 64820 is too much. That amount is OK if you want the transaction go through "now".
An amount around 10-20k would be fair and the transaction should go trough within a day.


There is anything i can do?

I thought to use the "abandon" option, but is disable in this transaction.

... I don't know 100%. There are a number of stories what to do for this, but I don't have a clear recipe.
From what I know, you can try to send out the same money again, but with higher fee.
If you have a copy of this wallet from just before sending the money, you can try this on another computer. But if you don't have another computer at hand, I would not overwrite the wallet now.
And the other ways should be done from scripts. Some know how to do this, I better leave the question open, they'll help out.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
DannyHamilton
Legendary
*
Offline Offline

Activity: 3388
Merit: 4616



View Profile
October 18, 2016, 12:08:38 PM
 #7

How can i ajust this fee and send again this transaction?

Create a backup of your wallet first and store it securely, just in case anything goes wrong as you attempt a process you are unfamilliar with.

Shut down the wallet software.

Restart the wallet software from a command line with the -zapwallettxes command line option.

Wait for the wallet to finish a re-scan.

Your unconfirmed transaction should now be gone.

Resend your transaction, using coin control features to include an input that was used in the original transaction if necessary.
soldierxxi (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
October 18, 2016, 01:37:53 PM
 #8

Thanks!
I did the step for rescan. Now my balance is again available.
Have some procedure especially for resend? Or just send again with correct fee?
soldierxxi (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
October 18, 2016, 11:51:10 PM
 #9

Did the procedure indicated by Danny Hamilton and resend the transaction. Now I could finish the transaction.

Thank you all for your help
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!