Dayun Zig Z1 - Lyra2Rev2 6.8GH/s Asic miner

[lennujuht]

Hi, has anybody tried pool https://www.mining-dutch.nl/  

Expected Profit 24H   0.00157334 BTC   

[zgzg]

prohashing.com last 3 day 24h profit = 0.0011   

[newgencryptomaker]

What about nlpool profits 24hours

[Pedram_01]

The device was destroyed. Profitability is zero. Six thousand dollars were lost

https://imgur.com/a/hII7Las

[lennujuht]

What about nlpool profits 24hours

NL pool 24hr 0.0027

[Wolf6270]

The device was destroyed. Profitability is zero. Six thousand dollars were lost

https://imgur.com/a/hII7Las

Apparently Dayun company stopped sponsoring the asikminervalue service and they showed real profit, not fake =)))
I personally dig the coin MONA, and sell on the stock exchange, so the profit is higher! I dig on F2POOL
https://www.f2pool.com/

[metnet]

The device was destroyed. Profitability is zero. Six thousand dollars were lost

https://imgur.com/a/hII7Las

Apparently Dayun company stopped sponsoring the asikminervalue service and they showed real profit, not fake =)))
I personally dig the coin MONA, and sell on the stock exchange, so the profit is higher! I dig on F2POOL
https://www.f2pool.com/

about asicminer value.com
so it is with my effort. but too late.

how much money do you get from mining mona.

[metnet]

@zigminer

frequently one or two hashboard goes 0 (zero). if it goes to 0, it stays long time unless device restart.
would you please make it new image that detect low hashrate and zero and restart just one or two hashboard separately.

thanks in advance.

next version will solve this bug.

thanks @zigminer

Dear @zigminer

when will we have new image version.

@zigminer

where are you? we are waiting new image. your site is under construction. please give a sound.

[Phuripat]

@zigminer

frequently one or two hashboard goes 0 (zero). if it goes to 0, it stays long time unless device restart.
would you please make it new image that detect low hashrate and zero and restart just one or two hashboard separately.

thanks in advance.

next version will solve this bug.

thanks @zigminer

Dear @zigminer

when will we have new image version.

@zigminer

where are you? we are waiting new image. your site is under construction. please give a sound.

No sound from heaven...

[JFoxOne]

Dayun again works with ASIC Hub.

Previously blocked by firmware, unfortunately.  

[christiano88]

The latest firmware for z1+ looks like it is stealing hashrate, a LOT of it. I had it set to 1000 freq with auto freq to 1, and it averaged 1.5gh while still consuming 1170w of power continuously, rejected shares/errors were under 3%. So for that power, the hashrate should have been 4 times higher, I think the hashrate is redirected, getting screwed once with the initial sale wasn't enough...now we get screwed with this.

[metnet]

The latest firmware for z1+ looks like it is stealing hashrate, a LOT of it. I had it set to 1000 freq with auto freq to 1, and it averaged 1.5gh while still consuming 1170w of power continuously, rejected shares/errors were under 3%. So for that power, the hashrate should have been 4 times higher, I think the hashrate is redirected, getting screwed once with the initial sale wasn't enough...now we get screwed with this.

interesting idea . are you sure with it. how many hours did you try. i heard about last version avg hashrate g/h between 5 and 6.

[astraleureka]

What makes you so sure that it's being stolen? Have you seen it sending shares to a foreign pool? Have you tried reducing the OC? It is very possible it is just malfunctioning, error reporting is not really guaranteed to work properly, especially when overclocking.

[christiano88]

I think I figured out the problem, it was switching pools like crazy (I had the same pool 3 times in the cases)...but shouldn't it stop consuming while switching, and the end result shouldn't it be the same? Also it was mining on very low difficulty from what I could see, but the rejects were still low...Anyways, put a version that is 2 releases back and it works now, it stopped jumping around, and shows OK hashrate (not the best but acceptable). The bad thing now is that I can't spin down the rpm on the fans...so no way to keep it in the house.

[Andartis]

Good news for followers in this thread ,AKminer is selling Whatsminer D1 with very competitive price ( Jan pre-order batch )
https://www.akminer.com/all-products/new-dcr-master-whatsminer-d1-48th-s-with-psu-shipout-ships-on-january-20-30-2019

WOW thats great news!! Very competition, fastest ROI.
Can I flash my Z1+ with the competetive priced Whatsminer D1?

[Phuripat]

https://www.zigminer.com/image/cache/catalog/banner/banner_z1+-1920x780.png

see this, truely spec Zig Z1+ is only 7.0Gh/s but in realized run only 6.5-6.6Gh/s

[astraleureka]

You probably need to set fixed difficulty, Z1+ does 7.2GH/s and higher if configured properly.

[metnet]

I have been using Zig1 since release.  All of a sudden I cannot load the dashboard anymore and so cannot get my Zig1s to operate.  Every time I try to load the page it is showing  "Internal Error Occurred".  Can anyone advise me on how to fix this?"

check your zigminer ip address

[Pedram_01]

Bad news

This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.

[areyouathief]

Bad news

This release contains the proposed upcoming Vertcoin main network hard fork to the new Lyra2REv3 mining algorithm at block 1080000 in order to rid the network of the current generation of Lyra2REv2 ASICs and FPGAs. It also contains the hard fork for the test network which already occurred at block 158221. The related pull request is here: #72. The difficulty will be forced down to 0x1b0ffff0 for 10 blocks after the fork before the usual KGW difficulty adjustment algorithm kicks in again to prevent the network from stalling due to the large expected decrease in network hashrate post-fork.

Monacoin, the last hope...