The problem Hushkey solves

At Hushkey, we take data security seriously. That's why we use a user's private key to encrypt and decrypt their data, which is then stored on IPFS, making it truly decentralized. This ensures that your sensitive information is always secure and under your control.

In the duration of hackathon we started storing the CID from IPFS in a smart contract deployed on FVM. This allowed us to keep all things native to the Filecoin Network, which is important for our project since IPFS is core to our platform. We deployed a smart contract to the Hyperspace testnet on FVM to accomplish this. However, we encountered a challenge with Biconomy meta transaction support for transactions happening on FEVM. To address this, we had to modify the smart contract on FVM so that the entire smart contract became Ownable, and we were doing transactions on behalf of the user by explicitly sending their address to the setCid and readCid functions.

In addition, we also implemented Push Notifications to notify users upon successful archival of their data. This ensures that users are always informed about the status of their data and have peace of mind knowing that their information is secure.
Both FVM and Push Intergation were integrated and completed during hackathon.

Challenges we ran into

We began our hackathon by targeting 3 integrations: Push, FVM, and Arcana. Our aim was to showcase the use case of a mobile-friendly decentralized app, so we built an android application.

Unfortunately, Arcana's mobile SDK was still in development, so we had to drop the idea of integrating a social login abstracted wallet.

To keep everything native to the Filecoin network, we deployed a smart contract (0xCf7659589DA9434568B87B508114664fa4F12aAa) to Hyperspace testnet on FVM, with IPFS as the core of our project. However, we faced a challenge with Biconomy meta transaction support for transactions happening on FEVM. To work around this, we modified the smart contract on FVM to map msg.sender with cid, and set the entire smart contract as Ownable, enabling us to do transactions on behalf of the user by explicitly sending their address to the setCid and readCid functions.

We also faced a challenge with sending Push notifications, as Push currently does not support transactions on FEVM. To address this, we connected Push channel with Polygon testnet and redeployed our original smart contract on Polygon (0xeD166d0b9D54dE20972c590B8FefaAB812b21e55). Now we are storing CID in two contracts, one deployed on Hyperspace FVM and another on Mumbai Polygon.