The problem WhistleBlower solves

In countries like China, North Korea, Cuba, and countless others where to and fro flow of news is highly restricted. News and media constitute the fourth pillar of any democracy. People, both inside and outside the regime, have a diluted image of the governing bodies. It is the media that is deemed responsible for exposing the true face of these bodies - be it good or bad. If the freedom of media is compromised, democracy is just another word in the dictionary. In these recent times, this freedom of speech, expression, and press have been threatened by a lot of centralized bodies ranging from terrorist groups, media agencies, departments of the government - reporters are getting attacked each and every day at some or other corner of the world, people are being fed with fake news circulating through these social media websites on a daily basis. There should be an open platform to get true and unbiased opinions from people without putting their fundamental rights at risk. This is where our application, WhistleBlower, comes into play.

WhistleBlower is a web3 application that maintains the user's anonymity while they deliver the news without any fear or favor. The application allows one to add relevant documents (proofs) to support the information. Also, they can check the news and their respective documents reported by others. The application reports all these transactions into the blockchain and documents (proofs) to the IPFS network without revealing the user's identity and ensuring that it can't be taken down for whatever reason by anyone. Any spam, fake or unnecessary information posted on the application gets filtered by the relevant users themselves with the help of the like/dislike feature along with other details in the comments. Users can gain traction for their posts by using the share button and gain some tokens generated in exchange for the same.

Challenges we ran into

1. Moving between local and test blockchain networks
2. Checking file formats from the IPFS file hash
3. Connecting the tokens with post logic