SafeBlow

SafeBlow

📣 While existing web2 whistleblowing platforms face limitations like centralized identity verification, SafeBlow offers a solution by enabling the verification of reports without storing individual identities, utilizing a proof-of-personhood solution through TLS Verification, and implementing a client hash identifier to separate identifying data from report content.

@G4nd4l7 

https://github.com/gabrielem/safeblow

https://www.youtube.com/watch?v=udUNtWdRP58

https://safeblow.vercel.app/

💡

Why is whistleblowing a hot topic in Italy? Well, with a history of corruption that could fill a pasta pot, Italy's got its share of organized crime lurking around public institutions. Enter Law No. 179/2017 - providing some protection for whistleblowers, but due to implementation inconsistencies and overall unawareness it is yet to be improved. 

Along with that, the cultural norms prioritizing loyalty often make it tough for folks to blow the whistle. However, with Italy under the EU's watchful eye and some jaw-dropping whistleblowing stories hitting the headlines, people are starting to wake up and realize just how important it is to speak out.

And let’s not forget, with so much of the economy in the public sector, whistleblowers are the unsung heroes exposing the not-so-fun side of government antics. So, here’s to our brave whistleblowers—fighting the good fight for transparency and accountability, one pasta scandal at a time!

There are multiple web2 whistleblowing platforms but there are some limitations of the product, like using centralized identity verification and centralized management of identifiers. 

SafeBlow is a solution to implement web3 tech to tackle those limitations. SafeBlow enables the system to verify with reasonable certainty that a specific report has been made by a certain person without needing to store the individual’s identity or documents, in non-anonymous reports. 

(1) By implementing proof-of-personhood solution using TLS Verification by ZKPass that has the user verify their identity through a KYC account that they already own (bank account or an exchange account). For anonymous applications it filers the spam. 

(2) Currently, a random ID (in the form of a numeric/alphanumeric code) is associated with each report and sent to the reporter. By submitting that ID a reporter can retrieve his or her report at a later date. It’s very important to separate the reporter's identifying data from the report's content. SafeBlow implements a client hash identifier with segregation between client and server. The hash can be generated also on the server without the need of communication between server and client. 

SafeBlow has a simple interface, with no noise. You don’t need to log in. 

This will ensure the process of implementing SafeBlow into web2 platforms smoothly.

Bounties:

Building a project that can fit on top of OpenBlow of Laser Romae.

Utilizing a proof-of-personhood through ZKPass for TSL Verification.