hard-code governance keys in SCM

[turadg]

What is the Problem Being Solved?

The governance keys are generated on each build, to prevent code from depending upon them. (Any code that did would break.)

This has a cost though to using the resulting build. Some of it can be automated (by pulling the key material from the image) but it's a royal pain with GUI tools like Keplr to update for each build.

Description of the Design

Generated the keys once and check the mnemonics into SCM. Have the build import those.

We still want to prevent logic depending on the specific keys. Code review may suffice but we've missed some before. Maybe a simple grep for agoric1 in proposals is worthwhile.

With the mnemonics not a secret, it might help to output them to logs for easy discovery.

[turadg]

I just noticed that VALIDATORADDR is actually a delegator. I hacked around it downstream with https://github.com/Agoric/agoric-sdk/blob/f8b99f2bbe8bf579b5b42b68813f9c231f941a0b/a3p-integration/proposals/c:stake-bld/test.sh but when this issue is tackled it should include an upsteam fix.