Is MoC already hardcoded into spec.json?
rstormsf opened this issue · 1 comments
Is there a way to specify a different spec.json?
I think our playbook is using poa-chain-spec which already has MoC address built in
NB: When launching new networks based make sure to checkout either sokol
or core
branch. master
is currently being updated, something might be broken
Yes, MoC address is part of poa network consensus constructor, so it's in spec.json in bytecode.
There is no built-in way to change spec, however there are some workarounds that depend on what exactly you want to achieve.
-
if you plan on changing other things, you can fork all related repositories (deployment-playbooks, poa-scripts-validator, poa-scripts-moc, poa-chain-spec, eth-netstats, eth-net-intelligence-api, chain-explorer) to your account
rstormsf
and then change this variable https://github.com/poanetwork/deployment-playbooks/blob/sokol/group_vars/all.network#L32 torstormsf
-
if you just want to change spec file, you'll need to provide its url here:
https://github.com/poanetwork/deployment-playbooks/blob/sokol/roles/bootnode/tasks/main.yml#L18
https://github.com/poanetwork/deployment-playbooks/blob/sokol/roles/explorer/tasks/main.yml#L18
https://github.com/poanetwork/deployment-playbooks/blob/sokol/roles/moc/tasks/main.yml#L18
https://github.com/poanetwork/deployment-playbooks/blob/sokol/roles/validator/tasks/main.yml#L18