based on the default fee settings. That being said, this doesn't seem like a bad idea at all...
So, a centralized source would declare a "default fee setting", and any time that source decided to change the default fee setting, there would be a new hard fork released that would change the blocksize calculation?
they are already in control as to what fee they require to include your TX, so make them vote and take the mean or avg or wtv of the votes, and use that as the "target fee" and have the block size calculation revolve around that.
Booya we solved it, call the devs!
lmao