Wickycd
A verified social profile for web3 using zkproofs and a profiling layer for dApps to easily integrate and get necessary data from!
Project Description
The Wickycd project addresses several key problems in the digital and Web3 environments:
Identity Verification and Trust: In digital interactions, especially in decentralized networks like Web3, verifying a user's true identity is challenging. Wickycd solves this by creating verifiable profiles linked to a user’s existing wallets, providing a reliable way to authenticate identity.
Combating Fake Profiles and Identity Misuse: The internet, especially social platforms, is rife with fake profiles and identity theft. By offering optional KYC elements and social profile links verified onchain, Wickycd ensures that the digital identity is authentic, reducing the risk of impersonation and fraud.
Ease of Information Sharing for Users: Users often need to prove certain aspects of their identity or qualifications (like professional skills, social media presence, etc.) on various platforms. Wickycd allows users to aggregate and share these details securely and conveniently.
Streamlining Data Access for dApps: dApps often require access to user information but fetching this data securely and with user consent can be complex. Wickycd’s API provides a standardized, secure way for dApps to access the needed information, with the user’s control over what is shared.
Privacy and Security in Data Sharing: In current Web2 platforms, users often have to compromise on privacy when sharing personal information. Wickycd’s use of zkproofs ensures that data sharing is secure and private, with users having control over who accesses their data.
Integration and Flexibility: By allowing users to connect any of their existing wallets, Wickycd offers flexibility and ease of integration, enhancing user experience in the Web3 space.
Links
How it's Made
While integrating Waku for inapp chatting requirements, we ran into a bug where because we let it refresh, it was taking too long, so we set it to a 5-10 second interval to make it work.
Push Protocol we wanted to integrate for notification requirements for verification of user profiles, chats and etc, however we were not able to find the channel we created for notifications, it was not being found while integrating Push, could not solve it.
