ZKBlind roadmap: https://github.com/ZkBlind/zkBlind

  1. Implement the protocol that ensures 1 email address can only register 1 account
  2. Generate and verify the zkp of your own this email
  3. GitHub base repo link https://github.com/zkemail/zk-email-verify
  4. In our use case, we should have the user public key written in the email
  5. Write the circuit that will generate the zk proof that (a.) the email has been signed by the correct email provider, (b.) secret of the public that is written in the email is used to sign this zkp (verify email sender and request sender is the same person)
  6. Use JS to verify this zkp
  7. Zk JWT which can acquire a JWT token with the metamask wallet
  8. We have a database records the user info which looks like userId -> public key
  9. Server needs to verify that user does have the secret key before letting user to do any actions
  10. Asking metamask wallet to sign every messages is a headache, and it would be nice to have a JWT issued and user only needs to sign in with metamask once.
  11. Front and backend of the zkInsider for demo. https://www.teamblind.com/

For our project to work there are several constraints

  1. emaill is signed with DKIM with legit sig (is done by zkemail, we just need to know how it works, you can try it their circom apart and test it out) - it is a big circuits and probably can be broke down into many smaller circuits
  2. email body has public key and a ECDSA sig (public key is the message that we are trying to sign. I was trying to do this with Spartan-ecdsa yesteday and can probably finish it soon)
  3. email body has only public key and a ECDSA sig, nothing else. (I can imagine it needs some regex circuits for this)
  4. user supplied a secret key which matches the public key in the email body

Untitled

Untitled