daily pastebin goal
4%
SHARE
TWEET

Untitled

a guest Apr 16th, 2018 54 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. /*
  2.  * Network timeouts.
  3.  * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
  4.  * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
  5.  * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
  6.  * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
  7.  * server usually takes to process our calls.
  8.  *
  9.  * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
  10.  * retry_time   - How long should we wait before another connection attempt.
  11.  *                Both values are in seconds.
  12.  * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
  13.  *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
  14.  */
  15. "call_timeout" : 10,
  16. "retry_time" : 30,
  17. "giveup_limit" : 0,
  18.  
  19. /*
  20.  * Output control.
  21.  * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
  22.  * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
  23.  * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
  24.  * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
  25.  *
  26.  * verbose_level - 0 - Don't print anything.
  27.  *                 1 - Print intro, connection event, disconnect event
  28.  *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
  29.  *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
  30.  *                 4 - All of level 3, and automatic hashrate report printing
  31.  *
  32.  * print_motd    - Display messages from your pool operator in the hashrate result.
  33.  */
  34. "verbose_level" : 3,
  35. "print_motd" : true,
  36.  
  37. /*
  38.  * Automatic hashrate report
  39.  *
  40.  * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
  41.  *                This option has no effect if verbose_level is not 4.
  42.  */
  43. "h_print_time" : 60,
  44.  
  45. /*
  46.  * Manual hardware AES override
  47.  *
  48.  * Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
  49.  * to false to force disable AES or null to let the miner decide if AES is used.
  50.  *
  51.  * WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner.
  52.  */
  53. "aes_override" : null,
  54.  
  55. /*
  56.  * LARGE PAGE SUPPORT
  57.  * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
  58.  * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
  59.  * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
  60.  * on Windows, please read the common issues in the README.
  61.  *
  62.  * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
  63.  * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
  64.  *
  65.  * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
  66.  * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
  67.  * 3. Expand Security Settings, and then expand Local Policies.
  68.  * 4. Select the User Rights Assignment folder.
  69.  * 5. The policies will be displayed in the details pane.
  70.  * 6. In the pane, double-click Lock pages in memory.
  71.  * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
  72.  * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
  73.  * 9. Reboot for change to take effect.
  74.  *
  75.  * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
  76.  * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
  77.  *
  78.  * On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
  79.  * ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
  80.  * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
  81.  * recommended for security reasons.
  82.  *
  83.  * Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
  84.  * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
  85.  * locked and unlocked memory. If that is your setup see option "no_mlck".
  86.  */
  87.  
  88. /*
  89.  * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
  90.  * always  - Don't even try to use large pages. Always use slow memory.
  91.  * warn    - We will try to use large pages, but fall back to slow memory if that fails.
  92.  * no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
  93.  *           It will never use slow memory, but it won't attempt to mlock
  94.  * never   - If we fail to allocate large pages we will print an error and exit.
  95.  */
  96. "use_slow_memory" : "warn",
  97.  
  98. /*
  99.  * TLS Settings
  100.  * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
  101.  * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
  102.  *
  103.  * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
  104.  */
  105. "tls_secure_algo" : true,
  106.  
  107. /*
  108.  * Daemon mode
  109.  *
  110.  * If you are running the process in the background and you don't need the keyboard reports, set this to true.
  111.  * This should solve the hashrate problems on some emulated terminals.
  112.  */
  113. "daemon_mode" : false,
  114.  
  115. /*
  116.  * Buffered output control.
  117.  * When running the miner through a pipe, standard output is buffered. This means that the pipe won't read
  118.  * each output line immediately. This can cause delays when running in background.
  119.  * Set this option to true to flush stdout after each line, so it can be read immediately.
  120.  */
  121. "flush_stdout" : false,
  122.  
  123. /*
  124.  * Output file
  125.  *
  126.  * output_file  - This option will log all output to a file.
  127.  *
  128.  */
  129. "output_file" : "",
  130.  
  131. /*
  132.  * Built-in web server
  133.  * I like checking my hashrate on my phone. Don't you?
  134.  * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
  135.  * outside of your home network. Ports lower than 1024 on Linux systems will require root.
  136.  *
  137.  * httpd_port - Port we should listen on. Default, 0, will switch off the server.
  138.  */
  139. "httpd_port" : 0,
  140.  
  141. /*
  142.  * HTTP Authentication
  143.  *
  144.  * This allows you to set a password to keep people on the Internet from snooping on your hashrate.
  145.  * Keep in mind that this is based on HTTP Digest, which is based on MD5. To a determined attacker
  146.  * who is able to read your traffic it is as easy to break a bog door latch.
  147.  *
  148.  * http_login - Login. Empty login disables authentication.
  149.  * http_pass  - Password.
  150.  */
  151. "http_login" : "",
  152. "http_pass" : "",
  153.  
  154. /*
  155.  * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
  156.  *               This setting will only be needed in 2020's. No need to worry about it now.
  157.  */
  158. "prefer_ipv4" : true,
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top