[ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9

[jombolo]

Switched from dstm last night to bminer just to give it a try. I'm using only 3x EVGA 1080's. bminer is reporting a 50-70 sol/s increase over dstm in SMoS, from about 1,680 (dstm) to 1,750 (bminer), however I cannot tell from the flypool graph if there is an actual increase. What IS apparent, there are far more invalid shares being reported with bminer. Link below shows: In the first 12 hours with dstm, only 1 invalid share, and in the second 12 hours with bminer there were 14 invalid shares. The big dip in the middle reflects where i made the switch from dstm to bminer. I do not yet know how this will affect my actual share of zec when i reach the 24 hour comparison, will be interesting.

http://i102.photobucket.com/albums/m87/jombolo1/2018-03-08%2008_36_22-Flypool%20Zcash%20-%20Miners%20Dashboard_zpszb6fxzxy.png

[1715173602]

1715173602

[1715173602]

1715173602

[1715173602]

1715173602

[realbminer]

5.5.0 has released.

• Show the fan speed in both console and UI.
• Fix compatibility issues for pool.miningspeed.com.
• Fix a bug that causes Bminer fails to start on Windows under some configuration.

Happy mining!

[Johnjay06]

Will you address the issues?

[NameTaken]

Atleast acknowledge user concerns instead of completely ignoring them.

[fr4nkthetank]

Atleast acknowledge user concerns instead of completely ignoring them.

well just that, disregarding any facts that can be found, kinda shows what is up with the software I guess.  I wouldnt really use it.  You can try excavator too.

[penderway]

When a con artist is under suspicion, their first line of defence is to ignore accusations, project confidence and change the subject.


I implore the community to keep asking questions and continue to seek answers. Individual research and investigations included.

If suspicion persists and the heat is turned up (by making more people aware of this issue), then we'll either get an acceptable explanation or we'll see the second line of defence for a con artist.

Tick, tock, tick tock...

P.S. the fact that many posters of this issue are newly registered may only mean that until now, they hadn't a motivation to register before (such is the reason for my registration).

[revbones]

5.5.0 has released.

• Show the fan speed in both console and UI.
• Fix compatibility issues for pool.miningspeed.com.
• Fix a bug that causes Bminer fails to start on Windows under some configuration.

Happy mining!

Translation:  probably obfuscate or encrypt code to further hide shady crap bminer will do on your machine.

[mycryptoverse]

Bminer is a highly optimized Equihash miner that runs on modern NVIDIA GPUs (Maxwell and Pascal, i.e. GPUs that have compute capability 5.0 or above). Bminer is the fastest publicly available Equihash miners today. It features a completely restructured algorithm to maximize the stream processor occupancy and the instruction pipeline efficiency. It realizes the full potentials of Pascal GPU cards.

Bminer also comes with REST APIs to facilitate production deployments (e.g., mining farms).

Similar to other miners, Bminer contains 2% devfee.

Features

Fast

• 735-745 Sol/s on GTX 1080Ti
• 450-460 Sol/s on GTX 1070
• 315-325 Sol/s on GTX 1060
• On stock settings

Secure and reliable

• SSL support
• Automatic reconnects to recover from transient network failures
• Automatic restarts if GPUs hang

Operation friendly

• Comes with REST APIs to facilitate production deployments

Quickstart

To mine Zcash on nanopool:

• Download and extract Bminer into a folder (e.g. C:\bminer or /home/bminer)
• Edit mine.bat (mine.sh on Linux) and change the address to the desired Zcash address that Bminer mines towards.
• Open command line prompt and run mine.bat (mine.sh).
• Enjoy mining  

Please see https://www.bminer.me for advanced usages, APIs and updates.

Downloads

• Linux x64: bminer-v5.5.0-aba7617-amd64.tar.xz
• SHA256 checksum: fd5cf3f5ccff1862424d0bb7ad2332cfdf43334daef48db51efb579b49bf6c7f
• Windows x64: bminer-v5.5.0-aba7617-amd64.zip
• SHA256 Checksum: a1533e599df386e144ded3052f14011a10524e711eb9884f8e36a9381940b6f9

Release notes

5.5.0

• Show the fan speed in both console and UI.
• Fix compatibility issues for pool.miningspeed.com.
• Fix a bug that causes Bminer fails to start on Windows under some configuration.

5.4.0

• Fix a reconnection issue in the network layer.
• Show additional statistics in console.
• Allow cross-domain requests to access the API.
• Fix the compatibility issue with docker.
• Introduce the option `-share-check` to make the time of recovering from no accepted shares configurable.

5.3.0

• Experimental support for EthOS / Ubuntu 14.04.
• Support AMD K10 CPUs.
• Automatically restart hanged network connections.
• Improve compatibilities with mining rigs with more than 8 cards.

5.2.0

• Introduced the option -logfile to append the logs into a file.
• Minor optimization on Windows for cards that are mounted on the risers.
• Improve compatibility for NiceHash.

5.1.0

• Support NiceHash.
• Fix unstable network connections in 5.0.0.
• Fix performance regressions for 1080Ti under Linux.

5.0.0

• Minor performance improvement for GTX 1060.
• Fixed performance regressions in 4.0.0 on Windows.
• Optimization on the networking layer.
• Show GPU ID in case of hardware errors.
• Introduced the option -no-timestamps which suppresses the timestamps in the logging messages.

4.0.0

• Minor performance improvement.
• Support older CPUs like Core 2 Duo.
• Support mining rigs that have more than 8 GPUs.
• Support luckpool.org.
• Removed the polling option.
• Introduced the option `-max-network-failures` which allows Bminer to exit after consecutive network failures.
• Various improvement on the UI.
• Localization for Russian and Chinese.

3.0.0

• Minor performance improvement.
• Disable CPU polling by default.
• Introduce a Web-based dashboard.
• Support slushpool.

2.1.0

• Add the -polling option to make GPU polling configurable.

Disabling polling reduces the CPU usage but it might reduce the performance in some configurations.

• Improve the stability of the network connections.
• First public release for Linux.

2.0.0

• First public release.

I have been using this miner on BTCP and seem to be getting around 570-600 SOL/s on my GTX 1080 8GB on +125 Core and +500 Mem. The lowest is the card in my gaming PC and where I receive my video. My hash being reported on the pool has been equal to the hash in the cmd prompt. This is just my experience over the course of 3 days now.

[gettilee]

5.5.0 has released.

• Show the fan speed in both console and UI.
• Fix compatibility issues for pool.miningspeed.com.
• Fix a bug that causes Bminer fails to start on Windows under some configuration.

Happy mining!

yet again, realbminer ignores page after page of concerns and questions.

1. he won't remove the private connection
2. console over reports hashrate
3. rejected shares due to the same seed for the nonce every time a new job is sent by the pool

realbminer doesn't deserve a 2% dev fee. hes just doing cosmetic updates while the miner has many serious flaws.

i'm done with bminer

[redlumek]

Hi. I have some error under linux

Code:

[INFO] [2018-03-10T07:40:28+01:00] Bminer: When Crypto-mining Made Fast (v5.5.0-aba7617) 
[INFO] [2018-03-10T07:40:28+01:00] Watchdog has started.                        
[INFO] [2018-03-10T07:40:28+01:00] Starting miner on devices [0 1 2 3 4 5 6 7 8 9 10 11] 
[INFO] [2018-03-10T07:40:28+01:00] Connected to btcp-eu1.mineflowpool.pl:3030   
[INFO] [2018-03-10T07:40:28+01:00] Subscribed to stratum server                 
[INFO] [2018-03-10T07:40:28+01:00] Set nonce to 000001c4                        
[INFO] [2018-03-10T07:40:28+01:00] Set target to 000000000000000000000000000000000000000000000080aaaaaaaaaaaa0a00 
panic: interface conversion: interface {} is string, not bool
[WARN] [2018-03-10T07:40:28+01:00] Miner died! It will be restarted soon...     
[INFO] [2018-03-10T07:40:38+01:00] Bminer: When Crypto-mining Made Fast (v5.5.0-aba7617) 
[INFO] [2018-03-10T07:40:38+01:00] Watchdog has started.                        
[INFO] [2018-03-10T07:40:38+01:00] Starting miner on devices [0 1 2 3 4 5 6 7 8 9 10 11] 
[INFO] [2018-03-10T07:40:38+01:00] Connected to btcp-eu1.mineflowpool.pl:3030   
[INFO] [2018-03-10T07:40:38+01:00] Subscribed to stratum server                 
[INFO] [2018-03-10T07:40:38+01:00] Set nonce to 780001cf                        
[INFO] [2018-03-10T07:40:38+01:00] Set target to 000000000000000000000000000000000000000000000080aaaaaaaaaaaa0a00 
panic: interface conversion: interface {} is string, not bool
[WARN] [2018-03-10T07:40:39+01:00] Miner died! It will be restarted soon...  

my config
-api 127.0.0.1:1880 -max-temperature 82 -uri stratum://b1SLasQf2D4GV13WNb2GeR5fwuApupsdCZJ.rig2:x@btcp-eu1.mineflowpool.pl:3030

[Supercoiner111]

I have also noticed these strange issues. Although there is a constant high hashrate on the console, I see there is lot of variance on the pool site hashrate and they are lower. Sometimes for a short period it peaks and is increased but, for a short period. This was observed consistently across several pools. I have been using Bminer for a while however, with these observations and the dev not really addressing the issue that is a concern.

I will be returning back to the more obvious and consistent DSTM.

[Alyeska]

I have also noticed these strange issues. Although there is a constant high hashrate on the console, I see there is lot of variance on the pool site hashrate and they are lower. Sometimes for a short period it peaks and is increased but, for a short period. This was observed consistently across several pools. I have been using Bminer for a while however, with these observations and the dev not really addressing the issue that is a concern.

I will be returning back to the more obvious and consistent DSTM.

This is exactly what I experienced and exactly what I did, back on DSTM hashing away,

I really liked the interface of Bminer's stats, telling me I was getting more, I simply would like to experience those actual stats, I feel the GUI was giving false readings at this point...

[dkmontague]

I have also noticed these strange issues. Although there is a constant high hashrate on the console, I see there is lot of variance on the pool site hashrate and they are lower. Sometimes for a short period it peaks and is increased but, for a short period. This was observed consistently across several pools. I have been using Bminer for a while however, with these observations and the dev not really addressing the issue that is a concern.

I will be returning back to the more obvious and consistent DSTM.

This is exactly what I experienced and exactly what I did, back on DSTM hashing away,

I really liked the interface of Bminer's stats, telling me I was getting more, I simply would like to experience those actual stats, I feel the GUI was giving false readings at this point...

Same.  Back on dstm unless issues are addressed.  Dev seems to have ZERO interest in doing so, so he will not get my 2%. 

[lktr]

Hi all
Does anybody know how to parse the api answer (api/status) to get an array? (Php)

[realbminer]

I am actively working on 6.0 and I hope I can release it out before next week. I am also working actively on a big release (after 6.0) which would bring additional hash algorithm supports in bminer.

I am not ignoring any of your concerns. During the last two weeks, I just focused more on the development and did not get time to monitor bitcointalk thread.

Here are my answers to questions about console hashrate, rejected shares, and private connections. I will also update FAQ because these questions have been raised many times.

# Why the reported hashrate of Bminer is higher than the reported hashrate from mining pools?

Bminer reports hashrate generated by your *hardware*, while a mining pool
estimates the hashrate based on the number of submitted shares. The Bminer
hashrate is different from the pool hashrate because:

1. The Bminer reported hashrate includes the devfee.

2. A small portion of the generated shares may get rejected or become stale due
   to network delay and transmission problems. Bminer reported hashrate will
   include such shares, but such shares will not contribute to the pool
   estimated hashrate.

3. Your pool hashrate is an estimate based on received shares, therefore it
   will vary a lot unless you control a significant amount of hashpower and you
   run it over a long period of time.

4. Some pools may calculate the estimated hashrate incorrectly.

Specially, if you turn on nofee option. You will see the same number of
hashrate but the underlying computation is slowed down due to disabled
optimizations.

# Why I see rejected shares when using Bminer?

There are many reasons for rejected shares. Two primary reasons for rejected
shares are:

1. Network latency: If your latency to the connected pool is too long, then a
   valid share may become stale and invalid during the transmission. This will
   cause the share being rejected. The solution to this problem is to choose a
   pool server that has low latency connection to your rig.

2. Overclocking: Aggressive overclocking setting may cause GPU to produce
   incorrect results and therefore generates invalid shares being rejected.

Software bugs in Bminer may also cause a small portion of rejected shares. We
will keep improving bminer and reduce the number of rejected shares.

# Why Bminer starts private connections to bminer.me

The first communication checks the update and receives license information,
including for example where to mine devfee. Note that in this communication
bminer *does not send out any information*, it only receives information from
bminer.me.

The follow-up communications only send runtime information of bminer, like the
mining speed of each card and performance status. This may enable bminer to
choose better optimization strategies. Starting from version 6.0.0, these
follow-up communications will become transparent.

[FQ_Neronk]

I am actively working on 6.0 and I hope I can release it out before next week. I am also working actively on a big release (after 6.0) which would bring additional hash algorithm supports in bminer.

And there will be support for Algo Equihash 96/5 (Mars) for coin MinexCoin?

[philipma1957]

I am actively working on 6.0 and I hope I can release it out before next week. I am also working actively on a big release (after 6.0) which would bring additional hash algorithm supports in bminer.

I am not ignoring any of your concerns. During the last two weeks, I just focused more on the development and did not get time to monitor bitcointalk thread.

Here are my answers to questions about console hashrate, rejected shares, and private connections. I will also update FAQ because these questions have been raised many times.

# Why the reported hashrate of Bminer is higher than the reported hashrate from mining pools?

Bminer reports hashrate generated by your *hardware*, while a mining pool
estimates the hashrate based on the number of submitted shares. The Bminer
hashrate is different from the pool hashrate because:

1. The Bminer reported hashrate includes the devfee.

2. A small portion of the generated shares may get rejected or become stale due
   to network delay and transmission problems. Bminer reported hashrate will
   include such shares, but such shares will not contribute to the pool
   estimated hashrate.

3. Your pool hashrate is an estimate based on received shares, therefore it
   will vary a lot unless you control a significant amount of hashpower and you
   run it over a long period of time.

4. Some pools may calculate the estimated hashrate incorrectly.

Specially, if you turn on nofee option. You will see the same number of
hashrate but the underlying computation is slowed down due to disabled
optimizations.

# Why I see rejected shares when using Bminer?

There are many reasons for rejected shares. Two primary reasons for rejected
shares are:

1. Network latency: If your latency to the connected pool is too long, then a
   valid share may become stale and invalid during the transmission. This will
   cause the share being rejected. The solution to this problem is to choose a
   pool server that has low latency connection to your rig.

2. Overclocking: Aggressive overclocking setting may cause GPU to produce
   incorrect results and therefore generates invalid shares being rejected.

Software bugs in Bminer may also cause a small portion of rejected shares. We
will keep improving bminer and reduce the number of rejected shares.

# Why Bminer starts private connections to bminer.me

The first communication checks the update and receives license information,
including for example where to mine devfee. Note that in this communication
bminer *does not send out any information*, it only receives information from
bminer.me.

The follow-up communications only send runtime information of bminer, like the
mining speed of each card and performance status. This may enable bminer to
choose better optimization strategies. Starting from version 6.0.0, these
follow-up communications will become transparent.

I am using bminer 5.4 from simplemining.net

https://www.nicehash.com/miner/3QPFEdX8rtXHoVZHct5eUbp7AK1t1vRMfL

will run it for a bit.  then run same gear on  dstm

I will also check to see if simplemining.net  will update to your latest version  6.0


to all  2%  is a huge amount of money  op has no incentive to steal as  people would just stop using his miner and go to dstm

lets see what my testing shows.

[supermoew]

Atleast acknowledge user concerns instead of completely ignoring them.

https://www.bminer.me/faq/

just found some answers here

[Scorpio777]

[quote author=realbminer
# Why the reported hashrate of Bminer is higher than the reported hashrate from mining pools?

Bminer reports hashrate generated by your *hardware*, while a mining pool
estimates the hashrate based on the number of submitted shares. The Bminer
hashrate is different from the pool hashrate because:

1. The Bminer reported hashrate includes the devfee.

2. A small portion of the generated shares may get rejected or become stale due
   to network delay and transmission problems. Bminer reported hashrate will
   include such shares, but such shares will not contribute to the pool
   estimated hashrate.

3. Your pool hashrate is an estimate based on received shares, therefore it
   will vary a lot unless you control a significant amount of hashpower and you
   run it over a long period of time.

4. Some pools may calculate the estimated hashrate incorrectly.

Specially, if you turn on nofee option. You will see the same number of
hashrate but the underlying computation is slowed down due to disabled
optimizations.
[/quote]
But the problem is that with DSTM in console my hasrate is 925sol and in the pool I have solid 900-910sol after 24 or 48 hours, as it should be with 2% devfee. And with bminer in the same conditions in console my hashrate is 955sol but in the pool after 24h only 860-870( And that is a big disappoint of bminer. I hope you will fix these issues in the future update)

[Bimmber]

Scorpio, pools do not know your hashrate, they only estimate it.