pool.ccminer.net:8080 new pool for big miners!!!
-
@ZapbuzZ About the same - it'd be less than a 10% reduction on the DL target.
-
no problems then :)
-
@ccminer I guess I don't have an issue either, anything to keep the pool super responsive. I'm guessing the only thing a shorter DL time is gonna hurt is shares sent from miners and their reward for a pool won block which in a sense would mean the block winner getting just a bit more of the pie of a win. Most block wins are extremely fast times anyways which means the winner gets more than likely 90%+ of the pot, prolly more than that and other DL times are usually only worth a few coins here and there. Obviously there are exceptions like the 10+ minute wins were other miners get more reward for subpar DL times. But those are the blocks where I think smaller miners pick up their rewards. I'm slowly increasing my farm from 57tbs to close to 100tbs so hopefully my times will get better.
Just my 2 cents...
-
@Garbear My point is just to keep the pool as more responsive as possible.
from 24 hours DL to 22 Hours the difference in the reward will be practically nothing but we can save several nonces from being submitted and keep the target <50 nonces processed per block
-
@ccminer said in pool.ccminer.net:8080 new pool for big miners!!!:
So I suggest to lower the DL limit to 22 hours and to keep lowering to 2 hours every time the pool surpass the 50 nonces limit!
I am happy with this as a plan, however at the moment I am only seeing 25 to 30 nonces on most Blocks with the initial rush being less than this. It then sometimes creeps up to 50 with the larger plots but I do not see this as a problem, so for the moment I think we are fine.
You need to get the balance right between responsiveness and driving the "smaller" Miners away.
We are hitting a very good number of blocks at the moment and retaining the number 1 slot.
Although it is only a small thing I would consider reducing the fee to 0.5% to match what ninja is planning.
I for the moment am uncertain about the v3 code, and will not be trying it until some more bugs are worked out and the developers share more about the changes and details of the configuration parameters.
Rich
-
@RichBC Yeah now less nonces are submitted, I'll keep checking on it
-
DL reduced to 22 hours folks since 2 days already, I forgot to write here before
-
Just forget a 23 minutes block!!
I know that long time blocks give you less in pool, but every time I get such a long DL block I feel a better satisfaction!
-
@ccminer It's been a while since I've seen a DL that long, but I see I got a 13 minute one just before yours. Did a whole lot of mining capacity just fall off the network ?
-
@haitch this morning my time I saw 60 000 as network difficulty (very high)
Now it is drop to 32 000
-
@haitch could it be a prelude to a 51% attack on the network?
-
@iKnow0 I don't think so. I think the very high difficulty was either:
- A false calculation by the network due to a series of really short winning DL's, or
- There is a huge private pool out there that went offline.
-
seems to be misbehaving goes through rounds then seems to become unresponsive could that be blocks?
-
-
@ccminer It doesn't seem to be dropping blocks, so most likely an issue with the proxy - probably DoS. How the pool doesn't seem to be missing blocks, so it doesn't seem to be impacting mining
-
i see your point of view however it seemed that the miner was unable to reach the pool between rounds but worked when new rounds started. As soon as i posted it went back to normal like 30 minutes later or so. @ccminer @Haitch thanks for checking.
-
@haitch do you get this message in between the running pool code. I still can't shake it.
{ [Error: socket hang up] code: 'ECONNRESET' }
-
@Burstde No, I don't get that. Check you ports
-
@haitch the only port not open is 443
-
@Burstde To the best of my knowledge none of the pools are on 443 - wallets are ssl encrypted, but pools aren't.

