NoTox Privacy

Demo

About

The problem it solves - NoTox makes professional networking safer and more private. Normally, people must share personal details like email or phone numbers immediately, which can lead to spam, harassment, or misuse of information. - NoTox solves this by allowing contact information to be revealed gradually based on trust levels. Users can connect step-by-step, starting with basic details and unlocking more information only when trust increases. - It also uses economic bonds, where users stake tokens to contact others. If someone harasses or misuses the connection, their bond is penalized and given to the victim, discouraging bad behavior. - Overall, NoTox helps people network safely, protect their privacy, and control who can access their personal contact

How it's made

Challenges we ran into While building Notox, we faced a few technical challenges during development. 1. Blockchain Integration Issues One major hurdle was connecting the MetaMask wallet with the frontend through the deployed smart contracts. While running the project using npm run dev, the terminal would often keep iterating, become slow, or sometimes get stuck. This made testing the wallet connection difficult. Another issue occurred because the Hardhat local blockchain node kept running in the background (typically on port 8545). Sometimes it conflicted with the frontend connection, which caused delays and errors until the process was restarted. We also temporarily lost Tailwind CSS styling on the website due to a small configuration issue. After debugging and fixing minor errors in the tailwind.config.js file, the styles started working again. 2. Database & API Integration While connecting the RESTful APIs between the frontend and the database, we faced several errors during API calls. After debugging the API routes and fixing the error handling and request structure, the connection started working correctly. How We Solved Them Most of these challenges were solved through debugging logs, checking configuration files, restarting background services like Hardhat, and correcting API request handling. Once these issues were resolved, the system integration worked smoothly.