Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 1,590
» Latest member: Breezey
» Forum threads: 384
» Forum posts: 2,181

Full Statistics

Online Users
There are currently 20 online users.
» 0 Member(s) | 20 Guest(s)

Latest Threads
XMR-STAK-RX - Free Random...
Forum: CryptoCurrency
Last Post: Monet
4 hours ago
» Replies: 0
» Views: 5
T-Rex 0.14.6 NVIDIA GPU m...
Forum: CryptoCurrency
Last Post: Monet
Yesterday, 03:04 PM
» Replies: 0
» Views: 22
Review nhà cái 22bet cho ...
Forum: WUG Discussions
Last Post: hieu16005
Yesterday, 06:56 AM
» Replies: 0
» Views: 14
GrinGoldMiner Windows min...
Forum: CryptoCurrency
Last Post: Monet
12-04-2019, 05:42 PM
» Replies: 0
» Views: 36
WildRig Multi 0.20.1: AMD...
Forum: CryptoCurrency
Last Post: Monet
12-02-2019, 05:55 PM
» Replies: 0
» Views: 39
The Skywallet has landed
Forum: News
Last Post: skyguy
12-01-2019, 09:26 PM
» Replies: 0
» Views: 62
Nanominer v1.6.3:Ethash,C...
Forum: CryptoCurrency
Last Post: Monet
11-28-2019, 01:28 PM
» Replies: 0
» Views: 56
EthMonitoring \ EthContro...
Forum: CryptoCurrency
Last Post: Monet
11-26-2019, 10:04 AM
» Replies: 0
» Views: 60
TT-Miner 3.1.0: Win & Lin...
Forum: CryptoCurrency
Last Post: Monet
11-22-2019, 08:07 AM
» Replies: 0
» Views: 60
Claymore's CryptoNote Win...
Forum: CryptoCurrency
Last Post: Monet
11-20-2019, 05:19 PM
» Replies: 0
» Views: 47

 
  CryptoDredge 0.22 — NVIDIA GPU Miner
Posted by: Monet - 11-04-2019, 07:25 PM - Forum: CryptoCurrency - No Replies

Downloads

Windows Download

(CUDA 9.1 version)
(CUDA 9.2 version)
(CUDA 10.0 version)

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

Devfee
Developer fee is 1% (2% for MTP)

Supported Algorithms


  • Allium

  • Argon2d (250/4096/DYN/NIM)

  • BCD

  • BitCore

  • CryptoLightV7 (Aeon)

  • CryptoNightFastV2 (Masari and Stellite)

  • CryptoNightGPU

  • CryptoNightHaven

  • CryptoNightHeavy

  • CryptoNightSaber (Bittube)

  • CryptoNightTurtle

  • CryptoNightV8

  • Cuckaroo29 (Grin)

  • CuckooCycle (Aeternity)

  • HMQ1725

  • Lyra2REv3

  • Lyra2vc0ban

  • Lyra2z

  • Lyra2zz (LAPO)

  • MTP (see the MTP Algorithm item)

  • NeoScrypt

  • Phi2

  • Pipe

  • Skunkhash

  • Tribus

  • X16R

  • X16RT

  • X16S

  • X17

  • X21S

  • X22i
QuickStart

The current version of CryptoDredge is a (portable) console application. Unpack the downloaded archive and edit one of the sample .bat/.sh files or provide the necessary command line arguments.
Example:
Code:
CryptoDredge -a <ALGO> -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> -p <OPTIONS>

Command-Line Arguments
-v--version Print version information
-a--algo Specify algorithm to use

  • aeon

  • aeternity

  • allium

  • argon2d-dyn

  • argon2d-nim

  • argon2d250

  • argon2d4096

  • bcd

  • bitcore

  • cnfast2

  • cngpu

  • cnhaven

  • cnheavy

  • cnsaber

  • cnturtle

  • cnv8

  • cuckaroo29

  • hmq1725

  • lyra2v3

  • lyra2vc0ban

  • lyra2z

  • lyra2zz

  • mtp

  • neoscrypt

  • phi2

  • pipe

  • skunk

  • tribus

  • x16r

  • x16rt

  • x16s

  • x17

  • x21s

  • x22i
-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)

  • ccminer-ws (WebSocket)

  • off
-b--api-bind IP[Image: clear.png]ort 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 Requirements

  • NVIDIA GPUs with Compute Capability 5.0 or above.

  • MTP require graphics card with at least 5Gb memory.

  • Latest GeForce driver

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

  • Internet connection
Windows

  • Windows 7/8.1/10 (64-bit versions)

  • Visual C++ Redistributable for Visual Studio 2015
Linux

  • Ubuntu 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
Notes

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

Rejected Shares
There are many reasons for rejected shares. The primary reasons are:

  • high network latency

  • overloaded mining server

  • aggressive graphics card overclocking
Watchdog
If you are using a third-party watchdog, you can disable the built-in watchdog by using --no-watchdog option.

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

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

Crash Reporting
If 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 version

  • Driver version

  • Miner configuration

  • Application crash data
MTP Algorithm

System Requirements:

  • GPUs with at least 5 GB of memory

  • There 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) Algorithm

If you encounter many "invalid share: invalid pow" errors from the pool, set --hashrate option to calculate the start difficulty.

Print this item

  [ANN] TeamRedMiner 0.5.9 - AMD GPU Miner for Grin, MTP, x16rv2 and more
Posted by: Monet - 11-04-2019, 07:17 AM - Forum: CryptoCurrency - No Replies

teamredminer v0.5.9 Release
This 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.9

API: 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.10
Slight performace improvement for Vegas on lyra2rev3
Pool 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.9
Added support for lyra2rev3 on amdgpu-pro and windows. ROCm support coming in later version.
Fixed API bug with not reporting dead GPUs

Changes in v0.3.8
Added 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 cards
Added 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.7
Redesigned 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.6
Added support for Rx550 cards (gfx804).
Improved stability on larger rigs, especially with weaker cpus.
Improved error reporting on failed initialization.

Changes in v0.3.5
Changed 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.4
Added CryptoNight v8 (CNv2) support
Changed stats display to include pool hashrate and better formatting
Added parallel GPU initialization
Added 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.3
ROCm support reintroduced
API support based on the sgminer API
Improved GPU platform detection
PCIe bus id printed on startup and is available over API
Added option for periodic stats interval

Changes in v0.3.2
Added windows support/build
Added vega PAL driver support
Removed ROCm support (temporarily)
Removed libjansson dependency

Changes in v0.3.1
Fixed phi2 issues with rejected shares and low pool-side hashrate.

Print this item

  SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching
Posted by: Monet - 11-02-2019, 07:05 PM - Forum: CryptoCurrency - No Replies

SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

Windows only

Download V1.9.3:


Mega : https://mega.nz/#F!RagwQKYA!dsK7FFIA_gTsNG5q4McjdA

DevFee only 0.85%
Windows only
Supports Nicehash & SSL/TLS encrypted connections
------------------------------------------------------------------------------------------------------------

============================================================
Significant hashrate increase (up to 15%) on VEGA56/64/FE/VII
Small hashrate increase on RX cards
Please read the TWEAKING PROFILES section
============================================================

Supports Nicehash & SSL/TLS encrypted connections
------------------------------------------------------------------------------------------------------------

============================================================
Significant hashrate increase (up to 15%) on VEGA56/64/FE/VII
Small hashrate increase on RX cards

ATTENTION:

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

Recommended driver:
Adrenalin 18.6.1

Supported algos:

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

DevFee:

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

Extra:

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

Tips:

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

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

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

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

lite

litev7
+Turtlecoin
+Iridium
+Aeon

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

bittubev2
+Ipbc/BitTube

artocash
+Artocash

alloy
+Alloy

marketcash
+MarketCash

b2n
+Bitcoin2Network

stellitev4
+Stellite

fast
+Masari

haven
+Haven

italo
+ItaloCoin (from block 55.000)

Update infos :

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

SRB-RESTARTER
------------------------------------------------------------------------------------------------------------
SRB-Restarter is a tool that monitors the main SRBMiner process, and if it's not running for some reason (like an app crash for example), it will run the script you specify (restart miner).

Only 3 parameters :

--interval value_in_seconds [def. is 10]
Specifies how often to check is the SRBMiner process running

--instance number
Use it if you run multiple SRBMiner instances on the same machine, example is below
You must use the following file naming :
SRBMiner-CN-n.exe where n is the instance number

--run filename [name of .bat file to run]
Name of .bat you want to run if SRBMiner process in not running


Note:
Miner is considered 'not running' after 2 checks!

Examples:

1.
SRB-Restarter.exe
[This will set interval to 10 seconds, and start.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN.exe]

2.
SRB-Restarter.exe --interval 5 --run turtle-coin.bat
[This will set interval to 5 seconds and run turtle-coin.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN.exe]

3.
SRB-Restarter.exe --interval 30 --run start-heavy.bat --instance 1
[This will set interval to 30 seconds and run start-heavy.bat if SRBMiner process is not running. It will monitor for a process named SRBMiner-CN-1.exe]

V1.9.3
- Fixed CN-Gpu algo compilation on RX 5700 and older GCN cards
- Improved CN-Gpu algo on Rx550/560 , Rx470/480/570/580/590
- 4gb Ellesmere cards got a small hashrate increase on CN-Conceal algo

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes

V1.9.1
- Added support for Navi10 (gfx1010)
- Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital algos have lower power consumption on Vegas with auto settings
- Hopefully fixed bug with invalid job id / same job id
- If more than 5 'invalid share' messages received from pool within same connection, auto miner restart
- Fixed cn-gpu hashrate (it was lower from v.1.8.8 -> my mistake)
- CN/R program precompilation process is now only logged, not displayed on screen

V1.9.0
- Added gpu ramp-up (slow start) possibility, so your PSU won't get suddenly overloaded (--enablegpurampup)
- Added low mode tweak profiles
- Added parameter --precompileblocks, which can set the number of blocks that get precompiled on CN/R algo
- Miner will try to restart if CN/R precompilation process takes more than 10 minutes for a gpu
- Minor bug fixes

V1.8.9
- Added tweaking profiles for RX 550/560, RX 470/480/570/580/590 - for some small fine tuning of existing vbios straps
- Profiles 1-6 for Vegas are now a little lighter, 7-10 stayed same
- Added embedded binaries for some gpu's
- Added parameter --nobinaries, use it to disable usage of embedded binaries
- Fixed some bugs in GPU detection code
- Added more info to log when using tweaking profiles
- Added watchdog for too many invalid job results, switches to next pool if more than 5 within the same connection
- Usage of external tweaking tool is now allowed, so you can now fine tune a profile even more if you know how
- Minor bug fixes

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats

V1.8.7
- Improvements with tweak profile 10 on Vega64 with Samsung memory
- Fixed a bug with pool reconnect on job timeout
- job_timeout is now disabled by default, to enable it set a value > 0
- Fixed min_rig_speed bug that triggered restart with V4 algos
- Added info in api/web stats about tweak profile
- Made hashrate display on web stats page bigger
- In guided setup mode changed max wallet and password length to 200 so address+payment id can be used

V1.8.6
- Added tweaking support for Radeon VII
- There are now 10 tweaking profiles, so you can fine tune even more
- Fixed Cn/R when used on coin other than Monero
- Added new algo 'Upx2' , the new Uplexa algo
- Added fork info about Uplexa and Cypruscoin

V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found

V1.8.4
- Performance increase for Vega56/64/Fe/Vii up to 15%!
- Minimum for 'main_pool_reconnect' is now 60 seconds instead of 180
- Added new cmd parameters: --disabletweaking, --cgputweakprofile
- Added new config parameter: tweak_profile

V1.8.3
- maxnosharesent parameter is not used anymore by default, also it's max is moved to 24h
- In guided setup mode password can now be 120 characters long instead of 80 that was previously
- Adl2 is now auto set to older gpus
- Removed Webchain algo
- heavy_mode 3 is now the default
- Fixed stratum+ssl:// in pool url, now it recognises and sets tls to true if used
- Gpu id and bus id now displayed with every accepted/rejected share
- preparedata parameter now gives a small boost on Vegas for turtle, mox, heavy, gpu algos
- Added fork info for sumokoin from cn to cn/r
- Possible fix of random miner crash
- SRB-Restarter now shows date and is logging to a file

V1.8.2
- Upx and litev7 algos on auto settings now have more hashrate or lower power consumption, or both
- Reworked networking code, so probably get rid of a bug or two
- Another try to fix V4 algo crashing
- Maxnosharesent parameter default value is now 45 minutes

V1.8.1
- Fixed a bug that could crash miner if using CNV4 ® algo
- Fixed a bug that crashed miner if doing fast algo switching from CNV4 to any algo
- Stales are not displayed anymore by default, added parameter --showstales which turns back on the display of stale shares
- Changed --maxnosharesent default value from 15 minutes to 30
- Logging is now disabled by default in the example start.bat
- Added parameter --preparedata, which could pontentially make a small speed increase on weak GPU's, but also could make it worse. All algos except webchain

V1.8.0
- Added new algo 'Graft' (graft, cryptonight_graft, cryptonight_reversewaltz, cryptonight_v8_reversewaltz)
- Added cmd parameters giveuplimit, retrytime, mainpoolreconnect, minrigspeed, shutdowntemperature, rebootscriptgpuwatchdog, rebootscriptminrigspeed
- No more mixing of cmd line setup and config files, now it's one or the other
- It is enough to set ccryptonighttype, cpool, cwallet in cmd, gpu's will be auto setup

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

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

Print this item

  Zealot/Enemy (z-enemy) NVIDIA GPU miner (ver2.3 - support x16rv2).
Posted by: Monet - 11-01-2019, 06:54 PM - Forum: CryptoCurrency - No Replies

Zealot/Enemy (z-enemy) NVIDIA GPU miner.
x16r, x16s, Bitcore, Phi1612, Xevan ,Tribus , x17, c11, AeriumX, XDNA(hex), phi, phi2, skunk etc ..
=========================================================

[b]Z-ENEMY 2.3 From: Dk & Enemy (z-enemy)
 NEW

IMPORTANT:
For maximum performance make sure you have latest drivers
http://www.nvidia.com/Download/index.aspx

Changes:
- Performance improvement: +2-3% x16rv2 algo

[b][b]Windows[/b]: [/b]https://mega.nz/#F!UXxxgKra!7eB8pqiBr4xKyLsvO4yVOg
[/b]

_______________________________________________________________________________ _________

Z-ENEMY 2.2 From: Dk & Enemy (z-enemy)


IMPORTANT:
For maximum performance make sure you have latest drivers

Changes:
Added x16rv2 algo (Upcoming Ravencoin hardfork 1st Oct.)
- Added support for secure stratum+ssl connections. New --no-cert-verify key.
(Disable certificate errors check for ssl connections)
- Fixed GPU data error in json api (/hwinfo)
- Fixed phi2 bug on Cuda 10.1

=====

IMPORTANTRavencoin is switching to the new x16rv2 algorithm on October 1st. There will be a new version of our miner z-enemy-2.2 with x16rv2 released in advance before the hard fork date .

=====

Z-ENEMY 2.1 From: Dk & Enemy (z-enemy)

This version includes a new way to manage and monitor the miner.

Changes:
- Performance improvements: +4-5% most algos (x16r, x16s, x17, hex, bitcore, bcd...)
- Stability improvements

___________________________________________________________________________ ___________________

Z-ENEMY 2.00 From: Dk & Enemy (z-enemy)

This version includes a new way to manage and monitor the miner.

[Image: ?u=https%3A%2F%2Fcdn.discordapp.com%2Fat...CH9kjrdKsA]

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 improvements

Notes:
- For HTTP server --api-allow command line option isn't having any effect (for now?)

_________________________________

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 cards

Z-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 cards

Bugfixes:
- 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 [Image: clear.png]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-122test

Z-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.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 improvements

32-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 XDNA


Z-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 algos


LAST 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=16

Diff x16 can be calculated by mutliplying the following:
Number of 1060's multiplied by 3-4
Number of 70ti's or 80's multiply by 4-8
Number of 80ti's multiply by 6-12

example: If you have 3 1060's then diff would be 9-12
if you have 8 70ti's then your diff would be 48-96


Dev 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: EchFugBmwShaJh5FugShvEchSmdBmwHamWrlJh5KckSkeHam

Means 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 x

z-enemy -a x16r -o stratum+tcp ://yiimp eu:3636 -u RWgpF9GefjD_your_wallet_1gQmQjpYtYt.GTX950 -p d=3 -i 19

z-enemy -a bitcore -o stratum+tcp://yiimp eu:3556 -u 1D2dKSprpK_your_wallet_1wa8b2LnJ826uf -p x -i 20

Suprnova pool:

z-enemy -a x16r -o stratum+tcp //rvn suprnova cc:6667 -u your_Login.your_worker_name -p x -i 20


FAQ:

I cannot start miner, it says I'm missing msvcr120.dll?
Download and reinstall drivers from

My 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.xx

What 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 cards

Is there an easy way to auto restart miner if it crashes?
Yes, check our samples *.cmd file in windows build. Like:
Confusedtart
z-enemy -a phi -o stratum+tcp://pool bsod pw:6667 -u LQCifDiNV_YOUR_WALLET_F3CUqZJBa75123 -p x
goto start

Does 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

Print this item

  PhoenixMiner 4.7c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Posted by: Monet - 11-01-2019, 07:14 AM - Forum: CryptoCurrency - No Replies

Important message for everyone that is running older versions of PhoenixMiner (before 4.7):

Changes in version 4.7c (since 4.6c):

New kernels for Navi (RX5700) with better stability. Should solve the freezing and restarts that some miners are experiencing with Navi cards
Reduced VRAM usage for both AMD and Nvidia cards on Windows and Linux
Added command-line option -config to load a config.txt file. This allows combining command-line options and config.txt file.
Added support for mining QuarkChain (QKC) without DAG switching on devfee (use -coin qkc)
Added support for the latest AMD Windows drivers up to 19.10.1
Other small improvements and fixes.

PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual mining
Ethash/Ubqhash with Blake2s.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files.

Please note that PhoenixMiner is extensively tested on many mining rigs but there still may be some bugs.
Additionally, we are actively working on bringing many new features in the future releases.
If you encounter any problems or have feature requests, please post them here (in this thread).
We will do our best to answer in timely fashion.


1. Quick start

You can download PhoenixMiner 4.7c from here:


https://mega.nz/#F!EKhhBSIA!2wybVCXirXJ2NYariY5ziw (MEGA)

Examples of settings for different pools.

ethermine org (ETH):
PhoenixMiner.exe -pool eu1 ethermine org:4444 -pool2 us1 ethermine org:4444 -wal YourEthWalletAddress.WorkerName -proto 3
ethermine org (ETH, secure connection):
PhoenixMiner.exe -pool ssl: //eu1 ethermine org: 5555 -pool2 ssl: //us1 ethermine org: 5555 -wal YourEthWalletAddress.WorkerName -proto 3
ethpool org (ETH):
PhoenixMiner.exe -pool eu1 ethpool org:3333 -pool2 us1 ethpool org:3333 -wal YourEthWalletAddress.WorkerName -proto 3
dwarfpool com (ETH):
PhoenixMiner.exe -pool eth-eu dwarfpool com:8008 -wal YourEthWalletAddress / WorkerName -pass x
nanopool org (ETH):
PhoenixMiner.exe -pool eu1 nanopool org:9999 -wal YourEthWalletAddress / WorkerName -pass x
nicehash (ethash):
PhoenixMiner.exe -pool stratum + tcp: //daggerhashimoto eu nicehash com: 3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
f2pool (ETH):
PhoenixMiner.exe -epool eth f2pool com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName
miningpoolhub (ETH):
PhoenixMiner.exe -pool us-east ethash-hub miningpoolhub com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
coinotron com (ETH):
PhoenixMiner.exe -pool coinotron com:3344 -wal YourLoginName.WorkerName -pass x -proto 1
ethermine org (ETC):
PhoenixMiner.exe -pool eu1-etc ethermine org:4444 -wal YourEtcWalletAddress.WorkerName
dwarfpool com (EXP):
PhoenixMiner.exe -pool exp-eu dwarfpool com:8018 -wal YourExpWalletAddress / WorkerName
miningpoolhub (MUSIC):
PhoenixMiner.exe -pool europe ethash-hub miningpoolhub com:20585 -wal YourLoginName.WorkerName -pass x -proto 1
ubiqpool (UBIQ):
PhoenixMiner.exe -pool stratum + tcp: //eu ubiqpool io: 8008 -wal YourUbiqWalletAddress -pass x -worker WorkerName
minerpool net (PIRL):
PhoenixMiner.exe -pool pirl minerpool net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
dodopool com (Metaverse ETP):
PhoenixMiner.exe -pool etp dodopool com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass
minerpool net (Ellaism):
PhoenixMiner.exe -pool ella minerpool net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass x

Pool options:

3. Command-line arguments

Note that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore's miner.


-pool <host:port> Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal <wallet> Ethash wallet (some pools require appending of user name and/or worker)
-pass <password> Ethash password (most pools don't require it, use 'x' as password if unsure)
-worker <name> Ethash worker name (most pools accept it as part of wallet)
-proto <n> Selects the kind of stratum protocol for the ethash pool:
1: miner-proxy stratum spec (e.g. coinotron)
2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
3: qtminer (e.g. ethpool)
4: EthereumStratum/1.0.0 (e.g. nicehash)
5: EthereumStratum/2.0.0
-coin <coin> Ethash coin to use for devfee to avoid switching DAGs:

auto: Try to determine from the pool address (default)
eth: Ethereum
etc: Ethereum Classic
exp: Expanse
music: Musicoin
ubq: UBIQ
pirl: Pirl
ella: Ellaism
etp: Metaverse ETP
pgc: Pegascoin
akroma: Akroma
whale: WhaleCoin
vic: Victorium
nuko: Nekonium
mix: Mix
egem: EtherGem
aura: Aura
hbc: Hotelbyte Coin
gen: Genom
etz: EtherZero
clo: Callisto
dbix: DubaiCoin
moac: MOAC
etho: Ether-1
etcc: EtherCC
yoc: Yocoin
b2g: Bitcoiin2Gen
esn: Ethersocial
ath: Atheios
reosc: REOSC

4. Configuration files

Note that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum miner
so you can use your existing configuration files without any changes.

Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when running PhoenixMiner.exe.

You will find an example config.txt file in the PhoenixMiner's directory.

Instead of specifying the pool(s) directly on the command line, you can use another configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.txt file in the PhoenixMiner's directory).

For the dual mining pools, you can use the dpools.txt file, which has the same format as epools.txt
but for the secondary coin. You will find an example epools.txt file in the PhoenixMiner's directory.
Note that unlike the epools.txt, which is loaded each time when the miner starts, the dpools.txt file
is only read if you specify a dual mining pool on the command line with -dpool, or at least add
the -dcoin blake2s command-line option.

The advantages of using config.txt and epools.txt/dpools.txt files are:
- If you have multiple rigs, you can copy and paste all settings with these files
- If you control your rigs via remote control, you can change pools and even the miner options by
uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
the miner.

5. Remote monitoring and management

Phoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring and
management. This means that you can use any tools that are build to support Claymore's dual miner,
including the "Remote manager" application that is part of Claymore's dual miner package.

We are working on much more powerful and secure remote monitoring and control functionality and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.

Print this item

  Whitelist shows n/a for all 8 nodes
Posted by: radarlarry1 - 10-04-2019, 06:14 AM - Forum: Miscellaneous - No Replies

Ever since the change over to .com my miners are showing N/Aon the whitelist.  It's happened once in the past and all I had to do was a restart and it was all good.  This time I can't seem to get them going... or is something that is a result of changes that have been made.  Was there something new I was supposed to do?  A new flash for the SDs?  Any help is appreciated!

Print this item

Information UPDATE: MAINTENANCE WORK ON SKYWIRE
Posted by: skyguy - 09-16-2019, 05:58 AM - Forum: Miscellaneous - Replies (2)

We migrated the discovery node and currently we are running some tests so that everything is working as expected.

We need everyone to pay attention to this announcement and the others that will follow as we will ask everyone to switch to the new discovery node after the tests are done.

Shortly after this the whitelisting system will also be available on whitelist.skycoin.com for registration.

We ask again for your patience and understanding in this migration process .
Thank you!!!

Please join @SkywirePSA to get the latest announcements as we will keep you updated through this channel!!!

Print this item

  Skycoin Whitelisting page
Posted by: radarlarry1 - 09-09-2019, 07:06 PM - Forum: Skycoin Project - Replies (2)

Is anyone else having trouble accessing the whitelisting page?  I have not been able to get in for two days... at least.  Eventually it times out.  Hope this is the correct place to post this.  If not, I'm positive someone... everyone will let me know.

Print this item

  DIY Skyminer on raspberry pi devices
Posted by: mfnx - 07-11-2019, 11:15 AM - Forum: Skywire - Replies (3)

INTRO

I wrote some simple scripts to setup your skiminer on raspberries pi, available on github.

Here is a short and extremely easy tutorial to set up your skyminer using raspberry pi (RB) devices. I used Raspberries pi 3 B+ with OS raspbian lite.


FLASH YOUR SD CARD

I downloaded the official OS raspbian lite. I chose the lite version because we don't need a desktop environment, the install is faster, and occupies les space (less than 1Gb).

Flash your SD card from:

Before removing the SD card from your pc/mac, you can activate ssh by adding a file named ssh (no extension) to the visible part of the SD card. Upon the next reboot of your RB, ssh will be activated. From windows, use MobaXterm, PuTTY or similar to connect to your RB with ssh. If you can't figure out how to do this, connect a monitor and a keyboard to your RB and proceed to the next step.


FIRST BOOT AFTER INSTALL

Let's boot the RB.

If you did not activate ssh, you can simply connect a monitor (HDMI) and a keyboard (USB) to the RB. In that case, you first log in with user pi and password raspberry. Also, you can now activate ssh from your RB:

Code:
sudo touch /boot/ssh
reboot

Upon reboot, you will be able to connect to your RB with ssh as described above and get rid of the monitor and keyboard. You can continue the installation process without ssh. However, I recommend you use ssh in order to overcome problems like bad configured keyboards. Also, it's really more comfortable to use ssh.

You can now connect to your RB from any device connected to your local network. For Linux/Mac, open a terminal and write:

Code:
ssh pi@<IP_OF_YOUR_RB>

For windows, use MobaXterm, PuTTY or similar.

From here on, it doesn't matter whether you connect through ssh or use the RB with monitor and keyboard setup. Let's log into our RB.

The default password for the user pi is raspberry. Once logged in, you can reset that password with:

Code:
sudo passwd pi

Also, reset the password of the root, as we will need the root in the coming sections:

Code:
sudo passwd root

Other useful commands:

Code:
sudo -i # or simply su to become root
sudo raspi-config # to setup basic stuff like wifi connection, timezone, keyboard, etc


SKYWIRE MANAGER AND NODES

One RB must run the skywire manager which manages the skywire nodes. That same RB can also run a node. The installation described below is exactly the same for each RB. However, you have to choose which RB will run the manager:

  1. Choose the RB which will run the manager
  2. Make sure the RB is connected to your local network (with wifi or ethernet)
  3. From a browser on any device connected to your local network, go to your router (typically 192.168.1.1 or 192.168.0.1)
  4. Locate your RB and set its IP as static
  5. Write the static IP down. Let's call it STATIC_IP (we'll refer to it later).
This is important! It makes sure that the IP of your RB which runs the manager (i.e. STATIC_IP) does not change. That way, the other RB nodes will be able to find the manager easily.


INSTALLATION

This is actually the easiest part! Log into your RB providing your user (pi) and password, download the install scripts from github, and execute them. Once logged in:

Code:
# first install git to download the scripts from github
sudo apt-get install git

# cd to the directory we want to download the scripts
cd /home/pi # for example

# download the scripts
git clone https://github.com/MFnx/skywire.git
cd skywire # cd into the downloaded skywire folder

# become root
sudo -i

# execute the install script
bash setup.sh --all --manager-ip STATIC_IP # STATIC_IP is the IP you wrote down before

At the end, your RB will reboot. You can now remove the folder /home/pi/skywire if you want to. Do the same for each RB, using the same STATIC_IP every time. The skywire services are run automatically upon each rebooot of your RB (give it a minute or two), so you won't have to do that manually.


SKYWIRE MANAGER

You can access the skywire manager from a browser on any device connected to your local network. Just enter STATIC_IP:8000. There you'll be able to monitor your nodes (you'll find the public and private keys there).


WHITELIST YOUR MANAGER

https://github.com/skycoin/skywire/wiki/...ing-System

Print this item

  Zealot/Enemy (z-enemy) NVIDIA GPU miner (ver 2.0)
Posted by: Monet - 06-27-2019, 08:43 PM - Forum: CryptoCurrency - Replies (1)

Quote: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) NEW

This version includes a new way to manage and monitor the miner.

[Image: ?u=https%3A%2F%2Fcdn.discordapp.com%2Fat...g9Dn72hLMg]

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 improvements

Notes:
- 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_8w

Linux:
Cuda 10.0: https://mega.nz/#!UCQlSaJI!j_b7REMSVkp5SRDQP2PjaaEpcA7tYuwxJZGj0GJFoqs
Cuda 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 cards

Z-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 cards

Bugfixes:
- 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 [Image: clear.png]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-122test

Z-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 [Image: wink.gif]


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 improvements

32-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 XDNA


Z-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 algos


LAST 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.
AddedC11(-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=16

Diff x16 can be calculated by mutliplying the following:
Number of 1060's multiplied by 3-4
Number of 70ti's or 80's multiply by 4-8
Number of 80ti's multiply by 6-12

example: If you have 3 1060's then diff would be 9-12
if you have 8 70ti's then your diff would be 48-96


Dev 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 FastMedium 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: EchFugBmwShaJh5FugShvEchSmdBmwHamWrlJh5KckSkeHam

Means 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 x

z-enemy -a x16r -o stratum+tcp ://yiimp eu:3636 -u RWgpF9GefjD_your_wallet_1gQmQjpYtYt.GTX950 -p d=3 -i 19

z-enemy -a bitcore -o stratum+tcp://yiimp eu:3556 -u 1D2dKSprpK_your_wallet_1wa8b2LnJ826uf -p x -i 20

Suprnova pool:

z-enemy -a x16r -o stratum+tcp //rvn suprnova cc:6667 -u your_Login.your_worker_name -p x -i 20


FAQ:

I cannot start miner, it says I'm missing msvcr120.dll?
Download and reinstall drivers from http://www.nvidia.com/Download/index.aspx

My 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.xx

What 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 cards

Is there an easy way to auto restart miner if it crashes? 
Yes, check our samples *.cmd file in windows build. Like:
Confusedtart
z-enemy -a phi -o stratum+tcp://pool bsod pw:6667 -u LQCifDiNV_YOUR_WALLET_F3CUqZJBa75123 -p x
goto start

Does 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

Print this item