Has the proposal passing threshold (10%) been adjusted to account for Evonodes?

[Macrochip]

(If I missed the discussion, kindly point it out to me, because I can't fathom that this hasn't come up anywhere)

We all know the amount of nodes went down significantly due to many MNOs switching to Evo-Nodes.
Also, these Evo-Nodes get 4 votes each within the Treasury, because they were originally comprised of -duh- 4 Masternodes.

That means, with everything else being equal, the total number of votes did not change within the Governance system, right?

Then please, for the love of Duff, someone tell me that the proposal passing threshold has been modified to count EvoNodes x4?! Because everywhere I look, it either says "Infinity%" (Dashninja.pl) or still displays 10% of total nodes across the network for a proposal to pass (DMT & dashcentral, namely 307 as of this writing which is nonsense).

You're not going to tell me you haven't thought of this, right?

 

[AgnewPickens]

(If I missed the discussion, kindly point it out to me, because I can't fathom that this hasn't come up anywhere)

We all know the amount of nodes went down significantly due to many MNOs switching to Evo-Nodes.
Also, these Evo-Nodes get 4 votes each within the Treasury, because they were originally comprised of -duh- 4 Masternodes.

That means, with everything else being equal, the total number of votes did not change within the Governance system, right?

Then please, for the love of Duff, someone tell me that the proposal passing threshold has been modified to count EvoNodes x4?! Because everywhere I look, it either says "Infinity%" (Dashninja.pl) or still displays 10% of total nodes across the network for a proposal to pass (DMT & dashcentral, namely 307 as of this writing which is nonsense).

You're not going to tell me you haven't thought of this, right?

The Dashcore protocol gets the numbers right, but Dash Central does not, I guess we need to fund Rango so he can fix some of this stuff.

 

[vazaki3]

The Dashcore protocol gets the numbers right, but Dash Central does not....

The Dashcore protocol does NOT get the numbers right.

Only three places have been coded in order to give us the correct voting outcome, after the establishment of the HCMN/EVO stupidity. All the rest Dash ecosystem refuses until now to become compatible with EVO. The three places are:

1. The core wallet. https://github.com/dashpay/dash/releases/
2. mnowatch leaderboard: https://mnowatch.org/leaderboard/
3. the Base3 votethenumbers page : https://mnowatch.org/votethenumbers/votethenumbers3/

But in reality, THERE IS ONLY ONE PLACE WHERE YOU CAN GET THE CORRECT-ACCURATE VOTING OUTCOME. Because both the core wallet AND mnowatch_leaderboard take into account the POSE_BANNED masternodes when calculating the votes!!!

So the only place where EVO is taken into account AND the votes of the POSE_BANNED masternodes are NOT calculated in the voting outcome (as any rational individual expects to be done) is https://mnowatch.org/votethenumbers/votethenumbers3/ .

@UdjinM6 tried to fix the bug, but the issue remains open and thus the correction is not yet merged into the main core wallet branch. And the mnowatch leaderboard remains compatible to this dash core bug (rather than compatible to logic) because whether a proposal is displayed as succesfull or not into the leaderboard is highly dependant to this bug!

fix: Do not relay/store/count votes from pose-banned MNs by UdjinM6 · Pull Request #5583 · dashpay/dash

Issue being fixed or feature implemented We only count enabled MNs when calculating voting threshold, so ignore non-enabled MNs when counting votes. (Alternative solution would be to count all MNs ...

github.com

Dash is a deep shit coin, operated by a bunch of irrational (very close to the animal level) masternode / crowdnode voters who keep supporting an extremely incompetent DCG...... A really deep shit coin.........................

VOTE THE NUMBERS, STUPID!!!