Beneath Protocol

Beneath Protocol addresses the insecurity of traditional email systems like Gmail and SMTP. By leveraging blockchain security, it offers a secure protocol, guarding against unauthorized access and impersonation. Beyond security, it enables cross-chain communication and ensures backward compatibility, facilitating seamless communication between web3 and web2 and vice versa. We do this by enabling cross-chain communication by bridging Web3 and Web2 mail systems across Ethereum, Polygon, Arbitrum, Base, and Zetachain.

At its core, Beneath Protocol employs the robust security features inherent in blockchain technology. By doing so, it establishes an impregnable barrier against potential threats, assuring users of the confidentiality and integrity of their communications. This innovative approach not only addresses current vulnerabilities but also anticipates and guards against emerging cyber threats, providing a comprehensive shield for sensitive information.

One of the distinctive features of Beneath Protocol is its commitment to ensuring backward compatibility. This means that it harmoniously integrates with existing email systems, creating a fluid and intuitive experience for users accustomed to traditional platforms. This interoperability is essential for a smooth transition into the future of decentralized communication, fostering user adoption and minimizing disruptions to established workflows.

Users leveraging Beneath Protocol not only experience heightened security but also gain control over their digital identities. The decentralized nature of blockchain technology empowers individuals by mitigating the risks associated with centralized data storage. As a result, users can communicate confidently, knowing that their personal information is shielded from unauthorized access and exploitation.

Links

• https://github.com/Beneath-Protocol/beneath-frontend
• https://github.com/Beneath-Protocol/beneath
• http://54.244.209.202:3000

Chainlink CCIP Integration Issues We initially planned to leverage Chainlink CCIP functionality for cross-chain communication. Despite investing significant effort and collaboration with the Chainlink Developer team, we encountered challenges. Developer issues on the Chainlink side and a lack of code updates in their docs posed hurdles. After exhaustive attempts and communication with the Chainlink team, we were advised to discontinue its use due to insurmountable challenges. This setback consumed a considerable portion of our time during the hackathon. Subsequently, we pivoted to developing our own decentralized protocol for achieving similar cross-chain communication goals, facilitating communication between different chains and bridging the gap between web3 and web2.

NextJS and Integration with Push Space and WebUI Kit While working with NextJS, we faced an unexpected roadblock during the integration of Push Space and WebUI Kit. An error arose, and upon consulting with the Push team, we discovered that resolving the issue within NextJS would be complex and impractical. Given that Push was a crucial feature in our project, we made the difficult decision to transition from NextJS to React. This necessitated re-implementing all functionalities within a tight time frame of less than 6 hours before the submission deadline. The team persevered through exhaustion to successfully migrate the project.

Learning Curve with New Technologies Our project involved a plethora of new technologies, including Zetachain, Arbitrum, Base, Push, and Lighthouse Storage. The learning curve for these technologies was steep, leading to initial challenges in navigating the documentation and understanding the intricacies of each. However, the well-maintained documentation and the responsiveness of the developer teams played a crucial role in overcoming these challenges. Despite the initial struggles, the support provided helped us gain proficiency in these technologies and use them.