Let's see... XMG has been delisted from nearly every exchange... The 2, maybe 3, that are still up and not eating transactions have very little volume. 
Pools are shutting down (some with no warning... looking at you m-hash)
Joe is MIA for what, nearly 3 years now?
While there has been a minor (community-made) update to the wallet, it still could benefit from further updates

The coin is pretty much on life support. Interest is still somehow there, but lacking some kind of development support it's hobbyware at this point.

source: minerclaim


lovely

From what I saw, it will be based on the Pi Zero W and that device only has half gig of RAM.

I was running the CLI wallet on one for a short time and with most unnecessary services disabled in Raspbian it was choking and struggling to keep in sync with the blockchain (CLI wallet uses, on average, 650-750 MB RAM). I guess if the GUI wallet is a bit more optimized, it might work but I'd stay away from this one device personally.

If you mean to download...

https://m-core.org/bin/block-chain/

There are probably ways, but it wouldn't be practical as you have pointed out.

Personally though, as I said here, 0.5xmg daily (average based on market value) is my break even. Whether the "whales" stay or go, makes no nevermind so long as I'm not operating at a loss.

For starters, the pools that have a hash limit should be enforcing it.

https://pom.m-hash.com/index.php?page=statistics&action=pool

Top 6, above 250 (user lida is consistently above). Granted #5 and #6 are barely and could be contributed to float.

https://magi.trasmamod.com/index.php?page=statistics&action=pool

#1 above 250.

Edit: the list could have changed since my post time... CBA to screenshot and whatnot, posting via my phone.

However, these users could just register a new account and split the hosts...

Then comes the rest of the pools with no fixed limit. You are asking them to impose an arbitrary value based on your disdain of high rate individuals. No where in the official documentation does it state a fixed hash limit. The short of it is "higher hash, lower rewards to keep things fair."

This has been discussed before (see page 924, or this link - https://bitcointalk.org/index.php?topic=735170.18460

A question posed back in August stills stands. What is reasonable (hashrate limit)? And just to sate my curiosity, why?

https://chainz.cryptoid.info/xmg/address.dws?9NtcPTmGbuHTj5DutHH5T9LSZG9GcBZi3p.htm

Wallet doesn't match the one in your sig line.


source: somewhere a couple pages back and here: https://www.reddit.com/r/coinmagi/comments/8kv07s/solo_mining_on_a_dozen_machines_how_do_i_confirm/dzarj8o

As I've said before, investment is a risk. I figured out a way to mitigate mine. The same method could have been employed by others should they have chosen to do so. Still can. If a pool is not performing to their expectations, move the miners to another pool or another coin.

However, I did lose a fair share as well due to not being able to manage my miners during my paying job time, especially during the chain splits... About half of what I earned ended up on the wrong split.

Also keep in mind that I only have ~110kh/s applied to this coin...

Well... Thanks to the chain issues over the last few weeks and a bit of management during that time (aka pool jumping), power is "paid" for the next 12 months.

The power consumption of my 9 SBCs (8 miners and 1 wallet) is less than a kW daily (between 0.7 and 0.9 kW). So long as a small-ish pool averages ~0.5 xmg daily, electricity is paid for... Actually it's less than that, but I prefer a little buffer to account for market price swings.

https://bitcointalk.org/index.php?topic=703657.0

See #9


First, freedom of speech does not apply to all countries. Secondly, if you own a website, you can do whatever you want in your webspace, as long as you do nothing illegal according to the laws in your country. This means the administrators of a website can choose to restrict communication to a single (or select few) language.

My mistake, I misinterpreted the address that is consistently showing up as being yours.

Edit:
Investment has risks. How you handle it is not for me to to say definitively, nor is it my problem. I can suggest things to possibly lessen the risk, but you choose to to listen or not.

Likewise. They probably got d/c'd as well and didn't realize  or haven't yet...


You're aware there is an issue, manage your rigs. Jump pools (or coins) if you notice something f*cky with the one you are on... Common sense.

I count 4 possible chains:

1) Minerclaim/Poolinfo/Joe's node (blockheight all match)
2) Trasma (different blockheight, mining sequential blocks)
3) xpoolx (another different blockheight, also sequential mining)
4) whatever Vitalik (guessing it is him) is doing as seen on CryptoID

Well, maybe 5 if you count m-hash before they hit the stop button.

I'd say whatever pool is mirroring .215 is on the correct chain (that'd be minerclaim for the time being). Although, minerclaim's stats are a bit messed. At the moment, pool hash is greater than network hash. Probably nothing...

My wallet is showing a similar blockheight to Dougy (3332 due to the time it took to type this up from my phone). Adjust your config and resync. While it goes against "decentralized," a central node is what we got to work with until whatever is broken is fixed.

No need to blow a gasket quite yet... Ain't hard to look at a few websites and compare things.

Edit: also, I imagine Joe is not responsible for maintaining pools. If he doesn't know, he doesn't need to respond to your inquiry.

Not the first time I've had to do a full resync (Wallet originally was on a Windows desktop, then found out the hard way a RPi Zero can't handle wallet duty, currently using an OrangePI PC for that task). Since then, I've had to resync a couple times... Reasons...

I have a copy of the 3042 chain from here: https://m-core.org/bin/block-chain/

Downloaded after the last update date listed on that page (but before today)...

Updated magi.conf to mirror the Trasma admin's advice using connect in lieu of add-node and switching off listen (see my previous post), deleted peers.dat, resynced. I have a single connection to I'm assuming Joe (if he runs .215) that is staying in sync with minerclaim and poolinfo at the moment...

Not much else I can say to that really...

I have in my magi.conf


add node is commented out for the time being (basically the ish from an earlier post)

Wallet is at (at the time of this post) 1823277

Trasma is at 1823132, xpoolx is at 1823148, minerclaim is staying in sync w/ the wallet...

Both Trasma and xpoolx are discovering sequential blocks... Probably safe to say those two are no longer on the "dev split," no?

m-hash shut off as well.

Mineproject appears to not be on the current chain after last week's fork.

Hashtech is offline, or at least their website is not responding.

https://bittrex.com/Status


If/when they start resyncing the chain, it could show up. Last update was at block 1805865 (or approx. 17k blocks behind).


Minerclaim is ~60 blocks behind m-hash/trasma/xpoolx so I'd wager no, not fixed... Or their confirmation system is being slow again (check a couple pages ago)

CryptoID hasn't fixed their chain database since the split last night so it won't exactly find yours (assuming it's a valid one to begin with) as they are ~1k blocks behind most pools. Edit: however it is recording new transactions under lower than actual block id's... Odd.

Appears to be. Xpoolx and minerclaim are ~20 blocks behind trasma/m-hash (or these 2 are ~20 blocks ahead...)

Luckypool is still on the last fork.

Mineproject is about 1k blocks behind... Probably still on the fork from a week ago?