Topic: [ANN] GirlsToken-2.0 - 2.3-ALPHA in testing now[ANN] (Read 25454 times)

DEATH

What news about the coin, or everyone forgot about it?

POW is end only POS. TOTHEMOON

Pool http://scryptminingpools.com/getting_started    -o stratum+tcp://scryptminingpools.com:3033 -u

Did we have a pool? In the network 3.8 GH

pls add wellet and config 2.2.0.0-g

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


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.


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.

 I really admire your work and like the project. I own some coins and will get some more as they are really cheap right now. Keep up with the good work and ignore all the fudding

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

Registering an online access to a kids or everyone without the abbility for this.

L3+ about an hour or two. Should have found block in few mins. Will try again once you updated to Alpha4

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.

Looks like pool not working - not finding blocks.

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

keep up the good work

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

right forgot to delete dir

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.

Alpha2 also didn't work for me. But alpha 1 did work fine.