Topic: help for canceling my zero fee transaction with 2.1 BTC... (Read 2164 times)

i am testing zero fee option and not successful 

If you remember that your wallet lost some coins, than why are you using the same wallet? And now transaction is big money, 2.1 bitcoin and I have one more question, why are you using zero fee? Pay some fee and you and your transaction's confirmation will be more secure.

Also if you deleted transactions date, than when all networks forget that, it will be returned to sender's adress, it won't be lost as I know.

You can permanently lose access to your bitcoins if you lose access to your private keys.  That (the private keys) is what the wallet is storing. It is not storing any bitcoins.

If you delete the wallet.dat file and you have not backed it up, or if your system crashes and you have not backed up your wallet, then you will lose access to the bitcoins.  It isn't that the bitcoins are gone from your wallet (they were never there in the first place). It's that the private keys, that allow you to prove that the bitcoins in the blockchain are under your control, are gone from your wallet.

It is therefore VERY IMPORTANT THAT YOU HAVE AT LEAST ONE BACKUP OF YOUR WALLET IN A SECURE LOCATION BEFORE YOU START MESSING AROUND WITH IT.

Thanks.. I remember my wallet lost many coin before.. will try to dump the private key and import to new wallet ...

The bitcoin was never in your wallet in the first place.  Bitcoins don't "go" anywhere. There are simply transactions that get recorded in the blockchain.

If the transaction gets included into the blockchain then it is called confirmed. Then each additional block added to the blockchain after that is considered to be an additional "confirmation".  When there are enough blocks stacked on top of the block with your transaction, the transaction is generally considered to be permanent.

Since your transaction is not confirmed yet, the bitcoins are still recorded in the blockchain as belonging to you.

There are two possibilities:

1. Your wallet has forgotten about the confirmed transaction ca1e4dff695a5a2649514ecefc7a14e693ca706ccc2bf1d47a02fdfa67ba848d where it received the 4.84802738 BTC back on April 29.  If this has happened, then the rescan will cause the wallet to read through the entire blockchain again to find all the transactions that the wallet has control over.  Therefore, it should find that transaction in the blockchain and update the balance that it shows you to include those 4.84802738 BTC.

OR

2. Your wallet still remembers your new unconfirmed transaction that spends the 4.84802738 BTC, but has forgotten that the 2.74802738 BTC output is going to an address that the wallet controls.  If this has happened, then you may need to try the zapwallettxes again, or you may need to try the rescan.  zapwallettxes should cause the wallet to forget about the unconfirmed transaction and search the blockchain to find the transaction that paid you, but perhaps for some reason it failed to do that.

If neither zapwallettxes nor rescan fix your problem, then there may be something wrong with the wallet.  You'll then need to find the private key for the 1Fnpr866zeRb24maVTtj6Kq162FgKy3c5B address and import that private key into some other wallet that is working properly.  The new wallet should then re-scan the blockchain and find the balance that you control.

If this transaction will not get confirmed then the funds will be returned to the sender which seems to be 1Fnpr866zeRb24maVTtj6Kq162FgKy3c5B.
So if you are the sender you should see the wallet balance will be like before otherwise you should ask the sender to send again.

Your 2.1BTC haven't really gone anywhere except the intended destination from what I see. 1JvYyMcpL12zZrspX4PXRy54BCsTfAyWXM is the intended destination, isn't it? I don't get why you keep posting that. It should return to your wallet if it never get confirmed and ended up getting dropped (it should've returned after you did zapwallettxes but not sure what happened).

Thanks.. I will try it .. but where is my 2.1BTC goes .. will it return back to my wallet
https://blockchain.info/address/1JvYyMcpL12zZrspX4PXRy54BCsTfAyWXM

And make sure you have a backup or two of your wallet.dat file just to be safe.

That transaction and address is the same ones you posted on the OP so I'm not sure what I'm supposed to make of them.

Try doing a rescan if it works (same way as -zapwallettxes but replace it with -rescan). Might not work because zapwallettxes do a rescan after deleting transactions but it's worth a try.

If that doesn't work you'll need to import your address to another wallet (I recommend electrum for this) and send from there. To get the private key for importing, go to "Help>Debug window> Console" and type dumpprivkey XXX. If your wallet is encrypted, enter walletpassphrase YYY 300 before dumping. Replace XXX with your address and YYY with your passphrase.

