It's not entirely clear (to me) from the documentation what pieces of data the user needs to backup and retain before, during and after vaulting / unvaulting.
Obviously the private keys (just the cold one?) and all involved public keys.
(we can ignore the fee wallet private key, since an improved design could use an ephemeral dust anchor)
since all relevant data aside from key material can be regenerated algorithmically
This suggests there's no other piece of data.
the transaction ID of the coin we spent into the vault, which is the only piece of information we need to reconstruct the vault plan and resume operations.
Which is contradicted here. This implies that every time you put a new coin in the vault you need to back up another id.
Though in practice you may be able to recover this from context.
Presumably the used block_delay needs to be stored as well? I'm assuming a situation where someone has to "reinstall" any software they used.
It's not entirely clear (to me) from the documentation what pieces of data the user needs to backup and retain before, during and after vaulting / unvaulting.
Obviously the private keys (just the cold one?) and all involved public keys.
(we can ignore the fee wallet private key, since an improved design could use an ephemeral dust anchor)
This suggests there's no other piece of data.
Which is contradicted here. This implies that every time you put a new coin in the vault you need to back up another id.
Though in practice you may be able to recover this from context.
Presumably the used
block_delayneeds to be stored as well? I'm assuming a situation where someone has to "reinstall" any software they used.