Will there be options for deleting seeds in the vault with future updates?
Imported seeds can already be deleted, but seeds derived on device are always re-derivable thanks to the BIP85 standard, so they can never really be truly deleted. This is why there is no UI option for this after archiving it.
Ok, got the point, but how can I make them invisible on the UI and in the archive. I want to get rid of a generated derived test seed in the UI in order to have a blank UI again.
There is currently no way to delete an archived child seed from view. Leaving it in the archive is completely harmless and has no impact on any other secrets in the vault.
Thanks for your answer, so now I can be sure, not to have missed anything. When I was onboarding Prime I wanted to test seed generation and played with it, so the archive started to get a little crowded. My use case for prime will be primarily general digital security and not storing seeds for wallets. So in order to get a clean UI I deleted my old master seed/key and created a new one, also deleted magic backup cards and re NFCed them with the newly generated master key. Now everything is clean for starting real application. Best to the team and all fellow Primers.
Thanks for circling back and mentioning the steps you took. Useful for others who might find themselves in a similar situation.
Is there a reason not to allow deleting from the archive? Some people like to keep things clean.
Derived seeds work differently to imported ones. Each is identified by its BIP85 index, and the Vault will not let you reuse an index. Try it and you get “Index is already in use”. The archived entry is what remembers that the index was used, so deleting it would lose that record and you could unknowingly derive the same child seed again later under a different name or for a different purpose.
I understand those risks. Perhaps adding the delete option with a warning to that effect?
@Jack leet’s add to backlog
SFT-7911 created to track this request - thanks!