|
1 | | -# rieMiner 0.9β1 |
| 1 | +# rieMiner 0.9β1.5 |
2 | 2 |
|
3 | 3 | rieMiner is a Riecoin miner supporting both solo and pooled mining, and using the latest known mining algorithm. It was originally adapted and refactored from gatra's cpuminer-rminerd (https://github.com/gatra/cpuminer-rminerd) and dave-andersen's fastrie (https://github.com/dave-andersen/fastrie). |
4 | 4 |
|
5 | | -Solo mining is done using the GetWork or the GetBlockTemplate protocol, while pooled mining is via the Stratum protocol. |
6 | | - |
7 | | -A benchmark mode is also proposed to compare more easily the performance between different computers. |
| 5 | +Solo mining is done using the GetBlockTemplate protocol, while pooled mining is via the Stratum protocol. A benchmark mode is also proposed to compare more easily the performance between different computers. |
8 | 6 |
|
9 | 7 | Official binaries will be distributed when the stable 0.9 code is out (which will not until Riecoin Core is officially updated). |
10 | 8 |
|
11 | 9 | This README also serves as manual for rieMiner. I hope that this program will be useful for you! Happy mining! |
12 | 10 |
|
13 | | -**Warning**: rieMiner 0.9β1 is the last version officially supporting the 0.10.2 wallet. It might work in future versions, but only the upcoming new Riecoin wallet will be tested for solo mining. GetWork support will also be removed. |
14 | | - |
15 | 11 |  |
16 | 12 |
|
17 | 13 | ## Compile this program |
@@ -114,14 +110,15 @@ It is case sensitive, but spaces and invalid lines are ignored. If an option or |
114 | 110 | * Port : port of the Riecoin wallet/server or pool. Default: 28332 (default port for Riecoin-Qt); |
115 | 111 | * User : username used to connect in the server (rpcuser for solo mining). Includes the worker name (user.worker) if using Stratum. Default: nothing; |
116 | 112 | * Pass : password used to connect in the server (rpcpassword for solo mining). Default: nothing; |
117 | | -* Protocol : protocol to use: GetBlockTemplate or GetWork for solo mining, Stratum for pooled mining, Benchmark for testing. Default: Benchmark; |
| 113 | +* Protocol : protocol to use: GetBlockTemplate for solo mining, Stratum for pooled mining, Benchmark for testing. Default: Benchmark; |
118 | 114 | * Address : custom payout address for solo mining (GetBlockTemplate only). Default: a donation address; |
119 | 115 | * Threads : number of threads used for mining. Default: 8; |
120 | 116 | * Sieve : size of the sieve table used for mining. Use a bigger number if you have more RAM, as you will obtain better results: this will usually reduce the ratio between the n-tuple and n+1-tuples counts. It can go up to 2^64 - 1, but setting this at more than a few billions will be too much and decrease performance. Default: 2^30; |
121 | 117 | * Tuples : for solo mining, submit not only blocks (6-tuples) but also k-tuples of at least the given length. Its use will be explained later. Default: 6; |
122 | 118 | * Refresh : refresh rate of the stats in seconds. 0 to disable them; will only notify when a k-tuple or share (k > 4) is found, or when the network finds a block. Default: 30; |
123 | 119 | * TestDiff : only for Benchmark, sets the testing difficulty (must be from 265 to 32767). Default: 1600; |
124 | | -* TestTime : only for Benchmark, sets the testing duration in s. Default: 21600 (6 hours). |
| 120 | +* TestTime : only for Benchmark, sets the testing duration in s. 0 for no time limit. Default: 0; |
| 121 | +* Test3t : only for Benchmark, stops testing after finding this number of 3-tuples. 0 for no limit. Default: 1000. |
125 | 122 |
|
126 | 123 | You can finally run the newly created rieMiner executable using |
127 | 124 |
|
@@ -151,7 +148,7 @@ These results were obtained with a Ryzen R7 2700X at 3.7 GHz, and you can use th |
151 | 148 |
|
152 | 149 | For pooled mining, the number of primes "non consecutive tuples" are shown instead, and there is an estimation of how much RIC/day you are earning. If you want to compare the performance with fastrie, multiply the speeds by 4.096. The performance should be the same as fastrie's, as rieMiner uses the same algorithm. |
153 | 150 |
|
154 | | -rieMiner will also notify if it found a k-tuple (k > 3) in solo mining or a share in pooled mining, and if the network found a new block. If it finds a block or a share, it will show the full submission and tell if it was accepted (solo mining only) or not. For solo mining, if the block was accepted, the reward will be generated and sent to a new random address which is included in your wallet (when using GetWork), or the one specified (for GetBlockTemplate). You can then spend it after 100 confirmations. |
| 151 | +rieMiner will also notify if it found a k-tuple (k > 3) in solo mining or a share in pooled mining, and if the network found a new block. If it finds a block or a share, it will tell if the submission was accepted (solo mining only) or not. For solo mining, if the block was accepted, the reward will be generated for the address specified in the options. You can then spend it after 100 confirmations. |
155 | 152 |
|
156 | 153 | ## Solo mining specific information |
157 | 154 |
|
@@ -238,24 +235,24 @@ To compare two different platforms, you must absolutely test with the same diffi |
238 | 235 | * Standard Benchmark |
239 | 236 | * Difficulty of 1600; |
240 | 237 | * Sieve of 2^30 = 1073741824; |
241 | | - * Test during 6 hours; |
| 238 | + * Stop after finding 1000 3-tuples or more; |
242 | 239 | * The computer must not do anything else during testing; |
243 | | - * Imprecise for slow computers but more like the real mining conditions; |
244 | | - * The precision will be about 3 digits for the 2 and 3-tuples/s metrics, and 2 for the 4-tuples/s one, for computers finding at least 0.1 3-tuple/s; |
245 | | - * 5 and 6-tuples find rates should be discarded as they are too rare; |
246 | | - * 6 hours are needed to get a reproductible enough result, but you could also do execute the Standard Benchmark for a few minutes if you only want an order of magnitude of your computer speed. |
| 240 | + * Very long for slow computers, but like the real mining conditions; |
| 241 | + * The precision will be 2 solid digits for the 2-tuples/s metric, and almost 2 digits for the 3-tuples/s one (the 2nd will still vary a bit). That said, you can share your result with 3 significant digits for each; |
| 242 | + * It would not be enough to even obtain just one solid digit for the 4-tuples/s metric, so 4, 5 and 6-tuples find rates should be discarded. |
247 | 243 |
|
248 | | -If you do not want to test during 6 hours, or have a slow computer, other testing parameters are suggested: |
| 244 | +Testing a few times longer will not really improve the precision. You would need to find tens if not hundreds times more tuples to gain another significant digit for each metric, which would be really unpractical. In the other direction, if you have a slow computer or want a very fast test, you can reduce the difficulty to find tuples much faster with these parameters: |
249 | 245 |
|
250 | | -* Simplified Benchmark |
| 246 | +* Easy Benchmark |
251 | 247 | * Difficulty of 800; |
252 | 248 | * Sieve of 2^27 = 134217728; |
253 | | - * Test during 30 minutes; |
254 | | - * The computer should not do anything else during testing, and must not do any other heavy tasks; |
| 249 | + * Stop after finding 1000 3-tuples or more; |
| 250 | + * The computer must not do anything else during testing; |
255 | 251 | * Not adapted for powerful computers; |
256 | | - * The precision will be about 3 digits for the 2 and 3-tuples/s metrics, and 2 for the 4-tuples/s one, for computers finding at least 1 3-tuple/s; |
257 | | - * 5 and 6-tuples find rates should be discarded; |
258 | | - * Note that the results will be completely different to the ones provided by the standard benchmark. |
| 252 | + * The precision will be similar to Standard Benchmark, but note that the results will be completely different to the ones provided by the standard benchmark; |
| 253 | + * 4, 5 and 6-tuples find rates should also be discarded. |
| 254 | + |
| 255 | +In all cases, the system must not swap. Else, the result would not make much sense. Ensure that you have enough memory when trying to benchmark. |
259 | 256 |
|
260 | 257 | ## Miscellaneous |
261 | 258 |
|
@@ -285,6 +282,5 @@ Donations welcome: |
285 | 282 | * [Get the Riecoin wallet](http://riecoin.org/download.html) |
286 | 283 | * [Fast prime cluster search - or building a fast Riecoin miner (part 1)](https://da-data.blogspot.ch/2014/03/fast-prime-cluster-search-or-building.html), nice article by dave-andersen explaining how Riecoin works and how to build an efficient miner and the algorithms. Unfortunately, he never published part 2... |
287 | 284 | * [Riecoin FAQ](http://riecoin.org/faq.html) and [technical aspects](http://riecoin.org/about.html#tech) |
288 | | -* [Bitcoin Wiki - Getwork](https://en.bitcoin.it/wiki/Getwork) |
289 | 285 | * [Bitcoin Wiki - Getblocktemplate](https://en.bitcoin.it/wiki/Getblocktemplate) |
290 | 286 | * [Bitcoin Wiki - Stratum](https://en.bitcoin.it/wiki/Stratum_mining_protocol) |
0 commit comments