The problem VeilPad solves

Privacy and anonymity in blockchain crowdfunding and token launches are significant challenges. Most platforms expose user identities and contribution amounts, making it difficult to participate in fundraising events without revealing personal data.

How VeilPad Helps

VeilPad is a privacy-focused launchpad that enables users to participate in token sales anonymously and securely using zero-knowledge proofs (ZKPs) and Merkle trees.

Key Benefits

• Preserves Anonymity 🕵️‍♂️
  Users can contribute to token sales without exposing their wallet addresses or transaction details.

• Secure Whitelisting ✅
  Participants prove their eligibility without revealing their identity, ensuring fair access.

• Decentralized & Trustless 🔗
  All proofs are verified on-chain, eliminating the need for centralized identity verification.

• Prevents Front-Running & Sniping 🚀
  Contributions remain private until the sale ends, reducing risks of manipulation.

• Seamless User Experience ✨
  Users generate proofs off-chain and submit them without complex technical steps.

Who Can Use VeilPad?

• Project Teams: Conduct private token sales without revealing sensitive user data.
• Investors: Participate in funding rounds without exposing portfolio details.
• DAOs & Communities: Raise funds while keeping members’ contributions confidential.

By combining privacy, security, and decentralization, VeilPad makes token launches safer, fairer, and more accessible to everyone. 🚀

Challenges we ran into

Challenges Faced During Development

Over the development of the project, we ran into several challenges. Some of them are:

1. Understanding the Concept of Zero-Knowledge Proofs
   The concept of zero-knowledge and zk-proofs was rather new to us, so understanding that took some effort.

2. Learning to Build Circom Circuits
   One big challenge we faced was learning the syntax of Circom and writing working circuits for zk-SNARK proofs.

3. ZKVerify Integration
   Integrating ZKVerify with our dApp through the zkverifyjs library also required effort.

4. Generating the zk-Proofs
   Since we had never used zk libraries such as snarkjs before, it was a little tough to write the code to generate Groth16 proofs using that.