1. Start by checking your TX
You can see your transaction/payment channel here on a LN Explorer:
ln.fiatjaf.com (query it here)
I have included the output (below)
from `satoshi_LM_bot`|base fee (sat)|fee %|delay (min HTLC locktime)|update|
| --- | --- | --- | --- |
from `03f9766594831b459b23`|base fee|fee %|delay|update|
| --- | --- | --- | --- |
|1 sat|0.0001|40|2021-07-29 08:50:22|
| --- | --- | --- | --- |
2. Read this guide on Recovery
Read this guide (Medium Link below):
Basically, we want to interact with your LND daemon on your node.
We are aiming to issue commands to your node to restore the "channel.backup" file which could be on your system as it could be created by default, automatically.
- If you can connect to your Umbrel node, you can do this over SSH / Terminal into your node then navigate to your LND CLI (If you have access to it ?) [recursive method]
ssh email@example.com <change to your IP>
- Change Directory to your lnd-cli
$ cd /home/umbrel/umbrel/bin
- Then List directory with argument -al to reveal your lnd daemon
umbrel@umbrel:~/umbrel/bin $ ls -al
drwxrwxr-x 2 umbrel umbrel 4096 Aug 5 16:43 .
drwxr-xr-x 18 umbrel umbrel 4096 Aug 17 02:43 ..
-rwxrwxr-x 1 umbrel umbrel 323 Aug 5 16:43 bitcoin-cli
-rwxrwxr-x 1 umbrel umbrel 313 Aug 5 16:43 lncli
- To interact with the LN Daemon you need to issue the “bash” command:
umbrel@umbrel:~/umbrel/bin $ bash lndcli --help
- Switch the - -help command with the commands in the guides to try and recover your funds.
These are the commands you will need to utilise:-
$ lncli restorechanbackup [command options] [–single_backup] [–multi_backup] [–multi_file]
–single_backup value - a hex encoded single channel backup obtained from exportchanbackup
–multi_backup value - a hex encoded multi-channel backup obtained from exportchanbackup
–multi_file value - the path to a multi-channel back up file
Read the guide here:
medium.com - Enable Channel Backups and fund Recovery on LND lightning network
The aim is to restore your channels so that you can see/interact with your transaction through bash/ssh command line.
How to access your funds after the time lock has occurred?
To be honest I don’t know your exact situation and its kind of difficult to troubleshoot as I’m not hands on sort of speak.
I don’t want to suggest anything I am not 100% on which could possibly make things worse…
- Based on what you have already stated you don’t have the channel backup…
- The payment-channel was Closed unilaterally
- You do have your 24-word Recovery phrase
So, this is going to be a bit long winded as I am still getting to grips with this tech myself.
If you have access to the node via SSH you should be golden.
Query the LND
api.lightning (LND API Ref shell#closechannel)
- In the reference documentation manual it states the following comment:
# Close an existing channel. The channel can be closed either cooperatively,
# or unilaterally (--force).
# A unilateral channel closure means that the latest commitment
# transaction will be broadcast to the network. As a result, any settled
# funds will be time locked for a few blocks before they can be spent.
# In the case of a cooperative closure, one can manually set the fee to
# be used for the closing transaction via either the --conf_target or
# --sat_per_vbyte arguments. This will be the starting value used during
# fee negotiation. This is optional.
# In the case of a cooperative closure, one can manually set the address
# to deliver funds to upon closure. This is optional, and may only be used
# if an upfront shutdown address has not already been set. If neither are
# set the funds will be delivered to a new wallet address.
# To view which funding_txids/output_indexes can be used for a channel close,
# see the channel_point values within the listchannels command output.
# The format for a channel_point is 'funding_txid:output_index'.
$ lncli closechannel [command options] funding_txid [output_index]
# --funding_txid value the txid of the channel's funding transaction
# --output_index value the output index for the funding output of the funding transaction (default: 0)
# --force attempt an uncooperative closure
# --block block until the channel is closed
# --conf_target value (optional) the number of blocks that the transaction *should* confirm in, will be used for fee estimation. If not set, then the conf-target value set in the main lnd config will be used. (default: 0)
# --sat_per_vbyte value (optional) a manual fee expressed in sat/vbyte that should be used when crafting the transaction (default: 0)
# --delivery_addr value (optional) an address to deliver funds upon cooperative channel closing, may only be used if an upfront shutdown address is not already set
- So we know the channel was closed unilaterally (–force’ed)
- This means that a number of blocks will need to be pass before HTLC (Time-lock) expires to unlocks your transaction.
If the medium article in step 2. has not resolved your issue the only alternative’s I can see is to
See, if waiting for the time lock to elapse and hopefully this will solve the problem and have it back into your wallet available to be spent.
Or if you have no luck using the cli maybe you could somehow use a light wallet like Blue Wallet to send out the sats after unlocked.
Apologies for such a bloated document.
I am researching this problem with you but I will try to update with a more thorough/complete answer after a little more research.
Try to glean some information from your log file you will need to pipe it out to a new file >>
umbrel@umbrel:~/umbrel/lnd/logs/bitcoin/mainnet $ cat lnd.log |grep <your txid>