What is the problem?

Currently, LI.fi predominantly routes through Hop for the commonly used USDC DAO path. A direct integration with Hop in our bridger could enhance the user experience and potentially offer better routes or rates.

Why are we solving it?

• User Experience: A direct integration can lead to a more streamlined user journey without additional hops.
• Strategic Positioning: By broadening our integration landscape, we position ourselves as a versatile platform in the crypto bridge space.
• Learning Opportunity: This project serves as a valuable learning experience for our product team to understand the nuances of new integrations.

How does it help Shapeshift users or DAO?

• Enhanced Routes: By directly integrating with Hop, users can potentially benefit from better or more varied routing options.
• Internal Usage: Dogfooding our product allows for better internal understanding and feedback.

How are we solving it?

1. Documentation Review: Go through the integration documentation of Hop to understand the technical requirements and potential challenges.
2. Engage with Hop: Initiate a conversation with the Hop team to gather insights about their upcoming v2 and its feature set.
3. Technical Feasibility: Conduct a technical spike to evaluate the feasibility and estimate the effort required for the integration.
4. Project Coordination: Incorporate the findings into the project coordination sheet and subsequently refine our approach based on the broader product roadmap.

What are the requirements (engineering, marketing, grants etc.)?

Product:

• Seamless user experience that aligns with our current offerings.
• User interface that clearly shows Hop as an available route.

Engineering:

• Familiarize with Hop's API and integration points.