Hardcode mnemonics

[LuqiPan]

Closes: #5

Testing

Not sure if I should add some tests that assert the addresses are expected, and if so, where should I add the tests?

[turadg]

Looking good.

Couple concerns:

• we shouldn't add any files to .agoric in the image. That's for validator state. We should actually be removing any files there that aren't in a production chain (optional to do in this PR)
• there shouldn't be any new files in the repo root. The keys are a concern of synthetic-chain, not the repo.

We could put the files somewhere else, but I think it would be best not to make these into files. Just set put them as vars in env_setup.sh.

[LuqiPan]

Well, turns out we do have places that depends on, for example, /root/.agoric/user1.key be present, namely

• contract/Makefile in Agoric/dapp-offer-up
• contract/Makefile in Agoric/dapp-agoric-basics
• proposals/34:upgrade-10/upgradeHelpers.js in Agoric/agoric-3-proposals

Maybe we can add them back into the container, but not under /root/.agoric directory? What do you think, @turadg?

[turadg]

What do you think, @turadg?

They're hard-coded now so we could copy the keys.

Or put them somewhere else as you suggest, if we want to make it easy for downstream to look them up by name. I'd suggest a place like the upgrade-test-scripts path so that it's more clear they're not part of production