Quote from: slapper on July 13, 2014, 12:55:45 PM

Quote from: vertoe on July 13, 2014, 12:42:00 PM

Quote from: DogTheHunter on July 13, 2014, 10:40:35 AM

Quote from: eltito on July 13, 2014, 04:51:19 AM

Quote from: camosoul on July 13, 2014, 04:12:45 AM

Quote from: newb4now on July 13, 2014, 04:11:57 AM

How is the dev team going to respond if some of these pools decide to never update? I think some of them are choosing to not pay masternodes on purpose

Orphan all their blocks. Has been the plan all month...

^^ What he said. Hunting down non-paying pools is a stop-gap measure while we await the implementation of code which will force pools to comply or render the blocks they find useless. This is generally what people in this thread are referring to when they talk about "enforcement" (though enforcement can refer to any feature in a broader context).

So enforcement doesn't ban pools, the network just won't accept their blocks if they haven't paid a master node when a block is submitted?

Yes.

It's currently only one big pool which did not update. The rest can be considered as dust.

Last 24h - Pool / Blocks:
- x11.ltc1btc.com 122
- ghash.io 6
- darkcoin.cryptocurrency.tw 5
- nicehash.com 4
- dark.v2.dedicatedpool.com 3
- dark.hashrate.eu 0

Yah ltc1btc complying would mean >98% overall. They are knowingly dodging the update, as Presidente noted yesterday, by trying to change their payout address.

Proveceday's ltc1btc thread https://bitcointalk.org/index.php?topic=627405.0

Last 3 posts are from DRK members asking him to update, but as expected no response from him.

http://wiki.darkcoin.eu/wiki/Important

Well, there is something happening on ltc1btc's end. http://drk.poolhash.org/masternode.html?srch&nmstr=x11ltc1btccom03

One of their subpools has been paying for 6 hours now. Only 10% however. But it seems they're not totally unwilling. Hopefully testing this on one server and then updating the others like multipool.us did.