Application

  1. Has the relay operator posted in the Call for Relays thread with the information required for application? Yes, https://research.lido.fi/t/lido-on-ethereum-call-for-relay-providers/2844/34

    1. Is the relay operator publicly available? *Yes, more info: https://titanbuilder.substack.com/p/titan-relay-launch-on-ethereum-mainnet*
    2. Is the relay publicly listed and maintained? If yes, please link to the dashboard/webpage. Yes: https://titanrelay.xyz/
    3. Is the relay open source? If yes, please link to the repository. Yes, https://github.com/gattaca-com/helix
    4. Is the relay code audited? What’s the most recent audited version of the code and have significant changes been made to the code base since? yes, https://github.com/gattaca-com/helix/blob/main/audits/spearbit-audit.pdf
    5. Are there any ethical or non-neutral considerations about the relay to disclose? This includes MEV strategies such as transaction reordering or censorship such as address filtering and sanctions/legal compliance. *Reviewer’s notes:

    1. Gattaca/Titan also operate a builder, thus this relay constitutes a vertically integrated builder+relay in one entity which offer the builder an edge over other builders if the relay isn’t operated as transparently and openly as possible. As a result, the RMC should take into account and monitor the relay (if it is successfully vetted) whether there’s any issues in this regard (e.g. certain builder winning bids here that don’t seem competitive).*

      2) Currently, the relay began as titan-only and has no progressed to whitelisted builders (and thus bids). The relay plans to accept permissionless block submissions in the next few weeks.

    1. How does the relay source from builders and searchers? (e.g. are they internal, external 3rd parties, publicly open, private, permissioned, permissionless)?

      Currently: Titan relay is permissionless for builders > At time of submission: Internal and third parties, currently permissioned.

    2. What is the relay operator’s policy for at-fault technical mishaps which result in missed proposals? there is no explicit policy

    3. Do we have all the necessary disclosures and contact information about the relay operator? Yes

Additional note: As of Aug 29th announcement, Titan will be taking over operation of Eden relay https://edennetwork.io/blog/eden-network-relay-transfer.

image.png

Revenue

  1. How is the relay funded and/or sustained? The relay seems to be funded predominantly by the block-building success of Titan Builder.

  2. What is the revenue/profit sharing model (if any) of the relay? Not explicitly, however the relay does seem to be getting private exclusive order flow, and their builder may be making additional gains from this contra other builders as a result (i.e. less total rewards being shared with proposers as % of block value).

    Untitled

  3. Is this model transparently disclosed and well understood? Yes.

Testing

  1. Does the relay operator have a testnet relay? Yes.

  2. How many days have node operators tested this relay? Hundreds! The relay was utilized during the tests for Simple DVT on Lido testnet for both SSV and Obol clusters as well as by curated operators. In general, some issues were noted during the first few weeks that the relay was set up on testnet (january 2024) but those issue have been fully resolved. https://blog.lido.fi/simpledvt-ssv-testnet-results/ https://blog.lido.fi/simpledvt-obol-testnet-results/

    1. Has the relay been tested for a minimum of two weeks? Yes, the relay has been tested for over 3 months and is running on mainnet with no serious issues noted.

  3. What was the success and failure rate of the relay’s proposed blocks? As per Metrika’s mainnet dashboard https://app.metrika.co/ethereum/dashboard/staking/mev-overview/all?tr=2w , failure rate seems acceptable

    Untitled

    Untitled

  4. Were there any incident or degraded performance reports from Lido Node Operators while testing the relay? (e.g. missed proposals due to missing/late payloads, validator registration errors, relay timeouts, etc.) Issues were noted due to bad bids and missed proposals in early testnet (Jan-Feb), but no issues have been noted since late March.

  5. Were observed issues and incidents during testing investigated and resolved sufficiently in a timely manner? Yes.

  6. Are there considerations and data to be observed and included from mainnet performance? Yes, see above.

  7. Has there been a report compiled to analyze the new relay with performance data on testnet and mainnet?

    No specific report was compiled for the relay due to the extensive usage over the Simple DVT testnet as well as the fact that the relay is already working on mainnet with acceptable performance, see above.

Additional questions: