Your LND seed backup exists. But have you actually verified it?
I wanted to answer a simple question about my own LND disaster recovery setup:
If the node disappeared today, could the 24-word aezeed I have stored offline actually derive the wallet holding my on-chain funds?
So I tested it.
I used a separate offline computer and a verified chantools v0.14.2 binary. The aezeed was entered interactively — never passed as a CLI argument, stored in a plaintext file, or exposed to an online service.
The core command was:
chantools genimportscript --format bitcoin-descriptors --lndpaths --recoverywindow 2500
Before the test, I identified three P2TR addresses containing real UTXOs belonging to the live LND wallet.
From the offline aezeed, chantools generated the wallet descriptors and all three known P2TR addresses were successfully reproduced.
No restore was performed. No bitcoin was moved. This was purely an offline recovery audit.
I documented the complete procedure here:
https://github.com/shadowbipnode/sovereign-linux-tools/blob/main/guides/lnd-aezeed-offline-audit.md
One important distinction: this verifies the aezeed against the on-chain wallet. It does not replace your Static Channel Backup.
aezeed → on-chain recovery
SCB → Lightning channel recovery
A backup isn’t really tested because the file or seed exists.
Test it before the emergency.
Write a comment