Topic: [ANN] GirlsToken-2.0 - 2.3-ALPHA in testing now[ANN] - page 14. (Read 25462 times)

Sending another 10k XGTC, Im sorry its so slow, but your contribution will be repaid as quickly as possible
txid = 1848fdd64cb2f0b7c408dc4ad4b711650cee3478be02d516fe41afad7f305a8e

And another 10k
txid = de3e25732cffeb656c3b0aa32014cef45e31ada6152bc9794ad898df4cf49206

I have worked up a concept for a new logo, and am working on one or two more, community members are welcome to submit their own aswell, and the community can decide through a poll once a few have been made

Yes there has absolutely been a fork, and the differences between them will get larger at block 450k when superblock removal and POS% dropping (10% to 2.5%) come in to play.
This is why users were warned not to send to exchanges until they had updated, and why the changes were decided by the community earlier in this thread.
As with all forks, one chain will eventually die out, or someone will continue development on the split and a new coin will be born.
I assumed (and still do) that because development on the old 1.0.8 chain has been completely stopped (see this thread and original XGTC thread for details) that most/all will soon switch over the chain that is actively developed.
I have put requests in to all 3 exchanges for them to update to the new code/chain and am awaiting reply. Any who choose to remain on the old code/chain that is not being developed absolutely risk loosing coins, as you pointed out, and as has been pointed out a few times throughout this thread.

UPDATE
Since backporting directly to the seed node caused issues, I am currently working on a new build of the 2.1.1 wallet. This one has UPNP fixed and the bloom filters update rolled back as it has caused more issues then it fixed. This will be version 2.1.1.1 and I will continue making small build updates (eg. 2.1.1.2) until I have fixed all of the issues with our 6.x wallet connecting to the newer 2.1.2 code based on a 9.x network protocol.

To explain the issue between the current and 2.1.2 wallets in more detail:
I am receiving multiple 'processmessage(inv, 37 bytes) failed' errors in the newest (unreleased) code, caused by "unkown INV type messages". This is a known issue between <7.x and >9.x wallets and was fixed in the 8.x series BTC wallets.


UPDATE #2
There has been a new release 2.1.1.1 available in the OP. This release rolls back the bloom filters which were quite buggy and fixes a few other issues. I will be making small updates to this branch [eg. 2.1.1.2] until I have successfully "bridged the gap" between the current version and the new version 2.1.2 that will be released in the future. The reason for the 2.1.1.1 branch is due to an issue with connections between 6.x and 9.x wallets.
WE ARE STILL WAITING ON EXCHANGES TO UPDATE. They have all been informed of the release and as none have completed the original upgrade yet, it should be no issue to switch to this one instead. I have also created the windows daemon that coinsmarkets required and as such they should be updated soon aswell.

I am working on the seed node now to try to "bridge the gap" between the 2.1.1 wallet and the new 2.1.2. My hope was to backport a few networking features to allow them to connect properly. I will revert my changes and all should be well again 😊


@kondrat
These changes have been reverted, please try again and syncing should be fine
Worst case scenario, please go to the GirlsToken folder and delete ONLY peers.dat, this will allow all connections to be refreshed, HOWEVER DO NOT DELETE anything else.
POOL CURRENT BLOCK NUMBER:
"blocks" : 411406,

After losing internet connection,I can not synchronize my wallet,Stuck at 404 5962 block.

Maybe we will see good things in the future... Good luck dev 

You are exactly right, there are many failed projects, and THIS WAS ONE! I was a community member of the original XGTC, who decided to try and help RECOVER the community's lost money.
I am doing all of this in my spare time, simply to try and help this coin and its users. Nothing done here is an attempt at a scam, or to take anyone's money.
I have taken NO premine or ICO, and have NO dev fund. Any XGTC I own is from mining and from pool fees.
All of this information is publicly available here in this thread. I have even gone as far as to reveal my real name in the OP, as well as to fully admit:
which is a direct quote from our OP.
I am doing my best to keep updates happening steadily, and have even produced new [to xgtc] things for the community, such as a vanity address generator and mac and linux qt wallets.
I have been nothing but upfront and honest with any issues that have happened and with any progress made.


as for my "new to crypto" comment, I truly meant no offense, and thought possibly that a miscommunication may have happened in my earlier explanations.

Yes I am "new" to crypto, new enough to notice fail projects like ECC or ICASH, see how people get money ripped off with an excuse of wallet, chain or whatever, I hope I see my money back...

Once again, if you read my response, your quoted text, or any portion of this thread, you will see WE ARE ALL WAITING on the exchanges to upgrade. It is not just you, NO ONE has taken your money. I myself am unable to send to an exchange at this time, so what possible motive would I have for causing you to "loose" money?
If this situation is new to you, or possibly you are new to crypto, I will explain once more in greater detail.

There were changes made to wallet to remove the superblocks, and to drop the POS %. This was done to lower inflation over time and give us all a coin worth a little more [smaller supply means more difficult to aquire in the future].
Because of these changes, the old wallet [with superblocks and 10%POS] was blocked using networking protocol versions. This would stop people from sending to the old wallets as eventually they will no longer be able to "locate a block source". The new wallet has been released and many have switched over.
We are all waiting on the exchanges to switch to the new wallet and support tickets have been filed asking for this very thing. Exchanges host multiple coins and as such may take time to complete the switch. Until that time ALL have been advised... multiple times... to avoid sending to the exchanges. This warning was to prevent users from ending up in your current situation, stuck in limbo waiting for a transaction to complete.
However, due to the nature of the blockchain, so long as you have your wallet.dat and private keys, your coins dont simply "disappear".
As soon as the upgrade is finished and we are ALL on the new codebase the transaction should complete and you should see your coins.

Frustration? WTF I want my money back!

Thank you for reading above And I apologize for it taking so long, I will send off another message to support in an attempt to speed things up. Coinexchange.io is currently in the same situation, and coinsmarkets is waiting on me [windows daemon needs to be built.] My hope is that I will be able to finish the new 2.1.2 wallet before they upgrade that way all can be on the same wallet.

As for the progress with the 9.x wallet, It connects to the network and sees peers, however at this point it seems to be too large of a leap [from 6.x to 9.x] and they are not correctly communicating with each other. This being said, I am currently looking for a good POSPOW scrypt coin with an 8.x network protocol version to compare and hopefully locate the portion of code that is causing "misbehaving" seed nodes.

My plan for today on the wallet is to use a simple "git difftool" command to locate any portions I may have missed or possibly forgotten in the new code, which may be causing the issues.

K read about not sending to exchanges. Will wait then

Is YoloBit asking for Million confirmations? Still havent credited my deposit from pool and one from wallet

Good luck to new dev

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.

This coin was moving around darn fast with only 2 confirmations until you mess it up.... just saying, I have few transactions to yobit no issues, what old chain, there is not old chain, sound like bs

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.


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

I tried to send coins from coinexchange to yobit  4 days ago, the transaction still shows pending on coinexchange, everything was working great before, why the mess now?

great to hear   keep up the good work