crypto: testnet parameter setup tooling #1885
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
force-pushed
the
zk-integration
branch
from
13b26e9
to
d8e7d40
Compare
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
force-pushed
the
zk-integration
branch
from
e1f8bfc
to
935a3be
Compare
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
changed the title
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
had a problem deploying
to
smoke-test
GitHub Actions
Failure
redshiftzero
force-pushed
the
zk-integration
branch
from
95882f8
to
68e98de
Compare
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
force-pushed
the
zk-integration
branch
from
68e98de
to
1b1f6dc
Compare
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
force-pushed
the
zk-integration
branch
from
1b1f6dc
to
b138bd8
Compare
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
redshiftzero
force-pushed
the
zk-integration
branch
from
b138bd8
to
34b3e6e
Compare
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
This was referenced Jan 31, 2023
I'm linking out as the link has detailed instructions for each platform which it seems silly to reproduce in our docs.
Committing the .gitattributes file is recommended for collaborating on repositories with Git LFS [0]. In that file we're currently saying that files ending in *.bin should always be tracked using Git LFS. [0] https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage
redshiftzero
force-pushed
the
zk-integration
branch
from
34b3e6e
to
5e9e818
Compare
redshiftzero
temporarily deployed
to
smoke-test
GitHub Actions
Inactive
|
@redshiftzero I enabled ad-hoc runs of the container build story in 01ca799. Can you rebase this PR and try kicking off a run of that workflow on this branch? |
|
Dope, tis running now: https://github.com/penumbra-zone/penumbra/actions/runs/4068809157 |
|
Build succeeded! Looks like the lfs knobs you enabled in the workflow are indeed sufficient for the container story. I haven't pulled down that container and inspected it, but will take a look at preview once this lands. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #711
This adds two crates:
tools/parameter-setupthat lets one generate (or regenerate) the parameters for the existing circuits. These parameters are then serialized to files inproof-params/src/gen/*.bin.penumbra-proof-paramsthat loads those parameters and deserializes them. This is the crate that would be a dependency added anywhere where we wish to create and verify proofs.Note to the interested observer: this code and the generated parameters will only be used for development and testnet purposes. A different procedure will be used for mainnet (tracked in #712).