feat: add activationBlockOffset to deploy config

Author: ezdac

contracts/deploy/500_configure_keypers.js

@@ -2,5 +2,5 @@ const { configure_keypers } = require("../lib/configure-keypers.js");
 
 module.exports = async function (hre) {
   var keyperAddrs = await hre.getKeyperAddresses();
-  await configure_keypers(keyperAddrs);
+  await configure_keypers(keyperAddrs, hre.deployConf.activationBlockOffset);
 };

contracts/hardhat.config.js

@@ -83,6 +83,7 @@ extendEnvironment((hre) => {
       keypers: null,
       collator: null,
       fundValue: "",
+      activationBlockOffset: 30,
     };
   }
 

contracts/scripts/change-keypers.js

@@ -27,9 +27,6 @@ async function main() {
   }
 
   const keyperSetIndex = parseInt(process.env.KEYPER_SET_INDEX);
-
-  // TODO can we get access to the hre in a script like this?
-  // TODO use a different json file to determine the keyper changes
   const deployConf = JSON.parse(fs.readFileSync(process.env.DEPLOY_CONF));
 
   const newKeyperSet = deployConf.keypers?.at(keyperSetIndex);
@@ -45,8 +42,9 @@ async function main() {
   const bankSigner = await ethers.getSigner(bank);
 
   const fundValue = hre.deployConf.fundValue;
+  const activationBlockOffset = hre.deployConf.activationBlockOffset;
   await fund(newKeyperSet, bankSigner, fundValue);
-  await configure_keypers(newKeyperSet, 30);
+  await configure_keypers(newKeyperSet, activationBlockOffset);
 }
 
 main()

docker/config.example/node-deploy.json

@@ -13,5 +13,6 @@
   ],
   "decryptors": ["0x0000000000000000000000000000000000000000"],
   "collator": "0x2E135FE171fB6351026B75aF688a7F9689B66B87",
-  "fundValue": "1000"
+  "fundValue": "1000",
+  "activationBlockOffset": "30"
 }