[ANN] ZERO - COMMUNITY TAKEOVER

[esbrave789]

Zero has a hard-coded option to use shielded transactions (Z) making it IMPOSSIBLE for anyone to track.
If I use zero to transfer, anyone can not see my transfer records, I understand so?

[1713908744]

1713908744

[1713908744]

1713908744

[1713908744]

1713908744

[1713908744]

1713908744

[1713908744]

1713908744

[CanErik]

Zero has a hard-coded option to use shielded transactions (Z) making it IMPOSSIBLE for anyone to track.
If I use zero to transfer, anyone can not see my transfer records, I understand so?

Hi;

From exchanges no, you should use windows or linux wallet.

Kind regards

[ConstantinGR]

Use the premodded windows version found in some of the pools

Hi;

I don't know why, my Win 7 OS rig don't work properly with the optimer 1.2.0 + GTX 1080 Ti GPUs while working properly with the  optimer 1.2.0 + RX480 8gb and RX580 8Gb rigs. It is keep crashing in 30 or 40 minutes. I set virtual memory to 12 Gb for each GTX (6 GTX * 12 Gb) If I use -d command miner chrash in a few secon, with -c at very beginig. Any ideas?

Kind regards

[zeki555]

I'm trying to mine with 6gb 1060 cards on ubuntu, but I keep getting this error:
./optiminer-equihash: error while loading shared libraries libopencl.so.1: cannot open shared object file: no such file or directory

Do you guys know what this means and how to fix this?

I downloaded libraries, It tries to connect now but gives the following error:

opencl error: failed to list opencl platforms

So no one knows how to fix this?

[oli123]

I'm mining zero coins ever since the beginning of this coin (early 2017). I was mainly interested in low consumption when mining. Currently the price is too low, the best time to buy.
From the roadmap I choose: To be listed in one Large-size Exchange - Q1 2018. So I'm looking forward to this and the price will go up.

[eurospeedy]

Hello,
I have mining question. I have on average 34sol/s per zero.forgetop.com pool and that gives me about 1.3zero a day. Is that right ? WhatToMine shows about 3zero a day with 34sol/s. I understand that WTM is just estimate but why is such a big difference.

And I should say I use windows with optiminer 1.2

Thanks in advance for any input.

[miknik]

Hi, i have this problem with Wallet, How i can solve? Thanks https://tlgur.com/d/wg26dPOg

[CanErik]

Use the premodded windows version found in some of the pools

Hi;

I don't know why, my Win 7 OS rig don't work properly with the optimer 1.2.0 + GTX 1080 Ti GPUs while working properly with the  optimer 1.2.0 + RX480 8gb and RX580 8Gb rigs. It is keep crashing in 30 or 40 minutes. I set virtual memory to 12 Gb for each GTX (6 GTX * 12 Gb) If I use -d command miner chrash in a few secon, with -c at very beginig. Any ideas?

Kind regards

Hi;

Can you share me that pools name please?

Kind reagards

[optiminer]

Here is an example from log files

We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}

ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid

Have you considered that the user might just have used the wrong hash algorithm param when connecting to the pool?

If the protocol is different it goes right away as an error on the first submit.

I have tested all the pools listed on the first page. They all report shares mined with a wrong algorithm as correct back to the miner:

$ ./optiminer-equihash -a  equihash200_9 -s zer-eu.forgetop.com:2053 -u <...> -p x
[2018-01-17 01:42:59.055] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
[2018-01-17 01:42:59.055] [default] [info] Connecting to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.149] [default] [info] Using 2 verifier threads.
[2018-01-17 01:42:59.149] [default] [info] Using highly optimized kernel code for Fiji devices.
[2018-01-17 01:42:59.149] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Fiji.bin
[2018-01-17 01:42:59.150] [default] [info] Autodetected '--intensity 5' for device 0.
[2018-01-17 01:42:59.192] [default] [info] Extranonce is '60000043'.
[2018-01-17 01:42:59.233] [default] [info] Mining target is 0050000000000000000000000000000000000000000000000000000000000000
[2018-01-17 01:42:59.234] [default] [info] Got new work.
[2018-01-17 01:42:59.260] [default] [info] [GPU0] Device info: {"id": "0/0" "name": "Fiji" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.314] [default] [info] Connected to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.464] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.464] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.465] [default] [info] Autodetected '--intensity 5' for device 1.
[2018-01-17 01:42:59.570] [default] [info] [GPU1] Device info: {"id": "0/1" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.773] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.773] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.773] [default] [info] Autodetected '--intensity 5' for device 2.
[2018-01-17 01:42:59.879] [default] [info] [GPU2] Device info: {"id": "0/2" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:43:01.015] [default] [info] [GPU2] Share accepted! (1 / 1)
[2018-01-17 01:43:02.549] [default] [info] [GPU0] Share accepted! (2 / 2)
[2018-01-17 01:43:03.061] [default] [info] [GPU2] Share accepted! (3 / 3)

It seems the pools internally filter those incorrect shares which is good. But they should be reported back to the miner as invalid.

The pool always get warnings when zcash solution is submited:

 Share rejected: {"job":"ccd0","ip":"::ffff:x.x.x.x","worker":"xxxxx.xxx","difficulty":0.01,"error":"incorrect size of solution"}

And also there is no hashrate.

Unfortunately this is not the case with the problem. Not a single warning is presented in the log files.

Those ppl have good steady hasrate, everything is OK, just when it comes to finding block it got rejected from zcashd.

Just checked, the solution verification has stayed the same in optiminer since version 2.0. You are chasing a red herring here.

The problem also does not seem to be new: https://github.com/zerocurrency/zero/issues/6

My best guess would be that there is NOMP and zerod validate the block difficulty.

[lutsifer]

Here is an example from log files

We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}

ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid

Have you considered that the user might just have used the wrong hash algorithm param when connecting to the pool?

If the protocol is different it goes right away as an error on the first submit.

I have tested all the pools listed on the first page. They all report shares mined with a wrong algorithm as correct back to the miner:

$ ./optiminer-equihash -a  equihash200_9 -s zer-eu.forgetop.com:2053 -u <...> -p x
[2018-01-17 01:42:59.055] [default] [info] Optiminer/Equihash 2.1.2 (C) Optiminer 2017
[2018-01-17 01:42:59.055] [default] [info] Connecting to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.149] [default] [info] Using 2 verifier threads.
[2018-01-17 01:42:59.149] [default] [info] Using highly optimized kernel code for Fiji devices.
[2018-01-17 01:42:59.149] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Fiji.bin
[2018-01-17 01:42:59.150] [default] [info] Autodetected '--intensity 5' for device 0.
[2018-01-17 01:42:59.192] [default] [info] Extranonce is '60000043'.
[2018-01-17 01:42:59.233] [default] [info] Mining target is 0050000000000000000000000000000000000000000000000000000000000000
[2018-01-17 01:42:59.234] [default] [info] Got new work.
[2018-01-17 01:42:59.260] [default] [info] [GPU0] Device info: {"id": "0/0" "name": "Fiji" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.314] [default] [info] Connected to zer-eu.forgetop.com:2053.
[2018-01-17 01:42:59.464] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.464] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.465] [default] [info] Autodetected '--intensity 5' for device 1.
[2018-01-17 01:42:59.570] [default] [info] [GPU1] Device info: {"id": "0/1" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:42:59.773] [default] [info] Using highly optimized kernel code for Ellesmere devices.
[2018-01-17 01:42:59.773] [default] [info] Reading bianry kernel from bin-223600/Equihash200_9-Ellesmere.bin
[2018-01-17 01:42:59.773] [default] [info] Autodetected '--intensity 5' for device 2.
[2018-01-17 01:42:59.879] [default] [info] [GPU2] Device info: {"id": "0/2" "name": "Ellesmere" "vendor": "AMD" "driver": "2482.3"}
[2018-01-17 01:43:01.015] [default] [info] [GPU2] Share accepted! (1 / 1)
[2018-01-17 01:43:02.549] [default] [info] [GPU0] Share accepted! (2 / 2)
[2018-01-17 01:43:03.061] [default] [info] [GPU2] Share accepted! (3 / 3)

It seems the pools internally filter those incorrect shares which is good. But they should be reported back to the miner as invalid.

The pool always get warnings when zcash solution is submited:

 Share rejected: {"job":"ccd0","ip":"::ffff:x.x.x.x","worker":"xxxxx.xxx","difficulty":0.01,"error":"incorrect size of solution"}

And also there is no hashrate.

Unfortunately this is not the case with the problem. Not a single warning is presented in the log files.

Those ppl have good steady hasrate, everything is OK, just when it comes to finding block it got rejected from zcashd.

Just checked, the solution verification has stayed the same in optiminer since version 2.0. You are chasing a red herring here.

The problem also does not seem to be new: https://github.com/zerocurrency/zero/issues/6

My best guess would be that there is NOMP and zerod validate the block difficulty.

This issue is for a pool that is not configured to work with zero at all.

[CoinMenX]

which anonymous technical will Zero using?

[Ginzink]

Optiminer, do you have reports from 1080 ti users that your miner just stops?
I dont remember the error code unfortunately but both me and my friend got it.
Think it may have been som memory fault, but ram and virtual memory was set way above required amount so unsure what caused it.

[zeki555]

I'm trying to mine with 6gb 1060 cards on ubuntu, but I keep getting this error:
./optiminer-equihash: error while loading shared libraries libopencl.so.1: cannot open shared object file: no such file or directory

Do you guys know what this means and how to fix this?

I downloaded libraries, It tries to connect now but gives the following error:

opencl error: failed to list opencl platforms

So no one knows how to fix this?

A little help here........

[ConstantinGR]

Optiminer, do you have reports from 1080 ti users that your miner just stops?
I dont remember the error code unfortunately but both me and my friend got it.
Think it may have been som memory fault, but ram and virtual memory was set way above required amount so unsure what caused it.

The Windows miner is unstable when used with nvidia. This is a known issue.
Best thing to do is to use Ethos & newest linux miner.

[ConstantinGR]

I'm trying to mine with 6gb 1060 cards on ubuntu, but I keep getting this error:
./optiminer-equihash: error while loading shared libraries libopencl.so.1: cannot open shared object file: no such file or directory

Do you guys know what this means and how to fix this?

I downloaded libraries, It tries to connect now but gives the following error:

opencl error: failed to list opencl platforms

So no one knows how to fix this?

A little help here........

You may have a misconfigured driver or a similar issue. Try ethos...

[zeki555]

I'm trying to mine with 6gb 1060 cards on ubuntu, but I keep getting this error:
./optiminer-equihash: error while loading shared libraries libopencl.so.1: cannot open shared object file: no such file or directory

Do you guys know what this means and how to fix this?

I downloaded libraries, It tries to connect now but gives the following error:

opencl error: failed to list opencl platforms

So no one knows how to fix this?

A little help here........

You may have a misconfigured driver or a similar issue. Try ethos...

Thanks for the answer much appreciated! So reconfiguring is not an option?

[ConstantinGR]

You can certainly try to reconfigure, but I have never used Ubuntu and I can't help you.
I have used ethos and since it is made for mining, it comes with drivers and it makes it easy to adjust fans, clocks and power. It also makes it easier to set up big rigs, unlike Windows.

[lovejoel]

nice name

[zeki555]

You can certainly try to reconfigure, but I have never used Ubuntu and I can't help you.
I have used ethos and since it is made for mining, it comes with drivers and it makes it easy to adjust fans, clocks and power. It also makes it easier to set up big rigs, unlike Windows.

Thanks I will give it a try.

[Hurtman]

Optiminer, do you have reports from 1080 ti users that your miner just stops?
I dont remember the error code unfortunately but both me and my friend got it.
Think it may have been som memory fault, but ram and virtual memory was set way above required amount so unsure what caused it.

The Windows miner is unstable when used with nvidia. This is a known issue.
Best thing to do is to use Ethos & newest linux miner.

http://ipic.su/img/img7/fs/1080tiZERO.1516291267.jpg