Happy to announce version v0.11.0 of the mev-boost-relay 
v0.11.0 is live on all Flashbots relays - Mainnet, Sepolia and Goerli.
Major updates:
- block submission cancellation in #206
- Reject block submissions after getpayload in #188
- logging improvements on errors: #208 + #197
-
toolcommand for archiving execution-payloads and bulk-exporting data in #192
Minor changes:
- Add Postgres and database tests to CI by @franciscodiazydiaz in #199
- db sort by slot, db-test dsn env var in #200
- added ARCHITECTURE.md and S3 index page in #196
New contributors:
- @franciscodiazydiaz made their first contribution in Add Postgres and database tests to CI by franciscodiazydiaz · Pull Request #199 · flashbots/mev-boost-relay · GitHub
See also:
Block Submission Cancellations
Block builders can now overwrite previous submissions by sending a new payload (even with lower value).
Cancellations enable a wider range of strategies and experiments for block builders.
- Before this change, only a higher value payload could override a previous one.
- Now always the latest payload by a builder is used.
This change is now live, so make sure that your latest payload is the one you have used.
Steps in replacing a payload:
- Block builder sends a payload with the
submitBlockAPI call. - Relay receives the request and puts the payload into a validation queue.
- The payload is simulated and validated, on average within about 150ms (but can also take longer).
- After a successful validation, the payload is saved and a new top bid is selected among the latest payloads from all builders.
- Once the
submitBlockrequest is completed, the new payload is updated and used going forward.
See also:
- Relay API documentation:
submitBlock - Flashbots relays: Mainnet, Sepolia and Goerli
Happy building 