Topic: EWBF's Cuda Equihash Miner 0.6 - page 36. (Read 85776 times)

yes

Is this the best miner to mine btcz?

I had to use on the testnet so I assume you will need it for Suprnova Pool.   I will be mining there as well and it is in my config file already to go.

Is line --pers BgoldPoW must be added to miner even on mainnet if i use, for example, Suprnova pool?

I think it's explained in the v0.2 descript on page 1 but like all miners it will mine every so many minutes or hashes to the Dev pool (usually flypool or Nanopool) and that's fine, EWBF is honest... 

Ok so it sounds like there is a fee.  How is that being paid, through the miner program ?  Is it a one time fee or ongoing?

Some keep asking about the No fee option as in --fee 0 used back in earlier versions, and I laugh because look how many suffer with the Claymore miners yet pay that fee.... so I pay the 2% EWBF fee. It takes time coding these miners...

What does it mean when you say DEV FEE left intact?   Are we paying someone to use EWBF, sorry for the naive question.

1060x6 averaging 22Mh/s using older Dell server board G43T, Intel E8500 3.16GHz, 8GB sys mem (set to System manage), tuned with Intel XTU utility, 3 cards EVGA. EWBF easily connects and looks quite promising as usual. Waiting for correct block height and ready to mine! DEV FEE left intact, every other miner gets and EWBF deserves it! Hope the DEV sticks with this 0.2 miner and keeps it tuned! THANKS EWBF!!

EDIT: looks like we are @ 535842 Blkhgt now...

Hi,

0.2 version on Ubuntu detects only 7 cards for me.

Anyone else? When is planned new release?

Thanks for the miner.

Just an observation and not sure how this is happening, these are the parameters

- Using EWBF V 0.2
- W10
- 3 * 1070 TI and 1 1050 TI
- Mining testnet net for Btg  http://btg-testnet.miningspot.net/miner/2N4cHD1gzU35ZJG1MsyXuSgj4AUPWbd164h

The issue becomes, when I mine with the miner in the bat file and all the parameters that go with it.  The number of sols reported on the test net page are correct and SHOW UP.
BUT
When I use all the miner command with just the config file and the config file has all the exact parameters the number of sols are not reported on the test net page.  

Works when I run it like this

miner  --algo 144_5 --pers BgoldPoW --server btg-testnet.miningspot.net --port 3857 --user 2N4cHD1gzU35ZJG1MsyXuSgj4AUPWxxxxxx --pass x --cuda_devices 0 1 2 3 4 5 --intensity 64 64 64 64 64 64 --templimit 80 --api 127.0.0.1:42000 --pec 1 --boff 0 --eexit 3 --tempunits C --log 3 --logfile BTG_miner_V2.log

DOES NOT WORK when I run it like this

miner --config miner.cfg

These are the parameters on in the miner.cfg file.  I am not sure if it is just a test net thing or not - Any suggestions ?

# Common parameters
# All the parameters here are similar to the command line arguments

[common]
cuda_devices 0 1 2 3 4 5
intensity    64 64 64 64 64 64
templimit    75
pec          1
boff         0
eexit        3
tempunits    c
log          3
logfile      BTG_miner_V2.log
api          127.0.0.1:42000
algo         144_5
pers         BgoldPOW

# The miner start work from this server
# When the server is fail, the miner will try to reconnect 3 times
# After three unsuccessful attempts, the miner will switch to the next server
# You can add up to 8 servers

# main server
[server]
server btg-testnet.miningspot.net
port   3857
user   2N4cHD1gzU35ZJG1MsyXuSgj4AUPWxxxxxx
pass   x

# additional server 1
[server]
server btg-testnet.miningspot.net
port   3857
user   2N4cHD1gzU35ZJG1MsyXuSgj4AUPWxxxxxx
pass   x

3-4 big farms can switch in 2min, like they did with lux fork, profit 0.30cent per GPU....... just with 2 big farms moving
big farms don`t care and they can do basic math as most are run by retards

Or the block-fork post?  

In theory you are right...But I'll tell you what:
Last year (October or November, can't remember) when BTG was launched I was sitting and waiting for the blockchain to come live hoping on a big profit during the first few days/weeks of mining. You know what...I didn't get rich. It appeared there were plenty of other smarty-pants doing the same thing.

FYI to all, at the BTG fork on block 536,200, about 3 days from now (countdown timer here: https://bitcoingold.org/bitcoin-gold-network-upgrade), the Difficulty will drop to 1/100th the prior difficulty.

Dropping 1/15 is to account for the hard algo (15x harder), but the rest is just to compensate in case a lot of miners/pool don't immediately migrate.

This means the early post-block forks will be hyper-profitable. 

I'm just sayin'.

The MPH banner shows they're supporting BTG after the fork, but yeah, BTG will have to come out of the auto-switching Equihash pool.

Their BTG page offers specs - they're keeping the same port number post-fork, so they must plan to take out the old pool and connect a new pool to that same port number at the time of the fork (or have otherwise automated the switch on their end - in which case, good job, MPH.)

https://bitcoin-gold.miningpoolhub.com/

You are probably right, BTG will have to be dropped from the port. MPH is however silent on that matter. We'll see.

Because the K & N change makes for what is essentially a new algo, it's not possible to have one port that supports "different equihashs" at the same time (unless the pool has special software to change from a to b). One miner that autochanged algos based on a given pool's switch would have to coordinate with that given pool. That's just not how miners work, unless they, or some overlay app, are proprietary to that pool (like nicehash).

Hi guys,
Here is my (and possibly many others') problem:
I'm on equihash autoswitch (zen, zec, btg, zcl; port 17203) at MininPoolHub; happily mining with older EWBF cuda miner.
BTG is however about to fork (~ July 1st) and switch to 144,5 algo.
Since new EWBF miner doesn't support 200,9 and older miner doesn't support 144,5, it will not be possible to mine at MPH with either of the miners. What would be a solution here?

EWBF,
Any chance you can restore 200,9 in the current version of the miner??

How many GPUs does this miner support?