mev-share

Users choose what transaction data to hide and what to reveal
searchers bid to execute in an OFA system for the right to execute against user’s private transaction
Selectively revealed transaction data helps searchers optimise their bids
Matchmaker inserts user pvt transactions into searcher’s partially created bundles and simulates them, looking for matches. Matched bundles are sent to block builders with a validity condition that MEV payments are made to the user
mev- share does not enshrine any builder
MEV-Share introduces privacy preferences, hints, private transaction insertion, and validity conditions.
Initially validity conditions are enforced only by social convention, trusting that builders will respect them and pay MEV to users. In practice this limits matchmakers to sending bundles to only trusted builders.
Matchmaker can be DDOS attacked by the searchers. Mitigation - reputation (as the Flashbots Builder uses today), requiring payment from searchers per bundle, or requiring searchers to post bonds that are slashable if they DDOS the matchmaker.

References