The problem Open Journal solves

We have created a platform to empower innovators and creators who create some digital consumable contents be it some artistic content, poetry, blog and as important contents as research papers. So we initially started with the idea to create a platform for the researchers who face problems in getting reviewed their papers. As it is a time taking process and we have a monopoly of IEEE who governs and distributes it via its own platform.

So we created a decentralized platform where the researchers can put their work and the fellow researchers can download it and review it. So there will be a charge to download the paper and it can be set by the researcher. After downloading if the fellow researcher chooses to review it, correct it then he can be awarded some cryptos back as well.

The major concerns that can be addressed by this Dapp are:

1. This process is slow and we have to buy a license to download these papers.
2. Since it is in blockchain no data can be tampered and will help to check the case of plagiarism.
3. Ensuring trust and transparency between all the participants is a must since there is no central authority.

We also realized that it is just a single use case of our platform. We may have a Dapp where any creator can share his/her work and any consumer can micro fund it as a token of appreciation. Also, any creator can lease or sell his creations that includes memes, art, poetry.

Challenges we ran into

We wanted to use Torus to have an SSO with Google and third-party application which would enable any user to login in a single click. So we started integrating it and sat with the mentors and we realized that the features which we were expecting to use are yet to be released in the upcoming versions.

We have deployed it in the Matic Network. We were facing a lot of issues as we were unable to deploy it in the Matic Network. Again we sat and discussed it with the mentors from Matic Network. And finally, after a lot of trial and error, we were able to deploy it.

We also realized that there were some bugs in our contracts that were creating some problems in the deployment. We fixed it and tested every method exposed.