Author

Topic: [ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9 - page 116. (Read 148347 times)

newbie
Activity: 50
Merit: 0
I've heard a lot of rumors on bminer

Do you trust bminer / use it?

Have you compared it w/ dstm and if so which one earned more (side by side comparison is needed not one after the other)


There seems to be a lot of hate against bminer, anyone have some good links to facts supporting X claim?

several people have tried to compare side by side but they don't have enough hashrate to make it accurate. you should take 2 rigs and compare them for your youtube channel. just run them for 24 hours, swap dstm/bminer on each rig at the 12 hour mark and see what you find out. or do it for a 3 days etc.

i know bminer over reports on the console for sure. i've tried it for a few weeks on my 1070ti rig and it was stable/consistent, seemed like it could be a tad faster than dstm...but without running side by side at the same time, who knows lol.

side note, how is your mining room remodel going?
newbie
Activity: 9
Merit: 0
So after testing Bminer more and more
i found out that the program isnt accurate and shows false numbers

the hashrate is not accurate
i mined using 2 rigs 1 with bminer with 6 gpus each at over 520~530 sols and 1 with dstm at 490 ~ 500sols

dstm stil mined more coins in comparision after 24hours

so either bminer shows false sols or bminer mines for someone else

this is my post from the other day


here is a test i ran for exactly 24 hours of mining

6X ZOTAC 1070 AMP EX
GPUs are OCd to 450 memory clock and 70 core clock with 120 power 100 volt
TEMP at 50~60

i mined ZCASH using BMINER @ 3100 sols 3.1KHs
every gpu was giving me over 500 sols and some ran at 520 sols
using miningpoolhub

i only mined .02708199 ZCASH ( around 11$ with current rate)
what to mine showed around 14~15$ by that time in 24h
the miner never stoped and never crashed it ran for a straight 24hours

is what i mined accurate?



this was an old test i ran by that time... my friend has .03 zcash coins mined incomparision


i dont want to throw out accusations but this is what i came up with after testing bminer



I think that won't be an accurate test because amount of mined coins could vary depending on the difficulty. What I personally did is put EWFB/DSTM to mine for 24 to 48 hours and check the average speed reported to the pool (make sure the pool/miner doesn't get down in that time) and then do the same with Bminer

I'm personally getting more average speed on the pool, aside from whatever it reports on the console. I'm even getting a bit less power consumption (using a wall plug to see this). I'm guessing this is because the cards are always at 100% so the power flow is more stable... but not sure.

However this is on SMOS (Linux)... on Windows bminer could be just worse than EWFB or DSTM. Actually on Windows I get more hashrate from EWFB/DSTM than on SMOS... so bminer might just be better than EWFB/DSTM only on Linux

Image for reference
https://d.pr/i/kwBVft
sr. member
Activity: 1414
Merit: 487
YouTube.com/VoskCoin
I've heard a lot of rumors on bminer

Do you trust bminer / use it?

Have you compared it w/ dstm and if so which one earned more (side by side comparison is needed not one after the other)


There seems to be a lot of hate against bminer, anyone have some good links to facts supporting X claim?
newbie
Activity: 29
Merit: 0
So after testing Bminer more and more
i found out that the program isnt accurate and shows false numbers

the hashrate is not accurate
i mined using 2 rigs 1 with bminer with 6 gpus each at over 520~530 sols and 1 with dstm at 490 ~ 500sols

dstm stil mined more coins in comparision after 24hours

so either bminer shows false sols or bminer mines for someone else

this is my post from the other day


here is a test i ran for exactly 24 hours of mining

6X ZOTAC 1070 AMP EX
GPUs are OCd to 450 memory clock and 70 core clock with 120 power 100 volt
TEMP at 50~60

i mined ZCASH using BMINER @ 3100 sols 3.1KHs
every gpu was giving me over 500 sols and some ran at 520 sols
using miningpoolhub

i only mined .02708199 ZCASH ( around 11$ with current rate)
what to mine showed around 14~15$ by that time in 24h
the miner never stoped and never crashed it ran for a straight 24hours

is what i mined accurate?



this was an old test i ran by that time... my friend has .03 zcash coins mined incomparision


