The problem Docs Universe solves

The store feature is a feature for uploading files to IPFS which is both a create operation on the application and write operation on the blockchain. The ownership feature can check the ownership of the uploaded file while allowing users to be able to retrieve files that have been saved, this is an implementation of read operations on the application and on the blockchain. The transfer feature allows users to be able to make ownership transfers of files that have been previously stored, this illustrates the implementation of update operation on the application and write operation on the blockchain.

In the Store feature, system flow starts from the Metamask check for account selection. Furthermore, the user can perform store operation by affixing the file to the form on the web interface, the application then converts the file into a buffer, user confirms the transaction and proceed with storing the file to IPFS. As output, the user will get information in the form of file hash and transaction hash.
Furthermore, the functionality of the Ownership feature is also started by checking the Metamask account. Followed by the choice of whether the user wants to check the ownership of a file or not. If so, the user can add the file that he wants to find out the owner of, but if the user does not want to check the ownership then the user can continue with the file retrieval feature. In the file retrieval feature, users only need to click the “Retrieve” button to retrieve the files they own.
As in the previous featurse flow, the Transfer feature also starts with a Metamask account check. Then users who wish to transfer ownership of their files can provide information on the destination account to be transferred, followed by confirming the transaction. The end result of this feature is the loss of the file entry that has been transferred and the receipt of the transfer transaction hash as proof that the ownership has been transferred.

Challenges I ran into

During the development of Docs Universe, we encountered several challenges:

Understanding the logic of smart contracts: Developing and understanding the intricacies of smart contracts required in-depth knowledge of Solidity and blockchain development.

Integrating the Filecoin Virtual Machine (FVM): Adapting the application to use the Filecoin Virtual Machine (FVM) instead of IPFS posed technical challenges. Understanding the FVM's functionalities and implementing them effectively required additional research and expertise.

Difficulties in file transfer: Ensuring seamless and secure file transfers between accounts within the DApp required addressing various technical challenges.

React development challenges: The team faced some difficulties while working with React, especially since some members came from a backend development background. Overcoming these challenges required learning and adapting to React's concepts and best practices.

Implementing WalletConnect for mobile-based wallets: Integrating WalletConnect into the frontend of the application for mobile-based wallets presented challenges due to compatibility and technical intricacies.

Accomplishments that we're proud of Despite the challenges we faced, we are proud of the following accomplishments:

Completing an intermediate level blockchain project: Developing Docs Universe using the Filecoin Virtual Machine (FVM) showcases our ability to work with advanced blockchain technologies and integrate them effectively.

Learning how to connect FVM, smart contracts, and web3: Gaining a deep understanding of the Filecoin Virtual Machine, smart contract development, and web3.js allowed us to create a robust and efficient digital document management platform.

Leveraging Ethereum blockchain and IPFS-API: Utilizing Ethereum blockchain technology and integrating it with the IPFS-API enabled us to provide secure and decentralized storage for digital documents.