Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[DStefanov]

v9.1:

- additional range checks in code for better stability.
- reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection, currently Flypool and Suprnova pools support encrypted connections, see Readme for samples.
- improved "-di detect" option: now after GPU order detection miner starts mining with the detected order.
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

Much better!  More stable so far - 30 minutes with no issues.  I also like the decreased devfee. 

Thanks Claymore!

+11111

I think the same!

[1714484319]

1714484319

[1714484319]

1714484319

[1714484319]

1714484319

[1714484319]

1714484319

[1714484319]

1714484319

[issie81]

Ok, you miners can't read:

 reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection

After using the SSL/TLS, the share rejection is 1.0 to 1.5% now. The rejection rate was 0.3 to 0.5 previously.

so the 2.5% is then more profitable?
since you lose around 1%?

[henz46]

Are f2pool can using ssl?

[vapourminer]

Ok, you miners can't read:

 reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection

After using the SSL/TLS, the share rejection is 1.0 to 1.5% now. The rejection rate was 0.3 to 0.5 previously.

my reject rate, with ssl, is 0.71% and 0.83% on my two rigs. more or less what it was before.

[rpg]

Ok, you miners can't read:

 reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection

After using the SSL/TLS, the share rejection is 1.0 to 1.5% now. The rejection rate was 0.3 to 0.5 previously.

my reject rate, with ssl, is 0.71% and 0.83% on my two rigs. more or less what it was before.

People don't understand that a rejected share is one that cross with a new job somewhere along the way. If the pool is slow processing incoming shares you also may get a reject. My rejects were around 1% at flypool going as high as 3% with timeouts that are frequent there. On the other end at dwarf the reject rate is 0.2%. So before blaming the miner you should be blaming the pool

[Gagana]

v9.1:

- additional range checks in code for better stability.
- reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection, currently Flypool and Suprnova pools support encrypted connections, see Readme for samples.
- improved "-di detect" option: now after GPU order detection miner starts mining with the detected order.
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

Great! Thanks!

[Raja_MBZ]

I don't think so that there is any need for the fee reduction, 2.5% is pretty much fine. I'll continue to use the non-encrypted connection and provide you a bit more fee, you deserve it.

[xeridea]

Ok, you miners can't read:

 reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection

After using the SSL/TLS, the share rejection is 1.0 to 1.5% now. The rejection rate was 0.3 to 0.5 previously.

my reject rate, with ssl, is 0.71% and 0.83% on my two rigs. more or less what it was before.

People don't understand that a rejected share is one that cross with a new job somewhere along the way. If the pool is slow processing incoming shares you also may get a reject. My rejects were around 1% at flypool going as high as 3% with timeouts that are frequent there. On the other end at dwarf the reject rate is 0.2%. So before blaming the miner you should be blaming the pool

My stale rate on suprnova went from ~0.25% before to 0.3% to 0.5% with SSL (Not running for long, need more time to get better number).  My response time went from 62ms to 140ms, due to not being on the US server anymore.  Before when on non US server response was ~125ms.  The increased stalerate seems roughly correlated with server response time, mining from US to Europe. Pool will probably add another SSH server in future.  I could also reduce my ping by ~30ms switching to gigabit fiber from the Comcast I have right now.....

Server response time would effect Ethereum a lot more, due to 10x faster blocktime.

[GabryRox]

Claymore should not mind peoples who do not know how to power their cards,
My rx480 cards can be powered 400W each safely (i even build own modular cables), my rig can work stable till 2,5kW (now using 760W), i am prepared for any algo with overclocking

ummm... dare I say that this seems like a huge waste of headroom?  Yes, I understand that it is ideal to have a max load of about 25% less than your PSU's wattage rating, but you indicate that your system has 70% headroom.  Not sure how you can ever ROI a system that includes excessive costs from idle PSU wattage capabilities, but you're right lol... you are certainly prepared to max out those 480's  

[smaxz]

Are f2pool can using ssl?

dont think f2pool stands for that kind of stuff.. kind of a no frills pool but cant hurt to bring up as a feature request in their thread.. its one of the main bitcoin pools so their thread is in the bitcoin mining section.

i would bring it up but i post there far too often as it stands.

[rpg]

Did I ever mention that I'm mining via thethering on a oneplus2? 

[Bojcha]

v9.1:

Timeout for new job should be increased from 10 to atleast 15minutes.

[giagge]

Anyone try new AMD driver RELIVE ? work ? more performance or minor consuption ? .

[Za1n]

Claymore should not mind peoples who do not know how to power their cards,
My rx480 cards can be powered 400W each safely (i even build own modular cables), my rig can work stable till 2,5kW (now using 760W), i am prepared for any algo with overclocking

ummm... dare I say that this seems like a huge waste of headroom?  Yes, I understand that it is ideal to have a max load of about 25% less than your PSU's wattage rating, but you indicate that your system has 70% headroom.  Not sure how you can ever ROI a system that includes excessive costs from idle PSU wattage capabilities, but you're right lol... you are certainly prepared to max out those 480's  

He is probably using a server PSU with an adapter board to break out the connections into a usable configuration. This is actually a pretty typical configuration and the server PSU's can be bought for little to nothing ($20-$50) depending on efficiency and capacity. Running at 240V inputs, a 2,000W-2,900W capacity server PSU is not that uncommon and readily available on places like eBay and Amazon.

[YIz]

Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

[ffthomas]

Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here..  

[EvilC0P]

Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here..  

v9 and v9.1 runs perfectly for me since release. and i overclock my rx 480 with afterburner.
2 cards running in Win7 and 4 cards in Win10.

[sorry2xs]

Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here.. 

v9 and v9.1 runs perfectly for me since release. and i overclock my rx 480 with afterburner.
2 cards running in Win7 and 4 cards in Win10.

+1

[mettalmag]

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?

[ober]

Anyone try new AMD driver RELIVE ? work ? more performance or minor consuption ? .

AMD RE? No way

Installed it on my test rig, REgot that code error43 again, that thing of the past RElives again. RErun AMD clenup utility, that 500MB package still lives in my drive. DIdn't bother DDU, REformat, dd *.img