Our current binaries embed the JSON from specs/bastiat.raw.json and specs/mainnet.raw.json during build and allow using --chain bastiat and --chain mainnet without having to use separate JSON file.
Let's stop publishing separate JSON files and make install.sh rely on embedded specs.
Rationale: this will greatly simplify the upgrade process for users in case of chain spec changes (new bootnodes, new telemetry server, recovering chain in case of catastrophic failure) - they'll be able to just drop-in new binary and things will just work.
Compatibility:
new docker image won't embed the spec files - users running docker will need to change their command line after updating to latest image
new install.sh script won't detect existing json-spec-based installations - users will be prompted to select the network (bastiat/mainnet) again when running script to update from json-spec to embedded-spec.
Our current binaries embed the JSON from
specs/bastiat.raw.jsonandspecs/mainnet.raw.jsonduring build and allow using--chain bastiatand--chain mainnetwithout having to use separate JSON file.Let's stop publishing separate JSON files and make install.sh rely on embedded specs.
Rationale: this will greatly simplify the upgrade process for users in case of chain spec changes (new bootnodes, new telemetry server, recovering chain in case of catastrophic failure) - they'll be able to just drop-in new binary and things will just work.
Compatibility:
install.shscript won't detect existing json-spec-based installations - users will be prompted to select the network (bastiat/mainnet) again when running script to update from json-spec to embedded-spec.