zkblind

Users of blind.com sends the people an email with a random code to click and signup. Sure this works but companies can restrict the receiving of this email. Essentially blocking the people working there from a platform like these. Also with the potential of emails being sent again and again for confirmation, its easier for companies to block access.

Simple, using zkemail, we are able to prove the fact that a specific ethereum address, along with a Semaphore random identity, and a company welcome email, that all employees receive or any specific email that fits the different verification types can be downloaded by the employees. This removes the need for a central entity sending an email to prove that someone works somewhere. The zk circuit generates a proof that the email belongs to a specific domain and by including the semaphore identity and ethereum address as part of it, avoids front running and restricts to the person having that semaphore identity. A verification of this proof, proves that the address belongs to someone working at a specific company and essentially all of the features of semaphore i.e groups, nullifiers and other controls are now applicable. This can also be onboarded with any such anon social group workings. Because the project will have lot of posts, discussions and considering recent trends, more discussions about general topics, we expect many transactions to take place and scroll, with its cheap txn costs, is the home for this project. Refer to the demo for how scroll was used to verify and the costs included for it.