juicypasta / claymore-no-fee-proxy Goto Github PK

Ignore me for now :)

It would be nice to include the versions with wich the miner has been tested.

Latest current is v11.0

It seems claymore is actually connecting to a SSL Servers.

Running wireshark without claymore and using pure Ethminer, and then with claymore, there is a distinct difference. Anyway to MitM the SSL? - I have trust issues, and with this SSL running. :(

I checked - 9.6 and 9.7 are the same.

Also, I see routed DNS packets and connections, which makes me think he is running his own DNS comparisons.

I'm talking about this miner: https://bitcointalk.org/index.php?topic=647251.msg7236047;topicseen#msg7236047
I try it and it starts and everything seems to be ok but I don't know how can I check if it's working or not

Thanks!

Claymore ( v11 ) gives messages about detection of local proxy.
There are two ways, it could detect local proxy, one would be checking IP address ( which fake wan etc solutions could work)
second would be ( I'm imagining ) checking latency during mining flow, especially initial connection state ( like pinging a sever , local servers will be faster to ping ).
So, it is possible to add some latency to proxy would prevent this detection ( and possible Claymore punishment )

On the static routes page of your router, such as OpenWrt, you can create a route to a WAN IP and have the miners set to this, then point the static route to a local IP like so:

Then you just set up the same IP on Windows / Linux for this WAN IP and the LAN IP like so:

Then you will see this in Claymore:

And this in Proxy:

Hi,

I'm on ubuntu.

running proxy
python stratum_proxy.py 0.0.0.0 8008 asia1.ethermine.org 4444 ETHER_ADDRESS

mining

./ethdcrminer64 -epool 123.45.67.89:8008 -ewal ETHER_ADDRESS.miner1 -epsw x -mode 1 -ftime 10

I have set up 123.45.67.89 to point to 0.0.0.0.

I can telnet 123.45.67.89:8008 with no problem.

But I'm getting
ETH: Job timeout, disconnect, retry in 20 sec...

Any ideas what went wrong?

Hello congratulations,
I'm trying to use with claymore 9.4 gpu.
However the format is different from the wallet.

I'm tending like this:
Windows 10 terminal as admin and Bytecoin coins
my pool http://bcn.bbmv.online/en.html#

Stratum_proxy.py 127.0.0.1 8008 bcn.bbmv.online 7777 MYWALLLET

The daemon runs ok.

But the address of the fees appears in the host pool

I'm starting claymores like this:
NsGpuCNMiner94 -o stratum + tcp: //127.0.0.1: 8008 -u MYWALLLET -p x

My wallet has this format here

24yWY3MTJiQQUcMwkRGTrTVteWwGbyhNrigvupkncSYaAXggM5z5Xhm43TLwfNxiN7MzWpYfdewWFAed5GMMmdEmHK5UT4o

He comes to appear on the console that

{"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"809534694370813","job":{"blob":"010094bebdcc05ebe3ec89b90d1688c3a173ba654aa47c368e217e919ada7979e0a7586ec2e224000000007011892f2495bcb1ea53a78afedc4a40893479ab8a4081ef139dae904a36e82201","job_id":"954558903560973","target":"b88d0600"},"status":"OK"}}

[-] budder - {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"809534694370813","job":{"blob":"010094bebdcc05ebe3ec89b90d1688c3a173ba654aa47c368e217e919ada7979e0a7586ec2e224000000007011892f2495bcb1ea53a78afedc4a40893479ab8a4081ef139dae904a36e82201","job_id":"954558903560973","target":"b88d0600"},"status":"OK"}}

So I guess it's just some adjustment.
If you can help me, I'm very grateful.
Thank you for your help

Hello,
Sometimes the server is down so that it's bettery to have some alternative servers to retry if it failed several times. I can add that feature to your code.

Hey :)
I used the previous version since a few days ago and edited the code myself to use the correct worker.
Now there's this new version and with this one I get

[!!] Failed to listen on 127.0.0.1:portnumber
[!!] Check for other listening sockets or stopping mining - datecode

but the script seems to work I think.
IMO it has to do with removing/altering the receive_first part, because I can't think of anything else?

extra info: I've edited the claymore epools.txt file and replaced all nanopool servers with "fake" ones, which I also added to the hosts file in Windows.

Any solution or reason why I see this message?
BTW: I also re-added my previous change about entering the worker_name via command line, but this is not causing the message.

Hello, I'm new to this program but I dont know if it's working with new Claymore 9.7

I had this "error" when mining

Miner detected that you use local pool or local stratum proxy.
This mode is not currently supported and will cause more stale shares.

My fake pool is dwarfpool with correct config in host file, stratum_proxy.py and Python 2.7.13 installed. My real pool is nanopool.

It's a problem? Thanks.

How do I add ./stratum_proxy.py 0.0.0.0 8008 eth-eu2.nanopool.org 9999 0xB7716d5A768Bc0d5bc5c216cF2d85023a697D04D
so it will auto start up in window 10

Update: (ignore stale shares - will test WAN faking from other thread):

Running 9.6 - testing it out, I have noticed that I am getting a marked increase of stale shares (see screenshot)

I get the warning (as per the other issue and the doc about a local address/proxy) and ignored it, but
there is a 10% stale share in a few places - see screenshot (the empty spot in the middle is the changeover to proxy)

This may be early days, I will watch and see - this may be dag file swap related or perhaps a connection issue to ethermine - I found I had connection issues to ethermine with the "may be temporary" message.

Also, are you averse to a pull request that will allow failovers (e.g. eu1 or eu2 if main fails to connect?) in the section where it has the "may be temporary" message?

Works with claymore 11.5?

I'm running Claymore 9.7 with the new v1.1 proxy, using fake WAN addresses and mining at ethermine.org. I restarted my rigs after setting it all up and the good news is I don't get the local proxy warning any more and the fee address swap is working.

But the number of shares received by the pool has dropped (see screenshot). I understand the effective hashrate varies a lot and Claymore and the pool's reported rate are the same but the actual shares received in the bottom graph before using the proxy were ~380–430 and with proxy I'm getting ~330–390.

Is this expected? Maybe something to do with how Claymore processed his fee's shares? Or is there a known slowdown due to using the proxy? Or something else?

Hello
i mine DBIX it's same ETh i redirect all ports to 8888 and edit the host file with list of eth pool !
So my issue is the proxy work only on this pool dwarfpool.com
i want the shares goes to my eth wallet on nanopool
this command i used

netsh interface portproxy add v4tov4 listenport=3333 listenaddress=127.0.0.1 connectport=8888 connectaddress=127.0.0.1 netsh interface portproxy add v4tov4 listenport=9999 listenaddress=127.0.0.1 connectport=8888 connectaddress=127.0.0.1 netsh interface portproxy add v4tov4 listenport=4444 listenaddress=127.0.0.1 connectport=8888 connectaddress=127.0.0.1

then i run the proxy with port 8888
127.0.0.1 8888 eth-eu2.nanopool.org 9999 False

then i got this error
http://prntscr.com/fty04k
but when devfee loop goes to dwarfpool.com it works
http://prntscr.com/fty0p8

wondering am i doing something wrong ?

Thanks

Hi JuicyPasta,

thanks for your mining proxy to stop greedy Claymore from getting too much money.

In your code you set

def receive_from(connection):

    buffer = ""

    # We set a 2 second time out depending on your
    # target this may need to be adjusted
connection.settimeout(0)

What background has setting "connection.settimeout(0)" ?
https://docs.python.org/2/library/socket.html

socket.settimeout(value)¶

Set a timeout on blocking socket operations. The value argument can be a nonnegative float expressing seconds, or None. If a float is given, subsequent socket operations will raise a timeout exception if the timeout period value has elapsed before the operation has completed. Setting a timeout of None disables timeouts on socket operations. s.settimeout(0.0) is equivalent to s.setblocking(0); s.settimeout(None) is equivalent to s.setblocking(1).

New in version 2.3.

If you don't set this the call is in so called blocking mode, means it returns only when there is new data. So CPU is used as little as possible.

When using this you could avaoid time.sleep(0.001) in 170
btw. I've changed to time.sleep(0.01) and now have reduced CPU usage a lot.

So do you have a special reason for the command in non blocking mode? Normally when programming network functions I work in blocking modes. Thus programs need a little CPU as possible.

Hello,
I try to set up your proxy (Ver 1.4.0) with Claymore (Claymore.CryptoNote.GPU.Miner.v9.7.Beta.-.POOL).

This is my host file :
194.1.1.10 xmr.cryptofake.fr

My proxy conf file :
{ "local_host": "xmr.cryptofake.fr:8888", "pool_address": "xmr.crypto-pool.fr:8443", "wallet": "<MywalletAdress>", "worker": "", "ssl": true }

My start.bat for Claymore :
setx GPU_MAX_ALLOC_PERCENT 100 NsGpuCNMiner.exe -o stratum+tcp://xmr.cryptofake.fr:8888 -u <MywalletAdress> X -p x

Claymore return this :
https://i.imgur.com/duSv6gh.jpg

I certainly made a mistake but I do not see where.
Thank's for helping.

Log console output to a log file.

Hi,

for dual mining should we setup 2 stratum proxy one for ETH and one for the other coin?
in both case should we use the same eth_address we own :
./proxy.py [localhost1] [localport1] [ethhost1] [ethport1] [same_eth_address]
./proxy.py [localhost2] [localport2] [otherhost2] [otherport2] [same_eth_address]

Thanks.

Title says it all.

Hi,
do You ready with Zec version ?
You make a lot people Happy !!!

Hi,
Claymore ETH dual miner 11.0 trying to mine devfee on SSL protocol in port 5555 so the proxy doesnt work.
Any chance to get it work?
Thank you!

Hello,

I'm primarily using linux for mining, but I'm a linux noob, and am not quite sure how to set this up. I've already got it running successfully on Windows. Thanks

What's wrong? How to fix?

[+] Received incomming connections from 127.0.0.1:51257[+] Auth in progress with address: MyWallet/rekt

[+] Received incomming connections from 127.0.0.1:51258
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51259
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51260
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51261
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51262
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51263
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51264
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51265[+] Auth in progress with address: MyWallet/rekt

[+] Received incomming connections from 127.0.0.1:51266
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51267
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51268[+] Auth in progress with address: MyWallet/rekt

[+] Received incomming connections from 127.0.0.1:51269
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51270
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51271[+] Auth in progress with address: MyWallet/rekt

[+] Received incomming connections from 127.0.0.1:51272
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51273
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51274
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51275[+] Auth in progress with address: MyWallet/rekt

[+] Received incomming connections from 127.0.0.1:51276
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51277
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51278
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51279
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51280
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51281
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51282
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51283
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51284
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51285
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51286
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51287
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51288
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51289
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51290
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51291
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51292
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51293
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51294
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51295
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51296
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51297
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51298
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51299
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51300
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51301
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51302
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51303
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51304
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51305
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51306
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51307
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51308
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51309
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51310
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51311
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51312
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51313
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51314
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51315
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51316
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51317
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51318
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51319
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51320
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51321
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51322
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51323
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51324
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51325
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51326
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51327
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51328
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51329
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51330
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51331
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51332
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51333
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51334
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51335
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51336
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51337
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51338
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51339
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51340
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51341
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51342
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51343
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51344
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51345
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51346
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51347
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51348
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51349
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51350
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51351
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51352
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51353
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51354
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51355
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51356
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51357
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51358
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51359
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51360
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51361
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51362
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51363
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51364
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51365
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51366
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51367
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51368
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51369
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51370
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51371
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51372
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51373
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51374
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51375
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51376
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51377
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51378
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51379
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51380
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51381
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51382
[+] Auth in progress with address: MyWallet/rekt
[+] Received incomming connections from 127.0.0.1:51383

DevFee: ETH: Stratum - connecting to 'eth-eu.dwarfpool.com' <127.0.0.1> port 8008
03:49:30:256 710 send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA", "x"], "id": 2, "method": "eth_submitLogin"}

03:49:30:261 710 DevFee: ETH: Stratum - Connected (eth-eu.dwarfpool.com:8008)
03:49:30:436 710 got 77 bytes
03:49:30:440 710 buf: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}

