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.