Archive key material on wallet closure #3797
Assignees
Labels
Comments
lukasz-zimnoch
added a commit
that referenced
this issue
Jun 11, 2024
#Refs: #3797. This PR handles archiving key material on wallet closures. Archiving the wallet data happens in two situations: - when the `WalletClosed` event is received - on node start, if there are closed wallets in the node's wallet registry. Archiving wallet's key material causes the wallet data to be moved to the `archive` directory and the wallet is removed form the registry's cache.. Such wallets will no longer participate in the RFC-12 coordination.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wallet operators should listen to
Bridge'sWalletClosedevents and perform necessary operations upon wallet closure. The most important thing is archiving the key material so the given wallet is no longer considered active by the operator's node. This is important in the context of the new RFC 12 coordination mechanism as closed wallets' operators should not waste network bandwidth for coordination messages.Tasks
The text was updated successfully, but these errors were encountered: