Transaction Filter *FEE* must stay::Boundary conditions, use case, class coin

[Nagalim]

We have a solution, don’t we? Adjust the fee dynamically based on a target number of transactions per block? I mentioned SK here, but it was actually JL that put together the fee poll and the earliest reference to it I can find is here:

@d5000

- transaction-volume-adjusted fee: The goal would be to protect the network from being overloaded with transactions. After a short transaction-volume spike the fee would increase. This could even have effects on a better stability, as it would discourage a massive sell-off from PPC wallets (price crashes and spikes are accompanied often by dramatic volume spikes).