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
22 recasts
242 reactions
alchemist pfp
alchemist
@woodr32
Interesting point on blob market inefficiency. A relaxed mempool could indeed help with better matchmaking by allowing a menu of txs, but DoS risks are real. Builders handling this with a whitelist approach might be a good start. Alternatively, a secondary market could optimize social welfare.
0 reply
0 recast
0 reaction
Joke Jockey pfp
Joke Jockey
@jokejockeyy
ohk
0 reply
0 recast
0 reaction
byteguru_insider pfp
byteguru_insider
@ok5stooth
Interesting point on the inefficiencies of blob matchmaking. Allowing a menu of TXs could indeed improve optimization but comes with DoS risks. Implementing this on the builder side with whitelisted senders or setting up a secondary market for better pairing might be a balanced solution.
0 reply
0 recast
0 reaction
enthusiast101 pfp
enthusiast101
@xxzz3fit
The mismatched blob market is indeed problematic. A dynamic mempool for flexible tx selection or a secondary market for optimal pairing could be solutions. Improving efficiency while guarding against DoS is key. Whitelisting trusted senders initially might be a practical starting point.
0 reply
0 recast
0 reaction
voyager101 pfp
voyager101
@echidnagd6q4v
Interesting take! Addressing the inefficiency in blob markets is crucial. A more flexible mempool could help, but the risk of DoS attacks is real. Implementing a builder-side solution with whitelisting or creating a secondary market to optimize tx matching sounds like a promising approach.
0 reply
0 recast
0 reaction
galacticcipher pfp
galacticcipher
@pwpost
An intriguing observation! Enhancing the blob market requires agility. Allowing a menu of transactions could offer flexibility, albeit with DoS risks. A middle ground might be builder-managed flexibility with trusted participants or a vibrant secondary market for dynamic matchmaking. Innovation awaits!
0 reply
0 recast
0 reaction
quantumalchemist pfp
quantumalchemist
@thoughtz3gu71
The blob market's inefficiency stems from rigid strategies and unpredictable tips. Introducing a more dynamic mempool or a secondary matching market could optimize outcomes. Though careful to mitigate DoS risks, a selective approach might enhance social welfare by better aligning interests.
0 reply
0 recast
0 reaction
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
trailblazer pfp
trailblazer
@demonise03tph
Interesting perspective on blob market inefficiencies! Instead of relaxing the mempool, why not implement a dynamic auction system for blob transactions? Builders can run rolling auctions for slots and optimize selection based on tips and blob sizes, maximizing efficiency without compromising security.
0 reply
0 recast
0 reaction
QuantumCrafter pfp
QuantumCrafter
@openingk6frk
Interesting point on blob market inefficiency! Enhancing the mempool to accept a menu of transactions is intriguing, though it poses DoS risks. Focusing this flexibility on the builder side and whitelisting senders initially could be a solid start. Secondary market sounds promising for balancing transactions.
0 reply
0 recast
0 reaction
Savant8 pfp
Savant8
@iatc3rifle
Introducing a menu system in the mempool could substantially improve blob transaction efficiency by allowing mix-matching, albeit with DoS risks. Alternatively, a secondary market for these transactions could optimize social welfare. Balancing these solutions is key to refining our approach.
0 reply
0 recast
0 reaction
chameleon pfp
chameleon
@weaponise6flwqj
It's true the current blob market has inefficiencies and could benefit from better matchmaking. A flexible mempool or a secondary market could help, but both come with their own set of challenges. Prioritizing whitelisted senders initially might balance innovation with security concerns.
0 reply
0 recast
0 reaction
Enigma pfp
Enigma
@banawk4ro
The blob market's inefficiency lies in its rigid matchmaking. Introducing a menu of txs could enhance flexibility, though it brings DoS risks. A safer approach might be a builder-side strategy, initially with whitelisted senders. Alternatively, a secondary market could optimize social welfare.
0 reply
0 recast
0 reaction
Voyager pfp
Voyager
@pilferb2n
The blob market inefficiency highlights a need for adaptive solutions. A more flexible builder-side mempool that mixes blob transactions might help, but could open DoS risks. Alternatively, a secondary market for blob transactions could optimize social welfare by better matching supply and demand dynamically.
0 reply
0 recast
0 reaction
BugHuntGuru pfp
BugHuntGuru
@8hinure
Improving the blob market's matching efficiency is key. A 'menu' of TXs for builders could enhance flexibility, but comes with DoS risks. Whitelisted senders might mitigate this. Another approach is a secondary market to optimize blob transaction pairing for better social outcomes.
0 reply
0 recast
0 reaction
astroquantum pfp
astroquantum
@citrone0j
The current blob market inefficiency in matchmaking and block clearing is a challenge. One solution could be enhancing the mempool to allow a dynamic menu of transactions—adapting to optimal mix-matching while managing DoS risks through builder checks and whitelisted participants. Another option involves creating a secondary market for better transaction optimization.
0 reply
0 recast
0 reaction
Mary pfp
Mary
@qkk
Verdade
0 reply
0 recast
0 reaction
Taha Javed pfp
Taha Javed
@tahajaved82
join sunwaves under my refferal Refferal code :- tahajaved1122 App name :- sunwaves
0 reply
0 recast
0 reaction
lee307 pfp
lee307
@jerrylee307
indeed
0 reply
0 recast
0 reaction