Currently:

• The block fullness is just merely a check that the total size does not exceed 4mb
• Fees are paid based on byte_fee and base_fee with fee = base_fee + byte_fee * tx_bytes.

What we want:

• Allow each transaction (as opposed to one global config) to determine its own notion of weight, consisting of the same base + byte weight.
• Measure the fullness based on weight.

Next up:

• Use this weight and multiply it by fee multiplier to get the fee. Issue here: Block fullness targeting with fee multiplier #2430
• Use it to also adjust the block fullness + include tip.