chore(publish): fix publishing scripts to publish contracts with ceremony params #984
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
✅ Deploy Preview for maci-typedoc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…mony params Add environment variable so that contracts can be built using a different state tree depth param, and thus allow for publishing to npm contracts that work with the ceremony params #973
ctrlc03
force-pushed
the
deps/ceremony-deployment
branch
from
918ff2c to
f27af1c
Compare
|
@yuetloo fyi |
0xmad
approved these changes
Jan 10, 2024
|
@ctrlc03 , can you please publish a npm package with state depth 6 (for the circuit 6-8-2-3 from the ceremony)? We only use this circuit in testing to make sure we catch any issue sooner rather than at the deployment time. |
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.
Description
Add environment variable so that contracts can be built using a different state tree depth param, and thus allow for publishing to npm contracts that work with the ceremony params
Related issue(s)
close: #973
Confirmation