Quote from: not.you on June 17, 2018, 03:49:31 PM

Quote from: scrypt on June 17, 2018, 04:26:05 AM

Quote from: not.you on June 17, 2018, 02:33:46 AM

Quote from: scrypt on June 15, 2018, 07:11:23 PM

Just realized that Monero auto withdrawals do not reach my wallet since 6 of April. Used the wallet for a long time, it was ok till the 6 of April.
Is it known problem related to the fork, or what?

Did you update your wallet software? Last payout I received from pool for monero was 6/1 and it went through fine for me. My wallet is v0.12.0.0.

Yes, had updated to the latest 0.12.0 - this is how I knew there is some real problem, before the update I was OK thinking the cause is my outdated client.

The last tx I see in my wallet is "e4f4" with Blockheight: UNCONFIRMED. Following 13 txs are lost.
https://i.imgur.com/MeVslax.jpg
https://i.imgur.com/MeVslax.jpg

I see what you mean. I'm not a monero expert but I noticed I had created a new address for myself back in Nov. Is it possible that your payout address was created with a much older client and therefor stopped working with the v0.12.0.0 update?

Can you post one of the TXID links from that MPH transaction page you screen shotted? So like one of these pages:
https://xmrchain.net/search?value=e3f690901d6914b672ebe78cf6d6fceaff3aa5f46d9d30d0206a23048e1d0ded

Just curious to see what it says. They all say confirmed on the MPH page there.

Looking closer at the screen shot of your client, why does it seem to say that the e4f4... payment which MPH sent on 4-10 was only just received on 6-14? That certainly seems odd. Actually can you post the xmrchain page for that TXID? Your client says unconfirmed for blockheight so that seems like a good one to examine. I'm starting to suspect your client may not be syncing quite right, or at least not decoding transactions sent to it.

The address to receive moneros from MPH was created using some 0.10.x client.

All of the txs have some non zero number of confirmations.
Here are three transactions from the list. Ok in local client, Unconfirmed in local client, and Lost in local client:
https://xmrchain.net/search?value=13388d6d3d313f7fd37c7e80a1c54b75b83ad5d142629e616549632de94c743c - it's Ok.
https://xmrchain.net/search?value=e4f403575ba970138c13af1adbcb57d28b582943528dbacefaeed052a75bb801 - Unconfirmed.
https://xmrchain.net/search?value=f77299fa528a9397400228062da7d12a8ee3303d14fa7953da37035a219850e3 - Lost.

>why does it seem to say that the e4f4... payment which MPH sent on 4-10 was only just received on 6-14?
It is strange for me too. 14 of June if the date I updated client to actual v0.12 and synch-ed the chain.

>I'm starting to suspect your client may not be syncing quite right, or at least not decoding transactions sent to it.
Yes, now this is my main suspicion (and hope) too that something is wrong with my client installation. Will have fresh install and synch from the scratch. Hope one whole day will be enough as I am going to leave for my vacation. If yes, will report here for the result tomorrow. If not, will report in 3 weeks(
Thank you for guiding me.

===========
UPD 19 June.
Yes, fresh installation resolved the problem. The rule of thumb: In any unclear circumstances make Fresh Install.
Long life, MPH.