I understand your frustration, however there is no need for accusations of "bs".
If you had bothered to read even a portion of this thread [including the part you personally quoted] You would see that there was an update to a new wallet 2.1.1 which has blocked the old 1.0.8 wallets [created by 'tami'] . This is what is meant when I said "old chain" it is the one that includes superblocks and has 10% POS.

Ok, so it seems the pool had skipped to a different chain, it has been reset, re-synced, and any missing tx's have been sent out of the remaining "good-chain" coins in the wallet. This, however, has sent the pool into a negative balance as it paid out the 'orphan' transactions coins on the good chain ... taking from the pool balance.
All should be well for now, however the payouts will be small until the inbalance is corrected with the pool fees, so all should be well moving forward.

Please keep me updated of any new issues or newly confirmed payments

In the post you quoted, it states that yobit is still on the old chain.
It is a known issue at this point and all we can do is wait
I have an upgrade request in to support, but am still waiting on a response. I apologize for any inconvienence while we are waiting, but sadly there is nothing that can be done on my end.

<edit>
After checking coinexchange.io their wallet  is still under maintenance aswell...

Hmmmmmm, I know its generally advised not to mine directly to an exchange wallet, however if some have already gone through Im going to assume thats not the issue.
Once I am back at home (about 30-45 mins) I will restart the wallet daemon with a -rescan and hopefully that will help locate the missing tx's and push them through.
What makes this situation quite strange is that generally when there no records transaction that means its sitting in the mempool waiting to be pushed into a block. Which would mean that the confirmations showing on the pool shouldnt exists at all (same with the tx's).
Stranger still the coins are being sent from the wallet (all pool stats in the admin section show successful transfers and smaller balances).
The only situation I can think of that could cause this is that somehow the pool has split to a different chain (this is simply a theory at this point).
To find out if i am correct I will compare some block hashes from the pool with ones from the explorer link you provided.
If all match up and we are still experiencing this issue, then you may need to open a support ticket at the exchange. (Not yet, let me asses things on my end first)

Can you please go to the "help" tab in your wallet, followed by the "debug console" and type getinfo. in the information that pops-up is a current block number, can you please let me know what that is to ensure we are at the same block height?
Also .... have you received any new deposits after the ~1.73? The pool is showing an 83 and a 59 LOG transaction within the last few hours to your address.

I am checking into it, and see exactly what you mean from your link. What is quite strange is that the pool shows many confs on the transactions in question... see below for one example


While trying to figure this out the pool may be up and down a bit while i resync and reindex to try and force through any missing tx's (as a worst case scenario)

<edit>
Another example from within the wallet RPC:

However, I'm still looking into it to see what could be the issue

100% the 9.x code is being built with the UPNP option, it was missing from the earlier releases as I was using an old 6.x base that suffered from a bug in the UPNP sections. To combat this I had disabled it during build.
I have chosen newer, cleaner code, with a few newer features and a bit nicer ui setup as a base for XGTC. The idea is that it will make implementing newer BIP protocols and features provided by some other altcoins a much easier task and allow for smoother updates ni the future.

@shotgun1969
Absolutely yobit has not switched over yet and is still on the old wallet and chain. Thank you for your list of seeds

@All
I am still working on the nicer newer 9.x codebase, It is nearly ready, I am just having a few small issues connecting it to our network properly. Once these issue have been resolved it will be released and we can move on to bigger and better things for XGTC

Currently at my day job, however, I will look into it the second I have time available thank you for reporting.

Looking into it right now



@wendigo your screen grab shows your using the hmq1725 mining algo, whereas we dont currently have any hmq1725 coins. Your choice is scrypt, skein2, or blake2s. The mining software featured on the webpage is from when we had hmq1725 coins, and I have been very busy with code, and have not yet updated that section. Using port 5766 it looks like youd like to mine blake2s.... and will need a miner for that algo.

@mrmerson it seems your Password is set to "c=PI" that was for mining picoin when available here. you need to change it to your desired coin "c=XGTC"

@kondrat -> please see update a few posts above...

@Louisa
Im not quite sure what you mean? will what be coming sooner the expected?

@ethereuming
Yes I had noticed the same, I am hoping they will change that while they are updating wallet.

@m1n3m1n3m1n3
Thank you for pointing that out I had no idea about that other coin, and that gives us another reason to change logo over time

@Everyone
I am currently working on a 2.1.2 wallet [from a 9.x codebase] as I have noticed a few small bugs and a bit of lag in certain aspects of the new wallet.
At this point we are still waiting for confirmation from exchanges that they have updated.
Once all exchanges have updated and all is running well, I will be working on an android wallet next

I am on the fence at this point at changing the name [maybe if we can settle on a good one in  the future], however I agree completely that the logo needs some updating. Likely, these changes will be after we get some more features and exposure with exchanges.
<edit>
I just checked coinexchange.io and it looks like our wallet is "undergoing maintenance", I have NOT received confirmation yet but it looks like they are in the process of updating their wallet with our new code Hopefully soon we will be able to exchange our XGTC to BTC again [for the miners ]

Ok, I am sorry your having that issue, but glad we have determined the pool is not the issue
Should you experience any other issue, please feel free to PM me or post here

Fixing now I am new to the blake2s algo and was unsure of a suitable base difficulty, and as such I left it at its default. This would cause to low diff shares for GPU's and anything bigger then a cpu. Give it about 10-20 minutes and please try again Note during this change pool will be spotty.

<edit>
As far as I can find there is no available AMD miner for this algo yet. So mining with your RX580 is currently not supported. If you have NVIDIA you should be fine to mine.
I understand and sympathize however as I run 280x's and have run into this same issue.
[/quote]

It might be the miner software because my 1060 doesn't work with sgminer on blake2 ether.. but it does using ccminer. going to try some other miners later. btw isnt decred the same algorithm? 
[/quote]
I am currently at my day job, but just wanted to check in and see if youve gotten the 1080 to run correctly using our pool. As I say, blake2s is a new algo to me so I am doing my best to get things running cleanly as quickly as possible

The women in crypto and technology niche is absolutely the way we plan to go for this coin. Once price and volume are up and we have some competitive features, then I will begin reaching out to non-profit organizations who also specialize in this niche.

We are absolutely open to ideas. The logo is still left from previous dev and will be changed eventually. I am just unsure yet if I will be firing up photoshop myself or if we should have a small contest.

As for the name, do you have any ideas? It wouldnt be done for awhile as there are more important aspects to work on first... but if many feel the same then a new logo and name will be added to the roadmap

I apologize that it will be in smaller amounts, but absolutely there will be a few more payments coming from my personal wallet as it builds. Likely ~10k at a time untill we have reached a fair payback for you 😊

Please note that is an estimated time, however, while looking into the issue the payments seem to have triggered and sent. I am heading to bed, but will investigate further in the morning

Fixing now I am new to the blake2s algo and was unsure of a suitable base difficulty, and as such I left it at its default. This would cause to low diff shares for GPU's and anything bigger then a cpu. Give it about 10-20 minutes and please try again Note during this change pool will be spotty.

<edit>
As far as I can find there is no available AMD miner for this algo yet. So mining with your RX580 is currently not supported. If you have NVIDIA you should be fine to mine.
I understand and sympathize however as I run 280x's and have run into this same issue.

here is the link, and the link in OP is now fixed aswell https://github.com/l8nit3tr0ubl3/GirlsToken-2.0/releases/download/2.1.1/GirlsToken2.1.1.exe