BFGMiner 4.5 Run-Down for Scrypt Miners

BFGMiner 4.5 is now available with a myriad of features and improvements for both Scrypt and SHA-2 mining. As the current maintainer of Scrypt support in BFGMiner, I thought I’d highlight some of the features that I’m excited about in this release.

Per-core mining stats for GridSeed and ZeusMiner ASICs

It is now possible to view per-core statistics for both GridSeed and ZeusMiner Scrypt ASICs. To take advantage of this feature, press the [D] key in the UI and then press [M] to enable processor-level statistics. Finally press [Return] to return to the main BFGMiner UI.
BFGMiner GridSeed Per-Core
BFGMiner ZeusMiner Per-Core

View / set clock frequency for GridSeed and ZeusMiner ASICs within the UI

Prior to BFGMiner 4.5, while you could change the clock speed for Scrypt ASICs via the command line, you could not make those changes within the UI. Starting with version 4.5 it is now possible to both view and change the frequency for GridSeed and ZeusMiner ASICs in the UI.

To do this, press the [M] key in the UI and then [Up] and [Down] arrows to view the clock speed of your ASICs. To change the frequency of a device, press the [C] key and enter the desired frequency followed by [Return].
BFGMiner GridSeed TUI
BFGMiner ZeusMiner TUI

Support for 256-chip ZeusMiner ASICs

Version 4.5 of BFGMiner provides official support for the 256-chip ZeusMiner-powered War Machine from GAW Miners. Simply pass in the number of chips using the --set argument to get started:

bfgminer -S zus:all --set zus:chips=256 --scrypt -o hostname -u username -p password
BFGMiner ZeusMiner 256-chips

Set clock frequency for ZeusMiner ASICs via the RPC API

It is now possible to set the clock frequency for ZeusMiner ASICs while mining via the RPC API (this was already supported with GridSeed ASICs). For instance, to set the frequency for the first ASIC to 330:


Improved compatibility with broken Scrypt pool implementations

Finally, BFGMiner 4.5 introduces improved compatibility with Scrypt pools that request a difficulty that is multiplied by the constant 0x10000. This is a standing convention with Scrypt pool implementations that BFGMiner has deprecated for some time. We are actively working with pool authors to upgrade their implementations to remove this unnecessary complication. For instance, P2Pool has merged a fix here.

For more details on the temporary compatibility fix you can reference the code here.


You can find downloads and resources for BFGMiner on Windows, Linux, OS X, and embedded devices here. If you are interested in running BFGMiner 4.5 on the TP-Link 703n router you can download firmware here.

Have fun and happy mining!

4 thoughts on “BFGMiner 4.5 Run-Down for Scrypt Miners

  1. Tim

    Hi there,

    i am currently experiencing that the latest version of bgminer (4.5.1) is randomly loosing connection to my pool.
    I just get the message “all pools are dead”, but my internet connection is fine and a restart fixes the problem.
    Any idea what is wrong there ?
    My setup is Mavericks Server with a Rockminer R-Box and a Jalapeño. I disabled app nap on the Terminal in which i run bfgminer. My pool is the bitminter pool.
    This hickup started when i switched from 3.1.0 to 4.5.1.


  2. Pingback: Review: Gaw miners Fury (Zeus) Asic Scrypt Miner

  3. JoeFab

    Nice job Nate!

    Is there any chance we will be able to get per miner chips/clock setting during the scan for hardware? I am trying to consolidate my miners into one instance of bfgminer in Minera, but they have different chip counts and clock speeds (a falcon, a black widow and a lightning x6).


  4. John

    Great job! Checked out the latest git repository, compiled and it all worked like a dream!

    Is there a plan to support SHA256 with GridSeed Orb devices?



Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>