Quote from: mdude77 on March 27, 2014, 11:37:42 PM

Quote from: BorisTheSpider on March 27, 2014, 11:06:42 PM

BTW while we're on the subject, can some of you check out http://www.reddit.com/r/vertcoin/comments/21imwo/consider_mining_on_2nd_p2pool_network_to_allow/ - it is for those of you with lower hashrate who were finding p2pool difficult to find shares on in time to get them counted in a block, and should drastically improve things. Please don't move over if you're a bigger hasher - it would be best to get a lot of smaller hashers on p2pool2 to get them to a workable mix of blockrate and sharerate.

Can you define small and big?

M

At current stage, any miner is welcome as we need to get 'time to block' to reasonable value (lets say 100Mhs for now).

Which network is better for particular miner is not exact, depends on how much variance you like. Typically, it's ideal if 'time to share' < 'time to block' for particular miner, assuming that pool has at least 2 hours to block.

What we are missing now badly is node scanner to inform people about second network.

Also, second network can grow very quickly if at least one big node from first network switches to second. And this helps to both networks, second gains needed hashrate whilst first lower share difficulty without impacting time to block much. Also without changing worker port, this can be done almost instantly. For miners this is also no problem as shares gained in first network will be awarded by rest of network. But I'm afraid pool operators have no reason to do it as this could lead to miners leaving if they don't like this move. At the opposite side, there are many angry miners mining on p2pool and getting nothing, which can be attracted.

I'm also curious about specifiing second network as low hashrate network. Yes, it is for now. But as there is no way how to enforce which network particular miners will join. One time second network can become bigger than first. Lets rather say 1st and 2nd network and educate miners about time to block/time to share consequences on p2pool.