galaxy.cryptcoins.net  has been on the new fork since 3/17/ ...  Just letting everyone know... update the listing in the thread here.

Woohoo!

Does the pos work on GalaxyCoin? Sorry if i missed it on the op. But can i get a quick recap please

ok thanks for the update icecube.

We have been screaming to folks to update to the new client for almost two+ weeks now.

I am not sure what will happen with your coins on the old fork; good luck.

There might be something wrong on the new folk.
Because I have more than 30k coin 2,3 months ago, and my balance reaches 70k after the recent purchases from cryptsy.com.

Now my balance becomes 17k on the new folk.
It doesn't sound right, if the folk happened recently.

Possible reasons:
1) Folk happened long time ago, several months?
2) The snapshot which used to start the new folk might be wrong? 

Reason's 1+2 are wrong; the fork happened almost two weeks ago because when the fork happened people got stuck on block 249716.

When were the purchases on Cryptsy?

I can find the transactions from cryptsy.com using gettransaction command in the debug windows of GLX 2.0.
The transactions looks OK. It means the withdraw transactions from cryptsy.com works properly in the new folk.

But it is wired that the total balance displayed in the wallet is not correct.

As shown in the wallet, my balance is around 26k (17k + 9k from cryptsy today):

getbalance:
26311.96000000

but the number is different to the one return by 'listaccounts':

listaccounts:
{
"" : 100051.15000000,
"1" : 2606.00000000,
"2" : 39067.00000000,
"3" : 1470.00000000,
"4" : 1470.00000000,
"5" : 1790.78000000,
"6" : 1729.00000000,
"7" : 1560.00000000,
"8" : 1560.00000000,
"9" : 1560.00000000,
"Miners" : 23671.67000000,
"cryptsy.com" : 38548.95000000
}

Any idea?

1) Yes, can not agree more that community contributors should be respected. 
2) But it does not naturally prove that it is right to make a folk in this way. As a coin holder, it is wired to see your coin gone after a compulsory update.
3) As a cryptocurrency, the GLX should be handled as a mission critical software. Higher standard of testing should be involved before any update, especially for the compulsory one.

The price of GLX is crashing, it might be a lesson for everyone.

By the way, on a client I left to download the block chain from scratch, I now get this (repeated already several times):

03/22/14 13:06:31 received block 0000008eae20635f44ff
03/22/14 13:06:31 SetBestChain: new best=0000008eae20635f44ff681b6efc740b1501721c0d871d5f54e08d3c6baac001  height=18924  trust=18925  blocktrust=1  date=07/17/13 08:04:10
03/22/14 13:06:31 ProcessBlock: ACCEPTED
03/22/14 13:06:31 received block 2273c83fc8168441c0c3
03/22/14 13:06:31 ERROR: ConnectInputs() : 2bd7a74729 stake reward exceeded
03/22/14 13:06:31 InvalidChainFound: invalid block=2273c83fc8168441c0c3  height=18925  trust=1587918  blocktrust=1568993  date=07/17/13 08:04:12
03/22/14 13:06:31 InvalidChainFound:  current best=0000008eae20635f44ff  height=18924  trust=18925  blocktrust=1  date=07/17/13 08:04:10
03/22/14 13:06:31 ERROR: SetBestChain() : SetBestChainInner failed
03/22/14 13:06:31 ERROR: AcceptBlock() : AddToBlockIndex failed
03/22/14 13:06:31 ERROR: ProcessBlock() : AcceptBlock FAILED
03/22/14 13:06:31 received block 000001b716889e17bd32
03/22/14 13:06:31 Postponing 1 reconnects
03/22/14 13:06:31 REORGANIZE
03/22/14 13:06:31 REORGANIZE: Disconnect 0 blocks; 0000008eae20635f44ff..0000008eae20635f44ff
03/22/14 13:06:31 REORGANIZE: Connect 1 blocks; 0000008eae20635f44ff..2273c83fc8168441c0c3
03/22/14 13:06:31 ERROR: ConnectInputs() : 2bd7a74729 stake reward exceeded
03/22/14 13:06:31 ERROR: Reorganize() : ConnectBlock 2273c83fc8168441c0c3 failed
03/22/14 13:06:31 InvalidChainFound: invalid block=000001b716889e17bd32  height=18926  trust=2633914  blocktrust=1045996  date=07/17/13 08:04:16
03/22/14 13:06:31 InvalidChainFound:  current best=0000008eae20635f44ff  height=18924  trust=18925  blocktrust=1  date=07/17/13 08:04:10
03/22/14 13:06:31 ERROR: SetBestChain() : Reorganize failed
03/22/14 13:06:31 ERROR: AcceptBlock() : AddToBlockIndex failed
03/22/14 13:06:31 ERROR: ProcessBlock() : AcceptBlock FAILED
03/22/14 13:06:31 received block 0000038bcfde6a76a612
03/22/14 13:06:31 Postponing 2 reconnects


it then goes on and on and postpones up to 499 reconnects...