Hmm was there an update in the last month for xmg; that could potentially cause a fork?
Reason I'm asking is because posw just got xmg back online; after a little over a month so I withdrew for obvious reasons. Got met with this tx
https://poswallet.com/blockChain/xmg/844e16365cc2f838ad73709d04a28174ca8813648d6c43517d7b6f3c2061e19e/
This is my wallet on posw saying unsent:
https://chainz.cryptoid.info/xmg/address.dws?9PYMGXGGJrZjoMqzdY6u7uu6R8P52GEqqd.htm
Reason I'm asking is because posw just got xmg back online; after a little over a month so I withdrew for obvious reasons. Got met with this tx
https://poswallet.com/blockChain/xmg/844e16365cc2f838ad73709d04a28174ca8813648d6c43517d7b6f3c2061e19e/
This is my wallet on posw saying unsent:
https://chainz.cryptoid.info/xmg/address.dws?9PYMGXGGJrZjoMqzdY6u7uu6R8P52GEqqd.htm
There was an update from v1.2 to v1.3 which involves changing db to LevelDB for block chain. While it is not so obvious and clearly understood, there seems a tendency of fork when different users use different wallet versions. We don't see clear fork as of yet but there was a few reports of wallet-not-syncing, which might be the case of posw too. Obviously the issue is local, and not propagating over the network since those users were not be able to gain connections to the other nodes.
Hmm interesting, so I see they have nodes, and are connected; so in theory they would be up to date and on v1.3 --> still waiting for a response from them about it.