GMiner long and does not always return to server#1, please fix it.

Is it possible to disable text highlighting in the console? My windows 7 does not support this color coding

OS: Windows
Pool: equipool ; miningpoolhub

I am not very pleased to talk about this. I am disappointed. bminer-v10.7 compared to gminer_1_10 and miniZ_v1.0h shows 33% less performance on the equihash144 / 5 algorithm (GTX 1066, driver 417.1). Fix it, you were previously one of the best on equihash.

gminer_1_08_windows64 VS ewbf Equihash miner v0.6 windows64. Rig 6*1070, Equihash 144,5 Power consumption + 10%, hash rate + 14%, config file works fine, good work. Thank!!!

What kind of preamble are we talking about? After the fork BTCZ, some pools remained on the old algorithm and no one restricted access to mining to anyone. This was known to the entire active community BTCZ. It was also possible to run your BTCZ Equihash 200/9 node downloaded from github.com. Your accusations are unfair.

An interesting project !!! I would say that this is a project for those  who later jumped on the train BTCZ and did not have time to get out of it in time.

But seriously, this is a very interesting formula for the issue of coins, I think it has every chance of success ...

We are waiting for dstm's Equihash 144/5 and 197/2 Nvidia Miner

Tell me what the problem is:
"24.06.2018 21:35:11 INFO: Detected new work: 135912420056607
24.06.2018 21:35:20 Temp: GPU0 62C GPU1 62C GPU2 62C GPU3 60C GPU4 59C GPU5 61C
24.06.2018 21:35:20 GPU0: 31 Sol/s GPU1: 29 Sol/s GPU2: 32 Sol/s GPU3: 30 Sol/s GPU4: 32 Sol/s GPU5: 31 Sol/s
24.06.2018 21:35:20 Total speed: 185 Sol/s
24.06.2018 21:35:29 CUDA: Device: 5 Thread exited with message: "unspecified launch failure"
24.06.2018 21:35:29 CUDA: Device: 4 Thread exited with message: "unspecified launch failure"
24.06.2018 21:35:29 CUDA: Device: 3 Thread exited with message: "unspecified launch failure"
24.06.2018 21:35:29 CUDA: Device: 0 Thread exited with message: "unspecified launch failure"
24.06.2018 21:35:30 CUDA: Device: 1 Thread exited with message: "unspecified launch failure"
24.06.2018 21:35:30 CUDA: Device: 2 Thread exited with message: "unspecified launch failure"
24.06.2018 21:35:30 WARNING: Looks like GPU0 are stopped. Restarting...
24.06.2018 21:35:30 INFO: GPU0 are restarted.
24.06.2018 21:35:30 WARNING: Looks like GPU1 are stopped. Restarting...
24.06.2018 21:35:30 INFO: GPU1 are restarted.
24.06.2018 21:35:30 WARNING: Looks like GPU2 are stopped. Restarting...
24.06.2018 21:35:30 INFO: GPU2 are restarted.
24.06.2018 21:35:30 WARNING: Looks like GPU3 are stopped. Restarting...
24.06.2018 21:35:30 INFO: GPU3 are restarted.
24.06.2018 21:35:31 WARNING: Looks like GPU4 are stopped. Restarting...
24.06.2018 21:35:31 INFO: GPU4 are restarted.
24.06.2018 21:35:31 WARNING: Looks like GPU5 are stopped. Restarting...
24.06.2018 21:35:31 INFO: GPU5 are restarted."
on the old algorithm, everything was fine, and now at 194.5 several times a day this failure

I am happy with the quick response. Good work. BTCZ already on June 16, this week switches to Equihash 144.5 Fork will take place on the block of 160,000 (if not mistaken). I also read in the tweeter that the BTG team thanked the developers of the BTCZ community for their assistance in combating asiks, which means that they also go over to 144.5 (I will not tell you in detail, I do not follow BTG). Development of the miner for Equichash 144.5 for the BTCZ community is carried out by renuzit (https://github.com/btcz/zhasher), Miner zhasher is currently very poorly optimized, it would be great if you implemented the support of Equihash 144.5 in your miner using your knowledge and experience ...

Hello realbminer, will there be support for ZHash (Equihash 144.5). We should pay attention to this algorithm as it will be popular, except for BTCZ it is implemented by BTG and I suppose that ZCL too can pass to it, the developers of BTCZ previously cooperated with the ZCL team.
ZHash(Equihash 144,5) is a new algo made by the BTCz decentralized team : it is a equihash variant (more ASIC resistant than the currents versions).

I join the question of ZHash support (Equihash 144,5)
 We should pay attention to this algorithm as it will be popular, except for BTCZ it is implemented by BTG and I suppose that ZCL too can pass to it, the developers of BTCZ previously cooperated with the ZCL team ...

This is due to the high profitability of BTCZ mining, BTCZ is often at the top of the list of mining profitability calculators.

You are absolutely right, investors primarily check ANN. At a cursory viewing our ANN became poorer and it scares away many potential investors. In addition, the transition ANN frightened some investors and they sold their deposits by flopping the course just like it was with the departure of Anthony (IMHO).
But what to do, life continues, work is under way, and the fall in exchange rate has allowed many others to increase their deposits.
And those investors who are deeper to learn the work that the developers are doing will make their choice in favor of BTCZ. But in order to facilitate this task, you need more activity in the ANN.

This is a fraudulent exchange, unreal swollen volumes, large restrictions on the withdrawal of deposits and very large commissions.

Does not help, 0 connections. Give a list of working nodes.

Unreasonable assumptions?
 I am a miner and beyond my competence to understand exactly what happened, however I have already seen such a situation with Bitcoin Gold (there lawsuits have been filed in this regard). And as I have the right to my opinion and I can express it, which I did. I did not blame anyone for fraud but only expressed an assumption, substantiating it (maybe not entirely objectively, based on the information that I had).
About your invitation to the discord. I consider bitcointalk to be the main source of information and discussions (which follows even from its name) and I think that it is here that first of all there should be information about the problems, discord and slack place for discussing the details and other things. It is in the bitcointalk that information about the problems should first of all be in order to reduce the financial losses of the rest of the community.
I appeal to the Zel team:
We miner pay you 6.2% of our production and I think we have the right to be timely aware of the problems that cause us damage, as well as, subsequently, about the true causes of these problems.
In addition, you stated about very serious technical tasks (Utilizing both Equihash and Ethash blockchains) that you intend to solve. So, really, you could not secure the blocking in advance from the 51% attack, registering protection in the work algorithm? What was it? When attacking 51%, as far as I know, a pool with a large hash may block the blocks of other network members, it turned out the other way around, for some reason the pool with the largest hash was an outcast.
Explain.
I apologize for my English (google translate)

I do not know where such information comes from but today it looks like the truth. My employees last 10 hours work useless, despite the fact that they are on a larger pool. Almost all the blocks for this time took the pool http://zel.cloudpools.net to which it is impossible to connect !!! (ping zel.cloudpools.net 100% loss) This is very similar to fraud. Confirmation of that in the explorer block, see blocks with 9447 Feb 11, 2018 4:01:35 AM Someone using z-nomp! by 9637 Feb 11, 2018 1:01:15 PM Someone using z-nomp! and further. A pool with a large hash
https://zelcash.miningspeed.com/ almost nothing gets !!! How so?
I hope you have a good explanation for this.

A strange question from not a new user. The difficulty has to do with the price only indirectly. First of all, the difficulty adjusts the generation time of the block to the set value (2 min 30 sec), depending on the power of the network at a given time. And because the coin is new and the network still has low power, then any power connection has an effect.

We conduct an action, raise funds for a professional video in several languages ​​with support for promotion in the network.
Those who wish can support at: https://axepool.com
Connection information on the main page.
And:

DSTM miner:
zm --server axepool.com --port 3032 --user t1M3fZ2aZ5U8pRdAoKH2rwLH2evnXmz3B3A.WorkerBitcointalk --pass x

EWBF Zec Miner:
miner.exe --server axepool.com --user t1M3fZ2aZ5U8pRdAoKH2rwLH2evnXmz3B3A.WorkerBitcointalk --pass x --port 3032


bminer:
@echo OFF

REM Change the following address to your Zcash taddr.

SET ADDRESS=t1M3fZ2aZ5U8pRdAoKH2rwLH2evnXmz3B3A

SET USERNAME=%ADDRESS%.WorkerBitcointalk

SET POOL=axepool.com:3032

SET SCHEME=stratum

START "Bminer: When Crypto-mining Made Fast" bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api localhost:42000


For the name wiorker write your username bitcointalk
Screenshots for memory will be shot