ethminer-0.9.41-genoil-1.1

[Genoil]

1.1.7 is out. Adds support for pools using eth-proxy-style stratum. Main reason to support it is because of the upcoming choice between soft-fork or not. Supporting more pools will allow users to choose between more pools that choose the path they support, without having to change to a different mining client.

Removed flags:
-SV (replaced by -SC)
-ES (superseded by -SP)

Added flags
-SC [n] Where n is 1 (async, default) or 2 (sync) stratum client. async uses a bit more CPU but has working --work-timeout, wheras sync client doesn't have that (yet).
-SP [n] Where n is 0 (stratum, default), 1 (eth-proxy) or 2 (nicehash). Stratum protocol to use.
-SE [e] Where e is email address. Used by eth-proxy. In some pools (like nano) you can also add it to the worker name using /.

Example dwarfpool:

ethminer.exe -U -S eth-eu.dwarfpool.com:8008 -SP 1 -O 0xeb9310b185455f863f526dab3d245809f6854b4d.worker -SE genoil@hotmail.com

https://github.com/Genoil/cpp-ethereum/tree/110/releases

Yes it could still have bugs, tested major pools (dwarf, f2, nano) with success, but something may have slipped through. Thanks for testing!

Using your chunky V1.0.7. The only version which works with my two ancient HD 6950. Slow and inconsistent but it works. Thank you.

Cool, thx . How big is the DAG these days? This chunky 1.0.7 was really just a sketch to test chunking, if I remember well, it should break after the DAG hits 1.5GB. Also, it is possible to make it faster by using bigger chunks. But that's not configurable in 1.0.7-chunky...

[vm_mpn]

I think it's around 1.3GB if I remember correctly... My both HD 6950 are 2 GB cards but seem to have hard-set max buffer size limit of 512 MB I could not extend with SETX command. I was amazed your chunky miner actually worked. Good job :-)

[clintar2]

1.1.7 is out. Adds support for pools using eth-proxy-style stratum. Main reason to support it is because of the upcoming choice between soft-fork or not. Supporting more pools will allow users to choose between more pools that choose the path they support, without having to change to a different mining client.

Removed flags:
-SV (replaced by -SC)
-ES (superseded by -SP)

Added flags
-SC [n] Where n is 1 (async, default) or 2 (sync) stratum client. async uses a bit more CPU but has working --work-timeout, wheras sync client doesn't have that (yet).
-SP [n] Where n is 0 (stratum, default), 1 (eth-proxy) or 2 (nicehash). Stratum protocol to use.
-SE [e] Where e is email address. Used by eth-proxy. In some pools (like nano) you can also add it to the worker name using /.

Example dwarfpool:

ethminer.exe -U -S eth-eu.dwarfpool.com:8008 -SP 1 -O 0xeb9310b185455f863f526dab3d245809f6854b4d.worker -SE genoil@hotmail.com

https://github.com/Genoil/cpp-ethereum/tree/110/releases

Yes it could still have bugs, tested major pools (dwarf, f2, nano) with success, but something may have slipped through. Thanks for testing!

Using your chunky V1.0.7. The only version which works with my two ancient HD 6950. Slow and inconsistent but it works. Thank you.

Cool, thx . How big is the DAG these days? This chunky 1.0.7 was really just a sketch to test chunking, if I remember well, it should break after the DAG hits 1.5GB. Also, it is possible to make it faster by using bigger chunks. But that's not configurable in 1.0.7-chunky...

How would I be able to build the equivalent for linux?

[Genoil]

I'll see if I can do a chunky 1.0.8 or perhaps even 1.1 with 3 or 4 x 512MB chunks.

I like making old stuff work 

[clintar2]

I'll see if I can do a chunky 1.0.8 or perhaps even 1.1 with 3 or 4 x 512MB chunks.

I like making old stuff work 

Cool, and thanks for the other stratum protocol support. That's awesome!

[jdc4429]

