Open UserDC-LeGrand opened 2 years ago
So you are saying that when -Poolname zpool
curvehash does not appear? The likely reason why is because some other parameter is causing it to be skipped over, such as the pool does not have enough hashrate or is not finding enough blocks to your parameter specifications (-min_blocks
)
I can try to add some thing to try to help Swarm find the miner it needs to unban that it banned, but I'm not sure if anything concrete can be made.
-Bans and bans
command edit the .json in config\pools.
Swarm doesn't do that, because it bans that specific miner combination. If you look at the files in the folder .\timeout and the files in .\config\pools you will see what I mean...The format is just very different.
I came up with an idea to make a easier workaround to the fundamental issue, and that is to enumerate the bans that SWARM does.
....
ban 1: cdredge has been banned mining kawpow on zergpool
ban 2: t-rex has been banned mining x16r
ban 3: lolminer-n has been banned mining equihash144/5 on zpool
On get stats
screen.
This way I can do:
bench ban number 1
And Swarm will search .\Timeout folder and remove it that specific ban based on the enumeration.
Great one!
From: @.> Sent: October 28, 2022 2:48 AM To: @.> Cc: @.>; @.> Subject: Re: [MaynardMiner/SWARM] Enhance the bench command to include pool (Issue #418)
I came up with an idea to make a easier workaround to the fundamental issue, and that is to enumerate the bans that SWARM does.
....
ban 1: cdredge has been banned mining kawpow on zergpool
ban 2: t-rex has been banned mining x16r
ban 3: lolminer-n has been banned mining equihash144/5 on zpool
On get stats screen.
This way I can do:
bench ban number 1
And Swarm will search .\Timeout folder and remove it that specific ban.
— Reply to this email directly, view it on GitHubhttps://github.com/MaynardMiner/SWARM/issues/418#issuecomment-1294537075, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXXBVDKZWATNL54HR4L2M5TWFNZLPANCNFSM6AAAAAARNO4EGM. You are receiving this because you authored the thread.Message ID: @.***>
In the use case where Poolname has two or more pools, and hence two choices for an algo, could the bench miner be expanded to include a 3rd argument to provide a specific pool name, such as:
bench miner wildrig-n-1 curvehash zpool ...or.... bench miner wildrig-n-1 curvehash zergpool
Also, for some reason, it is imposbble to bench curvehash on zpool, even with -Poolname=zpool setting only ... This works on zergpool though.
Please note: Running swarm_start_curvehash.sh test script pointed at zpool.ca works perfectly.