1

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?

Improve this question
8
  • your not bitcoin is update to the network?
    – vincenzopalazzo
    Dec 18, 2019 at 14:50
  • absolutely yes, up and running
    – dcfg
    Dec 18, 2019 at 14:58
  • 1
    So 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, 2019 at 15:46
  • both have 608865 as block-height
    – dcfg
    Dec 18, 2019 at 15:52
  • 1
    No 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, 2019 at 19:21

1 Answer 1

Reset to default
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.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.