There are several probable causes. I will explain all changes and git commits so all can read. Remember we are pushing the limits with 25 second block POS, the quickest I believe.
Topic: [ANN] Colossuscoin- 1.5.1 BIG, STRONG, and FRIENDLY - page 55. (Read 121123 times)
Np 
I restarted the qt after deleting the peers.dat and everything looks ok again. Woot found another. xD
Starcoin seems to be having issues aswell. Could this be some kind of attack on PoS and/or coin hopper resistant coins ?
I restarted the qt after deleting the peers.dat and everything looks ok again. Woot found another. xD
Starcoin seems to be having issues aswell. Could this be some kind of attack on PoS and/or coin hopper resistant coins ?
ADT is based on starcoin and that's working well only had a stuck block and that's it in a couple of weeks
STR has been stuck at 95.6k for hours and is showing conflicting difficulties.
Np
I restarted the qt after deleting the peers.dat and everything looks ok again. Woot found another. xD
Starcoin seems to be having issues aswell. Could this be some kind of attack on PoS and/or coin hopper resistant coins ?
I restarted the qt after deleting the peers.dat and everything looks ok again. Woot found another. xD
Starcoin seems to be having issues aswell. Could this be some kind of attack on PoS and/or coin hopper resistant coins ?
ADT is based on starcoin and that's working well only had a stuck block and that's it in a couple of weeks
Np
I restarted the qt after deleting the peers.dat and everything looks ok again. Woot found another. xD
Starcoin seems to be having issues aswell. Could this be some kind of attack on PoS and/or coin hopper resistant coins ?
I restarted the qt after deleting the peers.dat and everything looks ok again. Woot found another. xD
Starcoin seems to be having issues aswell. Could this be some kind of attack on PoS and/or coin hopper resistant coins ?
I'm not mad. heh.. I'm actually up 17.5M. 
In case it helps.. heres how mine adjusted.
Last valid block before the fork : 48414 (The date must be off because it should read as Sept 7.)
Status: 1784 confirmations, broadcast through 23 nodes
Date: 06/09/2013 00:05
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: abfea2f3d0390d206f005dc9cf35a89f6246f066cbd2cd2f925d0d73d1531c31
First block after : 49054
Status: 1143 confirmations, broadcast through 21 nodes
Date: 07/09/2013 02:57
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: d00f26daa4be526da4e6f195e6676941bbb663dbfba56eed08ec4b90a7bdceb3
In case it helps.. heres how mine adjusted.
Last valid block before the fork : 48414 (The date must be off because it should read as Sept 7.)
Status: 1784 confirmations, broadcast through 23 nodes
Date: 06/09/2013 00:05
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: abfea2f3d0390d206f005dc9cf35a89f6246f066cbd2cd2f925d0d73d1531c31
First block after : 49054
Status: 1143 confirmations, broadcast through 21 nodes
Date: 07/09/2013 02:57
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: d00f26daa4be526da4e6f195e6676941bbb663dbfba56eed08ec4b90a7bdceb3
Thankyou. Soz for the rant it just gets so frustrating rah.
I will clarify a bit of behind the scenes work to what is happening and how to improve the code moving forward.
The zero POS issue should correct tomorrow and without saying to much too early, we may have a clean chain.
Most importantly, STOP SENDING COINS around until the client is stable. Recommending not sending trans for 48hrs.
I'm not mad. heh.. I'm actually up 17.5M.
In case it helps.. heres how mine adjusted.
Last valid block before the fork : 48414 (The date must be off because it should read as Sept 7.)
Status: 1784 confirmations, broadcast through 23 nodes
Date: 06/09/2013 00:05
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: abfea2f3d0390d206f005dc9cf35a89f6246f066cbd2cd2f925d0d73d1531c31
First block after : 49054
Status: 1143 confirmations, broadcast through 21 nodes
Date: 07/09/2013 02:57
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: d00f26daa4be526da4e6f195e6676941bbb663dbfba56eed08ec4b90a7bdceb3
In case it helps.. heres how mine adjusted.
Last valid block before the fork : 48414 (The date must be off because it should read as Sept 7.)
Status: 1784 confirmations, broadcast through 23 nodes
Date: 06/09/2013 00:05
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: abfea2f3d0390d206f005dc9cf35a89f6246f066cbd2cd2f925d0d73d1531c31
First block after : 49054
Status: 1143 confirmations, broadcast through 21 nodes
Date: 07/09/2013 02:57
Source: Generated
Credit: 5000000.00 COL
Net amount: +5000000.00 COL
Transaction ID: d00f26daa4be526da4e6f195e6676941bbb663dbfba56eed08ec4b90a7bdceb3
I transferred yesterday xxx IC2 from https://btcltc.com/ because they did not accept COL Adresses.
Its still before Sep 08. I am not the only one who paid out to IC2 Adresses..there are many guys pay out there to IC2 Adress because https://btcltc.com/ did not accept COL Adresses yesterday.
I have updated the Client.
Please support IFC2 today, i have too much unconfirmed transactions. Yesterday everything was okay , no unconfimed transactions.
Thank you !
Its still before Sep 08. I am not the only one who paid out to IC2 Adresses..there are many guys pay out there to IC2 Adress because https://btcltc.com/ did not accept COL Adresses yesterday.
I have updated the Client.
Please support IFC2 today, i have too much unconfirmed transactions. Yesterday everything was okay , no unconfimed transactions.
Thank you !
I will support the main chain only. Think your pissed, I lost 200 million pos cause of this and it will more than likely happen again. From midnight tomorrow night the second fork will kick in and fuck off all the old clients
We just went through the first halving for the second time ! lol
Unfortunately it been posted for a week to update your wallets, unfortunately you did not. I assume others did not also which caused the massive forks that are happening. Ill investigate but am really wasting my time if people don't update.
POS generation started after 15 days, those without the col wallet could not pos and were fighting the network. People not upgrading was and now is the problem.
POS generation started after 15 days, those without the col wallet could not pos and were fighting the network. People not upgrading was and now is the problem.
hi,
whats wrong with the client
,
have also lots of transactions since yesterday, all of these are now unconfirmed!
I copied my IC2 wallet to COL wallet and all unconfirmed transactions disappear!!
whats wrong with the client
, have also lots of transactions since yesterday, all of these are now unconfirmed!I copied my IC2 wallet to COL wallet and all unconfirmed transactions disappear!!
Yep, investigating. Suspect it has to do with the hard fork and lack of client updates. Investigating
Also have a problem, daemon crashed ~ 3 hours ago, after block 51566 (it was an orphan).
I'm at block 49220 on both my rig and my daily computer and was able to send coins.
I think this is the main chain right now.
Have lots of transactions since yesterday, all of these are now unconfirmed. Client stucked @ 49927.
Yep, investigating. Suspect it has to do with the hard fork and lack of client updates. Investigating
Also have a problem, daemon crashed ~ 3 hours ago, after block 51566 (it was an orphan).
I'm at block 49220 on both my rig and my daily computer and was able to send coins.
I think this is the main chain right now.
Yep investigating. Hard fork is due midnight Sunday gmt which will fix the issue. At work ATM investigating will be able to do more after work.
Thanks!
Yep investigating. Hard fork is due midnight Sunday gmt which will fix the issue. At work ATM investigating will be able to do more after work.
Yep, investigating. Suspect it has to do with the hard fork and lack of client updates. Investigating
Also have a problem, daemon crashed ~ 3 hours ago, after block 51566 (it was an orphan).
Yep, investigating. Suspect it has to do with the hard fork and lack of client updates. Investigating
Just found a problem, the block is 515XX, a sudden jump back 48XXX block, and during my entire mining proceeds goes Unconfirmed COL
Man I thought we had another explorer. Anyways jump on the pos bandwagon.
Getting some block time spread out with POS generation, it's working though tuning is needed.
Jump to: