v3.1.0
What's Changed
- Changed the version of datahighway-collator and datahighway-parachain-runtime packages in their Cargo.lock files to be the same version 3.1.0
- Fixes treasury DHX DAO Unlocked Reserves SS58 address 4LTFqiD6H6g8a7ur9WH4RxhWx2givWfK7o5EDed3ai1nYTvk in chain_spec.rs so it is the correct amount of 30 million DHX.
- Old temporary DHX DAO Unlocked Reserves public key a42b7518d62a942344fec55d414f1654bf3fd325dbfa32a3c30534d5976acb21 was also being funded in chain_spec.rs so it has been removed.
- Add genesis.json file to import hardspoon account balances from the DataHighway Westlake standalone chain into the genesis block of the DataHighway parachain. The values in genesis.json should override any other values in genesis.json. The balance values are based on those obtained from Subscan and stored in the data/ subfolder using the script here
- Checked that total issuance when run locally is approx. 31.8 million DHX.
- Sudo account from DataHighway standalone chain with SS58 address 4NN9N4NCLWQWNsb2RRYE7CSPTN1tLa7Ez5eViJ4N1Q5wx9z3 still has the same balance on the DataHighway parachain. A democracy proposal may be created in future to burn the funds.
- Authorities from the DataHighway standalone chain will not also be authorities on the DataHighway parachain as they have different accounts and keys, but those on the DataHighway standalone chain were effectively run by the DataHighway (funded by MXC) to run validator nodes and to secure the standalone chain. Those accounts were given a head start with ~10 DHX in the initial DataHighway standalone genesis, and their remaining account balances will be transferred to the DataHighway parachain since they contributed to early development, noting that their account balances may have changed due to validator rewards. Their remaining old authority account balances were as shown here. Their grandpa, babe, imonline and authority discovery keys did not have an account balance.
- There were ten (10) validators run by the DataHighway (funded by MXC) who were slashed and so too were their nominators on the DataHighway standalone chain. In era 1089 it affected validators 6-9, and then later occurred again in era 1091 and affected validator 5 and 10. It was caused because the validators were offline for too long and the chain was using Babe instead of Aura. It was necessary to purge the database and resync the chain after adding the
--unsafe-pruning --pruning 1000
parameter, but the re-sync about a day and was done one validator at the time. A democracy proposal may be created to credit the slashed funds in future.
Full Changelog: https://github.com/DataHighway-DHX/DataHighway-Parachain/commits/v3.1.0