UNIFI

Screenshots

Problem Statement

The problem of managing multiple tokens on different chain is ever evolving and has a lot of UX issues in web3 . UNIFI believes in solving problems at single clicks , no need to learn how to bridge assets , no need to sign multiple Taxn’s, no need to do all the efforts to decide the particular channels even the user doesn't even need to know which chain he/she is dealing with. UniFi enables crosschain payments by chain abstraction in a single click by utilizing account abstraction.

Solution

ChallengesInfrastructure challengesWhile using chainlink functions we got to know that the maximum runtime of the functions are 9 secs which restricted us to utilize the chainlink functions as our scripts needed 5-8minsIn CCIP while doing cross chain messaging we were initiating cross chain transactions, however, CCIP only returns a message ID through which we cant track the status of the destination transactions in smart contract which restricted us to do the smart transaction ina single click.Safe Auth KitWe faced significant challenges with Safe Account Abstraction kit, particulary the Auth kit of AA kit. Due to version difference in the dependencies of SDK, we were not able to provide custom web3 auth provider in safe account abstraction kit restricting us to give a graceful user experience.SolutionTo solve the infrastructure issues we made a little changes in our architecture and we made the verification of the transactions off chain rather than doing on chain.We couldn't find a solution for safe and hence, we had to restrict on our user experience.