Anyone know how to get in touch with the acidpool owner?

Yes, same here

Thank you for contacting him, and he did a good job taking care of problem.

Be back soon

PS: Nice hash there btw 

Noise23 runs acidpool, he may have suspended payouts due to his recent troubles. I'd contact him directly. Meanwhile, http://gmc.cryptocloudhosting.org/GMC/public could use some miners

In other, much better, news, the block explorer is now fixed, and we can stop speculating about Coinmarketcap, it's now showing the correct supply. Be one hell of a coincidence if they were pulling their data from somewhere else and fixed it at the same time the official block explorer came back to full function

My apologies and thanks to all who waited it out. Usually when something goes wrong on the BE, it's easy to fix. This time, it was anything but. And I must own a part of that. After rebuilding it, I miskeyed a command, which made the front end go even more goofy. After I figured that out, it took about 22 hours to get everything right again. Much longer than I would have liked, but it's all good now.

THANKS

GMC! pool is back up with NOMP as it's stratum layer. As requested, there is now a stratum port for guys with big rigs. It doesn't currently show on the pool's 'getting started' page (it will soon) but it does work.


Regular stratum is stratum+tcp://gmc.cryptocloudhosting.org:3333 vardiff starting at diff 8

high power is stratum+tcp://gmc.cryptocloudhosting.org:3356 starting at diff 256

On my own little rig, I have run into some issues with the dashboard showing maybe 60 percent of what cgminer reports, but the logs and the pool stats and admin pages are reporting pretty close to right. This is also quite preliminary. Please, let me know what happens with stats, connection issues, anything out of the ordinary (even if it's good)

Update on the GMC! pool. It's been successfully migrated to a much larger server. I still got some backend tweaking to do to make it run smoother, but it should be ok now. One of you guys with large hashpower, could you do me the favor of pointin' that cannon my way and see if it is reporting correctly now? give it at least twelve minutes, because the stats only update every three. That will be changing, since the new server can handle the load

well acidpool is back up but someone is overpowering the pool with their high hash rate, who should be solo mining
my daily payout suffered a 2/3 hit
fun while it lasted ill just hold what i got and watch
H2C is pretty much the same even a lil less for a payout
kinda wish i had a lot of hashing power so i could solo mine, but im not about to buy a 90dB machine

on other news the price is going up nicely and what i have mined is well into profit
hope this trend continues and glad to see the devs hard work paying off

True. Result of being in a hurry When I have more time, I'll clean it up to just have the nodes

sure thing

[
{
"addr" : "5.196.20.189:40002",
"addrlocal" : "65.129.84.227:40002",
"services" : "00000001",
"lastsend" : 1435606041,
"lastrecv" : 1435605995,
"bytessent" : 48176,
"bytesrecv" : 76805,
"conntime" : 1435546880,
"pingtime" : 0.00000000,
"version" : 80006,
"subver" : "/GameCredits:0.9.4.3/",
"inbound" : false,
"startingheight" : 1122494,
"banscore" : 0,
"syncnode" : true
},

"inbound" : true,
"startingheight" : 1123084,
"banscore" : 0,
"syncnode" : false
}
]

For those who still need it: http://gmc.cryptocloudhosting.org/bootstrap/bootstrap.zip
Anyway, you can find almost everything on our OP, usualy under Resources section.
If we missed something - please point it out and we'll sort that pronto!

Working on a bootstrap.dat for the blockchain - should be ready in a few hours -- p2pool node will remain offline for the time being.

A checkpoint update for XencoinCommunity will be coming soon - we're back to having a collision with another alt-coin when the client runs - a checkpoint should solve this. Due to the fast blocktimes on this coin, along with the 'network confusion' issues brought on by lack of proper fork/clone by original source, I may have to start a rolling 'point' release schedule for this client (0.6.3.4 is current - 0.6.3.x <-- x being the point updates for checkpoints) - this may help alleviate the 'stuck downloading wrong chain' issues I'm starting to see again in these older litecoin-clone-based clients. Depending on how often this is needed will determine the 'schedule' - but it's looking like about 2-4 weeks per point release for the blockchain.

To anyone who has started using the latest release, please be sure to note any issues/problems/successes with this fork.  I can't fix things or attempt to improve things if I don't know what's wrong or what's happening. 

A new thread is coming soon as well - once I get some more things organized.  Community members who can contribute, please get setup on Github if you aren't already for issue tracking and code submission/pull requests.  Thanks!

Thanks for reply but both links have Source code. I don't know how to compile from it Windows wallet.
What i need is link with working updated complied wallet so i can start *.exe and use it. Sorry for all troubles

I don't see any link for updated + compiled windows wallet.

I just checked the DNS seed and there's only about a total of 8 XNC clients out there that are live and 'reachable' - 1 is the seed-node, 2 are the other (updated) client - and the rest are older clients --