is it working with new versions of claymore? #22

plscarrymeeeeeeee · 2018-02-10T23:36:01Z

is it working with new versions of claymore?

LostSoulfly · 2018-02-10T23:40:00Z

I haven't tested the changes that @samut3 has committed, but I've been using the same version for my miners since last year and I updated to the newest Claymore yesterday on one of my rigs and it worked just fine.

@samut3 added some commits that, iirc, targeted issues with the newer version of Claymore. I haven't run into any personally, though.

plscarrymeeeeeeee · 2018-02-11T17:09:20Z

for me it doesnt show the shares is that correct?

LostSoulfly · 2018-02-11T17:41:49Z

Are you using the new version I uploaded yesterday?

…

On Feb 11, 2018 12:09 PM, "inpanic" ***@***.***> wrote: for me it doesnt show the shares is that correct? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIsrB6tbrTPI9O58UkTTvOsEWL5YrIs2ks5tTx7AgaJpZM4SBIOr> .

plscarrymeeeeeeee · 2018-02-12T04:42:56Z

yes. i tested it with hiveos.farm linux (claymore 11)
it only shows accept share if gpu0 is finding a share.
if gpu2 - gpu5 find a share it shows nothing.

the log file:

[192.168.0.1_33434] 07:07:01: eth_getWork from Client.
[192.168.0.1_33434] 07:07:01: eth_getWork from server.
[192.168.0.1_33434] 07:07:03: From Client >---->
[192.168.0.1_33434] 07:07:03: Unknown ID: 12
[192.168.0.1_33434] 07:07:03: Method: eth_submitWork
[192.168.0.1_33434] 07:07:03: Param Count: 3
[192.168.0.1_33434] 07:07:03: {"id":12,"method":"eth_submitWork","params":["0x3bc1a918001447aa","0x4bfdff1a5ccfae4c34416bd1d57621b31d4d41a882314a8473af38cec8d6c51b","0x804c9a0e6a97beed2fb3c75d0190fa8e66ff62b44091f5b5ffbdb7f7656e459d"]}

[192.168.0.1_33434] 07:07:03: From Server2 <----<
[192.168.0.1_33434] 07:07:03: Unknown ID: 12
[192.168.0.1_33434] 07:07:03: Result: True
[192.168.0.1_33434] 07:07:03: {"id":12,"jsonrpc":"2.0","result":true}

same error on id Unknown ID: 11,12,13,14,15

ID 11 is gpu1
ID 12 is gpu2
ID 13 is gpu3
ID 14 is gpu4
ID 15 is gpu5
only gpu0 is working

proxy is on windows 10.

cowboyfoggy · 2018-02-12T21:14:33Z

