I did a bit more research on my own and it seems:
• Monolithic sent an update_fee with a high fee rate (6444 sats/kw) to adapt to current Bitcoin network conditions or their internal policy.
• My Alby Hub node rejected it, citing excessive dust exposure risk for 6.645 million msat in pending transactions.
Unable to reconcile this (e.g., if Monolithic couldn’t lower the fee rate or my node wouldn’t budge),
Monolithic force-closed the channel to avoid being stuck with an unresponsive or risky peer.
• This appears not to be about inactivity or my brief offline period being the sole cause—it’s about a mismatch in how my node (Alby Hub??) and Monolithic handled fee adjustments and risk tolerance with one another
Jason Ansley | Fractional COO | $BTC
npub1ur…xdx2w
2025-03-28 02:05:12
in reply to nevent1q…jlfw
Author Public Key
npub1ur5ju4pd0xegu7wxal543ywn3aykxmjg2c9gucvtj5aaa43sm74qcxdx2wPublished at
2025-03-28 02:05:12Event JSON
{
"id": "1bc547819d89b7aae97fe3932b9f9c4422ce232626b95806fa8c89433c6b7bb6",
"pubkey": "e0e92e542d79b28e79c6efe95891d38f49636e48560a8e618b953bded630dfaa",
"created_at": 1743127512,
"kind": 1,
"tags": [
[
"p",
"e0e92e542d79b28e79c6efe95891d38f49636e48560a8e618b953bded630dfaa",
"",
"mention"
],
[
"p",
"4657dfe8965be8980a93072bcfb5e59a65124406db0f819215ee78ba47934b3e",
"",
"mention"
],
[
"p",
"7f5c2b4e48a0e9feca63a46b13cdb82489f4020398d60a2070a968caa818d75d",
"",
"mention"
],
[
"e",
"5474380e5f264436469ab5c5cf1db466b558623cc721a2c9c497aef93e600d20",
"",
"root"
],
[
"e",
"7c873e93f9be7ac33bfea857e440d459f0e3843e53997c3c61865c333d80357c",
"",
"reply"
]
],
"content": "I did a bit more research on my own and it seems: \n\n• Monolithic sent an update_fee with a high fee rate (6444 sats/kw) to adapt to current Bitcoin network conditions or their internal policy.\n\n• My Alby Hub node rejected it, citing excessive dust exposure risk for 6.645 million msat in pending transactions.\nUnable to reconcile this (e.g., if Monolithic couldn’t lower the fee rate or my node wouldn’t budge), \nMonolithic force-closed the channel to avoid being stuck with an unresponsive or risky peer.\n\n• This appears not to be about inactivity or my brief offline period being the sole cause—it’s about a mismatch in how my node (Alby Hub??) and Monolithic handled fee adjustments and risk tolerance with one another",
"sig": "fedafae8fde15c1e1ba32e52e7327466533538ecdff39feef3681df1d43960e55d91a759e8bff517731186d3a8e21bf3f253ab7fe85b6e14c6b4ef01bab071dd"
}