endothermicdev on Nostr: We had fun encountering this particular fee environment scenario in Core Lightning ...
We had fun encountering this particular fee environment scenario in Core Lightning for the first time. The minimum acceptable feerate could end up the same as the proposed feerate (typically they are relatively far apart.) Then if one node increased by a single sat it would disable the channel and force a disconnect due to feerate disagreement. We now ensure a minimum offset (by the feerate proposer) to account for the next_block_feerate == min_relay_feerate situation.
Published at
2024-01-04 22:41:52Event JSON
{
"id": "11e5196ddf2fb3d351bd35888170e1311994b63080c52f2d4b5c8c837bccc0fc",
"pubkey": "6a46242f4d73c14e114d95e1336439f5b91189571dd9c2d4fa418db018cb8ef5",
"created_at": 1704408112,
"kind": 1,
"tags": [
[
"e",
"2b13d586033f17a49d8534a3e56e5e86f86ccf6f1f6b42ac0e2b246f5a8330bb",
"",
"root"
],
[
"p",
"ccaa58e37c99c85bc5e754028a718bd46485e5d3cb3345691ecab83c755d48cc"
]
],
"content": "We had fun encountering this particular fee environment scenario in Core Lightning for the first time. The minimum acceptable feerate could end up the same as the proposed feerate (typically they are relatively far apart.) Then if one node increased by a single sat it would disable the channel and force a disconnect due to feerate disagreement. We now ensure a minimum offset (by the feerate proposer) to account for the next_block_feerate == min_relay_feerate situation.",
"sig": "44383cea2eef7c528baf969bd9f78d173f122a9bfe002d0619cc719619ff39d2e125e88d3b0a0f2186d8b39d875c6ec11b29ff00b9e21323a24addf3b4ae2add"
}
