Continuously request open channel to create a channel at an interval of 1s, and find that the channel cannot be updated to the ready state.

Bug Report

Current Behavior

Use the script to continuously request openchannel to create a channel at an interval of 1s, and find that the channel cannot be updated to the ready state.

2024-10-23T09:27:39.868492Z ERROR fnn::fiber::channel: Error while processing channel message: Musig2VerifyError(BadSignature)

Due to this error, the channel status cannot be updated to the final state of CHANNEL_READY. The current status of 100 channels is SIGNING_COMMITMENT.

$ curl --location 'http://127.0.0.1:8227/' --header 'Content-Type: application/json' --data '{
    "id": 42,
    "jsonrpc": "2.0",
    "method": "list_channels",
    "params": [
        {
        }
    ]
}' | jq 'has("CHANNEL_READY")'
  % Total % Received % Xferd Average Speed ​​Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 41192 100 41077 100 115 2399k 6880 --:--:-- --:--:-- --:--:-- 2514k
false

Expected Behavior

Added that when a permanent error is encountered, the channel fails directly.

Environment

• fiber version: fnn 0.1.0
• Ckb Chain: testnet
• Operating system: Ubuntu 20.04
• Arch: Linux ip-172-31-100-41 6.8.0-1016-aws #17-Ubuntu SMP Mon Sep 2 13:48:07 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
• Installation: Built from source

Additional context/Screenshots

node1.log.tar.gz
node2.log.tar.gz
node3.log.tar.gz
script.bash.tar.gz

Start by reviewing script.bash.tar.gz and the node logs, then reproduce repeated openchannel requests at one-second intervals and trace the fnn::fiber::channel handling of Musig2VerifyError(BadSignature). Done means a permanent error transitions the channel to a failed state instead of leaving it stuck in SIGNING_COMMITMENT.