lnd – Earlybirds Invest https://earlybirdsinvest.com Latest Crypto News Thu, 21 Aug 2025 20:06:51 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.7 https://i0.wp.com/earlybirdsinvest.com/wp-content/uploads/2024/12/cropped-New-Project-2024-12-17T235703.455.png?fit=32%2C32&ssl=1 lnd – Earlybirds Invest https://earlybirdsinvest.com 32 32 240146708 LND Node Crash – Channel.Backup blocks recovery https://earlybirdsinvest.com/lnd-node-crash-channel-backup-blocks-recovery/ https://earlybirdsinvest.com/lnd-node-crash-channel-backup-blocks-recovery/#respond Thu, 21 Aug 2025 20:06:51 +0000 https://earlybirdsinvest.com/lnd-node-crash-channel-backup-blocks-recovery/

My node has crashed, I’m trying to restore it.

What I have:

  • wallet.db (and password)
  • LND Wallet XPRV
  • Channel.backup (many backups available)

What I don’t have:

I started a new node and tried to copy the wallet.db and channel.backup /data/lnd/data/chain/bitcoin/mainnet.

Here is the log I get:

2025-08-21 19:08:04.923 (ERR) LTND: Shutting down because error in main method: unable to start server: unable to refresh backup file: unable to extract on disk encrypted SCB: unable to de-serialize w/ unknown version: 131
2025-08-21 19:08:04.923 (WRN) HSWC: Htlc Switch already stopped
2025-08-21 19:08:04.923 (WRN) SRVR: failed to stop htlcSwitch: htlc switch already shutdown
2025-08-21 19:08:04.923 (INF) HSWC: Onion processor shutting down...
2025-08-21 19:08:04.923 (INF) INVC: InvoiceRegistry shutting down...
2025-08-21 19:08:04.923 (WRN) SRVR: failed to stop invoices: InvoiceRegistry stopped more than once
2025-08-21 19:08:04.923 (INF) HSWC: InterceptableSwitch shutting down...
2025-08-21 19:08:04.923 (WRN) SRVR: failed to stop interceptable switch: InterceptableSwitch stopped more than once
2025-08-21 19:08:04.923 (INF) SWPR: TxPublisher stopping...
2025-08-21 19:08:04.923 (WRN) SRVR: failed to stop txPublisher: TxPublisher stopped more than once
2025-08-21 19:08:04.923 (WRN) SRVR: Unable to stop BestBlockTracker: BestBlockTracker is not running
2025-08-21 19:08:04.923 (INF) CHFT: ChannelEventStore shutting down...
2025-08-21 19:08:04.923 (WRN) SRVR: Unable to stop ChannelEventStore: ChannelEventStore stopped more than once
2025-08-21 19:08:04.923 (WRN) SRVR: unable to shutdown liveness monitor: monitor already stopped
2025-08-21 19:08:04.923 (INF) RPCS: Stopping RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping ChainRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping NeutrinoKitRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping SignRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping WatchtowerRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping InvoicesRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping AutopilotRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping WalletKitRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping RouterRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping PeersRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping WatchtowerClientRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) RPCS: Stopping VersionRPC Sub-RPC Server
2025-08-21 19:08:04.923 (INF) TORC: Stopping tor controller
2025-08-21 19:08:04.923 (ERR) TORC: DEL_ONION got error: invalid arguments: unexpected code
2025-08-21 19:08:04.923 (ERR) LTND: error stopping tor controller: invalid arguments: unexpected code
2025-08-21 19:08:04.926 (INF) LTND: Shutdown complete
unable to start server: unable to refresh backup file: unable to extract on disk encrypted SCB: unable to de-serialize w/ unknown version: 131

Does anyone know how to solve this? Chantools can also be used.

Thank you for your cooperation,

]]> https://earlybirdsinvest.com/lnd-node-crash-channel-backup-blocks-recovery/feed/ 0 54426 lnd v0.19.2 Released with key bug fixes and performance upgrades https://earlybirdsinvest.com/lnd-v0-19-2-released-with-key-bug-fixes-and-performance-upgrades/ https://earlybirdsinvest.com/lnd-v0-19-2-released-with-key-bug-fixes-and-performance-upgrades/#respond Wed, 16 Jul 2025 22:41:16 +0000 https://earlybirdsinvest.com/lnd-v0-19-2-released-with-key-bug-fixes-and-performance-upgrades/

Today, a new version of Lightning Network Daemon (LND), version 0.19.2, has been released. This update focuses primarily on bug fixes and performance improvements.

Key fixes include bugs that missed payment confirmation, rare issues that could freeze nodes during startup, and memory leaks that cause the software to use more resources over time. It also fixes crashes that can occur when a node is up in a specific mode or backup process.

This release includes an option migration to reduce the size of the “Attension Log Database” (sphinxReplay.db) to reduce disk and memory usage. This cleanup will run automatically unless it is turned off in the settings.

“Migration is optional, but by default it is turned on,” the release notes said. “If you run into problems, you can opt out of the migration by setting NO-GC-Decayed-Log = True in Config. This migration does not prevent you from being downgraded to the previous v0.19.x-beta version.”

Code Health.

Other changes include better handling of peer-to-peer (P2P) connections, better tracking log payments, and more accurate pricing calculations. This update also improves compatibility with test networks and adds small updates to the Command Line Tool (LNCLI).

Check the Docker image.

Additional improvements include improved connection handling, improved AUX traffic, and updates to the RPC interface, making debugging easier. Lightning Seed Service supports TestNet4 and Signet, making it easier to peer discovery of new nodes.

Added RPC.

This update was built using go1.23.9, allowing others to check that the released files match the original source code. Docker users can also run scripts to confirm the installation before starting the container.

Check the FAG itself.

This release can be verified using PGP signatures and opertised stamps to ensure that it has not been tampered with. Details and instructions are available here.

]]> https://earlybirdsinvest.com/lnd-v0-19-2-released-with-key-bug-fixes-and-performance-upgrades/feed/ 0 48025 Critical discrepancy: Bitcoin Core nodes look at Utxo via ScantXOutset, but not motivated from ListunSpent and Sparrow Wallet Fail; lnd keys? https://earlybirdsinvest.com/critical-discrepancy-bitcoin-core-nodes-look-at-utxo-via-scantxoutset-but-not-motivated-from-listunspent-and-sparrow-wallet-fail-lnd-keys/ https://earlybirdsinvest.com/critical-discrepancy-bitcoin-core-nodes-look-at-utxo-via-scantxoutset-but-not-motivated-from-listunspent-and-sparrow-wallet-fail-lnd-keys/#respond Mon, 21 Apr 2025 07:15:47 +0000 https://earlybirdsinvest.com/critical-discrepancy-bitcoin-core-nodes-look-at-utxo-via-scantxoutset-but-not-motivated-from-listunspent-and-sparrow-wallet-fail-lnd-keys/

Hello LND Developers and Community,

Despite being fully synchronized after Bitcoin core node (v29.0.0, RPI5 fresh IBD, txindex = 1), we are facing a very unusual and important issue that on-chain funds related to past LND channel closures are inaccessible. However, both the ListUnSpent software and the external wallet software (Sparrow) are unable to view this UTXO, and importantly, the address holding the fund cannot be derived from my LND root key using standard methods.

System and history:

LND: v0.18.5-beta (upgraded from v0.5.2-beta). Only one wallet.db has been identified that is used throughout.

Bitcoin Core: V29.0.0 (RPI5), fully synced, IBD, TXINDEX = 1 report synced: true. Datadir/MNT/HDD/BITCOIN.

Channel History: Opened in March 2019 (LND V0.5.2, Funding TX: 7060 … 9D71), later closed the power by peers.

Sweep Transaction: April 1, 2024 (block 837257), TX 4C0407B1188E0BA39313B1D9C87C49F6C81D99AA2839026C8AF8C989CE102244 used the channel output and sent 0.01495 BTC to P2WPHH. BC1QT728QPLPUH6D98EVKL4A990ZDHWPWVUR6QG8QZ.

On-Chain Verification: Explorers confirm that this UTXO (4C04 …:0) is present and does not exist in BC1QT7 … G8QZ.

Core Issues and Conflicts:

After full IBD, make sure the txindex is synced on the Bitcoin Core node.

getrawtransaction 4c04... true Success: Node knows the history of funding transactions.

scantxoutset start '("addr(bc1qt7...)")' Returns UTXO successfully. This directly confirms that the node’s chainstate (UTXO set) database is correct and contains the previous output of BC1QT7 … G8QZ.

{
  "success": true, ...
  "unspents": ( { "txid": "4c04...", "vout": 0, ... "address": "bc1qt7...", "amount": 0.01495437 ... } ),
  "total_amount": 0.01495437
}

listunspent ... '("bc1qt7...")' (use -rpcwallet="" or any other loaded wallet) Returns (): Despite the UTXO present in the chain state, wallet-specific RPC calls cannot list it.

Sparrow Wallet (a fresh install connected to this node) shows a balance of 0. Import the confirmed LND root XPRV and configure BIP84 (M/84’/0’/0”, native Segwit P2WPKH), Sparrow completes the scan, but shows 0 balance and uses utxos.

Parallel Wallet Derived Failure:

Verified root XPRV (extracted from the correct Wallet.db via Chantools Showrootkey), using extensive checks using the offline tool (bip39-Standalone.html) (m/84’/0’/0’/0’/* and m/84’/0’/0’/0’/1/*). BC1QT728QPLPUH6D98EVKL4A990ZDHWPWVUR6QG8QZAfter checking millions of addresses.

Current Status and Emergency Questions:

I have an on-chain fund in bc1qt7…g8qz (per scantxoutset) the nodes fundamentally know, but they are not accessible via standard wallet RPC (listunspent) and external wallet (sparrow). To consolidate this is that you cannot derive this particular address from the LND root key using the standard BIP84 path.

Seek expert help:

Why can’t external wallets like Sparrow and external wallets like Sparrow not display UTXO when ScantxOutset on the same node confirm its presence in the UTXO set? Is this a known core bug, an issue with how Wallets queries addresses other than owners, or is it something else?

Given the derivation failure, is it possible for LND (especially after major version jump) to wipe out funds from the Aezeed root key to addresses that cannot be derived via the standard BIP84 path? Is a bug or a particular state likely to lead to using different derivation schemes, or can you use important keys that are unrelated to the main wallet in the sweep output?

Advanced methods or tools (LND debug commands, using specific Chantools, alternative wallet software known to handle edge cases) are:

a) Force Sparrow/LND to recognize UTXO based on node chain state confirmation?

b) Does it help clearly track the derived paths (even non-standard) used to generate bc1qt7…g8qz from wallet.db/xprv?

This situation seems very unusual. The insights and guidance are highly appreciated.

thank you.

]]> https://earlybirdsinvest.com/critical-discrepancy-bitcoin-core-nodes-look-at-utxo-via-scantxoutset-but-not-motivated-from-listunspent-and-sparrow-wallet-fail-lnd-keys/feed/ 0 31982