Zealot/Enemy (z-enemy) NVIDIA GPU miner.x16r, x16s, Bitcore, Phi1612, Xevan ,Tribus , x17, c11, AeriumX, XDNA(hex), phi, phi2, skunk etc ..=========================================================Z-ENEMY 2.00 From: Dk & Enemy (z-enemy) NEWThis version includes a new way to manage and monitor the miner.New features:- Added new HTTP JSON API (see json_api_help.txt for the details), available at port 4067 by default- Added web control panel with real-time monitoring and charts. The UI is responsive and should be looking well on most mobile phones and tablets.Other changes:- The miner informs about API servers (both Telnet and HTTP) being started- You can now disable both servers with --api-bind=0 and --api-bind-http=0 respectively- Minor bugfixes and stability improvementsNotes:- For HTTP server --api-allow command line option isn't having any effect (for now?)Windows:Cuda: 10.0; 9.2; 9.1 - https://mega.nz/#F!zZUHWShC!Z7WVzMeFhKIm2CNakx1_8wLinux:Cuda 10.0: https://mega.nz/#!UCQlSaJI!j_b7REMSVkp5SRDQP2PjaaEpcA7tYuwxJZGj0GJFoqsCuda 9.2: https://mega.nz/#!5bAxlSAI!3y5fu0uLjYz51gNNPeiz2959IrHgiyQlVJTobVk4aXA_______________________________________________________________________________ _________Z-ENEMY 1.28 From: Dk & Enemy (z-enemy) IMPORTANT:For maximum performance make sure you have latest drivers (ver. 415+)Performance improvements of 1.28 compared to previous version (1.27):- Bitcoin Diamond +7-8%, Hex 4-5% and +3-5% for x16r/s, x17, bitcore, c11, sonoa, etc...Other changes:- Added --no-nvml switch to disable NVML monitoring (useful to reduce load on low end CPUs)- After several tests we recommend using intensity 22 on 1080ti cards on x16r algo (and perhaps others)Z-ENEMY 1.27 From: Dk & Enemy (z-enemy) Performance improvements:Up to +3-4% for x16r/s and hex, +6-8% Bitcoin Diamond, 1-3% on others (x17, bitcore, c11, sonoa, etc...) on GTX 10x0 cardsZ-ENEMY 1.26 ver.1 From: Dk & Enemy (z-enemy) IMPORTANT:For maximum performance make sure you have latest drivers (ver. 415+)Performance improvements:- Up to +5-7% x16r/s, +7% bitcore, few percent on others (x17, c11, aergo ...) on GTX 10x0 cards.- Hex algo +10% for GTX 10x0 cards and +2% for RTX 20x0 cards.Other changes:- Removed renesis algo- Improved stability_______________________________________________________________________Z-ENEMY 1.25 ver.1 From: Dk & Enemy (z-enemy) IMPORTANT:For maximum performance make sure you have latest drivers (ver. 415+)Performance improvements in x16, x17, c11, bitcore, BCD, aergo, sonoa and hex:- +10% or more for RTX 2080/2080ti/2070 cards- +3-7% for GTX 1080Ti/1080/1070ti and lower cardsBugfixes:- Reduced CPU usage._______________________________________________________________________________ __________Z-ENEMY 1.24 ver.3 From: Dk & Enemy (z-enemy) IMPORTANT:For maximum performance make sure you have latest drivers (ver. 415+)- Major optimizations for skunk, polytimos and phi- Minor optimizations for hex and x16r/s, tribus.- Massive performance boost for RTX 2080/2080ti/2070 in many algorithms.Other: - Highlighted hardware stats reporting, colored GPU temperatures (green/yellow/red)- Added Volta architecture support- Important update(1.24 ver.2): Fixed multi-gpu crash bug (skunk and polytimos)- Important update(1.24 ver.3): Fixed reduced poolside hashrate ( XDNA : hex algo)Z-ENEMY VER 1.23 From: Dk & Enemy (z-enemy) IMPORTANT:For maximum performance make sure you have latest drivers (ver. 415+)- First wave of performance optimizations for RTX 2080 and 2080Ti series up to 10-20% in various algos x16,x17,c11,hex,bitcore,xevan...)- Minor performance optimizations for older cards (10x0)- Fixed tribus out of memory bug (now it's possible to run it with higher intensities)- Removed --tlimit and --plimit options- Added --max-temp --resume-temp options- Experimental CUDA 10 support: Higher speeds and stability, support for new RTX2080 & 2080 Ti cards- Performance improvements: 2-5% for most algos (Hex, X16, X17, Bitcore, C11, etc..)Cuda 10 version 32 & 64 performs faster in most algos ... Update you Nvidia drivers - minimum (ver. 415+)Important. This is the first basic build for Cuda 10, please leave feedback in our channel #z-enemy-122testZ-ENEMY VER 1.21a From: Dk & Enemy (z-enemy)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)- Performance and stability improvements, few bugs fixed.- Added uptime reporting.Same as with previous release, 32 bit version performs faster in some algos ...Z-ENEMY VER 1.20 (PUBLIC) From: Dk & Enemy (z-enemy)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)- Major performance improvements: 5-10% in various algos- Bitcoin Diamond: Support for the new famous top algorithm at high speed, 20-30% higher than the current ones.Same as with previous release, 32 bit version performs faster in some algos (x16/x17 etc) ...Enjoy Z-ENEMY VER 1.19 (PUBLIC) From: Dk & Enemy (z-enemy)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)- Major performance improvements: 5-7% in various algos (x16 ,x17 , bitcore, c11 , hex , etc ..)- Stability improvements32-bit version seems to be faster in some algos again, feel free to test it !Z-ENEMY VER 1.18 (PUBLIC) From: Dk & Enemy (z-enemy)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)Greetings! We're releasing an updated version of our mining software with some bugfixes and other changes:- Major performance improvements: 10-15% for Xevan (+ fixed reduced hashrate issue from 1.17)- Minor performance improvements for other algos- Stability improvements for XDNAZ-ENEMY VER 1.17 (PUBLIC) From: Dk & Enemy (z-enemy)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)Greetings, fellow miners! We're releasing an updated version of our mining software with some speed inside:- Major performance improvements: 5-10% for X16R & X16S, XDNA (hex), x17, Bitcore(BTX), c11, Sonoa, Renesis, Aergo- Lower end cards like 1050/1060 will see additional few % (yes, a bonus)- The miner no longer depends on memory, it allows to run memory clock at +0 or -500 MHz without performance loss.Happy mining!================================Z-ENEMY VER 1.16 (PUBLIC)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)zealot/enemy-1.16 (z-enemy) From: Dk & Enemy- Performance improvements:+7-10% hex(XDNA),+5%-7% x16r&s, few % for other algos (x17, c11, sonoa, renesis, aergo)- Experimental feature: intensity limit increased (most algos now allow intensity up to 25, test at your own risk)Z-ENEMY VER 1.12a (PUBLIC)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)For Windows Cuda 9.2 :zealot/enemy-1.12a (z-enemy) From: Dk & Enemy- Improved phi2 performance: +4-5% (up to 5 Mh/s for 1070ti, up to 7.5 Mh/s for 1080ti)- Minor performance improvements for other algosLAST Z-ENEMY VER 1.12 (PUBLIC)IMPORTANT:For maximum performance make sure you have latest drivers (ver. 398+)zealot/enemy-1.12 (z-enemy) From: Dk & Enemy- Minor performance improvements: x17 , x16r, x16s, c11 , bitcore, aeriumx and other ...- New algos: SONOA ( -a sonoa) and PHI2 ( -a phi2)Z-ENEMY VER 1.11 (PUBLIC)For Windows (Cuda 9.1)zealot/enemy-1.11 (z-enemy) From: Dk & Enemy- Performance improvements: x17 (+4-8%), x16r&s (+1-3%) , very fast Phi1612 and other ...- Fast start on multi gpu-rigs- GPUs limit increased to 24- AeriumX(AEX) - the miner supports Aerium new swap algo (-a aeriumx), starting 4th June.- Added: C11(-a c11) basic and fast x64(ver.4) , Skunk(-a skunk) basic , improved TimeTravel8(-a timetravel) and Polytimos (-a poly)Z-ENEMY VER 1.10 (PUBLIC)For Windows (Cuda 9.1)zealot/enemy-1.10 (z-enemy) From: Dk & Enemy- Fixed compatibility issues that resulted in performance degradation with some non-yiimp pools. Now you'll see the expected hashrate on them (suprnova).- Kernels speed improvements : (1.09a vs 1.10) +1-2% total (all algos) and (1.09b vs 1.10) +1-2% for x16r &x16s.- Support & impove new algo : Tribus (-a tribus) , recommended intensity for Tribus 20-21. +5% speed vs 1.09b ( Service release)First time or troubleshooting x16:- First time users - ver. 1.12 works on Cuda 9.1&9.2 and it is recommended to make sure you've updated your NVIDIA drivers. You can find drivers here ver., 398+++- Next important thing is intensity. We recommend intensity -19 at first, however if your PC has 8GB or more, fast SSD, and big swap file on it you may use -20/21.- X16r algo is very wild and eratic. *Very important* Make sure to have enough power reserve on PSU. Please be sure you have a minimum 20% headroom on your PSU or set your PL on 70-80% usage.- Using +core and +mem is useful but, use no OC at first until you verify stability. Performance and fine tuning x16: - This release z-enemy 1.12 is reported to be more stable when it using higher PL (90-110%) and +core and +memory overclocking, feel free to experiment with it.- Updating drivers can provide more gains- Recommended intensity is 20, set 21 only if you know what you are doing. ( 16GB RAM or/and good SWAP file on SSD) Use caution- Recommended memory 0 or +- Recommended core +50+150 ( 1800-1900MHz 1080 Ti)- Overclock slowly and allow plenty of time to verify stability (12-24hrs) before making anymore adjustments. x16r is a very chaotic algorithm so just because it works for 1 hr doesn't mean you can't crash over longer time. Sometimes hash order can lead to 2000+mhz and crash system. Keep in mind – overclocking is always at your own risk!- Yiimp pools recommend manual diff (-p d=16) - for small farms or (-p d=48 ) - for good farms like 5-6 1080 Ti If you need to name your rigs as well as set diff you may try -p rigname,d=16Diff x16 can be calculated by mutliplying the following:Number of 1060's multiplied by 3-4Number of 70ti's or 80's multiply by 4-8Number of 80ti's multiply by 6-12example: If you have 3 1060's then diff would be 9-12if you have 8 70ti's then your diff would be 48-96Dev fee:- low dev fee 1% - Dev fee will start randomly when miner is first started. After 1% of time mined then automatically switches back to user pool.Information about x16: Every block contain 16 random algos.All algos have Fast, Medium and Slow speeds so depending on the order and what speeds they are will determine your hashrate at any given time.Fast: Blake (Blk),Bmw512(Bmw), Keccak (Kck), Skein(Ske), Shabal(Shb), Sha512(Sha)Medium: Jh512 (Jh5), Luffa (Luf), Cube(Cub), Shavite (Shv), Fugue (Fug), Whirlpool (Wrl)Slow: Groestl (Gro), Simd (Smd), Echo (Ech), Hamsi (Ham)Example:Block 181085, difficulty 20228.532 Hashorder: EchFugBmwShaJh5FugShvEchSmdBmwHamWrlJh5KckSkeHamMeans first algo is Slow Echo (Ech)> next Medium Fugue (Fug) > …> last Hamsi (Ham). The more fast algos in a block is what drives miner speed to the moon! (more MH)Samples:Yiimp pools:z-enemy -a phi -o stratum+tcp ://pool bsod pw:6667 -u LQCifDiNVXjM_your_wallet_CUqZJBa75p11 -p xz-enemy -a x16r -o stratum+tcp ://yiimp eu:3636 -u RWgpF9GefjD_your_wallet_1gQmQjpYtYt.GTX950 -p d=3 -i 19z-enemy -a bitcore -o stratum+tcp://yiimp eu:3556 -u 1D2dKSprpK_your_wallet_1wa8b2LnJ826uf -p x -i 20Suprnova pool:z-enemy -a x16r -o stratum+tcp //rvn suprnova cc:6667 -u your_Login.your_worker_name -p x -i 20FAQ:I cannot start miner, it says I'm missing msvcr120.dll?Download and reinstall drivers from http://www.nvidia.com/Download/index.aspxMy miner crashed - cuda error in funk `cuda_check_cpu_setTarget` why ?This error is caused by overclocking, lower your GPU and VRAM clocks.Latest drivers recommended?Yes however, sometimes a new driver can cause an issue and using a previous version may work better. You will need to verify. We recommend at least NVIDIA drivers of 390+++ or 398.xxWhat is restart-fix.reg in windows download folder?This file will fix pop-up window and lets the miner restart after crash. Run once.How many GPU's can I run?We have confirmed reports on 19 cardsIs there an easy way to auto restart miner if it crashes? Yes, check our samples *.cmd file in windows build. Like::startz-enemy -a phi -o stratum+tcp://pool bsod pw:6667 -u LQCifDiNV_YOUR_WALLET_F3CUqZJBa75123 -p xgoto startDoes z-enemy 1.12 not support api?Yes, try --api-remote and/or --api-allow= ( simple 0/0 )z-enemy no supports ccminer.conf default value loading from .conf file ?z-enemy support config.json
T-Rex miner for modern NVIDIA GPUs - Maxwell and newerSupported algorithms:x16rx16rtmtpx16sx17x22ix25xx21sgeekdedalbcdhmq1725honeycombsha256tsha256qtimetravellyra2zbitcoresonoarenesisballoonpolytimosskunkc11phitribusGLT algos: astralhash, jeonghash, padihash, pawelhashRuns on both Linux and Windows.DownloadsWin: https://mega.nz/#!zAcXGapA!tZKGGHleTQy1selQuSbvYA9lzeXBs6DBrfwivjP705wLinux: https://mega.nz/#F!7UM12Iga!WqFyRsaRWjP2_CChGLzhrAUsageT-Rex supports command line arguments similar to that of ccminer:x16r:Code:t-rex -a x16r -o stratum+tcp://eu.minermore.com:4501 -u <wallet> -p xMTP:Code:t-rex -a mtp -o stratum+tcp://xzc.2miners.com:8080 -u <wallet> -p xTo get the full list of supported options run:Code:t-rex -hDev feeDev fee is set to 1%. When the miner starts and stops mining dev fee it reports it to the console output.Release notes0.12.0Add honeycomb algorithm (Beenode coin)Fix "GPU ... is idle" error when there is a pool connection problem0.11.1Significant x25x speed increaseNew features:Use environment variables in config files. Use %YOUR_ENV_VAR% in any config file field and it will substitute it with the value of YOUR_ENV_VAR environment variable set in your systemBug fixes:Temperature limit bug (GPU got disabled if there was problems with NVML)P2pool fixShow NVML errors and unsupported featuresTruncate MTP share log message when using --protocol-dumpFix start-up failure in some cases for CUDA 9.1 builds0.11.0Add x25x algo (will be used by SUQA/SIN after the fork)Bug fixes (built-in watchdog):Miner fails to start when using Windows task scheduler or Awesome MinerMiner restarts on Linux/Hive OSPreserve a single log file across miner restartsNOTE: Using built-in watchdog is encouraged. If you experience any issues with it, please let us know0.10.2Add MTP algo (Zcoin)Add Tesla P100 supportAdd built-in watchdog (can be disabled using --no-watchdog parameter)Default network timeout increased from 3 to 5 minutesNew parameter --hide-date to hide date part of the timestamp in the consolePrevent Windows from going to sleep mode while T-Rex is runningBug fixes:"does not validate on CPU" error on RTX cards (CUDA 10 builds)Long dev fee sessions if system clock "jumps"GPUs keep hashing even if the pool connection is lost0.9.2Add support for GIN (x16rt)Cosmetic changes:1) New parameter --ab-indexing to enable Afterburner-like GPU indexing2) Web-monitoring page enhancementsBug fixes:CentOS 7 compatibility issue0.9.1Add algos: x16rt (Veil), sha256q (Pyrite)Minor performance improvements for x16r, bcd, x22i and other x16-like algorithmsMultiple web monitoring page improvements* Switch between multiple config files dynamically (put your *.config files into the miner directory)* Dark themeBug fixes:cURL/SSL compatibility issue on newer Linux distros (Ubuntu 18, Debian 9)Miner wouldn't start if NVML wasn't installed0.8.9Performance improvements: +2-3% for x16 family of algorithms (x16r, bcd, x17, x22i etc.)Add config parameter: --no-nvml - Disable NVML GPU stats.Display miner version next to "Uptime" info.0.8.8Fix "result for ... does not validate on CPU!" errors on x21s and dedal0.8.6Add algos: astralhash, jeonghash, padihash, pawelhash (used by GlobalToken, can be mined atPerformance improvements: a few percent to x16r family of algorithms, skunk, x22iHighlight GPU temperatures in green/yellow/red. Temperature ranges are configured with --temperature-color parameterBug fixes:Invalid shares on Dedal for some hashordersNot identifying a found block when mining x22i0.8.5Performance improvements: x22i +5%0.8.4Performance improvements: x22i +1-4%0.8.3New algo: x21s (Ritocoin).New config parameter: --sharerate-avr - Sliding window length in seconds used to compute sharerate (default: 600).0.8.2New algo: dedalImprove x22i: +1-3%Fix skunk performance issue introduced in 0.8.10.8.1Performance improvements: x22i +10-20%Bug fixes:Miner hangs on start up when it doesn't receive authorize message response0.8.0New algo: geek (GeekCash coin)Performance improvements (1-3%) of x16-like algorithms for GTX/RTX cards.Added watchdog. Replace "t-rex.exe" with "watchdog.exe" in your bat file in order to use it.Watchdog lets you update T-Rex using the monitoring web page or perform auto-updates if launched with "--autoupdate" parameter, and also restarts the miner if it hangs for any reason.Default value for "-N" paramater increased from 30 to 60 seconds.Added "shares per minute" stats read-out.Bug fixes:"stratum+tcp://" pool URL prefix is no longer mandatoryReduce CPU load when using large "-N" parameter values"Clean jobs" feature removed in the previous release is backHung on Ctrl+C in Windows0.7.4Minor performance improvements for skunk and x16 family of algorithms for Pascal and Turing cardsBug fixes:Crashes 20 sec after dev fee session when using -r 0Temporary backed out "clean job" feature that was causing rejects on some pools e.g. beepool and bitpoolminingFix average hashrate reporting when using large -N values (over -N 4294)0.7.3Improve skunk, phi, polytimos; small improvements for x16r/s etc on some configurations.Performance improvements for Turing GPUs (20xx series)Add functionality to return to the main pool after mining on failover ones (see --back-to-main-pool-sec launch parameter)Handle client.reconnect stratum messages (used by MiningRigRentals)Handle clean jobs stratum flag correctly (resulting in fewer stale jobs) - this feature is supported by coinblockers.comAdd file handler to API. Allows to create custom files in miner directory via API.Add functionality to keep your failover pools separately in a config file. May be helpful if you need to load pools from file. (t-rex -c pools.json -a x16r <your parameters>)Bug fixesRemove assert on NULL rpath in Linux.Fix average hashrate reporting when using large -N values.0.7.2Added algo: x22iNote: if the miner crashes on x22i, decrease your overclock, the algorithm is quite "unstable"0.7.1Added algos: sha256t, timetravelReplace "--exit-on-fail-shares" parameter with "--reconnect-on-fail-shares"New/changed arguments:--temperature-start: When a GPU cools down to this temperature the miner starts using it again--exit-on-fail-shares: Now replaced with --reconnect-on-fail-shares-r (--retries): if set to 0, miner exits immediately upon the first network failure--cpu-priority: Set process priority (default: 2) 0 idle, 2 normal to 5 highestAllow C-style comments in config files (see config_example). Can be used to disable failover pools temporarily etc.A few cosmetic changes.API:Multiple http://localhost:4067/trex page enhancements, it now displays all the info you see in the console, including hashrate/power consumption on the graphs with zoom option. (click on left mouse button and drag) Don't need to use console anymore use your browser instead!New API handler "config".Some miner parameters can now be changed and saved on the fly.Please see the help file for additional details.Bug fixes:"bad weak ptr" errorShare rejects were not displayed (Suprnova, Aikapool, possibly some others)Command line arguments did not always override config file0.7.0Speed improvements: there's ~1% improvement in x16 family of algorithms on some configurations.Add support for Volta (Titan V) and Turing (20xx) cards - not optimised yet. Download CUDA 10 version to run on 20xx cards.New arguments:--temperature-limit: When a GPU reaches the temperature limit (in Celsius) the miner stops using it and keeps mining with the rest of GPUs--exit-on-fail-shares: Forces miner to immediately exit on N successively rejected shares (default: 10)Command line arguments now take precedence over config files. If an argument is set in both places, the value from cmd line overrides the config one.New HTTP API handler that allows you to control the miner via a web browser on the fly. By default is accessible at http://localhost:4067/trex. Functionality is limited but will be extended in future releases if there's demand. We're looking forward to getting your feedback.Bug fixes:Stability fixes, especially on x16r/s and bitcoreCUDA version reported by the miner is now the version that the miner has been built against rather than the one installed on user's machineRedirection of console output to stdout on Windows with no buffering in place.Cosmetic changes:Add miner efficiency (Hashes per Watt) to console output and APIPrint "Submitting found block!" message when a block is found and return this info in API0.6.10Speed improvements: x16r/s, x17, c11, bitcore, bcd, sonoa - 1-2%Add functionality for setting failover pools in cmd line by specifying -o, -u and -p arguments multiple times.New cmd line arguments:--gpu-report-interval: controls how often GPU report stats are displayed (by default every 5th share).--no-color: disable coloured output--time-limit: maximum time to mine before exiting the program.--quiet: disable GPU stats outputAdd ability to change averaging hashrate window, enable protocol dump mode, and change GPU report interval via API or web browser on the fly (without stopping the miner) - see the help file.Bug fixes:Hung/freeze issuesInvalid shares on x16rLong log path issue on Linux"extranonce subscribe timed out" on suprnova poolsCosmetic changes:Showing configured pools upon start upDisplaying colour representation of hashorders for x16r/sMiner uptime is displayed as part of GPU stats report0.6.6Speed improvements: bcd - 5%Cosmetic change: the miner will not show duplicate hashorder messages for x16r/s, bitcore, and they are no longer labeled as WARNTo disable API altogether set --api-bind-http / --api-bind-telnet to 0.HTTP API: new control command "shutdown" to quit the miner (read help file for details)0.6.5New algo: bcdSpeed improvements:x16r/s, bitcore, renesis, hmq1725 - 2-3%x17, c11, sonoa - 1-3%0.6.4New algo: hmq1725Improved x16r/s, x17, sonoa, c11, bitcore, renesis - 5-15% depending on algo and cardsBug fix: "hashrate-avr" parameter is ignored when using json config0.6.3New algos: balloon, polytimos, skunkImproved bitcore, c11, sonoa, x16r/s, x17 by a few percent. Renesis, phi - about 3-5%0.6.1New algos: bitcore, sonoa. Dropped phi2 support.Slight improvements (few %) of all algorithms except lyra2z.Added extra shares submit functionality. Reduced the number of rejects on pool side (both resulting in increased poolside hashrate).Fix for multiple scenarious where the miner used to freeze.Fix "doesn't validate on CPU" errors for phi/renesis algos.Display pool latency when submitting shares.Support decimal intensity values (e.g. 21.3)Highlight accepted/rejected shares using different colours (Windows version)Display GPU full name/temperature/power consumption/fan details.New command line option -P (stratum protocol dump).-N option now uses seconds rather than samples as a unit of measurement. E.g. -N 30 means a sliding window of 30 seconds is used to calculate average hashrate.Added support for Compute Capability 5.0 cards (e.g. 750, 750ti).HTTP API:Added GPU full name/temperature/power consumption/fan details.Added current pool details (name, difficulty etc)0.5.7Faster renesis, hsr, x16r, x16s, x17, c11. Few % improvement across all of them.0.5.6 (for those upgrading from 0.5.1)Added new algos: x16r, x16s, renesis.Faster hsr, x17.JSON API - return active pool informationAdded command line parameter "-N" - average hashrate display (number of samples in sliding window)Miner displays a notification in the console if the new version is availableBug fixes:Miner hanging on "Graceful shutdown"Config file - miner wouldn't start if no intensity specifiedTelnet API (ccminer compatible) - inconsistent newline characterHung issue (after "ApiServer: stopped listening" and connection loss)Immediate reconnect upon connection lossIncorrect initialisation when invalid command line argument supplied (now the miner won't start in that case)0.5.1Faster phi2, lyra2z, x17, c11.Added new algo HSR.Added API (HTTP JSON [preferable] and telnet ccminer compatible) - pending integration with monitoring software (ethmonitoring, awesome miner etc.)Multiple bug fixes, new config options, failover pools.0.4cAdded Phi2.JSON config file support. Multiple bugfixes.Miner source code is rewritten from scratch and no longer based on ccminer.0.3aFaster Lyra2z, Tribus and slightly faster Phi1612.Warning: If using Lyra2z in this version you will likely need to lower your overclock settings and probably also increase the power limit.0.2Added Lyra2z and Tribus.0.1Initial release. Phi1612 added.
(CUDA 9.1 version)(CUDA 9.2 version)(CUDA 10.0 version)
OverviewCryptoDredge 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.
DevfeeDeveloper fee is 1% (2% for MTP)
AlliumArgon2d (250/4096/DYN/NIM)BCDBitCoreCryptoLightV7 (Aeon)CryptoNightFastV2 (Masari and Stellite)CryptoNightGPUCryptoNightHavenCryptoNightHeavyCryptoNightSaber (Bittube)CryptoNightTurtleCryptoNightV8Cuckaroo29 (Grin)CuckooCycle (Aeternity)HMQ1725Lyra2REv3Lyra2vc0banLyra2zLyra2zz (LAPO)MTP (see the MTP Algorithm item)
QuickStartThe 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 useaeon
-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). For example: -i N[,N] (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--no-crashreport Force crash reporting 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)
-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, -1 retry indefinitely (default: -1)-R, --retry-pause N time to pause between retries, in seconds (default: 15)--timeout N network timeout, in seconds (default: 300)-c, --config JSON configuration file to use--no-nvml Force NVML off--hashrate Expected hashrate in kh/s (argon2d-nim only) (default: 100)System RequirementsNVIDIA GPUs with Compute Capability 5.0 or above.
MTP require graphics card with at least 5Gb memory.Latest GeForce driver2 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
WindowsWindows 7/8.1/10 (64-bit versions)Visual C++ Redistributable for Visual Studio 2015
LinuxUbuntu 14.04+, Debian 8+ (64-bit versions)Package libc-ares2. Installing libc-ares2 package is as easy as running the following command on terminal: apt-get install libc-ares2
NotesAntivirus Software ReportsCryptoDredge is not a piece of malicious software. You may try to add an exception in antivirus software you use.Rejected SharesThere are many reasons for rejected shares. The primary reasons are:high network latencyoverloaded mining serveraggressive graphics card overclocking
WatchdogIf 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
Several Instances After a WhileIt seems that you are using an own restart mechanism of CryptoDredge (see the Watchdog item).Crash ReportingIf the built-in watchdog is enabled then CryptoDredge will generate and send us the report. You can disable error reporting with --no-crashreport option. Allowing CryptoDredge to send us automatic reports helps us prioritize what to fix and improve in the future versions.Crash reports won't include any personal information about you, but they might include:Operating System versionDriver versionMiner configurationApplication crash data
MTP AlgorithmSystem Requirements:GPUs with at least 5 GB of memoryThere are no special CPU and RAM requirements, 4 GB must be sufficient
In comparison to other algorithms, MTP requires transferring large amounts of data to the pool. This may be a problem for limited and slow connections.The miner has to do some extra work every time that the pool sends a new "job", so an average hashrate will be a bit slow.Developer fee is 2% for MTP.Argon2d (NIM) AlgorithmIf you encounter many "invalid share: invalid pow" errors from the pool, set --hashrate option to calculate the start difficulty.
Miner T-Rex for the new NVIDIA GPU - Maxwell and newer.At the moment, is the top miner.
DownloadDownload T-Rex 0.9.1New algorithms / constantly updated.
Using:T-Rex supports command line arguments similar to ccminer arguments:
lyra2z:Code:t-rex -a lyra2z -o stratum + tcp: // pool.bsod.pw: 2159 -u -p x
tribus:Code:t-rex -a tribus -o stratum + tcp: // pool.bsod.pw: 2260 -u -p x
To get the full list of supported options:Code:t-rex -h
DevFee is 1%. When the miner shuts down or turns on the DevFee is displayed in the console.
0.9.1Add algos: x16rt (Veil), sha256q (Pyrite)Minor performance improvements for x16r, bcd, x22i and other x16-like algorithmsMultiple web monitoring page improvements
Switch between multiple config files dynamically (put your *.config files into the miner directory)Dark theme
Linux watchdog is now available.
Bug fixes:cURL/SSL compatibility issue on newer Linux distros (Ubuntu 18, Debian 9)Miner wouldn’t start if NVML wasn’t installed
0.8.9Performance improvements: +2-3% for x16 family of algorithms (x16r, bcd, x17, x22i etc.)Add config parameter: --no-nvml - Disable NVML GPU stats.Display miner version next to “Uptime” info.
0.8.8Fix “result for … does not validate on CPU!” errors on x21s and dedal
0.8.6Add algos: astralhash, jeonghash, padihash, pawelhash (used by GlobalToken, can be mined at https gltminer com/)Performance improvements: a few percent to x16r family of algorithms, skunk, x22iHighlight GPU temperatures in green/yellow/red. Temperature ranges are configured with --temperature-color parameter
Bug fixes:Invalid shares on Dedal for some hashordersNot identifying a found block when mining x22i
0.8.5Performance improvements: x22i +5%
0.8.4Performance improvements: x22i +1-4%
0.8.3New algo: x21s (Ritocoin).New config parameter: --sharerate-avr - Sliding window length in seconds used to compute sharerate (default: 600).
0.8.2New algorithm: dedalImproved x22i: + 1-3%Fixed skunk performance issue introduced in 0.8.1
0.8.1Performance improvements: x22i + 10-20%
Error correction:Miner freezes on startup when it does not receive a response to the message authorization.
0.8.0New algo: geek (GeekCash coin)Performance improvements (1-3%) x16-like algorithms for GTX / RTX cards.Added watchdog timer. Replace “t-rex.exe” with “watchdog.exe” in your bat file to use it.Watchdog allows you to update T-Rex using a monitoring web page or perform automatic updates if it is started with the “–autoupdate” parameter, and also restarts the miner if it hangs for any reason.The default value for the “-N” parameter increased from 30 to 60 seconds.Added share per minute statistics.
Error correction:“Stratum + tcp: //” pool U RL prefix is no longer requiredReduce processor load when using large “-N” valuesThe “Clear Tasks” feature removed in the previous release is backHung Ctrl + C in Windows
JCE Cryptonote CPU Miner
Welcome to the Fastest Cryptonote CPU Miner ever!
You can download it from the page or directly here: Download JCE_Miner
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-V, Cryptolight-V7 and Cryptonight-Heavy forks supported? Yes!
The --variation parameter let you choose the fork. More details below.
In short, JCE is:
Crazy fast on non-AES 64-bits, usually 35-40% faster than other miners
Still faster on non-AES 32-bits, usually 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
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, 4 threads, 64-bits, Cryptonight
JCE XMRStak XMRig Claymore
116 80 85 57
Core2 Quad 2.666 GHz, 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, 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
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 7 32-bits, with a SSE2 capable CPU. 64-bits is faster, prefer it.
For best performance, Huge 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:
Interplanetary Broadcast (IPBC)
Nicehash Cryptonight v7
MiningRigRentals Cryptonight v7
Otherwise, 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. Is there a HTTP server to monitor the miner?
No, modern pools provide all you need to monitor your miners (average hashrate, worker-id…). Monitoring is now a pool’s job.
Q. Are there requirements or dependencies?
No. JCE is just a big standalone .exe
Q. Is there a Linux version?
Q. Is there a GPU version?
Q. Is there a 32-bits version?
Yes, both 32 and 64 are always in the same release.
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. 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. I used “use_cache”:false and it still has a strong negative impact on other threads
The no-cache mode means the cache is instantly invalidated once used, not always entirely bypassed, depending on your hardware. And a mining thread always has an impact on TLB. So don’t try to use extra mining threads playing with the no-cache mode, rather use the dual-thread mining, which is made for that precise purpose.
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).
All current forks are supported:
N=1 Original Cryptonight
N=2 Original Cryptolight (for AEON)
N=3 Cryptonight V7 fork of April-2018
N=4 Cryptolight V7 fork of April-2018
The current Automatic mode behaves the old way on alt-coins:
Monero, Monero-V and Stellite are now Cryptonight V7,
Sumokoin is now Cryptonight-Heavy,
Aeon is still Cryptolight
TurtleCoin is now Cryptolight V7
Interplanetary Broadcast has is own Cryptolight-IPBC
Everything else is still assumed Cryptonight