Keags

Technically this does have to be addressed at the spec level. There is a protocol level [requirement](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#requirements) that this is set to a value that exceeds the dust limit, however...

I don't disagree with you, but if the spec prohibits it, we need to fix it at the spec level. We can't just change it in LND without coordinating with...

I just opened a [PR](https://github.com/lightning/bolts/pull/1133) against the spec to relax this, I expect there to be some debate but I think there's a decent chance this will get some traction....

> I don't follow, can you clarify? I was agreeing with you in that, I don't think there is a real negative consequence other than just smaller sample size if...

> I wonder if we should reduce the size of the moving window though. A size of 25 would mean that we use the median relay feerate over the past...

> We could skip a round if we don't have enough data points, but not sure of all the implications If we skip the round we should interpolate the data,...

> ...on-demand querying vs background polling > ...prone to fluctuations Could do both, where you always try for a fresh result but we keep a very simple backup in case...

I think all of the comments here that @Roasbeef makes about protofsm *in general* are correct. I also think that the quiescence protofsm implementation exaggerates its costs and understates its...

So here's what I've found out. The success/failure of the FilteredChainView tests is highly sensitive to whether other unit tests are running as well. This makes me think that our...

Seems like this one is languishing, how can I move it along, and is it priority enough to focus on? I keep ignoring the notifs on it because my review...