Same problem here too :(

Claymore 11
Windows 10

samu01 · 2018-02-13T13:52:13Z

Oh sorry, I don't have a multi gpu rig so I couldn't test that. Try building from the newest commit and tell me if that works.

It's a bit of a "ghetto" fix but meh.

cowboyfoggy · 2018-02-13T20:31:11Z

i dont have enogh free space on my hdd to install visual studio , will try tomorrow on another pc. i'll post the result

samu01 · 2018-02-13T20:35:02Z

@cowboyfoggy You can download my compiled executable here: https://ufile.io/m3036

LostSoulfly · 2018-02-22T00:02:23Z

I'm using the current version freshly compiled and I don't have any issues, Claymore v11.

What pool are you experiencing this issue on? I'm using Ethermine's ETC pool, and all my GPU shares are being correctly reported and submitted.

plscarrymeeeeeeee · 2018-02-22T00:28:24Z

the problem is with the dev fee. i only got the dev fee on gpu 0. i use now a python proxy without any problem

JsBergbau · 2018-03-03T11:24:00Z

Which python-proxy do you use? The JuicyPasta python proxy also doesn't work with v11.2 You simply get no devfee shares

[+] Received incomming connections from XXXX:58892
[+] Auth in progress with address: 0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
[*] DevFee Detected - Replacing Address - 2018-03-03 11:34:18.746265
[*] OLD: 0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
[*] NEW: XXXXXXX
[!] Sending packets to pool failed.
[!] Connection with pool lost. Claymo

Digging through the log always tells unrequested work provided and share rejected.

https://ethermine.org/miners/7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc/payouts
That greedy Claymore B*** gets 140.000 Dollar each month with his stealing devfee

plscarrymeeeeeeee · 2018-03-03T12:27:32Z

https://github.com/JuicyPasta/Claymore-No-Fee-Proxy thats my new solution

JsBergbau · 2018-03-03T12:30:44Z

Did you check the logs? I've also tried using this proxy with Claymore 11.2 and it also doesn't work. Shares found in devfee round aren't accepted.
LostSoulFly MinerProxy worked with Claymore v11.0 flawlessly (didn't use v11.1)

JsBergbau · 2018-03-03T12:32:04Z

@LostSoulfly
How can we support you, that you can improve your proxy also working with multiple GPUs

plscarrymeeeeeeee · 2018-03-03T12:33:06Z

i use claymore 10.2 and 10.5 now

JsBergbau · 2018-03-03T12:44:54Z

Strange, with 10.5 and 10.6 and LostSoulFly MinerProxy everything was working fine. Devfee shares went to mine account with any problems.

plscarrymeeeeeeee · 2018-03-03T12:46:37Z

why u update then?some people say he only makes updates to protect his fee

JsBergbau · 2018-03-03T12:55:07Z

Because v11.2 is a bit faster than v11.0
But youre right this guy is putting so much effort in protecting his fee. His miner could be a lot better if he would spend that time in really developing his software, this greedy s** o* b****
Currently I run 11.0 again, because the 2 % devfee go with this version to me and thus making more than the speedup in 11.2
However still would be nice to be able to use new version.
This is log from v11.0 and LostSoulFly MinerProxy so you see share from GPU5 is accepted without any problems.

12:39:51:577	1038	DevFee: ETH: Stratum - connecting to 'XXX' <XXX> port XXX
12:39:51:592	1038	send: devfee auth
12:39:51:592	1038	DevFee: ETH: Stratum - Connected (XXXXX)
12:39:51:624	1fcc	checked ETH share on CPU, spent 7ms
12:39:51:624	1fcc	ETH: put share nonce 433860e001cd3663
12:39:51:624	1fcc	ETH round found 1 shares
12:39:51:639	1fb4	ETH: 02/20/18-12:39:51 - SHARE FOUND - (GPU 5)
12:39:51:639	1fb4	send: {"id":15,"method":"eth_submitWork","params":["0x433860e001cd3663","0x631d65c8546bbc448e788c5259e3f95654338d990dac5cf101e668a33affdaaf","0x48db8968bddc43e3b1a63176b0abd059eb17389ea57bc9d3d90eabbee789e150"]}

12:39:51:717	1fb4	got 40 bytes
12:39:51:717	1fb4	buf: {"id":15,"jsonrpc":"2.0","result":true}

12:39:51:717	1fb4	parse packet: 39
12:39:51:717	1fb4	ETH: Share accepted (79 ms)!

LostSoulfly · 2018-03-04T03:08:30Z

I don't see myself doing any more work on this version of MinerProxy.

I have, however, begun work on a completely redesigned version and I'll test it with the newest Claymore version available when I get to that portion of the project. I don't have an ETA (but I hope to have it out soon^{^TM} ). It's not currently a public repo but will be in the future.

I'll update this repo and thread when I have more information.

In the meantime, I suggest using https://github.com/Demion/nodevfee on a supported version of Claymore. I actually use it inline with two MinerProxy instances. For instance, I'm mining Metaverse and the devfee goes to my ETC pool.

plscarrymeeeeeeee · 2018-03-04T04:26:09Z

thx for the work btw!

JsBergbau · 2018-03-04T12:03:41Z

@LostSoulfly Thanks for all your work.
Is your new Version also C#/.NET? I'm asking because MinerProxy works great with Mono on Linux.

In the meantime, I suggest using https://github.com/Demion/nodevfee on a supported version of Claymore. I actually use it inline with two MinerProxy instances. For instance, I'm mining Metaverse and the devfee goes to my ETC pool.

Thanks for the tip. I'll stay at your MinerProxy and Claymore v11 till your new release is out.

LostSoulfly · 2018-03-04T12:58:43Z

Yes, the new version will be in. .Net Core.

…

On Mar 4, 2018 7:03 AM, "JsBergbau" ***@***.***> wrote: @LostSoulfly <https://github.com/lostsoulfly> Thanks for all your work. Is your new Version also C#/.NET? I'm asking because MinerProxy works great with Mono on Linux. In the meantime, I suggest using https://github.com/Demion/nodevfee on a supported version of Claymore. I actually use it inline with two MinerProxy instances. For instance, I'm mining Metaverse and the devfee goes to my ETC pool. Thanks for the tip. I'll stay at your MinerProxy and Claymore v11 till your new release is out. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIsrBxMtSeCDmXD5BbbwTh2uWxgLf3nCks5ta9gdgaJpZM4SBIOr> .

LostSoulfly · 2018-03-04T23:51:02Z

I'm getting reports of newest Claymore version requiring SSL connections. MinerProxy won't be able to support those, but I'll wait to see how it all unfolds. I'll also look into supporting PhoenixMiner in the new versions.

samu01 · 2018-03-05T06:15:18Z

I am using Claymore v11.2 with minerproxy and it is working perfectly for me in a single gpu rig.

JsBergbau · 2018-03-05T17:22:13Z

@LostSoulfly
v11.2 brings support for SSL and reduced devfee when using SSL, but it's not an requirement

@samut3
Yes it works, but do you also get the shares mined during the devfee time? Please watch your log.

samu01 · 2018-03-09T06:10:59Z

@JsBergbau
http://prntscr.com/ios9u8 I do.

LostSoulfly · 2018-03-11T00:00:42Z

I've made a lot of progress on the new version of MinerProxy, so here's a peak at it so far:

For some more info, this version will be able to run multiple proxies in a single instance and only make one connection to the pool for all the connected miners. I'd also like to implement Telegram notifications for miner disconnections and such, but that's a ways off.

LostSoulfly · 2018-03-17T16:20:06Z

Another update! A lot of progress is being made, I think. I've got most of Ethereum working with 1 GPU. I'm moving to implement multiple miners next. Once I've got Ethereum working how I want, I can work on adding support for different protocols and pools. Then we move on to other coins.

LostSoulfly · 2018-03-18T02:33:01Z

Ugh. I spent a lot of my saturday working on this. Here's another update.

JsBergbau · 2018-03-24T21:23:31Z

@LostSoulfly
Thanks for the status updates. Is there any date yet when the new version will be out?

You're very deep into it, can you explain why getting shares from multiple GPUs is difficult or say different as from a single GPU system? For me as layperson it should be the same, a share is a share.

LostSoulfly · 2018-03-24T21:46:34Z

I don't have an ETA, but I'll probably put the project on github soon. Only Ethereum is working as of right now and I haven't tested pools that I don't use yet, either. And it's not that it's difficult, it's just different for each miner. And Claymore seems to do it differently. The original MinerProxy still works and passes Shares with the newer versions of Claymore, it just doesn't know that it was accepted or rejected (which is what one bug report was). *Also, Ni No Kuni 2 just released, so I've been playing that all weekend.

…

On Sat, Mar 24, 2018 at 5:23 PM, JsBergbau ***@***.***> wrote: @LostSoulfly <https://github.com/LostSoulFly> Thanks for the status updates. Is there any date yet when the new version will be out? You're very deep into it, can you explain why getting shares from multiple GPUs is difficult or say different as from a single GPU system? For me as layperson it should be the same, a share is a share. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIsrB_R2YEHgsa5_BVUaVV7F_mQauJ90ks5thrlUgaJpZM4SBIOr> .

JsBergbau · 2018-03-24T21:52:57Z

Wow thanks for your fast reply. Have fun playing Ni No Kuni 2

The original MinerProxy still works and passes Shares with the newer versions of Claymore, it just doesn't know that it was accepted or rejected (which is what one bug report was).

Really? Because Ethermine.org didn't show the devfee worker for hours with MinerProxy and the 11.2 Claymore version, so I think the share was lost... (Very unlikely that devfee got no shares over 5 hours with 170 MH/s)

LostSoulfly · 2018-03-24T22:40:32Z

You should check where it is connecting to because Claymore seems to be forcing SSL now. I don't know if it's because I use -allcoins 1 to mine altcoins (ubq, etp, etc), but it definitely connects through SSL for me sometimes. So I use PhoenixMiner on most of my machines that have Nvidia. Only use Claymore anymore for dual mining on my RX470s.

…

On Sat, Mar 24, 2018 at 5:52 PM, JsBergbau ***@***.***> wrote: Wow thanks for your fast reply. Have fun playing Ni No Kuni 2 The original MinerProxy still works and passes Shares with the newer versions of Claymore, it just doesn't know that it was accepted or rejected (which is what one bug report was). Really? Because Ethermine.org didn't show the devfee worker for hours with MinerProxy and the 11.2 Claymore version, so I think the share was lost... (Very unlikely that devfee got no shares over 5 hours with 170 MH/s) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIsrB6oyc26iMbl-GtZT1-WUnxSlXkU7ks5thsA5gaJpZM4SBIOr> .

JsBergbau · 2018-03-24T23:02:05Z

I don't use allcoins -1, so it connects to ethermine.org. It also gets its Eth: Stratum connected Eth: Authorized
Just when the share is found, there is no "Share accepted" message.
11.2 Definitively didn't force SSL. When you use allcoins 1 its very likely that it uses SSL for some connections, since it uses it's builtin (SSL)Adresses.

LostSoulfly · 2018-03-31T21:02:33Z

I've almost finished Ni No Kuni 2, and I've made a bit of progress on the new version of MP as well. FailOver pools are implemented as of today, and also today I added loading pools from files. You can have as many pools as you want in the same instance of MinerProxy2 as each pool has its own file.

JsBergbau · 2018-04-09T21:42:44Z

Thanks for sharing the progress. I'm looking forward using your new version.

LostSoulfly · 2018-04-09T22:48:25Z

I've made the repo for MinerProxy2 public: https://github.com/LostSoulFly/MinerProxy2 Currently only Ethereum is working, but I'm opening it up for testing and bug finding. You'll have to compile it yourself if you want to try it, though.

…

On Mon, Apr 9, 2018 at 5:42 PM, JsBergbau ***@***.***> wrote: Thanks for sharing the progress. I'm looking forward using your new version. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIsrB46jq79Ic8-JJF6dfwmdLJ443p3Xks5tm9XVgaJpZM4SBIOr> .

JsBergbau · 2018-04-10T08:36:46Z

Thank you very much. I'll try when I have some more freetime.

is it working with new versions of claymore? #22

is it working with new versions of claymore? #22

Comments

plscarrymeeeeeeee commented Feb 10, 2018

LostSoulfly commented Feb 10, 2018

plscarrymeeeeeeee commented Feb 11, 2018

LostSoulfly commented Feb 11, 2018 via email

plscarrymeeeeeeee commented Feb 12, 2018 • edited Loading

cowboyfoggy commented Feb 12, 2018 • edited Loading

samu01 commented Feb 13, 2018 • edited Loading

cowboyfoggy commented Feb 13, 2018

samu01 commented Feb 13, 2018

LostSoulfly commented Feb 22, 2018 • edited Loading

plscarrymeeeeeeee commented Feb 22, 2018

JsBergbau commented Mar 3, 2018 • edited Loading

plscarrymeeeeeeee commented Mar 3, 2018 • edited Loading

JsBergbau commented Mar 3, 2018 • edited Loading

JsBergbau commented Mar 3, 2018

plscarrymeeeeeeee commented Mar 3, 2018 • edited Loading

JsBergbau commented Mar 3, 2018

plscarrymeeeeeeee commented Mar 3, 2018

JsBergbau commented Mar 3, 2018 • edited Loading

LostSoulfly commented Mar 4, 2018 • edited Loading

plscarrymeeeeeeee commented Mar 4, 2018

JsBergbau commented Mar 4, 2018 • edited Loading

LostSoulfly commented Mar 4, 2018 via email

LostSoulfly commented Mar 4, 2018

samu01 commented Mar 5, 2018

JsBergbau commented Mar 5, 2018

samu01 commented Mar 9, 2018

LostSoulfly commented Mar 11, 2018

LostSoulfly commented Mar 17, 2018

LostSoulfly commented Mar 18, 2018

JsBergbau commented Mar 24, 2018

LostSoulfly commented Mar 24, 2018 via email • edited Loading

JsBergbau commented Mar 24, 2018 • edited Loading

LostSoulfly commented Mar 24, 2018 via email

JsBergbau commented Mar 24, 2018

LostSoulfly commented Mar 31, 2018 • edited Loading

JsBergbau commented Apr 9, 2018

LostSoulfly commented Apr 9, 2018 via email

JsBergbau commented Apr 10, 2018

plscarrymeeeeeeee commented Feb 12, 2018 •

edited

Loading

cowboyfoggy commented Feb 12, 2018 •

edited

Loading

samu01 commented Feb 13, 2018 •

edited

Loading

LostSoulfly commented Feb 22, 2018 •

edited

Loading

JsBergbau commented Mar 3, 2018 •

edited

Loading

plscarrymeeeeeeee commented Mar 3, 2018 •

edited

Loading

JsBergbau commented Mar 3, 2018 •

edited

Loading

plscarrymeeeeeeee commented Mar 3, 2018 •

edited

Loading

JsBergbau commented Mar 3, 2018 •

edited

Loading

LostSoulfly commented Mar 4, 2018 •

edited

Loading

JsBergbau commented Mar 4, 2018 •

edited

Loading

LostSoulfly commented Mar 24, 2018 via email •

edited

Loading

JsBergbau commented Mar 24, 2018 •

edited

Loading

LostSoulfly commented Mar 31, 2018 •

edited

Loading