PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[wtfonly16]

@PhoenixMiner:

you use my GPU kernels in your "fastest" miner, 100% match of binaries. I can prove it if you are not going to confirm it.
So do you confirm it?

I cant confirm if this is true, but Phoenix Miner is genuinely more stable than Claymore and I do get slightly more shares.
I think Claymore is great software but after a certain period mining, 1% fees for solo kinda grates, its extortionate in fact. Consequently, like you say in your readme "if you dont like the fees, dont use it" - I'm doing exactly that.

Thanks for you opinion and for registering on this forum just to say that, you are free to use any miner of course.
I just want the confirmation from the author of this software that he dumped my AMD GPU kernels and uses them in his miner.

how same kernels if pheonixminer is faster?

[P-D-A]

@PhoenixMiner:

you use my GPU kernels in your "fastest" miner, 100% match of binaries. I can prove it if you are not going to confirm it.
So do you confirm it?

I cant confirm if this is true, but Phoenix Miner is genuinely more stable than Claymore and I do get slightly more shares.
I think Claymore is great software but after a certain period mining, 1% fees for solo kinda grates, its extortionate in fact. Consequently, like you say in your readme "if you dont like the fees, dont use it" - I'm doing exactly that.

Thanks for you opinion and for registering on this forum just to say that, you are free to use any miner of course.
I just want the confirmation from the author of this software that he dumped my AMD GPU kernels and uses them in his miner.

how same kernels if pheonixminer is faster?

I completely agree

[JJkod]

claymore's lawsuit incoming... phoenixminer is already out there though, and it's faster.

[pickaxe123]

I've been mining since 2.4, now on 2.7b, on a single Vega 56, W10, latest drivers, and it's been mostly fine. I've only experienced one recurring problem where mining stops (driver crash AFAIK) then restart and hangs at detecting cards for 60-80 minutes before resuming mining. Before 2.7b, my wattman overclock settings were reset to default, now with 2.7b I get to keep my settings which is much better already.

Crash

Code:

17590:09:57:09.365: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17590:09:57:11.118: wdog GPU1 not responding
17590:09:57:11.118: wdog Thread(s) not responding. Restarting.
17590:09:57:13.351: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x67eee33b64b12a758aae121933ceda21975d7f6465e6cd9e2df2564ab35ec43f","0x1261dfe17d0bf58cb2861ae84734488b1463d282b7ee88ccfa18b7a92a7b77f7","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ee526"]}
17590:09:57:13.351: eths Eth: New job #67eee33b from eu1.ethermine.org:4444; diff: 4000MH
17590:09:57:14.343: main Eth speed: 0.000 MH/s, shares: 440/0/0, time: 10:42

First auto restart, failed to generate DAG (GPU might just be down/driver still hasn't recovered fully)

Code:

17590:09:59:10.755: main Phoneix Miner 2.7b Windows/msvc - Release
17590:09:59:10.755: main Cmd line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal xxx.xxx -cdm 0 -amd -fanmin 10 -fanmax 20 -tmax 65 -powlim 50 -cclock 997 -cvddc 935 -mclock 1125 -mvddc 950 -minRigSpeed 39 
17590:09:59:10.844: main Available GPUs for mining:
17590:09:59:10.844: main GPU1: Radeon RX Vega (pcie 3), OpenCL 2.0, 8 GB VRAM, 56 CUs
17590:09:59:10.855: main ADL library initialized
[...]
17590:09:59:11.260: GPU1 GPU1: Starting up... (0)
17590:09:59:11.260: GPU1 Eth: Generating light cache for epoch #172
17590:09:59:11.370: main GPU1: 32C 13%
17590:09:59:16.214: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17590:09:59:19.103: eths Eth: Received: 
[...]
17590:10:00:42.820: wdog GPU1 not responding
17590:10:00:42.820: wdog Thread(s) not responding. Restarting.
17590:10:00:46.823: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01

Second auto restart, where it hangs for an hour+

Code:

17590:10:00:53.931: main Phoneix Miner 2.7b Windows/msvc - Release
17590:10:00:53.931: main Cmd line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal xxx.xxx -cdm 0 -amd -fanmin 10 -fanmax 20 -tmax 65 -powlim 50 -cclock 997 -cvddc 935 -mclock 1125 -mvddc 950 -minRigSpeed 39 
17590:11:12:48.891: main Available GPUs for mining:
17590:11:12:48.891: main GPU1: Radeon RX Vega (pcie 3), OpenCL 2.0, 8 GB VRAM, 56 CUs
17590:11:12:49.049: main ADL library initialized
17590:11:12:49.367: main Eth: the pool list contains 4 pools
17590:11:12:49.367: main Eth: primary pool: eu1.ethermine.org:4444
17590:11:12:49.367: main Starting GPU mining

I've had 60/70 hours longs runs without issue, even while changing clock settings and playing games etc.

I'll gladly help with more logs and more details, feel free to ask

[fr4nkthetank]

wow.  Well im getting the popcorn   You people might want to consider saving a copy before it disappears if you really like the program... such drama much wow

[Claymore]

wow.  Well im getting the popcorn   You people might want to consider saving a copy before it disappears if you really like the program... such drama much wow

No drama and I'm not going to try to remove this miner thread. In fact, this miner is not 100% crack, its author spent some efforts and created own wrapper around my kernels. But people at least must know about the source of GPU kernels that are used here, this guy did not write them.

[P-D-A]

wow.  Well im getting the popcorn   You people might want to consider saving a copy before it disappears if you really like the program... such drama much wow

No drama and I'm not going to try to remove this miner thread. In fact, this miner is not 100% crack, its author spent some efforts and created own wrapper around my kernels. But people at least must know about the source of GPU kernels that are used here, this guy did not write them.

At least the PM did it better than Claymore 11+
And most importantly, he is not greedy like you.
With PM I get a good and stable speed.

[Iamtutut]

And I was amazed how, even when I had a single GPU to mine (30MH/s), claymore was always (and I mean it) finding shares during dev fee. With phoenix, during dev fee, share findings seem much more random.

[osnwt]

Simple: Claymore's dev fee mining uses lower share difficulty than your mining. It connects to the pool which starts from low difficulty shares. Don't simply count them but look at their difficulty.

[blackwhite5674]

@PhoenixMiner:

you use my GPU kernels in your "fastest" miner, 100% match of binaries. I can prove it if you are not going to confirm it.
So do you confirm it?

 Claymore is the OG, the GOAT, the legend...but a lower fee and slightly higher effective hashrate is the appeal here for miners trying to squeeze as much out of their rigs as they can.

Still, I wouldn't be surprised if this was true, and, if so, doesn't affect me at all.

[Branko]

Any reason to NOT use -mi 12, but lower number?

[peterboy1]

Any reason to NOT use -mi 12, but lower number?

we always have that 80% rule. just kidding. but in my opinion, its better not to push everything 100%.

[Bigdrago]

Do this program support OC, undervolt and set a work temp for gpu?

Can we remove devfee?

Too bad if this is a ripoff of Claymore.

[rdluffy]

Do this program support OC, undervolt and set a work temp for gpu?

No devfee?

Too bad if this is a ripoff of Claymore.

It's on first page:

* Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)

[unixm]

Firstly I don't particularly care whether PM are using Claymore kernels.  Correct me if I am wrong, but if 2 miners share the same kernels yet PM is even slightly faster then that says something about Claymore's code?

Claymore obviously feels threatend now there's competition, but competition is a good thing.

If Claymore's miner submits shares at a lower difficulty then that in itself is useful for him.  For example if you have a lower powered rig, perhaps 1 GPU, it's better to switch to his devfee and find any share even at a lower difficulty than it is to switch and find nothing - When the 2nd scenario occurs Claymore esentially misses out in that devfee window to get something from you, but you still lose because of the time it's taking away from mining for you.

I don't trust Claymore's software and I certainly don't like his Dev Fee's.  I suppose the same can be argued for PM, but I'm happier paying a lower dev fee and with a faster miner.

You may argue he's entilted and earned it but let me tell you, if you run a packet sniffer (Wireshark etc) when it switches to Nicehash for him (or any other pool) and look up his address and then check that against Nicehash/pool you will be truly astounded at the money he is pulling in, in BTC alone - And that's just one thing - I cannot even describe the amount of currency he is making from his miners.

I understand developers need to be paid, but when you run his software you are signing up to paying him constantly for the duration of the time you use his miners - And let's face it most people run his miners - And mainly for the reason that it's the most widely used - Most articles & guides reference his miners.  Think about the new people coming into crypto mining who are just reading guides on how to set-up miners, they are all potential new customers to him.  A lot of people will use his miners because they've simply got it to work and don't even think about changing or finding something better.

There ought to be a better way of paying for this software, why can't you develop a system where you purchase a number of licenses as a one time thing per GPU or per rig - Surely that's more fair ? You wouldn't pay a fee every day to run Windows 10 on 200 machines would you ? That'd be insane.

[ZombieWorm]

Can anyone help, Phoenix connects and mines away but it seems to get both my cards to mine under one miner. I have two cards that independantly mine using a profit switcher. How do I get Pheonix to mine an instance on one card and if the other card auto-switches opens another window should it need to?

I have nvidia and AMD card in case anyone is wondering.

[murgorx]

Guys, I have seen that the miner finds shares 4950MH and goes up to 928.2GH, have seen also results that go to 1TH+.
What is the meaning of this and how to regulate it, if I have to?
Could anyone give me an advice, please?

