The problem PrivacyForge solves

Have you ever found yourself wondering about the usage and access history of your documents? Traditionally, we've had to place our trust in banks, providing them with attested copies of our important documents and crossing our fingers, hoping that they are handled securely and responsibly.

However, we strongly believe that it's time for a change. With PrivacyForge, you gain the power to take control of your documents. No longer do you need to hope for the best; you can actively manage who has access to your documents and keep a close eye on how frequently they are viewed.

Think of PrivacyForge as a revolutionary tool, akin to a transactional app, but with a focus on something even more precious than money – your vital documents. With PrivacyForge, you have the freedom to tailor every aspect of each document transaction to your exact specifications. It puts you in the driver's seat, providing a new level of control and security for your most valuable information.

Challenges we ran into

The most difficult challenge to solve was to stop the use of screenshots. This can be solved by pushing users to use only PrivacyForge to make transactions. Now you will say that they could create a fake user and upload the screenshot of that document, but this is where our ML model comes in. It will run a deep-learning algorithm on each node and check for duplicates.
The other big problem was push protocol's package was not compatible with the latest versions of NPM and react so we had to change the code on the module ourselves hence we could only deploy it on the localhost.