-
Notifications
You must be signed in to change notification settings - Fork 11
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
turn 'phoenix-core' into a 'phoenix' workspace #171
Comments
moCello
added a commit
that referenced
this issue
May 16, 2024
moCello
added a commit
that referenced
this issue
May 16, 2024
moCello
added a commit
that referenced
this issue
May 16, 2024
moCello
added a commit
that referenced
this issue
May 16, 2024
Resolves #171 Co-authored-by: Xavier <xavier@dusk.network>
moCello
added a commit
that referenced
this issue
May 16, 2024
Resolves #171 Co-authored-by: Xavier <xavier@dusk.network>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
With the decision to move the transfer circuits out of 'rusk' and into the phoenix implementation library #170, we have decided to create a new workspace called 'phoenix' with the following structure:
The first step and scope of this issue is to add the workspace and its members. This will also include adding the existing elgamal encryption into the 'circuits' member.
The next step is adding the actual transfer circuits and gadgets as part of #170
The text was updated successfully, but these errors were encountered: