mirror of
https://github.com/autistic-symposium/mev-toolkit.git
synced 2025-07-12 01:09:41 -04:00
clean up chapter for mev-boost relays
This commit is contained in:
parent
27cfb209a1
commit
98c75869ee
1 changed files with 23 additions and 27 deletions
|
@ -1,11 +1,15 @@
|
|||
## pbs tx and/or mev-boost relays
|
||||
## mev-boost relays
|
||||
|
||||
<br>
|
||||
|
||||
### tl; dr
|
||||
|
||||
* relays are a bundle propagation service that receives bundles from searchers, simulate each txs, and forwards them to block producers.
|
||||
* validators can use relays to outsource their block production to entities specialized in extracting extra revenue.
|
||||
* on ethereum post-merge, relays act as trusted auctioneers between block proposers and block builders, validating blocks received by block builders and forwarding only valid headers to validators/proposers.
|
||||
* this ensures validators cannot steal the content of a block builder’s block, but can still commit to proposing this block by signing the respective block header.
|
||||
* when the proposer chooses to propose a block, the proposer requests `getHeader` to receive the highest bidding, eligible block header from the relay.
|
||||
* upon receiving the header associated with the winning bid, the proposer signs it and thereby commits to proposing this block built by the respective builder in slot `n`.
|
||||
* the signed block header is sent to the relay, along with a request to get the full block content from the relay (`getPayload`).
|
||||
* finally, the relay receives the signed block header (`signedAt`) and publishes the full block contents to the p2p network and proposer. when peers see the new block, validators assigned to the slot can attest to it.
|
||||
|
||||
<br>
|
||||
|
||||
|
@ -15,32 +19,24 @@
|
|||
|
||||
<br>
|
||||
|
||||
* **[the role of relays on reorgs, by dataalways (2024)](https://collective.flashbots.net/t/the-role-of-relays-in-reorgs/4247)**
|
||||
* **[mev relay list](https://github.com/eth-educators/ethstaker-guides/blob/main/MEV-relay-list.md)**
|
||||
* **[everything mev-boost](https://github.com/MEV-WAIFU-LABS/mev_toolkit/blob/main/flashbots/mev-boost/README.md)**
|
||||
* **[fb relay api](https://flashbots.notion.site/Relay-API-Spec-5fb0819366954962bc02e81cb33840f5)**
|
||||
* **[uptime monitor for relays](https://mev-relays.beaconstate.info/)**
|
||||
* **[mev relay ofac watch](https://www.mevwatch.info/)**
|
||||
* **[mev-boost relay data](https://mevboost.pics/)**
|
||||
* **[SushiGuardRouterV01 (with Manifold relay)](https://snapshot.org/#/sushigov.eth/proposal/bafkreigjjhjx2j2b526d3poeg23w2xan4rcgnzvcxinsssv7n37lu5p7s4)**
|
||||
* **[relayscan.io](https://www.relayscan.io/)**
|
||||
* **[malicious validator $20 from mev bots](https://eigenphi.substack.com/p/how-did-a-malicious-validator-steal)**
|
||||
* **[optimistic relays, by frontier.tech](https://frontier.tech/optimistic-relays-and-where-to-find-them)**
|
||||
* **[rated analytics on relays](https://www.rated.network/relays?network=mainnet)**
|
||||
* **[ethsaker relay list ](https://github.com/remyroy/ethstaker/blob/main/MEV-relay-list.md)**
|
||||
* **[beaconcha.in relay list and stats](https://beaconcha.in/relays)**
|
||||
* **[ultrasound money](https://relay.ultrasound.money/)**
|
||||
##### specs and docs
|
||||
|
||||
* **[mev relay list, by ethstaker](https://github.com/eth-educators/ethstaker-guides/blob/main/MEV-relay-list.md)**
|
||||
* **[mev relay list, by beaconcha.in](https://beaconcha.in/relays)**
|
||||
* **[mev relay ofac watch, by labrys](https://www.mevwatch.info/)**
|
||||
* **[mev-boost relay data, by t. wahrstätter](https://mevboost.pics/)**
|
||||
* **[mev-boost analytics, by relayscan.io](https://www.relayscan.io/)**
|
||||
* **[relay list, by ultrasound money](https://relay.ultrasound.money/)**
|
||||
|
||||
<br>
|
||||
|
||||
##### on building a relay
|
||||
##### research and code
|
||||
|
||||
* **[fork mev-boost relay](https://github.com/flashbots/mev-boost-relay)**
|
||||
* **[blocknative dreamboat](https://github.com/blocknative/dreamboat)**
|
||||
* **[join lido call for relays](https://research.lido.fi/t/lido-on-ethereum-call-for-relay-providers/2844/10)**
|
||||
* **[add label to beaconcha.in](https://beaconcha.in/relays)**
|
||||
* **[join fb boost relays tg](https://t.me/+E-HTvTDIsdI3MjM1)**
|
||||
* **[understanding mev-boost liveness risk, by hasu](https://writings.flashbots.net/writings/understanding-mev-boost-liveness-risks/)**
|
||||
* **[keeping relays honest](https://notes.ethereum.org/@yoav/BJeOQ8rI5)**
|
||||
* **[optimistic relay proposal](https://github.com/michaelneuder/optimistic-relay-documentation/blob/main/proposal.md)**
|
||||
* **[the role of relays on reorgs, by dataalways (2024)](https://collective.flashbots.net/t/the-role-of-relays-in-reorgs/4247)**
|
||||
* **[malicious validator $20 from mev bots, by eigenphi (2023)](https://eigenphi.substack.com/p/how-did-a-malicious-validator-steal)**
|
||||
* **[optimistic relay proposal, by michaelneuder (2023)](https://github.com/michaelneuder/optimistic-relay-documentation/blob/main/proposal.md)**
|
||||
* **[optimistic relays, by frontier.tech (2023)](https://frontier.tech/optimistic-relays-and-where-to-find-them)**
|
||||
* **[understanding mev-boost liveness risk, by hasu (2022)](https://writings.flashbots.net/writings/understanding-mev-boost-liveness-risks/)**
|
||||
* **[keeping relays honest, by yoav (2022)](https://notes.ethereum.org/@yoav/BJeOQ8rI5)**
|
||||
* **[mev-boost relay code, by flashbots](https://github.com/flashbots/mev-boost-relay)**
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue