I do not recommend to directly mine to a coin exchange deposit address using hodl.optiminer.pl. The pool still hodls mined block but just for 21 blocks. You are not supposed to transfer newly mined coins before that anyways so that should not be of any disadvantage. But exchanges might not like that. To be honest that was the easiest change to make the pool still work after the fork so I went with that. As there are other pools available now again I will probably keep things as is on hodl.optiminer.pl. So, just mine to an address of your wallet and transfer it from there. But most likely you want to hodl the coins anywas, right? To have that information listed on the instructions of the pool would have been very nice.... how about that? So I LOST my 300 hodl coins? Coinexchange replied to my ticket: "You cannot mine into an exchange address. It is a different type of transaction. Regards" I asked them if I can have back my coins... Sad to lost days of mining I did not think of that before. I will try to put a warning on the pool in the next days. But to be honest, technically this is not the pool's fault. The exchange should still accept the coins when the coins mature (which is after 21 blocks as I said, so almost immediatey). THEY have YOUR coins, so keep complaining.
|
|
|
I'm setting up a new rig with Ubuntu 14.04.4 and installed the fglrx drivers and doing driver checks I see my card. However when I try to list my devices in optiminer I get the following:
$ ./optiminer-zcash --list-devices ./optiminer-zcash: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./optiminer-zcash) ./optiminer-zcash: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./optiminer-zcash)
Anyone know what I'm missing? Seems like I should know the answer to this but I'm just struggling.
See https://github.com/Optiminer/OptiminerZcash#glibcxx_3420-not-found-on-ubuntu-1404
|
|
|
I do not recommend to directly mine to a coin exchange deposit address using hodl.optiminer.pl. The pool still hodls mined block but just for 21 blocks. You are not supposed to transfer newly mined coins before that anyways so that should not be of any disadvantage. But exchanges might not like that. To be honest that was the easiest change to make the pool still work after the fork so I went with that. As there are other pools available now again I will probably keep things as is on hodl.optiminer.pl. So, just mine to an address of your wallet and transfer it from there. But most likely you want to hodl the coins anywas, right?
|
|
|
whata bout nvidia miner? are you planning to make one or only amd?
I do have some plans for an nvidia miner. But cannot say when it will be ready. Also depends on the price development of the coin.
|
|
|
WOW this coin is literally impossible to mine, the top miner on suprnova pool is getting 0.01 ZER a day, and price is so cheap? Mining this coin is very difficult when you have a low specification computer but I used to get it when the price is high and I have enjoyed it That's not true. Both the hash rate and expected payout shown at suprnova are completely off. Let's do a quick estimate: - current network hash rate (shown at https://zeroexplorer.com): 2729 H/s - Daily mined coins: 7200 - Hash rate of an 8GB GPU (exact number depends on the model): ~8H/s This means your daily pay mining with 1 GPU will be: 7200 * 8 / 2729 * 0.99 = 20.9 ZER That's about $3.5 if you'd be crazy and dump at the current price level.
|
|
|
Yes, that's great. Just tag it such that it is more visible that the merge happened and we have a stable tag to checkout and build from.
|
|
|
The optiminer hodl pool ( http://hodl.optiminer.pl) has been updated with the new hodlcoin daemon 3.0 and an updated pool version that will stop locking mined block for 1 year after block 257000. Hope the transition will go smoothly.
|
|
|
I have updated the public ZERO node with IP 94.176.235.178 that accepts incoming connections. It is now based on the latest ZERO code-base at https://github.com/zerocurrency/zero - updated by the original Zero developer. Everyone interested may add it to their config. file ~/.zero/zero.conf: addnode=94.176.235.178 Thanks, zerodev2. Your node is now in github installation steps too. Can someone make an official release with the merged code? Or at least tag it in github.
|
|
|
I have 4 GPU but work only 3 GPU. 4x RX480 8gb. System i7 920 and 12gb. When i start optiminer say: [2017-05-10 18:46:21.474] [info] Connected to zero.suprnova.cc:6568. [2017-05-10 18:46:21.474] [info] Got new work. [2017-05-10 18:46:21.964] [info] [GPU3] Device info: {"id": "0/3" "name": "Ellesmere" "platform": "AMD" r": "2348.3"} [2017-05-10 18:46:31.694] [info] GPU3 Waiting for work from pool. [2017-05-10 18:46:31.694] [info] GPU3 Got work, start mining. [2017-05-10 18:46:31.714] [error] OpenCL error: readBuffer Solutions1 (CL_INVALID_EVENT_WAIT_LIST) [2017-05-10 18:46:31.724] [info] Press any key to exit application.
Help pls.
Assuming Windows: You probably need more virtual memory. For 4x 8GB cards, set virtual memory to 32gb. (Or use linux.)
|
|
|
im using znomp with my node and using optiminer keeps giving me: 2017-05-06 16:47:43 [Pool] [zero] (Thread 3) Share rejected: {"job":"cce2","ip":"::ffff:192.168.1.125","worker":"t1MA3j1b3CqV37HqqVo5putK8txB7WonecN.rig","difficulty":0.04,"error":"incorrect size of solution"} any pointers?! Looks like what you want to mine is Zcash not ZERO. Zcash miner is here: https://github.com/Optiminer/OptiminerZcash
|
|
|
I think what would be good for the coin is to get added to a second exchange.
And a second mining pool would also be good, currently 90% of mining power is concentrated within a single pool.
|
|
|
Concurrent write detected, queuing.
This warning can normally be ignored. It might be a hint that there is a network issue. In this case the miner would disconnect and reestablish the network connection soon after that.
|
|
|
optiminer, great news for so many smaller miners here. What did it take to fit into the 4GB, please?
It reuses some of the memory buffer between the rounds at the expense of less efficient memory access patterns. And cutting down the bucket sizes a bit. This means it will find a bit fewer solutions per iteration. Right on! Do you think some of these optimizations could apply to the CPU miner code as well? Tearo These 'optimizations' are for making the algo run with 4gb instead of 8gb but slower. So, this would only make sense for the CPU if you are short on memory. I still believe that equihash is much better suited for GPUs than CPUs even with the changes params. You could increase the memory usage even more like 8x more than currently. Then, it would be difficult to implement it with less then 32gb ram which would make it difficult to find a GPU where it works on.
|
|
|
Problem with 4gb cards solved for me ... but it is twice as slow ))
Yeah.. that's expected. With 4gb the memory access pattern are way worse.
|
|
|
Added release for 4GB cards running under linux.
|
|
|
optiminer, great news for so many smaller miners here. What did it take to fit into the 4GB, please?
It reuses some of the memory buffer between the rounds at the expense of less efficient memory access patterns. And cutting down the bucket sizes a bit. This means it will find a bit fewer solutions per iteration.
|
|
|
|