03:49:30:445 710 parse packet: 71
03:49:30:448 710 ETH: Share rejected (13859 ms)!

03:49:30:451 710 new buf size: 0
03:49:30:815 2c50 ETH: checking pool connection...

python stratum_proxy.py 127.0.0.1 8008 eu1.ethermine.org 4444 0xB7716d5A768Bc0d5bc5c216cF2d85023a697D04D

Hope to support ClaymoreZcash。Thank you

Claymore uses random different addresses.
How do I set this up for that?

So far I have seen 3

us1.ethpool.org:3333
eth-eu.dwarfpool.com:8008
us1.ethermine.org:4444

Launch multiple proxies?? That could get messy

https://github.com/ethash/eminer-release

I'm wondering if this project is just wrapping claymore+nofeeproxy in one app and redirecting the fee to their authors.

Thanks again for your code open source ：）

ETH: Authorization failed
: {"id":2,"result":null,"error":[101,"NeedSubscribed",null]}
ETH: Job timeout, disconnect, retry in 20 sec...

I m using btc pool

I get the error server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...

I am using windows and configured it as you said.

Any ideas?

Hello.
I updated to the latest version of proxy and set the parameter as stratum_proxy.py 127.0.0.1 8008 eth-us-west1.nanopool.org 9999 0x05a54walet and now in the proxy terminal window it doesn't show the log anymore yet I still get "rekt" worker activated about once every hour or two.
So I was wondering if it's a normal behavior because previous version did log every instance of the wallet switching.