I've been getting this error now for the past week with 1.1.3 and 1.1.6 , it occurs randomly between 6-48 hours after starting the miner.

  m  09:02:48|main  Mining on PoWhash #5b2a9aa9 : 15.71MH/s [A124+0:R0+0:F0]
  m  09:02:50|main  Mining on PoWhash #5b2a9aa9 : 14.67MH/s [A124+0:R0+0:F0]
CUDA error in func 'ethash_cuda_miner::search' at line 346 : an illegal memory a
ccess was encountered.
  X  09:02:52|cudaminer0  Error CUDA mining: an illegal memory access was encoun
tered
  m  09:02:52|main  Mining on PoWhash #5b2a9aa9 : 10.48MH/s [A124+0:R0+0:F0]
  m  09:02:54|main  Mining on PoWhash #5b2a9aa9 : 0.00MH/s [A124+0:R0+0:F0]
  i  09:02:55|stratum  Received new job #b7cdf5ca

After that it just hangs and won't do anything until i stop and restart the miner. This is on Windows 8

Any idea what's causing this?
Memory allocation related? Too much OC? Is the card starting to fail? Is some other software interefering with the miner or miner code reelated?

Been having the same issue.. Miner just freezes after 2 or more hours.  Unable to Ctrl-C out of the window and forced to close. 
Been working on a script to email me when it goes down (Ethminer or Geth) and possibly reboot because this is becoming such an issue... One good thing about using a pool is the notifications. Also see issues with Geth when you lose internet it does not seem to reconnect requiring a restart as well...  Mining is so much fun. lol

Same.  Have you tried switching back to 1.0.8?

Happens on both versions for me.. This is not new with 1.1.x
Running R9 290x's...

[crazyearner]

I'll see if I can do a chunky 1.0.8 or perhaps even 1.1 with 3 or 4 x 512MB chunks.

I like making old stuff work 

I have a question regarding old stuff I have a GPU that is 2GB ram x2 dual gpu in one when using mine reads as 2x gpus and read at 1024 GB ram per cpu. Am guessing this will no longer work due to DAG filesize now?

[McNulty]

1.1.7 is out. Adds support for pools using eth-proxy-style stratum. Main reason to support it is because of the upcoming choice between soft-fork or not. Supporting more pools will allow users to choose between more pools that choose the path they support, without having to change to a different mining client.

Removed flags:
-SV (replaced by -SC)
-ES (superseded by -SP)

Added flags
-SC [n] Where n is 1 (async, default) or 2 (sync) stratum client. async uses a bit more CPU but has working --work-timeout, wheras sync client doesn't have that (yet).
-SP [n] Where n is 0 (stratum, default), 1 (eth-proxy) or 2 (nicehash). Stratum protocol to use.
-SE [e] Where e is email address. Used by eth-proxy. In some pools (like nano) you can also add it to the worker name using /.

Example dwarfpool:

ethminer.exe -U -S eth-eu.dwarfpool.com:8008 -SP 1 -O 0xeb9310b185455f863f526dab3d245809f6854b4d.worker -SE genoil@hotmail.com

https://github.com/Genoil/cpp-ethereum/tree/110/releases

Yes it could still have bugs, tested major pools (dwarf, f2, nano) with success, but something may have slipped through. Thanks for testing!

is it possible to use a primary pool with stratum and a failover pool with ethproxy ?  (ethermine + dwarfpool for example)

[BitcoinSuisseAG]

Alpereum
www.Alpereum.ch

Swiss Crypto Mining & Mining Pools

Stratum V2 Support for Ethminer-Genoil Added!

Our unique stratum code supports both Stratum V1 & V2 on the same ports, no need to set anything special. Both V2 from Ethminer-Genoil or V1 from Eth-Proxy will work on the same port!!!

Use the following example code below to mine using Stratum V2 on our pool:

AMD

Code:

ethminer -G -SV 2 -S pool.alpereum.ch:3001 -O 0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359.WorkerName

Nvidia

Code:

ethminer -U -SV 2 -S pool.alpereum.ch:3001 -O 0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359.WorkerName

Locations:

Pool.Alpereum.ch - Europe
USA.Alpereum.ch - North America
Asia.Alpereum.ch - Asia

Multiple Static Diff Ports:
3000 - 500 Million Diff
3001 - 1 Billion Diff
3002 - 2 Billion Diff
3003 - 3 Billion Diff
3004 - 4 Billion Diff
3005 - 5 Billion Diff
3006 - 6 Billion Diff
3007 - 7 Billion Diff
3008 - 8 Billion Diff
3009 - 9 Billion Diff
3010 - 10 Billion Diff

[Dev_Sempak_coin]

anyone can help me ?
trying to delete dag and running genoil but i get this problem
i have tried re-instal driver but i get same problem.

[adamvp]

Alpereum
www.Alpereum.ch

Swiss Crypto Mining & Mining Pools

Stratum V2 Support for Ethminer-Genoil Added!

Our unique stratum code supports both Stratum V1 & V2 on the same ports, no need to set anything special. Both V2 from Ethminer-Genoil or V1 from Eth-Proxy will work on the same port!!!

Use the following example code below to mine using Stratum V2 on our pool:

AMD

Code:

ethminer -G -SV 2 -S pool.alpereum.ch:3001 -O 0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359.WorkerName

Nvidia

Code:

ethminer -U -SV 2 -S pool.alpereum.ch:3001 -O 0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359.WorkerName

Locations:

Pool.Alpereum.ch - Europe
USA.Alpereum.ch - North America
Asia.Alpereum.ch - Asia

Multiple Static Diff Ports:
3000 - 500 Million Diff
3001 - 1 Billion Diff
3002 - 2 Billion Diff
3003 - 3 Billion Diff
3004 - 4 Billion Diff
3005 - 5 Billion Diff
3006 - 6 Billion Diff
3007 - 7 Billion Diff
3008 - 8 Billion Diff
3009 - 9 Billion Diff
3010 - 10 Billion Diff

Hello,  flags changed a Little  in  new version

It should be - SC instead of SV now

[Termie]

noob question - what is the sense of these static diff ports?
Which one is recommended for ~88-90 MH/s?

[Dev_Sempak_coin]

noob question - what is the sense of these static diff ports?
Which one is recommended for ~88-90 MH/s?

i recomended dwarfpool im use it too.

[Termie]

I don´t ask for a pool, but for several diff ports of Alpereum.

[Genoil]

Can anybody with a 1080 or 1070 and Win10 try to get 368.20 drivers running? They are installed by Windows Update and may require a Windows Insider subscription. When running dxdiag with 368.20, WDDM version is upgraded from 2.0 to 2.1. No TLB fix for my 970, but it may solve the issue on Pascal cards.

[adamvp]

noob question - what is the sense of these static diff ports?
Which one is recommended for ~88-90 MH/s?

lower hashrate = lower diff

I am curious which diff is recomended, too..

[BitcoinSuisseAG]

noob question - what is the sense of these static diff ports?
Which one is recommended for ~88-90 MH/s?

You should utilize port 3001, 1 Billion Difficulty.


Port 3000 is useful for lower hashrate miners, such as those mining on a single GPU.

Port 3001 is the recommended port currently if you are not sure, especially since a majority of purpose built mining rigs are around the 80-150 MH/s mark currently. Even if you have several workers, they are still separate miners.

Port 3002 can be utilized as well, it is set at 2 billion difficulty and is a standard at other pools.

Further ports are meant for users that are renting hashrate, where all the workers are funneled through one proxy and appear as one worker. Also users that are utilizing Sammy007's proxy etc.

Generally speaking, multiple static diff ports was previously a taboo thing for an Ethereum pool to do. Before we investigated and fixed the issue, malicious miners used to be able to submit the same block header hash across multiple ports to scam an unsuspecting pool. Our development team figured out a way to patch this to permanently prevent that from happening.


We also currently have an experimental version of Variable Difficulty (VARDIFF) we are working on. We had to re-invent the way VARDIFF works for Ethereum. It cannot be compared to a Bitcoin/Bitcoin Clone type of pool that utilizes VARDIFF. The current VARDIFF system will re-target your miner every 10 minutes, trying to find the perfect difficulty so that you are submitting a share every 10 seconds. It may take a few hours until that diff point is found, and currently if you disconnect or timeout (30 minutes) you will have to start over again. That is why we offer several different starting difficulty points for VARDIFF.

