ethrd

Last smol post on unpacking the current blob market issue as far as what I can see. I can't claim I have a good solution to any of this, but I'm excited to see how it unfolds in the coming months.

1.) Blob tip is not an independent field. It's shared with execution tip. The total tip paid is execution tip multiplied by gas usage. Given two txs, one with higher execution usages than the other, the tip will be higher but that doesn't tell anything about how many blobs there are. Example: {blob_count: 6, tip: 2, gas_used: 5} beats out {blob_count: 1, tip: 9, gas_used: 1} even though it's paying a higher total tip in the end. It's not clear to me who simulates, I was told some builders already simulate, but the cleanest solution is to give the blob tip its own field.

What do you think about just making the existing tip fixed (and hence predictable)?

What do you think about just making the existing tip fixed (and hence predictable)?
https://notes.ethereum.org/@ansgar/execution-independent-priority-fee