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

Arkworks v0.5 #4927

Closed
wants to merge 3 commits into from
Closed

Arkworks v0.5 #4927

wants to merge 3 commits into from

Conversation

TalDerei
Copy link
Collaborator

@TalDerei TalDerei commented Nov 18, 2024

Describe your changes

Upgrade arkworks dependencies to v0.5

Issue ticket number and link

References #4911

Related to penumbra-zone/decaf377#109, penumbra-zone/poseidon377#65, penumbra-zone/decaf377-rdsa#27

Checklist before requesting a review

  • I have added guiding text to explain how a reviewer should test these changes.

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

@TalDerei TalDerei self-assigned this Nov 18, 2024
@TalDerei TalDerei marked this pull request as draft November 18, 2024 07:37
TalDerei pushed a commit that referenced this pull request Nov 18, 2024
## Describe your changes

The parameter-setup crate was broken due to outdated dependencies. The
options here are:
1. add this tool to the workspace
2. keep the dependencies updated instead of using workspace inheritance

Option 1 is more maintainable. Even though the parameters are fixed now
due to mainnet, folks may try to use this crate for debugging - the
scenario that motivated this commit.

To test: I followed the steps in
https://guide.penumbra.zone/dev/parameter_setup to ensure we could run
the parameter setup.

## Issue ticket number and link

This was discovered while debugging #4927

## Checklist before requesting a review

- [x] I have added guiding text to explain how a reviewer should test
these changes.

- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:

  > this is a dev only change
@TalDerei
Copy link
Collaborator Author

closing due to circuit breaking changes identified in penumbra-zone/decaf377#109 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant