The problem YieldSync solves

The idea for this app is actually derived from chainlink itself, in trying to unite all chains , why not we have a single point of entry for all yields across chain, be it eth staking, liquidity pools or lending protocols, it will be easy to analyse and quite user friendly to bring all the ways to earn in all chains into one app , just like how centralized exchanges bring all token into one protocol.

It makes it easy for users to find , analyse and communicate with yields across chain, it is not secure yet but this is a ground breaking idea (i think so).

Miscellaneous
I also made another project while at it, Decentralized Farmer Insurance protocol powered by chainlink functions to fecth off chain data and price feeds and automations. pls check it out

Challenges I ran into

Link token cross chain transfer.
I was using the link token for cross chain transfer between eth sepolia and base sepolia and was getting errors, i knew not all tokens were cross chain enabled but i just had the impression that link which is native to chainlink would be enabled across most chains so i was stuck for some time before i decided to use usdc. and it worked

Technical Issues

1. Handling multiple tokens in strategy contracts comes with lots of issues, because when sending token address as data across chain, tokens in deifferent chains dont have same address. this brings complication , 2 workarounds i saw.
   i. manually placing the destination chain address in the input which will be stressful especially when theres lots of tokens
   ii. better approach was to have each strategy be direct and specific. like a strategy for just usdc/eth pool, usdc vault only, so when sending data you know that this is what i am getting and this also helps in data validation also
   iii. tracking ,managing and aggregating user yields in frontend, still figuring it out, but i rather had a to put the strategies in mock json file and loop through them to render their ui and form for interaction, otherwise it will have to be done manually, since strategy functions will have different signatures
   iv. Tracking cross chain transaction settlement in frontend