https://wiki.vericoin.info/api.php?action=feedcontributions&user=Benzini&feedformat=atomVeriCoin & Verium Wiki - User contributions [en]2024-03-28T15:40:41ZUser contributionsMediaWiki 1.26.3https://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1515Verium Mining2020-07-11T19:16:48Z<p>Benzini: /* TheTinkeringTypist's CLI Monitor */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. While rare, when it occurs it is very lucrative. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
The payout algorithm of poolium, n3rd3d, beertendr and OVH recently was updated to [http://give-me-coins.com/support/faq/what-is-pplns/ PPLNS] to prevent pool hopping:<br />
<br />
<blockquote><br />
Pay Per Last N Shares (PPLNS) - A PPLNS pool is the same as a Prop pool in so much as the miner takes the risk of variance. Where they differ is how the payouts are calculated. PPLNS pools were designed to stop pool hoppers as they don’t technically payout the current block, rather they payout based on an average of the shares you submit over the last x number of blocks. As a result, when you first start mining on a PPLNS pool like d2’s pools you’ll notice that you hardly get paid anything until a few hours later. This will ramp up over time and once you stop mining, you still get paid for a few hours… this is due to the “buffer effect” of PPLNS and pool hoppers hate this as they cant jump on a fresh, profitable round! You, as a loyal miner still get the correct amount eventually but you have to be a bit patient for the ramp up and ramp down times.<br />
</blockquote><br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://www.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control (alternatively, you can re-use workers for multiple miners)<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
'''Special Hardware Guides:'''<br />
* [[Odroid]]<br />
* [[H96_Pro_Dongle_Mining]] or [[TV Box Mining|H96 s912 TV devices]]<br />
* [[Raspberry Pi]]<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
==== TheTinkeringTypist's CLI Monitor ====<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
URL: [https://github.com/thetinkeringtypist/verium-cli-monitor]<br />
<br />
A python script to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you are using a single miner or a miner bound to a different port number, change the ports in the list in monitor.py:<br />
<br />
#! monitor.py<br />
ports = [4048, 4049] #! NOTE: Change port numbers to those in use by your miners<br />
pool_mining = True #! NOTE: Change to False if solo mining<br />
<br />
Each miner has to be configured with the correct api-bind option at launch:<br />
<br />
cpuminer [options] --api-bind "0.0.0.0:<port-number>"<br />
<br />
So long as cpuminer is configured with the correct api-bind option, this script will work regardless of worker architecture.<br />
<br />
NOTE: different miners may not report all currently displayed information.<br />
<br />
==== g4b's CLI Monitor ====<br />
<br />
[[file:rigmon.png|thumb]]<br />
<br />
URL: [https://github.com/g4bwy/rigmon]<br />
<br />
Another python script to monitor miners, with focus on pool mining with grouped workers (ie. several cpuminer instances using the same pool worker id).<br />
<br />
Supports querying MPOS API to measure difference between cpuminer-reported hashrates and pool-reported hashrates.<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1460File:Cli monitoring.png2018-04-27T12:56:07Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1459Verium Mining2018-04-27T12:49:17Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. While rare, when it occurs it is very lucrative. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
The payout algorithm of n3rd3d, beertendr and OVH recently was updated to [http://give-me-coins.com/support/faq/what-is-pplns/ PPLNS] to prevent pool hopping:<br />
<br />
<blockquote><br />
Pay Per Last N Shares (PPLNS) - A PPLNS pool is the same as a Prop pool in so much as the miner takes the risk of variance. Where they differ is how the payouts are calculated. PPLNS pools were designed to stop pool hoppers as they don’t technically payout the current block, rather they payout based on an average of the shares you submit over the last x number of blocks. As a result, when you first start mining on a PPLNS pool like d2’s pools you’ll notice that you hardly get paid anything until a few hours later. This will ramp up over time and once you stop mining, you still get paid for a few hours… this is due to the “buffer effect” of PPLNS and pool hoppers hate this as they cant jump on a fresh, profitable round! You, as a loyal miner still get the correct amount eventually but you have to be a bit patient for the ramp up and ramp down times.<br />
</blockquote><br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
'''Special Hardware Guides:'''<br />
* [[Odroid]]<br />
* [[H96_Pro_Dongle_Mining]] or [[TV Box Mining|H96 s912 TV devices]]<br />
* [[Raspberry Pi]]<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor].<br />
<br />
A python script to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you are using a single miner or a miner bound to a different port number, change the ports in the list in monitor.py:<br />
<br />
#! monitor.py<br />
ports = [4048, 4049] #! NOTE: Change port numbers to those in use by your miners<br />
pool_mining = True #! NOTE: Change to False if solo mining<br />
<br />
Each miner has to be configured with the correct api-bind option at launch:<br />
<br />
cpuminer [options] --api-bind "0.0.0.0:<port-number>"<br />
<br />
So long as cpuminer is configured with the correct api-bind option, this script will work regardless of worker architecture.<br />
<br />
NOTE: different miners may not report all currently displayed information.<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1456File:Cli monitoring.png2018-04-22T18:06:07Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=Odroid&diff=1283Odroid2018-03-13T22:11:21Z<p>Benzini: /* Monitoring */</p>
<hr />
<div>Odroid XU4’s are popular. SBC systems in general are designed to be very power efficient, because of this they are pretty good at Verium mining. The downside is you need a lot of them to amass a sizeable amount of hashes. The up-front cost of SBC’s can be very high, but their power usage is very low. Remember to take into account all the required extras to make SBC’s function. (SD cards, power cables/supplies, network cables, switches, cooling, mounting mechanism, etc…) For SBCs the mining software usually needs to be compiled for 1way using 128 MB per thread. Many devices have been tested in terms of their hashrate and it can fairly be stated that the Odroid platform with its Octa core CPUs (Exynos5422 big.LITTLE) and 2 GB LPDDR3 RAM outperforms any other device. By now Odroid has even released a special version of the original XU4 which is called Odroid HC1 and is designed for clustering. It should be noted that despite their relative low total hasrate the ration hashrate per energy is still good. Also, there is software out in the community that helps on the maintenance of large clusters. For more information visit the [http://www.hardkernel.com official Odroid Website].<br />
<br />
== Optimized OS Image for Verium Mining ==<br />
[[File:Odroid_startup.png|thumb]]<br />
The ODROID Verium Mining Image (by joe_rondx) includes an optimized OS with preinstalled miner and several other handy features. It is made for the XU4 line, that is Odroid XU4, XU4Q, HC1, HC2, MC1. <br />
<br />
Performance features:<br />
* hugepages are enabled (thanks to birty & fireworm)<br />
* Maximal RAM clocking: 933 MHz<br />
* CPU downclocking of big cores: 1.9 GHz (read [[#Downclocking_.28yes.2C_down.21.29_the_CPU|here]] why 2 GHz is not worth it)<br />
* Optimal two miners configuration for big.LITTLE cores.<br />
Helper scripts:<br />
* Temperature logging in verium/cpu_temp.log<br />
* Status overview script vrmcheck.sh<br />
* Filesystem expansion by resize.sh<br />
<br />
[[File:Odroid_burn.png|thumb]]<br />
=== Setup the Image ===<br />
<br />
# [https://drive.google.com/open?id=1RbXnGUh5fwmfhMQNzefCK75PajyrXjQi Download] the Image. <br />
# Burn it without extracting it (The real issue is the following: the image consists of two partitions, if you extract the gz file you have to make sure you burn both partitions and not only the fat partition.) <br />
# On first bootup give it 5-10 mins time until you should be able to find the device in the network.<br />
# Log in with standard root/odroid<br />
<br />
=== Configuration of the Image ===<br />
<br />
The first thing you want to do is the configuration of the miner. The autostart of the miner is currently done<br />
in the rc.local file. <br />
nano /etc/rc.local <br />
At the end you will find two mining commands which you need to adjust for your pool/solo setup.<br />
<br />
In addition to the miner configuration you might want to change the hostname and password:<br />
nano /etc/hostname<br />
nano /etc/hosts<br />
passwd<br />
You can also expand the filesystem by using the script<br />
./resize.sh<br />
Reboot before going on<br />
reboot<br />
and run the resize script again<br />
./resize.sh<br />
<br />
==== Network ====<br />
<br />
Usually the Ethernet Port should just connect via DHCP. If you have a Wifi Stick you should use <br />
nmtui<br />
<br />
==== XU4 & XU4Q Tipps ====<br />
<br />
Since the image was created on an HC1 you might want to check the [[#Downclocking_the_GPU|GPU setting]].<br />
<br />
=== Usage and Monitoring ===<br />
<br />
There is a simple status script in the home directory, call<br />
./vrmcheck.sh<br />
which prints out the configuration in rc.local, the last 10 lines of each miner log, CPU frequency and the current temperature.<br />
<br />
Monitoring both miners is a bit of a challenge, but DerrickEs [https://github.com/derricke/MinerMonitor minerMonitor scripts] or casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor] support the configuration of ports (4048 & 4049 in this case). I also recommend mining on two pool to decentralize the hasrate, keep some hashes going if one pool is down and also for monitoring.<br />
<br />
=== Donation suggestion ===<br />
# The image starts mining right away - for joe_rondx (next version will include fireworm). This is not meant to be a rip off. Consider to have a freshly burned card mine for us perhaps one hour as initial donation.<br />
# If you are running less than 10 units (XU4, XU4Q, HC1, MC1/4) the initial donation is all we are asking for.<br />
# If you are running 10-19 units you may consider to have one small miner running on joe_rondx address.<br />
# If you are running 20-29 units you may consider to have one more small miner running on fireworms address.<br />
# If you are running 30-39 units you may consider to switch joes small miner to a big one.<br />
# If you are running 40-49 units you may consider to switch fireworms small miner to a big one.<br />
# If you are running 50+ units please also consider donating to the project via its donation page.<br />
Justification: Individual hasrates may vary, but let's assume you were getting 450 H/m per unit without<br />
this image. The image should give you 537 H/m which is an increase of nearly 20% . 10 units should produce<br />
5370 H/m while one small miner does about 137 H/m - which is about 2.5% of the total hashrate.<br />
<br />
== Other OS Images ==<br />
<br />
Let's start with special images by Odroid God birty: [https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk Odroid Miner images]<br />
In particular the newest image with enabled hugepages in combination with fireworms miner gives a significant boost of hashrate. It was used for the optimized image.<br />
<br />
Odroids [https://wiki.odroid.com/odroid-xu4/os_images/linux/start Official Images] are of course very well made. <br />
The newest Ubuntu Mate 16.04.3 (20171212) which was release after birtys image even has hugepages enabled. <br />
But unfortunately it uses too much RAM. Even more unfortunate is, that the Ubuntu 16.04.3 (20171213) (MINIMAL, BARE OS)<br />
image doesn't have hugepages enabled.<br />
<br />
I have once tested like 6 different images that are available for the XU4 platform.<br />
<br />
For the beginning I recommend the [http://dietpi.com/#download DietPi image] because its included diet-config tool already supports lots of the configurations you want to set. [http://dietpi.com/downloads/images/DietPi_OdroidXU4-armv7-(Jessie).7z Direct Link to image]<br />
<br />
The performance of [https://dl.armbian.com/odroidxu4/Ubuntu_xenial_default.7z Armbians headless 3.x kernel] was very good before the hugepages option was available.<br />
<br />
== Tweaking the OS for Mining ==<br />
<br />
The whole thing as a script (ARM Miner + XU4 Setup): [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh Download Shell script]<br />
wget https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh<br />
chmod +x 1wayARM_XU4_VeriumMiner_install.sh<br />
./1wayARM_XU4_VeriumMiner_install.sh<br />
<br />
=== Downclocking (yes, down!) the CPU ===<br />
<br />
To prevent throttleing due to heat it may actually increase your hashrate if the CPU doesn't run at 2 GHz (max). Even if you can prevent throttleing at 2GHz it is anyhow not worth it: you might get 10-15 H/m more but it costs about 2 Watts (out of 12) to get this last increase - so it won't pay back, for Details: [https://www.planet3dnow.de/vbulletin/threads/428622-Odroid-HC1 HC1 power benchmark].<br />
<br />
Install the utility (or use DietPi config)<br />
sudo apt-get install cpufrequtils<br />
use it directly <br />
sudo cpufreq-set -c 7 -u 1.9GHz -r<br />
and make the change permanent by creating a config file<br />
sudo nano /etc/default/cpufrequtils <br />
with the following settings<br />
ENABLE="true"<br />
GOVERNOR="performance"<br />
MAX_SPEED=1900000<br />
MIN_SPEED=1900000<br />
Now the CPU should always run at constant speed. This also saves a reasonable amount of power.<br />
<br />
=== Overclocking the RAM ===<br />
<br />
On the boot-FAT-Partition edit the boot.ini<br />
sudo nano boot.ini<br />
Find<br />
ddr_freq<br />
and change the value to 933<br />
# DRAM Frequency<br />
# Sets the LPDDR3 memory frequency<br />
# Supported values: 933 825 728 633 (MHZ)<br />
setenv ddr_freq 933<br />
<br />
Make sure before bootz to<br />
# set DDR frequency<br />
dmc ${ddr_freq} <br />
<br />
=== Downclocking the GPU ===<br />
<br />
Install this utility<br />
sudo apt-get install sysfsutils<br />
<br />
Then edit <br />
sudo nano /etc/sysfs.conf<br />
<br />
and insert the following line<br />
# Put GPU into powersave mode (= Downclocking it)<br />
devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor = powersave<br />
<br />
then start the service<br />
sudo service sysfsutils start<br />
<br />
Effect: reduced the power consumption by 0.7 – 0.8W, SOC will be 1-3°C cooler <br />
<br />
[https://obihoernchen.net/1340/lower-gpu-clock-of-odroid-xu4-for-headless-servers/ GPU for headless]<br />
<br />
Another way might be<br />
sudo nano /etc/rc.local<br />
and add this line before exit 0<br />
echo powersave > /sys/devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor<br />
<br />
=== Setting up a Swapfile ===<br />
<br />
Verium is memory intensive, so we increase the swap file (or use DietPi config)<br />
sudo fallocate -l 1G /var/swapfile<br />
sudo chmod 600 /var/swapfile<br />
sudo mkswap /var/swapfile<br />
sudo swapon /var/swapfile<br />
check it with <br />
free -h<br />
and configure that permanently<br />
sudo echo "/var/swapfile none swap sw 0 0" >> /etc/fstab<br />
<br />
=== Processes ===<br />
<br />
Further optimization can be done by checking the process tree<br />
pstree -p<br />
and disable/deinstall stuff that isn't needed. KILL 'EM ALL!<br />
<br />
I did not find it yet but if you come across ads7846 remove it.<br />
modprobe -r ads7846<br />
tee /etc/modprobe.d/blacklist-ads7846.conf <<< "ads7846"<br />
<br />
=== XU4 hardware ===<br />
<br />
The key is to exchange the thermal tape of the heatsink with some good thermal paste, decreases the temperature by 10 degrees (C) using same testing conditions. Also get the under side cooled as well.<br />
<br />
To save electricity you may turn down the power supplies voltage with a screw driver.<br />
<br />
Check sd card slot heat.<br />
<br />
== Optimal big.LITTLE and Maximal RAM Usage ==<br />
<br />
aka "Getting the last Hash out of your Odroid".<br />
<br />
The first step is to use an OS image that uses a minimum amount of RAM for the system.<br />
<br />
To illustrate how to use the big.LITTLE cores and most of the memory we first have a look at the configuration<br />
with effectstocause miner.<br />
<br />
=== The Goal ===<br />
<br />
Verium mining is a lot about RAM, so you want to maximize the memory usage. <br />
How does that work?<br />
The [[https://github.com/effectsToCause/veriumMiner|effectstocause veriumMiner]] can be configured to use a different amount of RAM per thread. So the '''idea''' is to use 2 different miner compilations and make use of the 2GB LPDDR3 RAM @ 933Mhz the Odroid has.<br />
<br />
Plus: do that wisely to also benefit from the big.LITTLE cores of the <br />
Samsung Exynos5422 Cortex™ ARM Cortex-A15 (2.0Ghz) / Cortex-A7 (1.4 Ghz) Octa core CPUs<br />
<br />
=== Technical details ===<br />
<br />
The miner settings are called '''1 way''' or '''3 way''' (or [[Nway]]) where<br />
1 way => 128 MB per mining thread <br />
3 way => 384 MB per mining thread <br />
The #way of the miner is configured in<br />
nano veriumMiner/algo/scrypt.c<br />
<br />
Now you can calculate around for yourself or just trust me that you want those two miner configurations and then run<br />
5 threads @ 1 way = 640 MB <br />
3 threads @ 3 way = 1152 MB <br />
1792 MB total RAM<br />
The system needs some memory, too and with this setting there is only around 60 MB left free - but only if you use the image linked above ( I have tested 6 different ones, only this works with -t 5 & -t 3 ).<br />
<br />
A 2 way compilation might be interesting as well, but my compilation try didn't work (only boooo's).<br />
<br />
=== Easy Installation ===<br />
<br />
I have prepared two scripts on my [[https://github.com/DJoeDt/verium git repository]] (no warranty whatsoever)<br />
* [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh 1wayARM_XU4_VeriumMiner_install.sh]<br />
* [https://github.com/DJoeDt/verium/raw/master/3wayARM_XU4_VeriumMiner_install.sh 3wayARM_XU4_VeriumMiner_install.sh]<br />
which install the miners into <br />
~/verium/1wayminer/<br />
~/verium/3wayminer/<br />
<br />
=== How to run them ===<br />
<br />
Having both compilations at hand we need to manage them properly. Besides the threads there are two things to configure<br />
# the big.little core<br />
# the API Port<br />
<br />
==== big cores -t 3 ====<br />
Thy '''big''' cores shall run the 3 way miner on the standard port 4048 with high priority<br />
--cpu-priority 4<br />
--cpu-affinity 0x00F0 <br />
-b 4048<br />
--api-bind 0.0.0.0:4048<br />
those are the options to be set. About using [[cpu-affinity]].<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 3way -t 3 big<br />
/root/verium/3wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 4 -t 3 --cpu-affinity 0x00FF --api-bind 0.0.0.0:4048 &<br />
Just copy it and give it a try as donation ;) .<br />
<br />
==== little cores -t 5 ====<br />
The ''little'' core shall run the 1 way miner on API Port 4049 with lower priority<br />
--cpu-priority 1<br />
-b 4049<br />
--api-bind 0.0.0.0:4049<br />
where I just don't touch --cpu-affinity and thus the remaining 4 little + 1 big cores are used.<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 1way -t 5 little<br />
/root/verium/1wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 1 -t 5 -b 4049 --api-bind 0.0.0.0:4049 &<br />
<br />
=== Monitoring ===<br />
<br />
If you use the API you need to configure both ports. My workaround with birtys <3 webscripts looks like this:<br />
<br />
So far I have copied index_monitor.php to index_monitor4049.php, reconfigured<br />
defined('API_PORT') || define('API_PORT', 4049);<br />
in it, and just included it by adding<br />
<?php include 'index_monitor4049.php';?><br />
to the index.php.<br />
<br />
More information on monitoring can be found [https://wiki.vericoin.info/index.php?title=Verium_Mining#Maintenance_.26_Monitoring here].<br />
<br />
=== The Result ===<br />
<br />
Some remarks before we look at H/m:<br />
# again: only the image linked above worked for me, but not even by default<br />
# you still have to create a swap file (included in my scripts)<br />
# I lied about the lines in my rc.local, I actually mine on two different pools. Decentralize it! ;)<br />
<br />
==== Hashrate Numbers!!11 ====<br />
<br />
Originally I ran birtys miner configuration which actually is the 1 way configuration. Without any -t option it just starts 8 threads and with '''pool mining''' i got an average of<br />
395 H/m = 1 way -t 8<br />
<br />
The two miners put out like<br />
195 H/m = 1 way -t 5<br />
250 H/m = 3 way -t 3<br />
<br />
Happy adding! :)<br />
<br />
I wonder how this performs when '''solo mining?'''<br />
<br />
=== Update to fireworm miner & hugepages ===<br />
<br />
1way : 128MB -> nr_hugepages = 65.<br />
3way : 384MB -> nr_hugepages = 193.<br />
6way : 768MB -> nr_hugepages = 386.<br />
<br />
==== Configuration of birtys image ====<br />
Setup: birtys hugepages minimal image: [[https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk|google drive]]<br />
<br />
Configure hugepages<br />
sudo nano /etc/sysctl.conf<br />
to<br />
vm.nr_hugepages=839<br />
<br />
Change host <br />
nano /etc/hostname<br />
nano /etc/hosts<br />
and '''dram_freq=933''' in<br />
nano /media/boot/boot.ini<br />
as well as the password by<br />
passwd<br />
<br />
Reboot before going on<br />
reboot<br />
<br />
==== Fireworm Miner Installation ====<br />
Remove old miner from birtys image:<br />
rm -rf veriumMiner<br />
<br />
Install newest miner by script:<br />
wget https://github.com/DJoeDt/verium/raw/master/nwayARM_HC1_fireworm_install.sh<br />
chmod +x nwayARM_HC1_fireworm_install.sh<br />
./nwayARM_HC1_fireworm_install.sh<br />
<br />
==== Miner Autostart Configuration ====<br />
Autostart config<br />
nano /etc/rc.local<br />
<br />
<nowiki><br />
# Verium Miner Configuration<br />
# big cores<br />
nice --10 /root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://vrm.n3rd3d.com:3332 -u joe_rondx.1 -p joe \<br />
-t 3 -1 1 --cpu-affinity 0x00F0 --cpu-priority 2 \<br />
--api-bind 0.0.0.0:4048 --no-color >> /root/verium/nwayminer/3waymine.log &<br />
<br />
sleep 5 # delay for hugepages allocation<br />
<br />
# little cores<br />
/root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://eu.vrm.mining-pool.ovh:3032 -u joe_rondx.HC1_1 -p joe \<br />
-1 4 --cpu-affinity-stride 1 --cpu-affinity-oneway-index 0 --cpu-priority 0 \<br />
--api-bind 0.0.0.0:4049 -b 4049 --no-color >> /root/verium/nwayminer/1waymine.log <br />
</nowiki><br />
<br />
Run the 3way miner '''first''' !!<br />
-t 3 -1<br />
First because it should make maximal use of hugepages.<br />
<br />
Secondly run only 1way<br />
-1 4 <br />
where 1 thread runs without hugepages.<br />
<br />
==== Hashrate ====<br />
<br />
=> 400 + 137 = 537 H/m @ 1.9 GHz<br />
<br />
== Power to the Rig ==<br />
<br />
The specs say 4 Amps @ 5V for an Odroid. But there is way more to consider if you want to power your rig.<br />
<br />
=== Amp calculations ===<br />
<br />
=== PSU choice ===<br />
<br />
=== Cables ===<br />
<br />
=== Fuses ===<br />
<br />
== Links ==<br />
<br />
* https://ameridroid.com/products?keywords=aluminum<br />
* https://forum.odroid.com/viewtopic.php?f=93&t=27239<br />
* http://www.thinkwiki.org/wiki/How_to_use_cpufrequtils<br />
* https://wiki.odroid.com/odroid-xu4/os_images/linux/ubuntu_4.14/ubuntu_4.14<br />
* https://forum.odroid.com/viewtopic.php?f=146&t=28895&sid=873dc51d2cf97257c807b99826f91525</div>Benzinihttps://wiki.vericoin.info/index.php?title=Odroid&diff=1274Odroid2018-03-04T13:59:46Z<p>Benzini: /* Monitoring */</p>
<hr />
<div>Odroid XU4’s are popular. SBC systems in general are designed to be very power efficient, because of this they are pretty good at Verium mining. The downside is you need a lot of them to amass a sizeable amount of hashes. The up-front cost of SBC’s can be very high, but their power usage is very low. Remember to take into account all the required extras to make SBC’s function. (SD cards, power cables/supplies, network cables, switches, cooling, mounting mechanism, etc…) For SBCs the mining software usually needs to be compiled for 1way using 128 MB per thread. Many devices have been tested in terms of their hashrate and it can fairly be stated that the Odroid platform with its Octa core CPUs (Exynos5422 big.LITTLE) and 2 GB LPDDR3 RAM outperforms any other device. By now Odroid has even released a special version of the original XU4 which is called Odroid HC1 and is designed for clustering. It should be noted that despite their relative low total hasrate the ration hashrate per energy is still good. Also, there is software out in the community that helps on the maintenance of large clusters. For more information visit the [http://www.hardkernel.com official Odroid Website].<br />
<br />
== Optimized OS Image for Verium Mining ==<br />
[[File:Odroid_startup.png|thumb]]<br />
The ODROID Verium Mining Image (by joe_rondx) includes an optimized OS with preinstalled miner and several other handy features. It is made for the XU4 line, that is Odroid XU4, XU4Q, HC1, HC2, MC1. <br />
<br />
Performance features:<br />
* hugepages are enabled (thanks to birty & fireworm)<br />
* Maximal RAM clocking: 933 MHz<br />
* CPU downclocking of big cores: 1.9 GHz (read [[#Downclocking_.28yes.2C_down.21.29_the_CPU|here]] why 2 GHz is not worth it)<br />
* Optimal two miners configuration for big.LITTLE cores.<br />
Helper scripts:<br />
* Temperature logging in verium/cpu_temp.log<br />
* Status overview script vrmcheck.sh<br />
* Filesystem expansion by resize.sh<br />
<br />
[[File:Odroid_burn.png|thumb]]<br />
=== Setup the Image ===<br />
<br />
# [https://drive.google.com/open?id=1RbXnGUh5fwmfhMQNzefCK75PajyrXjQi Download] the Image. <br />
# Burn it without extracting it (The real issue is the following: the image consists of two partitions, if you extract the gz file you have to make sure you burn both partitions and not only the fat partition.) <br />
# On first bootup give it 5-10 mins time until you should be able to find the device in the network.<br />
# Log in with standard root/odroid<br />
<br />
=== Configuration of the Image ===<br />
<br />
The first thing you want to do is the configuration of the miner. The autostart of the miner is currently done<br />
in the rc.local file. <br />
nano /etc/rc.local <br />
At the end you will find two mining commands which you need to adjust for your pool/solo setup.<br />
<br />
In addition to the miner configuration you might want to change the hostname and password:<br />
nano /etc/hostname<br />
nano /etc/hosts<br />
passwd<br />
You can also expand the filesystem by using the script<br />
./resize.sh<br />
Reboot before going on<br />
reboot<br />
and run the resize script again<br />
./resize.sh<br />
<br />
==== Network ====<br />
<br />
Usually the Ethernet Port should just connect via DHCP. If you have a Wifi Stick you should use <br />
nmtui<br />
<br />
==== XU4 & XU4Q Tipps ====<br />
<br />
Since the image was created on an HC1 you might want to check the [[#Downclocking_the_GPU|GPU setting]].<br />
<br />
=== Usage and Monitoring ===<br />
<br />
There is a simple status script in the home directory, call<br />
./vrmcheck.sh<br />
which prints out the configuration in rc.local, the last 10 lines of each miner log, CPU frequency and the current temperature.<br />
<br />
Monitoring both miners is a bit of a challenge, but DerrickEs [https://github.com/derricke/MinerMonitor minerMonitor scripts] or casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor] support the configuration of ports (4048 & 4049 in this case). I also recommend mining on two pool to decentralize the hasrate, keep some hashes going if one pool is down and also for monitoring.<br />
<br />
=== Donation suggestion ===<br />
# The image starts mining right away - for joe_rondx (next version will include fireworm). This is not meant to be a rip off. Consider to have a freshly burned card mine for us perhaps one hour as initial donation.<br />
# If you are running less than 10 units (XU4, XU4Q, HC1, MC1/4) the initial donation is all we are asking for.<br />
# If you are running 10-19 units you may consider to have one small miner running on joe_rondx address.<br />
# If you are running 20-29 units you may consider to have one more small miner running on fireworms address.<br />
# If you are running 30-39 units you may consider to switch joes small miner to a big one.<br />
# If you are running 40-49 units you may consider to switch fireworms small miner to a big one.<br />
# If you are running 50+ units please also consider donating to the project via its donation page.<br />
Justification: Individual hasrates may vary, but let's assume you were getting 450 H/m per unit without<br />
this image. The image should give you 537 H/m which is an increase of nearly 20% . 10 units should produce<br />
5370 H/m while one small miner does about 137 H/m - which is about 2.5% of the total hashrate.<br />
<br />
== Other OS Images ==<br />
<br />
Let's start with special images by Odroid God birty: [https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk Odroid Miner images]<br />
In particular the newest image with enabled hugepages in combination with fireworms miner gives a significant boost of hashrate. It was used for the optimized image.<br />
<br />
Odroids [https://wiki.odroid.com/odroid-xu4/os_images/linux/start Official Images] are of course very well made. <br />
The newest Ubuntu Mate 16.04.3 (20171212) which was release after birtys image even has hugepages enabled. <br />
But unfortunately it uses too much RAM. Even more unfortunate is, that the Ubuntu 16.04.3 (20171213) (MINIMAL, BARE OS)<br />
image doesn't have hugepages enabled.<br />
<br />
I have once tested like 6 different images that are available for the XU4 platform.<br />
<br />
For the beginning I recommend the [http://dietpi.com/#download DietPi image] because its included diet-config tool already supports lots of the configurations you want to set. [http://dietpi.com/downloads/images/DietPi_OdroidXU4-armv7-(Jessie).7z Direct Link to image]<br />
<br />
The performance of [https://dl.armbian.com/odroidxu4/Ubuntu_xenial_default.7z Armbians headless 3.x kernel] was very good before the hugepages option was available.<br />
<br />
== Tweaking the OS for Mining ==<br />
<br />
The whole thing as a script (ARM Miner + XU4 Setup): [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh Download Shell script]<br />
wget https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh<br />
chmod +x 1wayARM_XU4_VeriumMiner_install.sh<br />
./1wayARM_XU4_VeriumMiner_install.sh<br />
<br />
=== Downclocking (yes, down!) the CPU ===<br />
<br />
To prevent throttleing due to heat it may actually increase your hashrate if the CPU doesn't run at 2 GHz (max). Even if you can prevent throttleing at 2GHz it is anyhow not worth it: you might get 10-15 H/m more but it costs about 2 Watts (out of 12) to get this last increase - so it won't pay back, for Details: [https://www.planet3dnow.de/vbulletin/threads/428622-Odroid-HC1 HC1 power benchmark].<br />
<br />
Install the utility (or use DietPi config)<br />
sudo apt-get install cpufrequtils<br />
use it directly <br />
sudo cpufreq-set -c 7 -u 1.9GHz -r<br />
and make the change permanent by creating a config file<br />
sudo nano /etc/default/cpufrequtils <br />
with the following settings<br />
ENABLE="true"<br />
GOVERNOR="performance"<br />
MAX_SPEED=1900000<br />
MIN_SPEED=1900000<br />
Now the CPU should always run at constant speed. This also saves a reasonable amount of power.<br />
<br />
=== Overclocking the RAM ===<br />
<br />
On the boot-FAT-Partition edit the boot.ini<br />
sudo nano boot.ini<br />
Find<br />
ddr_freq<br />
and change the value to 933<br />
# DRAM Frequency<br />
# Sets the LPDDR3 memory frequency<br />
# Supported values: 933 825 728 633 (MHZ)<br />
setenv ddr_freq 933<br />
<br />
Make sure before bootz to<br />
# set DDR frequency<br />
dmc ${ddr_freq} <br />
<br />
=== Downclocking the GPU ===<br />
<br />
Install this utility<br />
sudo apt-get install sysfsutils<br />
<br />
Then edit <br />
sudo nano /etc/sysfs.conf<br />
<br />
and insert the following line<br />
# Put GPU into powersave mode (= Downclocking it)<br />
devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor = powersave<br />
<br />
then start the service<br />
sudo service sysfsutils start<br />
<br />
Effect: reduced the power consumption by 0.7 – 0.8W, SOC will be 1-3°C cooler <br />
<br />
[https://obihoernchen.net/1340/lower-gpu-clock-of-odroid-xu4-for-headless-servers/ GPU for headless]<br />
<br />
Another way might be<br />
sudo nano /etc/rc.local<br />
and add this line before exit 0<br />
echo powersave > /sys/devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor<br />
<br />
=== Setting up a Swapfile ===<br />
<br />
Verium is memory intensive, so we increase the swap file (or use DietPi config)<br />
sudo fallocate -l 1G /var/swapfile<br />
sudo chmod 600 /var/swapfile<br />
sudo mkswap /var/swapfile<br />
sudo swapon /var/swapfile<br />
check it with <br />
free -h<br />
and configure that permanently<br />
sudo echo "/var/swapfile none swap sw 0 0" >> /etc/fstab<br />
<br />
=== Processes ===<br />
<br />
Further optimization can be done by checking the process tree<br />
pstree -p<br />
and disable/deinstall stuff that isn't needed. KILL 'EM ALL!<br />
<br />
I did not find it yet but if you come across ads7846 remove it.<br />
modprobe -r ads7846<br />
tee /etc/modprobe.d/blacklist-ads7846.conf <<< "ads7846"<br />
<br />
=== XU4 hardware ===<br />
<br />
The key is to exchange the thermal tape of the heatsink with some good thermal paste, decreases the temperature by 10 degrees (C) using same testing conditions. Also get the under side cooled as well.<br />
<br />
To save electricity you may turn down the power supplies voltage with a screw driver.<br />
<br />
Check sd card slot heat.<br />
<br />
== Optimal big.LITTLE and Maximal RAM Usage ==<br />
<br />
aka "Getting the last Hash out of your Odroid".<br />
<br />
The first step is to use an OS image that uses a minimum amount of RAM for the system.<br />
<br />
To illustrate how to use the big.LITTLE cores and most of the memory we first have a look at the configuration<br />
with effectstocause miner.<br />
<br />
=== The Goal ===<br />
<br />
Verium mining is a lot about RAM, so you want to maximize the memory usage. <br />
How does that work?<br />
The [[https://github.com/effectsToCause/veriumMiner|effectstocause veriumMiner]] can be configured to use a different amount of RAM per thread. So the '''idea''' is to use 2 different miner compilations and make use of the 2GB LPDDR3 RAM @ 933Mhz the Odroid has.<br />
<br />
Plus: do that wisely to also benefit from the big.LITTLE cores of the <br />
Samsung Exynos5422 Cortex™ ARM Cortex-A15 (2.0Ghz) / Cortex-A7 (1.4 Ghz) Octa core CPUs<br />
<br />
=== Technical details ===<br />
<br />
The miner settings are called '''1 way''' or '''3 way''' (or [[Nway]]) where<br />
1 way => 128 MB per mining thread <br />
3 way => 384 MB per mining thread <br />
The #way of the miner is configured in<br />
nano veriumMiner/algo/scrypt.c<br />
<br />
Now you can calculate around for yourself or just trust me that you want those two miner configurations and then run<br />
5 threads @ 1 way = 640 MB <br />
3 threads @ 3 way = 1152 MB <br />
1792 MB total RAM<br />
The system needs some memory, too and with this setting there is only around 60 MB left free - but only if you use the image linked above ( I have tested 6 different ones, only this works with -t 5 & -t 3 ).<br />
<br />
A 2 way compilation might be interesting as well, but my compilation try didn't work (only boooo's).<br />
<br />
=== Easy Installation ===<br />
<br />
I have prepared two scripts on my [[https://github.com/DJoeDt/verium git repository]] (no warranty whatsoever)<br />
* [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh 1wayARM_XU4_VeriumMiner_install.sh]<br />
* [https://github.com/DJoeDt/verium/raw/master/3wayARM_XU4_VeriumMiner_install.sh 3wayARM_XU4_VeriumMiner_install.sh]<br />
which install the miners into <br />
~/verium/1wayminer/<br />
~/verium/3wayminer/<br />
<br />
=== How to run them ===<br />
<br />
Having both compilations at hand we need to manage them properly. Besides the threads there are two things to configure<br />
# the big.little core<br />
# the API Port<br />
<br />
==== big cores -t 3 ====<br />
Thy '''big''' cores shall run the 3 way miner on the standard port 4048 with high priority<br />
--cpu-priority 4<br />
--cpu-affinity 0x00F0 <br />
-b 4048<br />
--api-bind 0.0.0.0:4048<br />
those are the options to be set. About using [[cpu-affinity]].<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 3way -t 3 big<br />
/root/verium/3wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 4 -t 3 --cpu-affinity 0x00FF --api-bind 0.0.0.0:4048 &<br />
Just copy it and give it a try as donation ;) .<br />
<br />
==== little cores -t 5 ====<br />
The ''little'' core shall run the 1 way miner on API Port 4049 with lower priority<br />
--cpu-priority 1<br />
-b 4049<br />
--api-bind 0.0.0.0:4049<br />
where I just don't touch --cpu-affinity and thus the remaining 4 little + 1 big cores are used.<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 1way -t 5 little<br />
/root/verium/1wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 1 -t 5 -b 4049 --api-bind 0.0.0.0:4049 &<br />
<br />
=== Monitoring ===<br />
<br />
If you use the API you need to configure both ports. My workaround with birtys <3 webscripts looks like this:<br />
<br />
So far I have copied index_monitor.php to index_monitor4049.php, reconfigured<br />
defined('API_PORT') || define('API_PORT', 4049);<br />
in it, and just included it by adding<br />
<?php include 'index_monitor4049.php';?><br />
to the index.php.<br />
<br />
More information on monitoring can be found [https://wiki.vericoin.info/index.php?title=Verium_Mining#Web-based_Monitoring here] and [https://wiki.vericoin.info/index.php?title=Verium_Mining#CLI_Monitoring here].<br />
<br />
=== The Result ===<br />
<br />
Some remarks before we look at H/m:<br />
# again: only the image linked above worked for me, but not even by default<br />
# you still have to create a swap file (included in my scripts)<br />
# I lied about the lines in my rc.local, I actually mine on two different pools. Decentralize it! ;)<br />
<br />
==== Hashrate Numbers!!11 ====<br />
<br />
Originally I ran birtys miner configuration which actually is the 1 way configuration. Without any -t option it just starts 8 threads and with '''pool mining''' i got an average of<br />
395 H/m = 1 way -t 8<br />
<br />
The two miners put out like<br />
195 H/m = 1 way -t 5<br />
250 H/m = 3 way -t 3<br />
<br />
Happy adding! :)<br />
<br />
I wonder how this performs when '''solo mining?'''<br />
<br />
=== Update to fireworm miner & hugepages ===<br />
<br />
1way : 128MB -> nr_hugepages = 65.<br />
3way : 384MB -> nr_hugepages = 193.<br />
6way : 768MB -> nr_hugepages = 386.<br />
<br />
==== Configuration of birtys image ====<br />
Setup: birtys hugepages minimal image: [[https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk|google drive]]<br />
<br />
Configure hugepages<br />
sudo nano /etc/sysctl.conf<br />
to<br />
vm.nr_hugepages=839<br />
<br />
Change host <br />
nano /etc/hostname<br />
nano /etc/hosts<br />
and '''dram_freq=933''' in<br />
nano /media/boot/boot.ini<br />
as well as the password by<br />
passwd<br />
<br />
Reboot before going on<br />
reboot<br />
<br />
==== Fireworm Miner Installation ====<br />
Remove old miner from birtys image:<br />
rm -rf veriumMiner<br />
<br />
Install newest miner by script:<br />
wget https://github.com/DJoeDt/verium/raw/master/nwayARM_HC1_fireworm_install.sh<br />
chmod +x nwayARM_HC1_fireworm_install.sh<br />
./nwayARM_HC1_fireworm_install.sh<br />
<br />
==== Miner Autostart Configuration ====<br />
Autostart config<br />
nano /etc/rc.local<br />
<br />
<nowiki><br />
# Verium Miner Configuration<br />
# big cores<br />
nice --10 /root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://vrm.n3rd3d.com:3332 -u joe_rondx.1 -p joe \<br />
-t 3 -1 1 --cpu-affinity 0x00F0 --cpu-priority 2 \<br />
--api-bind 0.0.0.0:4048 --no-color >> /root/verium/nwayminer/3waymine.log &<br />
<br />
sleep 5 # delay for hugepages allocation<br />
<br />
# little cores<br />
/root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://eu.vrm.mining-pool.ovh:3032 -u joe_rondx.HC1_1 -p joe \<br />
-1 4 --cpu-affinity-stride 1 --cpu-affinity-oneway-index 0 --cpu-priority 0 \<br />
--api-bind 0.0.0.0:4049 -b 4049 --no-color >> /root/verium/nwayminer/1waymine.log <br />
</nowiki><br />
<br />
Run the 3way miner '''first''' !!<br />
-t 3 -1<br />
First because it should make maximal use of hugepages.<br />
<br />
Secondly run only 1way<br />
-1 4 <br />
where 1 thread runs without hugepages.<br />
<br />
==== Hashrate ====<br />
<br />
=> 400 + 137 = 537 H/m @ 1.9 GHz<br />
<br />
== Power to the Rig ==<br />
<br />
The specs say 4 Amps @ 5V for an Odroid. But there is way more to consider if you want to power your rig.<br />
<br />
=== Amp calculations ===<br />
<br />
=== PSU choice ===<br />
<br />
=== Cables ===<br />
<br />
=== Fuses ===</div>Benzinihttps://wiki.vericoin.info/index.php?title=Odroid&diff=1272Odroid2018-03-03T20:41:37Z<p>Benzini: /* Usage and Monitoring */</p>
<hr />
<div>Odroid XU4’s are popular. SBC systems in general are designed to be very power efficient, because of this they are pretty good at Verium mining. The downside is you need a lot of them to amass a sizeable amount of hashes. The up-front cost of SBC’s can be very high, but their power usage is very low. Remember to take into account all the required extras to make SBC’s function. (SD cards, power cables/supplies, network cables, switches, cooling, mounting mechanism, etc…) For SBCs the mining software usually needs to be compiled for 1way using 128 MB per thread. Many devices have been tested in terms of their hashrate and it can fairly be stated that the Odroid platform with its Octa core CPUs (Exynos5422 big.LITTLE) and 2 GB LPDDR3 RAM outperforms any other device. By now Odroid has even released a special version of the original XU4 which is called Odroid HC1 and is designed for clustering. It should be noted that despite their relative low total hasrate the ration hashrate per energy is still good. Also, there is software out in the community that helps on the maintenance of large clusters. For more information visit the [http://www.hardkernel.com official Odroid Website].<br />
<br />
== Optimized OS Image for Verium Mining ==<br />
[[File:Odroid_startup.png|thumb]]<br />
The ODROID Verium Mining Image (by joe_rondx) includes an optimized OS with preinstalled miner and several other handy features. It is made for the XU4 line, that is Odroid XU4, XU4Q, HC1, HC2, MC1. <br />
<br />
Performance features:<br />
* hugepages are enabled (thanks to birty & fireworm)<br />
* Maximal RAM clocking: 933 MHz<br />
* CPU downclocking of big cores: 1.9 GHz (read [[#Downclocking_.28yes.2C_down.21.29_the_CPU|here]] why 2 GHz is not worth it)<br />
* Optimal two miners configuration for big.LITTLE cores.<br />
Helper scripts:<br />
* Temperature logging in verium/cpu_temp.log<br />
* Status overview script vrmcheck.sh<br />
* Filesystem expansion by resize.sh<br />
<br />
[[File:Odroid_burn.png|thumb]]<br />
=== Setup the Image ===<br />
<br />
# [https://drive.google.com/open?id=1RbXnGUh5fwmfhMQNzefCK75PajyrXjQi Download] the Image. <br />
# Burn it without extracting it (The real issue is the following: the image consists of two partitions, if you extract the gz file you have to make sure you burn both partitions and not only the fat partition.) <br />
# On first bootup give it 5-10 mins time until you should be able to find the device in the network.<br />
# Log in with standard root/odroid<br />
<br />
=== Configuration of the Image ===<br />
<br />
The first thing you want to do is the configuration of the miner. The autostart of the miner is currently done<br />
in the rc.local file. <br />
nano /etc/rc.local <br />
At the end you will find two mining commands which you need to adjust for your pool/solo setup.<br />
<br />
In addition to the miner configuration you might want to change the hostname and password:<br />
nano /etc/hostname<br />
nano /etc/hosts<br />
passwd<br />
You can also expand the filesystem by using the script<br />
./resize.sh<br />
Reboot before going on<br />
reboot<br />
and run the resize script again<br />
./resize.sh<br />
<br />
==== Network ====<br />
<br />
Usually the Ethernet Port should just connect via DHCP. If you have a Wifi Stick you should use <br />
nmtui<br />
<br />
==== XU4 & XU4Q Tipps ====<br />
<br />
Since the image was created on an HC1 you might want to check the [[#Downclocking_the_GPU|GPU setting]].<br />
<br />
=== Usage and Monitoring ===<br />
<br />
There is a simple status script in the home directory, call<br />
./vrmcheck.sh<br />
which prints out the configuration in rc.local, the last 10 lines of each miner log, CPU frequency and the current temperature.<br />
<br />
Monitoring both miners is a bit of a challenge, but DerrickEs [https://github.com/derricke/MinerMonitor minerMonitor scripts] or casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor] support the configuration of ports (4048 & 4049 in this case). I also recommend mining on two pool to decentralize the hasrate, keep some hashes going if one pool is down and also for monitoring.<br />
<br />
=== Donation suggestion ===<br />
# The image starts mining right away - for joe_rondx (next version will include fireworm). This is not meant to be a rip off. Consider to have a freshly burned card mine for us perhaps one hour as initial donation.<br />
# If you are running less than 10 units (XU4, XU4Q, HC1, MC1/4) the initial donation is all we are asking for.<br />
# If you are running 10-19 units you may consider to have one small miner running on joe_rondx address.<br />
# If you are running 20-29 units you may consider to have one more small miner running on fireworms address.<br />
# If you are running 30-39 units you may consider to switch joes small miner to a big one.<br />
# If you are running 40-49 units you may consider to switch fireworms small miner to a big one.<br />
# If you are running 50+ units please also consider donating to the project via its donation page.<br />
Justification: Individual hasrates may vary, but let's assume you were getting 450 H/m per unit without<br />
this image. The image should give you 537 H/m which is an increase of nearly 20% . 10 units should produce<br />
5370 H/m while one small miner does about 137 H/m - which is about 2.5% of the total hashrate.<br />
<br />
== Other OS Images ==<br />
<br />
Let's start with special images by Odroid God birty: [https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk Odroid Miner images]<br />
In particular the newest image with enabled hugepages in combination with fireworms miner gives a significant boost of hashrate. It was used for the optimized image.<br />
<br />
Odroids [https://wiki.odroid.com/odroid-xu4/os_images/linux/start Official Images] are of course very well made. <br />
The newest Ubuntu Mate 16.04.3 (20171212) which was release after birtys image even has hugepages enabled. <br />
But unfortunately it uses too much RAM. Even more unfortunate is, that the Ubuntu 16.04.3 (20171213) (MINIMAL, BARE OS)<br />
image doesn't have hugepages enabled.<br />
<br />
I have once tested like 6 different images that are available for the XU4 platform.<br />
<br />
For the beginning I recommend the [http://dietpi.com/#download DietPi image] because its included diet-config tool already supports lots of the configurations you want to set. [http://dietpi.com/downloads/images/DietPi_OdroidXU4-armv7-(Jessie).7z Direct Link to image]<br />
<br />
The performance of [https://dl.armbian.com/odroidxu4/Ubuntu_xenial_default.7z Armbians headless 3.x kernel] was very good before the hugepages option was available.<br />
<br />
== Tweaking the OS for Mining ==<br />
<br />
The whole thing as a script (ARM Miner + XU4 Setup): [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh Download Shell script]<br />
wget https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh<br />
chmod +x 1wayARM_XU4_VeriumMiner_install.sh<br />
./1wayARM_XU4_VeriumMiner_install.sh<br />
<br />
=== Downclocking (yes, down!) the CPU ===<br />
<br />
To prevent throttleing due to heat it may actually increase your hashrate if the CPU doesn't run at 2 GHz (max). Even if you can prevent throttleing at 2GHz it is anyhow not worth it: you might get 10-15 H/m more but it costs about 2 Watts (out of 12) to get this last increase - so it won't pay back, for Details: [https://www.planet3dnow.de/vbulletin/threads/428622-Odroid-HC1 HC1 power benchmark].<br />
<br />
Install the utility (or use DietPi config)<br />
sudo apt-get install cpufrequtils<br />
use it directly <br />
sudo cpufreq-set -c 7 -u 1.9GHz -r<br />
and make the change permanent by creating a config file<br />
sudo nano /etc/default/cpufrequtils <br />
with the following settings<br />
ENABLE="true"<br />
GOVERNOR="performance"<br />
MAX_SPEED=1900000<br />
MIN_SPEED=1900000<br />
Now the CPU should always run at constant speed. This also saves a reasonable amount of power.<br />
<br />
=== Overclocking the RAM ===<br />
<br />
On the boot-FAT-Partition edit the boot.ini<br />
sudo nano boot.ini<br />
Find<br />
ddr_freq<br />
and change the value to 933<br />
# DRAM Frequency<br />
# Sets the LPDDR3 memory frequency<br />
# Supported values: 933 825 728 633 (MHZ)<br />
setenv ddr_freq 933<br />
<br />
Make sure before bootz to<br />
# set DDR frequency<br />
dmc ${ddr_freq} <br />
<br />
=== Downclocking the GPU ===<br />
<br />
Install this utility<br />
sudo apt-get install sysfsutils<br />
<br />
Then edit <br />
sudo nano /etc/sysfs.conf<br />
<br />
and insert the following line<br />
# Put GPU into powersave mode (= Downclocking it)<br />
devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor = powersave<br />
<br />
then start the service<br />
sudo service sysfsutils start<br />
<br />
Effect: reduced the power consumption by 0.7 – 0.8W, SOC will be 1-3°C cooler <br />
<br />
[https://obihoernchen.net/1340/lower-gpu-clock-of-odroid-xu4-for-headless-servers/ GPU for headless]<br />
<br />
Another way might be<br />
sudo nano /etc/rc.local<br />
and add this line before exit 0<br />
echo powersave > /sys/devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor<br />
<br />
=== Setting up a Swapfile ===<br />
<br />
Verium is memory intensive, so we increase the swap file (or use DietPi config)<br />
sudo fallocate -l 1G /var/swapfile<br />
sudo chmod 600 /var/swapfile<br />
sudo mkswap /var/swapfile<br />
sudo swapon /var/swapfile<br />
check it with <br />
free -h<br />
and configure that permanently<br />
sudo echo "/var/swapfile none swap sw 0 0" >> /etc/fstab<br />
<br />
=== Processes ===<br />
<br />
Further optimization can be done by checking the process tree<br />
pstree -p<br />
and disable/deinstall stuff that isn't needed. KILL 'EM ALL!<br />
<br />
I did not find it yet but if you come across ads7846 remove it.<br />
modprobe -r ads7846<br />
tee /etc/modprobe.d/blacklist-ads7846.conf <<< "ads7846"<br />
<br />
=== XU4 hardware ===<br />
<br />
The key is to exchange the thermal tape of the heatsink with some good thermal paste, decreases the temperature by 10 degrees (C) using same testing conditions. Also get the under side cooled as well.<br />
<br />
To save electricity you may turn down the power supplies voltage with a screw driver.<br />
<br />
Check sd card slot heat.<br />
<br />
== Optimal big.LITTLE and Maximal RAM Usage ==<br />
<br />
aka "Getting the last Hash out of your Odroid".<br />
<br />
The first step is to use an OS image that uses a minimum amount of RAM for the system.<br />
<br />
To illustrate how to use the big.LITTLE cores and most of the memory we first have a look at the configuration<br />
with effectstocause miner.<br />
<br />
=== The Goal ===<br />
<br />
Verium mining is a lot about RAM, so you want to maximize the memory usage. <br />
How does that work?<br />
The [[https://github.com/effectsToCause/veriumMiner|effectstocause veriumMiner]] can be configured to use a different amount of RAM per thread. So the '''idea''' is to use 2 different miner compilations and make use of the 2GB LPDDR3 RAM @ 933Mhz the Odroid has.<br />
<br />
Plus: do that wisely to also benefit from the big.LITTLE cores of the <br />
Samsung Exynos5422 Cortex™ ARM Cortex-A15 (2.0Ghz) / Cortex-A7 (1.4 Ghz) Octa core CPUs<br />
<br />
=== Technical details ===<br />
<br />
The miner settings are called '''1 way''' or '''3 way''' (or [[Nway]]) where<br />
1 way => 128 MB per mining thread <br />
3 way => 384 MB per mining thread <br />
The #way of the miner is configured in<br />
nano veriumMiner/algo/scrypt.c<br />
<br />
Now you can calculate around for yourself or just trust me that you want those two miner configurations and then run<br />
5 threads @ 1 way = 640 MB <br />
3 threads @ 3 way = 1152 MB <br />
1792 MB total RAM<br />
The system needs some memory, too and with this setting there is only around 60 MB left free - but only if you use the image linked above ( I have tested 6 different ones, only this works with -t 5 & -t 3 ).<br />
<br />
A 2 way compilation might be interesting as well, but my compilation try didn't work (only boooo's).<br />
<br />
=== Easy Installation ===<br />
<br />
I have prepared two scripts on my [[https://github.com/DJoeDt/verium git repository]] (no warranty whatsoever)<br />
* [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh 1wayARM_XU4_VeriumMiner_install.sh]<br />
* [https://github.com/DJoeDt/verium/raw/master/3wayARM_XU4_VeriumMiner_install.sh 3wayARM_XU4_VeriumMiner_install.sh]<br />
which install the miners into <br />
~/verium/1wayminer/<br />
~/verium/3wayminer/<br />
<br />
=== How to run them ===<br />
<br />
Having both compilations at hand we need to manage them properly. Besides the threads there are two things to configure<br />
# the big.little core<br />
# the API Port<br />
<br />
==== big cores -t 3 ====<br />
Thy '''big''' cores shall run the 3 way miner on the standard port 4048 with high priority<br />
--cpu-priority 4<br />
--cpu-affinity 0x00F0 <br />
-b 4048<br />
--api-bind 0.0.0.0:4048<br />
those are the options to be set. About using [[cpu-affinity]].<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 3way -t 3 big<br />
/root/verium/3wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 4 -t 3 --cpu-affinity 0x00FF --api-bind 0.0.0.0:4048 &<br />
Just copy it and give it a try as donation ;) .<br />
<br />
==== little cores -t 5 ====<br />
The ''little'' core shall run the 1 way miner on API Port 4049 with lower priority<br />
--cpu-priority 1<br />
-b 4049<br />
--api-bind 0.0.0.0:4049<br />
where I just don't touch --cpu-affinity and thus the remaining 4 little + 1 big cores are used.<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 1way -t 5 little<br />
/root/verium/1wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 1 -t 5 -b 4049 --api-bind 0.0.0.0:4049 &<br />
<br />
=== Monitoring ===<br />
<br />
If you use the API you need to configure both ports. My workaround with birtys <3 webscripts looks like this:<br />
<br />
So far I have copied index_monitor.php to index_monitor4049.php, reconfigured<br />
defined('API_PORT') || define('API_PORT', 4049);<br />
in it, and just included it by adding<br />
<?php include 'index_monitor4049.php';?><br />
to the index.php.<br />
<br />
=== The Result ===<br />
<br />
Some remarks before we look at H/m:<br />
# again: only the image linked above worked for me, but not even by default<br />
# you still have to create a swap file (included in my scripts)<br />
# I lied about the lines in my rc.local, I actually mine on two different pools. Decentralize it! ;)<br />
<br />
==== Hashrate Numbers!!11 ====<br />
<br />
Originally I ran birtys miner configuration which actually is the 1 way configuration. Without any -t option it just starts 8 threads and with '''pool mining''' i got an average of<br />
395 H/m = 1 way -t 8<br />
<br />
The two miners put out like<br />
195 H/m = 1 way -t 5<br />
250 H/m = 3 way -t 3<br />
<br />
Happy adding! :)<br />
<br />
I wonder how this performs when '''solo mining?'''<br />
<br />
=== Update to fireworm miner & hugepages ===<br />
<br />
1way : 128MB -> nr_hugepages = 65.<br />
3way : 384MB -> nr_hugepages = 193.<br />
6way : 768MB -> nr_hugepages = 386.<br />
<br />
==== Configuration of birtys image ====<br />
Setup: birtys hugepages minimal image: [[https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk|google drive]]<br />
<br />
Configure hugepages<br />
sudo nano /etc/sysctl.conf<br />
to<br />
vm.nr_hugepages=839<br />
<br />
Change host <br />
nano /etc/hostname<br />
nano /etc/hosts<br />
and '''dram_freq=933''' in<br />
nano /media/boot/boot.ini<br />
as well as the password by<br />
passwd<br />
<br />
Reboot before going on<br />
reboot<br />
<br />
==== Fireworm Miner Installation ====<br />
Remove old miner from birtys image:<br />
rm -rf veriumMiner<br />
<br />
Install newest miner by script:<br />
wget https://github.com/DJoeDt/verium/raw/master/nwayARM_HC1_fireworm_install.sh<br />
chmod +x nwayARM_HC1_fireworm_install.sh<br />
./nwayARM_HC1_fireworm_install.sh<br />
<br />
==== Miner Autostart Configuration ====<br />
Autostart config<br />
nano /etc/rc.local<br />
<br />
<nowiki><br />
# Verium Miner Configuration<br />
# big cores<br />
nice --10 /root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://vrm.n3rd3d.com:3332 -u joe_rondx.1 -p joe \<br />
-t 3 -1 1 --cpu-affinity 0x00F0 --cpu-priority 2 \<br />
--api-bind 0.0.0.0:4048 --no-color >> /root/verium/nwayminer/3waymine.log &<br />
<br />
sleep 5 # delay for hugepages allocation<br />
<br />
# little cores<br />
/root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://eu.vrm.mining-pool.ovh:3032 -u joe_rondx.HC1_1 -p joe \<br />
-1 4 --cpu-affinity-stride 1 --cpu-affinity-oneway-index 0 --cpu-priority 0 \<br />
--api-bind 0.0.0.0:4049 -b 4049 --no-color >> /root/verium/nwayminer/1waymine.log <br />
</nowiki><br />
<br />
Run the 3way miner '''first''' !!<br />
-t 3 -1<br />
First because it should make maximal use of hugepages.<br />
<br />
Secondly run only 1way<br />
-1 4 <br />
where 1 thread runs without hugepages.<br />
<br />
==== Hashrate ====<br />
<br />
=> 400 + 137 = 537 H/m @ 1.9 GHz<br />
<br />
== Power to the Rig ==<br />
<br />
The specs say 4 Amps @ 5V for an Odroid. But there is way more to consider if you want to power your rig.<br />
<br />
=== Amp calculations ===<br />
<br />
=== PSU choice ===<br />
<br />
=== Cables ===<br />
<br />
=== Fuses ===</div>Benzinihttps://wiki.vericoin.info/index.php?title=Odroid&diff=1271Odroid2018-03-03T20:40:44Z<p>Benzini: /* Usage and Monitoring */</p>
<hr />
<div>Odroid XU4’s are popular. SBC systems in general are designed to be very power efficient, because of this they are pretty good at Verium mining. The downside is you need a lot of them to amass a sizeable amount of hashes. The up-front cost of SBC’s can be very high, but their power usage is very low. Remember to take into account all the required extras to make SBC’s function. (SD cards, power cables/supplies, network cables, switches, cooling, mounting mechanism, etc…) For SBCs the mining software usually needs to be compiled for 1way using 128 MB per thread. Many devices have been tested in terms of their hashrate and it can fairly be stated that the Odroid platform with its Octa core CPUs (Exynos5422 big.LITTLE) and 2 GB LPDDR3 RAM outperforms any other device. By now Odroid has even released a special version of the original XU4 which is called Odroid HC1 and is designed for clustering. It should be noted that despite their relative low total hasrate the ration hashrate per energy is still good. Also, there is software out in the community that helps on the maintenance of large clusters. For more information visit the [http://www.hardkernel.com official Odroid Website].<br />
<br />
== Optimized OS Image for Verium Mining ==<br />
[[File:Odroid_startup.png|thumb]]<br />
The ODROID Verium Mining Image (by joe_rondx) includes an optimized OS with preinstalled miner and several other handy features. It is made for the XU4 line, that is Odroid XU4, XU4Q, HC1, HC2, MC1. <br />
<br />
Performance features:<br />
* hugepages are enabled (thanks to birty & fireworm)<br />
* Maximal RAM clocking: 933 MHz<br />
* CPU downclocking of big cores: 1.9 GHz (read [[#Downclocking_.28yes.2C_down.21.29_the_CPU|here]] why 2 GHz is not worth it)<br />
* Optimal two miners configuration for big.LITTLE cores.<br />
Helper scripts:<br />
* Temperature logging in verium/cpu_temp.log<br />
* Status overview script vrmcheck.sh<br />
* Filesystem expansion by resize.sh<br />
<br />
[[File:Odroid_burn.png|thumb]]<br />
=== Setup the Image ===<br />
<br />
# [https://drive.google.com/open?id=1RbXnGUh5fwmfhMQNzefCK75PajyrXjQi Download] the Image. <br />
# Burn it without extracting it (The real issue is the following: the image consists of two partitions, if you extract the gz file you have to make sure you burn both partitions and not only the fat partition.) <br />
# On first bootup give it 5-10 mins time until you should be able to find the device in the network.<br />
# Log in with standard root/odroid<br />
<br />
=== Configuration of the Image ===<br />
<br />
The first thing you want to do is the configuration of the miner. The autostart of the miner is currently done<br />
in the rc.local file. <br />
nano /etc/rc.local <br />
At the end you will find two mining commands which you need to adjust for your pool/solo setup.<br />
<br />
In addition to the miner configuration you might want to change the hostname and password:<br />
nano /etc/hostname<br />
nano /etc/hosts<br />
passwd<br />
You can also expand the filesystem by using the script<br />
./resize.sh<br />
Reboot before going on<br />
reboot<br />
and run the resize script again<br />
./resize.sh<br />
<br />
==== Network ====<br />
<br />
Usually the Ethernet Port should just connect via DHCP. If you have a Wifi Stick you should use <br />
nmtui<br />
<br />
==== XU4 & XU4Q Tipps ====<br />
<br />
Since the image was created on an HC1 you might want to check the [[#Downclocking_the_GPU|GPU setting]].<br />
<br />
=== Usage and Monitoring ===<br />
<br />
There is a simple status script in the home directory, call<br />
./vrmcheck.sh<br />
which prints out the configuration in rc.local, the last 10 lines of each miner log, CPU frequency and the current temperature.<br />
<br />
Monitoring both miners is a bit of a challenge, but DerrickEs [https://github.com/derricke/MinerMonitor minerMonitor scripts] or casanova's CLI Monitor [https://github.com/bezeredi/verium-cli-monitor] support the configuration of ports (4048 & 4049 in this case). I also recommend mining on two pool to decentralize the hasrate, keep some hashes going if one pool is down and also for monitoring.<br />
<br />
=== Donation suggestion ===<br />
# The image starts mining right away - for joe_rondx (next version will include fireworm). This is not meant to be a rip off. Consider to have a freshly burned card mine for us perhaps one hour as initial donation.<br />
# If you are running less than 10 units (XU4, XU4Q, HC1, MC1/4) the initial donation is all we are asking for.<br />
# If you are running 10-19 units you may consider to have one small miner running on joe_rondx address.<br />
# If you are running 20-29 units you may consider to have one more small miner running on fireworms address.<br />
# If you are running 30-39 units you may consider to switch joes small miner to a big one.<br />
# If you are running 40-49 units you may consider to switch fireworms small miner to a big one.<br />
# If you are running 50+ units please also consider donating to the project via its donation page.<br />
Justification: Individual hasrates may vary, but let's assume you were getting 450 H/m per unit without<br />
this image. The image should give you 537 H/m which is an increase of nearly 20% . 10 units should produce<br />
5370 H/m while one small miner does about 137 H/m - which is about 2.5% of the total hashrate.<br />
<br />
== Other OS Images ==<br />
<br />
Let's start with special images by Odroid God birty: [https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk Odroid Miner images]<br />
In particular the newest image with enabled hugepages in combination with fireworms miner gives a significant boost of hashrate. It was used for the optimized image.<br />
<br />
Odroids [https://wiki.odroid.com/odroid-xu4/os_images/linux/start Official Images] are of course very well made. <br />
The newest Ubuntu Mate 16.04.3 (20171212) which was release after birtys image even has hugepages enabled. <br />
But unfortunately it uses too much RAM. Even more unfortunate is, that the Ubuntu 16.04.3 (20171213) (MINIMAL, BARE OS)<br />
image doesn't have hugepages enabled.<br />
<br />
I have once tested like 6 different images that are available for the XU4 platform.<br />
<br />
For the beginning I recommend the [http://dietpi.com/#download DietPi image] because its included diet-config tool already supports lots of the configurations you want to set. [http://dietpi.com/downloads/images/DietPi_OdroidXU4-armv7-(Jessie).7z Direct Link to image]<br />
<br />
The performance of [https://dl.armbian.com/odroidxu4/Ubuntu_xenial_default.7z Armbians headless 3.x kernel] was very good before the hugepages option was available.<br />
<br />
== Tweaking the OS for Mining ==<br />
<br />
The whole thing as a script (ARM Miner + XU4 Setup): [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh Download Shell script]<br />
wget https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh<br />
chmod +x 1wayARM_XU4_VeriumMiner_install.sh<br />
./1wayARM_XU4_VeriumMiner_install.sh<br />
<br />
=== Downclocking (yes, down!) the CPU ===<br />
<br />
To prevent throttleing due to heat it may actually increase your hashrate if the CPU doesn't run at 2 GHz (max). Even if you can prevent throttleing at 2GHz it is anyhow not worth it: you might get 10-15 H/m more but it costs about 2 Watts (out of 12) to get this last increase - so it won't pay back, for Details: [https://www.planet3dnow.de/vbulletin/threads/428622-Odroid-HC1 HC1 power benchmark].<br />
<br />
Install the utility (or use DietPi config)<br />
sudo apt-get install cpufrequtils<br />
use it directly <br />
sudo cpufreq-set -c 7 -u 1.9GHz -r<br />
and make the change permanent by creating a config file<br />
sudo nano /etc/default/cpufrequtils <br />
with the following settings<br />
ENABLE="true"<br />
GOVERNOR="performance"<br />
MAX_SPEED=1900000<br />
MIN_SPEED=1900000<br />
Now the CPU should always run at constant speed. This also saves a reasonable amount of power.<br />
<br />
=== Overclocking the RAM ===<br />
<br />
On the boot-FAT-Partition edit the boot.ini<br />
sudo nano boot.ini<br />
Find<br />
ddr_freq<br />
and change the value to 933<br />
# DRAM Frequency<br />
# Sets the LPDDR3 memory frequency<br />
# Supported values: 933 825 728 633 (MHZ)<br />
setenv ddr_freq 933<br />
<br />
Make sure before bootz to<br />
# set DDR frequency<br />
dmc ${ddr_freq} <br />
<br />
=== Downclocking the GPU ===<br />
<br />
Install this utility<br />
sudo apt-get install sysfsutils<br />
<br />
Then edit <br />
sudo nano /etc/sysfs.conf<br />
<br />
and insert the following line<br />
# Put GPU into powersave mode (= Downclocking it)<br />
devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor = powersave<br />
<br />
then start the service<br />
sudo service sysfsutils start<br />
<br />
Effect: reduced the power consumption by 0.7 – 0.8W, SOC will be 1-3°C cooler <br />
<br />
[https://obihoernchen.net/1340/lower-gpu-clock-of-odroid-xu4-for-headless-servers/ GPU for headless]<br />
<br />
Another way might be<br />
sudo nano /etc/rc.local<br />
and add this line before exit 0<br />
echo powersave > /sys/devices/platform/11800000.mali\:/devfreq/11800000.mali\:/governor<br />
<br />
=== Setting up a Swapfile ===<br />
<br />
Verium is memory intensive, so we increase the swap file (or use DietPi config)<br />
sudo fallocate -l 1G /var/swapfile<br />
sudo chmod 600 /var/swapfile<br />
sudo mkswap /var/swapfile<br />
sudo swapon /var/swapfile<br />
check it with <br />
free -h<br />
and configure that permanently<br />
sudo echo "/var/swapfile none swap sw 0 0" >> /etc/fstab<br />
<br />
=== Processes ===<br />
<br />
Further optimization can be done by checking the process tree<br />
pstree -p<br />
and disable/deinstall stuff that isn't needed. KILL 'EM ALL!<br />
<br />
I did not find it yet but if you come across ads7846 remove it.<br />
modprobe -r ads7846<br />
tee /etc/modprobe.d/blacklist-ads7846.conf <<< "ads7846"<br />
<br />
=== XU4 hardware ===<br />
<br />
The key is to exchange the thermal tape of the heatsink with some good thermal paste, decreases the temperature by 10 degrees (C) using same testing conditions. Also get the under side cooled as well.<br />
<br />
To save electricity you may turn down the power supplies voltage with a screw driver.<br />
<br />
Check sd card slot heat.<br />
<br />
== Optimal big.LITTLE and Maximal RAM Usage ==<br />
<br />
aka "Getting the last Hash out of your Odroid".<br />
<br />
The first step is to use an OS image that uses a minimum amount of RAM for the system.<br />
<br />
To illustrate how to use the big.LITTLE cores and most of the memory we first have a look at the configuration<br />
with effectstocause miner.<br />
<br />
=== The Goal ===<br />
<br />
Verium mining is a lot about RAM, so you want to maximize the memory usage. <br />
How does that work?<br />
The [[https://github.com/effectsToCause/veriumMiner|effectstocause veriumMiner]] can be configured to use a different amount of RAM per thread. So the '''idea''' is to use 2 different miner compilations and make use of the 2GB LPDDR3 RAM @ 933Mhz the Odroid has.<br />
<br />
Plus: do that wisely to also benefit from the big.LITTLE cores of the <br />
Samsung Exynos5422 Cortex™ ARM Cortex-A15 (2.0Ghz) / Cortex-A7 (1.4 Ghz) Octa core CPUs<br />
<br />
=== Technical details ===<br />
<br />
The miner settings are called '''1 way''' or '''3 way''' (or [[Nway]]) where<br />
1 way => 128 MB per mining thread <br />
3 way => 384 MB per mining thread <br />
The #way of the miner is configured in<br />
nano veriumMiner/algo/scrypt.c<br />
<br />
Now you can calculate around for yourself or just trust me that you want those two miner configurations and then run<br />
5 threads @ 1 way = 640 MB <br />
3 threads @ 3 way = 1152 MB <br />
1792 MB total RAM<br />
The system needs some memory, too and with this setting there is only around 60 MB left free - but only if you use the image linked above ( I have tested 6 different ones, only this works with -t 5 & -t 3 ).<br />
<br />
A 2 way compilation might be interesting as well, but my compilation try didn't work (only boooo's).<br />
<br />
=== Easy Installation ===<br />
<br />
I have prepared two scripts on my [[https://github.com/DJoeDt/verium git repository]] (no warranty whatsoever)<br />
* [https://github.com/DJoeDt/verium/raw/master/1wayARM_XU4_VeriumMiner_install.sh 1wayARM_XU4_VeriumMiner_install.sh]<br />
* [https://github.com/DJoeDt/verium/raw/master/3wayARM_XU4_VeriumMiner_install.sh 3wayARM_XU4_VeriumMiner_install.sh]<br />
which install the miners into <br />
~/verium/1wayminer/<br />
~/verium/3wayminer/<br />
<br />
=== How to run them ===<br />
<br />
Having both compilations at hand we need to manage them properly. Besides the threads there are two things to configure<br />
# the big.little core<br />
# the API Port<br />
<br />
==== big cores -t 3 ====<br />
Thy '''big''' cores shall run the 3 way miner on the standard port 4048 with high priority<br />
--cpu-priority 4<br />
--cpu-affinity 0x00F0 <br />
-b 4048<br />
--api-bind 0.0.0.0:4048<br />
those are the options to be set. About using [[cpu-affinity]].<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 3way -t 3 big<br />
/root/verium/3wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 4 -t 3 --cpu-affinity 0x00FF --api-bind 0.0.0.0:4048 &<br />
Just copy it and give it a try as donation ;) .<br />
<br />
==== little cores -t 5 ====<br />
The ''little'' core shall run the 1 way miner on API Port 4049 with lower priority<br />
--cpu-priority 1<br />
-b 4049<br />
--api-bind 0.0.0.0:4049<br />
where I just don't touch --cpu-affinity and thus the remaining 4 little + 1 big cores are used.<br />
<br />
This is the complete line from my <nowiki>/etc/rc.local</nowiki><br />
# 1way -t 5 little<br />
/root/verium/1wayminer/cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd --cpu-priority 1 -t 5 -b 4049 --api-bind 0.0.0.0:4049 &<br />
<br />
=== Monitoring ===<br />
<br />
If you use the API you need to configure both ports. My workaround with birtys <3 webscripts looks like this:<br />
<br />
So far I have copied index_monitor.php to index_monitor4049.php, reconfigured<br />
defined('API_PORT') || define('API_PORT', 4049);<br />
in it, and just included it by adding<br />
<?php include 'index_monitor4049.php';?><br />
to the index.php.<br />
<br />
=== The Result ===<br />
<br />
Some remarks before we look at H/m:<br />
# again: only the image linked above worked for me, but not even by default<br />
# you still have to create a swap file (included in my scripts)<br />
# I lied about the lines in my rc.local, I actually mine on two different pools. Decentralize it! ;)<br />
<br />
==== Hashrate Numbers!!11 ====<br />
<br />
Originally I ran birtys miner configuration which actually is the 1 way configuration. Without any -t option it just starts 8 threads and with '''pool mining''' i got an average of<br />
395 H/m = 1 way -t 8<br />
<br />
The two miners put out like<br />
195 H/m = 1 way -t 5<br />
250 H/m = 3 way -t 3<br />
<br />
Happy adding! :)<br />
<br />
I wonder how this performs when '''solo mining?'''<br />
<br />
=== Update to fireworm miner & hugepages ===<br />
<br />
1way : 128MB -> nr_hugepages = 65.<br />
3way : 384MB -> nr_hugepages = 193.<br />
6way : 768MB -> nr_hugepages = 386.<br />
<br />
==== Configuration of birtys image ====<br />
Setup: birtys hugepages minimal image: [[https://drive.google.com/drive/folders/0B26cQdlGFXo2S3ViQ3IxaVhfUkk|google drive]]<br />
<br />
Configure hugepages<br />
sudo nano /etc/sysctl.conf<br />
to<br />
vm.nr_hugepages=839<br />
<br />
Change host <br />
nano /etc/hostname<br />
nano /etc/hosts<br />
and '''dram_freq=933''' in<br />
nano /media/boot/boot.ini<br />
as well as the password by<br />
passwd<br />
<br />
Reboot before going on<br />
reboot<br />
<br />
==== Fireworm Miner Installation ====<br />
Remove old miner from birtys image:<br />
rm -rf veriumMiner<br />
<br />
Install newest miner by script:<br />
wget https://github.com/DJoeDt/verium/raw/master/nwayARM_HC1_fireworm_install.sh<br />
chmod +x nwayARM_HC1_fireworm_install.sh<br />
./nwayARM_HC1_fireworm_install.sh<br />
<br />
==== Miner Autostart Configuration ====<br />
Autostart config<br />
nano /etc/rc.local<br />
<br />
<nowiki><br />
# Verium Miner Configuration<br />
# big cores<br />
nice --10 /root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://vrm.n3rd3d.com:3332 -u joe_rondx.1 -p joe \<br />
-t 3 -1 1 --cpu-affinity 0x00F0 --cpu-priority 2 \<br />
--api-bind 0.0.0.0:4048 --no-color >> /root/verium/nwayminer/3waymine.log &<br />
<br />
sleep 5 # delay for hugepages allocation<br />
<br />
# little cores<br />
/root/verium/nwayminer/cpuminer \<br />
-o stratum+tcp://eu.vrm.mining-pool.ovh:3032 -u joe_rondx.HC1_1 -p joe \<br />
-1 4 --cpu-affinity-stride 1 --cpu-affinity-oneway-index 0 --cpu-priority 0 \<br />
--api-bind 0.0.0.0:4049 -b 4049 --no-color >> /root/verium/nwayminer/1waymine.log <br />
</nowiki><br />
<br />
Run the 3way miner '''first''' !!<br />
-t 3 -1<br />
First because it should make maximal use of hugepages.<br />
<br />
Secondly run only 1way<br />
-1 4 <br />
where 1 thread runs without hugepages.<br />
<br />
==== Hashrate ====<br />
<br />
=> 400 + 137 = 537 H/m @ 1.9 GHz<br />
<br />
== Power to the Rig ==<br />
<br />
The specs say 4 Amps @ 5V for an Odroid. But there is way more to consider if you want to power your rig.<br />
<br />
=== Amp calculations ===<br />
<br />
=== PSU choice ===<br />
<br />
=== Cables ===<br />
<br />
=== Fuses ===</div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1270Verium Mining2018-03-03T19:44:13Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. While rare, when it occurs it is very lucrative. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
The payout algorithm of n3rd3d, beertendr and OVH recently was updated to [http://give-me-coins.com/support/faq/what-is-pplns/ PPLNS] to prevent pool hopping:<br />
<br />
<blockquote><br />
Pay Per Last N Shares (PPLNS) - A PPLNS pool is the same as a Prop pool in so much as the miner takes the risk of variance. Where they differ is how the payouts are calculated. PPLNS pools were designed to stop pool hoppers as they don’t technically payout the current block, rather they payout based on an average of the shares you submit over the last x number of blocks. As a result, when you first start mining on a PPLNS pool like d2’s pools you’ll notice that you hardly get paid anything until a few hours later. This will ramp up over time and once you stop mining, you still get paid for a few hours… this is due to the “buffer effect” of PPLNS and pool hoppers hate this as they cant jump on a fresh, profitable round! You, as a loyal miner still get the correct amount eventually but you have to be a bit patient for the ramp up and ramp down times.<br />
</blockquote><br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor].<br />
<br />
A python script to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you are using a single miner or a miner bound to a different port number, change the ports in the list in monitor.py:<br />
<br />
#! monitor.py<br />
ports = [4048, 4049] #! NOTE: Change port numbers to those in use by your miners<br />
<br />
Each miner has to be configured with the correct api-bind option at launch:<br />
<br />
cpuminer [options] --api-bind "0.0.0.0:<port-number>"<br />
<br />
So long as cpuminer is configured with the correct api-bind option, this script will work regardless of worker architecture.<br />
<br />
NOTE: different miners may not report all currently displayed information. For example, tpruvot's miner does not report accurate CPU temperatures for XU4s out of the box (as of this writing).<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1268Verium Mining2018-03-01T03:31:16Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. While rare, when it occurs it is very lucrative. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
The payout algorithm of n3rd3d, beertendr and OVH recently was updated to [http://give-me-coins.com/support/faq/what-is-pplns/ PPLNS] to prevent pool hopping:<br />
<br />
<blockquote><br />
Pay Per Last N Shares (PPLNS) - A PPLNS pool is the same as a Prop pool in so much as the miner takes the risk of variance. Where they differ is how the payouts are calculated. PPLNS pools were designed to stop pool hoppers as they don’t technically payout the current block, rather they payout based on an average of the shares you submit over the last x number of blocks. As a result, when you first start mining on a PPLNS pool like d2’s pools you’ll notice that you hardly get paid anything until a few hours later. This will ramp up over time and once you stop mining, you still get paid for a few hours… this is due to the “buffer effect” of PPLNS and pool hoppers hate this as they cant jump on a fresh, profitable round! You, as a loyal miner still get the correct amount eventually but you have to be a bit patient for the ramp up and ramp down times.<br />
</blockquote><br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor].<br />
<br />
A couple of python scripts to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you are using a single miner or a miner bound to a different port number, simply change the port number(s) in the agent script.<br />
<br />
#! miner-apid.py<br />
ports = [4048, 4049] #! NOTE: Change port numbers to those in use by your miners<br />
<br />
The monitor was tested on a setup with 21 ODROIDS, two laptops, and two Raspberry Pi 3Bs.<br />
It should work on S912s. I have one on the way to test with.<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1267Verium Mining2018-03-01T02:35:18Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. While rare, when it occurs it is very lucrative. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
The payout algorithm of n3rd3d, beertendr and OVH recently was updated to [http://give-me-coins.com/support/faq/what-is-pplns/ PPLNS] to prevent pool hopping:<br />
<br />
<blockquote><br />
Pay Per Last N Shares (PPLNS) - A PPLNS pool is the same as a Prop pool in so much as the miner takes the risk of variance. Where they differ is how the payouts are calculated. PPLNS pools were designed to stop pool hoppers as they don’t technically payout the current block, rather they payout based on an average of the shares you submit over the last x number of blocks. As a result, when you first start mining on a PPLNS pool like d2’s pools you’ll notice that you hardly get paid anything until a few hours later. This will ramp up over time and once you stop mining, you still get paid for a few hours… this is due to the “buffer effect” of PPLNS and pool hoppers hate this as they cant jump on a fresh, profitable round! You, as a loyal miner still get the correct amount eventually but you have to be a bit patient for the ramp up and ramp down times.<br />
</blockquote><br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor].<br />
<br />
A couple of python scripts to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you are using a single miner or a miner bound to a different port number, simply change the port number(s) in the agent script.<br />
<br />
The monitor was tested on a setup with 21 ODROIDS, two laptops, and two Raspberry Pi 3Bs.<br />
It should work on S912s. I have one on the way to test with.<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1252File:Cli monitoring.png2018-02-24T16:17:11Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1251File:Cli monitoring.png2018-02-24T15:07:50Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1250File:Cli monitoring.png2018-02-24T15:07:20Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1249File:Cli monitoring.png2018-02-24T15:06:36Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=File:Cli_monitoring.png&diff=1248File:Cli monitoring.png2018-02-24T14:57:54Z<p>Benzini: Benzini uploaded a new version of File:Cli monitoring.png</p>
<hr />
<div></div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1247Verium Mining2018-02-24T14:53:41Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
casanova's [https://github.com/bezeredi/verium-cli-monitor CLI Monitor].<br />
<br />
A couple of python scripts to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you would like to use it on machines using a different number of miners or miners using different port numbers, you'll<br />
have to modify the agent script. The scripts use Python 3 and ZMQ.<br />
<br />
The monitor was tested on a setup with 21 ODROIDS, two laptops, and two Raspberry Pi 3Bs.<br />
It should work on S912s. I have one on the way to test with.<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1246Verium Mining2018-02-24T14:53:02Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
Evan's [https://github.com/bezeredi/verium-cli-monitor Verium CLI Monitor].<br />
<br />
A couple of python scripts to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you would like to use it on machines using a different number of miners or miners using different port numbers, you'll<br />
have to modify the agent script. The scripts use Python 3 and ZMQ.<br />
<br />
The monitor was tested on a setup with 21 ODROIDS, two laptops, and two Raspberry Pi 3Bs.<br />
It should work on S912s. I have one on the way to test with.<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzinihttps://wiki.vericoin.info/index.php?title=Verium_Mining&diff=1245Verium Mining2018-02-24T14:51:16Z<p>Benzini: /* CLI Monitoring */</p>
<hr />
<div>The days of needing specialized computing hardware and sophisticated know-how to mine digital currency are over. Anyone can easily mine Verium. Just download the Verium Vault software to any computer, click mine and starting earning Verium, the digital gold that backs the digital currency VeriCoin. Verium is one of the few digital currencies that can not be mined by specialized GPUs and ASICs.By making it easy for anyone and everyone to mine Verium the project has created a more decentralized system.<br />
<br />
'''Power Based Rewards'''<br />
<br />
As mining power increases the reward slowly decreases, this mechanism makes the reserve commodity supply curve drop based on increased demand and can drive a value increase over time and increased usage.<br />
<br />
== General ==<br />
<br />
The overall network can be viewed in the [http://veriumstats.vericoin.info/ Live Global Mining Statistics].<br />
<br />
The network difficulty evolution is displayed [http://explorer.vrm.vericoin.info/diff here].<br />
<br />
* Complete Guide [https://steemit.com/verium/@birty/cpu-mining-is-back-a-complete-how-to-guide-and-profit-analysis-for-verium-mining-on-a-farm-of-single-board-computers-part-1 How To Mine Verium] by birty<br />
<br />
=== Miner command options ===<br />
<br />
The mining command options differ a bit depending on the actual software and setup you use, but this sample should give an overview:<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -1 4<br />
\ Pool URL or Solo Wallet IP / \ Pool User Name / \ PoolPwd / \ #threads /<br />
Details for [[#Pools|pool miners]] or [[#Solo|solo miners]].<br />
<br />
Further options <br />
* CPU specific <br />
--cpu-priority 4 --cpu-affinity 0x0000F0<br />
* API<br />
-b 4049 --api-bind 0.0.0.0:4049<br />
<br />
== Mining Software Guides ==<br />
<br />
=== Source Code ===<br />
<br />
The first mining software especially designed for Verium was provided by Douglas Pike aka effectstocause, one of the creators of this project. <br />
* [https://github.com/effectsToCause/veriumMiner Git repository effectstocause/veriumMiner]<br />
<br />
Based on effectstocauses original miner fireworm has created an update which includes several optimizations especially for Linux (memory) and ARMv8 CPUs.<br />
* [https://github.com/fireworm71/veriumMiner Git repository fireworm71/veriumMiner]<br />
<br />
cpuminer, cpuminer-opt can be used as well.<br />
<br />
=== Windows ===<br />
<br />
* [[Windows#Verium_Mining|Windows Mining ]]<br />
<br />
=== Mac OS ===<br />
<br />
* [[Mac_OS#Verium_Mining|Mac OS Mining ]]<br />
<br />
=== Linux ===<br />
<br />
* [[Linux#Verium_Mining|Linux Mining ]]<br />
<br />
=== Android ===<br />
<br />
* [https://www.reddit.com/r/vericoin/comments/7i7kg4/put_those_old_android_devices_to_use_mining_verium/ Put Those Old Android Devices to Use Mining Verium]<br />
<br />
== Solo vs. Pool Mining ==<br />
<br />
=== Solo ===<br />
<br />
Solo mining is not for everyone but with a little patience and determination even low hash rates can render results. If you have over 15Kh/m and don't mind waiting for your rewards, there are several advantages.<br />
<br />
* Zero downtime - You are directly connected to the blockchain<br />
* Zero pool fees - Typically about 1%<br />
* Zero withdrawal fees<br />
* Zero trust in a third party<br />
* zero dependency on pool availability<br />
* All transaction fees per block!<br />
<br />
==== Step 1: Setup your Wallet ====<br />
<br />
Once you have your verium wallet installed, you must edit your verium.conf file. The following example assumes your local network is 192.168.1.0/24 and your wallet has an IP address of 192.168.1.10. You will need to keep your 'rpcuser' and 'rpcassword' when you point your miner to your wallet.<br />
<br />
<pre style="color: blue"><br />
server=1<br />
daemon=1<br />
rpcuser=solouser<br />
rpcpassword=s0l0pass<br />
rpcallowip=192.168.1.*<br />
rpcallowip=localhost<br />
</pre><br />
<br />
The verium.conf can be found in the following locations:<br />
<br />
Windows:<br />
<pre style="color: blue"><br />
%APPDATA%\Roaming\Verium<br />
<br />
or<br />
<br />
c:\users\[username]\appdata\roaming\verium<br />
</pre><br />
<br />
Linux\*nix:<br />
<pre style="color: blue"><br />
~/.verium <br />
<br />
or<br />
<br />
/user/home/.verium<br />
<br />
(The folder is hidden so you must put the "." in the path)<br />
</pre><br />
<br />
==== Step 2: Point your miner to your wallet ====<br />
<br />
Once you have you wallet setup. You can start pointing your miners to mine direct. <br />
<br />
For windows:<br />
<pre style="color: blue"><br />
cpuminer.exe -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
For *NIX:<br />
<pre style="color: blue"><br />
./cpuminer -o 192.168.1.10:33987 -O solouser:s0l0pass<br />
</pre><br />
<br />
REF:<br />
<br />
* [http://resources.vericoin.info/wp-content/uploads/Verium-Solo-Mining-Guide.pdf Verium Solo Mining Guide]<br />
<br />
* [https://docs.google.com/document/d/19aLLX7VmwZWFSLou7nf3mcKcAGWn0emqB9noS2boEM0/edit?usp=sharing Drawde's Guide]<br />
<br />
=== Pools ===<br />
<br />
'''NEW''': [https://poolstats.vericoin.info/ Detailed overview] of all pools.<br />
<br />
The following mining pools are available. Please look at their "Getting started" pages:<br />
<br />
* [https://beertendr.com/ beertendr]<br />
* [https://moulesfrites.call-cc.be MoulesFrites]<br />
* [https://pools.bloxstor.com/ bloxstor]<br />
cpuminer -o stratum+tcp://pool-eu.bloxstor.com:3003 -u VEXMki29ycW5vSt3MmdM5iwHqsHux91EMr.Guide -p GuidePwd -t x -1 y<br />
\ Pool URL incl. port for difficulty ^ / \ Pool User Name + Worker ^/ \ PoolPwd / \ #threads /<br />
* [https://verium.everythingembedded.com The Verium Zone]<br />
* [https://vrm.mining-pool.ovh mining-pool.ovh]<br />
* [https://vrm.n3rd3d.com/ n3rd3d - Verium Mining Pool]<br />
cpuminer -o stratum+tcp://us.vrm.n3rd3d.com:3333 -u Weblogin.WorkerName -p WorkerPassword<br />
\ Pool URL incl. diif.-port ^ / \ Pool User+ Worker / \ PoolPwd / <br />
* [https://vrm.poolium.win/ poolium]<br />
::# Register for an account<br />
::# Login and create a worker for each miner you control<br />
::# Download your miner e.g. cpuminer-opt or verium miner<br />
::# Configure your miner for Poolium<br />
::::''Poolium Settings'':<br />
<br />
::::For cpuminer-opt...<br />
::::<code>./cpuminer-opt -a scrypt:1048576 -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Or for verium miner...<br />
::::<code>./cpuminer -o stratum+tcp://vrm.poolium.win:3333 -u Weblogin.WorkerName -p WorkerPassword</code><br />
<br />
::::Weblogin is your registered username from Step 1.<br />
::::Workername and WorkerPassword are the values you set when you created your worker in Step 2.<br />
<br />
::::''''Note:'''' These command lines are for Linux. If you are using Windows, replace the "./" with the path to your .exe file. <br />
<br />
* [https://vrm.poolsloth.com poolsloth]<br />
<br />
How to [[Setting up a Verium Mining Pool|set up a Verium Mining Pool]].<br />
<br />
Reminder: when solomining there is zero downtime, zero pool fees, zero withdrawal fees, zero trust, zero dependency, plus all transaction fees per block!<br />
<br />
Fee efficient payout is 20 VRM (which will cost 0.2 fee).<br />
<br />
==== Pool FAQs ====<br />
<br />
* [[Complete_FAQ_Collection#Pools|Pool FAQs]]<br />
<br />
== Hardware ==<br />
<br />
=== Hashrates ===<br />
<br />
See a comparison of hashrates across a variety of processors! <br />
* [https://docs.google.com/spreadsheets/d/1O-hyFS-bqsopttmql6NgYWlWej9rZk_lm5MWivnehXg/edit#gid=0 Hashrate Spreadsheet]<br />
<br />
Help us out by adding your hashrate to the growing database! <br />
* [https://docs.google.com/forms/d/1dA8Tc2cp38XPtZu9PeondxscRhHd60V2IPrxeVrpsbM/viewform?edit_requested=true Verium Hashrate Comparison (solo mining only)]<br />
<br />
* [https://github.com/phiten/hashcomp Automatic hashrate submission and comparison]<br />
<br />
A hashrate profitability calculator:<br />
# Please make your own copy of [https://docs.google.com/spreadsheets/d/1b02BuES4AwZW9kpqzmyrPlEfO55TWdU_mFhgnVaakQ4/edit#gid=366374027 this spreadsheet] by selecting "File > Make Copy"<br />
# Make changes locally by entering your data into the green fields (the spreadsheet has been locked except for green cells to ensure continued functionality)<br />
<br />
=== Hardware Buying Guide ===<br />
If you are planning on purchasing hardware for VRM mining there are 4 main routes you can take. The fasted ROI can be had from used server hardware; the best long term profitability comes from used laptops and SBC’s.<br />
<br />
# Used Server Hardware<br />
# Used Laptops<br />
# Single Board Computers (SBC)<br />
# Desktops<br />
<br />
The below table outlines the basic pros and cons of each build type:<br />
<br />
{| class="wikitable"<br />
| || Power Usage || Upfront Cost || Maintenance Burden || Hashrate <br />
|-<br />
| Used Server || High-Low || Low-High || Low || High <br />
|-<br />
| Used Laptop || Low || Low || Medium || Low/Medium <br />
|- <br />
| SBC || Low || High || High || Low <br />
|-<br />
| Desktop || Medium || Medium || Low || Medium <br />
|}<br />
<br />
'''[[Hardware_Buying_Guide|Complete Hardware Buying Guide]]'''<br />
<br />
== Maintenance & Monitoring ==<br />
<br />
If you have a Raspberry Pi at hand there is an [[Raspberry_Pi#Verium_CLI_Wallet_.26_Webmonitor_Image|OS image with pre-installed Web-based Miner Monitor]] for easy use.<br />
<br />
=== Web-based Monitoring ===<br />
<br />
A web-based miner monitor was initially contributed <br />
* [http://goo.gl/rCF0cx here] by birty and there is an <br />
* extended version [https://github.com/derricke/MinerMonitor here] done by DerrickE as well as <br />
* another one [https://github.com/wienerdogracing/MinerMonitor here] by wienerdog. <br />
* Updated frontend version forked from DerrickE's by ChiefThunderCunt [https://github.com/drfogs/MinerMonitor here]<br />
* [https://miner.farm Miner.farm] is interesting. Needs some set-up and shuffling of binaries but it also allows control of miner (at least start/stop) from any web browser. I have played around with it some. Very spiff. Not $cheap. Low system resource use.<br />
* [https://getminera.com Minera] can be set up for custom local-miner and also can monitor miners on your LAN by RPC. ad-supported $free. I have played with it, some. Spiff. Easy install and set-up. Requires node.js and all the system overhead that comes with it. Right now Minera does not appear to work with Fireworm's cpuminer port.<br />
<br />
You can also check your miners if you run your wallet on linux by executing:<br />
Netstat | grep :33987 <br />
in a terminal. If they are connecting means they are working.<br />
<br />
=== CLI Monitoring ===<br />
<br />
[[File:cli_monitoring.png|thumb]]<br />
<br />
A couple of python scripts to help monitor miners on a LAN, great for small to moderate sized SBC setups.<br />
<br />
By default, it is configured to work on a machine running two miner instances, one using port 4048 and one using port 4049.<br />
If you would like to use it on machines using a different number of miners or miners using different port numbers, you'll<br />
have to modify the agent script. The scripts use Python 3 and ZMQ.<br />
<br />
The monitor was tested on a setup with 21 ODROIDS, two laptops, and two Raspberry Pi 3Bs.<br />
It should work on S912s. I have one on the way to test with.<br />
<br />
It can be found [https://github.com/bezeredi/verium-cli-monitor here].<br />
<br />
== Optimization ==<br />
<br />
=== Windows === <br />
<br />
* [[Windows#Optimization|Windows Optimization]]<br />
<br />
=== Mac OS === <br />
<br />
* [[Mac_OS#Optimization|Mac OS Optimization]]<br />
<br />
=== Linux === <br />
<br />
* [[Linux#Optimization|Linux Optimization]]<br />
** Special [[Odroid]] Section</div>Benzini