MCPcopy Create free account
hub / github.com/ElementsProject/lightning / accepted_commitment_feerate_min

Function accepted_commitment_feerate_min

openingd/dualopend.c:444–451  ·  view source on GitHub ↗

Ignoring the fee limits drops the policy bounds, but never the sanity * ceiling: a feerate above that means a broken fee source, and whatever we * accept here is what we go on to store. * * For anchor channels the commitment only has to relay: its fee gets topped * up by the anchor spend when we actually need it onchain, so the relay floor * is the real bound there. Holding the opener to ou

Source from the content-addressed store, hash-verified

442 * refuse the very feerate we would propose ourselves, since lightningd also
443 * uses the floor for anchors (see update_feerates()). */
444static u32 accepted_commitment_feerate_min(const struct state *state)
445{
446 if (state->ignore_fee_limits)
447 return 1;
448 if (channel_type_has_anchors(state->channel_type))
449 return FEERATE_FLOOR;
450 return state->min_feerate;
451}
452
453static u32 accepted_feerate_max(const struct state *state)
454{

Callers 1

accepter_startFunction · 0.85

Calls 1

channel_type_has_anchorsFunction · 0.85

Tested by

no test coverage detected