feat: use fhevm deployer private key for deployment #552
+362
−555
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.
Now instead of using the mnemonic+
signers[9]
for the fhevm deployer, I am using a new env variablePRIVATE_KEY_FHEVM_DEPLOYER
.I also updated the
launch-fhevm.sh
.Also I added an optional argument
useAddress
to be used in thetask:addSigners
when adding the KMS signers after deployment of KMSVerifier, this will fetch addresses env variables from the.env
instead of private keys for the kms signers.I also did some cleaning, like renaming
computePredeployAddress
tocomputeGatewayAddress
, removed obsolete tasks, moved old obsolete contracts in legacy folder etc.