Does anyone know what is going on at pom.m-hash.com? Almost everything I mine this week has being orphaned I was getting 1 some times 2 coin a day and I only got one this week.
I hate to keep asking about this but this is crazy I've minded all week and have not got 1 coin. I normally get 1 sometimes 2 a day everything is going orphaned. I have not changed anything on my end. example current round 7358 share valid 4 Invalid. Go over to translations every blocks tx's are orphaned and 0 earnings.
Are you in a pool?
Or solo mining? (If solo what's your total hashrate?)
I'm in a small pool (https://www.coinsump.com/xmg.php) and getting 5-8 blocks a day with the pool having around 2Mh/s hashrate. We are getting the odd Orphan (4 in the past week or so). But it's not a huge number.
If you are solo mining and every block fond is "Orphaned" then you're on the wrong blockchain. You need to re-sync using the following instructions :
Code:
1) Make backup of your wallet.dat
2) Delete peers.dat
3) Delete folder blocks
4) Delete folder database
5) Download latest Wallet : https://www.m-core.org/bin/m-wallet-1.4.6.2/
6) Download official chain: https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
7) Extract the zip-file and put the two folder “database” and “blocks” into your .magi folder
8) Adjust the magi.conf to:
- Remove ALL “addnode”
- Remove ALL “connect”
+ change (or add): listen=0
+ add: connect=104.128.225.215
9 ) Start the magid (wallet)
(*note*: If you are getting no connect or disconnect, you are then temporary banned on the masternode. Then you have stop your magid (wallet) to wait for x hours or change your public IP. Then start magid (wallet) again)
10) When you are in sync with the 104.128.225.215 (you can look at the poolinfo (poolinfo.systms.org) to see if you are in sync with the master) then you run: checkwallet and repairwallet
If you're in a pool, get in contact with the pool owner and ask them to update their wallet.
*note* invalid shares are ok if you're not getting over 10%. If you are, then check your connection. I had an rpi3 on plastic 10mm insulated legs on a metal shelf and the wireless connection threw 20%-25% invalid shares. Once I raised it away from the metal shelf by another 40mm I stopped getting invalid shares.
