Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#9,595 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
c
Ambito
backend, payments

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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?
Lingua principale
C
Stelle
3.1k
Fork
1k
Merge medio
3g 10h
PR unite (30g)
40

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ElementsProject/lightning

Tutte le issue di ElementsProject/lightning

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.