Co-authored-by: Xiliang Chen <xlchen1291@gmail.com>

…ic key hex

…r storage

…arams

resolved errors that i was getting in the logsoffchain_workers error fetching mpower  and offchain_workers error unknown transaction type  , which appears to because i needed to change the GRACE_PERIOD to a shorter period of say 10 seconds instead of 1 minute

i also only had a single account Alice in the chain_spec as a value for cooling_off_period_days_remaining, but I also needed Bob since, and because in the hard-coded mpower data response from the API i had two accounts with an mpower value, but they accidently both had Alice’s public key hex, so it was using the same account when iterating over multiple miners.

i also wasn’t providing the correct value for the account id to the function set_mpower_of_account_for_date (i was providing the unsigned account id instead of the account id property i’d added as mpower_data_item.account_id_registered_dhx_miner

i checked that i could successfully check on-chain storage for MPowerForAccountForDate` by providing the start of a current date that had been stored, and the public key (hex) value that was provided for the account id in the API response (even though we’re storing the key as Vec<u8> it still fetches it correctly in the UI

change to store accounts as public keys Vec<u8> instead of AccountId

…t so only Sudo or governance may change

…e does not already exist in storage