Disable participation key checking #2596
Comments
|
Changing estimate to 3, which might still be too low. The key checking system is also responsible for implicitly registering new keys which means the key installation process needs some minor refactoring. |
AlgoStephenAkiki
added a commit
that referenced
this issue
May 5, 2022
Resolves #2596 Removes function which calls loadParticipationKeys() every 60 seconds since MakeFull() for the FullNode does the same thing
AlgoStephenAkiki
added a commit
that referenced
this issue
May 12, 2022
Resolves #2596 Removes function which calls loadParticipationKeys() every 60 seconds since MakeFull() for the FullNode does the same thing
AlgoStephenAkiki
added a commit
that referenced
this issue
May 16, 2022
Resolves #2596 Removes function which calls loadParticipationKeys() every 60 seconds since MakeFull() for the FullNode does the same thing
AlgoStephenAkiki
added a commit
that referenced
this issue
May 17, 2022
* Install State Proof Keys Resolves #3924 Installs state proof keys inside of algod after getting the binary blob * Remove Node Key Monitoring Function Resolves #2596 Removes function which calls loadParticipationKeys() every 60 seconds since MakeFull() for the FullNode does the same thing * Testing * PR comments * Test with secrets * Check that state proofs aren't empty * Different error message * Removed error handling for state proofs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because keys are being copied to the data dir by the node directly, we no longer need to scan the data dir every 60 seconds for new key files.
Convert
node.loadParticipationKeys()into a function that is called once during node initialization instead of once every 60 seconds.The text was updated successfully, but these errors were encountered: