EWBF's Cuda Equihash Miner 0.6

[gsambolin]

Is getting 29.5 sol/s on a 1070 card doing 144.5 ZHash. Is that about right?

you can some more

Uptime: 0d 02:54:32   
Server: btcz.suprnova.cc:6586   Connected
Statistics of the GPUs
GPU   Temp   Power   Speed   Efficiency   Accepted   Rejected
GeForce GTX 1070   59 C   154 W   33 Sol/s   0.21 Sol/W   225   0
GeForce GTX 1070   52 C   148 W   35 Sol/s   0.24 Sol/W   211   0
GeForce GTX 1070   58 C   145 W   32 Sol/s   0.22 Sol/W   237   0
GeForce GTX 1070   56 C   148 W   34 Sol/s   0.23 Sol/W   213   1
GeForce GTX 1070   63 C   155 W   33 Sol/s   0.21 Sol/W   226   0
GeForce GTX 1070   54 C   151 W   34 Sol/s   0.23 Sol/W   214   0
Total   -   901 W   201 Sol/s   0.22 Sol/W   1326   1
EWBF v0.2

Would you please share your MSI burner settings? I barely get 30

ubuntu, no MSI
GPU ~2000, MEM 8900, PL 160

Would you please share your SuprNova config settings?
Thanks in advance

[1695405417]

1695405417

[nUm81]

Memory speed on the 1070's doesn't seem to matter much.





Power is expensive here, so the less power the better. 

[nUm81]

i tried with one 1060 3gb it works but the shares are not showing on the pool it stays at zero is this beacause it's just too low 19 sols? my 8 card rigs shows up just fine....

Try using a port that is very low difficulty.  The pool may be sending you shares that are too big for the card to solve before the next share is received and it has to start again. 

[abstractHaze]

can anyone confirm 144_5  with 1060 3gb on windows.. also was main display an issue?

- thank you.

[Coin++]

Is there a significant difference with the unakoshi-miner?

What is it ?

https://forum.bitcoingold.org/t/main-tutorial-for-testnet/1671

I've tested the Funakoshi miner in 3.2 version (last one).
It is not a final release : just a beta one.
It's working, but make very very few shares.
Back to EWBF, very stable in Cuda8 version (some issues with Cuda9 version : Windows 10-64).

[Jonpete]

Any chance dev could make it work with maxwell architecture my 980ti on old algo was pulling 480 to 500 sol on new algo 9 to 11 would be much appreciated.

[umadns]

mining rig 9x 1070ti and one 1070.
Keeps crashing half of the gpus thread exited with message:''out of memory''

works fine in old ewbf,tried to remove overclock settings same,tried to run 2 instances of ewbf same...

any help would be much appreciated...

Yes, this is virtual memory, try to increase the paging file to 30 - 50 Gb

Thanks a lot, it worked 325avg sols.<3 https://imgur.com/a/DG16YnS

Still couldn't make it work with 12 cards and was forced to separate the rig into 2 instances.
The 2x1070's were shown as stuck and miner was trying non stop to restart them. https://imgur.com/a/eJxHk3J

[inudemon]

Any chance dev could make it work with maxwell architecture my 980ti on old algo was pulling 480 to 500 sol on new algo 9 to 11 would be much appreciated.

I suppose it's the same case as Maxwell on DaggerHashimoto. I remember that every DAG file (every 2 weeks)  my GF970s made less and less comparing to 1060s (12 MH to 25 MH for example) while the power consumptiong was 160W to 100 Watts.  Finally I stoped to mine DaggerHashimoto  and soon sold my 970s to gamers.

[juville]

Hi EWBF,

Can we use this new miner to mine the coins that use 200, 9 like zencash?

[ComputerGenie]

Hi EWBF,

Can we use this new miner to mine the coins that use 200, 9 like zencash?

...
*  Solver for equihash 200,9 has been deleted.
...

[duyvu1311]

How many GPUs does this miner support?

[crypper]

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??

[ComputerGenie]

...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?...

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).

[crypper]

...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?...

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).

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

[MentalNomad]

...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?...

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).

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

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/

[MentalNomad]

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'.

[crypper]

the early post-block forks .

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.

[reb0rn21]

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

[gsambolin]

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

[kockas]

Hi,

0.2 version on Ubuntu detects only 7 cards for me.

Anyone else? When is planned new release?

Thanks for the miner.