Now it just shows "auth in progress with following wallet...."

Please tell me if I am doing something wrong here.

Also the reported hash rate stays the same however about once an hour the calculated hashing drops from 190 down to 125 then after 10 mins or so bounces back up.

The following error happens approx every 3 hours. I am keeping wireshark open so I can send PCAP data with it.

Traceback (most recent call last):
File "c:\Python27\lib\threading.py", line 801, in __bootstrap_inner
self.run()
File "c:\Python27\lib\threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File ".\proxy\stratum_proxy.py", line 121, in proxy_handler
remote_socket.send(local_buffer)
error: [Errno 10053] An established connection was aborted by the software in your host machine

Any idea how to go about making it work?

Work with claymore 10.

Thanks for your work.

The latest claymore code showed the red message "Miner detected that you use local pool or local stratum proxy. This mode is not currently supported and will cause more stale". Does that affect to the total of the shares I receive?
P/s: my "rekt" is receiving some shares from faking the devfee address.

Thanks.

Hello
is this proxy support monero ?

Thanks

Hello. I've got this :

DevFee: ETH: Stratum - connecting to 'eu1.ethermine.org' <127.0.0.1> port 4444
DevFee: ETH: Stratum - Connected (eu1.ethermine.org:4444)
ETH: Authorization failed
: {"id":2,"result":false,"error":null}
Stratum - reading socket failed 10038, disconnect
DevFee: ETH: Job timeout, disconnect, retry in 20 sec...

