<p>For readers, this issue has been solved by @cdecker here: <a href="https://github.com/ElementsProject/lightning/issues/3359" rel="nofollow noreferrer">https://github.com/ElementsProject/lightning/issues/3359</a>.</p>

<p>TL;DR: Use <a href="https://lightning.readthedocs.io/lightningd-config.5.html#general-options" rel="nofollow noreferrer">the <code>--rescan</code> startup parameter of <code>lightningd</code></a>. </p>

CC BY-SA 4.0
2020-02-10T11:09:49.277Z
2020-02-10T11:09:49.277Z
Antoine Poinsot
<p>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 <code>newaddr</code> command. I used the <code>p2sh</code> address (aka starting with 3...) because last time I had some issues with the <code>bech32</code> 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 <code>listfunds</code> command. 
Using <code>dev-rescan-outputs</code> didn't get any results as well. 
Am I miss something? Have that utxo gone lost?</p>

CC BY-SA 4.0
2019-12-18T14:50:14.560Z
your not bitcoin is update to the network?
vincenzopalazzo
CC BY-SA 4.0
2019-12-18T14:58:51.727Z
absolutely yes, up and running
dcfg
CC BY-SA 4.0
2019-12-18T15:46:13.403Z
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
CC BY-SA 4.0
2019-12-18T15:52:03.600Z
both have 608865 as **block-height**
dcfg
CC BY-SA 4.0
2019-12-18T16:32:10.063Z
rescan completed, no results at all. Really concerned of losing those funds
dcfg
CC BY-SA 4.0
2019-12-18T19:21:26.287Z
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
CC BY-SA 4.0
2019-12-19T14:14:39.863Z
For more flexibility in debugging this issue we migrated the discussion here https://github.com/ElementsProject/lightning/issues/3359
cdecker
CC BY-SA 4.0
2019-12-19T14:15:11.873Z
We will write a summary here once the issue has been resolved with the necessary details.
cdecker
<lightning-network><core-lightning><lost-transactions><funds><submarine-swaps>
c-lightning missing outputs
dcfg
# c-lightning missing outputs

(Asked by: username_0 on 2019-12-18)

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?

**Tags:** lightning-network, core-lightning, lost-transactions, funds, submarine-swaps

> **Comments:**
> **username_1**: your not bitcoin is update to the network?  
> **username_0**: absolutely yes, up and running  
> **username_2**: 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).  
> **username_0**: both have 608865 as **block-height**  
> **username_0**: rescan completed, no results at all. Really concerned of losing those funds  
> **username_2**: 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.  
> **username_2**: For more flexibility in debugging this issue we migrated the discussion here https://github.com/ElementsProject/lightning/issues/3359  
> **username_2**: We will write a summary here once the issue has been resolved with the necessary details.  

---

## 1 answers

### Answer by username_3 on 2020-02-10. Score: 0 | Accepted answer

For readers, this issue has been solved by @username_2 here: <https://github.com/ElementsProject/lightning/issues/3359>.

TL;DR: Use [the `--rescan` startup parameter of `lightningd`](https://lightning.readthedocs.io/lightningd-config.5.html#general-options).


---

