Topic: [ANN] Colossuscoin- 1.5.1 BIG, STRONG, and FRIENDLY - page 33. (Read 121143 times)

Lol, the difficulty is one factor but if you look over the past 8 months, every time Bitcoin spiked in price most alts tanked hard.  When Bitcoin went down these same alts shot up.

This is the inverse correlation I've been shouting about all to no avail.

Does anybody know what the total COL coins will be now?  Last I read muddafuda said 400 Billion to 500 billion but it wasn't a final estimate.   TIA!

what you have to remember is that for the payment processors to be affectively used auto sell is needed in 1 form or anther

Litecoin will be replaced by Goldcoin (as someone keeps yelling it out in Cryptsy Chat).
IF it gets put on Cryptsy, I hope the DEV has every right to tell Cryptsy to Turn off Autosell for the COIN.  Ever since that option came into play, 95% of the Alt coins tanked.
I would love to see COL without ANY Autosell feature just to see how it will react...  Will it be the next pre-autosell IFC (shooting up to 400) or stay low like post-autosell ADT.

Honestly, I would rather see it @ Coinex.pw.  I find their trade engine is actually faster and smoother than at Cryptsy (for non C programmed exchanges)

Fyi, the alts are not gettin flushed. The are coming back down to terra firma.

BTC's dollar value has nothing to do with it. Its the current difficultly, stupid.

This thing is never gonna get listed on Cryptsy if it doesn't stop breaking down.  ShitCoin breaks down less.

I talked to Mullick on Cryptsy and I had the impression Vern was waiting for COL to get it together and then it would get listed.  Getting on Cryptsy can definitely get COL to another price level, maybe even in the 20-40 range.  Call it crazy but tix ran up over 100 just 2 weeks after going to Cryptsy, and so did ADT.

Let's get this thing fixed and make some serious coin before Litecoin gets Flushed.

Sync'n stops every time the client loses the 3rd connection and/or hits a PoS block. All of them are orphans...

Its hit and miss. I've tried that several times and still can't solo mine.

I think it syncs if/when it feels like it. lol

S.O.S. muddafudda .. S.O.S.

Yes, it works now!

Thank you !

Muddafudda please update the OP:

COL Logos:


COL Homepage: http://www.Colossuscoin.org

COL Forum: http://www.Colossuscointalk.org

COL Facebook Page: https://www.facebook.com/Colossuscoin

COL Twitter: https://twitter.com/Colossuscoin


Thank you!
Sudo

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.

muddafudda more nodes?
1.5 client stucked

Still can't synch 

Looks like we still are stuck on Stake issues again.

Maybe a few ideas to help further?
- Anyway to hard code the Stake Diff to 15 instead of 502 so that Stakes can process faster and therefore POW can start computing?  By lowering the POS DIFF, it will force it to stake faster (since it is CPU based and those who use el cheapo/low hash powered AMD or Intel Processors for their mining rigs)
- Can we add hard coded counters for blocks and alternate between POS and POWs? (1 POS to every 3 POWs)
- Add CPU hash speed check prior to setting the POS DIFF

Hopefully COL will clear up and get moving again... waiting patiently until it does.

This is what I did.  If it gets stuck, close Wallet, delete the PEERS.DAT, reopen wallet and it will continue syncing.
some reason it sticks with some wallets.
Mine got synced after doing this 4 times.

That is good.  You have your full amount on Stake.
That means you will get a stake for your full amount.  Once your CPU computes the Stake it will release it out of stake and you will gain Interest on that full amount.

Nothing is wrong here. Just you need to ensure your CPU is fast enough to compute the stake for it.

Mine doesnt sync after a full delete. So ppfff.

this is the situation. any help?

nevermind. synced, recopiead old wallet.dat file. Coins still in stake and waiting for confirmations though. Any action going on?

ok. so re-downloaded the block chain, still not syncing and no sign of coins. Please help

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
}
]