SRBMiner Cryptonight AMD GPU Miner

Windows only

Download V1.7.0:

Mega : Download SRB_Miner  https://mega.nz/#!uvZnRQDb!FKFCsS594vhSHiYopjDAzbpMN8pkIsfCQaiQYMZE8tk

If you have a Vega, and want to mine V7 algos, use Adrenaline 18.6.1 drivers, if you want to mine Heavy algos, use Adrenaline 18.3.4

ATTENTION:
From V1.4.0 the miner uses a separate pools.txt file, where you define your pools, wallet, etc.
Config from older versions that includes pool related data, won’t be used!

Supported algos:

Cryptonight [normal]
Cryptonight Lite [lite]
Cryptonight V7 [normalv7]
Cryptonight Lite V7 [litev7]
Cryptonight Heavy [heavy]
Cryptonight Haven [haven]
Cryptonight Fast [fast]
Cryptonight BitTubeV2 [bittubev2]
Cryptonight StelliteV4 [stellitev4]
Cryptonight ArtoCash [artocash]
Cryptonight Alloy [alloy]
Cryptonight B2N [b2n]
Cryptonight MarketCash [marketcash]
Cryptonight Italo [italo]
Supports Nicehash, Nicehash V7 & SSL/TLS encrypted connections

DevFee:

Low DevFee (0.85%) ; every ~2 hours 1 minute mining for the dev
Non-agressive DevFee mining ; if miner can’t connect to DevFee pool, no problem, switching back to user pool ASAP

Performance:

Only one parameter you have to play with : intensity (0 - 300)
Leave intensity on 0, and miner will try to set a minimum start intensity automatically
To get even better results, there is an option to use double threads

Extra:

Watchdog that monitors your GPU threads, if they stop hashing for a few minutes, miner restarts itself
Hash monitor, if 5 minute average hash falls under the value you define, miner restarts itself
Set system shutdown temperature, to protect your GPU’s from overheating
Restart (disable/enable) Vega gpu’s with devcon before mining
API for rig monitoring

Tips:

If you leave intensity on 0 it will play safe, so in many cases you can increase that value to get better results
For better results set double_threads to true, and leave intensity on 0
If you get an error that says it can’t create scratchpad buffer, you have to lower intensity
Largest intensity setting won’t always give you the best hashrate. Experiment and find the best setting for your GPU.

Here’s a (not complete) list of supported coins, and which algo has to be used

normal
+Electroneum
+ByteCoin
+Karbo
+DigitalNote
+Leviar
+Ultranote
+BalkanCoin
+BitSum
+CrepCoin
+DinastyCoin
+LeviarCoin
+BitCoal
+Sumo
+IntuCoin

normalv7
+Monero
+MoneroV
+Intense
+Graft
+BBS
+Wownero
+Lines
+Fonero
+Myztic

lite

litev7
+Turtlecoin
+Iridium
+Aeon

heavy
+Ryo
+Loki
+Bloc.Money
+BixBite
+Saronite
+Ombre
+ItaloCoin
+Niobio
+ZBucks

bittubev2
+Ipbc/BitTube

artocash
+Artocash

alloy
+Alloy

marketcash
+MarketCash

b2n
+Bitcoin2Network

stellitev4
+Stellite

fast
+Masari

haven
+Haven

italo
+ItaloCoin (from block 55.000)

Update infos :

Don’t copy newer version of miner over old one, or if you do make sure you delete .srb files from Cache folder before running it!

V1.7.0

Speed increase on BitTube/Haven/Heavy/Italo algos up to ~10% (depends of gpu)
Small speed increase on V8 algo for Vegas
Added new algo CN-Dark [CryoNote]
Added new algo CN-Fest [Festival coin]
Added startup monitor which monitors miner startup process
Added new work mode for GPU hashrate watchdog [–gpuwatchdogdisablemode]
Added yet another gpu tuning parameter ‘aes’
Fixed a bug related to hash speed monitor and algo switching
Small bug fixes
V1.6.9

Algo switching without miner restart
Benchmark everything from algos.txt and just paste the hashrates (–benchmarkalgos)
Added number of algo switches to API and stats
Added cmd parameter --resetmineronalgoswitch which forces miner to reset on algo change
Changed minimum --algoswitchmintime from 3 min to 30 sec, default is still 600 sec
Fixed API pool stats when not connected to a pool
Added cmd parameters --cjobtimeout, --cmaxdifficulty, --ckeepalive
When critical temp is reached, ADL temp is now logged before shutdown
Notification on too many compute errors (set with --gpuerrorsalert value)
Added a performance tuning parameter ‘fragments’ for gpu_conf and cmd
Fixed a bug that could crash miner on shutdown
V1.6.4

Added possibility/support to set GPU’S with cmd parameters directly in start.bat
Added parameter --sendallstales , which enables sending of every stale share
Minor bug fixes

V1.6.3

More speed on Vega56 cards on every algo (probably on Vega64 and VegaFE too, i don’t have them to test)
Added parameter --enableduplicategpuid (used in start.bat), that enables to use the same gpu id in gpu_conf multiple times
Removed useless kernels 3 and 4
Removed useless CPU opencl support

V1.6.2

Added support for Italocoin new algo (from block 55.000)
Auto intensity for Vega cards improved, also managed to increase hashing speed on Vega cards for about ~1-1.5% (mainly on heavy algos)
If user uses non existing GPU id in gpu_conf, it will be ignored, no error will be thrown
Fixed miner crash when using a non AES capable CPU on some algos
Added Windows version and build in log
Added video driver version in log
Added info about CPU AES support in log
Statistics now shows number of stale shares that were accepted by pool
Added parameter ‘min_rig_speed_duration’ that can set period for ‘min_rig_speed’ parameter (minimum is 30 sec), default is 5 min

V1.6.1

Changed IPBC/Bittube old algo to new BitTubeV2 algo (from block 110000)
Max difficulty reconnecting mechanism is now triggering instantly
Added ‘worksize’ option in config.txt, that is applied to every GPU (only if not set in gpu_conf)
Hopefuly fixed a bug with job timeout reconnecting
Hashrate watchdog now triggers even when user not connected to pool

Supported OS:

Windows 7/10
Ubuntu
EthOS
nvOC
SimpleMining OS
Current version 0.0.33:

Support SMS/Telegram/Push notifications when:
– GPU temperature gets higher than required
– GPU temperature gets lower than required
– Miner is not responding for X amount of minutes
– GPU Fan speed is lower than X
– GPU Fan speed is higher than X
– Miner hashrate too low
– GPU hashrate too low
Supports multiple miners with one local software installed.

Log file support.
CCMiner-Alexis 1.0
CCMiner Palgin skunk mod
CCMiner SP Skunk mods
CCMiner >= 2.0
EWBF Support
XMR-Stak
SGMiner
dstm ZM
EthMiner
BMiner
PhoenixMiner
Excavator by NiceHash (1.4, 1.5)
Claymore’s Dual Miner support
Added SSL support for data update.
ASIC AntMiner support
Web service

Profit monitoring
Dailiy profit graph
WhatToMine.com 2 profit calculation based on current hashrate and power
Hashrate graphs
Temp graphs
Power usage graphs
EthControl v0.0.19a

Supports CCMiner auto-restart when CPU does not validate.
Supports EWBF auto-restart when cuda device thread exited.
Bulk updates for remote configuration / install.
Ethminer full monitoring with GPU hashrate, GPU temp and GPU fan speeds.
Remote rig reboot support.
Remote stop/start support for mining software.
Web console for remote diagnostics
Automatic miner software installation support and updates
GPU monitoring.
Afterburner profile loading
Starts with windows automatically
Crash reports
CCMiner “invalidate cpu” error auto-restart
Easily deploy custom ccminer forks, claymore updates, custom software to multiple rigs
# Supports #

CCminer
Cast XMR
EthMiner
Claymore dual miner
ZM dstm
EWBF
eMiner
bMiner
Phoenix Miner
Excavator
Gateless gate
XMR-Stak
Cast-XMR
How to use:
Download windows binary from here: Download EthMonitoring https://mega.nz/#!XrYVWYzI!4xyDBt961cZp6mB20q32kT043mr99JLCsS3uTuXtEZA

JCE Cryptonote CPU Miner

Welcome to the Fastest Cryptonote CPU Miner ever!

You can download it from the Mega page here:
Download JCE Miner https://mega.nz/#!y2ISiQ7I!tBmzyLxf0bWFZ9STZtyyCb_SFJ9gtMPwHLK8cR36Zk0

Is that a Virus? No!

Like all miners, JCE gets detected as a virus by most Antiviruses, including Windows Defender. But it’s not. Read more about Privacy and Security below.

Is it just yet-another fork of a common miner? No!

You’re not losing your time testing a made-up rip of a common miner, JCE is brand new, using 100% new code.

Are the new Monero-V7, Cryptolight-V7, Cryptonight-Heavy, IPBC, Alloy, MKT and XTL forks supported? Yes!

The --variation parameter let you choose the fork. More details below.

Speed

In short, JCE is:

Crazy fast on non-AES 64-bits, usually 35-40% faster than other miners
Compared to other 32-bits miners, still faster on non-AES 32-bits, sometimes beating even the other miners 64-bits versions
And still faster on non-AES 32-bits Cryptonight-Heavy, with usually +50% speed.
Barely faster than the other best on AES 64-bits, beating them by ~1%, +2.8% on V7 fork, +4% on Cryptonight-Heavy
Also a lot faster on AES 32-bits, but it’s a rare case (mostly seen on Intel Atom tablets)
Here’s a benchmark against three other common miners.
The test is fair : run on the exact same Win10 Pro computer, all Huge Pages enabled, no background task, best configuration.

XMRStak means: the released Unified binary from github (not recompiled myself)
XMRig means: the respective best released binary gcc (32-bits) and msvc (64-bits) from github (not recompiled myself)
Claymore means: best Claymore CPU (3.4 for 32-bits, 3.9 for 64-bits)
When not supported, score is zero, if not tested yet, score is ?
Fees are included in the score
Core2 Quad 2.666 GHz 12M, 4 threads, 64-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
116   80   85   57
Core2 Quad 2.666 GHz 12M, 4 threads, 32-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
93   0   68   50
Ryzen 1600, 8 threads, 64-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
506   502   502   443
Ryzen 1600, 8 threads, 32-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
434   0   327   275
Ryzen 1600, 8 threads, 64-bits, Cryptonight V7

JCE   XMRStak   XMRig   Claymore
503   492   491   ?
Ryzen 1600, 8 threads, 32-bits, Cryptonight V7

JCE   XMRStak   XMRig   Claymore
424   0   320   ?
Core2 Quad 2.666 GHz 12M, 4 threads, 64-bits, Cryptonight Heavy

JCE   XMRStak   XMRig   Claymore
50   33   36   0
Ryzen 1600, 4 threads, 64-bits, Cryptonight Heavy

JCE   XMRStak   XMRig   Claymore
252   169   250   0
Ryzen 1600, 4 threads, 32-bits, Cryptonight Heavy

JCE   XMRStak   XMRig   Claymore
191   0   174   0
Getting started

If you’re new at mining Cryptonight, here’s the simplest way:

Choose the coin to mine, see the list below. The most common is Monero.
Get a wallet, that’s a ~95 character long identifier. If you don’t have one yet, you can create it
Choose a pool to mine on, and its port. For example Pool pool minexmr com and port 4444
Edit the start.bat that’s shipped in the .zip
Change the example POOL by yours
Change the example PORT by yours
Change the example WALLET by yours
You can leave the default password x
(Optional) If your coin is exotic, maybe you also need to change FORK=0 to another number. See the list in the start bat
Run start bat
Basic topics

Q. Is it free (as in beer, as in freedom)?
No and no. It has fees, and is not open source. But the program itself is free to distribute.

Q. How much cost the fees?
Current fees are:

3.0% when using at least one mining thread with non-AES architecture, or 32-bits
1.5% when using only 64-bits AES architecture
The fees are twice higher in non-AES mode and/or 32-bits because JCE offers a huge performance gain here.

Q. Can I avoid fees?
Not really. I plan to offer a paying per-licence-no-fee (pay-once-for-all) version, but it’s a lot more complicated to set up than a fee-based miner.
Also, JCE never takes any fee during the first minute, so if you run it, and kill it after one minute, and repeat again and again, then you’ll never pay any fee, but JCE takes a few seconds to start, and your Pool probably won’t let your reconnect continuously.

Q. Will it work on my computer?
Minimum is Windows Vista 32-bits, or Linux, with a SSE2 capable CPU. 64-bits is faster, prefer it.
For best performance, Large Pages must be enabled, JCE will try to auto-configure them, but it may work or not depending on your Windows version and security configuration.

Q. What currency can I mine? On which pools?
You can mine any coin on any pool.
If your coin is listed, all is automatic.
Run the miner with --coins parameter to get the up-to-date list. Current list is:

Monero (XMR)
Monero-V (XMV)
Electroneum (ETN)
Karbowanec (KRB)
Bytecoin (BCN)
Sumokoin (SUMO)
Bitcoal (COAL)
Bitcedi (BXC)
Dinastycoin (DCY)
Leviarcoin (XLC)
Fonero (FNO)
Turtlecoin (TRTL)
Graft (GRFT)
Dero (DERO)
Stellite (XTL)
UltraNote (XUN)
Intense (INTS)
Crepcoin (CREP)
Pluracoin (PLURA)
Haven (XHV)
FreelaBit (FBF)
BlueberriesCoin (BBC)
B2BCoin (B2B)
Bitsum (BSM)
Masari (MSR)
SuperiorCoin (SUP)
EDollar (EDL)
Interplanetary Broadcast (IPBC)
Alloy (XAO)
BBSCoin (BBS)
BitcoiNote (BTCN)
Elya (ELYA)
Iridium (IRD)
Italo (ITA)
Lines (LNS)
Niobio (NBR)
Ombre (OMB)
Solace (SOL)
Triton (TRIT)
Truckcoin (TRKC)
Qwertycoin (QWC)
Loki (LOK)
Ravencoin(RVN)
Gadcoin (GAD)
MarketCash (MKT)
ArtoCash (RTO)
Nicehash Cryptonight v7
Minergate Cryptonight v7
MiningPoolHub Cryptonight v7
MiningRigRentals Cryptonight v7
Suprnova Cryptonight v7
Otherwise, if your coin is not listed, or your wallet not recognized, use the --any parameter, plus the --variation N parameter, with N the fork number, see list below. The fork detection is automatic on known coins, but manual on unknown coins. The coin list is periodically updated.

Q. Is Nicehash supported?
Yes, see list above. The Nicehash-specific Nonce is then automatically enabled.

Q. Is SSL supported?
Yes, with parameter --ssl

Q. I get only bad shares, what happens?
Your coin has probably forked. Add --variation N parameter, with N as listed below, until you find the one that works.

Q. What if my wallet is not recognized, or as a different coin?
Some coins use a wallet syntax so close that they’re hard to differenciate, like Lines and Loki. If JCE fails to detect the coin, force it with --any --variation N (with N as listed below) and let the miner run. It will still display the wrong coin but mine the good one. And of course proof-check pool side that you correctly get the shares.

Q. Is there a HTTP server to monitor the miner?
Modern pools provide all you need to monitor your miners (average hashrate, worker-id…). Monitoring is now a pool’s job. Still, a minimal HTTP Json server is available with parameter --mport P (P the port number) to ease integration of JCE into mining tools, but not intended for human reading. Forager was the first tool to integrate JCE, take a look!
For more compatibility, with extra parameter --stakjson, the JSON will be in XMR-Stak format.

Advanced topics

Q. Are there requirements or dependencies?
No. JCE is just a big standalone executable.

Q. Is there a Linux version?
Yes, starting from version 0.29

Q. Is there a GPU version?
Not yet.

Q. Is there a 32-bits version?
Yes, both 32 and 64 are always in the same release, for both Linux and Windows.

Q. How many threads can I setup?
Maximum is 64 threads on 64 CPUs.

Q. Do I get a discount on fees if I use SSL?
I’m not Claymore.

Q. What is that value logged when I find a share?
The amount of hashes your pool will credit you. This is not the amount of crypto-coins.

Q. How is developed JCE?
The network and stratum handling is C++14, and the mining algos are assembly (to be precise, GNU Extended Assembly). Hence the speed increase.

Q. Can I plug it to a stratum proxy?
No, it must mine on a real pool on Internet.

Q. Is it really new? It looks familiar to me…
Yes it is. But it reuses, on purpose, some de-facto conventions from other common miners, like a XMRStak-style cpu configuration, and the colors of Claymore (green=share, red=error, blue=hashrate, yellow=status).

Q. How is the hashrate calculated?
That’s the average speed of the last 512 hashes (not shares found, computed hashes), rounded at 0.01. And it’s fair, the displayed number has no tweak, and includes the fees. The total is first summed from exact per-thread values, then rounded (said differently, it’s a rounded sum, not sum of rounded).

Q. Can I get a long-time speed average?
Better look at your pool’s reports, but JCE also gives the average effective net hashrate when pressing R. It’s usually slightly lower than the physical hashrate because of outdated shares and fees.

Q. Can I do multi-pool auto-switch in case of failure? Or periodically?
Not directly, but the -q and/or the --autoclose parameters, with the help of a simple .bat, can do the job. The .zip comes with an example, open and edit it to match your needs.

Q. What if the Architecture codename is wrong (e.g. my CoffeLake is detected as Core2)?
It may be because of an option in your BIOS Max CPUID or the microcode is not up-to-date. However the codename displayed is mostly cosmetical and JCE will still choose the good assembly based on your CPU instruction set. If a normally available instruction set is missing (e.g. your Westmere has no AES) again, that’s to be unlocked in your BIOS.

Q. Can I mix architectures when mining (i.e. thread 1 uses core2, thread 2 uses pentium4)?
It sounds strange, but yes. However, that’s mostly useful for tests.

Q. Can I mix coins when mining (i.e. thread 1 mines XMR, thread 2 mines ETN)?
No.

Q. Can I mix simple-hash and multi-hash?
Yes, and it’s a very common case when mining TurtleCoin or IPBC.

Q. What is “use_cache”:false useful for?
The no-cache mode means the cache is mostly bypassed, depending on your hardware. When using a lot of cache but few cores (typically when mining Cryptonight-Heavy) assigning unused physical cores to no-cache mining can give you a few extra h/s for free. However mixing cache and no-cache of logical CPUs of the same physical core causes terrible performance.

Q. What a great job! Can I make a donation?
Thanks bro. You can, with the --donate parameter which raise the fees to 80%, or by sending coins to the donation wallet (the one in the start.bat file included).

#################################################
# dstm's ZCash Cuda miner
#################################################

I've written it initially for my own purpose. It performs pretty well - so here it is.
Compatible with devices having Compute Capability 5.0 and greater i.e. it should run fine on Maxwell/Pascal GPUs.
Supports every server using the stratum protocol. If you have issues with certain pools pls. report them here.
Contains 2% devfee.
Suggestions are welcome.

Download: Zcash Nvidia_Miner
Linux x64:
https://mega.nz/#!rXpjAC7D!1BLUk0PVwI9BMKLzk0HHUQLx4UBMEZL_1IXh1sJa6uU

Win x64:
https://mega.nz/#!qv4jELBK!_mrKsExtp9SYW14Md4DIRyfGWh94GCGFGW7DD0zBF_g

Performance:
1080Ti 725-740 Sol/s
1070 440-450 Sol/s
stock settings


UI:
Sample output mining on a rig with 8 GPUs.
GPU0-7: 1070Ti


Code:
> GPU0 65C 75% | 507.9 Sol/s 504.9 Avg 269.8 I/s | 4.52 S/W 112 W | 3.74 100 39 ++++++++
> GPU1 64C 70% | 508.4 Sol/s 509.1 Avg 273.0 I/s | 4.57 S/W 111 W | 4.11 100 38 +++++++++
> GPU2 62C 70% | 512.9 Sol/s 514.0 Avg 274.0 I/s | 4.60 S/W 110 W | 2.62 100 37 +++++
> GPU3 61C 70% | 502.4 Sol/s 500.8 Avg 266.9 I/s | 4.48 S/W 113 W | 2.24 100 38 ++++++++*
> GPU4 64C 70% | 508.6 Sol/s 508.2 Avg 272.9 I/s | 4.53 S/W 111 W | 1.49 100 38 ++++++++++++
> GPU5 57C 70% | 506.7 Sol/s 504.7 Avg 270.0 I/s | 4.53 S/W 110 W | 1.94 100 38 ++++++++++
> GPU6 59C 70% | 514.5 Sol/s 506.3 Avg 270.4 I/s | 4.55 S/W 112 W | 2.36 100 38 ++++++
> GPU7 64C 75% | 511.1 Sol/s 515.1 Avg 275.2 I/s | 4.62 S/W 109 W | 1.12 100 37 ++++++++
> ============== | 4072.6 Sol/s 4063.3 Avg 2172.1 I/s | 4.55 S/W 891 W | 19.63 100 37 ++++++++++


Sol/s: solutions per second
Avg: average solutions per second
I/s: iterations per second done by the GPU
S/W: efficiency - average Sol/s per Watt
W: power consuption in Watt
last 3 colums: <shares per minute> <accepted shares ratio> <network latency in ms>


> : indicates that a new job was received
+ : indicates one submitted share
* : indicates one submitted dev fee share
= : sum/average if mining on multiple GPUs


Features:
To get help just start zm without any arguments

Code:

ZM 0.6.1, dstm's ZCASH/Equihash Cuda Miner

Usage:
zm --server hostname --port port_nr --user user_name
[--pass password] [options]...

zm --cfg-file[=path]

Stratum:
--server Stratum server hostname
prefix hostname with 'ssl://' for encrypted
connections - e.g. ssl://mypool.com
--port Stratum server port number
--user Username
--pass Worker password

Options:
--help Print this help
--list-devices List available cuda devices

--dev Space separated list of cuda devices to use.
If this option is not given all available devices
are used.

--time Enable output of timestamps
--color colorize the output

--logfile [=path] Append logs to the file named by 'path'
If 'path' is not given append to 'zm.log' in
current working directory.
--noreconnect Disable automatic reconnection on network errors.

--temp-target =dev_id:temp-target[,dev_id:temp-target] ...
In C - If set, enables temperature controller.
The workload of each GPU will be continuously
adjusted such that the temperature stays around
this value. It is recommended to set your fan speed
to a constant value when using this setting.
Example: --temp-target=0:65,2:70

--intensity =dev_id:intensity[,dev_id:intensity] ...
Reduce the load which is put on the GPU - valid
intensity range ]1.0-0.0[.
Example: --intensity=0:0.893,2:0.8

--telemetry [=ip:port]. Starts telemetry server. Telemetry data
can be accessed using a web browser(http) or by json-rpc.
If no arguments are given the server listens on
127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
Valid port range [1025-65535]

--cfg-file [=path] Use configuration file. All additional command
line options are ignored - configuration is done only
through configuration file. If 'path' is not given
use 'zm.cfg' in current working directory.

--pool =hostname,port_nr,user_name[,pass]
Setup additional failover pools.

Example:
zm --server servername.com --port 1234 --user username


BIG THANKS TO SWISSTRADER for providing access to hardware.


Dependencies
Linux:
openssl 1.0 (for versions <= 0.5.7)

Windows:
.Net 2.0+


Version 0.6.1
- fix failover-pool not switching back on ssl errors
- fix failover-pool not switching back on some servers
- add support for stratum's client.reconnect rpc
- support configuration of 'temp-target', 'intensity', 'pool' via cmd-line parameters
- report current difficulty and target on term-ui
- sort output by gpu_id on term-ui
- colorize temperature above 70°C on term-ui
- report intended fan speed on term-ui, web-ui, json-rpc
- report power consumption on term-ui
- improve performance on linux systems by ~2%


Version 0.6
- failover pool support
- introduce configuration file
- introduce intensity option
- support per gpu temp-target via cfg-file
- support per gpu intensity via cfg-file
- json-rpc report gpu_name, pci_bus_id, pci_device_id
gpu_uuid
- improve error reporting
- improve handling of invalid server resposes
- improve reconnection in cases where servers
become reachable but respond with malformed data
- ui: add colorized output
- web-ui: use dark colors


Version 0.5.8
con: add support for protocol v.01000020
link openssl statically


Version 0.5.7
reduce cpu load
minor performance improvements
con: use single pool connection
con: ssl: clear session data before reconnect
nvml: handle invalid values


Version 0.5.6
reduce cpu load
minor performance improvements


Version 0.5.5
con: handle failure of dev share pool
con: disable reconnect limit
logfile: disable buffering


Version 0.5.4
fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version


Version 0.5.3
cpu: reduce cpu load
con: fix recon loop
con: network latency measurement
ui: add accepted/rejected shares ratio
ui: add network latency
ui: add information about selected devices


Version 0.5.2
fix a race that might have corrupted shares
net: tcp: disable the Nagle algorithm
which reduces network latency in some circumstances
net: lower keepalive for nat-networks


Version 0.5.1
con: fix reconnection might have give up too early
con: enable TCP Keepalive to prevent nat-routers from
dropping the connection.
ui: output rejected shares
ui: optional output of timestamps
telemetry: make web ui mobile friendly + add share stats
telemetry: json: add more GPU stats


Version 0.5
con: support set_extranonce rpc
con: improve handling of temporary slow network conditions
con: add monitoring support using web browser
con: add monitoring support using json-rpc
mp: rebalance queue sizes - this improves the solution rate as
seen by the pools, especially on pools that submit new jobs often


Version 0.4.5
fix: bad miner performance when using --temp-target
on systems with many GPUs
reduce temperature controller cpu usage


Version 0.4.4
fix: Sol/W might have produced wrong values
fix: Sum not shown if --dev was used
fix: memory leak on reconnection
improve stability


Version 0.4.3
stratum: support more pools
ui: flush stdout stream
con: improve reconnections
performance improvements 0.3-0.5 %


Version 0.4.2
mp: more accurate time measurements
ui: calculate efficiency


Version 0.4.1
improve performance


Version 0.4.0
temperature controller added
cpu: reduce CPU usage
con: improve pool support
minor performance improvement


Version 0.3.2
mp: improve stability
con: support more pools
con: more robust reconnection support for unreliable
servers which often drop the connection
ui: report GPU temperature

Version 0.3.1
cpu: reduce CPU usage


Version 0.3
con: support encrypted connections


Version 0.2.2
con: Miner reconnects automatically on connection loss now,
e.g. on DSL-disconnects / public IP-changes
UI: report submitted devfee-shares


Version 0.2.1
Performance improvements:
- about 4% on Maxwell
- about 1% on Pascal


Version 0.2
- Improved pascal perfromance.
- Added support for concurrent mining on multiple GPUs.
- Be asynchronous where possible.
- Security work

NoDevFee - for Claymore`s Dual Ethereum and Phoenix miner

Version 1.0.0 Beta

Features of the program

autostart with Windows
Commission for software developers (Claymore dual miner and Phoenix miner) returns to your wallet
Simplicity in setting (You do not need to own any special features in order to customize the mining)
cons of the program supports only ETH

This is the first version of the program so there are possible bugs
Since we are still developing and we do not need much money from the commission, we take 25% of the miner’s wallet. So, you get a commission at the rate of 0.25% when you are mining with Claymore Dual miner. And when mining with a Phoenix miner 0.16%.
in the future monitor farm without white ip

Adding other Crypto-Currency
Adding other pools
Creating website
Improve stability and increase functionality

Suported pools

Ethermine org
Nanopool org
f2pool com
dwarfpool com
The program has an intuitive interface and no need to fill in the command line … Just select the pool, enter the wallet and the vendor. And the program will begin to mine for you.

Download link
Download NoDevFee - https://mega.nz/#!W6xgwQIb!1dmRHDzAX29Yip6jp5mdXtWJY-2pYuU_Q0C0q2ITtJ4

JCE Cryptonote CPU Miner

Welcome to the Fastest Cryptonote CPU Miner ever!

You can download it from the Mega page here:
https://mega.nz/#!KzgigCjK!g493xrvqbimEwnAN3uxatVhD8MEku8zXwMyCW7pI7Fw

Is that a Virus? No!

Like all miners, JCE gets detected as a virus by most Antiviruses, including Windows Defender. But it’s not. Read more about Privacy and Security below.

Is it just yet-another fork of a common miner? No!

You’re not losing your time testing a made-up rip of a common miner, JCE is brand new, using 100% new code.

Are the new Monero-V7, Cryptolight-V7, Cryptonight-Heavy, IPBC, Alloy, MKT and XTL forks supported? Yes!

The --variation parameter let you choose the fork. More details below.

Speed

In short, JCE is:

Crazy fast on non-AES 64-bits, usually 35-40% faster than other miners
Compared to other 32-bits miners, still faster on non-AES 32-bits, sometimes beating even the other miners 64-bits versions
And still faster on non-AES 32-bits Cryptonight-Heavy, with usually +50% speed.
Barely faster than the other best on AES 64-bits, beating them by ~1%, +2.8% on V7 fork, +4% on Cryptonight-Heavy
Also a lot faster on AES 32-bits, but it’s a rare case (mostly seen on Intel Atom tablets)
Here’s a benchmark against three other common miners.
The test is fair : run on the exact same Win10 Pro computer, all Huge Pages enabled, no background task, best configuration.

XMRStak means: the released Unified binary from github (not recompiled myself)
XMRig means: the respective best released binary gcc (32-bits) and msvc (64-bits) from github (not recompiled myself)
Claymore means: best Claymore CPU (3.4 for 32-bits, 3.9 for 64-bits)
When not supported, score is zero, if not tested yet, score is ?
Fees are included in the score
Core2 Quad 2.666 GHz 12M, 4 threads, 64-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
116   80   85   57
Core2 Quad 2.666 GHz 12M, 4 threads, 32-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
93   0   68   50
Ryzen 1600, 8 threads, 64-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
506   502   502   443
Ryzen 1600, 8 threads, 32-bits, Cryptonight

JCE   XMRStak   XMRig   Claymore
434   0   327   275
Ryzen 1600, 8 threads, 64-bits, Cryptonight V7

JCE   XMRStak   XMRig   Claymore
503   492   491   ?
Ryzen 1600, 8 threads, 32-bits, Cryptonight V7

JCE   XMRStak   XMRig   Claymore
424   0   320   ?
Core2 Quad 2.666 GHz 12M, 4 threads, 64-bits, Cryptonight Heavy

JCE   XMRStak   XMRig   Claymore
50   33   36   0
Ryzen 1600, 4 threads, 64-bits, Cryptonight Heavy

JCE   XMRStak   XMRig   Claymore
252   169   250   0
Ryzen 1600, 4 threads, 32-bits, Cryptonight Heavy

JCE   XMRStak   XMRig   Claymore
191   0   174   0
Getting started

If you’re new at mining Cryptonight, here’s the simplest way:

Choose the coin to mine, see the list below. The most common is Monero.
Get a wallet, that’s a ~95 character long identifier. If you don’t have one yet, you can create it
Choose a pool to mine on, and its port. For example Pool pool minexmr com and port 4444
Edit the start.bat that’s shipped in the .zip
Change the example POOL by yours
Change the example PORT by yours
Change the example WALLET by yours
You can leave the default password x
(Optional) If your coin is exotic, maybe you also need to change FORK=0 to another number. See the list in the start bat
Run start bat
Basic topics

Q. Is it free (as in beer, as in freedom)?
No and no. It has fees, and is not open source. But the program itself is free to distribute.

Q. How much cost the fees?
Current fees are:

3.0% when using at least one mining thread with non-AES architecture, or 32-bits
1.5% when using only 64-bits AES architecture
The fees are twice higher in non-AES mode and/or 32-bits because JCE offers a huge performance gain here.

Q. Can I avoid fees?
Not really. I plan to offer a paying per-licence-no-fee (pay-once-for-all) version, but it’s a lot more complicated to set up than a fee-based miner.
Also, JCE never takes any fee during the first minute, so if you run it, and kill it after one minute, and repeat again and again, then you’ll never pay any fee, but JCE takes a few seconds to start, and your Pool probably won’t let your reconnect continuously.

Q. Will it work on my computer?
Minimum is Windows Vista 32-bits, or Linux, with a SSE2 capable CPU. 64-bits is faster, prefer it.
For best performance, Large Pages must be enabled, JCE will try to auto-configure them, but it may work or not depending on your Windows version and security configuration.

Q. What currency can I mine? On which pools?
You can mine any coin on any pool.
If your coin is listed, all is automatic.
Run the miner with --coins parameter to get the up-to-date list. Current list is:

Monero (XMR)
Monero-V (XMV)
Electroneum (ETN)
Karbowanec (KRB)
Bytecoin (BCN)
Sumokoin (SUMO)
Bitcoal (COAL)
Bitcedi (BXC)
Dinastycoin (DCY)
Leviarcoin (XLC)
Fonero (FNO)
Turtlecoin (TRTL)
Graft (GRFT)
Dero (DERO)
Stellite (XTL)
UltraNote (XUN)
Intense (INTS)
Crepcoin (CREP)
Pluracoin (PLURA)
Haven (XHV)
FreelaBit (FBF)
BlueberriesCoin (BBC)
B2BCoin (B2B)
Bitsum (BSM)
Masari (MSR)
SuperiorCoin (SUP)
EDollar (EDL)
Interplanetary Broadcast (IPBC)
Alloy (XAO)
BBSCoin (BBS)
BitcoiNote (BTCN)
Elya (ELYA)
Iridium (IRD)
Italo (ITA)
Lines (LNS)
Niobio (NBR)
Ombre (OMB)
Solace (SOL)
Triton (TRIT)
Truckcoin (TRKC)
Qwertycoin (QWC)
Loki (LOK)
Ravencoin(RVN)
Gadcoin (GAD)
MarketCash (MKT)
ArtoCash (RTO)
Nicehash Cryptonight v7
Minergate Cryptonight v7
MiningPoolHub Cryptonight v7
MiningRigRentals Cryptonight v7
Suprnova Cryptonight v7
Otherwise, if your coin is not listed, or your wallet not recognized, use the --any parameter, plus the --variation N parameter, with N the fork number, see list below. The fork detection is automatic on known coins, but manual on unknown coins. The coin list is periodically updated.

Q. Is Nicehash supported?
Yes, see list above. The Nicehash-specific Nonce is then automatically enabled.

Q. Is SSL supported?
Yes, with parameter --ssl

Q. I get only bad shares, what happens?
Your coin has probably forked. Add --variation N parameter, with N as listed below, until you find the one that works.

Q. What if my wallet is not recognized, or as a different coin?
Some coins use a wallet syntax so close that they’re hard to differenciate, like Lines and Loki. If JCE fails to detect the coin, force it with --any --variation N (with N as listed below) and let the miner run. It will still display the wrong coin but mine the good one. And of course proof-check pool side that you correctly get the shares.

Q. Is there a HTTP server to monitor the miner?
Modern pools provide all you need to monitor your miners (average hashrate, worker-id…). Monitoring is now a pool’s job. Still, a minimal HTTP Json server is available with parameter --mport P (P the port number) to ease integration of JCE into mining tools, but not intended for human reading. Forager was the first tool to integrate JCE, take a look!
For more compatibility, with extra parameter --stakjson, the JSON will be in XMR-Stak format.

Advanced topics

Q. Are there requirements or dependencies?
No. JCE is just a big standalone executable.

Q. Is there a Linux version?
Yes, starting from version 0.29

Q. Is there a GPU version?
Not yet.

Q. Is there a 32-bits version?
Yes, both 32 and 64 are always in the same release, for both Linux and Windows.

Q. How many threads can I setup?
Maximum is 64 threads on 64 CPUs.

Q. Do I get a discount on fees if I use SSL?
I’m not Claymore.

Q. What is that value logged when I find a share?
The amount of hashes your pool will credit you. This is not the amount of crypto-coins.

Q. How is developed JCE?
The network and stratum handling is C++14, and the mining algos are assembly (to be precise, GNU Extended Assembly). Hence the speed increase.

Q. Can I plug it to a stratum proxy?
No, it must mine on a real pool on Internet.

Q. Is it really new? It looks familiar to me…
Yes it is. But it reuses, on purpose, some de-facto conventions from other common miners, like a XMRStak-style cpu configuration, and the colors of Claymore (green=share, red=error, blue=hashrate, yellow=status).

Q. How is the hashrate calculated?
That’s the average speed of the last 512 hashes (not shares found, computed hashes), rounded at 0.01. And it’s fair, the displayed number has no tweak, and includes the fees. The total is first summed from exact per-thread values, then rounded (said differently, it’s a rounded sum, not sum of rounded).

Q. Can I get a long-time speed average?
Better look at your pool’s reports, but JCE also gives the average effective net hashrate when pressing R. It’s usually slightly lower than the physical hashrate because of outdated shares and fees.

Q. Can I do multi-pool auto-switch in case of failure? Or periodically?
Not directly, but the -q and/or the --autoclose parameters, with the help of a simple .bat, can do the job. The .zip comes with an example, open and edit it to match your needs.

Q. What if the Architecture codename is wrong (e.g. my CoffeLake is detected as Core2)?
It may be because of an option in your BIOS Max CPUID or the microcode is not up-to-date. However the codename displayed is mostly cosmetical and JCE will still choose the good assembly based on your CPU instruction set. If a normally available instruction set is missing (e.g. your Westmere has no AES) again, that’s to be unlocked in your BIOS.

Q. Can I mix architectures when mining (i.e. thread 1 uses core2, thread 2 uses pentium4)?
It sounds strange, but yes. However, that’s mostly useful for tests.

Q. Can I mix coins when mining (i.e. thread 1 mines XMR, thread 2 mines ETN)?
No.

Q. Can I mix simple-hash and multi-hash?
Yes, and it’s a very common case when mining TurtleCoin or IPBC.

Q. What is “use_cache”:false useful for?
The no-cache mode means the cache is mostly bypassed, depending on your hardware. When using a lot of cache but few cores (typically when mining Cryptonight-Heavy) assigning unused physical cores to no-cache mining can give you a few extra h/s for free. However mixing cache and no-cache of logical CPUs of the same physical core causes terrible performance.

Q. What a great job! Can I make a donation?
Thanks bro. You can, with the --donate parameter which raise the fees to 80%, or by sending coins to the donation wallet (the one in the start.bat file included).

MinerMonitoring.com - Crypto mining rig monitoring software for Linux and Windows


Notifications

-- GPU temperature gets higher than required
-- GPU temperature gets lower than required
-- (AntMiner) Chip temperature gets higher than required
-- (AntMiner) Chip temperature gets lower than required
-- Miner is not responding for X amount of minutes
-- GPU Fan speed is lower than X
-- GPU Fan speed is higher than X
-- Miner hashrate too low
-- GPU hashrate too low
-- Notification when miner comes back online

Download: https://mega.nz/#!a3gFXJYZ!wBNF9dCSPkVr-LcvspSMp1YTN64Ea_ZXNKkYB9Xqrww

Supported software

- CCMiner-Alexis 1.0
- CCMiner Palgin skunk mod
- CCMiner SP Skunk mods
- CCMiner >= 2.0
- T-Rex Miner
- LolMiner
- CryptoDredge
- EWBF Support
- XMR-Stak
- SGMiner
- dstm ZM
- EthMiner
- BMiner
- CastXMR
- SKMiner
- EnemyMiner
- PhoenixMiner
- Excavator by NiceHash (1.4, 1.5)
- Claymore's Dual Miner support
- ASIC AntMiner support
- Supports miners without API (Stats-Only mode, reports GPU stats)

Web service

- Profit monitoring
- Pool 24h revenue tracking
- Dailiy profit graph
- Wallet monitoring service
- Coincalculator.io profit calculation based on current hashrate and power
- Hashrate graph
- Share monitoring / graph
- Temp graph
- Power usage graph


EthControl v0.0.20 build 1025 (Windows)

- Fan curve support
- Supports CCMiner auto-restart when CPU does not validate.
- Supports EWBF auto-restart when cuda device thread exited.
- Bulk updates for remote configuration / install.
- Ethminer full monitoring with GPU hashrate, GPU temp and GPU fan speeds.
- Remote rig reboot support.
- Remote stop/start support for mining software.
- Web console for remote diagnostics
- Automatic miner software installation support and updates
- GPU monitoring.
- Afterburner profile loading
- Custom OC profiles for AMD / nVidia cards
- Custom OC settings
- OhGod pill support with automatic loading
- Starts with windows automatically
- Crash reports
- CCMiner "invalidate cpu" error auto-restart
- Easily deploy custom ccminer forks, claymore updates, custom software to multiple rigs


EthMonitoring v1.0.1 (Windows)

- Supports multiple miners monitoring from one PC (Only monitoring no control)
- Supports local rig monitoring with stats-only mode (no control)
- Supports SGMiner/CGminer pool management (AntMiners)


Wallet Monitoring

- Daily balance graph
- Monitoring multiple coins from Cryptopia, Luno, Nicehash or by explorer
- Transactions history in apps and web
- Notifications for incoming/outgoing transactions
- Masternode tracking support


Rig rebooter

- Automatic rig rebooting when offline detected
- Manual start/stop, reboot from app and web


API support
- Remote config change
- Stats retrieving

Custom colors
- We support custom colors for hashrate, fan speed and temperature for easier tracking

Compact view
- Complete overview for TV screens
- Automatic scrolling
- Scroll to offline/notified rig
- Sound alarms
- Custom colors

Downloads
https://mega.nz/#!b2QTWIRL!pClPcoXr9fVh9iHgFZQ3nbakahYirbuU144KbikpSg8

Overview
CryptoDredge is a simple in use and highly optimized cryptocurrency mining software. It takes full advantage of modern NVIDIA graphics cards through the use of unique optimization techniques. We have also devoted great attention to stable power consumption. These benefits, along with the very small developer fee, make our product one of the best publicly available miners.

Features
Developer fee is 1%

Supported AlgorithmsAllium

Blake (2s)
Lyra2REv2
Lyra2z
NeoScrypt
PHI1612
Phi2
Skein
Skunkhash
Tribus

QuickStart
The current version of CryptoDredge is a (portable) console application. Unpack the downloaded archive and edit one of the sample .bat/.sh files or provide the necessary command line arguments.

Example:
Code:
CryptoDredge -a <ALGO> -o stratum + tcp :// <POOL> -u <WALLET_ADDRESS> -p <OPTIONS>

Command-Line Arguments
-v, --version Print version information
-a, --algo Specify algorithm to use
allium
blake2s
lyra2v2
lyra2v2-old (see the Lyra2REv2 Issues item)
lyra2z
neoscrypt
phi
phi2
skein
skunk
tribus
-d, --device List of comma-separated device IDs to use for mining. IDs are numbered 0,1...,N - 1
-h, --help Print help information
-i, --intensity Mining intensity (0 - 6) (default: 6)
-o, --url URL of mining pool
-p, --pass Password/Options for mining pool
-u, --user Username for mining pool
--log Log output to file
--no-color Force color off
--no-watchdog Force watchdog off
--cpu-priority Set process priority in the range 0 (low) to 5 (high) (default: 3)
--api-type Specify API type to use (default: ccminer-tcp)
ccminer-tcp (TCP)
ccminer-ws (WebSocket)
off
-b, --api-bind IP:port for the miner API, 0 disabled (default: 127.0.0.1:4068)
-r, --retries N number of times to retry if a network call fails, 0 retry indefinitely (default: 0)
-R, --retry-pause N time to pause between retries, in seconds (default: 15)
--timeout N network timeout, in seconds (default: 30)

System Requirements NVIDIA GPUs with Compute Capability 5.0 or above

Latest GeForce driver
2 GB RAM (4 GB recommended). Some algorithms such as NeoScrypt require the virtual memory (swap file) with the same size as all of the GPU's memory.
Internet connection

Windows
Windows 7/8.1/10 (64-bit versions)
Visual C++ Redistributable for Visual Studio 2015


Troubleshooting

Antivirus Software Reports
CryptoDredge is not a piece of malicious software. You may try to add an exception in antivirus software you use.

Rejected Shares

There are many reasons for rejected shares. The primary reasons are:
high network latency
overloaded mining server
aggresive graphics card overclocking

Watchdog
If you are using a third-party watchdog, you can disable the built-in watchdog by using --no-watchdog option.
Example:
Code:
CryptoDredge -a <ALGO> -o stratum + tcp :// <POOL> -u <WALLET_ADDRESS> --no-watchdog

Lyra2REv2 Issues
In case if you have issues with the current implementation of Lyra2REv2 (lyra2v2), you might want to try lyra2v2-old.
Example:
Code:
CryptoDredge -a lyra2v2-old -o stratum + tcp :// <POOL> -u <WALLET_ADDRESS>

Several Instances After a While
It seems that you are using an own restart mechanism of CryptoDredge (see the Watchdog item).