Knc Titan rejection rate

[wolverine5pl]

Hi there
Can anyone help with settings for titan?
I get around 5-10% rejections with following setting:


{
"pools": [
{
"url": "stratum+tcp://prohashing.com:3333/#xnsub#skipcbcheck",
"user": "USERNAME",
"pass": "x"
}
],
"scrypt-n": 10,
"failover-only": true,
"no-submit-stale": true
}

[Steve Sokolowski]

Kires, you there? You would probably know better than I do.

[kires]

Morning, guys.

Here's my config file:

Code: Select all

{
  "pools": [
    {
      "url": "stratum+tcp://prohashing.com:3333/#skipcbcheck",
      "user": "kires",
      "pass": "n=Titan_1 d=16384"
    },
    {
      "url": "stratum+tcp://multi.ghash.io:3333",
      "user": "Kires.Titan01",
      "pass": "x"
    },
    {
      "url": "stratum+tcp://ltc.ghash.io:3333",
      "user": "Kires.Titan01",
      "pass": "x"
    }
  ],
  "no-submit-stale": false,
  "scrypt-n": 10,
  "failover-only": true
}

The only real differences I see are the difficulty, the xnsub, and the no-submit stale. The no submit stale is lowering your effective hashrate a bit, but I don't think it's increasing your rejects, at least not server side. FWIW, I notice that while my reject rate is usually around 0-1 percent, every now and then it will increase for a bit, sometimes as high as the 5 or 10 percent you've reported, and then calm back down. Are you seeing the rejects client or server-side, and are they being sustained over a period of more than an hour or so?

[Steve Sokolowski]

kires, what is the reason you get for the 5-10% rejects? Messages could be "stale share," "incorrect algorithm," or so on. Which one is it? And, are you referring to here or to some other pool?

[tucsondirect]

get rid of, #xnsub the pool does not currently implement extranonce

[kires]

Apologies, Steve. I don't have that information, although I think they get called stale. It's been a few days since I saw my reject rates go above a whole percent, so my confidence in that answer is not high. I'll keep an eye out, and let you know if/when it happens again. And I was referring to my reject rate here; it's much higher when they fail over to ghash.

[wolverine5pl]

after all day running 11% rejects. will try your settings kires. thanks for help

after running it for a while rejects much lower around 1%. Big thanks for help

[dexubdg]

for pool use this stratum+tcp://pooladdrs:3333/#skipcbcheck#xnsub
for password use r=60 d=8192

in bfgminer config
"scrypt-n": 10,
"failover-only": true,
"no-submit-stale": true

in bfgminer use

[S]cantime: 1

and you're done

my reject rate after 24h is 1 - 1,2 %

Best Regards

[tucsondirect]

don't include "#xnsub" as it has not been implemented yet(at prohashing).... this will cause rejects and weirdness on the knc

[peck0081]

for pool use this stratum+tcp://pooladdrs:3333/#skipcbcheck#xnsub
for password use r=60 d=8192

in bfgminer config
"scrypt-n": 10,
"failover-only": true,
"no-submit-stale": true

in bfgminer use

[S]cantime: 1

and you're done

my reject rate after 24h is 1 - 1,2 %

Best Regards

Won't using r=60 in the password field prevent you from mining any of the very low diff coins since you are telling the pool that it takes you 60 seconds to start on new work? I let the pool determine mine and it ends up being 0.6s-1.5s.

I also set the [S]cantime manually to 1 every time I restart my miner which helps in switching between those low diff coins. You can add it in "Manual edit mode" but that setting never seems to stick between restarts.

For no-submit-stale, I go with the pool's recommendation which lets the pool reject it if it's stale instead of you automatically considering it stale which is based on [E]xpiry I think.

ProHashing Help:
Submit stale shares
Prohashing pays miners for suboptimal shares. Ensure that your miner submits stale shares to the pool, which may not be the default configuration of your version of BFGminer. Make sure that your configuration does not include the --no-submit-stale argument.

FYI, I'm on firmware titan 2.00 and see reject rates of around 0.1%