The problem Stealth Pass solves

Anonymous users, such as developers attending ETHGlobal events, conferences, or Devcon, often face significant challenges when purchasing on-chain tokens for tickets. These challenges include:

1. Identity Doxxing:

   • At real-time events, users are required to reveal their real-world identities, which get mapped to their on-chain identities.
   • Many users rely on their on-chain profiles for sensitive consumer-centric transactions or subscriptions that they prefer to keep private.
   • Users holding significant funds face security risks and are reluctant to doxx themselves when attending these events.

2. Lack of Composability with ZK-Based Solutions:

   • Event organizers using ZK approaches cannot utilize ticket data for analytics or data markets due to the lack of user information.
   • ZK solutions prevent users from using their primary wallets for event interactions. For instance, users winning on-chain raffles cannot claim rewards due to the commitment-based model.
   • Proving tickets on-chain with ZK solutions is computationally expensive.

3. Government Requirements for Confidential Access Control:

   • Governments have shown interest in NFT-based event ticketing but require confidentiality and controlled access to data.
     StealthPass addresses these issues by leveraging Fully Homomorphic Encryption (FHE):
   • It ensures user confidentiality while allowing composability for event organizers to utilize data within privacy-preserving constraints.
   • Users can securely use their main wallets to claim rewards and participate in on-chain activities.
   • It provides affordable and efficient ticket validation while meeting government standards for confidentiality and access control.

Challenges we ran into

We first deployed the dapp on L1 made from Avalanche but then we werent able to intgrate Inco's confidentiality layer as it listens to calls from RPC, AA wallets integration with Telegram mini app, Issues in including whole singnature inside QR code