-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing private keys #11
Comments
@Bill do we have the a list of testing keys and addresses or should I compute one into a csv file? |
We can use the RGOV test keys (https://github.com/rchain-community/rgov/tree/master/bootstrap/PrivateKeys) to enable inter-operation and eventual testing between the repositories/teams. |
@David405 Do we have private keys for testing? |
Testing Keys 1 Testing Keys 2 Testing Keys 3 |
I think this should be in a file with the equivalent rev address, ETH address and pub key. That way we know what to assert for in the test |
We can always generate those from the private keys, but I can create a file for those. |
How about one file per key that contains ETH, REV, PubK, etc? |
why would need a separate file for each? do we want to run nodes using this library? |
Maybe I didn't type it right. One file for each private key that contains the PK, ETH, REV, PubK. |
The goal of having all of them is so that we can know independent of the code what to expect, and the code should generate the expected values. |
Testing will require the use of standard private keys, which need to be created and managed
The text was updated successfully, but these errors were encountered: