Bitcoin Forum
March 01, 2021, 11:03:15 AM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Zap wallet txns in pruned mode?  (Read 1018 times)
-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 11, 2017, 10:20:22 PM
 #1

Since -zapwallettxes implies -rescan, it means its use is effectively mutually exclusive of using pruned mode. Does anyone have any suggestions for a workaround without redownloading the whole blockchain again?

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1614596595
Hero Member
*
Offline Offline

Posts: 1614596595

View Profile Personal Message (Offline)

Ignore
1614596595
Reply with quote  #2

1614596595
Report to moderator
1614596595
Hero Member
*
Offline Offline

Posts: 1614596595

View Profile Personal Message (Offline)

Ignore
1614596595
Reply with quote  #2

1614596595
Report to moderator
1614596595
Hero Member
*
Offline Offline

Posts: 1614596595

View Profile Personal Message (Offline)

Ignore
1614596595
Reply with quote  #2

1614596595
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 2422
Merit: 3643


Just writing some code


View Profile WWW
February 11, 2017, 11:34:21 PM
 #2

Right click the transaction and choose "Abandon transaction" or use the abandontransaction command in the rpc console.

Or you can use something like pywallet and remove the transaction from your wallet file manually.

-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 11, 2017, 11:35:35 PM
 #3

Right click the transaction and choose "Abandon transaction" or use the abandontransaction command in the rpc console.

Or you can use something like pywallet and remove the transaction from your wallet file manually.
Abandon transaction is greyed out so presumably it's subject to the same limitations as zap.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
achow101
Moderator
Legendary
*
Offline Offline

Activity: 2422
Merit: 3643


Just writing some code


View Profile WWW
February 11, 2017, 11:45:39 PM
 #4

Abandon transaction is greyed out so presumably it's subject to the same limitations as zap.
No, that means that something else is blocking it from being abandoned. I'm pretty sure it still works in pruned mode as I'm pretty sure I did it before.

-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 11, 2017, 11:57:24 PM
 #5

Abandon transaction is greyed out so presumably it's subject to the same limitations as zap.
No, that means that something else is blocking it from being abandoned. I'm pretty sure it still works in pruned mode as I'm pretty sure I did it before.
That's interesting in itself. What else could possibly be blocking it?

Code:
bitcoin-cli abandontransaction XX
error code: -5
error message:
Transaction not eligible for abandonment

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
achow101
Moderator
Legendary
*
Offline Offline

Activity: 2422
Merit: 3643


Just writing some code


View Profile WWW
February 12, 2017, 12:02:01 AM
 #6

That's interesting in itself. What else could possibly be blocking it?

Code:
bitcoin-cli abandontransaction XX
error code: -5
error message:
Transaction not eligible for abandonment
Anything that would cause this function: https://github.com/bitcoin/bitcoin/blob/02464da5e4aa8c19d4fff3859dcdee822e2af78c/src/wallet/wallet.cpp#L1052 to return false. So it seems the only criteria are that the transaction is not in the mempool and it is not confirmed. So clearing the mempool by restarting the node should work (if you are using any version greater than 0.13.2 i.e. a build of master, then you need to delete mempool.dat in the datadir).

-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 12, 2017, 12:03:38 AM
 #7

That's interesting in itself. What else could possibly be blocking it?

Code:
bitcoin-cli abandontransaction XX
error code: -5
error message:
Transaction not eligible for abandonment
Anything that would cause this function: https://github.com/bitcoin/bitcoin/blob/02464da5e4aa8c19d4fff3859dcdee822e2af78c/src/wallet/wallet.cpp#L1052 to return false. So it seems the only criteria are that the transaction is not in the mempool and it is not confirmed. So clearing the mempool by restarting the node should work (if you are using any version greater than 0.13.2 i.e. a build of master, then you need to delete mempool.dat in the datadir).
Weird, I've restarted it a few times, perhaps another node that I have whitelisted elsewhere is submitting the transaction immediately once I restart. I'll try isolating it from the network and doing it.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
achow101
Moderator
Legendary
*
Offline Offline

Activity: 2422
Merit: 3643


Just writing some code


View Profile WWW
February 12, 2017, 12:13:21 AM
 #8

Weird, I've restarted it a few times, perhaps another node that I have whitelisted elsewhere is submitting the transaction immediately once I restart. I'll try isolating it from the network and doing it.
If you run
Code:
getmempoolentry <txid>

beforehand and it tells you that the transaction is not in the mempool but you still can't abandon it, then there must be something else that is blocking it from being abandoned, but I don't know what that could be.

-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 12, 2017, 12:17:28 AM
 #9

Weird, I've restarted it a few times, perhaps another node that I have whitelisted elsewhere is submitting the transaction immediately once I restart. I'll try isolating it from the network and doing it.
If you run
Code:
getmempoolentry <txid>

beforehand and it tells you that the transaction is not in the mempool but you still can't abandon it, then there must be something else that is blocking it from being abandoned, but I don't know what that could be.
Well it is in the mempool and it's 0.13.2 and restarting it doesn't remove it from the mempool... Hmm it could be because I getblocktemplates regularly from the bitcoind... or not :s

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
achow101
Moderator
Legendary
*
Offline Offline

Activity: 2422
Merit: 3643


Just writing some code


View Profile WWW
February 12, 2017, 12:54:17 AM
 #10

Well it is in the mempool and it's 0.13.2 and restarting it doesn't remove it from the mempool... Hmm it could be because I getblocktemplates regularly from the bitcoind... or not :s
Oh, duh, of course its in the mempool, restarting will have the wallet put the transactions back into the mempool on start. You need to set the -walletbroadcast=false command line option when you start it up again in order to prevent that from happening.

-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 12, 2017, 01:17:42 AM
 #11

Well it is in the mempool and it's 0.13.2 and restarting it doesn't remove it from the mempool... Hmm it could be because I getblocktemplates regularly from the bitcoind... or not :s
Oh, duh, of course its in the mempool, restarting will have the wallet put the transactions back into the mempool on start. You need to set the -walletbroadcast=false command line option when you start it up again in order to prevent that from happening.
That did it. The abandon transaction option was no longer greyed out and now the transaction still appears in the interface but is marked in red and the details say not in mempool, even after restarting. I guess this is enough since theoretically it could still be bouncing around somewhere in the network at large. Thanks!

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
-ck
Legendary
*
Offline Offline

Activity: 3318
Merit: 1353


Ruu \o/


View Profile WWW
February 13, 2017, 12:42:26 PM
 #12

Hah the network had the last laugh and processed the transaction after about 3 days anyway.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
jnano
Member
**
Offline Offline

Activity: 291
Merit: 62


View Profile
August 18, 2019, 04:40:32 PM
 #13

The clunky interface is still around in the latest version.

"Abandon transaction" should never be grayed out. When it can't work, it should explain why. Or better, automatically stop broadcasting the wallet.

achow101
Moderator
Legendary
*
Offline Offline

Activity: 2422
Merit: 3643


Just writing some code


View Profile WWW
August 18, 2019, 04:52:33 PM
 #14

The clunky interface is still around in the latest version.

"Abandon transaction" should never be grayed out. When it can't work, it should explain why. Or better, automatically stop broadcasting the wallet.
Complaining about it here isn't going to help. Pretty much none of the Bitcoin Core developers read this forum (except for me). If you want to request a feature or change, open an issue in the github repo

jnano
Member
**
Offline Offline

Activity: 291
Merit: 62


View Profile
August 18, 2019, 05:08:27 PM
 #15

I guess I'm just venting with no specific goal in mind. Smiley

Core's focus seems to be the network and RPC rather than the GUI. There are more important GUI features to deal with, so no point in bringing up this specific one.
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!