The problem Panic Finance solves

The problem that we are solving is the difficulty in managing assets across different accounts and platforms in the decentralized finance (DeFi) space. When assets are on multiple platforms such as Uniswap, AAVE, and Superfluid, in case they are not actively monitored, they may create major losses.
Another problem that we aim to solve is that, if the private key to a wallet is compromised, it’s very difficult to move all the assets linked to this wallet quickly. This gives a potential attacker time to steal the assets.

Challenges we ran into

• We couldn't replicate the exact UI that we designed in time.
• Trying to build the backend service for the impermanent loss calculations and transactions took more time than we expected.
• We didn't have enough time to deploy the graph for the new contract, and since the events were not changed, we decided to use our previously deployed subgraph for our submission and create a demo for the same. The work on the backend, frontend and smart contract was done during the hackathon duration.
• We made significant changes to the Uniswap impermanent loss functionality, many things were added including the struct code modified. The only components that were retained were the function naming and events. The updated contract can be found here: https://github.com/shreyaspapi/panic-finance/blob/dev/contract/contracts/Panic.sol, but yes we think the graph code used for the demo was made 30 days before the hackathon.