Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a guide to help devs migrate from v3 to v4 #606

Open
2 tasks
cedoor opened this issue Jan 30, 2024 · 1 comment
Open
2 tasks

Create a guide to help devs migrate from v3 to v4 #606

cedoor opened this issue Jan 30, 2024 · 1 comment
Assignees
Labels
documentation 📖 Improvements or additions to documentation

Comments

@cedoor
Copy link
Member

cedoor commented Jan 30, 2024

Tasks

  • List code differences
  • Migration strategy

Links

@cedoor cedoor added the documentation 📖 Improvements or additions to documentation label Jan 30, 2024
@cedoor cedoor added this to the Semaphore V4 milestone Jan 30, 2024
@cedoor cedoor self-assigned this Jul 5, 2024
@artwyman
Copy link
Contributor

FYI Zupass is going to be tackling this migration soon, so I'll stay in touch about our strategy.
The most interesting part is probably our desire to derive a V4 identity from a V3 identity. The likely default there is to do something (append, hash, xor) with the V3 secrets to derive a V4 secret, but we have some people thinking about whether there are things we can do which are more clever (but still secure) which might allow us to ZK prove that a given V4 identity was derived from a V3 identity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation 📖 Improvements or additions to documentation
Projects
Status: 🗒 Tasks
Development

No branches or pull requests

2 participants