i dont want to throw out accusations but this is what i came up with after testing bminer

hero member
Activity: 789
Merit: 501
Nice and fast.

On my 2 GTX 1080
[GPU 0] Speed: 521.34 Sol/s 279.19 Nonce/s Temp: 68C Power: 121W 4.31 Sol/J
[GPU 1] Speed: 558.37 Sol/s 296.42 Nonce/s Temp: 59C Power: 129W 4.33 Sol/J

I just add it to my monitorig tool to manage it Smiley
https://bitcointalksearch.org/topic/m.31663967
newbie
Activity: 210
Merit: 0
You don`t need to post, you can just click WATCH and NOTIFY buttons in top right corner...
jr. member
Activity: 50
Merit: 1
Posting here so it's easier for me to see replies and keep up with Bminer development.
sr. member
Activity: 441
Merit: 252
Posting here so it's easier for me to see replies and keep up with Bminer development.

(I run it on my SMOS rigs, but it's not in ETHOS yet so those rigs run EWBF/DSTM.)
newbie
Activity: 9
Merit: 0
I have a 8x 1080ti rig and bminer is definitively working way better than DSTM and EWFB. On the pool EWFB was about 5,74 Sol/s Average speed... now I've been using bminer and it's about 5,93 Sol/s

With EWFB on SMOS I was getting around 5700-5740, which is around 717 sol/s per card. This is not bad but individually on my Windows machine I was getting around 735-750. I was wondering why I wasn't getting more or less same speed on SMOS and it seems to be the miner (same EWFB on Windows and on SMOS)

Now with bminer I'm getting around 5940 sol/s on console and around the same on the pool.

The whole rig is also consuming around 50-70w less!

One interesting thing I noticed is that using the command nvidia-smi the usage of the cards was going from 90 to 100% using DSTM or EWFB but with bminer is always at 100%

newbie
Activity: 50
Merit: 0
realbminer,

you need to add the gpu identifier to your reporting for shares. how is anyone supposed to troubleshoot when we can't identify which gpu is having invalid solutions

Code:
[INFO] [2018-03-04T18:59:52-05:00] Total 3167.89 Sol/s 1689.23 Nonce/s Accepted shares 14916 Rejected shares 90
[INFO] [2018-03-04T18:59:57-05:00] Received new job ece94fb45eb66adb8a4c       
[WARN] [2018-03-04T18:59:57-05:00] Rejected share #15010 ([20, "Invalid Equihash solution"])
[INFO] [2018-03-04T19:00:02-05:00] Accepted share #15011                       
                 
newbie
Activity: 10
Merit: 0

I'd like to see those stats for excavator, keep up the good work.  Its well built, im pretty sure reporting is accurate and overall speeds should be pretty good.
...
Just started up Bminer 5.4.0 allowing devfee, so lets see what a week can do there. :-)
Sheet updated a week later, once again. But, I could use some help interpreting some of the numbers.

As you can clearly see on the Shares sheet, Nanopool reports quite a few more shares from Bminer than the others I've tested.

Now, maybe someone can explain to me why payments are being stretched out into more time? Is the difficulty increasing? If so, why wouldn't I be sending fewer shares?

Also, what shares is Bminer reporting in its log?
I grabbed a couple of lines as far back as my cmd session would allow, and then some of the latest lines.

It seems Bminer is nice and stable and keeps counting Accepted shares with a fairly low number of Rejected shares. But, this number of accepted shares is nowhere near the number of shares reported by Nanopool. Please, can someone explain the difference in numbers to me.

Code:
[INFO] [2018-03-03T21:44:06+01:00] Total 443.89 Sol/s 238.26 Nonce/s Accepted shares 8827 Rejected shares 38
[INFO] [2018-03-03T21:44:36+01:00] [GPU 0] Speed: 447.78 Sol/s 238.34 Nonce/s Temp: 65C Power: 150W 2.99 Sol/J
[INFO] [2018-03-03T21:44:36+01:00] Total 447.78 Sol/s 238.34 Nonce/s Accepted shares 8827 Rejected shares 38
[INFO] [2018-03-03T21:44:59+01:00] Received new job 1520028718
[INFO] [2018-03-03T21:45:06+01:00] [GPU 0] Speed: 447.76 Sol/s 238.39 Nonce/s Temp: 64C Power: 152W 2.95 Sol/J
[INFO] [2018-03-03T21:45:06+01:00] Total 447.76 Sol/s 238.39 Nonce/s Accepted shares 8827 Rejected shares 38
[INFO] [2018-03-03T21:45:36+01:00] [GPU 0] Speed: 447.40 Sol/s 238.42 Nonce/s Temp: 65C Power: 149W 3.00 Sol/J
[INFO] [2018-03-03T21:45:36+01:00] Total 447.40 Sol/s 238.42 Nonce/s Accepted shares 8827 Rejected shares 38
[INFO] [2018-03-03T21:46:00+01:00] Received new job 1520028719
[INFO] [2018-03-03T21:46:06+01:00] [GPU 0] Speed: 446.06 Sol/s 238.26 Nonce/s Temp: 65C Power: 147W 3.03 Sol/J
[INFO] [2018-03-03T21:46:06+01:00] Total 446.06 Sol/s 238.26 Nonce/s Accepted shares 8827 Rejected shares 38
[INFO] [2018-03-03T21:46:36+01:00] [GPU 0] Speed: 444.67 Sol/s 238.34 Nonce/s Temp: 65C Power: 149W 2.98 Sol/J
[INFO] [2018-03-03T21:46:36+01:00] Total 444.67 Sol/s 238.34 Nonce/s Accepted shares 8827 Rejected shares 38
[INFO] [2018-03-03T21:46:44+01:00] Accepted share #8869
[INFO] [2018-03-03T21:46:44+01:00] Accepted share #8870
[INFO] [2018-03-03T21:46:44+01:00] Accepted share #8871
...
[INFO] [2018-03-04T21:52:47+01:00] Received new job 1520096193
[INFO] [2018-03-04T21:53:06+01:00] [GPU 0] Speed: 445.63 Sol/s 237.40 Nonce/s Temp: 66C Power: 148W 3.01 Sol/J
[INFO] [2018-03-04T21:53:06+01:00] Total 445.63 Sol/s 237.40 Nonce/s Accepted shares 10262 Rejected shares 47
[INFO] [2018-03-04T21:53:20+01:00] Accepted share #10313
[INFO] [2018-03-04T21:53:36+01:00] [GPU 0] Speed: 450.07 Sol/s 237.36 Nonce/s Temp: 66C Power: 147W 3.06 Sol/J
[INFO] [2018-03-04T21:53:36+01:00] Total 450.07 Sol/s 237.36 Nonce/s Accepted shares 10263 Rejected shares 47
[INFO] [2018-03-04T21:53:48+01:00] Received new job 1520096194
[INFO] [2018-03-04T21:54:06+01:00] [GPU 0] Speed: 447.56 Sol/s 237.57 Nonce/s Temp: 66C Power: 144W 3.11 Sol/J
[INFO] [2018-03-04T21:54:06+01:00] Total 447.56 Sol/s 237.57 Nonce/s Accepted shares 10263 Rejected shares 47
[INFO] [2018-03-04T21:54:06+01:00] Accepted share #10314
[INFO] [2018-03-04T21:54:19+01:00] Received new job 1520096195
[INFO] [2018-03-04T21:54:36+01:00] [GPU 0] Speed: 447.01 Sol/s 237.72 Nonce/s Temp: 65C Power: 147W 3.04 Sol/J
[INFO] [2018-03-04T21:54:36+01:00] Total 447.01 Sol/s 237.72 Nonce/s Accepted shares 10264 Rejected shares 47
[INFO] [2018-03-04T21:55:06+01:00] [GPU 0] Speed: 447.31 Sol/s 237.80 Nonce/s Temp: 65C Power: 146W 3.06 Sol/J
[INFO] [2018-03-04T21:55:06+01:00] Total 447.31 Sol/s 237.80 Nonce/s Accepted shares 10264 Rejected shares 47
[INFO] [2018-03-04T21:55:19+01:00] Received new job 1520096196
[INFO] [2018-03-04T21:55:36+01:00] [GPU 0] Speed: 446.88 Sol/s 237.84 Nonce/s Temp: 65C Power: 147W 3.04 Sol/J
[INFO] [2018-03-04T21:55:36+01:00] Total 446.88 Sol/s 237.84 Nonce/s Accepted shares 10264 Rejected shares 47
newbie
Activity: 141
Merit: 0
how you adding email for nanopool ?

bminer -uri stratum://[email protected]:6666

BTC




-uri stratum://.$rigName.:[email protected]:6666 -no-timestamps -api 127.0.0.1:1880
member
Activity: 126
Merit: 11
Just FYI,

I have noticed a number of occurrences that a GPU crash will cause a restart with all miners mining directly to the dev pool.

I do not mine to nanopool, as I mine to a local private pool.

I found this while trying to identify a GPU that was not stable in the rig.


Code:
[INFO] [2018-03-04T13:29:33+11:00] Accepted share #40
[INFO] [2018-03-04T13:29:34+11:00] Accepted share #41
[FATA] [2018-03-04T13:29:40+11:00] Fatal cuda error in GPU 0. Terminate soon...

[WARN] [2018-03-04T13:29:41+11:00] Miner died! It will be restarted soon...
[INFO] [2018-03-04T13:29:47+11:00] Bminer: When Crypto-mining Made Fast (v5.4.0-ae18e12)
[INFO] [2018-03-04T13:29:47+11:00] Watchdog has started.
[INFO] [2018-03-04T13:29:47+11:00] Starting miner on devices [0 1 2 3 4]
[INFO] [2018-03-04T13:29:48+11:00] Starting miner on device 0...
[INFO] [2018-03-04T13:29:48+11:00] Connected to zec-eu1.nanopool.org:6666
[INFO] [2018-03-04T13:29:48+11:00] Started miner on device 0
[INFO] [2018-03-04T13:29:48+11:00] Starting miner on device 1...
[INFO] [2018-03-04T13:29:48+11:00] Started miner on device 1
[INFO] [2018-03-04T13:29:48+11:00] Subscribed to stratum server
[INFO] [2018-03-04T13:29:48+11:00] Set nonce to 5b800000000000004423afba09478925
[INFO] [2018-03-04T13:29:48+11:00] Set target to 000000000000000000000000000000000000000000000000000000005c8f0200
[INFO] [2018-03-04T13:29:48+11:00] Starting miner on device 2...
[INFO] [2018-03-04T13:29:48+11:00] Started miner on device 2
[INFO] [2018-03-04T13:29:48+11:00] Starting miner on device 3...
[INFO] [2018-03-04T13:29:48+11:00] Authorized
[INFO] [2018-03-04T13:29:48+11:00] Received new job 1520082352
[INFO] [2018-03-04T13:29:49+11:00] Started miner on device 3
[INFO] [2018-03-04T13:29:49+11:00] Starting miner on device 4...
newbie
Activity: 1
Merit: 0
What a load a horseshite ... you continue to be totally vague, despite repeated requests for actual details and explanations. You must think we're all stupid. Let's see:

The first communication checks the update and receives license information, including for example where to mine devfee. Because of security reasons, it would be very hard to eliminate this private communication.

Total BS. If that were true, all miners would require it. What security concerns? Explain it to the experts. I'm a dev myself. Let's hear it.

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.

Complete BS. You don't need to call back home to enable optimizations. Build them into the executable like any sane developer.

I understand your concerns about the private connection. In future, I will consider making the follow-up runtime communications transparent. Or alternatively, I can create an option to opt-out the communications.

Remove it. Can't you see it's the biggest reason why people hate you and your miner?

Right now it all screams that you are shady. Sorry, but the repeated times you were called out on this and failed to provide details to reassure users all point to hidden interests.

I've been working really hard to try to expose what's being sent back and forth to his servers, but he's gone to great lengths to protect it. So far, here's what I've found:

This is the communication that occurs as soon as you start the miner (there's also some unprintable characters which I omitted, I believe this is encrypted info that I won't be able to break):
GET https://api.bminer.me/v1/init/zec/520 HTTP/1.1
User-Agent: Go-http-client/1.1
Content-Type: application/octet-stream
Accept-Encoding: gzip
stratum+ssl://[email protected]:6633/
-----BEGIN CERTIFICATE-----
MIID/DCCAuagAwIBAgIID+rOSdTGfGcwCwYJKoZIhvcNAQELMIGLMQswCQYDVQQG
EwJVUzEZMBcGA1UEChMQQ2xvdWRGbGFyZSwgSW5jLjE0MDIGA1UECxMrQ2xvdWRG
bGFyZSBPcmlnaW4gU1NMIENlcnRpZmljYXRlIEF1dGhvcml0eTEWMBQGA1UEBxMN
U2FuIEZyYW5jaXNjbzETMBEGA1UECBMKQ2FsaWZvcm5pYTAeFw0xNDExMTMyMDM4
NTBaFw0xOTExMTQwMTQzNTBaMIGLMQswCQYDVQQGEwJVUzEZMBcGA1UEChMQQ2xv
dWRGbGFyZSwgSW5jLjE0MDIGA1UECxMrQ2xvdWRGbGFyZSBPcmlnaW4gU1NMIENl
cnRpZmljYXRlIEF1dGhvcml0eTEWMBQGA1UEBxMNU2FuIEZyYW5jaXNjbzETMBEG
A1UECBMKQ2FsaWZvcm5pYTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AMBIlWf1KEKR5hbB75OYrAcUXobpD/AxvSYRXr91mbRu+lqE7YbyyRUShQh15lem
ef+umeEtPZoLFLhcLyczJxOhI+siLGDQm/a/UDkWvAXYa5DZ+pHU5ct5nZ8pGzqJ
p8G1Hy5RMVYDXZT9F6EaHjMG0OOffH6Ih25TtgfyyrjXycwDH0u6GXt+G/rywcqz
/9W4Aki3XNQMUHNQAtBLEEIYHMkyTYJxuL2tXO6ID5cCsoWw8meHufTeZW2DyUpl
yP3AHt4149RQSyWZMJ6AyntL9d8Xhfpxd9rJkh9Kge2iV9rQTFuE1rRT5s7OSJcK
xUsklgHcGHYMcNfNMilNHb8CAwEAAaNmMGQwDgYDVR0PAQH/BAQDAgAGMBIGA1Ud
EwEB/wQIMAYBAf8CAQIwHQYDVR0OBBYEFCToU1ddfDRAh6nrlNu64RZ4/CmkMB8G
A1UdIwQYMBaAFCToU1ddfDRAh6nrlNu64RZ4/CmkMAsGCSqGSIb3DQEBCwOCAQEA
cQDBVAoRrhhsGegsSFsv1w8v27zzHKaJNv6ffLGIRvXK8VKKK0gKXh2zQtN9SnaD
gYNe7Pr4C3I8ooYKRJJWLsmEHdGdnYYmj0OJfGrfQf6MLIc/11bQhLepZTxdhFYh
QGgDl6gRmb8aDwk7Q92BPvek5nMzaWlP82ixavvYI+okoSY8pwdcVKobx6rWzMWz
ZEC9M6H3F0dDYE23XcCFIdgNSAmmGyXPBstOe0aAJXwJTxOEPn36VWr0PKIQJy5Y
4o1wpMpqCOIwWc8J9REV/REzN6Z1LXImdUgXIXOwrz56gKUJzPejtBQyIGj0mveX
Fu6q54beR89jDc+oABmOgg==
-----END CERTIFICATE-----

I'm reasonably sure this is Nanopool's cert which he uses explicitly to prevent cert forging and MITM attacks on his devfee.

This is the communication that occurs every 10-15 minutes or so (note the content length is way higher than the content which means im missing stuff, possibly speeds):
POST https://api.bminer.me/v1/stats/zec/520 HTTP/1.1
Host: api.bminer.me
User-Agent: Go-http-client/1.1
Content-Length: 727
Content-Type: application/octet-stream
Accept-Encoding: gzip
Connection: close
Linux*
GenuineIntel
GeForce GTX 1080 9GB
(GPU-5bea6e5b-1234-4321-abab-12b7e7a78789
0000:00:00.0
GeForce GTX 1080 9GB
(GPU-5bea6e5b-1234-4321-abab-12b7e7a78789
0000:00:00.0
GeForce GTX 1080 9GB
(GPU-5bea6e5b-1234-4321-abab-12b7e7a78789
0000:00:00.0
GeForce GTX 1080 9GB
(GPU-5bea6e5b-1234-4321-abab-12b7e7a78789
0000:00:00.0
GeForce GTX 1080 9GB
(GPU-5bea6e5b-1234-4321-abab-12b7e7a78789
0000:00:00.0
GeForce GTX 1080 9GB
(GPU-5bea6e5b-1234-4321-abab-12b7e7a78789
0000:00:00.0

Make your own opinions I guess.

cc. @cryptoyes

Can you try to modify the wallet address? does it works?
newbie
Activity: 13
Merit: 0
I made a little comparison between Bminer 5.4.0 and DSTM 0.6 (24h for both) on my GTX1080+GTX970 (MSI Gaming)...
The results is:
In the miners console my speed are:
- In Bminer: for GTX1080 - 600Sol, for GTX970 - 350Sol (950sol for both)
- In DSTM:  for GTX1080 - 580Sol, for GTX970 - 340Sol (920sol for both)
But my pool (Viabtc) report that hashrate after 24h is: 890-900sol for DSTM (as it should be with 2% devfee and 0.5% rejected shares) and only 850-860 for Bminer (with nofee or with) -10%!!!
And with bminer I have a little more rejected shares (1.2% vs 0.5% on DSTM).
On the bminer side is more stable work (with DSTM I need to reduce a little my VGAs clocks). In my opinion - bminer is a good and stable miner but in final result on the pool it is not as fast as it report in console, or it work for someone else more often than it should be and without my permission?...
Conclusion: for now I will stay with DSTM, but keep waiting for a new version of Bminer with more stable and honest hashrate, because I like this miner for its stable work. Good luck Reallbminer and don't give up!    
newbie
Activity: 1
Merit: 0
how you adding email for nanopool ?

bminer -uri stratum://[email protected]:6666

BTC


newbie
Activity: 93
Merit: 0
Dev needs to address these issues, but he's nowhere. I'm uninstalling, too risky
newbie
Activity: 64
Merit: 0
@realbminer not saying this miner is a Trojan horse, but it was working ok for many hours then in the night suddenly it started using all my hash for miners using it "Bminer 5.4" to mine somewhere else with IP address amazon compute(i.e. hosted by amazon) and some other places there was no change on the console nor was there a disconnect from the miner just that all shares found where going else where and my pool address share rate went to zero for about 30-60 minutes though miners where mining for all systems using the miner.

That is miner was mining for someone else for 30-60 minutes(not fee mining), this could have been triggered remotely by you as the miner appears shady, you need to explain, also there maybe a back door author uses to access mining machines using windows RDP (I had to disable this as passwords no longer accepted on some systems for RDP sessions)



https://imgur.com/a/ANf3N

I had same issue. Worked for one hour then all my hashpower got robbed.

How many people having this issue? I used for more than 24 hours, it behaves as intended, just 2% fee.
newbie
Activity: 25
Merit: 0
You guys tried https://www.forgetop.com/ for equihash mining !? Really nice pool, only just found it and very stable/fair which is always a plus these days  Smiley


First block reward already sent  Grin Grin

https://zclexplorer.forgetop.com/tx/bc152f41ef2edf25fc2976347bac6711085296caa20dd10b3f11d8d0c1f29367

Also this is a new block explorer gift for the community, since it seems every one abandoned  the old ones.. (it is still synchronizing slowly but it will catch up!)


So in short - you are welcome to the new ZCL pool https://forgetop.com

If you hurry up you will be able to get the 0% mining fee , there is still some days left  Grin

Happy mining to all!


Wow that's awesome. Such a unique pool. Had no issues yet and payout always on time!  Cool Thanks so much for making the process easy!
jr. member
Activity: 108
Merit: 1
Fatal cuda error in GPU 6. Terminate soon...

anyone had experience with this kind of error?

This could be a problem with the card or the rig in general, too much overclock, faulty riser, not enough power supply, i had same issue with one rig removed one card and everything is stable for a week now since.
Jump to: