Titan Relay

Titan operates an MEV-Boost compatible relay which can be found at the locations below:

Network
Relay URL

Holesky

https://0xaa58208899c6105603b74396734a6263cc7d947f444f396a90f7b7d3e65d102aec7e5e5291b27e08d02c50a050825c2f@holesky.titanrelay.xyz

Mainnet Global (non-filtering)

https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72dece09bb313f2a1855595ab677d@global.titanrelay.xyz

Mainnet Regional (filtering)

https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72dece09bb313f2a1855595ab677d@regional.titanrelay.xyz

These URLs use AWS geo-routing to find the best relay cluster to send to. We have found this can sometimes route requests to the wrong region, so we have also added specific geo-location URLs. You can drop these directly in place of regional.titanrelay.xyz or global.titanrelay.xyz in the above URLs.

Global URLs:

  • eu-global.titanrelay.xyz

  • us-global.titanrelay.xyz

  • tk-global.titanrelay.xyz

  • sg-global.titanrelay.xyz

Reigonal URLs:

  • eu-regional.titanrelay.xyz

  • us-regional.titanrelay.xyz

  • tk-regional.titanrelay.xyz

  • sg-regional.titanrelay.xyz

MEV-Boost Client Configuration

In order to include the Titan relay in your MEV boost configuration, simply append it to the list of relays in the command line arguments.

./mev-boost -mainnet -relay-check -relays <relay1>,<relay2>

Simply replace the placeholders <relay1> and <relay2> with the appropriate connection URL.

NextBuilders

Last updated