Creating and storing persistent VRF public and secret keys.

Question

Creating and storing persistent VRF public and secret keys.

Jasleen1 opened this issue 2 years ago · comments

Now that we have a PR implementing the VRFs, we should find a way to securely generate, store and access the VRF secret key and to publish a VRF public key.

The vrf crate could probably support key generation but still it needs to be stored somewhere.

Sean Lawlor · Answer 1 · Wed Jan 05 2022 23:15:32 GMT+0800 (China Standard Time)

Update: Will be moved to a trait which will be implemented by users of the library (since key storage varies widely by implementation constraints)

Ercan Ozturk · Answer 2 · Thu Jan 06 2022 01:42:27 GMT+0800 (China Standard Time)

Github offers encrypted secrets that can be used with Github actions. Did you mean a solution for key generation/storage/access for the long term?

Sean Lawlor · Answer 3 · Thu Jan 06 2022 03:22:19 GMT+0800 (China Standard Time)

Github offers encrypted secrets that can be used with Github actions. Did you mean a solution for key generation/storage/access for the long term?

Yeah no, it's more where the VRF key would live which is specific to each deployment (my deployment may not want to talk to github, or even have network access, etc). It's better as a trait which is left to whoever is going to utilize the lib to implement where to get the VRF key from.