Skip to content

Commit

Permalink
change mev-blocker emoji
Browse files Browse the repository at this point in the history
  • Loading branch information
andytudhope committed Apr 5, 2024
1 parent 4c78390 commit e4f23c5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/what-to-build.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Order Flow Auctions (OFAs) are responsible for taking in a transaction or intent
You can learn more about it by reading ["Illuminating Ethereum's Order Flow Landscape"](https://writings.flashbots.net/illuminate-the-order-flow).

- [MEV-Share](https://github.com/flashbots/mev-share) 🔄
- [MEV-Blocker](https://mevblocker.io/) 🛑
- [MEV-Blocker](https://mevblocker.io/) 🏖️
- MEV-Share+
- Dynamic refund: currently, users set their own refund percent, but depending on the state of the mempool and blockspace auction, they may want a lower or higher refund percent. A SUAPP could simulate a user's trade, query L1 state to get pool and token information, and use this to reason about what refund % to use on that user’s bundle.
- Dynamic hint: one of the open research questions around programmable privacy is where the privacy efficiency lies. An example of this, relevant to MEV-Share, is as follows: given a Uniswap L1 trade, how much information should be revealed? A $10 trade most likely can leak the entire trade details because it would be better to batch, but a very large trade has a risk of being probabilistically front-run; therefore, it should leak less information, or at least that is one possibility.
Expand Down

0 comments on commit e4f23c5

Please sign in to comment.