I used to have 4.84802738btc in my wallet . sent 2.1btc with no fee and rest 2.74 was showing as pending. after using -zapwallettexes , my wallet is showing 0 now..

you can check my transaction like and I am wondering where the BTC went ....

That's quite a specific amount, how do you know that exactly 4.84802738btc is missing? Does it show that amount anywhere? That's the amount of the input of the transaction and it shouldn't have disappeared because it's already confirmed.

I have tried your suggestion by using "run bitcoin-qt.exe with -zapwallettexes" . After it finished , I found pending translation was disappear but my wallet is short around 4.84802738 BTC ......??   any idea how i can get my missing BTC back to my wallet??

https://blockchain.info/address/1JvYyMcpL12zZrspX4PXRy54BCsTfAyWXM

https://blockchain.info/tx/0d214e4818a606d0255564556c5b3b9424e1d6dad177823ba935f8253b952663

What I don't get it why you published the transaction. Some dickgead couldmore easily that not just get the Hex transaction from blockchain and keep rebroadcasting it...

And yet that's exactly what you said:

See here:



Yes.  That's the point I've been trying to make here.  There is nothing "faster" or "easier" about starting over with a brand new wallet and exporting private keys from your old wallet and importing them into the new wallet.  It is an option, and if done correctly it would work, but it is "more difficult" and "slower".  If you had suggested it saying that it is a more difficult, slower, and riskier option, I probably wouldn't have ever gotten involved in this thread.


Glad I could help.


I believe it was first added in 0.12.0:

See here:


Correct.

I never claimed otherwise though. I think this should be clear to most of the Bitcoin users (or atleast I hope so).

This was the key error in my rationalization (I disregarded the waiting time after importing).

This viewpoint has made me learn something new today. Thank you for this explanation. I see the error in my thought process as I completely disregarded some aspects when comparing the two options. I don't even know when 'abandontransaction' was added (there seems to be a commit in 0.13.0 for it). The old method of exporting/importing is definitely redundant and slow in comparison to this.

Nodes don't care what wallet you are using when deciding whether to relay a transaction.  There is no difference between sending a new transaction with the same wallet or sending it after importing into a new wallet.  If you have to wait after abandontransaction, then you also have to wait after importing into a new wallet.  If you don't have to wait after importing into a new wallet, then you don't have to wait after abandontransaction.  There is nothing about exporting and importing into a new wallet that makes it faster or easier.

If a node doesn't remember your old transaction, then they will accept and rebroadcast your new transaction (assuming it is valid and has an adequate fee).  This is true if you abandontransaction and is true if you export and import.  The reason that the node doesn't remember your old transaction doesn't matter.  Maybe they don't remember it because they didn't like the fee and never accepted it into memory, maybe they don't remember it because it has been a long time and they've cleared it out of memory to make room for a new transaction. The end effect is the same.  If they don't remember the old transaction, they'll relay the new one.  If they do remember to old transaction, they won't relay the new one.


But my point is that it ISN'T faster.

If you have to wait for the network to 'forget about it' and it "(takes a day or two)" after abandontransaction, then you ALSO have to wait for the network to 'forget about it' and it "(takes a day or two)" after importing into a new wallet.

Interesting. What about nodes that have don't have/remember the old transaction due to inadequate fees and/or other reasons? Starting with 0.13.0 nodes won't even relay TX's to others nodes if they don't meet their minrelayfee criteria (AFAIK).

I was referring to "faster" than abandoning it and waiting for the network to 'forget about it' (this is why I quoted the part with "(takes a day or two)"). However, it is most certainly not faster than just using abandontransaction. It is actually much slower.

The user doesn't "have to", but it's usually a good idea.

If you create a new transaction (with the same wallet OR after importing to a new wallet) that uses the same inputs, then any node on the network that still remembers the old transaction will simply refuse to accept and relay your new transaction.

Importing into a new wallet doesn't solve this problem.  The rest of the network doesn't know (or care) that you are using a new wallet.  They will still continue to ignore the new transaction if they still remember the old transaction.


Are either of them (exporting or importing) faster or easier than abandontransaction (is this newbie user "huzhuzhu" even likely to know which private key to export)?  That's what you seem to have stated and what I've asked for your reasoning about.

It does seem like it, although there is no way to know for sure which miners supports it (at this time).

Doesn't the user have to wait for the network to 'forget' about the transaction before sending another one with a higher fee? Exporting the key into a new wallet doesn't take that much time, importing it just takes a while (at least on Core).