Comment on page
Below mentioned script used to build, deploy and Verify the PERI Finance Source code to a Different testnet and mainnet Network.
This will compile bytecode and ABIs for all .sol files found in node_modules and the contratcs folder. It will output them in a compiled folder in the given build path mentioned below, along with the flattened source files under the folder flattened
# build (flatten and compile all .SOL sources)
node publish build # "--help" for options
This will deploy (or reuse) all of the contracts listed in the contract-flags input file, as well as perform initial connections between the contracts.
# deploy (take compiled SOL files and deploy)
node publish deploy # "--help" for options
-a, --add-new-pynthsWhether or not any new pynths in the pynths.json file should be deployed if there is no entry in the config file.
-b, --build-path [value]Path for built files to go. (default of
./build- relative to the root of this repo). The folders
flattenedwill be made under this path and the respective files will go in there.
-c, --contract-deployment-gas-limit <value>Contract deployment gas limit (default: 7000000 (7m))
-d, --deployment-path <value>Path to a folder that has your input configuration file (
config.json), the synths list (
synths.json) and where your
deployment.jsonfile will be written (and read from if it currently exists).
-g, --gas-price <value>Gas price in GWEI (default: "1")
-m, --method-call-gas-limit <value>Method call gas limit (default: 150000)
-n, --network <value>The network to run off. One of mainnet, kovan. (default: "kovan")
-o, --oracle <value>The address of the oracle to use.
-f, --fee-auth <value>The address of the fee Authority to use for feePool. --oracle-gas-limit
# deploy to rinkeby with 8 gwei gas
node publish deploy -n ropsten -d publish/deployed/ropsten -g 20
node publish deploy -n rinkeby -d publish/deployed/rinkeby -g 20
node publish deploy -n kovan -d publish/deployed/kovan -g 8
node publish deploy -n local -d publish/deployed/local -g 8
To verify the contracts on Etherscan (by uploading the flattened source files and ABIs).
# verify (verify compiled sources by uploading flattened source to Etherscan via their API)
node publish verify # "--help" for options
For all given contracts, will invoke nominateNewOwner for the given new owner;
# Nominate New Owner
node publish nominate # "--help" for options
It assist owner take ownership of nominated contracts and run any deployment tasks deferred to them.
# Helps the owner take ownership of nominated contracts and run any deployment tasks deferred to them
node publish owner # "--help" for options
This script attempt to remove all given synths from the PERI finance contract (as long as they have total supply of 0 and update config.json and pynths.json for the deployment folder.
# Remove all given synths from the Peri finance contract
node publish remove-synths # "--help" for options
This will attempt to replace all given synths with a new given subclass It does this by disconnecting the existing TokenState for the Pynth and attaching it to the new one.
# attempt to replace all given synths with a new
node publish replace-synths # "--help" for options
Will attempt purge the given synth with all token holders it can find. Uses the list of holders from mainnet, and as such won't do anything for other networks.
# attempt purge the given synth with all token holders
node publish purge-synths # "--help" for options
Will initiate the PeriFinance release process, publishing the PeriFinance
npmmodule and updating all dependent projects in GitHub and
# attempt to initiate the PeriFinance release process
node publish release # "--help" for options
Will deploy an instance of StakingRewards.sol with the configured stakingToken and rewardsToken in rewards.json. Then
run node publish verify
# attempt to Staking Rewards
node publish deploy-staking-rewards # "--help" for options
PeriFinancerepo, we are using the following branch mapping:
PRs should start being merged into
developthen deployed onto
KOVAN, then merged into
stagingonce deployed for releasing onto
ropstenfor staging into a
mainnetrelease. These can be done multiple times for each branch, as long as we keep these up to date.
Using semantic versioning (semver):
MAJORstipulates an overhaul of the Solidity contracts
MINORare any changes to the underlying Solidity contracts
ADDITIONALare for testnet deployments
-betafollows alpha, and contains
-rc[N]follows beta, and contrains
0and can be incremented until we are ready to release without the suffix.
- 1.In the environment folder you are deploying to, add the synth key to the
pynths.jsonfile. If you want the synth to be purgeable, add
subclass: "PurgeablePynth"to the object.
- 2.[Optional] Run
buildif you've changed any source files, if not you can skip this step.
deployas usual but add the