random ip adress connect to my proxy

149.172.52.168:35647

how can i modify the proxy that he only accept ip adress on a whitelist?

Hey guys,

I've read a lot of claymore's miner fees in the past and want to find a way to avoid them. After i've read your guide to set am JuicyPasta Clamore Proxy im a little frustrated in general. Even after several hours of trying I'm not able to set up your Proxy. I understand your first steps and set up a fake wan by adding a fake adress to my ipv4-adapter (194.12.12.2). But I don't know what to do next. Phyton is installed and I've been downloading your stratum_proxy.py-file. Could you please specify what to do next. I know I'm a bit nooby into that but I like your concept and think even more People would use it if it woult be not that complicated.

Curruntly I'm dual mining on eu1.ethermine.org:14444 and sia.eu.nicehash.com:3360

I would like to donate if you could help me to find a solution. Thank you.

I don't understand. Claymore IS mining DevFee on my real pool and port.
I am mining ETC on us1-etc.ethermine.org:4444

When DevFee appears he is also mining on us1-etc.ethermine.org:4444
So if I don't have it in the hosts file how do I redirect it to my address?

Thank you for this tool and help.

Hello guys. I am trying this no fee proxy. I am having a hard time getting it to work.

I installed python. I edited the python settings and included my wallet there.

I added the "127.0.0.1 eth-us-west1.nanopool.org" to the hosts file

I edited the claymore start command to connect to the fake address "EthDcrMiner64.exe -epool eth-us-west1.nanopool.org:8008 -ewal 0x05a54a................"

I started daemon.
I then started claymore and when it tries to connect to the nano pool it tells me it is unable to connect and it restarting.

I am running a Windows 10 x64. Python 2.7

Please see attached screenshots of the claymore and proxy.

What to do?

Thank you.