гарні новини
Dash Core v20.0.0 Release Announcement
- Thread starter Pasta
- Start date
I always managed everything
Дякую за попередження
qwizzie
Well-known member
For Masternode / Evonode owners
How to avoid Pose scores during future Dash Core updates (updating to future Dash Core v20.0.3 for example) :
Check either your debug.log (Masternode) or your core.log (Evonode). I normally download it and open it with Notepad++
Go to the very end of that log (ctrl + end) and search (ctrl + f) backwards for :
quorum initialization OK for llmq_100_67 qi[0]
return from my core.log : CDKGSessionManager::InitNewQuorum -- height[1993008] quorum initialization OK for llmq_100_67 qi[0]
If returned height (1993008) is older then current block height (https://chainz.cryptoid.info/dash/), then there is currently no involvement with this specific quorum. This LLMQ has an interval of 24 blocks / 1 hour.
quorum initialization OK for llmq_60_75
return from my core.log : CDKGSessionManager::InitNewQuorum -- height[1992991] quorum initialization OK for llmq_60_75 qi[31]
If returned height (1992991) is older then current block height (https://chainz.cryptoid.info/dash/) & it indeed returns [31], then there is currently no involvement with this specific quorum.
Note : this llmq quorum runs from 0-31 (31 blocks), so if it returns anything other then 31, then wait with updating Dash Core untill it reached [31] and current block height is higher then quorum block height. This LLMQ has an interval of 288 blocks / 12 hours.
This should prevent receiving a high PoSe Penalty score during a Dash Core update or even an instant PoSe ban when your Masternode or Evonode happens to be involved in both quorums, when you try to update your Dash Core version to a new version. It also allows you to do some sporadic server maintenance (OS updates), without increased risk for a PoSe Penalty score. That is my hope at least.
If above is in need of correction, please let me know.
Far better would of course be a way to interrupt this at protocol level and warn MNO's if their Masternode or Evonode is currently involved in one or more llmq quorums and shutting down dashd / dashmate is not recommended at this specific time --> https://www.dash.org/forum/index.php?threads/dashmate-discussion.53951/page-4#post-237247
How to avoid Pose scores during future Dash Core updates (updating to future Dash Core v20.0.3 for example) :
Check either your debug.log (Masternode) or your core.log (Evonode). I normally download it and open it with Notepad++
Go to the very end of that log (ctrl + end) and search (ctrl + f) backwards for :
quorum initialization OK for llmq_100_67 qi[0]
return from my core.log : CDKGSessionManager::InitNewQuorum -- height[1993008] quorum initialization OK for llmq_100_67 qi[0]
If returned height (1993008) is older then current block height (https://chainz.cryptoid.info/dash/), then there is currently no involvement with this specific quorum. This LLMQ has an interval of 24 blocks / 1 hour.
quorum initialization OK for llmq_60_75
return from my core.log : CDKGSessionManager::InitNewQuorum -- height[1992991] quorum initialization OK for llmq_60_75 qi[31]
If returned height (1992991) is older then current block height (https://chainz.cryptoid.info/dash/) & it indeed returns [31], then there is currently no involvement with this specific quorum.
Note : this llmq quorum runs from 0-31 (31 blocks), so if it returns anything other then 31, then wait with updating Dash Core untill it reached [31] and current block height is higher then quorum block height. This LLMQ has an interval of 288 blocks / 12 hours.
This should prevent receiving a high PoSe Penalty score during a Dash Core update or even an instant PoSe ban when your Masternode or Evonode happens to be involved in both quorums, when you try to update your Dash Core version to a new version. It also allows you to do some sporadic server maintenance (OS updates), without increased risk for a PoSe Penalty score. That is my hope at least.
If above is in need of correction, please let me know.
Far better would of course be a way to interrupt this at protocol level and warn MNO's if their Masternode or Evonode is currently involved in one or more llmq quorums and shutting down dashd / dashmate is not recommended at this specific time --> https://www.dash.org/forum/index.php?threads/dashmate-discussion.53951/page-4#post-237247
Last edited:
v20.0.3 has been released!
https://github.com/dashpay/dash/releases/tag/v20.0.3
This release is highly recommeneded for masternodes and users with large wallets experiencing slow lock and unlock times; but is optional.
https://github.com/dashpay/dash/releases/tag/v20.0.3
This release is highly recommeneded for masternodes and users with large wallets experiencing slow lock and unlock times; but is optional.
v20.0.4 has been released!
https://github.com/dashpay/dash/releases/tag/v20.0.4
This release is highly recommeneded for masternodes. Additionally, Windows anti-virus false positives have been resolved.
Additionally please fill out this short survey https://forms.gle/kHpPvP7DoBDymNENA about user habits of validating their downloads!
https://github.com/dashpay/dash/releases/tag/v20.0.4
This release is highly recommeneded for masternodes. Additionally, Windows anti-virus false positives have been resolved.
Additionally please fill out this short survey https://forms.gle/kHpPvP7DoBDymNENA about user habits of validating their downloads!
qwizzie
Well-known member
See also this :
I did notice for awhile now something missing on https://www.dash.org/downloads/#windows(besides currently having no download links to v20.0.4 !) :
* SHA256SUMS.asc
* Windows binaries to directly replace current binaries (i am not talking about the Dash wallet setup binary / dashcore-20.0.x-win64-setup.exe)
dashcore-20.0.x-win64.zip
dashcore-20.0.x-win64.zip.asc
SHA256SUMS.asc
Those seem to be only available on Dashpay Github (https://github.com/dashpay/dash/releases/tag/v20.0.4).
Which is a bit of a shame as Windows users are not always that familiar with Github and not always have a need to
download a Dash wallet setup file and when using dashcore-20.0.x-win64.zip (or any Dash wallet .zip file), they will need
the SHA256SUMS.asc for hash verification.
I think above mentioned files should also be available on https://www.dash.org/downloads/#windows, so users don't need to switch to Github to get those specific wallet files and do a hash verification from there. Basically DCG is limiting the SHA256 hash verification part to Github only, thereby not reaching a wider Dash users audience. Therefore not teaching the importance of SHA-256 hash verification on downloads to all Dash users, just to those Dash users already familiar with Github and not in need of the Dash wallet setup file.
Now for something entirely different....
To Masternode and Evonode owners who setup their nodes through Dashmate and plan to update to v20.0.4 :
You can use my shell script to do a LLMQ PoSe check before stopping Dashmate, thereby hopefully avoiding a high PoSe Penalty score (interrupting 1 LLMQ) or Instant PoSe ban (interrupting 2 or more LLMQ) on your Masternode / Evonode : https://www.dash.org/forum/index.ph...ode-setup-through-dashmate.54445/#post-237453
I did notice for awhile now something missing on https://www.dash.org/downloads/#windows
* SHA256SUMS.asc
* Windows binaries to directly replace current binaries (i am not talking about the Dash wallet setup binary / dashcore-20.0.x-win64-setup.exe)
dashcore-20.0.x-win64.zip
dashcore-20.0.x-win64.zip.asc
SHA256SUMS.asc
Those seem to be only available on Dashpay Github (https://github.com/dashpay/dash/releases/tag/v20.0.4).
Which is a bit of a shame as Windows users are not always that familiar with Github and not always have a need to
download a Dash wallet setup file and when using dashcore-20.0.x-win64.zip (or any Dash wallet .zip file), they will need
the SHA256SUMS.asc for hash verification.
I think above mentioned files should also be available on https://www.dash.org/downloads/#windows, so users don't need to switch to Github to get those specific wallet files and do a hash verification from there. Basically DCG is limiting the SHA256 hash verification part to Github only, thereby not reaching a wider Dash users audience. Therefore not teaching the importance of SHA-256 hash verification on downloads to all Dash users, just to those Dash users already familiar with Github and not in need of the Dash wallet setup file.
Now for something entirely different....
To Masternode and Evonode owners who setup their nodes through Dashmate and plan to update to v20.0.4 :
You can use my shell script to do a LLMQ PoSe check before stopping Dashmate, thereby hopefully avoiding a high PoSe Penalty score (interrupting 1 LLMQ) or Instant PoSe ban (interrupting 2 or more LLMQ) on your Masternode / Evonode : https://www.dash.org/forum/index.ph...ode-setup-through-dashmate.54445/#post-237453
Last edited:
Hi!