Abillity to delete old transactions.

GuardianLiarus commented at 9:29 pm on August 27, 2021: none

Is your feature request related to a problem? Please describe.

As a Vertcoin miner, i get a lot of small payments due pools having a low minimum payout ammount, and all those transactions gets spammed to my Vertcoin Core wallet (which is based on Bitcoin Core), i have arrived to around 1500 transactions in a span of ~3 months, and now when i open my wallet, it freezes a little when loading all the transactions, it would be great if we could choose a transaction / a range of transactions and delete them from the wallet.

I also thought about maybe a toggle option that is off by default, that allows you to “keep only the transaction history from the past X days”

GuardianLiarus added the label Feature on Aug 27, 2021

katesalazar commented at 5:09 pm on August 31, 2021: contributor

Hi

[…] it would be great if we could choose a transaction / a range of transactions and delete them from the wallet.

I think wallets hold keys and transactions are in blockchains? I’m not sure what you are asking for.

While there isn’t any better for you, have you thought about having two wallets? A “fast” wallet where you receive micropayments and aggregate utxos (maybe using command line interface, if you perceive a performance improvement) to send them to a “slow” wallet with fewer transactions which loads fast in the Qt client.

I also thought about maybe a toggle option that is off by default, that allows you to “keep only the transaction history from the past X days”

Now the blockchain is growing at a more or less predictable pace, you could use “prune”, meant to prune by (exact) size, in order to prune by (approximate) time.

 0$ ./src/qt/bitcoin-qt -help | grep -A10 '  -prune'
 1  -prune=<n>
 2       Reduce storage requirements by enabling pruning (deleting) of old
 3       blocks. This allows the pruneblockchain RPC to be called to
 4       delete specific blocks, and enables automatic pruning of old
 5       blocks if a target size in MiB is provided. This mode is
 6       incompatible with -txindex, -coinstatsindex and -rescan. Warning:
 7       Reverting this setting requires re-downloading the entire
 8       blockchain. (default: 0 = disable pruning blocks, 1 = allow
 9       manual pruning via RPC, >=550 = automatically prune block files
10       to stay under the specified target size in MiB)

GuardianLiarus commented at 5:26 pm on August 31, 2021: none

Hi

[…] it would be great if we could choose a transaction / a range of transactions and delete them from the wallet.

I think wallets hold keys and transactions are in blockchains? I’m not sure what you are asking for.

While there isn’t any better for you, have you thought about having two wallets? A “fast” wallet where you receive micropayments and aggregate utxos (maybe using command line interface, if you perceive a performance improvement) to send them to a “slow” wallet with fewer transactions which loads fast in the Qt client.

I also thought about maybe a toggle option that is off by default, that allows you to “keep only the transaction history from the past X days”

Now the blockchain is growing at a more or less predictable pace, you could use “prune”, meant to prune by (exact) size, in order to prune by (approximate) time.
 0$ ./src/qt/bitcoin-qt -help | grep -A10 '  -prune'
 1  -prune=<n>
 2       Reduce storage requirements by enabling pruning (deleting) of old
 3       blocks. This allows the pruneblockchain RPC to be called to
 4       delete specific blocks, and enables automatic pruning of old
 5       blocks if a target size in MiB is provided. This mode is
 6       incompatible with -txindex, -coinstatsindex and -rescan. Warning:
 7       Reverting this setting requires re-downloading the entire
 8       blockchain. (default: 0 = disable pruning blocks, 1 = allow
 9       manual pruning via RPC, >=550 = automatically prune block files
10       to stay under the specified target size in MiB)

Oh yeah i know that all transactions are in the blockchain, what i am requesting is purely a visual / quality of life feature, i guess “delete” transactions wasn’t the right word, it was more about hiding them / not showing them i guess, so i don’t have to load as much stuff when opening my wallet.

katesalazar commented at 6:35 pm on August 31, 2021: contributor

Hi GuardianLiarus.

I think you want a more simple (at least in visual appearance) interface, with faster boot, fewer elements initially but buttons that trigger deferred data loads.

I suspect, this would be desirable, but would end up being large enough of a change, that whenever it is added to the code, you’ll already fixed your problem by moving to a setup with specialized wallets.

If you ever move to a setup with specialized wallets, could you write some followup on the perceived performance difference?

hebasto added the label Wallet on Sep 29, 2021

GuardianLiarus commented at 8:06 pm on December 9, 2021: none

Hi GuardianLiarus.

I think you want a more simple (at least in visual appearance) interface, with faster boot, fewer elements initially but buttons that trigger deferred data loads.

I suspect, this would be desirable, but would end up being large enough of a change, that whenever it is added to the code, you’ll already fixed your problem by moving to a setup with specialized wallets.

If you ever move to a setup with specialized wallets, could you write some followup on the perceived performance difference?

Sorry, what do you mean by specialized wallets ?, basically having a different wallet for X purpose ?

katesalazar commented at 8:19 pm on December 10, 2021: contributor

yup

did you do that?

On Thu, Dec 9, 2021 at 9:06 PM Liarus_ @.***> wrote:

Hi GuardianLiarus.

I think you want a more simple (at least in visual appearance) interface, with faster boot, fewer elements initially but buttons that trigger deferred data loads.

I suspect, this would be desirable, but would end up being large enough of a change, that whenever it is added to the code, you’ll already fixed your problem by moving to a setup with specialized wallets.

If you ever move to a setup with specialized wallets, could you write some followup on the perceived performance difference?

Sorry, what do you mean by specialized wallets ?, basically having a different wallet for X purpose ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bitcoin-core/gui/issues/412#issuecomment-990203241, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMRS4W5YO36A6GGBEIUUGQTUQED4JANCNFSM5C6KHKFA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

GuardianLiarus commented at 9:31 pm on December 10, 2021: none

yeah, that’s what i always did, it’s just that the lag due to loading all those things is a bit inconvenient, but i’ve always been running that way yeah, i use a trezor as my main walet but vertcoin core for the one i mine to.

Abillity to delete old transactions. #412