Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Funder-side channel stuck in CHANNELD_AWAITING_LOCKIN if funding never confirms

未关闭
#9,112 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
c

调研方向

从复现器 #9113 开始,跟踪 CHANNELD_AWAITING_LOCKIN 附近的 funder 侧通道状态处理,包括 spenderp 清理和 unreserveinputs 路径。将其与现有 BOLT 2 fundee 侧的 forget 规则以及 --max-funding-unconfirmed-blocks 进行比较。当 funding 交易永远无法确认的 funder 侧通道会被 forget,而不是无限期保留时,即表示完成。

由索引模型根据 Issue 内容生成。

描述

When a node is the funder of a channel whose funding tx never
confirms — broadcast rejected at ATMP, evicted from mempool, or
simply never broadcast — the channel record stays in
CHANNELD_AWAITING_LOCKIN indefinitely. CLN already implements the
BOLT 2 fundee-side forget rule (PR #1468,
--max-funding-unconfirmed-blocks, default 2016) but has no
equivalent on the funder side. Once the would-be funding inputs are
spent in other transactions the funding tx is permanently
unconfirmable, yet the channel record remains.

Similar to #9102

Concrete instance

More details about the following channel can be found in clboss
issue #312
.
@ksedgwic operates the funder.

Channel
  • channel_id: 0b12c289525bf5593e932eca14277dbcb0921f125731b586d3a75d2f4b328dde
  • funding_txid: de8d324b2f5da7d386b53157121f92b0bc7d2714ca2e933e59f55b5289c2120b — never confirmed on chain
  • opener: us; closer: us
  • created 2025-10-14; broadcast rejected by bitcoind at 22:46:28 UTC
    with min relay fee not met, 507 < 511; spenderp ran cleanup
    (unreserveinputs) but the channel record on lightningd's side
    persisted
  • still in AWAITING_UNILATERAL (a later close attempt also could not
    broadcast — its commitment input is the never-existing funding
    output) on our node as of 2026-05-04, ~6.5 months later
  • All 7 of the funding tx's input UTXOs are now spent in other
    transactions, so the funding tx can never confirm

Reproducer

Reproduced by #9113

主要语言
C
星标
3.1k
派生
1k
平均合并
4 天 4 小时
30 天内合并 PR
27

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ElementsProject/lightning 的其他 Issue

查看 ElementsProject/lightning 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。