Fix TSS AccountId keys in chainspec
#993
Conversation
HCastano
changed the title
AccountID keys in chainspec
HCastano
changed the title
AccountID keys in chainspecAccountId keys in chainspec
| /// Mnemonic: "beef dutch panic monkey black glad audit twice humor gossip wealth drive" | ||
| pub static ref DAVE: sp_runtime::AccountId32 = | ||
| super::hex!["12bf1c8e365c20cc2af606e3814b98b192857d85d182dac5e33fb90d0380ca75"].into(); | ||
| super::hex!["0a9054ef6b6b8ad0dd2c89895b2515583f2fbf1edced68e7328ae456d86b9402"].into(); |
There was a problem hiding this comment.
So I thought we were just supposed to be using subkey for these, not the HPKE stuff.
This is because an operator would be passing this in using the --mnemonic flag, which ideally they get by running subkey generate.
In this case then, the public key here should be 0x12bf1c8e365c20cc2af606e3814b98b192857d85d182dac5e33fb90d0380ca75 iiuc.
❮ ./target/release/entropy key inspect "beef dutch panic monkey black glad audit twice humor gossip wealth drive"
Secret phrase: beef dutch panic monkey black glad audit twice humor gossip wealth drive
Network ID: substrate
Secret seed: 0xb7bb3269a4a184529445a7fc91b03a87c17be3309cfa23adbcccb0f0fbc7f087
Public key (hex): 0x12bf1c8e365c20cc2af606e3814b98b192857d85d182dac5e33fb90d0380ca75
Account ID: 0x12bf1c8e365c20cc2af606e3814b98b192857d85d182dac5e33fb90d0380ca75
Public key (SS58): 5CVHVSDm8643E1JWesWUjt7GZR6zMQa5oytg9TkBTMJ8T3cq
SS58 Address: 5CVHVSDm8643E1JWesWUjt7GZR6zMQa5oytg9TkBTMJ8T3cq
There was a problem hiding this comment.
so you can get the phrase and pass it in then on spin up the tss server will generate the keys from the seed and spit it out in the .production file under account_id
There was a problem hiding this comment.
The auditors didn't like us deriving the encryption keys from signing keys, so now both signing keypair and encryption keys are derived from the mnemonic, using a different derivation process to that of subkey.
There was a problem hiding this comment.
Okay maybe I need to follow up with that issue again 🤔
There was a problem hiding this comment.
that is cool gonna merge in the meantime since it is blocking
| @@ -75,15 +75,15 @@ pub mod tss_account_id { | |||
| pub static ref CHARLIE: sp_runtime::AccountId32 = | |||
There was a problem hiding this comment.
How come Alice, Bob, and Charlie don't need to change?
There was a problem hiding this comment.
they were done correctly by @ameba23 when he added hpke, I added these ones later for the four node images
| /// Mnemonic: "impact federal dish number fun crisp various wedding radio immense whisper glue" | ||
| pub static ref EVE: sp_runtime::AccountId32 = | ||
| super::hex!["f2b4113735e988f662fe45e97b39770e804ebcd893ad0ab7cd8b7c5b5dcfff22"].into(); | ||
| super::hex!["ac0d9030598f1722ff7c6a2a3043fa65903448dcc7a23011ec06c1c31cdad120"].into(); |
There was a problem hiding this comment.
Similar thing here
❮ ./target/release/entropy key inspect "impact federal dish number fun crisp various wedding radio immense whisper glue"
Secret phrase: impact federal dish number fun crisp various wedding radio immense whisper glue
Network ID: substrate
Secret seed: 0x0b22c9142215fbb5de12d6f372e3a0819887945209c98405787a68c10a9ed4fb
Public key (hex): 0xf2b4113735e988f662fe45e97b39770e804ebcd893ad0ab7cd8b7c5b5dcfff22
Account ID: 0xf2b4113735e988f662fe45e97b39770e804ebcd893ad0ab7cd8b7c5b5dcfff22
Public key (SS58): 5HYvwGKUxxCLWnhhGXbonLdgQ3wTLopUVyMvjAAo4o2j3XQi
SS58 Address: 5HYvwGKUxxCLWnhhGXbonLdgQ3wTLopUVyMvjAAo4o2j3XQi
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
|
to answer both comments, yes I got these keys from actually running the TSS server and grabbing the output of what is generated |
Keys were generated incorrectly with subkey when we needed to use hpke