Hello, it looks like your export is failing?! strange that it does not appear in the block explorer! what are the wallets concerned?
Hi. Thanks for checking. The send was from Mining-Dutch.nl to the address at Bleutrade. This happened at a time when BATA wallets were offline on Cryptopia so, I decided to just move my BATA to my Bluetrade account. No help from Bata team or Bleutrade to find lost transaction. Mining-Dutch says the transaction was sent to the blockchain, which is why they list the transaction ID. I have no idea what happened and Bata team will not answer questions or help resolve. I will NEVER mine BATA again!
The Bata team has helped you, we do not control third parties.
A support ticket was sent to both exchanges.
As per previous post good advice by Granty mine to your wallet, in fact most exchanges will advise you to do that, as micro transactions clutter their wallets.
No, you did not "help" me. You may have submitted support tickets, but you didn't bother to follow up or inform me of the outcome. I've waited patiently for over a week and you only reply when I begin to get flustered. Worst, now you blame the user. If I was the only one this happened to, I'd let it go, but I'm not, and you know it! It should not matter if coins go to a wallet or an exchange. Your system is flawed and hundreds, if not thousands, of people have lost money mining your unsupported and lack-luster coin. If you really cared about your customers, you would find out why so MANY people have lost, and are still losing, their transactions. If you don't believe me, just read the BATA forums ANYWHERE on the internet.
So, instead of pounding my head, I will join the chorus of other people in the forums, bemoaning your "coin," and will work to get it delisted in as many places as possible!
The sad part is, all you had to do is care enough to help the disenfranchised people who wanted to be a part of something great by mining your coin. Instead, you blame the user and take NO responsibility for your failures.
Giggles go join another forum then. The only way to fix the problem in this instance was to contact the exchange.