The problem CrossFi solves

CrossFi creates a smoother DeFi experience than ever before. With the growing number of chains, depositing into a protocol on a specific chain has become increasingly complex. Users face the hassle of obtaining native tokens, on each chain just to cover gas fees—a cumbersome task. CrossFi removes these obstacles, enabling seamless deposits into any protocol without concerns any overhead. It brings true chain abstraction to the forefront.

It achieves seamless cross-chain functionality through integrations with Squid and ODOS. Squid, a cross-chain swap solution built on top of Axelar, allowing users to move assets from one chain to another with ease. Beyond simple token transfers, Squid supports advancedcross-chain contract calls, making it possible to interact with protocols on the destination chain directly.

Covalent is used to fetch the and show the positions that users have created across chains so they can modify, update or close their position directly from our interface.

Once Squid bridges the tokens to the target chain, its multicall contract initiates a call to the ODOS contract. ODOS, a smart order routing API, provides optimized quotes for the transaction, ensuring users receive the best possible execution on their swaps. By leveraging both Squid’s cross-chain capabilities and ODOS’s efficient order routing, CrossFi delivers a frictionless, chain-agnostic experience.

The problem it solves -

Complex Cross-Chain Interactions:
Users must manually bridge assets and navigate different wallets to access DeFi protocols across various chains. This multi-step process is time-consuming and can be intimidating.

Missed Opportunities Across Chains:
Different chains offer unique DeFi opportunities, but users often miss out due to the complexity of moving funds between chains.

High Costs and Security Risks:
Cross-chain transactions involve multiple transactions, often resulting in high fees and exposing users to potential security risks with bridges.

Challenges I ran into

Making cross chain contract calls is a cumbersome process as it requires the amount that user will be receiving on destination chain and we can't be sure of what exact amount user will get on destination chain. So we can generate a quote for that amount using odos. Eventually I figured it out and decided to rely on the minimum amount user will receive and sending the rest of the amount back to the user.

Squid also has some problem in their post hook which is that we can not execute a transaction prior to bridging it due to which we have to first swap the protocol's market token into their underlying token and then execute it and then bridge that token which is fixable after the hackathon via squid support.