A few days ago I did a submarine swap in order to rebalance a channel of mine. I opted to be refunded on-chain using a brand-new address generated with c-lightning newaddr command. I used the p2sh address (aka starting with 3...) because last time I had some issues with the bech32 version.
Here is the point: the on-chain transaction has (at time of writing) more than 80 confirmations, but my c-lightning node still cannot show the output with the listfunds command.
Using dev-rescan-outputs didn't get any results as well.
Am I miss something? Have that utxo gone lost?
Asked
Active
Viewed 131 times
1
dc_Bita98
- 394
- 3
- 14
-
your not bitcoin is update to the network? – vincenzopalazzo Dec 18 '19 at 14:50
-
absolutely yes, up and running – dc_Bita98 Dec 18 '19 at 14:58
-
1So `lightning-cli getinfo` has the same blockheight as `bitcoin-cli getblockchaininfo` and it matches what blockexplorers say is the latest block? You can try rescanning using `--rescan=-confirmationheight` (notice the minus in front of the absolute height). – cdecker Dec 18 '19 at 15:46
-
both have 608865 as **block-height** – dc_Bita98 Dec 18 '19 at 15:52
-
rescan completed, no results at all. Really concerned of losing those funds – dc_Bita98 Dec 18 '19 at 16:32
-
1No worries, if the funds are there, we should be able to recover them. Might just be a regression that we fail to look for `p2sh` outputs. – cdecker Dec 18 '19 at 19:21
-
For more flexibility in debugging this issue we migrated the discussion here https://github.com/ElementsProject/lightning/issues/3359 – cdecker Dec 19 '19 at 14:14
-
We will write a summary here once the issue has been resolved with the necessary details. – cdecker Dec 19 '19 at 14:15
1 Answers
0
For readers, this issue has been solved by @cdecker here: https://github.com/ElementsProject/lightning/issues/3359.
TL;DR: Use the --rescan startup parameter of lightningd.
Antoine Poinsot
- 5,881
- 2
- 11
- 28