[aurus33]

Guys, I have seen that the miner finds shares 4950MH and goes up to 928.2GH, have seen also results that go to 1TH+.
What is the meaning of this and how to regulate it, if I have to?
Could anyone give me an advice, please?

Higher difficulty shares means more profit reflected on your earnings from the pool, I do not think there's a way to regulate it, I think it's just simply luck, sometimes you solve higher diff shares, some other times you solve lower diff shares and, sometimes you solve nothing

I might be wrong tho, this is my understanding so far, havent come up with a good read on how the pools handle difficulty.

[hamteivos]

Hitting with this error for the past 2 days, mining ETC on ethermine.
Both gtx 1060 and 1070 no hang, i still can see them using after burner.
Anyone hitting with this kind of errors?

17591:07:20:22.496: main Eth speed: 79.625 MH/s, shares: 47/0/0, time: 0:46
17591:07:20:22.496: main GPUs: 1: 18.465 MH/s (9) 2: 31.832 MH/s (21) 3: 29.329 MH/s (17)
17591:07:20:25.706: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xeb77fae561c0afcd983a8ff0a1c8372dbead6d4264853049fc44725f2dcbfa7f","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5382a3"]}
17591:07:20:25.706: eths Eth: New job #eb77fae5 from eu1-etc.ethermine.org:14444; diff: 4000MH
17591:07:20:27.512: main Eth speed: 78.413 MH/s, shares: 47/0/0, time: 0:46
17591:07:20:27.512: main GPUs: 1: 17.995 MH/s (9) 2: 31.103 MH/s (21) 3: 29.316 MH/s (17)
17591:07:20:29.897: GPU2 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17591:07:20:29.897: GPU2 GPU2 search error: unspecified launch failure
17591:07:20:29.948: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17591:07:20:29.949: GPU1 GPU1 search error: unspecified launch failure
17591:07:20:32.334: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x4bdeed8","0x94d6170da9ae5da346e6ef1432826c5f7c8d2db8c37ea7de36306d9565f93789"]}

17591:07:20:32.526: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17591:07:20:32.544: main Eth speed: 79.620 MH/s, shares: 47/0/0, time: 0:46
17591:07:20:32.544: main GPUs: 1: 18.463 MH/s (9) 2: 31.829 MH/s (21) 3: 29.329 MH/s (17)
17591:07:20:37.575: main Eth speed: 29.327 MH/s, shares: 47/0/0, time: 0:46
17591:07:20:37.575: main GPUs: 1: 0.000 MH/s (9) 2: 0.000 MH/s (21) 3: 29.327 MH/s (17)
17591:07:20:38.346: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x020e766278c1681f610557f3dfcc9dbf2713e80daafe51c570d60cf53b50a20d","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5382a4"]}
17591:07:20:38.347: eths Eth: New job #020e7662 from eu1-etc.ethermine.org:14444; diff: 4000MH
17591:07:20:38.350: GPU1 GPU1: Starting up...
17591:07:20:38.397: GPU2 GPU2: Starting up...
17591:07:20:38.431: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17591:07:20:38.431: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
17591:07:20:38.469: GPU2 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17591:07:20:38.469: GPU2 GPU2 initMiner error: all CUDA-capable devices are busy or unavailable
17591:07:20:42.592: main 
17591:07:20:42.592: main Eth: Mining ETC on eu1-etc.ethermine.org:14444
17591:07:20:42.592: main Eth speed: 29.332 MH/s, shares: 47/0/0, time: 0:46
17591:07:20:42.592: main GPUs: 1: 0.000 MH/s (9) 2: 0.000 MH/s (21) 3: 29.332 MH/s (17)
17591:07:20:42.592: main Eth: Accepted shares 47 (0 stales), rejected shares 0 (0 stales)
17591:07:20:42.592: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%

[infectedmushi]

17591:07:20:29.897: GPU2 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17591:07:20:29.897: GPU2 GPU2 search error: unspecified launch failure
17591:07:20:29.948: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17591:07:20:29.949: GPU1 GPU1 search error: unspecified launch failure
17591:07:20:32.334: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x4bdeed8","0x94d6170da9ae5da346e6ef1432826c5f7c8d2db8c37ea7de36306d9565f93789"]}
.
.
.

17591:07:20:38.350: GPU1 GPU1: Starting up...
17591:07:20:38.397: GPU2 GPU2: Starting up...
17591:07:20:38.431: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17591:07:20:38.431: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
17591:07:20:38.469: GPU2 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17591:07:20:38.469: GPU2 GPU2 initMiner error: all CUDA-capable devices are busy or unavailable

i was having this also, for me it was related to some OC settings.

@Claymore competition is always healthy for every party.. despite if PM dev is using Claymore's code, he should give him credits for it at least..