PLzV6v9TDCZSsTosGiunEoujFYLZs6Jigm

Thank you!

sCzNtG66hT2mXCEtu6NzTCL9kRcCVWNzJ

Awesome, thank you!

I'm synced.
Current number of blocks 158872
Mon Oct 21 19:39:57 2013

If you were recently synced but can't do it now, try closing the client and deleting peers.dat and relaunching. May have to do it once or twice before it works.

have you guys tried backing up your wallet and then deleting everything in your appdata\roaming\Colossuscoin folder?
Let it fully redownload the blockchain, and then close the client and put your wallet back in the colossuscoin folder. That has worked for me in the past when I couldn't sync.

I'm fully synced. My peers are listed below.
The only thing that I have in my colossuscoin.conf is listen=1



[
{
"addr" : "106.186.113.60:40986",
"services" : "00000001",
"lastsend" : 1382107063,
"lastrecv" : 1382107063,
"conntime" : 1382106930,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 157644,
"banscore" : 0
},
{
"addr" : "77.22.197.166:54058",
"services" : "00000001",
"lastsend" : 1382107071,
"lastrecv" : 1382107072,
"conntime" : 1382106937,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 119072,
"banscore" : 0
},
{
"addr" : "72.179.164.248:57364",
"services" : "00000001",
"lastsend" : 1382107063,
"lastrecv" : 1382107063,
"conntime" : 1382106954,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 157647,
"banscore" : 0
},
{
"addr" : "1.122.249.38:12454",
"services" : "00000001",
"lastsend" : 1382107064,
"lastrecv" : 1382107063,
"conntime" : 1382106961,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 157653,
"banscore" : 0
},
{
"addr" : "151.74.241.241:56033",
"services" : "00000001",
"lastsend" : 1382107064,
"lastrecv" : 1382107063,
"conntime" : 1382106985,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 157675,
"banscore" : 0
},
{
"addr" : "5.83.21.59:59366",
"services" : "00000001",
"lastsend" : 1382107063,
"lastrecv" : 1382107063,
"conntime" : 1382107034,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 157724,
"banscore" : 0
},
{
"addr" : "72.238.90.11:12454",
"services" : "00000001",
"lastsend" : 1382107064,
"lastrecv" : 1382107063,
"conntime" : 1382107061,
"version" : 70000,
"subver" : "/Colossus:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 157740,
"banscore" : 0
}
]

To mine at beeeer use the miner that he has in the first thread here: http://www.ppcointalk.org/index.php?topic=485.0

I can say from personal experience that I get significantly more from beeeer than I do at ypool.

about 8600 miners right now.

Testing this out. 2.58MH on my 6970.

+1

I love the interface! All the information that I could possibly need is there. I'm definitely interested in signing up if you do decide to make this a paid service.

Also, does your rig 1 always run at 80c? Seems kind of hot?

I'd be glad to test if there is still a spot open, thank you

I agree with this, and only see the lack of liquidity problem increasing if they add more coins to the XPM market. I'm all for a 3rd market, but make it a coin that has more than 2 million units.

The next block halving is at block #241920
Slightly over 8 days from now.

If the PoS block generation is the problem, then why even have that feature on this coin?
Even if everyone moves their coins to temporarily stop the PoS issue, once solo mining starts up the problem will only end up showing up again after a few weeks have passed, and we'll all be in this exact same spot once again. Don't get me wrong here, I currently hold a significant amount of this coin and really would like to see it become successful.

It appears that GPU efficiency has just dropped again.

running 1.4.2 just fine. Zero coins lost from my wallet. Thank you Muddafudda. 

Nice pool! The immediate payouts are very nice! 

I have that as well. The dev just needs to update the checkpoint. Everything is fine.

That's awesome news!

on your quark pool, in the getting started section there is a typo:

minerd -a quark -o stratum+tcp://ark.coinmine.pl:6010 -u worker_name.1 -p password