在AwaitingChannel Ready被困了数小时——不能放弃/下沉;只重新开始增加故障细节(用同对等点重复两次)

Summary On fnn 0.8.1, a channel can stay in: AwaitingChannelReady(OUR_CHANNEL_READY) for hours after funding is confirmed on-chain, never transitioning to ChannelReady. While stuck: - abandon_channel is rejected ("please shutdown the channel instead") - shutdown_channel (cooperative) is rejected (invalid state) - shutdown_channel(force=true) is rejected (invalid state) I then restarted the node hoping it would recover. After restart, the channel was still stuck, and list_channels started showing: failure_detail: "Peer disconnected during channel opening" So that failure string is a post-restart symptom, not the original reason the open got stuck. Before restart, the channel was already stuck in AwaitingChannelReady with no recovery path. Related: #1545, #606, #996. ## Environment Network: CKB testnet fnn: 0.8.1 ## Timeline (current incident) 1. Opened a public channel with peer 03bf42…7b10 (I already had 3 Ready channels with this peer). 2. Funding confirmed on-chain. 3. Local state stayed in AwaitingChannelReady(OUR_CHANNEL_READY) and **did not become Ready after waiting ~2+ hours. 4. Tried recovery RPCs while still in that state — all failed (see below). 5. Restarted fnn to see if state would heal. 6. After restart: still stuck in AwaitingChannelReady; now also shows failure_detail: "Peer disconnected during channel opening". 7. Peer is currently connected again (list_peers); reconnect + retry shutdown still fails. ## Pattern I observed (hypothesis) Same remote peer both times: - Peer pubkey: 03bf4208b9ada97a5589ef9924819fe511b2a5e9ed3812df21a79435d39a147b10- Peer multiaddr:/ip4/49.13.159.45/tcp/8228/p2p/Qmc9gzZB7aHYrVNxpakaQ8mLFchnnkesLhDfPPJEHQNbPtIn my cases this correlates with **~100k CKB aggregate capacity already open / opening with this peer** (hypothesis only): 1. **First wallet** — large opens stuck (~100k + ~50k). 2. **Second wallet** — opened smaller channels bit-by-bit. First three becameChannelReady(~20k + ~30k + ~50k ≈ **99,703 CKB**). A fourth ~50k channel then stuck the same way. This is not "first channel with peer fails"; Ready channels with the peer already existed when the latest one got stuck. ## Incident A — first wallet (earlier) **My node pubkey** 03ea6d62f0dab7a9a4e1162f7f7a19b78db9d908468728ae5e2407713cbb09f0e6 **Announced address** /ip4/197.211.63.22/tcp/8228/p2p/QmPWAqZUFxYwjH3b9VKT1P9Nh6cQMCbvqHUBxzqVjxkD8i Stuck channels (fnn 0.8.1). Funding confirmed; bothAwaitingChannelReadywithOUR_CHANNEL_READY|CHANNEL_READY. After restart attempts, failure detail was also Peer disconnected during channel opening. 1. **~100k CKB** - channel_id: 0x7cc479b706ce66e322c1c2dcacc2ca278e93d56c43eb31162a14046057457418 - funding tx / outpoint: 0x852fac88c14602d51256511ecf7603706ac75fbb7f7219fab25377bc943f1dc1:0 - created: 2026-07-10 01:30:15 UTC 2. **~50k CKB** - channel_id`: 0x7cc479b706ce66e322c1c2dcacc2ca278e93d56c43eb31162a14046057457418 - funding tx / outpoint: 0x852fac88c14602d51256511ecf7603706ac75fbb7f7219fab25377bc943f1dc1:0 - created: 2026-07-10 01:30:15 UTC