Still a 2.3MH/s whale in m-hash. I thought that pool was like the MAIN PoM pool? Is no one monitoring it at all?

I think Im done mining for good, once everything came back there is 200+MH/s now with the sweet spot being like 40-50? Pfft. Nothing but .25 xmg to split. I went from making 1-2 XMG a day to not ever getting .30/day. Not worth anyone's time unless theyre getting free energy.

The pool owner who posted said ~412 XMG the whales took, even at a .25/block payout, in FORTY FIVE MINUTES. That's 400+ bucks an hour, to one person, from one pool. I mean, cool they got tons of machines to use, but meh, Magi can't call itself green/ecofriendly any longer. If anything, this way they're burning MORE energy than normal.

Hmm ... maths. Let say network energy use, at optimal levels, is 100KWh. Now, let's assume 1 Block per half hour being found, that is 2 blocks/hour. This results in a max payout of ~40 XMG. That is a total of .4KWh/XMG.

Now, we're pushing GOBS of hashpower at the thing. Dropping 2 blocks, worth .50 XMG, for the same 100KWh. That is 50KWh/XMG, 50KWh of energy to find ~.35 cents of XMG ... All being ran 24/7. The entire chain will eat up YEARS of electricity and might even account for a small increase in global temp (Im talking hundredths of a degree, but a rise nonetheless.) IOW, not eco-friendly.

Exactly the same problem. I tried Debian 8/9, Win x86, all go to crash. No matter the binary I take, or compile by myself (compile only on Debian 8 ). Win x64 seems not crash, but also not sync.
Wallet 1.4.5.2

just cd to magi folder
wget https://github.com/filoozom/magi/commit/2ffa778bf7be59a4da76bd1d56b77a133ce795ef.patch
git apply 2ffa778bf7be59a4da76bd1d56b77a133ce795ef.patch