Networking dapp for Web3 events

Problem:：Networking at web3 events.

• ① Difficult to find people who you want to meet at the events.
• ② Difficult to exchange personal profiles and contact information.
• ③ It’s challenging to keep track of events.

Solution:：Networking dapp for Web3 events

• ① See all attendees’s profile at the event.
• ② Exchange profiles by scanning each other’s QR code, or via one link
• ③ Find all Web3-related events in one place.

①Deploy SBT to Blockchain

• Mina：For users to deploy SBT.

• Boba：For users to deploy SBT.

• Gnosis：For users to deploy SBT.

• Polygon：The Souldbound minting contract deployed and consumed with cheap fees.

• Optimism：The Souldbound minting contract deployed to this network to experience high scalabality.

• The Graph：To build the SBTs gallery for each user profile so the user can see the information almost instantly by subgraph, in the future we can also leverage it to get aggregated information about minted SBTs or other statistical data.

• Open Zeppelin：We are using the following open zeppelin libraries:erc721metadata, erc165, erc712, ownable, bitmap and signature checker. We are also using their upgradeability pattern using UUPS and also open zeppelin upgrades hardhat plugin here are the code lines:

②For user's privacy

• IPFS/Filecoin： To upload metadata about the encounter, upload media data, dapp deployed to IPFS.code is here

• Ceramic： To mix these on-chain solutions with off-chain portable data by using Ceramic and Lit protocols, to achieve a superior UX combined with React to easily onboard every kind of use in any platform so that users can own data by themself.code is here

• ENS：Optional subdomains or just integration with avatar, twitter fields, create profile in eth page and redirect to web2 eth.link.code is here

• Sismo：To increase trust and understand about users well by aggregating on-chain data visible while protecting user privacy information.code is here

1.Privacy fighter ：Adding NFT collector badge to use in case use wants to have more security for their NFTs but still use ZK Badge for reputation. It's merged and deployed here. And here. ZK badge in sismo codebase.

Technical details

• ①The Soulbound tokens and their characteristics: non transferable but burnable to avoid spam.
• ②The Etherum standards we based the product on: ERC712 for signature verifications, ERC4973 for SBTs and contracts upgradeable with UUPS.
• ③The signatures are stored off-chain and encrypted with Threshold cryptography thanks to Lit protocol, any sensitive data is encrypted that way as well.
• ④Part of the data relevant to encounter goes onchain when a user decides to mint the SBT to proof the encounter.
• ⑤We built universal apps for web (nextjs) and mobile (ios, android).