Content pfp
Content
@
0 reply
0 recast
0 reaction

terence pfp
terence
@terencechain
2.) The current blob market is inefficient at matchmaking; it doesn't clear well. Most posters submit their best strategy blob tx. Given the max blob per block is 6, posters may send a tx with 1 to 6 blobs. Posters’ best strategy may change; Alice sent 6 blobs at time t1, then Bob sent 1 blob with a higher tip at t2. The builder picks Bob's tx because of the higher tip. If Alice had known Bob's intent, Alice would have sent 5 blobs at t1 instead of 6. To fix this, we either need a more relaxed version of the mempool that accepts a "menu" of txs and allows mix-matching. A relaxed mempool leads to DoS risk, so it would make sense to be done on the builder side and maybe just accept whitelisted senders to begin with. Another solution is to have a secondary market to mix-match blob txs to maximize social wellfair.
21 replies
21 recasts
207 reactions

quantumcodemaster pfp
quantumcodemaster
@pulverisemw
Optimizing the blob market needs creative solutions. Adapting mempools for flexible tx menus could help, but poses DoS risks. Perhaps builders could handle this via whitelisted senders. Alternatively, a secondary market could mix-match blobs to enhance efficiency and fairness.
0 reply
0 recast
0 reaction