The problem WhistleDAO solves

Whistle DAO empowers you to:

Anonymity is Your Shield: Report incidents anonymously, without fear of your identity being revealed. This eliminates the risk of retaliation and allows you to speak freely.
Transparency Builds Trust: Witness an incident and unsure if it's being addressed? Whistle DAO promotes openness by documenting and tracking reported issues, ensuring accountability throughout the process.
Report from Anywhere, Anytime: Limited access to reporting channels is a thing of the past. With Whistle DAO, all you need is an internet connection to file a report, empowering individuals from any location to be heard.
Cutting Through the Noise: Unfounded reports can dilute the truth. Whistle DAO utilizes innovative Zero Knowledge methods like anon-aadhar verification to ensure the authenticity of reports, giving weight to your voice.
Simplicity is Key: Complex reporting procedures can be a nightmare. Whistle DAO offers a user-friendly platform that makes reporting incidents as easy as possible, encouraging more voices to come forward.
Whistle DAO is more than just a reporting tool; it's a platform that fosters a culture of safety and accountability. We believe that everyone deserves a voice, and Whistle DAO empowers you to use it.

Challenges we ran into

Challenges Encountered:

1. Integration of Frameworks: Achieving seamless communication between diverse frameworks presented a significant obstacle. Designing data exchange formats, communication protocols, and workflows demanded meticulous planning to prevent bottlenecks and data inconsistencies.

2. Managing Framework Dependencies: Negotiating the intricate network of framework dependencies posed challenges. Ensuring compatibility among different framework versions required extra attention to avert conflicts and unexpected errors.

3. Limited Documentation and Community Support: Sparse documentation and a smaller community around specific frameworks complicated issue troubleshooting. The scarcity of resources for finding solutions and debugging problems heightened the difficulty compared to widely-used frameworks.

4. Optimizing Framework Utilization: Determining the optimal use of each framework's features within the application was not always straightforward. Understanding the intricacies of each framework demanded time investment to integrate them effectively as features rather than mere external libraries.

5. ANON- Integration Hurdles : Integrating ANON proved to be a major challenge, exacerbated by the discovery that the provided SDK was deprecated. Overcoming this obstacle required alternative approaches and additional development effort.