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

Core Lightning onchaind failed to resolve 3,043,561 sats after remote-initiated splices

未关闭
  • 哪里不对？
#9,595 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
c
领域
backend, payments

调研方向

Start with the reported onchaind messages, the three funding-spend transaction IDs, and the affected output indexes. Compare the outputs’ listchainmoves and listfunds state and investigate the rejected dev-rescan-outputs command, without restoring the backup or broadcasting a transaction. Done means identifying a supported recovery or reindexing procedure and confirming the outputs are safely handled.

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

描述

Hello,

I’m running StartOS 0.4.0.1 with Core Lightning 26.06.8:3 on Bitcoin.

Three channels recently went through remote-initiated splice operations. In each case, the channel briefly returned to CHANNELD_NORMAL, then received a protocol error and went on-chain.

Affected channels:

969219x39x0
969244x29x1
969290x93x0

The observed sequence was:

  1. The channel reached CHANNELD_NORMAL.
  2. The remote peer initiated a splice.
  3. The splice completed.
  4. The channel returned briefly to CHANNELD_NORMAL.
  5. CLN received a protocol ERROR.
  6. The channel entered AWAITING_UNILATERAL.
  7. The remote peer spent the funding transaction.
  8. CLN’s onchaind failed to resolve some outputs.

The relevant CLN log message was:

Could not find resolution for output 2: did *we* cheat?
Could not find resolution for output 3: did *we* cheat?

CLN later logged:

onchaind complete, forgetting peer

The funding-spend transactions were:

f54914b3b3bea085ad13ba28414423c833ac42142c66db62a4a767b04129bb14
ffa608bc6c672ed7d6dfd161ca537bbc1579df7c2da575e52806cabcdac30ff8
c4e0b155116be1d96f7d5fc540a9f0a97fb2bc857a44b7ff45c4c7c58ed8c076

The local outputs identified by CLN are:

f54914...:3  1,229,771 sats  confirmed at block 969222
ffa608...:3  1,229,171 sats  confirmed at block 969247
c4e0b1...:2    584,619 sats  confirmed at block 969296

Total:

3,043,561 sats

These outputs are now past the apparent CSV delay. However:

  • They remain credited in listchainmoves.
  • Each still has debit_msat: 0.
  • They do not appear in listfunds as wallet outputs.
  • No sweep transaction has been created.
  • CLN is fully synced.
  • The node is still running and has active channels.
  • The funds have not been manually spent or moved.

I attempted:

dev-rescan-outputs

but CLN rejected it because developer-only commands are disabled.

I also upgraded CLN to 26.06.8:3. The upgrade did not resolve the outputs, but the node identity and channel database remained intact. I have a StartOS service backup from September 21, although it predates these splice events.

I have not:

  • Deleted the CLN database.
  • Restored the backup.
  • Manually spent the outputs.
  • Shut down the node.
  • Broadcast any recovery transaction.

Could someone advise on the supported recovery procedure?

Specifically:

  1. Is this a known splice or onchaind resolution issue in CLN 26.06.8:3?
  2. Can the broken onchaind state be repaired or reindexed?
  3. Is there a supported way to rescan or re-register these mature outputs?
  4. Should the September 21 StartOS backup be provided or inspected?
  5. What is the safest way to recover the outputs without constructing or broadcasting an unsafe manual transaction?
  6. Is there any additional diagnostic information I should collect?
主要语言
C
星标
3.1k
派生
1k
平均合并
3 天 10 小时
30 天内合并 PR
40

环境准备

  • 提供 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 摘要。