Skip to content

Commit

Permalink
GITBOOK-427: change request with no subject merged in GitBook
Browse files Browse the repository at this point in the history
  • Loading branch information
Leo Weese authored and gitbook-bot committed May 16, 2024
1 parent 4d36be9 commit 4b32546
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion lightning-network-tools/pool/account_recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

In this section, we'll cover the possible ways of recovering the funds within a Pool account upon data corruption/loss. Account funds are locked to a 2-of-2 multi-sig output of the account owner and the Pool auctioneer until the account's expiration has been met, giving the account owner full control of the funds. This expiration is included in the account output script, so it must be known in order to spend the account funds. There are two possible ways to recover an account's funds after data corruption/loss: one that requires the Pool auctioneer's cooperation, which is the only method currently supported, and one without, which will require storage of an additional data blob similar to the Static Channel Backups present within `lnd`. An auctioneer-assisted account recovery intent can be issued through the `pool accounts recover` command or the `RecoverAccounts` RPC.

```text
```
$ pool accounts recover -h
NAME:
pool accounts recover - recover accounts after data loss with the help of the auctioneer
Expand Down Expand Up @@ -32,3 +32,7 @@ Upon the auctioneer receiving the intent, it will verify the challenge response,

Note that as a part of this process, all orders belonging to an account being recovered are canceled within the auction and are not restored to the account owner.

## Umbrel

In Umbrel, you may run the following command to recovery your account:\
`docker exec -it lightning-terminal_web_1 pool --rpcserver=localhost:8443 --tlscertpath=~/.lit/tls.cert accounts recover`

0 comments on commit 4b32546

Please sign in to comment.