Relay Spike

[0xean]

https://docs.relay.link/what-is-relay

TLDR:

gets us a bunch of new routes (for chains we dont support yet also) and derisks lifi a bit

Spec:

https://www.notion.so/shapeshift/Relay-Link-mini-9bc4118d6fb64916985d5f0208f6c00c

Desired outputs:

• Technical review
• high level breakdown into tickets for implementation
• confirm we can add affiliate fees (tim has this one for now)

[twblack88]

Oh i found the fee bit:

appFees: Third party fees added on top of the existing fees, this fee is added by app developers and accrues offchain to minimize gas costs. the app fee payee must manually claim them later.

[NeOMakinG]

I didn't find the need to do a fully detailed spike, here are my notes:

• No rate like Li.Fi
• Refunds are to the from address as from currency
• App fees are using the native currency of the chain, so the user needs enough native amount to pay app fees ⚠️
• We need to add the receiveAddress, as we are multichain
• Use the relay SDK to get quotes? I would say yes so it's fully typed (https://github.com/reservoirprotocol/relay-kit/blob/main/packages/sdk/src/types/api.ts)
• Maybe AdaptedWallet if we use the SDK but not required (https://github.com/reservoirprotocol/relay-kit/blob/main/packages/sdk/src/types/AdaptedWallet.ts), I think we don't need it because we have our own abstraction, it would be required if we wanted their SDK to execute the TX etc
• Multiple steps (so far I only seend approval for altcoins to ETH for example)
• Weird chainIds (solana is 792703809 on relay side), can be fetched using /chains on relay side but I would prefer to use a static map constant (https://docs.relay.link/resources/supported-chains)
• Quote stale after 30sec
• We can check trade status using https://api.relay.link/intents/status/v2 passing the requestId from the quote endpoint
• Supporting Bitcoin, Ethereum, Avalanche, Base, Arbitrum and Arbitrum Nova, Optimism, Gnosis, Polygon, Solana
  I- don't know why but there is a transaciton index post api endpoint (https://docs.relay.link/references/api/transactions-index), that's supposed to trigger some TX detection in their backend but I suppose we don't need

❓ One pending question to relay team: how do we manage fees, specially when multichain (fees are supposed to be using the native token, seems like we would need to claim the fees on each chain family we are operating, that would mean 3 TXs to claim fees are we are supporting 3 different chain families with relay)

• We might have weird behaviors because of fees, as they are supposed to use the native currency, if the user doesn't have enough of native to operate fees + gas fees, it would fail, but we need to handle those maths in our codebase (I think we do handle gas fees, but not affiliate fees included so far, this is a relay specific case I think).
• • To be implemented as specific case in validateTradeQuote

Tickets to be created:

• Add Relay feature flag + implement getTradeQuote (which would also be getTradeRate, so let's include this in the same ticket), disable flag in production, use relay SDK to get quote
• Implement EVM transaction handlers + checkTradeStatus
• Implement UTXO transaction handler (only btc)
• Implement Solana transaction handler
• Ask for fees addresses on different chains and confirm with DFC
• Add relay to develop and make it tested by the ops team
• Activate Relay in production

[0xApotheosis]

• Add ticket to spike on fee claiming flow for the DFC
• Spike to ensure we can send the native token + a value using Chain Adapters, which will be necessary for collecting fees in both native and ERC20 tokens in the same TX

[NeOMakinG]

All tickets are created, closing this one