Crazy time again...
Do another resyncing

It seems xmgpool is on the right track.

Thanks for your support! 

You can check Network block from https://poolinfo.systms.org/ . If the pool does not match with Last Block at top, then the pool could be in a wrong fork. I just resyced xmgpool ( http://104.207.149.217 ) and already found two new blocks now.

It seems another fork? Hope the new version will fix it.

Just resyc the blockchain and cleaned the data. Blocks between 1478829 and 1478959 are orphaned.

I just set up a NOMP pool with MPOS as frontend. I also migrated all the accounts from xmgpool. Please check your account before mining. You can try the new pool at
xmg.luckypool.ml

stratum+tcp://xmg.luckypool.ml:3008            VarDiff: 4 (slow cpu 20kh/s)
stratum+tcp://xmg.luckypool.ml:3333          VarDiff: 32 (fast cpu 100kh/s)

luckypool detail transanctions
Tried auto payout and manual payout, no problem found.

Happy mining!

I messaged jcreyesb with detail transactions and it seemed the problem resolved since he didn't response my message.

After xmgpool reopened recently, there was some fork going on. So I may delete those orphan blocks from database by comparing with https://chainz.cryptoid.info/xmg. It seems most of the 700 could be related to orphan blocks. You already PMed me. So if you want to resolve the problem, then be reasonable and resolve it privately.

2) PoS & PoW blocks will be checked to make sure they follow a pattern, for example, in-between two PoW block are at least two PoS blocks; within continuous five blocks must be the occurrence of a PoW block.

3) Regarding PoW mining, I strongly believe the way we should be heading is the way we are right now. We might need to stick to the big vision, and fulfill the task as much as possible, by getting around the issues, or mitigating the impacts, but not by just turning off the source. From what I can see, without PoW will lead MAGI to nowhere. I propose a check on the PoW blocks on the overall network mining hashrate, say a total of 40MH/s will make all PoW blocks being rejected; in other words, PoW is turned off once network hashrate exceeds the limit, and back to life once below the limit. Until we figure out a better solution, this might help. Let me know the maximum hashrate you'd like.

2) and 3) are contradictable if hashrate >40MH for some time with more than 5 blocks? Or reject both PoW and PoS after 4 blocks until hashrate decline below 40MH. I think the limit should be adjusted dynamically to 2x or 1 1/2 x the normal hashrate(maybe 6 hour average hashrate) with an upper hard limit 90Mh.

Fee is changed back to 1%.

PM your username, wallet address, let me check.

Just tuned the apache server for better response for the website  http://104.207.149.217 . I will monitor it to see if it needs another tuning. Also add a link for the [xmgpool detail transaction] in the homepage for easy track with chainz.cryptoid.info. Automatically payout is made every half an hour.  

Just lower the xmgpool pool fee to 0.5% for this weekend. Enjoy mining!

Server upgraded. Should have no problem now.

I just found the web server apache2 takes too much resources. So I temporarily shut the website down. Need sometime to fix it.
You can check
https://chainz.cryptoid.info/xmg/address.dws?93vbq7qfqCZvvTmHMqrHfWMeXkmJaoDCmA.htm

After shutdown the apache2 server, the pool can find another block. I will lower the pool fee to 0.5% for some time after fix the apache2 problem.

Just fixed everything and made some performance tuning on the server.

Payout is enforced at xmgpool: http://104.207.149.217.

replace/put block, database under folder
windows      C:\Users\username\AppData\Roaming\Magi
Ubuntu        .magi

BTW, xmgpool is up. Need to fix orphan blocks for the frontend.

xmgpool is on another fork. You'd better use other pool right now.

I just restarted it. I do not know when it will have another fork.

The cpuminer-opt is faster unber Ubuntu. But the windows binary is slower. I do not know how to compile faster under window.

The pool is on another fork for that time. I just checked with
https://chainz.cryptoid.info/xmg/address.dws?93vbq7qfqCZvvTmHMqrHfWMeXkmJaoDCmA.htm

 to set those blocks as orphan. Bad luck on a wrong fork which is out of my control.

Agree!

I also need some time to figure out how to fix the database after some payouts with a wrong fork. Though I restarted the pool, the findblock will have errors with those wrong transactions.