mirror of
https://github.com/ACINQ/eclair.git
synced 2025-03-01 00:58:59 +01:00
530b3c206f
We remove utxos locks that were previously set, otherwise we may have utxos that stay locked indefinitely. This may happen if we started funding a channel and restarted before completing the funding flow: the channel will be safely forgotten but the corresponding utxos stay locked. The only drawback that this may have is if we have funded and signed a funding transaction but didn't publish it and we accidentally double-spend it after a restart. This shouldn't be an issue because: - locks are automatically removed when the transaction is published anyway - funding transactions are republished at startup if they aren't in the blockchain or in the mempool - funding transactions detect when they are double-spent and abort the channel creation - the only case where double-spending a funding transaction causes a loss of funds is when we accept a 0-conf channel and our peer double-spends it, but we should never accept 0-conf channels from peers we don't trust We provide three strategies when locked utxos are detected: stop eclair, unlock the utxos automatically, or ignore them. |
||
|---|---|---|
| .. | ||
| release-notes | ||
| API.md | ||
| Architecture.md | ||
| CircularRebalancing.md | ||
| Cluster.md | ||
| Configure.md | ||
| FAQ.md | ||
| Features.md | ||
| Guides.md | ||
| Logging.md | ||
| Monitoring.md | ||
| MultipartPayments.md | ||
| PostgreSQL.md | ||
| Tor.md | ||
| TrampolinePayments.md | ||
| Usage.md | ||