Prohashing Mining Pool Forums

You definitely want to enable submission of stale shares.

cgminer and other mining software detects stale shares based upon whether the primary block is stale. However, the merge mined blocks may not be stale.

If you set the mining software to ignore stale shares, you waste money. You still get paid for the merge mined blocks that are valid when you submit stale shares, which is often 10% of the total earnings. If your miner throws away 5% in "stale" shares, and this were the only factor, then you are already wasting 0.5% of your profit.

Additionally, some miners consider a share "stale" when a new job is sent. Many times, a new job is sent because there is a more profitable coin, not because a new block was found on the old coin. In this case, the old share will be fully paid, not just for the merge mining earnings. If you are configured to not submit shares for this, and your work restart time is low, you could be incurring huge losses, of 10% or 20%.

Hi All,

Thought about starting a thread for us Titan miners last week but was busy.

This is a PPS pool, you want to submit your stales too.

I use #skipcbcheck#xnsub without an issue.

Right now (last 15+ days) I have D=8192 (password) scantime=1 Expiry=30 Queue=10 and Retries=-1 (in bfg)

I used to have expiry=1 and queue=0 (I think it was recommended by nicehash pool for Titans) but changed it a while ago when I thought it is causing an issue, but it was something on the pool that the bros changed and changed back later or other issue.
I do have more "pool 0 is issuing work for and old block...." now but it is stable at around 340-350MH/s with very low rejected shares.

Should I go back to my old settings? expiry=1 and queue=0? Should we use D=16384?

Thanks and best of luck to all.
ZX

ok, thank you .. i'll try this conf.

Hi All,

Just in case someone wonders about the difficulty settings for Titan, been running my Titan (OCd to 340+MHs) with d=16384 for the past week and I don't see any difference in hashing speed or payout vs 8192.

GL to all.
ZX

Just for the record, mine have been set at 16384 since the first few days mining here. That's what the dynamic setting kept going to, so I figured there might be some slight benefit to manually setting it instead of letting the system use the resources to figure it out.

I actually set mine to d=4096 even though the pool would set it to 16384 if I let it handle it. My main reason for this was when we were mining many coins with <1 difficulty, I would not get any shares submitted over the course of a dozen rapid coin changes. Setting it to 4096 let me sneak in a bunch more shares and find more low diff blocks for the pool. It also resulted in a smoother hash rate chart with smaller peaks and valleys. Overall I kept the same average hash rate because I was getting more small shares accepted, but not getting as much credit during the long runs of litecoin mining.

For me 4 days and 20:14:51 hours of mining at prohashing with 8192 diff and 0.13% rejected .. av 326 Mh/s it's nice !

Best Regards