The problem ChainWhiZ solves

There are many freelancers and companies who can help you build your smart contract. But, wouldn't it be better, if you get a solution approved by a community of experts. Think no more, because we came up with a project just to solve the same issue.

The three pain participants in our platforms are Publisher, Voter, and Solver. As a user, one has to deposit tokens from Ropsten to Matic network to get the roles they desire. To get each role, each of them has to deposit a certain amount of tokens so as to get their respective role. A publisher will publish the problem statement for which he wants a solution with a certain amount of tokens as a reward. The problem statement is being stored in IPFS and the respective IPFS hash is stored in the Blockchain. The solvers will solve the problem on the EthFiddle platform and put their solution link into our ChainWhiZ platform along with the Readme file whose IPFS hash will be stored on our blockchain. The voters will be responsible for going through the solution, testing them using the EthFiddle link of specific solutions, and then voting for the ones they see as a perfect one. The publisher will have a profile page where he/she can view the total number of solutions to a specific problem statement posted on the ChainWhiZ platform with the corresponding accuracy of each solution voted and tested by experts. In this manner, the solution with the highest votes will be rewarded after a predefined deadline. The publisher will not only find a solution but a solution that is tested and approved by the community of experts. This ensures quality and efficient solutions.

The whole platform functions in a decentralized manner. In that way, no one can forcefully promote their solution. The identity of voters is not known so no solver can bribe them or corrupt them in any way. The admins are the controlling body that can remove any participant who tries to do the malicious activity.

Challenges we ran into

1. At first, we were having limited access to the number of test tokens in Matic. We overcame this by compromising on the number of tokens needed.

2. Then, we were getting unwanted results while switching networks from Ropsten to Matic and vice versa. We overcame this issue by making a separate page where people can switch networks to get their roles.

3. We tried to integrate Metamask with our nodejs backend for testing. But we faced some problem due to recent upgradation in Metamask. We solved that using a package called node metamask