Variable Difficulty is still in experimental/testing stages. Use at your own risk.


VARDIFF Ports:
4000 - 300 Million Starting Diff
4001 - 1 Billion Starting Diff
4003 - 3 Billion Starting Diff
4005 - 5 Billion Starting DIff

[davembg]

Is there a specification for Eth Stratum v2? Currently my SGMiner port only works with getwork, and it does NOT work well at low diff.

Try DonkeyPool - min diff is 1.5 Bill and fluctuates so all miners share submit average is equal to the average ETH blocktime.
That's what stratum is suppose to do, right?

There are now (3) stratum options (thanks to NiceHash).
They each have differing opinions on how to deliver getWork from the wallet without polling a websocket.

DonkeyPool supports the Coinotron spec, which makes the most sense.
Why use a proxy? all miners now support some type of stratum.

DonkeyPool still has getWork support, but only until June 30.
Then it's all stratum(ish) support.

DonkeyPool getwork string would be address: / workername / hashrate integer value

eg
www.donkeypool.com/0xaaaadddreeesss/worker/10

[davembg]

Is there a specification for Eth Stratum v2? Currently my SGMiner port only works with getwork, and it does NOT work well at low diff.

Try DonkeyPool - min diff is 1.5 Bill and fluctuates so all miners share submit average is equal to the average ETH blocktime.
That's what stratum is suppose to do, right?

There are now (3) stratum options (thanks to NiceHash).
They each have differing opinions on how to deliver getWork from the wallet without polling a websocket.

DonkeyPool supports the Coinotron spec, which makes the most sense.
Why use a proxy? all miners now support some type of stratum.

DonkeyPool still has getWork support, but only until June 30.
Then it's all stratum(ish) support.

DonkeyPool getwork string would be address: / workername / hashrate integer value

eg
www.donkeypool.com/0xaaaadddreeesss/worker/10

No, Stratum is a lot better, which is why I'd rather SGMiner use it than getwork. But fucking NiceHash had to reinvent the wheel (again) - are there actual specs for any of these stratum versions? Specifically 2 and 3?

Stratum is marginally better - for pools.
It's easier to administrate - but keeping a socket open has essentially the same footprint as 2 requests to nginx per second, per miner.
There is no spec, only code.
NiceHash's document is outdated and I haven't found it to be accurate.
Maybe they just haven't updated.

[davembg]

Is there a specification for Eth Stratum v2? Currently my SGMiner port only works with getwork, and it does NOT work well at low diff.

Try DonkeyPool - min diff is 1.5 Bill and fluctuates so all miners share submit average is equal to the average ETH blocktime.
That's what stratum is suppose to do, right?

There are now (3) stratum options (thanks to NiceHash).
They each have differing opinions on how to deliver getWork from the wallet without polling a websocket.

DonkeyPool supports the Coinotron spec, which makes the most sense.
Why use a proxy? all miners now support some type of stratum.

DonkeyPool still has getWork support, but only until June 30.
Then it's all stratum(ish) support.

DonkeyPool getwork string would be address: / workername / hashrate integer value

eg
www.donkeypool.com/0xaaaadddreeesss/worker/10

No, Stratum is a lot better, which is why I'd rather SGMiner use it than getwork. But fucking NiceHash had to reinvent the wheel (again) - are there actual specs for any of these stratum versions? Specifically 2 and 3?

Stratum is marginally better - for pools.
It's easier to administrate - but keeping a socket open has essentially the same footprint as 2 requests to nginx per second, per miner.
There is no spec, only code.
NiceHash's document is outdated and I haven't found it to be accurate.
Maybe they just haven't updated.

Not just better for pools - you can find two shares in a row, and submit both with Stratum. With shitty Eth getwork, it forces new work every submit.

Not true with DonkeyPool.
Nnginx sits between the wallet and proxies eth_submitWork.

The getWork params only change when there's a blockchange, as it should be.