Updated Pools running 0.9.11.4/5/6 (Paying Masternode Payments)

mattmct

Member
Mar 13, 2014
259
92
88
Cheers for updates guys, I'll get the pools with 11.05 added.


Shame it will be harder to workout if they have or not, simply by looking at the list.
 

chaeplin

Active Member
Mar 29, 2014
749
356
133
19 mins ago 06/30 14:12:16 94044 [1][2][3] 4817.278 5 coinotroncom Xk1cQZoUoZ7C5soDsB7uRyZUsv5jz5tgRr 1.000200 [1][2][3][-]

 
  • Like
Reactions: mattmct

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
19 mins ago 06/30 14:12:16 94044 [1][2][3] 4817.278 5 coinotroncom Xk1cQZoUoZ7C5soDsB7uRyZUsv5jz5tgRr 1.000200 [1][2][3][-]
Finally !! Do you have any stats on % of updated clients?
 

Ryan Taylor

Well-known Member
Foundation Member
Jul 3, 2014
550
1,649
263
Scottsdale, AZ, USA
As of 8pm EDT tonight, coinotron appears to have STOPPED paying masternode payments. Is this correct?

Also, my analysis of the blockchain today shows that we are not only no longer gaining ground, but actually losing ground on the percentage of blocks that pay... statistically, the trend is toward fewer masternode payments, possibly as low as 40% currently (though I'm not sure I have enough data to prove statistical significance). I think the evidence shows that miners are actively seeking to mine for non-updated pools (which makes sense for them, economically). Pools are likewise disincentivized to update. I'm not sure there's anything we can do at this point except shame bad actors (especially cases like coinotron that WERE updated, but seem to have reversed course, not that I can really blame them) and put our own hash power to work on compliant pools. Any ideas?
 

chaeplin

Active Member
Mar 29, 2014
749
356
133
As of 8pm EDT tonight, coinotron appears to have STOPPED paying masternode payments. Is this correct?

Also, my analysis of the blockchain today shows that we are not only no longer gaining ground, but actually losing ground on the percentage of blocks that pay... statistically, the trend is toward fewer masternode payments, possibly as low as 40% currently (though I'm not sure I have enough data to prove statistical significance). I think the evidence shows that miners are actively seeking to mine for non-updated pools (which makes sense for them, economically). Pools are likewise disincentivized to update. I'm not sure there's anything we can do at this point except shame bad actors (especially cases like coinotron that WERE updated, but seem to have reversed course, not that I can really blame them) and put our own hash power to work on compliant pools. Any ideas?
http://drk.poolhash.org/masternode.html?srch&nmstr=coinotroncom
coinotroncom is paying.
I think coinotroncom has a issue on Masternode list syncing.

And I have changed http://drk.poolhash.org/poolhash.html , from 3 hours to 6 hours.
pool pool_unknown_146 got a lot of blocks with no paying.

So percentage of payments is decreasing.


And I will make a graph showing percentage of payments, every hour, from starting block 91796.
 

flare

Grizzled Member
May 18, 2014
2,286
2,404
1,183
Germany
So percentage of payments is decreasing.
No , the ratio has not changed. 144 of last 280 blocks (96008-96288) were not paid --> 51% unpaid. Thats exactly the same ratio we had 4 days ago:

I had a look at the last 12hours (Block 93776 - Block 94056) on http://drk.poolhash.org/graph.html

Total generation: 280 Blocks
Paid blocks: 137 Blocks
Unpaid Blocks: 143 Block

This means there is still 51% of overall hashpower belonging to 'bad actors'.
Remarkable that we are touch and go on a "51% attack" boundary here for days...

And I will make a graph showing percentage of payments, every hour, from starting block 91796.
This will be very usefull indeed :)
 

chaeplin

Active Member
Mar 29, 2014
749
356
133
Hmm, are you sure that matches the numbers on http://drk.poolhash.org/poolhash.html ?

Blocks 96118 to 96401 --> 283 blocks total, 143 unpaid, 140 paid. Thats more 50% to 50%, whereas you graph implies 44% to 56%
Every 30 minutes, count last 576 blocks(1 day).
(block height - 6 blocks - 576 blocks) ~ (block height - 6 blocks)

It use result in http://drk.poolhash.org/masternode.html

(tip do http://drk.poolhash.org/masternode.html?srch&nmstr=tx_0_vout_1
http://drk.poolhash.org/masternode.html?srch&nmstr=X
)

Code:
[email protected]:~> tail -576  blocks/blocks_payee | grep tx_0_vout_1 | wc -l
258
[email protected]:~> tail -288  blocks/blocks_payee | grep tx_0_vout_1 | wc -l
145
[email protected]:~> tail -283  blocks/blocks_payee | grep tx_0_vout_1 | wc -l
144
 
Last edited by a moderator:
  • Like
Reactions: flare

flare

Grizzled Member
May 18, 2014
2,286
2,404
1,183
Germany
Every 30 minutes, count last 576 blocks(1 day).
(block height - 6 blocks - 576 blocks) ~ (block height - 6 blocks)

It use result in http://drk.poolhash.org/masternode.html

(tip do http://drk.poolhash.org/masternode.html?srch&nmstr=tx_0_vout_1
http://drk.poolhash.org/masternode.html?srch&nmstr=X
)

Code:
[email protected]:~> tail -576  blocks/blocks_payee | grep tx_0_vout_1 | wc -l
258
[email protected]:~> tail -288  blocks/blocks_payee | grep tx_0_vout_1 | wc -l
145
[email protected]:~> tail -283  blocks/blocks_payee | grep tx_0_vout_1 | wc -l
144
OK, got it :)

Maybe a chart like below is more convenient to get the actual ratio / percentage?
 

jpr

Active Member
May 11, 2014
493
393
133
Is the whole process of asking all the pools to update is a one-time thing? Or is it going to start again after RC4 update?
 

flare

Grizzled Member
May 18, 2014
2,286
2,404
1,183
Germany
Is the whole process of asking all the pools to update is a one-time thing? Or is it going to start again after RC4 update?
50:50 :-D

The pool need to do two things:

1) update their stratum code to pay 20% to MNs
2) update their wallet to stay on the correct blockchain

#1 is a one time action for now, and only necessary if Evan ever changes the MN payout ratio (10% or 25%)

#2 is usual wallet maintenance for the pool owner. If they don't update to RC4, they will not be able to mine.
 
  • Like
Reactions: mattmct and jpr

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
Is the whole process of asking all the pools to update is a one-time thing? Or is it going to start again after RC4 update?
Well currently the masternode payments are voluntary. But as soon as enforcement is switched on, all the pools which did not update will fork off and get orphaned by the main network (currently >75% are paying).
 
  • Like
Reactions: flare and jpr

jpr

Active Member
May 11, 2014
493
393
133
Well currently the masternode payments are voluntary. But as soon as enforcement is switched on, all the pools which did not update will fork off and get orphaned by the main network (currently >75% are paying).
Yes, but the enforcement will not be switched on until most of them update :) How many % we need? 90?