status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

link to document of available external builder relays (#4157)

This commit is contained in:
tersec 2022-09-26 19:11:34 +00:00 committed by GitHub
parent d76df065a1
commit 6c18e82506
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/the_nimbus_book/src/external-block-builder.md
View File

@ -3,6 +3,7 @@
[Maximal extractable value](https://ethereum.org/en/developers/docs/mev/) involves consensus clients contacting an external block builder which might maximize profit or some other defined metric in ways hindered for a purely local consensus and execution client setup. This external builder network uses the [builder API](https://ethereum.github.io/builder-specs/) which consensus clients use to access external block builder bundles found by searchers. In exchange, such searchers and builders might choose to retain some of the profit gained from such bundles. A builder API relay provides access to multiple searchers via a single URL. [Maximal extractable value](https://ethereum.org/en/developers/docs/mev/) involves consensus clients contacting an external block builder which might maximize profit or some other defined metric in ways hindered for a purely local consensus and execution client setup. This external builder network uses the [builder API](https://ethereum.github.io/builder-specs/) which consensus clients use to access external block builder bundles found by searchers. In exchange, such searchers and builders might choose to retain some of the profit gained from such bundles. A builder API relay provides access to multiple searchers via a single URL.
Nimbus supports this API to access these external block builders. If one is configured, the block production flow becomes modified: Nimbus supports this API to access these external block builders. If one is configured, the block production flow becomes modified:
1. attempt to use the specified external block builder relay or builder to create an execution payload 1. attempt to use the specified external block builder relay or builder to create an execution payload
2. if the external block builder builder or relay doesn't function, and Nimbus has not signed a blinded beacon block, then fall back to existing local execution client to produce a block 2. if the external block builder builder or relay doesn't function, and Nimbus has not signed a blinded beacon block, then fall back to existing local execution client to produce a block
@ -22,3 +23,7 @@ There exists a failure mode, intrinsic to the builder API, wherein the consensus
```sh ```sh
./run-prater-beacon-node.sh --payload-builder=true --payload-builder-url=https://${HOST}:${PORT}/ ./run-prater-beacon-node.sh --payload-builder=true --payload-builder-url=https://${HOST}:${PORT}/
``` ```
## Useful resources
- [MEV relay list](https://github.com/remyroy/ethstaker/blob/main/MEV-relay-list.md)