Thank you for your words of encouragement and welcome to the community!

<update>
It seems the pool (running a new Alpha5) is properly finding blocks with our new updates, once it is known if our negative block issue is repaired a release will be built for all of the XGTC community.

<update #2>
Well, Alpha5 is able to find blocks properly, however we still have compatibility issues with the yiimp setup. Once again this has caused a negative balance on the pool. Luckily I happened to be watching it at the time and it only reached ~1000 XGTC negative. So even with the updates, we still have an issue lying somewhere within the GBT or GB functions.

I have stopped the mining on the pool for now, and will continue to work on the code untill we have these issues cleared up.

Pool is back open for testing, sorry for the delay, the servers incoming net speed seems slow the past few days so it took awhile for ~1.17 mil blocks to sync. Hopefully this new version fixes our mining issues and we can release

Alpha4 is now up on the pool, however it needs to do a full sync before mining will be opened for testing

Can you please elaborate? How much hash, for how long? Did the miner show blocks found? Cpu, Gpu, Asic?

Also, I found that as soon as I add in anything bloom related at this point we get a huge speed drop, and seem to lock up and lag quite often. Alpha4 is up with bloom rolled back, but all other updates still in place Alpha4.

Pool will be updated to Aplha4 later today, and may need a resync. I will update when this process is started, and when its finished.

Known Bugs in Alpha4:
-Progress bar time changes, yet bar remains same size throughout sync.

Alpha3 is up for those interested, shouldnt need to clear datadir for this one Alpha3. The pool is now on this updated code aswell.

Also, we finally have "dumpwallet" & "importwallet" commands for dumping all privkeys at once and import said dump files

Just to bring everyone up to speed with my general plans for the near future.

I have been working hard on our codebase to bring it from an ancient 0.6.x based wallet up to a 0.9.x or 0.10.x. Currently I am using mostly commits from a combination of Bitcoin, Vertcoin, and Peercoin and modifying them to work correctly with our code.

This will involve a massive re-write of nearly all files currently in our code, splitting up the ancient codebase into more manageable parts, updated dependancies, and eventually an updated build system using autotools or possibly the newer "depends" system found in most 0.10.x clones.

Once finished with bringing the code as close to up-to-date as possible, i will begin working to add the multi-algo and eventually masternodes to our owm codebase rather then simply cloning DASH or PIVX.

The reasoning behind this is simple, when finished we will not only have a more complete and streamlined codebase (choosing only the desired or neccessary commits rather then cloning the full source). Also we will have a dev (me) with a far deeper understanding of literally every aspect of the code.

Alphas, betas, and small releases will continue throughout this process, however once the multi-algo is working, we will split off into XGT3 and have two separate chains for the coinswap.

Thank you all for your support and patience

Thank you both for testing And for the quick reply.
Alpha1 should be fine to run with the same data dir, however alpha2 has had an upgrade to leveldb and as such would need to resync from scratch with an empty datadir (keep wallet.dat of course)

With that said, I have also noticed bugs in Alpha2 that kick in around block 350k while syncing. So, at this point Alpha1 is the one to test. I will remove Alpha2, and rollback the code updates untill I know which one caused the issues.

<update>
The pool is being re-opened to help stress test an alpha version of a slightly updated 2.3 version of our current wallet.

THIS IS NOT:
-The new XGT3
-A huge change with tons of new features

THIS IS:
-A cleaner, smoother running version, with bugfixes for usability
-Fixes "greyed out upnp settings" some had experienced
-Fixes Mining issues - Still being tested
-Less "Transaction too large" issues for massive wallets with many small transactions - Still testing
-Added getaddednodeinfo for better info on nodes added through cmd line
-Added additional checkpoints to help keep all on correct chain
-Extend POW period indefinitely at a rate of 10XGTC/Block starting at block 1.4 million

The decision to extend the POW period was made after serious thought. The reason for it is this:
-Up untill this point most of the mining for XGTC has been solo
-This cuts out many users who are unwilling or unsure how to solo mine
-Extending the POW  at 10/Block allows new users/miners to join while letting the OG community keep a bonus for early adoption (higher POW rewards early on)

There are likely to still be bugs as this has been only tested in house so far, and I have been up for days building it.
For those who would like to test the new code the windows wallet is available here: GirlsToken-2.3-ALPHA.exe

VirusTotal results available here: Results

Please report bugs here or in a DM to me personally, and I will do my best to squash them as quickly as possible.

Also It seems CoinExchange.io has re-opened deposits and trading for XGTC! Happy Trading

Current nodes:
addnode=93.116.29.98
addnode=88.198.38.66
addnode=129.213.107.143
addnode=203.118.153.128
addnode=91.90.235.216
addnode=178.157.250.196
addnode=104.218.18.50
addnode=176.10.170.65
addnode=51.15.162.24
addnode=107.161.95.108
addnode=31.173.188.162
addnode=83.58.98.122
addnode=93.116.29.98
addnode=86.126.215.170

<update>
Alpha2 is up for anyone looking to test. Before starting wipe out everything except wallet.dat in your data folder and as always, back up your wallet.dat.
Link -> Alpha2

Bootstrap.dat has been updated on the GitHub to 1109181 blocks. HOWEVER, the wallet still has lag issues whether you sync from network or bootstrap. Explorer should be back up momentarily, and I will update again when there is more news to share.

Bootstrap link https://github.com/l8nit3tr0ubl3/GirlsToken-2.0/releases/download/2.2.1/bootstrap.dat

As for CE and lpool, these are not run by me, and any changes or decisions made about XGTC is done by their staff.

Hello all,

I apologize for being away so long, I have been dealing with some family issues. (not an excuse, simply an explanation).

ON XGTC 2.0 (current):
I have rebuilt the pool/explorer and the XGTC explorer is currently downloading blocks. Once fully synced, I will build a new bootstrap.dat since, as mentioned, the last one made was quite awhile ago. As we still have a strange bug in the code casuing issues with the pool, I WILL NOT be opening the pool for XGTC 2.0, simply the explorer.

ON XGT3:
I am currently still working on the multi-algo code, using many different bases to find the best fit for us. However, along the way I have figured out how to properly separate "GetHash" from "GetPOWHash" which is a nice but small step along the way. Please remember I am not a c++ dev and am learning most of this along the way. With that said, there is work going on in the background as much as possible, but it will still be slow going untill we have a "ready-for-release" XGT3.

I will my do best to check in far more often here now that I am back at a keyboard a bit more.

where can I buy currently? I am prepared to buy enough for an MN but am unable to find somewhere to buy.

Yes that is the current version, the block explorer is available at http://yiimp.l8nit3-miners.com/explorer to check current block height.

I will be contacting coinexchange.io this evening after work. The issue was that the explorer was down, and to be safe and ensure that all coins were also safe, the exchange put the wallet in maintenance mode.

Also over the next few days, I will be working on and putting Girlstoken.org back online, and am still working hard on the 3.0 wallet myself as talks with other devs are on hold at this point. (many wanted to inflate price after quote, or had no idea what multialgo was)


The pool has been running and paying out quite stable now ,however as changes are made ( both to the pool and to XGTC) it is ALWAYS recommended to have backup pools setup  in case of connection issues... even if those backups are other coins. This ensures you always get your moneys worth with a rental.

Many are 0.5 BTC or more. A substantial sum for a small coin with one dev. That being said however, I still plan on having at least one solid exchange when we are ready for release, just keep in mind price will be a deciding factor.

I answered right above your post, this has been an ongoing issue for quite sometime. It is entirely in yobits hands, and if they choose not to ever update theres nothing anyone else can do including me. I do not have any say in what yobit does.

<edit>
Reposting this bit just so all can see it as the newest post:

As for an update on the progress with the new wallet, I am currently interviewing 8 different developers to help speed up finalizing the multi-algo code. At this point  there is one developer far in the lead and I am waiting on one final response from them before giving them the green light to begin work.

For the pool, I will be working on it sparingly over the next week and will hopefully have it back up very soon,

Explanation for the delay:
I was using "localbitcoins.com" during the recent up and down swing of BTC. My goal was to trade up enough BTC for a good exchange listing on release. However, I was the victim of multiple chargebacks (paypal) and multiple interac "chargebacks". These unscrupulous users caused both of my bank accounts and paypal accounts to have large losses. I have since cleared up most of these issues, learned my lesson, and finally have time to get back to work for the community

This particular issue is a yobit issue, the code was changed in such a way that the old 1.0.8 wallet and the newer 2.2.1 wallet are NOT compatible in any way. Yobit has refused to answer dozens of support tickets from myself and from community members about this exact issue. I realize this is not what your looking to hear... but until yobit decides to play ball there is nothing you or I can do about the situation.

As for an update on the progress with the new wallet, I am currently interviewing 8 different developers to help speed up finalizing the multi-algo code. At this point  there is one developer far in the lead and I am waiting on one final response from them before giving them the green light to begin work.

For the pool, I will be working on it sparingly over the next week and will hopefully have it back up very soon,

Explanation for the delay:
I was using "localbitcoins.com" during the recent up and down swing of BTC. My goal was to trade up enough BTC for a good exchange listing on release. However, I was the victim of multiple chargebacks (paypal) and multiple interac "chargebacks". These unscrupulous users caused both of my bank accounts and paypal accounts to have large losses. I have since cleared up most of these issues, learned my lesson, and finally have time to get back to work for the community

Hello malekbaba, and all community

I wanted to provide some updates to let everyone know what progress is being made, complete with screen shots

1st- I have registered "girlstoken.org" and am building us a nice, slick, html5 info page for the upcoming release (images below):




2nd- I have a fully working scrypt masternode wallet, that is technically ready for release, however there are no true innovations at this point to set us apart. I have managed to successfully build a version with a basic, 2 algo "multi-algo pow" setup, which is building and being tested now. (untested linux-qt pics below):



Currently included, and being tested is scrypt and xevan algos. With plans to add a few more including skein2 and phi1612 after the current code is fully tested and deemed working.

Happy holidays to all

No definitely not over I am nearing completion on the first GirlsToken3.0 wallet. It will be a masternode release, with POS and scrypt POW at first. I am still working on adding the multi-algo POW, however that will be added in as a hard fork in the future.
The pool is down due to issues in the codebase of our 2.x versions, which will be fixed with our new 10.x+ codebase. Once the 3.0 version is released, it will be added to the pool and 2.x will be removed.

The plan is to have a 60 day coinswap, and then after everyone has switched over I will be working on the addition of multi-algo once again. I am also looking at pricing of a few different exchanges for listings. The hope is to have at least one larger exchange at the time of release, even if I have to pay out of pocket untill things get running.

The current planned coin specs are as follows:
Masternode cost: 5000
Masternode reward: 15% forever, no seesaw rewards, or growing rewards. <- this way POW miners still have incentive
Block time: 15 seconds times number of algos
Confirmations: 10 <- this + 15 sec block time means ~2.5 minutes for fully confirmed tx's
Block reward: 5 halving at every 518400 blocks
Ports: still 10666 and 10665
Max_Money: This is still a working number only, but approx 7-9 million
Premine: there will be a small premine, that will include coinswap coins. The working number is around 2%. with ~1% for coinswap, ~0.7% for dev fund (listings, bounties, etc), and 0.3% for the developer (me) for previous work and continued work. The 0.3% will be used to setup 2 masternodes with a small remainder that will be my personal balance (as I have no coins left to swap, due to funding the pool repeatedly)

Also, I am looking at changing the ticker to XGT3 to differentiate between the new code and old code on exchanges and such... hopefully this will prevent "lost" coins from sending to certain exchanges.

These are the current numbers we are working with, however they are subject to change before actual release

I apologize, I have been working nearly non-stop lately for extra holiday money, and as such have not been able to give the pool the proper attention it deserves. I have initiated the payments manually for all available coins in the wallet. You should see a payment shortly

I will be dedicating some time this weekend to updating the pool code and applying a few more bugfixes. After the release of XGTC 3.0 wallet, I will be taking down the pool for a full rebuild on both servers, aswell as adding some upgrades to the large server for stability and to allow for greater expansion of the pool and the supported coins

also is iQVBarS4S9LVr3oAbxZSCzhmBWsbjLqZhy a valid LOG address?? or are there missing sections?

This is normal at this time, the cause of this is the imbalance I spoke of earlier in the thread. Basically, as the coins come in they are being split between users, however with the negative imbalance there isnt enough to fully pay every users balance [yet]. As such, the pool is paying the largest balances possible [while still weighting based on share submission] using the available balance + pool fees which are currently dumping directly back into the pool wallet to help speed up the correction. The minute the pool balance has equalized, full size payments will begin again.

Also to help prevent this in the future, I have setup a VM copy of the pool for testing new yiimp commits before actually pushing them to the pool, and possibly causing issues such as this.
Thank you for your patience, and your assistance with reporting issues

At this point we do not offer a bounty, this will however be possible after the coinswap and release of version 3.0 as we will have a small dev fund to "play" with.

To all community members, I would like to provide a brief update and let everyone know that I am in fact still alive

-We currently have at our disposal a copy of XLR that I have switched over the algo from xevan to scrypt. However, there seems to be a "re-index" bug causing a blckchain re-index every startup [I have also personally noticed this issue on a stock XLR wallet]
-Due to the issue above I have abandoned [while still keeping the code for reference] the XLR base and have instead decided to use DASH as our base. Once again I have managed to get all of our "placeholder" specs added in, made the gen block, and am working on implementing multi-algo POW.
-Anyone who would like to view progress made on either of the above codebases, can check out my github and view recent commits

We still have a long road ahead of us, but progress is being made each day and I am confident the wait will be well rewarded for all of us