CPU miner for Litecoin and Bitcoin
C Assembly C++ Other
Pull request Compare This branch is 2 commits ahead, 1 commit behind CohibAA:master.
Latest commit 3f129a4 Nov 14, 2014 @Bitcoines add md
Failed to load latest commit information.
AUTHORS Version 2.0 Jan 16, 2012
Dockerfile Add dockerfile Dec 13, 2013
LICENSE Convert over to autotools. Release version 0.1. Nov 25, 2010
README Compile Fix Nov 14, 2014
README.md add md Nov 14, 2014
configure.ac Version 2.4 May 20, 2014
scrypt-arm.S Add support for scrypt(N, 1, 1) May 25, 2014
scrypt-x86.S Add support for scrypt(N, 1, 1) May 25, 2014
sha2-x64.S Add a configure option to disable assembly code May 16, 2014
sha2.c Add a configure option to disable assembly code May 16, 2014
util.c yescrypt support init Sep 12, 2014
yescrypt.c yescrypt support init Sep 12, 2014
yescrypt.h yescrypt support init Sep 12, 2014


This is a multi-threaded CPU miner for GlobalBoost-Y (BSTY) using the Yescrypt Algorithm

(fork of Jeff Garzik's reference cpuminer)

License: GPLv2. See COPYING for details.

Git tree: https://github.com/noncepool/cpuminer-yescrypt

Windows Binary: https://mega.co.nz/#!uQEQVCbD!PXXZzUHRWA0rnUQWRAp9uAKvCO6222aH1IvWWikLFU8


libcurl         [http://curl.haxx.se/libcurl/](http://curl.haxx.se/libcurl/)
jansson         [http://www.digip.org/jansson/](http://www.digip.org/jansson/)
    (jansson is included in-tree)

Install Build Dependencies on Debian, Ubuntu and other APT-based distros:

sudo apt-get install build-essential libcurl4-openssl-dev

Install Build Dependencies on Fedora, RHEL, CentOS and other yum-based distros:

sudo yum install gcc make curl-devel

Install Build Dependencies on OpenSUSE and other ZYpp-based distros:

sudo zypper in gcc make libcurl-devel

Basic *nix build instructions:

./autogen.sh    # only needed if building from git repo
./nomacro.pl    # only needed if building on Mac OS X or with Clang
./configure CFLAGS="-O3"

Notes for AIX users:

* To build a 64-bit binary, export OBJECT_MODE=64
* GNU-style long options are not supported, but are accessible
  via configuration file

Basic Windows build instructions, using MinGW:

Install MinGW and the MSYS Developer Tool Kit (http://www.mingw.org/)
* Make sure you have mstcpip.h in MinGW\include

If using MinGW-w64, install pthreads-w64

Install libcurl devel (http://curl.haxx.se/download.html)

    * Make sure you have libcurl.m4 in MinGW\share\aclocal
    * Make sure you have curl-config in MinGW\bin

In the MSYS shell, run:

./autogen.sh    # only needed if building from git repo
LIBCURL="-lcurldll" ./configure CFLAGS="-O3"

Architecture-specific notes:

ARM:    No runtime CPU detection. The miner can take advantage
    of some instructions specific to ARMv5E and later processors,
    but the decision whether to use them is made at compile time,
    based on compiler-defined macros.

    To use NEON instructions, add "-mfpu=neon" to CFLAGS.

x86:    The miner checks for SSE2 instructions support at runtime,
    and uses them if they are available.

x86-64: The miner can take advantage of AVX, AVX2 and XOP instructions,
    but only if both the CPU and the operating system support them.

        * Linux supports AVX starting from kernel version 2.6.30.
        * FreeBSD supports AVX starting with 9.1-RELEASE.
        * Mac OS X added AVX support in the 10.6.8 update.
        * Windows supports AVX starting from Windows 7 SP1 and
          Windows Server 2008 R2 SP1.

    The configure script outputs a warning if the assembler
    doesn't support some instruction sets. In that case, the miner
    can still be built, but unavailable optimizations are left off.

Usage instructions: Run "minerd --help" to see options.

To Connect to BSTY-P2Pool using your GlobalBoost-Y Wallet Address: ./minerd --algo=yescrypt -o -u BSTYaddress -p x

Note: Do not mine to online wallet addresses, including exchanges, as you may experience loss of coins due to how newly mined coins are confirmed.

Connecting through a proxy: Use the --proxy option.

To use a SOCKS proxy, add a socks4:// or socks5:// prefix to the proxy host.

Protocols socks4a and socks5h, allowing remote name resolving, are also available since libcurl 7.18.0.

If no protocol is specified, the proxy is assumed to be a HTTP proxy.

When the --proxy option is not used, the program honors the http_proxy and all_proxy environment variables.

Also many issues and FAQs are covered in these forum threads dedicated to this program: