From 8406df62d03278e2751d7c523ecc82bf8fe7b62b Mon Sep 17 00:00:00 2001 From: yi <67046731+yizhang0901@users.noreply.github.com> Date: Mon, 16 Feb 2026 16:50:05 -0500 Subject: [PATCH 1/3] Update README.md updating readme for builders to receive orderflow --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index c84d89e..29187a0 100644 --- a/README.md +++ b/README.md @@ -14,3 +14,17 @@ Builders can register to receive orderflow from MEV-share matchmakers by submitt In the PR description, Builders must attest that they agree to the Fair Market Principles outlined in `fair-market-principles.md`. Note that registering does not guarantee that a builder will receive orderflow from any or all matchmakers. Matchmakers or users may choose to limit the set of builders that they share orderflow with by default or in general. The purpose of this registry is to signal intent, compatibility, and agreement with the principles. Builders could be removed or flagged if the MEV-share community determines that they have failed to uphold these principles. + +## Receiving orderflow + +To receive multiplexed orderflow, a builder must: +* Build ≥2% of canonical Ethereum blocks over the trailing 60 days +* Provide a real-time communication channel for technical coordination +* Commit to the [Flashbots Fair Market Principles](https://github.com/flashbots/dowg/blob/main/fair-market-principles.md) + +Builders may be suspended if they: +* Fall below 2% block share over the trailing 30 days; or +* Violate the Fair Market Principles; or +* Experience documented technical instability materially affecting inclusion reliability. + +In rare cases where these thresholds would impact transaction inclusion for users, Flashbots may temporarily adjust the multiplexing criteria. Any adjustments will be documented and applied equally across all builders. From 42fecd192c9831a86eaee73f89cca34d0c32cc81 Mon Sep 17 00:00:00 2001 From: yi <67046731+yizhang0901@users.noreply.github.com> Date: Tue, 17 Feb 2026 14:05:18 -0500 Subject: [PATCH 2/3] Update README 2.md update readme for registration --- README.md | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index 29187a0..f2209d6 100644 --- a/README.md +++ b/README.md @@ -6,25 +6,27 @@ This repository is in progress and will host the work of the Decentralized Order ## Builders -Builders can register to receive orderflow from MEV-share matchmakers by submitting a PR to this repository. In the PR, they should add an entry to `registrations.json` with the following information: -* Their name as they would like it displayed. -* The RPC endpoint that matchakers should send bundles to. -* The API versions they support. Builders can find the complete set of bundle APIs [here](https://github.com/flashbots/mev-share/tree/main/specs/bundles) (version names are indicated by the file name). We recommend that builders upgrade to the latest version when new versions are released. For an example of how to integrate the new `mev_sendBundle` method (and in particular how to enforce validity conditions), you can reference the open-source [Flashbots MEV-Boost Block Builder](https://github.com/flashbots/builder/tree/mev-share). - -In the PR description, Builders must attest that they agree to the Fair Market Principles outlined in `fair-market-principles.md`. +### Eligibility for receiving orderflow -Note that registering does not guarantee that a builder will receive orderflow from any or all matchmakers. Matchmakers or users may choose to limit the set of builders that they share orderflow with by default or in general. The purpose of this registry is to signal intent, compatibility, and agreement with the principles. Builders could be removed or flagged if the MEV-share community determines that they have failed to uphold these principles. - -## Receiving orderflow - -To receive multiplexed orderflow, a builder must: +To be eligible to receive orderflow, a builder must: * Build ≥2% of canonical Ethereum blocks over the trailing 60 days * Provide a real-time communication channel for technical coordination -* Commit to the [Flashbots Fair Market Principles](https://github.com/flashbots/dowg/blob/main/fair-market-principles.md) - +* Commit to the Flashbots Fair Market Principles + Builders may be suspended if they: * Fall below 2% block share over the trailing 30 days; or * Violate the Fair Market Principles; or * Experience documented technical instability materially affecting inclusion reliability. - + In rare cases where these thresholds would impact transaction inclusion for users, Flashbots may temporarily adjust the multiplexing criteria. Any adjustments will be documented and applied equally across all builders. + +### Registration to receive orderflow + +Builders can register to receive orderflow by submitting a PR to this repository. In the PR, they should add an entry to `registrations.json` with the following information: +* Their name as they would like it displayed. +* The RPC endpoint that matchakers should send bundles to. +* The API versions they support. Builders can find the complete set of bundle APIs [here](https://github.com/flashbots/mev-share/tree/main/specs/bundles) (version names are indicated by the file name). We recommend that builders upgrade to the latest version when new versions are released. For an example of how to integrate the new `mev_sendBundle` method (and in particular how to enforce validity conditions), you can reference the open-source [Flashbots MEV-Boost Block Builder](https://github.com/flashbots/builder/tree/mev-share). + +In the PR description, Builders must attest that they agree to the Fair Market Principles outlined in `fair-market-principles.md`. + +Note that registering does not guarantee that a builder will receive orderflow from any or all matchmakers. Matchmakers or users may choose to limit the set of builders that they share orderflow with by default or in general. The purpose of this registry is to signal intent, compatibility, and agreement with the principles. Builders could be removed or flagged if the MEV-share community determines that they have failed to uphold these principles. From a6612f1d5e3355fc717fbf8289c9242306386e56 Mon Sep 17 00:00:00 2001 From: yi <67046731+yizhang0901@users.noreply.github.com> Date: Tue, 17 Feb 2026 14:07:19 -0500 Subject: [PATCH 3/3] Update README 2.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f2209d6..e8522fe 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ This repository is in progress and will host the work of the Decentralized Order ## Builders -### Eligibility for receiving orderflow +### Criteria for receiving orderflow To be eligible to receive orderflow, a builder must: * Build ≥2% of canonical Ethereum blocks over the trailing 60 days @@ -20,7 +20,7 @@ Builders may be suspended if they: In rare cases where these thresholds would impact transaction inclusion for users, Flashbots may temporarily adjust the multiplexing criteria. Any adjustments will be documented and applied equally across all builders. -### Registration to receive orderflow +### Registering to receive orderflow Builders can register to receive orderflow by submitting a PR to this repository. In the PR, they should add an entry to `registrations.json` with the following information: * Their name as they would like it displayed.