AVBpodcast on Nostr: So, I went over the Bitcoin Knots default settings in their spam-filtering. And I ...

So, I went over the Bitcoin Knots default settings in their spam-filtering.

And I noticed the settings for minimal transaction fees.

I don't think this is very positive to just enable as-is.
But that's just my opinion.

Maybe someone should go over all these settings one-by-one and see how this impacts some legit functions. (yes, it prevents spam, but let's look at what we're doing here).
(also it sets it by default to pruning... but that's a separate issue... )

example:
bytespersigop=20 (Equivalent bytes per sigop in transactions for relay and mining)

bytespersigopstrict=20 (Minimum bytes per sigop in transactions we relay and mine)


Increased Costs for Sigop-Heavy Small Transactions:

Small transactions with many sigops (e.g., complex multisig or script-heavy transactions) will have their effective size inflated by the 20 vbytes per sigop rule. For example, a transaction with 5 sigops is treated as having an additional 100 vbytes (5 × 20), significantly increasing its fee requirement to achieve a competitive fee rate.

This makes such transactions more expensive to confirm, potentially discouraging their use unless the sender is willing to pay higher fees.