Find below information on setup of your miner for Verium and the file location
This is from the Github site:
Currently no pools available. You must run your own veriumd and point miners to that IP.
A verium.conf file must be configured (see Usage Instructions)
To use this miner, you can do one of the following:
[install dependencies for your os]
git clone https://github.com/VeriConomy/veriumMiner
cd veriumMiner
./build.sh
./cpuminer ...
[install dependencies for your os]
git clone https://github.com/VeriConomy/veriumMiner
cd veriumMiner
./autogen.sh
perl nomacro.pl
./configure CFLAGS="-O2" --with-curl --with-crypto
make clean && make
./cpuminer ...libcurl http://curl.haxx.se/libcurl/
jansson http://www.digip.org/jansson/ (jansson source is included in-tree)
openssl libcrypto https://www.openssl.org/
pthreads
zlib (for curl/ssl)
Ubuntu / Debian:
apt-get install automake autoconf pkg-config libcurl4-openssl-dev libjansson-dev libssl-dev libgmp-dev zlib1g-dev
FreeBSD:
pkg install automake autoconf git
Build libcurl by compiling and installing the curl port cd /usr/ports/ftp/curl; make install
git clone https://github.com/VeriConomy/veriumMiner
./build.shexport C_INCLUDE_PATH=$INCLUDE_PATH:/usr/local/include
export CPLUS_INCLUDE_PATH=$INCLUDE_PATH:/usr/local/include
export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib
./autogen.sh
/usr/local/bin/perl ./nomacro.pl
./configure CFLAGS="-march=native" --with-crypto --with-curl
make
Pacman -Syu
pacman -Sy mingw-w64-x86_64-gcc
pacman -Sy make
pacman -Sy automake
pacman -Sy autoconf
pacman -Sy mingw-w64-x86_64-curl
pacman -Sy curl libcurl libcurl-devel mingw-w64-x86_64-curl mingw-w64-x86_64-libwinpthread-git libopenssl openssl openssl-develDownload https://netix.dl.sourceforge.net/project/ezwinports/make-4.2.1-without-guile-w32-bin.zip
Copy everything in C:\msys64\mingw64 without replacing anything
Download and extract the Miner from Git, place it in C:\msys64
Open MSYS2 MinGW64 Shell:
cd /veriumMiner-master
./mingw64.sh
libeay32.dll, libjansson-4.dll, and libwinpthread-1.dll from the C:\msys64\mingw64\bin folder, as well as cpuminer.exe.-mfpu=neon to CFLAGS.Run "cpuminer --help" to see options.
Wallet verium.conf options generally would include the following:
Typical command line string to get you mining:
./cpuminer -o xxx.xxx.xxx.xxx:33987 -O username:password --coinbase-addr=walletaddress --no-longpoll --no-getwork --no-stratum --no-extranonce
This should get you mining hopefully with no errors. If you do have errors, please check your rpcworkqueue value in your config file, or on your verium daemon.
HugePages allow for faster memory lookups, which is very important for this miner. Enabling HugePages typically gets 10% or more performance.
To make matters complicated, there are two ways of doing this. One is transparent_hugepages one is preallocated. Even more complicated, one is sometimes faster than the other.
This miner will use transparent_hugepages by default.
To enable transparent_hugepages, (on Ubuntu 16.04): echo always | sudo tee /sys/kernel/mm/transparent_hugepage/enabled
To disable transparent_hugepages, (on Ubuntu 16.04): echo never | sudo tee /sys/kernel/mm/transparent_hugepage/enabled
To verify the status of transparent_hugepages cat /sys/kernel/mm/transparent_hugepage/enabled ([] will show around the current status).
To enable preallocated hugepages (on Ubuntu 16.04), first check that you have /proc/sys/vm/nr_hugepages by doing ls /proc/sys/vm (you should see nr_hugepages in the print out). Then,
sudo nano /etc/sysctl.conf,vm.nr_hugepages=sizeCtrl+O, then [Enter], then Ctrl+X.sudo sysctl -pTo disable:
sudo nano /etc/sysctl.conf,vm.nr_hugepages=sizeCtrl+O, then [Enter], then Ctrl+X.sudo sysctl -pNote that you can also reboot and this will cause HugePages to allocate / deallocate.
When enabling, you should see vm.nr_hugepages=size print out on the console. If not, check your distro. You may need to recompile your kernel to enable this. You can also verify that memory is allocated by running free and seeing that you now have a ton of memory allocated, but aren't running anything that's using it.
size = (the amount of memory each miner thread needs) / (2048 * 1024).
How much memory is be used per thread?
Multiply that number by the number of threads, and you will have the size needed. Note, you may not have enough RAM for this on ARM SoCs. The miner should still work, but it will not be as optimal.
For example, 4 threads on an SSE4, you'd type vm.nr_hugepages=772. Since 4 (threads) * 193 (hugepages per thread) = 772.
You can now specify a number of 'oneway' threads to acompany your 'default way' threads. Default way is determined by your CPU instruction set.
'-1 n' will specify the number of oneway threads to spawn. You can also use --oneways n. Some folks (on arm especially) see perf gains due to the implementation. Additionally, there are new options to help control affinity for these threads and 'default' way threads too. --cpu-affinity-stride N, --cpu-affinity-default-index N, --cpu-affinity-oneway-index N, and --cpu-priority-oneway 0-5
Affinity stride works by saying how many cpus should be skipped before assigning the thread to it. So, if you have 8 cpu's and set 'stride' to 3, you will start with CPU (0 + 3 * 0), then CPU (0 + 3 * 1), then CPU (0 + 3 * 2), aka CPU's 0, 3, 6. 'default' index is the starting index ('0' in the example) for the number of -t threads. 'oneway-index' is the starting index for oneway -1 threads.
Play around with them, and pass -D to get some debug output.
e.g, 'Bind oneways to odd threads, 'defaults' to even threads: ./cpuminer ... -t 4 -1 4 --cpu-affinity-stride 2 --cpu-affinity-default-index 0 --cpu-affinity-oneway-index 1 e.g.2, 'Bind oneways to the last 4 cpu's after the defaults' ./cpuminer ... -t 4 -1 4 --cpu-affinity-stride 1 --cpu-affinity-default-index 0 --cpu-affinity-oneway-index 4 (edited)
--ryzen.Ryzen's implementation of AVX2 is ... subpar. Please pass --ryzen on the commandline to default to the AVX implementation. Users reported ~25% gains.
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.
Some people have reported increases by using GCC 7.2. Please note, this will replace your existing GCC installation, which may become unrecoverable if any errors occur in the make process.
To build and install GCC 7.2 on Ubuntu do the following:
apt-get -y install unzip flexwget https://github.com/gcc-mirror/gcc/archive/gcc-7_2_0-release.zipunzip gcc-7_2_0-release.zipcd gcc-gcc-7_2_0-releasesudo ./contrib/download_prerequisitesmkdir build && cd build../configure --enable-languages=c,c++ --disable-multilibmake -j 8make install
CPUMiner-multi was forked from pooler's CPUMiner, and has been started by Lucas Jones.
GPLv2. See COPYING for details.