Merge pull request #51 from BitPoolMining/Dev

Updated TRex and CryptoDredge

Author: saltyminer

BitPoolMiner/BitPoolMiner.csproj

@@ -33,14 +33,18 @@ SUPPORTED ALGORITHMS
   CryptoNightSaber (Bittube)
   CryptoNightV7
   CryptoNightV8    (Monero)
+  Dedal
   Exosis
   HMQ1725
   Lbk3
   Lyra2REv2
+  Lyra2REv3
+  Lyra2vc0ban
   Lyra2z
   NeoScrypt
   PHI1612
   Phi2
+  Pipe
   Polytimos
   Skein
   Skunkhash
@@ -49,6 +53,7 @@ SUPPORTED ALGORITHMS
   X16R
   X16S
   X17
+  X21S
   X22i
 
 QUICKSTART
@@ -78,15 +83,18 @@ COMMAND-LINE ARGUMENTS
                        cnsaber (BitTube)
                        cnv7
                        cnv8 (Monero)
+                       dedal
                        exosis
                        hmq1725
                        lbk3
                        lyra2v2
-                       lyra2v2-old (see the "Lyra2REv2 Issues" item)
+                       lyra2v3
+                       lyra2vc0ban
                        lyra2z
                        neoscrypt
                        phi
                        phi2
+                       pipe
                        polytimos
                        skein
                        skunk
@@ -95,6 +103,7 @@ COMMAND-LINE ARGUMENTS
                        x16r
                        x16s
                        x17
+                       x21s
                        x22i
   -d, --device         List of comma-separated device IDs to use for mining.
                        IDs are numbered 0,1...,N - 1
@@ -164,23 +173,14 @@ TROUBLESHOOTING
 
     Example:
 
-      CryptoDredge -a lyra2v2-old -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> --no-watchdog
+      CryptoDredge -a <ALGO> -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> --no-watchdog
 
-  4. Lyra2REv2 Issues
-
-    In case if you have issues with the current implementation of Lyra2REv2
-    (lyra2v2), you might want to try lyra2v2-old.
-
-    Example:
-
-      CryptoDredge -a lyra2v2-old -o stratum+tcp://<POOL> -u <WALLET_ADDRESS>
-
-  5. Several Instances After a While
+  4. Several Instances After a While
 
     It seems that you are using an own restart mechanism of CryptoDredge
     (see the "Watchdog" item).
 
-  6. Crash Reporting
+  5. 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.

BitPoolMiner/MinerApps/CryptoDredge_0.11.0/run-lyra2v2-nicehash.bat

@@ -1,3 +1,27 @@
+# Release 0.14.0 - (December 11, 2018)
+
+ * Improve X22i algorithm
+ * Improve Skunkhash algorithm
+ * Improve x16-like algorithms, as a secondary effect
+ * Add Lyra2REv3 algorithm
+ * Fix Dedal bug described in Numus 1.5.0.3 release
+ * Implement "histo" API method
+ * Add --no-nvml option to force NVML off
+
+# Release 0.13.0 - (December 1, 2018)
+
+ * Improve X22i algorithm
+ * Improve Skunkhash algorithm
+ * Add X21S algorithm
+ * Add Lyra2vc0ban algorithm
+ * Fix Exosis and Dedal algorithm when started from BLAKE
+ * Add color hash order for x16
+
+# Release 0.12.0 - (November 28, 2018)
+
+ * Add Pipe (UOUcoin) algorithm
+ * Add Dedal (Numus) algorithm
+
 # Release 0.11.0 - (November 21, 2018)
 
  * Improve following algorithms (Up to 4%)

BitPoolMiner/MinerApps/CryptoDredge_0.11.0/run-mona-bsod.bat

@@ -0,0 +1,4 @@
+@echo off
+title Lyra2REvc0ban (c0ban) - pecadol pool
+CryptoDredge -a lyra2vc0ban -o stratum+tcp://pool.pecadol.xyz:4534 -u WALLET_ADDRESS -p c=RYO
+pause