FLIP 351: Transaction Fee Update to Enable Inflation-Neutral Tokenomics

[vishalchangrani]

Tracked by Issue: #351
Comment Period: 19th Nov, 2025 to 3rd Dec, 2025

[bluesign]

This is great change, thank you for this work @vishalchangrani

[bjartek]

Good change! If anything i would increase the fees even more so that we send a signal we want to cover more of the rewards with fees earlier.

[bluesign]

Good change! If anything i would increase the fees even more so that we send a signal we want to cover more of the rewards with fees earlier.

yeah I was also thinking that, but with scheduled stuff it becomes expensive fast :) Like anything very simple scheduled with 500 gas , every hour, makes like 30 flow ~ 8 usd per month.

[joshuahannan]

I support increasing fees across the board too. I don't think we should worry too much about scheduled transactions though. If we think those fees are too high, we can always propose lowering the multipliers, but I have a feeling that users will be able to work around that. More important for base fees to be higher across the board

[bluesign]

To be clear I support this change too, just saying increasing more ( like 10x more ) can have negative effect. Inflation neutral is a bit dream to be honest, but at least this will cut evm bots.

[vishalchangrani]

Good change! If anything i would increase the fees even more so that we send a signal we want to cover more of the rewards with fees earlier.

yeah I was also thinking that, but with scheduled stuff it becomes expensive fast :) Like anything very simple scheduled with 500 gas , every hour, makes like 30 flow ~ 8 usd per month.

Thanks @bluesign for your comments.
500 gas (compute units) would be a lot given that the compute units have dropped significantly after FLIP 346 - see example.

[bluesign]

Once again I am ok with this change. My comment is only for increasing this. ( like 10x or something)

I think 500 compute is not that much to be honest. Like usual scenario will be something like this:

• 50-100 compute scheduledcallback overhead
• some computation I will do
• 50 - 100 compute to reschedule myself
• 50 - 100 compute buffer for unpredictability of metering :)

So I have like 300-400 compute. Let's say I do some bridge interaction + some swap etc, I think it barely fits.

Some example: ( not the best one but anyway )

https://www.flowscan.io/tx/cf1e291e4905381678f8f0ab49a5ae9222763be407af51a4415da4f81a1f231a?tab=script

[janezpodhostnik]

Nice!

[vishalchangrani]

Deploying this change to Testnet today.
See announcement: https://forum.flow.com/t/upcoming-testnet-update-transaction-fee-changes-going-live-on-monday-dec-1/8405

[vishalchangrani]

The transaction fee increase is now live on testnet.

[vishalchangrani]

Marking this FLIP as Accepted but feel free to leave comments here.
The change will be rolled out to mainnet in the coming days.
Thank you reviewing it.