Zilminer - mine POW coin in dual mine mode with almost no power use!!!!!

[Marvell2]

After mining it should be red as dag is deleted so you can mine primary coin

Also why don`t you put all miners in same folder, also main miner bat should include:
taskkill /F /IM miner_name
miner.exe

so there is no chance to start primary miner 2x

AMD rigs works but some don`t and they should use zill swicher till better miner is not made

switching works fine on my AMD rigs, main issue is multiple command windows i guess i could put them all in same folder

Vega rigs are the ones that seem to crash

[1713991133]

1713991133

[1713991133]

1713991133

[1713991133]

1713991133

[reb0rn21]

This might fix it:
taskkill /f /im miner.exe >null

[Marvell2]

This might fix it:
taskkill /f /im miner.exe >null

I had that, int there, before , I had copied from the files you linked me.

Putting them in the same folder works for now , I hate that tho

*** ok putting it in same folder fucked up things worse, now both ethminer and zlminer run in the same window wtf lol

[sprstoner]

*** ok putting it in same folder fucked up things worse, now both ethminer and zlminer run in the same window wtf lol

i had that problem with some miner software, try doing your bat like this:

START cmd /c "miner.exe all your algo, pool, address, and rig info"

starts the new window for your bat.. i learned that from the master

[Marvell2]

Too many issues , Gona try and set up a node from scratch or something see if that helps

[reb0rn21]

Nvidia works gr8 with zilminer in dual mode, zero issue

AMD also works gr8 with zil switcher for solo or pool mine is same if you wana dual mine you need to setup one of those, both works and switch when node send the POW start and POW end whatever it is pool or solo, its the same

[RuMiner]

I just want the window to closer otherwise i ended up with 20 cmd promps

use call some.bat instead of start some.bat, both miners work in one console window idk how but looks nice
this is Claymore's dualminer along with zilminer

[Marvell2]

I just want the window to closer otherwise i ended up with 20 cmd promps

use call some.bat instead of start some.bat, both miners work in one console window idk how but looks nice
this is Claymore's dualminer along with zilminer

Wait lol I saw this too on my setup but how do you know it’s working lol makes no sense to me.

I got my nvidia rigs to work by dumping awesome miner for now till they update, one thing looks like I have

30 accepts and  45 submitted so far with 17 6 card rigs 180 MHz per rig , what would be the earnings ? Is it 9 zip per accepted share ?

[RuMiner]

Wait lol I saw this too on my setup but how do you know it’s working lol makes no sense to me.

it works stable on 5 rigs more than a week already. both miners give shares, primary coin pool doesn't even notice those dumps on graph. what else do you need? )

[Marvell2]

Wait lol I saw this too on my setup but how do you know it’s working lol makes no sense to me.

it works stable on 5 rigs more than a week already. both miners give shares, primary coin pool doesn't even notice those dumps on graph. what else do you need? )

so do you stop the claymore miner ? when POW for ZL starts ? , I know you cant run both together or claymore hash goes down or sometimes even crashes

most rigs I keep getting the error - Zlminerhas stopped working - a problem has caused the program to stop working

hard crash of zlminer and primary miner

[RuMiner]

@Marvell2, yes, bat files stop Claymore during pow window, than run it back. I've coped with crashres via windows errors log as wrote some pages ago. scheduler runs crashed miner again, but it's a rare thing itself

[Marvell2]

@Marvell2, yes, bat files stop Claymore during pow window, than run it back. I've coped with crashres via windows errors log as wrote some pages ago. scheduler runs crashed miner again, but it's a rare thing itself

seems to happen constanltly to me

[reb0rn21]

ATM current diff is 68Ghs, some 450Mhs is needed for one share, we have ~16 epoch now, if all stay stable 6 card rig should do ~6 shares per day, with constant diff rejects should be less, if diff start to go insane again rejects will go up also

[Rabinovitch]

Which parameter values should I use at rudnik? My current values are:

Code:

--farm-recheck 15000 --work-timeout 10800

But I also saw people use these values:

Code:

--max-submit=1 --farm-recheck 10000 --work-timeout=7200 --farm-retries=10 --retry-delay=10

Which values are best?

[reb0rn21]

Use this one
--farm-recheck 15000 --work-timeout 10800

Network is today slow so expect less POW till zilliqa devs fix it

[Rabinovitch]

There's something wrong I guess:

Code:

m 06:43:54 zilminer 54:02 A1:R6 0.00 h - cu0 0.00
 m 06:44:04 zilminer 54:03 A1:R6 0.00 h - cu0 0.00
 m 06:44:14 zilminer 54:03 A1:R6 0.00 h - cu0 0.00
 X 06:44:19 zilminer No new work received in 10 800 seconds.
 i 06:44:19 zilminer Disconnected from rudnik.hopto.org [142.93.85.148:5000]
 i 06:44:19 zilminer No connection. Suspend mining ...
 i 06:44:19 zilminer Selected pool rudnik.hopto.org:5000
 i 06:44:19 zilminer Established connection to rudnik.hopto.org [142.93.85.148:5
000]
 i 06:44:19 zilminer Resume mining ...
 i 06:44:20 zilminer ZIL PoW Window Start
 i 06:44:20 zilminer Call system command: stop.bat

E:\Distrib\Zilliqa\zilminer_from_rudnik>taskkill /F /IM bminer.exe  1>null
 i 06:44:21 zilminer Send dummy work to init DAG
 i 06:44:21 zilminer Job: 00000000... rudnik.hopto.org [142.93.85.148:5000]
 i 06:44:21 zilminer Epoch : 0 Difficulty : 17.00 h
 i 06:44:21 zilminer Job: 00000000... rudnik.hopto.org [142.93.85.148:5000]
cu 06:44:22 cuda-0   Generating DAG + Light : 1.02 GB
 m 06:44:24 zilminer 54:03 A1:R6 0.00 h - cu0 0.00
cu 06:44:25 cuda-0   Generated DAG + Light in 4 067 ms. 6.98 GB left.
cu 06:44:25 cuda-0   Job: 00000000... Sol: 0x468d57d0cb86fc68
 m 06:44:34 zilminer 54:03 A1:R6 193.99 h - cu0 193.99
 m 06:44:44 zilminer 54:03 A1:R6 0.00 h - cu0 0.00
 m 06:44:54 zilminer 54:03 A1:R6 0.00 h - cu0 0.00
 m 06:45:04 zilminer 54:04 A1:R6 0.00 h - cu0 0.00
 m 06:45:14 zilminer 54:04 A1:R6 0.00 h - cu0 0.00
 m 06:45:24 zilminer 54:04 A1:R6 0.00 h - cu0 0.00
 m 06:45:34 zilminer 54:04 A1:R6 0.00 h - cu0 0.00
 m 06:45:44 zilminer 54:04 A1:R6 0.00 h - cu0 0.00
 m 06:45:54 zilminer 54:04 A1:R6 0.00 h - cu0 0.00
 m 06:46:04 zilminer 54:05 A1:R6 0.00 h - cu0 0.00
 m 06:46:14 zilminer 54:05 A1:R6 0.00 h - cu0 0.00
 m 06:46:24 zilminer 54:05 A1:R6 0.00 h - cu0 0.00
 m 06:46:34 zilminer 54:05 A1:R6 0.00 h - cu0 0.00
 m 06:46:44 zilminer 54:05 A1:R6 0.00 h - cu0 0.00
 m 06:46:54 zilminer 54:05 A1:R6 0.00 h - cu0 0.00
 m 06:47:04 zilminer 54:06 A1:R6 0.00 h - cu0 0.00
 m 06:47:14 zilminer 54:06 A1:R6 0.00 h - cu0 0.00
 m 06:47:24 zilminer 54:06 A1:R6 0.00 h - cu0 0.00
 i 06:47:28 zilminer Job: 00000000... rudnik.hopto.org [142.93.85.148:5000]
 i 06:47:28 zilminer ZIL PoW Window End
cu 06:47:33 zilminer Clear DAG Buffer
 i 06:47:33 zilminer Call system command: mine_grin_luxor.bat
 m 06:47:34 zilminer 54:06 A1:R6 0.00 h - cu0 0.00
 m 06:47:44 zilminer 54:06 A1:R6 0.00 h - cu0 0.00
 m 06:47:54 zilminer 54:06 A1:R6 0.00 h - cu0 0.00

BTW, why there are so many rejected shares here? I have PoWs Accepted=18, while PoWs Submitted=42. 42.8% of rejected shares! It's terrible!

[reb0rn21]

This is not POW coin but a lot more complex system each A share is max per one node, to understand you need to read whole white paper
In short we have 3-4 shards of 600 places max while the dev in there have over 70% of their guard nodes and we have rest if we manage to get full 600 POW submition in <1min time, over that imagine their diff retarget shifting 400% up just because we had 100+ A at 34Gh and next diff is 137Gh then on next POW we have 4x less shares and we always lose 600 accapted shares.... don`t ask me why they don`t have smarted diff retarget I am not zilliqa dev

On top of that all shares have <1min to be accepted by each node, so its a race and even there pool from verified accepted shares have 50% nodes that not get in shard so recejt for me is even more.... but its the way network work as this is not POW coin in any way

1. diff is low, many miners submit 600 shares in 10-15sec all shares after that are rejected as shard (600 nodes) is full
2. diff spike 4x we have no hash to make 600+ shares, we make 350-550A all that shares are rejected by network as we did not make 600 nodes (full network not just pool)
3. best case solution diff is same over a day then we can expect ~80% accepted and only rejects when we pass 40-50sec window if shard is full
4. 100% accepted is impossible that would mean 1min POW window took all miners to submit just 600 share no more nor less and all get in network fine

"06:44:21 zilminer Send dummy work to init DAG"

Also older zilminer use fake dag generation and generate a lot rejected shares so it be ready for next POW with almost zero diff (almost no GPU work done), thats why I say you need to watch only for accepted for you hash not rejected as they are part of this sistem

PS: they still work on network I hope they fix it soon

[Marvell2]

This is not POW coin but a lot more complex system each A share is max per one node, to understand you need to read whole white paper
In short we have 3-4 shards of 600 places max while the dev in there have over 70% of their guard nodes and we have rest if we manage to get full 600 POW submition in <1min time, over that imagine their diff retarget shifting 400% up just because we had 100+ A at 34Gh and next diff is 137Gh then on next POW we have 4x less shares and we always lose 600 accapted shares.... don`t ask me why they don`t have smarted diff retarget I am not zilliqa dev

On top of that all shares have <1min to be accepted by each node, so its a race and even there pool from verified accepted shares have 50% nodes that not get in shard so recejt for me is even more.... but its the way network work as this is not POW coin in any way

1. diff is low, many miners submit 600 shares in 10-15sec all shares after that are rejected as shard (600 nodes) is full
2. diff spike 4x we have no hash to make 600+ shares, we make 350-550A all that shares are rejected by network as we did not make 600 nodes (full network not just pool)
3. best case solution diff is same over a day then we can expect ~80% accepted and only rejects when we pass 40-50sec window if shard is full
4. 100% accepted is impossible that would mean 1min POW window took all miners to submit just 600 share no more nor less and all get in network fine

"06:44:21 zilminer Send dummy work to init DAG"

Also older zilminer use fake dag generation and generate a lot rejected shares so it be ready for next POW with almost zero diff (almost no GPU work done), thats why I say you need to watch only for accepted for you hash not rejected as they are part of this sistem

PS: they still work on network I hope they fix it soon

So the moral of this long story is only 600 shares get accepted total per 1 min window?

1 for each node that gets approved as a shard ? How do miners get paid then if the rewards go only to shards

[reb0rn21]

Depend limit is 2400 atm but many are guard nodes which should drop over time by devs, and you need full shard or we drop to 1800 nodes... so each Accepted is one node, reward is is not per share but only if node join shard and received in next 100 block zil reward (~27zil) that also depend on node reputation, network etc
I have no reward math per node nor per A, as many valid shares that are credited to miners are not getting node in shard for xx reason, you can read in white paper
All I do is calculate all rewards I get and adjust what I can pay to miners per accepted share

So in short you will get pay for each accepted share, even if node does not get in shard that is why reward is lower then 27zil as atm that rate is not fix and know to drop under 50% or more

PS devs announced update in few hours so chain should start to move soon again

[reb0rn21]

The network was updated this morning and its now stabilized again at 68Gh where there is less rejects

they slow down a chain a bit so less POW per day as we had 16 and now back to ~10-12