You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are two ways of deploying MACI's contracts, via the cli or the contracts tasks. Given the contracts tasks are a much better solution, we should consolidate our processes and documentation to remove any confusion, and focus improvements only on one of the two methods.
For this, we could create a separate package which can be used for deployment (and other tasks like merging and proving)
The text was updated successfully, but these errors were encountered:
@0xshikhar so the main idea here is to use maci-contracts task helpers (Deployer, Prover, ProofGenerator and etc) inside maci-cli, so we don't duplicate the code. maci-cli will have only terminal module and argument parser with validation. Main functionality will be used from thehelpers from maci-contracts. @ctrlc03 potentially, user interaction won't be affected and api will be the same, only internal parts will be changed just to get rid of duplicated code. In case if we want to drop maci-cli in the future, we still have maci-contracts with core logic.
Currently there are two ways of deploying MACI's contracts, via the cli or the contracts tasks. Given the contracts tasks are a much better solution, we should consolidate our processes and documentation to remove any confusion, and focus improvements only on one of the two methods.
For this, we could create a separate package which can be used for deployment (and other tasks like merging and proving)
The text was updated successfully, but these errors were encountered: