Topic: Zilminer - mine POW coin in dual mine mode with almost no power use!!!!! - page 10. (Read 6567 times)

blockchain today was stuck at xx99 block, and for start/stop its worst case solution as API is switiching miners

btw can u explain what each of these do? --work-timeout 10800 --report-hr=1 --clear-dag --farm-recheck 15000

work-timeout is triggered to reconect if no work is received in 10800sec
--report-hr=1 report hashrate to proxy
--clear-dag  empty GPU memory before main miner is restarted so it has full 4/8/11GB of ram available
--farm-recheck ask for new work each 15sec if no solution is found

hello recently i had few issues, using zil miner + ethminer 0.18rc0 mining zil+eth on 4/8gb card.

- hash hasnt been reported on ETH pool
- when zil pow started it stoped eth ethminer and started mining, but has was 0 for all cards.
- what is --pow-earlier good for?

my bat files was
"zilminer.exe --pow-start stop.bat --pow-end start.bat --pow-end-at-startup -P zil://[email protected]:5000/api -G"
"ethminer.exe -P stratum1+tcp://[email protected]:9999/worker/email -G"

i tweaked bat files liek this as i have few 4GB cards so probably would need clear dag as ETH has 3+gb on widnows?:

"zilminer.exe --pow-start stop.bat --pow-end start.bat --pow-end-at-startup -P zil://[email protected]:5000/api -G --work-timeout 10800 --report-hr=1 --clear-dag --farm-recheck 15000" (addded few parameters, are these ok?)
"ethminer.exe -P stratum://[email protected]:9999/worker/email -G"   (removed stratum1+tcp and left only stratum)


btw can u explain what each of these do? --work-timeout 10800 --report-hr=1 --clear-dag --farm-recheck 15000

P.S. i have checked your site and there is "PoW is running" message more than 10mintues already..
also on explorer https://explorer.zilliqa.com/home there is still DS 289 and TX block 28899 for long....any issue?

EDIT: web says PoW is still running after 1+hour and explorer still stuck on 28898 block
EDIT2: seems it is now moving again, block 28890 and i also got some accepted shares and some rejected shares.

Well duno, there is a reason as no one used sharding so far, also their node do not receive rewards but do limit community nodes out, their plan is in steps shut down guard nodes and let more community nodes in as network progress and grow

Also I am here for profit same as miners, time will tell at lest you don`t burn a lot power in this, from tech point side i think no one can say till we don`t see stability of network, sharded network for sure will offer a lot more space for transactions but will it be safe enough i don`t know

As transactions are still disabled, as miners are lazy to set up miners, as investment in pool are huge, diff is still pretty low


True, but I invested a lot more
server + 160 dual core VPS for nodes and a lots of time tweaking it so node receive some rewards per accepted share (no node do not get reward per each share as shard are very limited in space and atm devs nodes are keeping ~70% of network)

My interest is for this to work...

it feels risky for how long we have to mine to be sure we will be paid.... however, i feel the risk/reward ratio makes it worthwhile. my opinion.

How can it be waste of effort? only if you think zilliqa will be worthless or pool will not payout after bootstrap period

atm one mining rig mine ~5-6 shares per day at current price its ~0.7$, as you lose almost nothing from mining primary coins, zilliqa mining is almost free on top on your coin

pls read about zilliqa mining, network diff is 30-70ghs, POW is 8 times a day with usual rig of 180Mhs you  would make 3-5 shares per day, depending on luck

"it works out of box with bminer" i didnt understand what you mean ?

please if you can describe little more ?

i had tried as ur miner pack, just edited wallet address which i registered on the mentioned pool.
but no luck always gets 0 share , just shows hashrate on pool nothing else.

br,
bdmi9

I used keys --pow-start stop.bat --pow-end start.bat
stop.bat taskkills claymore before hashing zil, start.bat restarts it again after pow time finished

hello,


Some drivers crash, i assume during swapping of miners, once the drivers crashes, the new POW after does start but gets 0 hash for all cards, even though it appears only one card was affected by the driver crash. then this rig will not add any hash during POW  until fixed.... one of my rigs seems to need a restart, one seems just restarting the miners fixes it.

would this "--work-timeout 10800"  address this problem or a different problem

What? What kills claymore? I don´t understand this answer sorry.

Look in the miner window when it starts POW. You see it will hash for 2 - 3 minutes and then, nothing for 3 minutes, no getwork. So this 3 minutes are lost time, with the pow end command it will reduce the time after the last getwork.

Your hashing power is 132mh on pool side, so it is total that no share found after this short time. Zilminer has not the same hash power like claymore or phönixminer.

no, it kills Claymore with bat file.
0xb45db9d35392b94ecf66accf0b2079fd891f5547

After the last getwork it needs around 2 - 3 min to start the primary miner, this 30 seconds reduce this time. You say your mining time is around 93% and 7minutes every pow, so this is the answer to reduce the 7minutes. 
An it is normal that you not find a share every POW. Sometimes i find only 1 share after 3 - 4 POW.
It is a new mining concept so give it a bit time.

What is your address? Is the miner hashing in POW? Some of my cards cannot mine with zilminer, because it cannot handle the OC settings, but on claymore or phönixminer it is stable for over 1 year.

sxemini testing on 8 card-rig, about 220 mhs. how can 30 seconds help if it cannot manage to find a share during 5+ minutes?

Tweaking your start.bat with command --pow-end-timeout 30. I am at 96 - 96,5% mining time at main coin.

How much hashrate?

really, works well on rigs with blockchain drivers. although I got 0 shares during last pow session

upd waited for next pow time. it was 1.40 instead of 2.5-3 hours and main miner was offline for almost 7 minutes instead of 30 seconds. Soooo it's about 93% downtime instead of 99.95%.
am I doing something wrong again or promises are a little bit embellished?
also still 0 shares accepted after second pow time )

yes 19.x amd driver not working

a shame for radeon VII owners 

Some driver on some AMD card are no good, some are happy with blockchain driver from august and some use newer

zil miner is a fork of ethminer so same issue/solutions

if anyone have issue that miner stop to receive new work pls add command at zilminer:
--work-timeout 10800

tried zilminer on Vega64 with latest drivers and W10 LTSC - system hangs up after "dag generated" message even if no other miner is running. Claymore's dualminer works stable on this PC. what am I doing wrong?

When zilliqa devs enable transactions after bootstrap mode atm 30 march is the plan