-
Notifications
You must be signed in to change notification settings - Fork 19
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
Randomly assign triples to a node after creation #412
Conversation
Terraform Feature Environment (dev-412)Terraform Initialization ⚙️
|
While it's not strictly necessary right now (every node should be running the same version) it will save people trouble should they ever want to loosen that restriction/if nodes are running subtley different binaries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but yeah we should look into why there are so many duplicate(?) messages being generated
Created an issue to understand why so many messages are getting sent at https://github.com/near/mpc-recovery/issues/415 |
Terraform Feature Environment Destroy (dev-412)Terraform Initialization ⚙️
|
Terraform Feature Environment Destroy (dev-412)Terraform Initialization ⚙️
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DavidM-D Can the node generate a triple, check if its entropy (big_c) will allow it to own it, and only then proceed?
@volovyks what do you mean by "then proceed"? You only get to know |
Closes #384