GUI CHIA

[TomaszWM]

On gui chia how I can delete the unused pool contracts ? For example Red Reptile on the picture belong.

[Jacek-ghub]

I don't think that you can do that using chia UI, as it is too primitive. Although, you can remove it from the config file. Take a look at that video:

https://youtu.be/F0VHlvvf8fE?t=102

[loppefaaret]

in a future update, we have planned for users to be able to hide unwanted plotNFT's, but it is not possible currently, from an official standpoint

[Jacek-ghub]

@loppefaaret
In such a case, if we remove pool info from the config.yaml, isn't it the same as removing a pool or hiding it? Or are we causing a potential instability in the setup by doing that?

[loppefaaret]

if there are no plots tied to it, i personally can't see any problems with it - if it does have plots tied to it, i'd imagine there could very well be problems correctly farming those plots

[Jacek-ghub]

As plots are bound to the (local, or rather UI) pool, I would also imagine that removing such pool from config.yaml will render those plots orphaned. Or rather those pools belong to a wallet, and info in config.yaml is just a cached info?

Although, if config.yaml is the only place that keeps a given pool info, that may also imply that if someone restores that pool info in config, those plots would get a second life. Still, removing a pool with plots is not really a good idea what potentially implies that one should keep a backup of config.yaml just for that reason.

[loppefaaret]

apart from the plots themselfs, everything else can be restored from the chain and with your 24 words - what i mean is that you might have a backup from 14 days ago, but did something last week - and then if you choose to manually restore the pol list in config.yaml - you might have incorrect data in the entry, and i cant say how the client reacts if it meets unexpected values in there... hence why i suggest sticking to restoring the wallet from before the plotNFT creation - personally, i got a wallet db backup the day before i created my first plotNFT - so i can skip 500k blocks of wallet syncing, should i ever need to

[Jacek-ghub]

Thank you!

[Jacek-ghub]

I also used before backed up wallet db to speed up syncing, although just for a new wallet creation testing - worked great.

With that said, would it be possible to do a live backups of walled db as a client enhancement? For instance, specify duration/location/retention count for those backups in config.yaml. This way, it would not be a manual task that requires stopping the client, plus your backup would always be close to the latest.

[loppefaaret]

currently, both the node and wallet DB needs to be backed up while being offlined - wether there is any plans for it, not as far as i know, and i do not know about any ongoing work - there is some wallet things planned - but when is up in the air
as always, we do have a public available trello board with lots of plans pinned on it
https://trello.com/b/ZuNx7sET/engineering-core
though we at times do could be better at keeping it up to date - just that the devs are just kinda deepdiving straight into the next issue constantly

[Jacek-ghub]

Maybe devs can look into master/slave libs (e.g., LiteReplica, or sqlite2-sync)? Looks like not that much work to enable the client to be the master, and gives an option to implement (if desired) a slave on another box. With such design, you can always pause the slave to get up-to-date backup (manually or through a script), whether for testing, doing backups, or to speed up restoring the client.

I am not a db expert, but implemented it some time ago for MySQL, and it worked great. Not really that much work needed, but huge benefit of having hot backups.

[BrandtH22]

@TomaszWM , since this ticket was opened a number of years ago without further comments it seems this issue has been resolved.
We will be closing this ticket but if we have closed this ticket in error do not hesitate to reach out to us again with any followup questions or comments.

The best place to reach our support team is on Discord (https://discord.gg/chia) or by reopening this ticket.