Repeatedly RBF the Tx with the same fee after channel close

[19710405]

Issue and Steps to Reproduce

After a channel was force closed by my own node, it repeatedly trying to RBF the p2wkh output with the same fee.

Worse, it keeps trying to use 1sat/vbyte which isn't even enough to enter the mempool.

From the log:

2023-05-26T23:32:24.062Z INFO    02d695b01c7a6909e716c863fb39bc5fb7bbdc3824b7fdce53adc593e5be080e73-chan#97: RBF onchain txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat) with txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat)
2023-05-26T23:33:04.064Z INFO    02d695b01c7a6909e716c863fb39bc5fb7bbdc3824b7fdce53adc593e5be080e73-chan#97: RBF onchain txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat) with txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat)
2023-05-26T23:33:57.066Z INFO    02d695b01c7a6909e716c863fb39bc5fb7bbdc3824b7fdce53adc593e5be080e73-chan#97: RBF onchain txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat) with txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat)
2023-05-26T23:34:39.071Z INFO    02d695b01c7a6909e716c863fb39bc5fb7bbdc3824b7fdce53adc593e5be080e73-chan#97: RBF onchain txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat) with txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat)
2023-05-26T23:35:25.073Z INFO    02d695b01c7a6909e716c863fb39bc5fb7bbdc3824b7fdce53adc593e5be080e73-chan#97: RBF onchain txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat) with txid 8b9b8c2999ccc0e8380cc50a5cd439b523045af1a835cd524d6d87a597eb785c (fee 122sat)

"version": "23.05"

From listchannels:

"status": [
            "ONCHAIN:Tracking our own unilateral close",
            "ONCHAIN:1 outputs unresolved: waiting confirmation that we spent DELAYED_OUTPUT_TO_US (cd76421b6e8762ae7f32b76597a9f9eac000d3e49a530513910248096350a4b4:0) using OUR_DELAYED_RETURN_TO_WALLET"
         ],

Is there a config for setting the fee rate of the OUR_DELAYED_RETURN_TO_WALLET tx? Thanks!

[rustyrussell]

Since there's no hurry, it's using a deadline of 300 blocks by default. Anything over 200 blocks always gets sent at 1 sat/vbyte. 100-200 blocks away we use whatever is the minimum to get us into the mempool. 100 and less we start asking bitcoind for estimates.

We do keep spamming with RBF (uselessly), though INFO level is a bit obnoxious, so I'll downgrade that...