Skip to main content

Quick Start

Eden Relay fully conforms to the most recent Builder API spec. As such, your validator client already supports using Eden Relay out of the box. All that is needed to use Eden Relay for block production are some simple command line flags in your chosen client (see below).

If you would like to connect to other relays in addition to Eden Relay, see our mev-boost implementation guide

Prysm​

To use Eden Relay as your source for block production with Prysm, you simply need to add the following flag to your beacon node client:

--http-mev-relay=https://0xb3ee7afcf27f1f1259ac1787876318c6584ee353097a50ed84f51a1f21a323b3736f271a895c7ce918c038e4265918be@relay.edennetwork.io

And the following to your validator client:

--enable-builder

Lighthouse​

To use Eden Relay as your source for block production with Lighthouse, you simply need to add the following flag to your beacon node client:

--builder=https://0xb3ee7afcf27f1f1259ac1787876318c6584ee353097a50ed84f51a1f21a323b3736f271a895c7ce918c038e4265918be@relay.edennetwork.io

And the following to your validator client:

--builder-proposals

See official Lighthouse Documentation for more details and advanced configuration options.

Teku​

To use Eden Relay as your source for block production with Teku where your beacon node and validator are run in the same process, you simply need to add the following flags to your client:

--validators-builder-registration-default-enabled=true 
--builder-endpoint=https://0xb3ee7afcf27f1f1259ac1787876318c6584ee353097a50ed84f51a1f21a323b3736f271a895c7ce918c038e4265918be@relay.edennetwork.io

If you are running a Teku setup where your beacon node and validator are run in different processes, your setup should look like the following:

Validator client:​

teku validator-client --validators-proposer-blinded-blocks-enabled=true --validators-proposer-config="/etc/teku/proposerConfig.json"

Proposer configuration:​

{
  "proposer_config": {
    "0xa057816155ad77931185101128655c0191bd0214c201ca48ed887f6c4c6adf334070efcd75140eada5ac83a92506dd7a": {
      "fee_recipient": "0x50155530FCE8a85ec7055A5F8b2bE214B3DaeFd3",
    }
  },
  "default_config": {
    "fee_recipient": "0x6e35733c5af9B61374A128e6F85f553aF09ff89A",
    "builder": {
      "enabled": true
    }
  }
}

Beacon node:​

teku --validators-proposer-default-fee-recipient="0x6e35733c5af9B61374A128e6F85f553aF09ff89A" --ee-endpoint="http://127.0.0.1:8551" --ee-jwt-secret-file="/etc/jwt-secret.hex" --builder-endpoint="https://0xb3ee7afcf27f1f1259ac1787876318c6584ee353097a50ed84f51a1f21a323b3736f271a895c7ce918c038e4265918be@relay.edennetwork.io"

See official Teku Documentation for more details and advanced configuration options.