Redeployment scripts for constructor proofs #204
Merged
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.
When we have a secret state initialised in the constructor, we need a proof and verification. This can make it finicky to redeploy since we must recreate the constructor proof and sync up local dbs before the contract is deployed.
I've added a redeployment script and a short note for users in the readme.
EDIT:
restart will no longer work for a running zapp since the nullifier state is kept inside the zapp js files (as opposed to a mongo container for commitments, for example)UPDATE: Added a
reinstateNullifiers
method for re-adding nullifiers known to the local state, designed to be used after redeploying as above.To test:
redeploy
scriptnpm restart
for APIs