Separate Offers from Wallet database, so offer files are retained when deleting the wallet database due to issues.

[OverActiveBladderSystem]

Occasionally users have deleted the wallet database as a solution to problems (either on their own or advised to do so) and any existing offers get deleted with it, this has caused issues like forgotten offers and/or having to recreate offers to track in the GUI.

Users could (after resync) spend all their coins to ensure offers get cancelled on chain but this can be problematic, it could come with a cost per transaction and is not practical to do so with hundreds or thousands of existing offers (and/or assets).

Would separating Offers from the Wallet database be an ideal solution?

An "Offer directory" with a text file for each offer could allow for offer files to be added back when a wallet database is deleted, allowing the user to pickup where they left off with minimal disruption (also allowing portability between wallet vendors if they adopt).

This could also be used for additional identification and organization of offer files by amending "active" "accepted" "expired" "(custom tag)" etc etc to the file names, allowing users to group and sort offer files by type for taxes or other reasons.

[OverActiveBladderSystem]

Piggybacking off this idea of separating Offers from the Wallet database...

A similar issue is experienced with manually added descriptive names of CAT coin assets added to the wallet. Users who delete the wallet database must now re-add all the individual asset names they have entered prior (some users have several dozen different CAT coins).

Is there a way to also separate the users manually added CAT coin naming data from the wallet database for recovery purposes?

Data that can be recreated easily via a blockchain sync is less important to safeguard, but data users manually add/create should be protected because it is not so easy to recover from that without missing items or spending unnecessary time and potential costs to do so.