-
Notifications
You must be signed in to change notification settings - Fork 39
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
feat(dashmate): warn user if the node is participating in DKG sessions #1648
Comments
dashmate core cli 'quorum memberof protxhash 1' looks to be working too. [ So two quorum involvements currently (llmq 400_85 & llmq 100_67), for this specific Evonode. Not sure if these two llmq quorums will also be giving high PoSe Penalty scores (DKG), when getting interrupted by a Dashmate restart. |
Unfortunately, udjin says that it only shows mined DKG windows, in other words that alread have passed |
@pshenmic does it mean that we still can warn user if masternode is participating in the current DKG session (but not future)? |
I guess we will need a new Evo RPC that Dashmate can use to check if a specific Masternode / Evonode is currently involved (before mined) in LLMQ_50_60 (?), LLMQ_100_67, LLMQ_60_75 LLMQ_50_60 is consistently failing to initiate according my core.logs, seems connected to DIP24 somehow ? So maybe this LLMQ does not need to be included. Not sure if LLMQ_400_60 is involved with high PoSe Penalty DKG scores, UdjinM6 mentioned (/24)*24 & (/288)*288 so that could also include LLMQ_400_60 |
Interim solution (untill this gets tackled on protocol level) : https://www.dash.org/forum/index.php?threads/llmq-pose-check-on-your-evonode-or-masternode-setup-through-dashmate.54445/#post-237453 |
Expected Behavior
Warn user if masternode is participating or going to participate in the DKG session soon when user want to stop or restart the node
Current Behavior
If user restart core service during DKG session, it will likely receive a POSE ban. We should warn the user about that so that he would choose different restart time window
Possible Solution
We can calculate time window with the given formula:
![image](https://private-user-images.githubusercontent.com/17009187/292920379-dd0f1d80-6bc9-45eb-8bff-cf3e0cc6c140.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyMjAzOTAsIm5iZiI6MTczOTIyMDA5MCwicGF0aCI6Ii8xNzAwOTE4Ny8yOTI5MjAzNzktZGQwZjFkODAtNmJjOS00NWViLThiZmYtY2YzZTBjYzZjMTQwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDIwNDEzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc1ODQ0NjAyMjQ2MDI4YmQyNjAwZWQ0OTc1YTE1YWQ2ZDBkMGUyNGE0NmI3Y2NkNmI0MjA1YjVhN2U3NGQ0YjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.HsfnOEV8COK3-_M12aBy2yyieqOG9gxIfHqx-X-Ad8I)
The text was updated successfully, but these errors were encountered: