XMR: Moving from Minergate to mineXMR

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

cafcwest

Member
Feb 15, 2013
136
14
18
Richmond, VA
Hello all,

After reading the comments here and elsewhere, and constantly not achieving what mining calculators said I should be achieving, last week I moved my 9 miners to mineXMR.com. For reference, I have 5 Xeon 5600 era Windows servers running Stak-CPU, 3 of the same server running Ubuntu and Wolf's, and a single quad-AMD machine with Ubuntu also running Wolf's. Total capability is about 4.5KH/s.

For the first two days, I simply changed the payment address from my Minergate email address to a wallet address for a MyMonero wallet. I did not, and still do not see any balance from these two days of mining (should be about 0.6XMR). When I log into that wallet, I receive the message "Your account is catching up, your details may be out-of-date until it is finished (10 blocks behind)".

Friday I downloaded the official Monero GUI onto a spare machine and allowed it to fully synchronize. Once that completed, I swapped all of my miners over to this new wallet address. This has been running since Saturday, and yet I still show 0.0XMR balance.

What's up? Am I missing something super obvious? mineXMR says standard minimum payment is 0.5XMR - which I certainly should have mined by now, why don't I have that in my wallet?

My Stak config:

Code:
/*
 * Thread configuration for each thread. Make sure it matches the number above.
 * low_power_mode - This mode will double the cache usage, and double the single thread performance. It will
 *                  consume much less power (as less cores are working), but will max out at around 80-85% of
 *                  the maximum performance.
 *
 * no_prefetch -    Some sytems can gain up to extra 5% here, but sometimes it will have no difference or make
 *                  things slower.
 *
 * affine_to_cpu -  This can be either false (no affinity), or the CPU core number. Note that on hyperthreading
 *                  systems it is better to assign threads to physical cores. On Windows this usually means selecting
 *                  even or odd numbered cpu numbers. For Linux it will be usually the lower CPU numbers, so for a 4
 *                  physical core CPU you should select cpu numbers 0-3.
 *
 * On the first run the miner will look at your system and suggest a basic configuration that will work,
 * you can try to tweak it from there to get the best performance.
 *
 * A filled out configuration should look like this:
 * "cpu_threads_conf" :
 * [
 *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
 *      { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
 * ],
 */
"cpu_threads_conf" :
  [
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 4 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 6 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 8 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 10 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 12 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 14 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 16 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 18 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 20 },
       { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 22 },
  ],

/*
 * LARGE PAGE SUPPORT
 * Lare pages need a properly set up OS. It can be difficult if you are not used to systems administation,
 * but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is
 * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
 * on Windows, please read the common issues in the README.
 *
 * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
 * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
 *
 * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
 * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
 * 3. Expand Security Settings, and then expand Local Policies.
 * 4. Select the User Rights Assignment folder.
 * 5. The policies will be displayed in the details pane.
 * 6. In the pane, double-click Lock pages in memory.
 * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
 * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
 * 9. Reboot for change to take effect.
 *
 * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
 * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
 *
 * On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
 * ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
 * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
 * recommended for security reasons.
 *
 * Memory locking means that the kernel can't swap out the page to disk - something that is unlikey to happen on a
 * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
 * locked and unlocked memory. If that is your setup see option "no_mlck".
 */

/*
 * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
 * always  - Don't even try to use large pages. Always use slow memory.
 * warn    - We will try to use large pages, but fall back to slow memory if that fails.
 * no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
 *           It will never use slow memory, but it won't attempt to mlock
 * never   - If we fail to allocate large pages we will print an error and exit.
 */
"use_slow_memory" : "warn",

/*
 * NiceHash mode
 * nicehash_nonce - Limit the noce to 3 bytes as required by nicehash. This cuts all the safety margins, and
 *                  if a block isn't found within 30 minutes then you might run into nonce collisions. Number
 *                  of threads in this mode is hard-limited to 32.
 */
"nicehash_nonce" : false,

/*
 * TLS Settings
 * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
 * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
 *
 * use_tls         - This option will make us connect using Transport Layer Security.
 * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
 * tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
 */
"use_tls" : false,
"tls_secure_algo" : true,
"tls_fingerprint" : "",

/*
 * pool_address      - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
 * wallet_address - Your wallet, or pool login.
 * pool_password  - Can be empty in most cases or "x".
 */
"pool_address" : "pool.minexmr.com:7777",
"wallet_address" : "42cDgrUAE6X2p4RE2x7A7FczB87RL1HS8Ejrww98PtbWJXz3rb4fq2zRX3ka1cCut43GQR145wfC4aYVUvwR17t4GyfkWmk.C1N1HRV",
"pool_password" : "x",

/*
 * Network timeouts.
 * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
 * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
 * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
 * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
 * server usually takes to process our calls.
 *
 * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
 * retry_time    - How long should we wait before another connection attempt.
 *                Both values are in seconds.
 * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
 *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
 */
"call_timeout" : 10,
"retry_time" : 10,
"giveup_limit" : 0,

/*
 * Output control.
 * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
 * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
 * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
 * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
 *
 * verbose_level - 0 - Don't print anything.
 *                 1 - Print intro, connection event, disconnect event
 *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
 *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
 *                 4 - All of level 3, and automatic hashrate report printing
 */
"verbose_level" : 3,

/*
 * Automatic hashrate report
 *
 * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
 *                This option has no effect if verbose_level is not 4.
 */
"h_print_time" : 60,

/*
 * Output file
 *
 * output_file  - This option will log all output to a file.
 *
 */
"output_file" : "",

/*
 * Built-in web server
 * I like checking my hashrate on my phone. Don't you?
 * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
 * outside of your home network. Ports lower than 1024 on Linux systems will require root.
 *
 * httpd_port - Port we should listen on. Default, 0, will switch off the server.
 */
"httpd_port" : 0,

/*
 * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
 *               This setting will only be needed in 2020's. No need to worry about it now.
 */
"prefer_ipv4" : true,

Thanks!!
 

Marsh

Moderator
May 12, 2013
2,644
1,496
113
On the minxmr.com home page
Your Stats & Payment History
How much is your Pending Balance: ?
How much is your Total Paid: ?
 

cafcwest

Member
Feb 15, 2013
136
14
18
Richmond, VA
Hey Marsh, if you check back, is there something I need to do to 'apply' the personal threshold field? Made the change here but the page refreshes every few minutes and go back to the default 2XMR value.
 

Marsh

Moderator
May 12, 2013
2,644
1,496
113
There is no apply button, just hit the < > button to change Personal Threshold (Editable): .

I think the default is something like 0.5 XMR , so it must accept your change.

BTW, I have it set to 5.0 XMR payout to avoid the unnecessary fee for each small amount of payout.
I mine ~ 1 XMR each day, and expect to be paid every 5 days.
 

cafcwest

Member
Feb 15, 2013
136
14
18
Richmond, VA
There is no apply button, just hit the < > button to change Personal Threshold (Editable): .

I think the default is something like 0.5 XMR , so it must accept your change.

BTW, I have it set to 5.0 XMR payout to avoid the unnecessary fee for each small amount of payout.
I mine ~ 1 XMR each day, and expect to be paid every 5 days.
Yup, it all makes sense now.

I found my MyMonero wallet that I had mined into for the two days at 0.491992321154 XMR. Going to hit it for 2 hours with my beefiest server to push it up to 0.5 - hopefully make that adjustment and get paid out, then switch back over to new wallet.

Darn shame XMR is tanking this evening, but this seems to be the pattern - every time it comes back stronger though!
 

spfoo

Member
May 23, 2017
102
16
18
I've been at MinerGate originaly as well. I can't understand how they can exist still - they steal enormously.
But since I moved to mineXMR I've been following my worker performances there and I see the stats are not matching the hash rates on my nodes. 10-20% seems to be missing. I use individual worker id's for all my nodes so it's easy to track. Anybody else seeing this?
 

spfoo

Member
May 23, 2017
102
16
18
The stats seem off but the earnings are inline with estimates for me. I'm hashing about 12K.
Looking at the stats closer it seems they are sometimes above and sometimes below expected values. So maybe the average is close to real. In any case minexmr is very different from water.. I mean ... minergate.
 

Klee

Well-Known Member
Jun 2, 2016
1,289
396
83
I've been at MinerGate originaly as well. I can't understand how they can exist still - they steal enormously.
But since I moved to mineXMR I've been following my worker performances there and I see the stats are not matching the hash rates on my nodes. 10-20% seems to be missing. I use individual worker id's for all my nodes so it's easy to track. Anybody else seeing this?

Its EASY to install and use on Windows and Linux, thats why so many start with it.

I used it for two weeks and realized something was very fishy with my payouts.

Then I installed Wolfs then XMR-STAK and been on mineXMR since.
 

spfoo

Member
May 23, 2017
102
16
18
If anyone is interested, working on a miner monitoring tool that works with MineXMR. Sends email notifications on workers not hashing, payouts, etc.
Interesting. I've been planning to do the same. Which platform are you using for the tool? Just since my last MS Windows was 3.1. I switched to Linux kind of early - at kernel 1.0.