Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. MindMiner - the miner manager programm with online monitoringMiner manager programm. Support CPU mining and mining on nVidia and AMD cards.This isnt a next fork based on MultiPoolMiner (NemosMiner, SniffDogMiner, MegaMiner, NPlusMiner and etc).This is full new source code written by me with my minds of a console miner manager programm.Thanks to aaronsace to the idea but weak implementation.Download newVersion: MindMiner_v.4.98You may config any supported miner to any configuration.Features:* Accounting power consumption* Very small code size* Low memory use ~50Mb* Self update* User confirm for benchmarks and new pools* No memory leak* Small CPU usage* Fast switch for most profit algo/coin* Very configurable* Different verbose level* Pools actual balance* Actual miners (if not write me)* Api Pools proxy for more then 10 rigs (prevent blocking api pools request)* Api/status server (http://localhost:5555)* Switching resistance by percentage or timeout* Run process before & after execution of miner* Account accepted & rejected sharesSupported Pools:* NiceHash* MinigPoolHub* Zpool* AhashPool* ZergPool* BlazePool* HashRefinery* BlockMastersSupported Miners:* bminer* dstm zcash (equihash)* cast xmr* cpuminer (any)* cpuminer-opt* ccminer (any)* ewbf (disabled by default, to enable change config file .\Miners\ewbf-xxx.config.txt)* nheqminer (disabled by default, to enable change config file .\Miners\nheqminer-xxx.config.txt)* sgminer (any)* gatelessgate* Claymore ethereum (no dual algo support for now)* Claymore zcash (equihash)* Claymore cryptonight* Claymore neoscrypt* PhoenixMiner (ethash)* xmrig* jce cryptonote* cryptodredgeRequirements:PowerShell 5.0Windows 10 x64 or Server 2016 already contain PowerShell 5.0.For Windows 7 SP1, 8.1, Server 2008 R2 SP1, 2012, 2012 R2 install PowerShell 5.0PowerShell requires Microsoft .NET Framework 4.5 or above.The Windows is x64 need as most of the miners support only x64 bit.Install:Download latest release to any folder. Unpack and may create config.txt (see config section) or just run "run.bat" and enter BTC wallet and other asked data.Config:Place simple config.txt file into programm folder with json contentCode:{"Wallet": { "BTC": "Your BTC wallet" },"Login": "Login for pool with registration (MPH)"}Fee:MindMiner has development fee 1%.MindMiner - miner manager programm with autoswitch between Algos&Polls.This isnt a fork based on MultiPoolMiner (Nemos, SniffDog, Mega, NPlus & etc)ahash/block/zerg/z pools, Lowered cpu usage on pools, solo/party/mc at BlockMasters pool, Added support phi2-lux algo on zergpool. And all Btc, Eth, Xmr, Etc pool.
  3. Last week
  4. Claymore’s Miner Manager - Monitoring and managing mining by rigsCertainly some of you do not know that the Claymore miners, currently popular with the miners, such as the Claymore Zcash AMD GPU miner and the Claymore Dual miner, include the very handy Ethman Remote manager utility, which allows you to centrally control and monitor the rigs that are running miners from Claymore on the local network. In this article I will explain how to configure monitoring rigs using the Ethman Remote manager using the example of the Claymore Zcash AMD GPU miner.So, if you have not installed the latest version of the miner from Claymore, then download and install it. Currently, the most profitable mining algorithm for mining is EquiHash, which produces such altcoins as Zcash (ZEC) and Zcash Classic (ZCL). Therefore, I give a link by which you can download the miner from Claymore for this particular algorithm. Download the latest version of the miner for this link. At the time of this writing, this is version v15.0Download miner: Claymore's Dual Miner Manager v.15.0Claymore's Miner Manager main features:Monitoring rigs parameters that are in the local network.Editing miner configs.Restart miners.Setting the sound alert when stopping the mining process.Automatic launch of a .bat file when stopping the mining process.Now let's proceed directly to setting up the application for monitoring miners from ClaymoreWe launch the miner from Claymore with the help of the .bat file, which contains your settings for mining.Go to the folder "Remote manager", which is located in the folder with the Claymore miner and run the program "EthMan.exe".If your miner is running on the same computer as EthMan, then to add your mining rig to the program, simply click the "Add Miner" button, then enter the name of the rig, enter 127.0.0.1 in the IP address field, and enter in the Port input field: 3333, then click on OK.Now, in the monitoring window, you can see all the main indicators that are transmitted by the miner to the EthMan program via the JSON API in real time: Name of the rig, IP and port, time of the miner, current hashrayt, temperature of all GPUs and fan rotation speed, mining pool, miner version.If the miner is running on the computer on which you run the program for monitoring EthMan, then instead of IP 127.0.0.1 you should enter the IP address of your rig in the local network. (e.g. 192.168.1.1 or other).In addition, you can change the port number of the miner to get statistics. To do this, in the .bat file of your miner simply add the additional parameter "-mport new port number", for example, "-mport 3444". And when adding a barn to the monitoring program, do not forget to specify this particular port later.In order for the miner to give correct results, in the "Options" tab of the Claymore's Miner Manager specify the Main Coin Name: Zcash, Second Coin Name: -, Speed units: KH / s. Then click "Save Settings".By default, the monitoring program on the 8000 port has an http web server installed, with which you can monitor the statistics of your rigs directly through the browser. To do this, simply enter in the address bar of your browser. 127.0.0.1:8000. the port can be changed in the settings of the monitoring program.Supported: • Claymore's miner 15.0 support • Phoenix miner 4.7 c+support • Ethminer +Support • Support Cast XMR + • Dstm v0 support.5.4+ • Support EWBF b+ • XMR-Stak support • Srbminer 1.5.2+Support • Support For XMRig + • Support For Bminer + • Support for ccminer + • Z-enemy 1.12+support • Support JCE Cryptonote + • Support T-Rex + • Detailed statistics for each GPU miner • Remote control for Claymore miner • Alert if miner is offline • Low hashrate alert • Alarm at high temperature GPU • Easy setup - one IP address for all miners • DNS name support • View miner with password (in the miner is set by the-mpsw parameter) • Conversion of Hasrat • View miner console • Simple and user-friendly interface
  5. Earlier
  6. Teamredminer v0.5.9 ReleaseThis is an optimized miner for AMD GPUs created by todxx and kerney666.For questions/comments about chukwa or cryptonight algorithms, please post in this.This is the cuckarood29, cuckatoo31, mtp, x16rv2, x16r, x16rt, x16s, lyra2rev3, lyra2z, and phi2 thread for this miner.Algorithms: Cryptonight R (monero) Cryptonight v8 turtle (turtlecoin, loki) Cryptonight v8 half (stellite, masari) Cryptonight v8 double (x-cash) Cryptonight v8 reverse waltz (graft) Cryptonight v8 upx2 (uPlexa) Cryptonight v8 Cryptonight heavy Cryptonight haven (haven) Cryptonight saber (bittube) Cryptonight conceal (conceal) Chukwa (trtl) x16rv2 (rvn) x16r (rvn) x16s (pgn, xsh) x16rt (veil, gin) MTP (zcoin) Cuckarood29 (grin) Cuckatoo31 (grin) Lyra2rev3 (vtc) Lyra2z Phi2 (lux, argoneum) GPUs Supported and Tested: RX 580/570/480/470 on windows and linux with rocm or amdgpu-pro drivers RX Vega 64/56, Vega FE on windows and linux with rocm or amdgpu-pro/PAL drivers RX 560/550 on windows and linux with rocm or amdgpu-pro drivers Radeon VII on windows and linux with rocm or amdgpu-pro/PAL drivers Windows/Linux download available here:Download teamredminer v.0.5.9API: The miner includes a read-only api based on the sgminer-5.5 API.Both the json and text formats are supported. For more details, we refer to the sgminer api documentation.Software Requirements: Supported GPU driver (see GPUs Supported above) For chukwa, mtp, cryptonight algos and lyra2rev3 on linux, only amdgpu-pro drivers are supported. Version 18.30 or newer is needed for Vegas. ROCm is not supported. This miner includes the following dev fees: Cryptonight R: 2.5% Cryptonight v8 turtle: 2.5% Cryptonight v8 half: 2.5% Cryptonight v8 double: 2.5% Cryptonight v8 reverse waltz: 2.5% Cryptonight v8 upx2: 2.5% Cryptonight v8: 2.5% Cryptonight heavy: 2.5% Cryptonight haven: 2.5% Cryptonight saber: 2.5% Cryptonight conceal: 2.5% Chukwa 2.5% x16rv2 2.5% x16r 2.5% x16s 2.5% x16rt 2.5% MTP 2.5% Cuckarood29 2.5% Cuckatoo31 2.5% Lyra2rev3: 2.5% Lyra2z: 3% Phi2: 3% For reporting bugs and/or for features requests please make a post here and we'll do our best to respond.Any feedback would be appreciated.Features In Development: New Algorithms Pool Failover Changes in v0.5.9 Added x16rv2 for the upcoming Ravencoin fork. Optimization work on x16r: +8-10% hashrate depending on clocks. Optimization work on x16r: mem clock no longer as important. Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues. Changes in v0.5.8 Added Chukwa-512 algo For Turtlecoin (trtl_chukwa). Issue fix: kernels not loaded properly for Conceal. Issue fix: added logic for pool reconnect on N rejected shares in a row (see --pool_max_rejects=N). Changes in v0.5.7 Added CN conceal algo for Conceal (CCX). Added cuckarood29 algo for grin. Changes in v0.5.6 MTP improvements for Vega and Polaris (+1-3% hashrate, improved efficiency, esp Polaris) Changes in v0.5.5 Added cuckatoo31 algo for grin. Changes in v0.5.4 Fixed API bug for MTP, crashing when using Awesome Miner. Small MTP improvements, mostly for Polaris. Changes in v0.5.3 Added MTP algo for Zcoin/XZC (please read MTP_MINING.txt before mining). Further small stabilization fixes for CN variants, primarily 4MB algos. Changes in v0.5.2 Bugfix release only, no new added algos or features. Fix for 1-2% degraded hashrate on Radeon VIIs in some scenarios. Fix for Radeon VII allocation bug, causing hw errs. Fix for allocation bug causing crashes for some drivers and gpus. Changes in v0.5.1 Added better support for CN intensities 16*15, use --allow_large_alloc under Linux. Added --no_ntime_roll for mining x16rt on e.g. bsod.pw. Added Tonga device recognition. Better error reporting for pool communication issues. Changes in v0.5.0 Added cryptonight 4MB variants: heavy, haven and saber. Added x16 algo suite: x16r, x16s, x16rt (both gin and veil). Auto-tuning mode for all CN variants, see bundled guide. Manual key-driven CN tuning mode available inside the miner. Additional data in miner stats console output. Watchdog now detecting single stuck thread when mining CN. Fix: in rare cases, poolside hash for compute algos (lyra2z, phi2, lyra2rev3) only reached ~95% of expected value. Changes in v0.4.5 Added cryptonight v8 upx2 for the uPlexa coin fork. Reworked init procedure, added retry logic on comm errors. Added section on temps to the CN_MAX_YOUR_VEGA guide. Added a new howto MAP_YOUR_GPUS describing how to map gpus between miner/tools/registry. Changes in v0.4.4 Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas. Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage. Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck. Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js). Added hotkey menu system (show stats, enable/disable gpu). Changes in v0.4.3 Added cryptonight v8 turtle (--algo cnv8_trtl) algo for coins such as turtle coin and loki. Added support for running CN mining single-threaded using Y+0 configurations. Changed the auto config mode for Radeon VII to L30+0 as a temporary setting. Changes in v0.4.2 Added cryptonight v8 half (--algo cnv8_half) algo for coins such as stellite and masari. Added cryptonight v8 double (--algo cnv8_dbl) algo for coins such as x-cash. Added cryptonight v8 reverse waltz (--algo cnv8_rwz) algo for coins such as graft. Added support for running devices on multiple OpenCL platforms. Fixed more issues with console colors on older windows versions. Added more cpu verification optimization for CN/R. CN/R cpu usage should decrease ~70%. Changes in V0.4.1 Removed server name verification for SSL connections. (Pools like supportxmr now work with SSL) Fixed bug causing GPUs to fail to initialize on some systems. Fixed bug causing GPUs to only run one thread (but display 2x hashrate) Fixed bug where having GPU_MAX_WORKGROUP_SIZE set too high would cause GPUs to crash. Fixed bug where older windows versions would get no console output. Added work-around for driver bug in linux amdgpu-pro drivers resulting in low pool-side hash for polaris cards in rare cases. Added some cpu verification optimizations. CN/R cpu usage should decrease about 15%. Changes in v0.4.0 Added cryptonight R support. (--algo cnr) Added support for ssl/tls pool connections using the stratum+ssl:// prefix. Added colors (and an option to disable them). Slight performance increase for lyra2rev3 (~0.5%). Fix for occasional crashes when pool disconnects. Added more messages regarding not being connected to dev pool. Changed printing to not block mining progress if stdout writes block. Changes in v0.3.10Slight performace improvement for Vegas on lyra2rev3Pool stratum protocol work-arounds for some pools, fixing duplicate share error.Changed handling of unrecognized pool rpcs to be ignored instead of causing a reconnect.Fix for duplicate shares on 480/580/Vega56 cards with lyra2rev3.Changes in v0.3.9Added support for lyra2rev3 on amdgpu-pro and windows. ROCm support coming in later version.Fixed API bug with not reporting dead GPUsChanges in v0.3.8Added support for fan speed and temperatures.Added watchdog function for gpu init stuck, dead gpu, over-temp gpu, and non-responding pool.Added new optional ‘L’ config prefix for low-end cards like lexa/baffin for a 10+% speed-up on some cardsAdded an option for writing out a log file.Added cycling through multi-entry dns records when connecting to pools.Added a pool-connect timeout.Added measurement and displaying of pool response times.Added support for 80-byte headers for Phi2 algo (for non-LUX coins).Slightly tuned the ‘+’ mode for polaris, some GPUs will show slight performance increase.Fixed bug with API interface occasionally getting stuck.Changes in v0.3.7Redesigned GPU initialization, should now be less error prone.Added clean shutdown to reduce driver/GPU crashes.Added staggered GPU start-up to reduce GPU crashes.Added CPU verification for CNv8 and associated --no_cpu_check option.Fixed crash on pool authentication error.Added --pool_broken_rpc work-around option for pools that violate json rpc spec.Added option to reorder by PCIe bus numbers.Added --list_devices option to show available devices.Added changed stats formatting to indicate which numbers are accepted/rejected/hw-error shares.Added uptime to stats.Changes in v0.3.6Added support for Rx550 cards (gfx804).Improved stability on larger rigs, especially with weaker cpus.Improved error reporting on failed initialization.Changes in v0.3.5Changed GPU initialization to be sequential by default and added --init_style option for faster init styles.Fixed network buffer size issue preventing the use of very long usernames/passwords/rig_ids.Added opencl platform auto-detection for AMD platforms when --platform is not specified.Changes in v0.3.4Added CryptoNight v8 (CNv2) supportChanged stats display to include pool hashrate and better formattingAdded parallel GPU initializationAdded output of submitted/accepted/rejected shares.Changed hashrate reported to be full GPU hashrate (previously hashrate reported was after dev fee deduction)Changes in v0.3.3ROCm support reintroducedAPI support based on the sgminer APIImproved GPU platform detectionPCIe bus id printed on startup and is available over APIAdded option for periodic stats intervalChanges in v0.3.2Added windows support/buildAdded vega PAL driver supportRemoved ROCm support (temporarily)Removed libjansson dependencyChanges in v0.3.1Fixed phi2 issues with rejected shares and low pool-side hashrate.
  7. ################################################# # 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 v0.6.2Version 0.6.2 update:- fix ssl handshake failures- fix device selection bug introduced in 0.6.1- make linux performance improvements introduced in 0.6.1 optionalvia 'mq-solver' parameter (due to issues on some systems)- improve device initialization on large systems Linux x64: Download Zcash_Nvidia for LinuxWin x64 v0.6.2:Download Zcash_Nvidia for WindowsPerformance:1080Ti 725-740 Sol/s1070 440-450 Sol/sstock settingsUI: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 secondAvg: average solutions per secondI/s: iterations per second done by the GPUS/W: efficiency - average Sol/s per WattW: power consuption in Wattlast 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 GPUsFeatures:To get help just start zm without any argumentsCode:ZM 0.6.2, dstm's ZCASH/Equihash Cuda MinerUsage:zm --server hostname --port port_nr --user user_name[--pass password] [options]...zm --cfg-file[=path]Stratum:--server Stratum server hostnameprefix hostname with 'ssl://' for encryptedconnections - e.g. ssl://mypool.com--port Stratum server port number--user Username--pass Worker passwordOptions:--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 devicesare 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' incurrent 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 continuouslyadjusted such that the temperature stays aroundthis value. It is recommended to set your fan speedto 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 - validintensity range ]1.0-0.0[.Example: --intensity=0:0.893,2:0.8--telemetry [=iport]. Starts telemetry server. Telemetry datacan be accessed using a web browser(http) or by json-rpc.If no arguments are given the server listens on127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222Valid port range [1025-65535]--cfg-file [=path] Use configuration file. All additional commandline options are ignored - configuration is done onlythrough configuration file. If 'path' is not givenuse '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 usernameBIG 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.2- fix ssl handshake failures- fix device selection bug introduced in 0.6.1- make linux performance improvements introduced in 0.6.1 optionalvia 'mq-solver' parameter (due to issues on some systems)- improve device initialization on large systemsVersion 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_idgpu_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 colorsVersion 0.5.8con: add support for protocol v.01000020 link openssl staticallyVersion 0.5.7reduce cpu loadminor performance improvementscon: use single pool connectioncon: ssl: clear session data before reconnectnvml: handle invalid valuesVersion 0.5.6reduce cpu loadminor performance improvementsVersion 0.5.5con: handle failure of dev share poolcon: disable reconnect limitlogfile: disable bufferingVersion 0.5.4fix: device selectionfix: latency reportingadd logfile supportadd option to disable auto reconnecthandle disconnect periods in web/json statsadd basic GPU responsiveness infrastructureui: change timestamps to ISO 8601 formatwebui: report: uptime contime server user portjson: report: uptime contime server user port versionVersion 0.5.3cpu: reduce cpu loadcon: fix recon loopcon: network latency measurementui: add accepted/rejected shares ratioui: add network latencyui: add information about selected devicesVersion 0.5.2fix a race that might have corrupted sharesnet: tcp: disable the Nagle algorithmwhich reduces network latency in some circumstancesnet: lower keepalive for nat-networksVersion 0.5.1con: fix reconnection might have give up too earlycon: enable TCP Keepalive to prevent nat-routers fromdropping the connection.ui: output rejected sharesui: optional output of timestampstelemetry: make web ui mobile friendly + add share statstelemetry: json: add more GPU statsVersion 0.5con: support set_extranonce rpccon: improve handling of temporary slow network conditionscon: add monitoring support using web browsercon: add monitoring support using json-rpcmp: rebalance queue sizes - this improves the solution rate asseen by the pools, especially on pools that submit new jobs oftenVersion 0.4.5fix: bad miner performance when using --temp-targeton systems with many GPUsreduce temperature controller cpu usageVersion 0.4.4fix: Sol/W might have produced wrong valuesfix: Sum not shown if --dev was usedfix: memory leak on reconnectionimprove stabilityVersion 0.4.3stratum: support more poolsui: flush stdout streamcon: improve reconnectionsperformance improvements 0.3-0.5 %Version 0.4.2mp: more accurate time measurementsui: calculate efficiencyVersion 0.4.1improve performanceVersion 0.4.0temperature controller addedcpu: reduce CPU usagecon: improve pool supportminor performance improvementVersion 0.3.2mp: improve stabilitycon: support more poolscon: more robust reconnection support for unreliableservers which often drop the connection ui: report GPU temperatureVersion 0.3.1cpu: reduce CPU usageVersion 0.3con: support encrypted connectionsVersion 0.2.2con: Miner reconnects automatically on connection loss now, e.g. on DSL-disconnects / public IP-changes UI: report submitted devfee-sharesVersion 0.2.1Performance 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
  8. NoDevFee - for Claymore`s Dual Ethereum and Phoenix miner ========================= Version 14.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 nicehash.com DOWNLOAD LINK: MEGA - https://mega.nz/#F!nZ1wSKwJ!i6Q2HKNvJ4JhCCWqY55gqQDev Fee's - 0.05%FEATURES:- Supports applying optimized memory timings (straps) on-the-fly in Windows, without flashing VBIOS (currently Polaris, Vega, Nvidia 10xx cards only), up to 20% speedup. Best straps for Ethereum are included.- Supports new "dual mining" mode: mining both Ethereum and Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak at the same time, with no impact on Ethereum mining speed. Ethereum-only mining mode is supported as well.- Effective Ethereum mining speed is higher by 3-5% because of a completely different miner code - much less invalid and outdated shares, higher GPU load, optimized OpenCL code, optimized assembler kernels.- Supports both AMD and nVidia cards, even mixed.- No DAG files.- Supports all Stratum versions for Ethereum: can be used directly without any proxies with all pools that support eth-proxy, qtminer or miner-proxy.- Supports Ethereum and Siacoin solo mining.- Supports both HTTP and Stratum for Decred.- Supports both HTTP and Stratum for Siacoin.- Supports Stratum for Lbry, Pascal, Blake2s, Keccak.- Supports failover.- Displays detailed mining information and hashrate for every card.- Supports remote monitoring and management.- Supports GPU selection, built-in GPU overclocking features and temperature management.- Supports Ethereum forks (Expanse, etc).- Windows and Linux versions.This version is POOL/SOLO for Ethereum, POOL for Decred, POOL/SOLO for Siacoin, POOL for Lbry, POOL for Pascal, POOL for Blake2s, POOL for Keccak.For old AMD cards, Catalyst (Crimson) 15.12 is required for best performance and compatibility.For AMD 4xx/5xx cards (Polaris) you can use any recent drivers.For AMD cards, set the following environment variables, especially if you have 2...4GB cards:GPU_FORCE_64BIT_PTR 0GPU_MAX_HEAP_SIZE 100GPU_USE_SYNC_OBJECTS 1GPU_MAX_ALLOC_PERCENT 100GPU_SINGLE_ALLOC_PERCENT 100This miner is free-to-use, however, current developer fee is 1%, every hour the miner mines for 36 seconds for developer. For all 2GB cards and 3GB cards devfee is 0%, so on these cards you can mine all ETH forks without devfee, this miner is completely free in this case.If some cards are 2...3GB and some >3GB, 2...3GB cards still mine for you during devfee time, only cards that have more than 3GB memory will be used for devfee mining. Miner displays appropriate messages during startup.Second coin (Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak) is mined without developer fee.So the developer fee is 0...1%, if you don't agree with the dev fee - don't use this miner, or use "-nofee" option.Attempts to cheat and remove dev fee will cause a bit slower mining speed (same as "-nofee 1") though miner will show same hashrate. Miner cannot just stop if cheat is detected because creators of cheats would know that the cheat does not work and they would find new tricks. If miner does not show any errors or slowdowns, they are happy.This version is for recent AMD videocards only: 7xxx, 2xx and 3xx, 2GB or more. Recent nVidia videocards are supported as well.CONFIGURATION FILEYou can use "config.txt" file instead of specifying options in command line. If there are not any command line options, miner will check "config.txt" file for options.If there is only one option in the command line, it must be configuration file name.If there are two or more options in the command line, miner will take all options from the command line, not from configuration file.Place one option per line, if first character of a line is ";" or "#", this line will be ignored. You can also use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment variable and use it as "%WORKER%" in config.txt or in epools.txt.If for Ethereum-only mining:ethpool:NoDevFee.exe -epool us1.ethpool.org:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw xsparkpool:NoDevFee.exe -epool eu.sparkpool.com:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw xf2pool:NoDevFee.exe -epool eth.f2pool.com:8008 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -eworker rig1nanopool:NoDevFee.exe -epool eth-eu1.nanopool.org:9999 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -eworker rig1nicehash:NoDevFee.exe -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal 1LmMNkiEvjapn5PRY8A9wypcWJveRrRGWr -epsw x -esm 3 -allpools 1 -estale 0Ethereum forks mining:NoDevFee.exe -epool exp-us.dwarfpool.com:8018 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -allcoins -1FAILOVERUse "epools.txt" and "dpools.txt" files to specify additional pools (you can use "-epoolsfile" and "-dpoolsfile" options to use different filenames). These files have text format, one pool per line. Every pool has 3 connection attempts. Miner disconnects automatically if pool does not send new jobs for a long time or if pool rejects too many shares.If the first character of a line is ";" or "#", this line will be ignored. Do not change spacing, spaces between parameters and values are required for parsing.If you need to specify "," character in parameter value, use two commas - ,, will be treated as one comma.You can reload "epools.txt" and "dpools.txt" files in runtime by pressing "r" key.Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list. If no pool was specified in the command line then first pool in the failover pools list is main pool.You can change 30 minutes time period to some different value with "-ftime" option, or use "-ftime 0" to disable switching to main pool.You can also use environment variables in "epools.txt", "dpools.txt" and "config.txt" files. For example, define "WORKER" environment variable and use it as "%WORKER%" in config.txt or in epools.txt.You can also select current pool in runtime by pressing "e" or "d" key.REMOTE MONITORING/MANAGEMENTMiner supports remote monitoring/management via JSON protocol over raw TCP/IP sockets. You can also get recent console text lines via HTTP.Start "EthMan.exe" from "Remote management" subfolder (Windows version only).Check built-in help for more information. "API.txt" file contains more details about protocol.KNOWN ISSUES- AMD cards: on some cards you can notice non-constant mining speed in dual mode, sometimes speed becomes a bit slower. This issue was mostly fixed in recent versions, but not completely.- AMD cards: in Linux with gpu-pro drivers, the list of GPUs may differ from the list of temperatures. You can use -di to change order of GPUs to match both lists.- nVidia cards: dual mode is not so effective as for AMD cards.- Windows 10 Defender recognizes miner as a virus, some antiviruses do the same. Miner is not a virus, add it to Defender exceptions. I write miners since 2014. Most of them are recognized as viruses by some paranoid antiviruses, perhaps because I pack my miners to protect them from disassembling, perhaps because some people include them into their botnets, or perhaps these antiviruses are not good, I don't know. For these years, a lot of people used my miners and nobody confirmed that my miner stole anything or did something bad. Note that I can guarantee clean binaries only for official links in my posts on this forum (bitcointalk). If you downloaded miner from some other link - it really can be a virus.However, my miners are closed-source so I cannot prove that they are not viruses. If you think that I write viruses instead of good miners - do not use this miner, or at least use it on systems without any valuable data.TROUBLESHOOTING1. Install Catalyst v15.12 for old AMD cards; for Fury, Polaris and Vega cards use latest blockchain drivers.2. Disable overclocking.3. Set environment variables as described above.4. Set Virtual Memory 16 GB or more.5. Reboot computer.6. Check hardware, risers.7. Set some timeout in .bat file before starting miner at system startup (30sec or even a minute), and try "-ethi 4" to check if it is more stable. It can help if miner is not stable on some system.
  9. Cast XMR - Highspeed CryptoNight (Monero/Bytecoin/DigitalNote/Loki/Haven/BitTube/Aeon) Miner for Radeon RX Vega and RX 470/480/560/570/580/590 GPUsFeatures- Full support for:CryptoNightV8 (CNv2)Monero (XMR) Graft (GRFT) Lethean (LTHN) Safex (SAFEX) CryptoNightV7 (CNv1) Quantum Resistant Ledger (QRL) DigitalNote (XDN) CryptoNight (Classic)Electroneum (ETN) Bytecoin (BCN) CryptoNightXTLStellite (XTL) CryptoNight-HeavyLoki (LOKI) Saronite (XRN) CryptoNightXHV-HeavyHaven (XHV) CryptoNightV7-LiteAeon (AEON) Turtlecoin (TRTL) CryptoNightTUBE-HeavyBitTube (TUBE) CryptoNight-FastMasari (MSR) CryptoNight-SuperFastFree Haven (XFH)– Fastest miner for AMD Radeon RX Vega 64 GPUs about 2000 CryptoNight/V7 Hashes/s about 1850 CryptoNightV8 Hashes/s (10 min average) about 1635 CryptoNight-Heavy Hashes/s about 4100 CryptoNight-Lite Hashes/s – Fastest miner for AMD Radeon RX Vega56 GPUsl more then 2000 CryptoNight/V7 Hashes/s about 1825 CryptoNightV8 Hashes/s (10 min average) about 1550 CryptoNight-Heavy Hashes/s about 4260 CryptoNight-Lite Hashes/s – Fastest miner for AMD Radeon Vega Frontier Edition GPUs about 2100 CryptoNight/V7 Hashes/s about 1930 CryptoNightV8 Hashes/s (10 min average) about 2120 CryptoNight-Heavy Hashes/s about 4260 CryptoNight-Lite Hashes/s – Optimized cores for Vega and Polaris based GPUs – Automatic driver version detection and setup recommendations – Multiple GPU support for upto 24 Vega GPUs – Monitor temperature and fan speed of each GPU – Full pool support – Nicehash support – Fast Job Switch option to minimize outdated shares – Rate Watchdog to monitor each GPU performance – Includes switch-radeon-gpu command line tool to restart GPUs, switch on/off HBCC, Compute Mode and Large Pages – Remote http access for statistics in JSON format – only 1% dev feeRequirements– Windows 8/8.1/10 64 bit or – Ubuntu Linux 16.04 or later – AMD Radeon RX Vega 56/64 GPU with at least 8GB RAM – or AMD Radeon RX Vega Frontier Edition with 16GB RAM – or AMD Radeon RX 470/RX 480/RX 560/RX 570/RX 580/RX 590 GPU with a least 4GB RAM – For up to 50% higher hash rates the Radeon Driver 18.5.1 or later has to be installedVersion HistoryCast XMR Version 1.8.0 (2019/02/21) support for Radeon VII GPUs addedCast XMR Version 1.7.1 (2019/01/26) fix for Masari (MSR) to support uncle mining and the network upgrade to CryptoNightV8-Fast, now –algo=6 has to be used to mine MasariCast XMR Version 1.7.0 (2019/01/24) support for CryptoNightV8-Fast (–algo=6) for mining Stellite (XTL). The previous CryptoNightXTL algo has been removed support for CryptoNight-Turtle (–algo=9) for the upcoming Turtlecoin (TRTL) PoW network upgrade (at block 1,200,000) Vega FE: option to turn –intensity up to 13 for “Fast” CryptoNight variants to gain 2% higher hash rates Cast XMR Version 1.6.6 (2018/11/30) – support for RX 590 GPUs added – fixes for detecting Compute Mode on Polaris based GPUs – support for CryptoNight-SuperFast (–algo=11) for mining Free Haven Protocol (XFH) – updated switch-radeon-gpu to version 1.2.0, which includes bugfixes for newer versions of the AMD Radeon driversCast XMR Version 1.6.0 (2018/11/07) – Vega 56/64: 0.5 to 1% performance improvement on CryptoNightV8 – Vega 56/64: 2 to 3% speed improvement on CryptoNight-Heavy variants (Loki, BitTube, Haven) – updated included switch-radeon-gpu to version 1.0.5 – support for RX 560 GPUs addedCast XMR Version 1.5.0 (2018/9/27) – Support for the Monero V8 Network Upgrade which introduces a new CryptoNight variant CryptoNightV8 aka CNv2. The Monero V8 update is scheduled for 18th October. In case you are mining Monero make sure to update Cast XMR before that date. Also make sure that the algo for Monero is not explicitly set to CryptoNightV7 but set to auto detect with –algo=-1 to automatically switch from CryptoNightV7 to CryptoNightV8 when the upgrade is happening. Please also note that the CryptoNight V8 algo has added complexity which decreases the hashrate up to 7% for Vega GPUs.Cast XMR Version 1.4.0 (2018/8/28) – 3% performance improvement for CryptoNightTUBE-Heavy when mining BitTube (TUBE) – support for Festival Coin (FEST) upcoming update which introduces a new CryptoNight variant: CryptoNightFEST. Use –algo=9 to continue mining Festival Coin after the network update happened – subtle performance improvements – Tested with Radeon Adrenalin Driver 18.5.1Cast XMR Version 1.3.0 (2018/6/29) – Performance improvement for job switches with multiple GPUs – Support for BitTube (TUBE) V4 Pow Update which introduces the new algo CryptoNightTUBE-Heavy aka CN Saber. Stay on –algo=5 to switch automatically from CryptoNightIPBC-Lite to CryptoNightTUBE-Heavy when the update is happening (approx. 2nd July). Please note that the hash rate will drop as it is a switch from a Lite to a Heavy variant.Cast XMR Version 1.2.5 (2018/6/19) – Support for CryptoNight-Fast introduced with the Masari (MSR) update. Set –algo=8 to mine Masari (MSR). CryptoNight-Fast will produce higher hash rates than classic CryptoNight, typical hash rates are: – Vega64, 1025 Mhz MemClock: 3630 Hashes/s – Vega56, 945 Mhz MemClock: 3700 Hashes/s – VegaFE, 1025 Mhz MemClock: 3900 Hashes/s – RX 470/570, 2250 Mhz MemClock: 1550 Hashes/sCast XMR Version 1.2.0 (2018/6/12) – Fix for “unauthenticated shares” pool error – Support for the upcoming Haven (XHV) V3 update. In case you are mining Haven set –algo=7 now. Cast will then automatically switch to CryptoNightXHV-Heavy when the network update is happening.Cast XMR Version 1.1.5 (2018/6/7) – Fix for mixed up device order – Support for Stellite (XTL) V4 Update. Add –algo=6 in case you are mining Stellite. It will automatically switch to CryptoNightXTL when the network update is happening. – Stability fixesCast XMR Version 1.1.0 (2018/6/1) – All new –intensity option to specify the memory allocation in the range of 0 to 10, upto 12 for Vega Frontier Edition. The default setting will correspond with the settings of version 1.0 and are displayed at startup. – Vega Frontier ‘Large Pages’ support added, up to 30% higher hash rates for CryptoNight-Heavy, 5% increase for CryptoNight – Includes the switch-radeon-gpu command line tool to restart GPUs, switch on/off HBCC, Compute Mode and Large Pages – Nicehash supports now up to 24 GPUs – –maxmem option is deprecated, will now be mapped to an corresponding intensity setting – –forcecompute is deprecated, ‘Compute Mode’ of Polaris GPUs will be automatically detected. To overwrite use the –intensity option – Default mining algo changed to CryptoNightV7, to still mine CryptoNight Classic add –algo=0 – Tested with Radeon Adrenalin Driver 18.4.1Cast XMR Version 1.0.0 (2018/4/24) – Support for Aeon (AEON) CryptoNight Lite variant set –algo=3 to mine – Support for Turtlecoin (TRTL) CryptoNightV7 Lite variant set –algo=4 to mine – Support for Interplanetary Broadcast Coin (IPBC) CryptoNight Lite IPBC variation set –algo=5 to mine – Up to 3% performance improvement with new option –maxmem to allocate the maximum memory of the card. For Vega cards the “HBCC Memory Segment” has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the –maxmem option is used.Cast XMR Version 0.9.6 (2018/04/17) – CryptoNight-Heavy fix for very low hash rates when HBCC Memory Segment is enabled – HBCC Memory Segment performance hint for Vega64 when mining CryptoNightV7 – Improvement for 4GB versions of RX 470/480/570/580 when mining CryptoNightV7Cast XMR Version 0.9.5 (2018/04/14) – 0.5% performance improvement for the CryptoNightV7 kernel – support for CryptoNight Heavy set –algo=2 to mine: – Sumokoin (SUMO) – Haven (XHV)Cast XMR Version 0.9.2 (2018/03/29) – Improvements for RX Vegas that achieve 99% the performance of the Blockchain Compute Beta driver with the latest standard Radeon Driver 18.3.4Cast XMR Version 0.9.1 (2018/03/22) – 0.5% overall performance improvement for Vega based GPUs – –ratewatchdog experimental option to monitor the hash rate, in case an occasional happening drop of the hash rate is detected the kernel will be resetted to restore the optimal hash rate – fully tested CryptoNight variant (CryptoNightV7) for the Monero V7 Network Upgrade PoW Change which is now scheduled for the 6th April. – In case you want to mine the Graft coin use the –algo=0 option, an automatic detection of the used CryptoNight variant is not possible for this coin. For all other known CryptoNight coins the hash variant seems to be detected correct – In case you are mining with nicehash.com or any other automatic coin switching pool that has the Graft coin in the mix the –algo=0 option is advised to prevent invalid shares on the Graft coin. Be aware to remove the option when the Monero V7 network upgrade is happpening otherwise it then will clash with mining Monero!Cast XMR Version 0.9.0 (2018/03/08) – support for the Monero V7 network upgrade. Read more about it here – the Monero PoW switch will be automatically detected, no restart of cast XMR is required. Only make sure to update cast XMR before the network upgrade is happening and that the used Monero pool supports the network upgrade – no decrase in hash rate for other currencies was introduced by the change – CryptoNightV7 will run at the same hash rate as CryptoNight – for any case there is the new –algo option to force which CryptoNight variant to use: – -1 = autodetect (default) – 0 = CryptoNight – 1 = CryptoNightV7 (Monero V7 network upgrade)Cast XMR Version 0.8.5 (2018/02/07) – 1% performance gain for Vega Frontier Edition with Blockchain driver (fastest GPU around) – 1% performance improvement with current stock driver (18.1.1) for RX Vega 56/64 (40% to go to reach Blockchain driver performance) – fix for random blocking console output – GPU now always logs with its device id not the order they are listed in the -G argument – –log option to log console output to a file – remote access includes CORS support in HTTP headerHow Tocast_xmr has a command line interface. For a minimal configuration run:cast_xmr -S [pool server] -u [username or wallet address]For a complete list of configuration options run:cast_xmr –helpDownload Cast XMR 1.8.0 for Windows (64bit)
  10. JCE Cryptonote CPU MinerWelcome to the Fastest Cryptonote CPU Miner ever! Try the GPU Version (includes the CPU miner), the fastest CN-Heavy/XHV/Tube miner!You can download it from the Mega page here:Download JCE MinerLike 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.Recent history0.33q CPU and 0.33b18 GPUQuote* TurtleCoin defaults to v2* Fix possible Masari v8 bad shares* Waltz/Graft fork as --variation 220.33b17 GPUQuote* Masari v8 support* watchdog can restart the miner instead of quit, parameter --restart0.33p CPUQuote* Native Stellite v8 and Masari v8 support0.33b16 GPUQuote* Stellite v8* Rig-id* Light optim for mixed cpu/gpu mining0.33n CPUQuoteNew fork: Stellite v8Rig-id parameter (optional)0.33b15 GPUQuoteBackport of 0.33m CPUNew fork: Turtle v2, as --variation 20New coin: DeroGoldRemote Managment through the HTTP serverIGP autoconfig fix0.33m CPUQuoteNew fork: Turtle v2, as --variation 20New coin: DeroGoldRemote Managment through the HTTP server0.33k CPUQuoteSeparate assembly for Bulldozer x64 on v8 algo0.33b14 GPUQuoteuPlexa fork, as --variation 19Backported CPU optim from 0.33j--legacy now keeps the CPU idle when mining only with GPU0.33j CPU (upgrade to this one or later for CPU mining highly recommended)QuoteuPlexa fork, as --variation 19Better/restored speed on v8Updated a few (the S-word)coins forks.0.33i CPUQuoteBig optimization for v8, for all CPUs +2%Sumokoin wallets default to Ryo0.33b12 GPU0.33b11 GPUQuoteNew coin FredCoinBetter pool-side efficiency0.33h CPUQuoteNew coin FredCoinLittle optim for Zen CPU on v80.33b10 GPU+CPUQuoteFixed possible bad sharesLittle optim for RX on v8Little optim for Zen CPU on v8Warning when a non-AMD gpu is enabled to mine0.33b9 GPU (upgrade to this one or later highly recommended)QuoteFixed Nicehash netcodeVery little optim for RX on Heavy/forksWarmup now all automatic0.33b8 GPUQuoteMore stable hashrateSpeed increase in most cases0.33b7 GPUQuoteCryptonight-FreeHaven backported from CPU versionCryptonight-Dark tooFees lowered back to 0.9% for all algosLittle optims0.33g CPUQuoteCryptonight-FreeHaven algo with --variation 18MoneroOcean "algo_perf" configuration possibleUpdated doc0.33f CPUQuoteCryptolight-Dark algo with --variation 17Parameterless config (service style)0.33b6 GPUQuoteMore stable hashrateTemperature watchdogFixed OpenCL bug 0-2.10Updated docVery light perf boost0.33b5 GPUQuoteCrazy huge performance boost for Heavy/HVX/Tube + 20%Respective fees increased to 2.1%Very light perf boost for CN-v80.33b4 GPUQuoteHuge performance boost on CN-v8Graft now defaults to CN-v8SpeedIn short, JCE is:Crazy fast on non-AES 64-bits, usually 35-40% faster than other minersCompared to other 32-bits miners, still faster on non-AES 32-bits, sometimes beating even the other miners 64-bits versionsAnd 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-HeavyAlso 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.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 scoreCore2 Quad 2.666 GHz 12M, 4 threads, 64-bits, CryptonightJCE XMRStak XMRig Claymore116 80 85 57Core2 Quad 2.666 GHz 12M, 4 threads, 32-bits, CryptonightJCE XMRStak XMRig Claymore93 0 68 50Ryzen 1600, 8 threads, 64-bits, CryptonightJCE XMRStak XMRig Claymore506 502 502 443Ryzen 1600, 8 threads, 32-bits, CryptonightJCE XMRStak XMRig Claymore434 0 327 275Ryzen 1600, 8 threads, 64-bits, Cryptonight V7JCE XMRStak XMRig Claymore503 492 491 ?Ryzen 1600, 8 threads, 32-bits, Cryptonight V7JCE XMRStak XMRig Claymore424 0 320 ?Core2 Quad 2.666 GHz 12M, 4 threads, 64-bits, Cryptonight HeavyJCE XMRStak XMRig Claymore50 33 36 0Ryzen 1600, 4 threads, 64-bits, Cryptonight HeavyJCE XMRStak XMRig Claymore252 169 250 0Ryzen 1600, 4 threads, 32-bits, Cryptonight HeavyJCE XMRStak XMRig Claymore191 0 174 0Getting startedIf 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 itChoose a pool to mine on, and its port. For example Pool pool minexmr com and port 4444Edit the start.bat that’s shipped in the .zipChange the example POOL by yoursChange the example PORT by yoursChange the example WALLET by yoursYou 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 batRun start batBasic topicsNeed .net 4.0 and >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:2.0% when using at least one mining thread with non-AES architecture, or 32-bits0.5% when using only 64-bits AES architectureThe fees are twice higher in non-AES mode and/or 32-bits because JCE offers a huge performance gain here.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:Aeon (AEON)Alloy (XAO)ArQmA (ARQ)ArtoCash (RTO)B2BCoin (B2B)Bitcoin2network (B2N)BBSCoin (BBS)Bitcoal (COAL)BitcoiNote (BTCN)Bitsum (BSM)BlackRose (BLR)Bloc (BLOC)BitTube (TUBE)BlueberriesCoin (BBC)Bytecoin (BCN)Caliber (CAL)Catalyst (XAT)Citadel (CTL)Citicash (CCH)Constella (XCC)Crepcoin (CREP)CryoNote (XCN)Dero (DERO)DeroGold (DEGO)Dinastycoin (DCY)DragonGlass (DRGL)Electronic Dollar (EDL)Electroneum (ETN)Elya (ELYA)Fonero (FNO)FreeHaven (XFH)FreelaBit (FBF)FuryCoin (FURY)Gadcoin (GAD)Graft (GRFT)Haven (XHV)HospitalCoin (HOSP)Iridium (IRD)Italo (ITA)KashKoin (KHK)Karbowanec (KRB)Lethean (LTHN)Leviarcoin (XLC)Lines (LNS)Loki (LOK)Lumeneo (LMO)MarketCash (MKT)Masari (MSR)MinergateMiningPoolHubMiningRigRentalsMonero (XMR/XMV)MoneroOceanMox (MOX)NicehashNiobio (NBR)Ombre (OMB)ParsiCoin (PARS)Plenteum (PLE)Pluracoin (PLURA)PrivatePay (XPP)PyrexCoin (PYX)Qwertycoin (QWC)Remix (RMX)Saronite (XRN)Solace (SOL)Stellite (XTL)Sumokoin (SUMO)SuperiorCoin (SUP)SuprnovaSwap (SWAP)TaxfreeCoin (TXC)Tritanium (TTNZ)Triton (TRIT)Truckcoin (TRKC)Turtlecoin (TRTL)UltraNote (XUN)UPlexa (UPX)Veronite (XVV)VideoGamesCoin (VGC)Wownero (WOW)Xaria (XARI)X-Cash (XCA)zBucks (ZBK)Zelerius (ZLS)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 --sslQ. 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.Advanced topicsQ. Are there requirements or dependencies?No. JCE is just a big standalone executable.Q. Is there a Linux version?Yes, starting from version 0.29Q. 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. Can I plug it to a stratum proxy?No, it must mine on a real pool on Internet.
  11. Thanks, This is helpful. I keep getting an error that Difficult is too low, even through I'm mining with vpn starting diff of 400k.
  12. willieaames

    Windows 7

    Go and install windows 10, you will forget everything.
  13. Version 2.14

    8 downloads

    Updated XMRig
  14. Version 2.13.1

    2 downloads

    Zero dev fee XMRIG CPU miner
  15. Awesome post...Nice work!
  16. Version 1.0.0

    4 downloads

    This mod gives me ~10 hash/s more than the SRB pimp my straps option, using original rom
  17. Version 1.0.0

    2 downloads

    AMD RX570 hash/watt chart, which shows power draw, hash, and best hash/watt
  18. Version 1.0.0

    4 downloads

    Some example log for OC your AMD cards
  19. TL;DR: A too long post on how to get more hash and less power draw from your GPU's, while saving $20+ per GPU on power costs per year, and maybe increasing hash speeds up to 20%. If you are still interested, keep reading. If you think, BS! my rig produce max hash, then its your loss, max hash doesn't mean u earn the most possible $: you are just making a lot of heat. RX550 2GB ITX doing 520 - 530 h/s @ wall power draw of 76 - 77 Watt, or ~ 11.5 h/s/W (max possible hash = max earnings) RX570 4GB ITX doing 860 - 890 h/s @ wall power draw of 85 - 90 Watt, or ~ 9.5 - 10 h/s/W (for best possible earnings, max hash would be 900 - 960 hash, at <= 8 h/s/W) Thanks: First some important thanks to the guys from codpool (I am not affiliated in anyway btw), providing a lot of insights and help setting up my miners: CODpool, which runs various CryptoNight pools (Monero, Graft, BBS, and 20 others or so) with limited pool fees: Central pool page: https://codpool.com/ Combined Discord and Telegram chat (thanks to the awesome chat bridge from Bencey). Here you can find me too if you have any questions, suggestions, or want to share your thoughts. If you like this post, just say hi in the discord or forums, and mine for a bit on a codpool pool, into your own wallet, and maybe add them as fall back pool for when your pool might be down. No need to send me coins or whatever (but maybe send me an other card to test 🙄, as I out-tested my cards for now). Lets start with why this long-read: Power costs money (at least for most of us): 10 Watt power reduction at $0.10 per kWh will give you: 10W / 1000 * $0.10 * 24h * 365.2421875... = $8.77. For a RX570 4GB, lowering default voltages, flashed, and overclocked and stable memory, you can cut 40W easily. 20W more is also possible, as you will see below. Saving you $52.59 on a single card, per year. Power brings heat (nice when its cold outside, but lower heat is better for your cards, ears, etc.): Above saving of 60W will give you: 60W / 1000 * 24h * 365.24... = 525.95 kWh. With that amount of power you could make 525.95 / 0.444 = 1184.57 * 1 liter cans of boiling hot tea..., each year.... ( 1 liter = 0.264 US gallon btw). Starting tips: Get a Power meter between the plug and the PSU cord (~$10 - $20), so u actually know what power you draw or are saving: I got this one, which seems to be rather good: brennenstuhl-pm-231-e Software tools like HWi, GPUz, etc DON'T give you the correct power draw, and are way off. Maybe get 2, so you can add one on your main rig, and use the other one while testing. Power draw is a good way to spot if something is wrong with your miner (with focus on clocking resets, hanging miner, etc) Make some simple test setup: Motherboard with PCIe connection and onboard video (so hash is not affected by the monitor), maybe use a PC-case for power buttons, otherwise use a screwdriver (only if you know what u are doing). PSU that can handle the TDP of the CPU and GPU, so something like 300W - 500W. Temporary monitor, mouse, keyboard for installing Windows, and setting your bios right with video output via internal graphics. Later on I prefer to use remote desktop. Preferably SSD (fast, as u will be rebooting a lot) or old 2.5 inch HDD (they both use not much power, and cause less power fluctuations), although I used an 3.5 inch HDD but that costs a lot of time for rebooting and reading out average power draw. Download the following software: I have provided only 'official' links to the pages of the developers of the actual software, don't go for tools that seem to be more recent, but not from trusted sources. Windows 10 latest Autologon this will make your PC login automatically, even when Remote Desktop is enabled. Just double click the file, and provide your credentials. This helps starting your Miner and other tools to start automatically after a reboot, without the need to login. (if your miner does start, but not continues after a bit, you need to mess with internal graphics in your BIOS, maybe attached a fake monitor dongle, or a turned of monitor). Often preferred AMD driver, or some recent AMD driver, which I use and seems to give way less memory errors on bad cards. I don' like the AMD GUI, it is slow, annoying in remote desktop, etc. So I extracted the package, canceled the actual installation, went to Windows Device Manager, chose update driver for a AMD card, selected the C:\AMD folder to be looked into for the driver, and voila. Compute mode can easily and fast be set via SRBminer, no need for the GUI. Copy the original start .bat file, and make the last lines look like below, and run it as admin: SRBMiner-CN.exe --setcomputemode timeout 20 HWi, for monitoring memory errors, voltages, clockings, temp, fan speed etc. AMD/ATI flash for flashing your GPU bios with better straps. AMD/ATI pixel clock patcher (needs to be run after flashing GPU bios, or your GPU wont be recognised). OverdriveNTool, for changing clocks and reduce voltages, (note that for recent drivers, you'll need a recent version of this tool, or even a beta, otherwise some options might not work!) SRBPimp for making custom straps (to get higher hash rates), use the 'pimp my straps' option, or make straps with some other PolarisBiosEditor. (I used this RX550 mod to get just a bit better hash than using SRBpimp: MSI AERO ITX RX550 2GB Lexa hynix elpida mod. Various miner options: TeamRedMiner, claims to be great for Vega, and is great for RX550s, not yet for RX570s as I tested it extensively. SRBMiner, easy to use, stable, lots of features, gives good hash speeds for my RX570s, and voltages can be set extremely low, meaning less power draw. XMR-Stak, more difficult to configure, atm limited hash speed compared to options above ... DDU for total removal of GPU drivers if needed, and a clean install, or when you want to update drivers. Just deinstalling drivers won't remove them completely, maybe causing issues Make some spreadsheet to log all your tests and settings, because after 5 setting changes you wont know what u did before, and with 100s of possible settings, you will get lost, So log the following: Most important: Power draw (Watt), Hash/s, Memory errors, test duration (say 10 - 15 min each). With the duration you can calculated memory errors per hour (MER/h). Values set for Core Clock (CC), Core Voltage (CV), Memory Clock (MC), Memory Voltage (MV) Maybe also actual CV, MV, reported by HWi. Basics on GPU power draw: Power companies bill on kWh power usage, which means using 1000 W for 1 hour = 1kWh Power (W) = Ampere (A) * Voltage (V), and for GPUs (and CPUs) we can only easily lower the voltage, so by lowering voltage, we lower power draw, and therefore costs. GPU voltages are set well above stable values, to always guarantee good operation under any load. For a RX570 the Core Clock (CC), the Core Voltage (CV) is about 1150 mV, while I run those for mining on 800 mV or less, meaning ( 1150 - 800) / 1150 * 100% = 30% less power draw by the core. Memory voltage is by default around 900 mV, and can be lowered to about 800 mV too, saving only (900 - 800) / 900 * 100% = 11% power draw by the memory. Luckily the core is the largest power consumer, so can we reduce the power draw by about 30%? In the results below I will show you I reduced power from 155 W (stock voltages, CC at stable overclock) to 86 W, or by 44%, but resulting in more hash loss than power gain. Optimum hash vs power usage for me resulted in 90 W power draw instead of 155 W, or a reduction of power usage by 42%. To measure your GPU power draw, build your rig without GPU attached, boot it, let it run idle for a couple minutes, and read out the power draw at the plug. This is your base power draw, which should about 15W to 30W. Write this down as you later will be needing it. (idle GPUs draw about 10 W to 20 W) The most interesting part of this post: In short: LOG EVERYTHING, especially Hash and power draw, I made this: Example OC Log AMD video cards Optimize on earnings = $/h * h - W * $/W, not on just hash or h/W. Use SRBminer as this seems the most stable miner while testing odd stuff, and get a quick and sufficient understanding of your cards behaviour. Max out MC, lower MV, (CC CV MC MV) start: (1244 1150 1925 900) = 887 H/s @165 Watt Use default CC, lower CV until just stable. end: (1244 887 1920 775) = 913 H/s @111 Watt Lower CC by a 50 or 100 Mhz step, then smaller steps (eg do something like 1250 1150 1100 1075 1050 1025) With each step also lower CV till stable, for less power draw Got free power? or just don't believe lower CC will earn you more, up it, and if needed power too. (and don't forget to read out power draw) best: (1075 762 1920 775) = 866 H/s @90 Watt Hash will drop, but power draw will drop faster till a certain point, upping your hash/W, just log al those points, so you can put them in a chart: click for larger image: Some explanation on above: This is just data for a typical RX570 4GB ITX + SRB, so don't blame me if you get better data, just be proud you got better cards than me, or can tune better! Maybe drop your plots below. Al cases where I got more than 4 MER/h are left out of the chart Al runs are like 10-15 minute ones (some are way longer, just to see if I am right) Chart is based on ~150 test runs, showing you only need a couple of tests. (maybe 20, even just 5 - 10 if you have a set of similar cards) Results: A little bit more max hash, costs a lot more power (= more heat, more MER/h btw) Lower MC doesn't allow for a lower MV, no h/W gain here for lower MC So just max out MC, and lower MV till stable, no need to test for other MC than max. (MV draws limited power, so no worries to set it a tiny bit above the lowest value) Biggest h/W gain comes from lowering CV, this may require lower CC. Those angled dotted straight lines show the Hash/Watt, so dots more to the left, the better h/, but they also cost a little total hash If power costs are low, or h/W is high, it could mean almost max hash at best voltages, without lowering CC, might be the best spot. For me this is at about 11 h/s/W, so my RX550s are ~maxed out, while my RX570 produce ~60 h/s less than maxed out With a lot of details: Flash your GPU BIOS with SRBPimp + ati flash. (make sure you save the original BIOS per card (yeah, even for the same brand/type/series/serialnumber/etc they might differ, I have 3 identical cards, bought at the same time, each with different original BIOS) Choose your miner, and apply possible best miner settings: SRBminer, use defaults as a good start, (my first choice for testing to get good base clock and voltage settings) TRMminer, use defaults as a good start, or read here XMR-stak, defaults suck, you need to google for this, stroll on reddit, check xmrstak.com, read through all open en clossed issues Make some spreadsheet to log everything you change, and the effects on hash and memory errors of it. example log: Vary only 1 item for each test, otherwise you don't know what is causing the changes Start with defaults, or known OK clocks. Make runs of say 10 - 15 minutes each, if too many errors, or miner doesn't work OK, just go back to the last setting that worked, and end the run. Apply new settings just before reboot. Always reboot. Why those long runs? I make the miner start directly after reboot, so Windows and other stuff will still be starting Max hash can take a couple of minutes to be reached. I want a sufficient duration to get a good view of the amount of memory errors per hour (MER/h), as I accept 1 - 4 MER/h max, as long as it doesn't cause errors in the miner. A limited amount of errors does in general not affect your hash rate. Having some MER over time, indicate that you are actually on the maximum possible for a card. If you don't get any, you havent maxed out your card... In the mean time, you can do something useful, like writing this crap, or do laundry... Why always reboot? Crash and/or settings reset in general cause lower hashes Closing miner, and restarting in general won't bring you back to max hash Disableing + Reenabling GPU via device manager (or script) is not (even a 80%) guarantee the GPU is back how it should work Changing GPU settings often needs a reboot, especially when it has been under load before. Changing GPU settings while mining will not give you the results you need, or crash your miner, etc. In the end it saves you time making runs that are actually bogus. (Maybe tune a bit with the default miner settings, but discussing that here is not the goal) Every GPU will have different best settings, not one card is the same, but similar cards, will have close to similar settings. Find your max possible hash based your GPU properties (stable hash) (log each step/change): Set / change GPU clocks and voltages using OverdriveNTool, (ODNT) for RX5XX atleast, leave Core P1, P2 and P7 active, (deactivate others by a click on the PX). First 2 postions are locked in register anyway, and provide a stable, low power draw for when your card is not mining for some reason, and therefore not pulling tons of power. For the memory, deactivate position P2. Use all default clocks and voltages, maybe cut core clock already back to 900mV - 950mV Increase memory clocks in steps of 50 Mhz if you are in a hurry, and do 25 Mhz step back if you notice too much issues , otherwise just use 25 Mhz increases. (Memory clocks are the biggest factor in maximum hash) For each increase, run for 10-15 min, log hash, power draw, settings, MER/h, and possible other notes like miner settings, BIOS flash etc. Get some MC with little to no MER/h, and a bit more Mhz will increase the number of MER/h a lot, then you got your max MC on your card. Cut down your memory voltage in steps of 25 mV, and if needed use smaller steps of 12 mV (use values like X12, X25, X37, X50, X62, X75, X87, X00), till you notice a loss in hash, a crashing miner, or a increase in MER/h. (what I noticed, is that the MV lower limit is basically the same for all realistic MC for a typical GPU). Tips on miners: TRM miner needs in general like 25 mV more MV and CV compared to SRB, while the power draw won't increase much. A little more (like 12-25 mV juice here can also improve hash by 10%). SRBminer is great for all its features and simplicity for tuning. Stak is on that part a disaster. Tips on rig components: Use a decent PSU, 80Plus Golds are definitely worth it if you tend to run it for a year or longer. 80Plus Golds are about 5% more efficient than 80Plus Bronze. At say a power draw of 800W, or 800W / 1000 * $0.10 * 24h * 365.24... * 5% = $35.06 savings per year. So you can easily spend that $70 more on a great PSU instead of that crappy $30 PSU that probably will burn your house down too. Dont run your PSU at 100% power, but stick with about 60% load. This means 3% better efficiency on Corsair PSUs (so not even for the cheap ones), or about $21/year gain based on above, making it worth to just get that bigger PSU! Buy your PSU based on 90% of total TDP, as with undervolting you can bring it back to ~50-60%, and wont overload the PSU when all your GPUs reset to defaults, under full load. Plus side of those more expensive PSUs, the come with overheat, short-circuit and what not protection, and it probably will save you a new motherboard for wrong made connections etc. Current SSDs use about 5x less power than a current HDD, older ones can easily go up to 10x, maybe saving you $4/year. Recently I got an 120GB SSD for $25, while the HDDs where larger, and more expensive. As you will be using large page files, so memory not only on the RAM but on the disk, the drives will be loaded continuously. CPU, get the new cheapest ones, mining on CPU is not profitable in general. Newer CPUs use easily 10W less power when idle than an old one of 5 - 10 years ago. Risers and cables, don't go for the really cheap ones, and get some spare items too because you can count on it some will fail...
  20. This post cannot be displayed because it is in a password protected forum. Enter Password
  21. This post cannot be displayed because it is in a password protected forum. Enter Password
  1. Load more activity

Announcements



×
×
  • Create New...