at day 13 hour 23:40 prev session
[MMP] made 2016 key:hash associated to block2008 to be used as nest session block maker keys
[HM]and all the [AJ's] have 1 key/hash associated to block 2008.. [AJ] is too low. [HM] has one super strong
I believe no as [HM] would have more than one as no one said that you as an HM should stop mining when you found one good enough hash. So no point splitting your hashrate as one private key can have more than one blocks or you can create separated PK for all blocks you intend to mine.
Because of this a proof hash's accumulated and listed in the proof block would be distributed by hashrate. If your hashrate is too low [AJ] you should join a pool as happens today.
Because of this there is no reason to withhold as hashes will be coming relatively quick, so if you don't create a proof block as fast as possible someone else will and that will be the block => you lost.
i said HM will have 1
you said 'no as [HM] would have more then one' but then you explained it by saying no one said [hm] should stop when getting a 'good enough' hash..
.. weird explanation.. because by your suggestion.. not stopping means continuing 1 hash but even stronger
.. you then said no point splitting hashrate.. meanign you also suggest not working on second hash
meaning you ended up explaining yourself into a scenario where [hm] does infact end up with 1 key:hash proof of block 2008
(you talked yourself into agreeing with what my scenario suggested in the first place)
sooo.. going with my first scenario suggestion of [hm] sticking with one key:hash proof of block 2008 that is super strong. rather than splitting his hash for multiple attempts of the 1hour 2008 proof of weaker key:hash
as you then say the special 'proof block' lists 2016 key:hash by hashrate.
so knowing [MMP] has been making 2016key:hash
[mmp] gets more listings in the special block and [hm] only has 1 chance
..
then when forming the special block.
[hm] templates his own list 1key. and his preferred 2016 keys he has had relayed to him from competitors
and he makes his own attempt at special block
[mmp] template ignoring competitors relayed to them.. and just list their own 2016 keys, meeting min diff.
and they pool mine [mmp1to8] and make their own special block with more combined hash than [hm]
thus [mmp] win as they done most work on the special block
thus their listed preferred key:hash of 2016 keys get to be the PoS signers for the next fortnight
and now mmp can do their own gaming of the system in secret.
..
again for a reminder all the 2016 keys of the next session of the winning special block are [mmp] managed
meaning only their listed keys can make blocks.
this opens up 2 attacks
1. PoS mine all blocks in 7 hours secretly. broadcast publicly at prescribed times
2. because they're the only miners allowed to mine for next fortnight.. they can just all NOT broadcast anything for whole fortnight
(yes 2 means loss of reward revenue due to not making blocks to have rewards)
but its still a stall event for a fortnight