March 13, 2024
Today we ran through a fairly simple demo day on two topics:
- Assigning consumer keys
- Setting a security contact
Consumer key assignment
In the early days of ICS, validators were encouraged to either assign a consumer key or reuse their provider key for consumer chains. That recommendation has changed! It is now only recommended to assign a consumer key and use a unique key for each chain. Never reuse keys, and keep track of which keys are used for which chains.
To reinforce this, we demonstrated key assignment on pion-1
The transaction to assign a consensus key to a consumer chain is in the provider module:
gaiad tx provider assign-consensus-key pion-1 <consumer pubkey>
Of the 56 testnet validators, 42 have now assigned a consumer key. Prior to this demo day, it was only 26 
Set security contacts
Setting a security contact is a lightweight way to verify that an email or social media handle is approved by the keyholders of your validator node, making it easier to speak for your validator without having to touch your keys. Make sure your security contact is up to date though – letting it go stale could mean being you’re being represented by an email or handle that shouldn’t be speaking for you 
To set your validator’s security contact field, use this command as reference:
gaiad tx staking edit-validator --security-contact <contact info> --from <self-delegation address>
49 validators have now set their security contact on the testnet.
Next week
Next week we’ll be taking a testnet break to focus on the mainnet upgrade!
By now, everyone on mainnet should be running assigned consumer keys…so prepare to get roasted if we see any reused keys 
