Skip to content

Update relay configuration #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
metachris merged 1 commit into from
May 8, 2025
Merged

Update relay configuration #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 2 additions & 5 deletions docs/orderflow-sharing-confidentiality.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,7 @@ During initial BuilderNet bootstrapping Flashbots will receive logs and have acc

### MEV-Boost Relays

Orderflow is only leaving the TDX instance when sent in blocks to MEV-Boost relays. Currently, these relays are used:
1. Flashbots
1. Agnostic
1. Ultrasound EU and US
Orderflow only leaves the TDX instance when sent in blocks to MEV-Boost relays. BuilderNet prioritizes relays that are fast, independent, and reliable (more [here](https://collective.flashbots.net/t/updated-mev-boost-relay-settings/4881)).

We are working to get rid of centralized relays through efforts such as [tee-boost](https://collective.flashbots.net/t/tee-boost/3741),
We are also working to get rid of centralized relays through efforts such as [tee-boost](https://collective.flashbots.net/t/tee-boost/3741),
to end-to-end encrypt the entire MEV supply chain.