Do the test kernels help in limiting temp and memory clocks?
Just use overdriventool. You can set core, memory clock and control voltage. It is very stable.
Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 496. (Read 785074 times)
January 13, 2018, 01:19:45 AM
Just use overdriventool. You can set core, memory clock and control voltage. It is very stable.
January 13, 2018, 12:58:13 AM
Ok, it seems that we can't send PM for some reason, so here it is the download link for the beta version of PhoenixMiner 2.3:
(MEGA links are no longer active)
Here are the checksums of the PhenixMiner.exe file:
Note that this is not fully tested yet and not an official release. The major changes are:
(MEGA links are no longer active)
Here are the checksums of the PhenixMiner.exe file:
Code:
File: PhoenixMiner.exe
SHA-1: 90e455d81ce2f396e3d8121a5db3f4a356910dff
SHA-256: f119ae5b1085019522ab2a3752d20579647ed9fd9ff55cc739002de269adbc55
SHA-512: 3b876dc5491dae6da8849af941f4d0395b051e64a7fdcd42f126819d4788ef860c7d5f6e59763a5ed2d3368e93ec9b7e6bb6bca0476509e2a95d0856fe26fd68
SHA-1: 90e455d81ce2f396e3d8121a5db3f4a356910dff
SHA-256: f119ae5b1085019522ab2a3752d20579647ed9fd9ff55cc739002de269adbc55
SHA-512: 3b876dc5491dae6da8849af941f4d0395b051e64a7fdcd42f126819d4788ef860c7d5f6e59763a5ed2d3368e93ec9b7e6bb6bca0476509e2a95d0856fe26fd68
Note that this is not fully tested yet and not an official release. The major changes are:
- Added alternative kernels for RX470/480/570/580, which can be used by specifying -clKernel 2 (or -asm 2) on the command-line. In some cases these can be faster than the default kernels but more often than not you are better off with the default kernels. Additionally, the hashrate can be more unstable with the alternative kernels.
- Fixed a problem with not reporting temperatures/fan speed with the latest AMD drivers
- Fixed a problem with Intel iGPUs, which PhoenixMiner sometimes tries to use for mining, fails and then restarts and tries again, and so on.
Can I control core clock and memory clocks from the bat files...? I m using rx580 armor oc edition..
No, not yet. We are working on this feature but it is going to take some time as the different versions of the AMD drivers behave quite differently when trying to use Overdrive APIs. For now you should use MSI Afterburner, Wattman, or something similar to control the clocks and fans. January 13, 2018, 12:39:02 AM
Nodez coin is setting up their test net and the Dev there said he would be interested in adding their coin to your mining devfee algo. He stated he would be happy to setup if you might like to reach out to him. I sent a link to the Discord from this bitcointalk thread to help you gain some support. They are looking to launch mining in the next couple days!
Thank you for the info. It can be done (to avoid devfee DAG switching for Nodez) but we need a working wallet and working pool for this coin (with at least a dozen GH/s or so). Devfee of 0.65% means that it is only about 1 in 153 found shares on average that goes to the devfee account and if the hasrate for this coin is below certain threshold, the devfee is essentially zero. When I press "r" to reload the epool.txt, it seems that the miner cannot connect any pool. I press Ctrl + C to quit then it crashed. It was mining happily before I press the "r". 
Sorry for this problem. We managed to reproduce it here thanks to the log you have send. It doesn't happen often but when it does it can be fairly annoying. Eventually the miner manages to connect but it may take a ten or more attempts. We are going to find the root cause and will introduce a fix (but probably not in version 2.3 as it is already being tested internally). In the meantime if the miner can't connect with "Connection attempt aborted" error after a few attempts, the best workaround it to close it (ignore the error on exit if you get one) and start it again.yes i can help you test kernel, im on windows 10 with the amd blockchain driver
We will send you the link to the new version via PM. It includes slightly modified kernels for Ellesmere GPUs (RX470/480/570/580), which can be used if the option -clKernel 2 (or -asm 2 if you prefer Claymore's command-line syntax). Please note that during our testing on similar hardware to yours, the alternative kernel runs a little bit faster but only with very specific combination of core/mem clocks so in most cases we recommend using the default Ellesmere kernels. January 12, 2018, 08:10:29 PM
Hi,
When I press "r" to reload the epool.txt, it seems that the miner cannot connect any pool. I press Ctrl + C to quit then it crashed. It was mining happily before I press the "r".
When I press "r" to reload the epool.txt, it seems that the miner cannot connect any pool. I press Ctrl + C to quit then it crashed. It was mining happily before I press the "r".
Code:
17544:09:22:08.498: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:13.094: main Eth speed: 183.750 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:13.094: main GPUs: 1: 30.667 MH/s (3) 2: 30.663 MH/s (4) 3: 30.672 MH/s (1) 4: 30.644 MH/s (3) 5: 30.663 MH/s (2) 6: 30.442 MH/s (1)
17544:09:22:18.271: main
17544:09:22:18.271: main Eth: Mining ETH on asia1.ethermine.org:4444
17544:09:22:18.271: main Eth speed: 183.762 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:18.271: main GPUs: 1: 30.666 MH/s (3) 2: 30.626 MH/s (4) 3: 30.644 MH/s (1) 4: 30.555 MH/s (3) 5: 30.639 MH/s (2) 6: 30.632 MH/s (1)
17544:09:22:18.271: main Eth: Accepted shares 14 (0 stales), rejected shares 0 (0 stales)
17544:09:22:18.271: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
17544:09:22:18.271: main Eth: Maximum difficulty of found share: 74.0 GH (!)
17544:09:22:18.271: main Eth: Average speed (3 min): 183.797 MH/s
17544:09:22:18.271: main Eth: Effective speed: 175.00 MH/s; at pool: 175.00 MH/s
17544:09:22:18.271: main
17544:09:22:18.459: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17544:09:22:18.459: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xaf48488","0xdb505ca89c5f206be24ec09ae9dcc2683618205675a281584b4b64daa9e1e323"]}
17544:09:22:18.500: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:18.540: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:18.541: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17544:09:22:23.274: main Eth speed: 184.010 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:23.274: main GPUs: 1: 30.647 MH/s (3) 2: 30.669 MH/s (4) 3: 30.672 MH/s (1) 4: 30.670 MH/s (3) 5: 30.673 MH/s (2) 6: 30.678 MH/s (1)
17544:09:22:28.452: main Eth speed: 183.957 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:28.452: main GPUs: 1: 30.659 MH/s (3) 2: 30.652 MH/s (4) 3: 30.660 MH/s (1) 4: 30.652 MH/s (3) 5: 30.663 MH/s (2) 6: 30.672 MH/s (1)
17544:09:22:28.460: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17544:09:22:28.501: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:33.457: main Eth speed: 183.915 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:33.457: main GPUs: 1: 30.584 MH/s (3) 2: 30.665 MH/s (4) 3: 30.671 MH/s (1) 4: 30.655 MH/s (3) 5: 30.674 MH/s (2) 6: 30.665 MH/s (1)
17544:09:22:35.654: main GPU1: 60C 26%, GPU2: 55C 24%, GPU3: 47C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:22:38.473: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17544:09:22:38.473: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xaf4859f","0xdb505ca89c5f206be24ec09ae9dcc2683618205675a281584b4b64daa9e1e323"]}
17544:09:22:38.476: main Eth speed: 182.615 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:38.476: main GPUs: 1: 30.357 MH/s (3) 2: 30.387 MH/s (4) 3: 30.382 MH/s (1) 4: 30.385 MH/s (3) 5: 30.420 MH/s (2) 6: 30.683 MH/s (1)
17544:09:22:38.516: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:38.555: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:38.555: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17544:09:22:43.486: main Eth speed: 183.578 MH/s, shares: 14/0/0, time: 0:05
17544:09:22:43.486: main GPUs: 1: 30.655 MH/s (3) 2: 30.672 MH/s (4) 3: 30.659 MH/s (1) 4: 30.601 MH/s (3) 5: 30.675 MH/s (2) 6: 30.316 MH/s (1)
17544:09:22:44.584: GPU6 Eth: GPU6: ETH share found!
17544:09:22:44.584: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x11f09358634b76f5","0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0x7bd061e905404708bd08967de5dbed299ed4b498414875ac7b05741a091165f5"]}
17544:09:22:44.584: eths Eth: Share actual difficulty: 26.8 GH (!)
17544:09:22:44.629: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
17544:09:22:44.629: eths Eth: Share accepted in 45 ms
17544:09:22:48.479: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17544:09:22:48.520: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4ac0b1"]}
17544:09:22:48.558: main Eth speed: 184.649 MH/s, shares: 15/0/0, time: 0:05
17544:09:22:48.558: main GPUs: 1: 30.658 MH/s (3) 2: 30.669 MH/s (4) 3: 30.672 MH/s (1) 4: 30.674 MH/s (3) 5: 30.674 MH/s (2) 6: 31.303 MH/s (2)
17544:09:22:51.601: GPU5 Eth: GPU5: ETH share found!
17544:09:22:51.601: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x7c67ac6cba2de823","0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xa8295ad3c70722c8c717b27f9f972cc67dd5f5b08129ebd57ab641e5c7a4b16f"]}
17544:09:22:51.601: eths Eth: Share actual difficulty: 10.2 GH (!)
17544:09:22:51.645: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
17544:09:22:51.645: eths Eth: Share accepted in 44 ms
17544:09:22:53.574: main Eth speed: 184.775 MH/s, shares: 16/0/0, time: 0:05
17544:09:22:53.574: main GPUs: 1: 30.662 MH/s (3) 2: 30.631 MH/s (4) 3: 30.676 MH/s (1) 4: 30.643 MH/s (3) 5: 31.537 MH/s (3) 6: 30.627 MH/s (2)
17544:09:22:56.617: GPU6 Eth: GPU6: ETH share found!
17544:09:22:56.617: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x11f093587925191e","0xba0aa415c649d8b94fd896aedd0f7d464c18f2d3f43e092e8ea9013f7a59145b","0xa89d6809e3f6c80b0e30a3dba70431855719e4355fa35263274a2808fb2bece7"]}
17544:09:22:56.617: eths Eth: Share actual difficulty: 15.8 GH (!)
17544:09:22:56.661: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
17544:09:22:56.661: eths Eth: Share accepted in 44 ms
17544:09:22:56.840: main Reloading epools.txt
17544:09:22:56.840: main Eth: the pool list contains 4 pools
17544:09:22:56.840: main Eth: primary pool: asia1.ethermine.org:4444
17544:09:22:56.840: eths Eth: Reconnecting in 10 seconds...
17544:09:23:03.663: main GPU1: 61C 26%, GPU2: 55C 24%, GPU3: 46C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:23:06.851: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:23:10.139: unkn Eth: Connection attempt aborted
17544:09:23:10.139: unkn Eth: Reconnecting in 15 seconds...
17544:09:23:24.893: GPU6 Unable to submit share - pool disconnected
17544:09:23:25.145: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:23:26.938: GPU2 Unable to submit share - pool disconnected
17544:09:23:28.441: unkn Eth: Connection attempt aborted
17544:09:23:28.441: unkn Eth: Reconnecting in 20 seconds...
17544:09:23:31.863: main GPU1: 60C 26%, GPU2: 55C 24%, GPU3: 46C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:23:37.086: main Reloading epools.txt
17544:09:23:37.086: main Eth: the pool list contains 4 pools
17544:09:23:37.086: main Eth: primary pool: asia1.ethermine.org:4444
17544:09:23:37.086: unkn Eth: Reconnecting in 10 seconds...
17544:09:23:47.092: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:23:50.381: unkn Eth: Connection attempt aborted
17544:09:23:50.381: unkn Eth: Reconnecting in 15 seconds...
17544:09:23:52.542: GPU5 Unable to submit share - pool disconnected
17544:09:24:00.020: main GPU1: 60C 26%, GPU2: 54C 24%, GPU3: 51C 0%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:24:05.396: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:24:08.679: unkn Eth: Connection attempt aborted
17544:09:24:08.679: unkn Eth: Reconnecting in 20 seconds...
17544:09:24:16.881: main
17544:09:24:16.881: main Select pool (press key from 0 to 3)
17544:09:24:16.881: main * 0. asia1.ethermine.org:4444
17544:09:24:16.881: main 1. asia1.ethermine.org:14444
17544:09:24:16.881: main 2. us1.ethermine.org:4444
17544:09:24:16.881: main 3. asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:16.881: main
17544:09:24:21.754: main Mining on GPU3 is disabled
17544:09:24:23.530: main Mining on GPU3 is enabled
17544:09:24:28.123: main GPU1: 61C 25%, GPU2: 54C 24%, GPU3: 50C 26%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 57C 24%
17544:09:24:28.683: unkn Eth: Connecting to ethash pool asia1.ethermine.org:4444
17544:09:24:31.992: unkn Eth: Connection attempt aborted
17544:09:24:31.992: unkn Eth: Giving up after 3 retries, switching to next pool
17544:09:24:31.992: unkn Eth: Reconnecting in 7 seconds...
17544:09:24:34.457: main
17544:09:24:34.457: main Select pool (press key from 0 to 3)
17544:09:24:34.457: main 0. asia1.ethermine.org:4444
17544:09:24:34.457: main * 1. asia1.ethermine.org:14444
17544:09:24:34.457: main 2. us1.ethermine.org:4444
17544:09:24:34.457: main 3. asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:34.457: main
17544:09:24:36.857: main Eth: Switching to pool: asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:36.857: unkn Eth: Reconnecting in 10 seconds...
17544:09:24:43.835: GPU5 Unable to submit share - pool disconnected
17544:09:24:46.865: unkn Eth: Connecting to ethash pool asia.ethash-hub.miningpoolhub.com:20535
17544:09:24:50.182: unkn Eth: Connection attempt aborted
17544:09:24:50.182: unkn Eth: Reconnecting in 15 seconds...
17544:09:24:56.255: main GPU1: 61C 25%, GPU2: 54C 24%, GPU3: 48C 24%, GPU4: 60C 29%, GPU5: 57C 24%, GPU6: 58C 24%
17544:09:25:05.048: unkn Quitting...
17544:09:25:05.186: unkn Eth: Connecting to ethash pool asia.ethash-hub.miningpoolhub.com:20535
January 12, 2018, 01:51:54 PM
Admin,
Nodez coin is setting up their test net and the Dev there said he would be interested in adding their coin to your mining devfee algo. He stated he would be happy to setup if you might like to reach out to him. I sent a link to the Discord from this bitcointalk thread to help you gain some support. They are looking to launch mining in the next couple days!
https://discordapp.com/channels/359804055490658315/359804055490658317
Nodez Dev Info:
WallerMaDev
[email protected]
www.twitter.com/wallermadev
-Tom
Nodez coin is setting up their test net and the Dev there said he would be interested in adding their coin to your mining devfee algo. He stated he would be happy to setup if you might like to reach out to him. I sent a link to the Discord from this bitcointalk thread to help you gain some support. They are looking to launch mining in the next couple days!
https://discordapp.com/channels/359804055490658315/359804055490658317
Nodez Dev Info:
WallerMaDev
[email protected]
www.twitter.com/wallermadev
-Tom
January 12, 2018, 08:04:03 AM
I did some tests with RX 570 4GB (bios mod + core 1190/mem2000)
Claymore 10.0 29.17MH/s (1% devfee - 0,29MH/s) 28,88MH/s effective
PhoenixMiner 2.2b 29.52MH/s (0.65% devfee - 0,19MH/s) 29,33MH/s effective
Goobur ethminer 0.12.0 29.14MH/s (0% devdee if u suck)
#########
Mix of cards seems better too:
RX580 8gb + GTX 1060 6gb
2 GPU CLAYMORE 10.0
ETH: GPU0 30.394 Mh/s, GPU1 23.240 Mh/s
2GPU PHOENIX 2.2b
GPUs: 1: 30.703 MH/s 2: 23.385 MH/s
#########
Seems like it's worth to use PhoenixMiner, these are local tests and need to be confirmed online.
I like these pool hashrate reports, same as claymore command line is big +
Claymore 10.0 29.17MH/s (1% devfee - 0,29MH/s) 28,88MH/s effective
PhoenixMiner 2.2b 29.52MH/s (0.65% devfee - 0,19MH/s) 29,33MH/s effective
Goobur ethminer 0.12.0 29.14MH/s (0% devdee if u suck)
#########
Mix of cards seems better too:
RX580 8gb + GTX 1060 6gb
2 GPU CLAYMORE 10.0
ETH: GPU0 30.394 Mh/s, GPU1 23.240 Mh/s
2GPU PHOENIX 2.2b
GPUs: 1: 30.703 MH/s 2: 23.385 MH/s
#########
Seems like it's worth to use PhoenixMiner, these are local tests and need to be confirmed online.
I like these pool hashrate reports, same as claymore command line is big +
January 12, 2018, 07:46:54 AM
I have been running for 8hrs without any problem. Hash rate are approx. the same as using claymore. I can now see 3mins average hashrate and stale share. I will change to phoenixminer if it is stable for 1-2 days. Good work! 
January 12, 2018, 05:14:45 AM
Wow very good clapclap nice review. The problem is you are a newbie too. Why all of a sudden post something as detailed as this?
Pardon my doubts but to be transparent I also have doubts that you could be the topic starter in disguise.
I too am hoping this is legit and we can finally spread the wealth to other developers aside from claymore (extra interested given the claims that this is a faster and cheaper miner).
Until further testing is done by brave souls, will hold off on using this miner.
What, exactly, are you afraid of? If shares are normally coming from your rig to pool, and coins from your pool to your wallet,
what harm can miner do to your rig?
January 12, 2018, 04:41:04 AM
Well, I'm not sure I qualify as "security expert" but I certainly am a "full-time security paranoic" 
And as no one else seem to risk it, I downloaded and tested the miner as well as I could.
First, I used an online virus scanner to check the file.
The results are: 2/67 detected (https://www.virustotal.com/#/file/74cfd6a34e158c2f5fe1b8422d6b8daee304394eeaf85992b117bf5de315d569/detection), which is actually an excellent result, given that the Claymore's miner gives 41/68 positives (https://www.virustotal.com/#/file/7852c50c835d7110ab8d055cccad06674e94d85324414f91366852bed9be29cc/detection).
And even the open-source ethminer 0.12.0 gives 26/67 positives, which is ridiculous (https://www.virustotal.com/#/file/4aa1082b5581540eced3acb18ee52cd06ee062772a5d386cf7501b2a8b7af094/detection)
So, I prepared a backup image of the SSD of my rig (in case that this new miner turn out to be malicious) and then ran it for about 18 hours while monitoring the PhoenixMiner.exe network, file system, and registry activity with Wireshark and some advanced system calls monitors. It connected to my mining pool as it should and then opened port 3333, which turned out to be the port for remote control similar to Claymore's miner. I disabled to remote port with the "-cdm 0" commnad-line switch and restarted the miner. Sure enough, this time port 3333 wasn't opened and the only connection was the one to my pool.
The first new connection was observed after 16 minutes of mining, which connected to another pool (ehtermine.org) and the miner showed that it was mining for developer fee. It disconnected after 35 seconds as advertised. After that I left the rig alone and analyzed the Wireshark and the other logs the next day.
The miner connected to the devfee pool every 90 minutes, with one exception when it wasn't able to connect to the ehtermine.org. It then tried again after 13 minutes and then resumed the normal 90 minutes period between devfee connections. No other network activity was recorded. The registry activity was also normal (no keys were created and no suspicious registry key reading was detected). Also, no files outside the current folder were opened or touched.
As for the mining speed, my rig has 6x ASUS Strix 570 OC (with BIOS mod) and under Claymore's miner it makes about 173 mhs. With Phoenix the speed was about 174.5 mhs, which is not much better but I guess is still something. The power consumption from the wall was about the same (755-765W). According the the pool, the speed was even better (169 vs 166 with claymore) but this doesn't mean much as I've seen this numbers change a lot without any apparent reason, so it would take some more time before declaring PhoenixMiner to be faster.
Of course, there is no guarantee that the PhoenixMiner won't "decide to go bad" at some point of the future, but right now it seems legit.
Some suggestions for the devs: the share difficulty is a nice touch but it would be better to directly show the number of blocks found. Most pools doesn't report this and even when they do, I'm always suspicions. Also, your miner does seem to be compatible with Claymore's manager, which is nice, but I hope that you will produce a better manager (and maybe even a mobile app for Android), because the claymore's manager is rather simplistic and I miss a lot of features.
And as no one else seem to risk it, I downloaded and tested the miner as well as I could.First, I used an online virus scanner to check the file.
The results are: 2/67 detected (https://www.virustotal.com/#/file/74cfd6a34e158c2f5fe1b8422d6b8daee304394eeaf85992b117bf5de315d569/detection), which is actually an excellent result, given that the Claymore's miner gives 41/68 positives (https://www.virustotal.com/#/file/7852c50c835d7110ab8d055cccad06674e94d85324414f91366852bed9be29cc/detection).
And even the open-source ethminer 0.12.0 gives 26/67 positives, which is ridiculous (https://www.virustotal.com/#/file/4aa1082b5581540eced3acb18ee52cd06ee062772a5d386cf7501b2a8b7af094/detection)
So, I prepared a backup image of the SSD of my rig (in case that this new miner turn out to be malicious) and then ran it for about 18 hours while monitoring the PhoenixMiner.exe network, file system, and registry activity with Wireshark and some advanced system calls monitors. It connected to my mining pool as it should and then opened port 3333, which turned out to be the port for remote control similar to Claymore's miner. I disabled to remote port with the "-cdm 0" commnad-line switch and restarted the miner. Sure enough, this time port 3333 wasn't opened and the only connection was the one to my pool.
The first new connection was observed after 16 minutes of mining, which connected to another pool (ehtermine.org) and the miner showed that it was mining for developer fee. It disconnected after 35 seconds as advertised. After that I left the rig alone and analyzed the Wireshark and the other logs the next day.
The miner connected to the devfee pool every 90 minutes, with one exception when it wasn't able to connect to the ehtermine.org. It then tried again after 13 minutes and then resumed the normal 90 minutes period between devfee connections. No other network activity was recorded. The registry activity was also normal (no keys were created and no suspicious registry key reading was detected). Also, no files outside the current folder were opened or touched.
As for the mining speed, my rig has 6x ASUS Strix 570 OC (with BIOS mod) and under Claymore's miner it makes about 173 mhs. With Phoenix the speed was about 174.5 mhs, which is not much better but I guess is still something. The power consumption from the wall was about the same (755-765W). According the the pool, the speed was even better (169 vs 166 with claymore) but this doesn't mean much as I've seen this numbers change a lot without any apparent reason, so it would take some more time before declaring PhoenixMiner to be faster.
Of course, there is no guarantee that the PhoenixMiner won't "decide to go bad" at some point of the future, but right now it seems legit.
Some suggestions for the devs: the share difficulty is a nice touch but it would be better to directly show the number of blocks found. Most pools doesn't report this and even when they do, I'm always suspicions. Also, your miner does seem to be compatible with Claymore's manager, which is nice, but I hope that you will produce a better manager (and maybe even a mobile app for Android), because the claymore's manager is rather simplistic and I miss a lot of features.
Wow very good clapclap nice review. The problem is you are a newbie too. Why all of a sudden post something as detailed as this?
Pardon my doubts but to be transparent I also have doubts that you could be the topic starter in disguise.
I too am hoping this is legit and we can finally spread the wealth to other developers aside from claymore (extra interested given the claims that this is a faster and cheaper miner).
Until further testing is done by brave souls, will hold off on using this miner.
January 12, 2018, 01:04:55 AM
I like the miner ,runs faster and more shares per hr then other miners, the fan speed and temp doesnt display with win10-64bit-radeon-software-adrenalin-edition-17.12.2 hopefully that can get fixed in next version. I find these drivers more stable then the blockchain drivers.
Thank you for reporting this problem. It appears that there is a bug in 17.12.2 drivers - they do not report the PCIe bus id of the OpenCL devices, which prevents the miner from matching each OpenCL device to a physical GPU in order to get its temperature and fan speed. Hopefully AMD will fix the problem in the next driver release. In the meantime we have implemented a workaround for PhoenixMiner 2.3, which should be released in a few days.
January 11, 2018, 11:13:23 AM
I like the miner ,runs faster and more shares per hr then other miners, the fan speed and temp doesnt display with win10-64bit-radeon-software-adrenalin-edition-17.12.2 hopefully that can get fixed in next version. I find these drivers more stable then the blockchain drivers.
great work
great work
January 11, 2018, 10:08:54 AM
I have been using this miner since it was first launched about 2 weeks ago. The first version 2.0 worked fine but the Dag switch for ETP caused issues and stoppage. The new 2.2b version with added Dags solved my problem perfectly. I have had no issues what so ever and I do see about a 1-2 mh/s more on my 6 card rig. I find this more stable for me than Claymore has been in the past. I use this miner full time and the dev has been both responsive and prompt in this forum
Some additional things I like:
- Alt Dags available when mining other than Eth
- Each card shows shares found and which card finds block
- Miner shows highest share found
The file does post a false positive for a virus in Windows 10 but an exception solved this problem in the host folder. This is not the first time mining software has prompted this warning for me with other downloads. My rig is solely used for mining, which is recommended, so I have nothing to steal or be hacked from the rig itself.
6/RX 580 8gb Gaming - Modded bios - Blockchain drivers - 185 mh/s
Cheers!
Some additional things I like:
- Alt Dags available when mining other than Eth
- Each card shows shares found and which card finds block
- Miner shows highest share found
The file does post a false positive for a virus in Windows 10 but an exception solved this problem in the host folder. This is not the first time mining software has prompted this warning for me with other downloads. My rig is solely used for mining, which is recommended, so I have nothing to steal or be hacked from the rig itself.
6/RX 580 8gb Gaming - Modded bios - Blockchain drivers - 185 mh/s
Cheers!
January 11, 2018, 07:33:14 AM
5 x RX 570
...
asm 2 use a different "kernel" i think and is not present in phoenixminer
...
asm 2 use a different "kernel" i think and is not present in phoenixminer
Could you please tell us the core and memory clocks of these RX 570s? We will try to recreate the same results on our test rigs and see why is this happening. Then we will tweak our kernels for RX470/480/570/580 and see if we can increase the speed for this particular case. Are you willing to test the new kernels when they are ready?
yes i can help you test kernel, im on windows 10 with the amd blockchain driver
my settings are
core clock: 1150
memory: 2070
i have some 4g and some 8g of memory so they dont do all the same MHs but really all do 30.x for a total of 152.x
January 11, 2018, 06:39:03 AM
5 x RX 570
...
asm 2 use a different "kernel" i think and is not present in phoenixminer
...
asm 2 use a different "kernel" i think and is not present in phoenixminer
Could you please tell us the core and memory clocks of these RX 570s? We will try to recreate the same results on our test rigs and see why is this happening. Then we will tweak our kernels for RX470/480/570/580 and see if we can increase the speed for this particular case. Are you willing to test the new kernels when they are ready?
January 10, 2018, 07:50:10 AM
I've tested it and apart from the virus alerts ( which as far as i can tell are harmless, i've tested the application behaviour in sandbox ),
it works great.
Tnx !
Compare to Claymore miner, how many percent can be increased at hashrate?it works great.
Tnx !
id like to know this too.. can someone post some result of their cards?
January 10, 2018, 04:06:38 AM
I've tested it and apart from the virus alerts ( which as far as i can tell are harmless, i've tested the application behaviour in sandbox ),
it works great.
Tnx !
Compare to Claymore miner, how many percent can be increased at hashrate? it works great.
Tnx !
January 10, 2018, 03:06:04 AM
I've tested it and apart from the virus alerts ( which as far as i can tell are harmless, i've tested the application behaviour in sandbox ),
it works great.
Tnx !
it works great.
Tnx !
January 10, 2018, 03:00:09 AM
hi
just want to confirm that you support the same command for clock, voltage, temp, fan than claymore?
i really like to try your miner
Only the hardware monitoring (i.e. reporting temperature and fan speed) is currently supported. You will have to use something like Afterburner or Wattman to control voltages and fan speed. We are working on hardware control but the AMD drivers tend to break compatibility too often.just want to confirm that you support the same command for clock, voltage, temp, fan than claymore?
i really like to try your miner
New version still has Trojan/Win64.Wdfload virus. Be warned.
Stop trolling here and find other threads to pile your useless posts.Maybe you should work on getting rid of this wdfload trojan and people would take you more seriously.
January 10, 2018, 12:29:52 AM
is it possible to add dual mining to lyra2rev2 xvg mining. ?
lyra2rev2 xvg is not memory based.
lyra2rev2 xvg is not memory based.
January 09, 2018, 11:25:09 PM
hi
just want to confirm that you support the same command for clock, voltage, temp, fan than claymore?
i really like to try your miner
Only the hardware monitoring (i.e. reporting temperature and fan speed) is currently supported. You will have to use something like Afterburner or Wattman to control voltages and fan speed. We are working on hardware control but the AMD drivers tend to break compatibility too often.just want to confirm that you support the same command for clock, voltage, temp, fan than claymore?
i really like to try your miner
New version still has Trojan/Win64.Wdfload virus. Be warned.
Stop trolling here and find other threads to pile your useless posts. Jump to: