terraman

[uakc]

What is this for ?

var walletArray = [ "t1fJuHWrfcWnYMYyP9VAF96vRnvND2NziMG", "terraman",

[Mcracker]

this is the ewbf developer wallet. in yourWalletID you should replace on your wallet. DevFee going under the worker yourWorkerName.

[cannonballdex]

So are you saying we have to replace the var walletArray = [ "t1fJuHWrfcWnYMYyP9VAF96vRnvND2NziMG", "terraman", address with our own?

[cannonballdex]

Don't Waste Your Time. Hash rate dropped from 7.09 to 5.6 someone was getting paid but it wasn't me.

[Jaywizkid]

Don't touch the terraman wallet address, the code needs that line so that when the miner tries to send DevFee share to said wallet address it can intercept and redirect them to your wallet address instead.

The only things you need to change in server.js is

Var YourPoolAddress Var YourPoolPort Var YourWalletID

Optionally you can change

Var YourWorkerName = '1080tiDevFee'

This will make it easy to identify the exact worker that had it's DevFee's intercepted.

[cicicice]

@Jaywizkid sorry to bump this ancient thread, which does not matter really these days with the ASICs anyway, I am just running some small mining experiments. I am racking my brain to see the intention of the code here, but I cannot boil it down to one theory. Is the code supposed to show a different worker for the devfee and a different worker for the normal mining? Also, if "my pool" is supposed to be both in YourPool and RemotePool, why ask twice for the Port? Also, you say "you only need to replace YourXXX" but the code commentary says replace "remotePoolAddress". Now, I can see at least the intention of the IP. The intention is to actually connect to my pool IP without interpretation from the hosts file, there was danger of some vicious circle somehow. I can also see that the program could "reverse engineer" my packets to see my address but it is simpler to ask me what that was. I cannot immediately see why the "bad guys" address is there, maybe to make pattern matching easier? Because if you know which part of the traffic is the address it does not matter what other addresses are there in the traffic, you can always enforce my address and that's it. Finally, I think I can see why my pool has to be in hosts, but I am not sure. I think you wrote in another thread, my pool has to be intercepted, but mostly it doesn't. In most cases when the bad guys are sending traffic to other pools it will be intercepted, but once in a while they may send to my pool, which needs intercepting.

[cicicice]

Well, that was quick fun. With uncommon pools and ports, the script does not seem to work and says it will not work, my port is 6058 and the miner does not work when pointing to 127.0.0.1 because 6058 is not intercepted/redirected, more of bug than a feature. The MITM reports redirecting 127.0.0.1:3333/6666/8088/8008

Aha! It needs towards the end server5.listen(6058);