Called sleep... NOT everyone can work 24 / 7.

Anyways, would like to say I was able to recover my wallet AFTER creating a new one.  Here are some simple instructions to follow to repair your wallet.

• Backup your %appdata%/Colossuscoin folder completely.
• Start Colossuscoin QT
• Click Transactions > Export to export your transaction list
• Goto Help > Debug Window
• Select Console Tab and type in listaddressgroupings
• Copy out each colussuscoin address you see there into Notepad
• For each address found by listaddressgroupings, type dumpprivkey <colossuscoinaddress>
• Record the results of dumpprivkey beside each colossuscoin address, repeat until whole list is done
• Close ColossusCoin QT
• Navigate to %appdata%/Colossuscoin and wipe every file and folder, EXCEPT your colossuscoin.conf and ANY BACKUPS you made.
• Check your colossuscoin.conf and remove any addnodes in there.  it is not needed there.
• Install the new version 1.4 Colossuscoin QT if you have not done so.
• Start Colossuscoin QT and goto Help > Debug Window
• Select Console Tab
• For each colossuscoin address you have, type in importprivkey <colossuscoinaddress> and wait for the blank return by the system. Repeat until all are imported
• No need to wait for the blockchain to download, Close Colossuscoin QT and restart it again.
• Now you need to wait for the blockchain to download
• Once all is downloaded, you should have most of your transactions here.

If you found this article helpful for you, you may donate to

COL: w6W9HXsXsseuAeUXBka4Xa5k9Wpev4UK4
BTC: 1Gvu4cJo8gkKhjWrn6xRNpzw1ZPmL6dEV5

Suggestion for the pool if this does happens in the future:

- Add a script to MySQL if it detects that the Coin has forked (If New Block < Previous Block) Set the site automatically and immediately into Maintenance Mode and stop the stratum server.
- Have All forked blocks moved out into a forked table.  Display the forked tables in a separate table so that people can see what was lost.
- Any withdrawals that occurred during the fork, all pre-forked coins need to be returned to the users.  Need to find the Forked block #, check the failed withdrawal to see which blocks were paid out up to the previous payout.  Set those failed paid out coins back to nonpaid mode so that users can withdraw them again.

The coin may have faulted but the Pool Server should ADAPT to the problem.  This is like the Gas Peddle being stuck open.  It should never happen but after 2-300 cases of gas peddle being stuck needs attention.  A redesign is needed.  The coin Creator did his...  but the Pool software also needs its fixes too.

Yes I understand the Withdrawal is gone... However, some of the COIN before the Forked block can be recovered.  Could you at least try to recover those for me please?  I know it would not be the full amount.

I understand there was a failed fork attempt.  What was the forked block?  Need to know so I can recover at least SOME of my coin before the forking.
Pool Operator said that he could not recover the withdrawal but there were blocks I got before the coin forking which I would like restored.  Want him to at least restore those for me.

The coin has not been returned into my account on the pool    Could you please verify it?

THanks.

HI Torzsy,

I got hit with the same problem.  Unfortunately I withdrew when it occurred.  Could you please verify and see?
Some of the coin withdrawn are from before the fork... I understand some of the coin may be missing due to the fork but those that were there before the fork should still be in your wallet.  Could you please forward those or restore the funds in the Pool and I will recover it.

Thanks.


Status: 0/unconfirmed
Date: 2013-09-19 01:43
From: unknown
To: zYAxqRE2buqu3ESmGL7SHcrAbxppkydyK (own address, label: Cryptominer.net COL)
Credit: 25011850.489 COL
Net amount: +25011850.489 COL
Transaction ID: f54901da9baeec4e217b472f8de64a499cecf325a37be78bc0411d395cc8bc66

tried to send some coin to Cryptsy and got error: transaction creation failed.

Tried to export and import my private keys and when importing got an error importing the key.

ANy help would be nice...

** Update #1 **  Played with the numbers... Tried to transfer 4600 coins, it failed.  Tried 4350 and it charges me 10.0 coins in TX fees.  Anything higher fails... Is there a problem with TX fees over 10 coins?

** Update #2 ** Seems like there is a problem with DumpPrivKey and ImportPrivKey functions...  Tried to dump and import into a new wallet.dat but it did not add in the address into my wallet.  Any problems there?

Or configure another pool and turn failover only on to switch when pool is unresponsive.  Another reason why we need longer (15-30 minutes) changes from one coin to another (unless the profitability drops >50% then change earlier.)

After 3 days of mining, a bit of outages as well, I have accumulated approximately 0.13579313 BTC for ~2.8 GH/s. This is a combination of Autosell and kept coins at current prices.  I think we would have made more if we sold them when the markets were up for those days.

It will take 22 days to make 1 BTC.

So it may be more worth it mining 1 coin non-stop instead.

Yes, all confirmed coins would be sold hourly if autosell is on.  Excellent example: HBN went from 0.00005231 to 0.00006969 for half hour.  If we could have sold it when it was up, a higher profit would have been obtained.

OR the other option...

Monitor the start bid price, each minute query the current bid price.  If the price moves up x %, sell y % of the current confirmed coins where y would be a percentage of coins (eg: 25-75% of confirmed coins) and then still monitor again if it goes up... If it continues to rise, sell another block of coins, etc until it stops going up.  Minimum sell is 25% of the coins.

Called SCam Coin.. YOu are mining for the DEV.

tried to email support but never got a reply. 
I am trying to withdraw my ADT and getting

Withdraw Error
There was an error creating your withdraw request, please contact support.

I tried contacting support but support never responds.
I would like to get my coins please.

One IMPORTANT issue that needs to be addressed soon:

- Hourly payouts.  Need to pay out the confirmed hourly batches ASAP.  Cause in 24 hours, it could be 50% lower.  Need to do it within the hour to maximize the profits.

Yes it is in priority... top being the first coin I would like to see... ALL these coins have a future, I weeded out the bad/crap ones already.  These are ones that are left that actually have some value in them (utility and service wise)

Add:

ColossusCoin COL: Solid coin.  Withstood 3 GH/s network attack.  Coin self-healed during attack (was forked but self-healed by reverting back to fork point, Pool softwares had failed.  No support for fork reversal and therefore accounting for coins were incorrect.)  PoS that actually does work extremely well.  
AndroidsTokens ADT
AnonCoin ANC
BitBar BTB
BitGem BTG
Diamond DMD
Emerald EMD
GrandCoin GDC
AlphaCoin ALF
HoboNickels HBN
KrugerCoin KGC
BBQCoin BQC
CasinoCoin CSC
Memecoin MEM
CraftCoin CRC
Doubloons DBL
Franko FRK
Gilcoin GIL
Globalcoin GLC
Pennies CENT
PrimeCoin XPM

Something missing that should be displayed:

- Per Coin Profitability Rates.

This way we can see how it is really profitable.

Additionally, use the past data (accepts/rejects/round) to adjust profitability for the coin.

I think this may be due to the 8 digit limit on COL.  Not sure if the new wallet addressed this issue.  Previous wallets could only send 99999999.99999999 COL.

How about adding something like this:

or

Since it was hard to cause it to fork permanently.
or

Colossus of Rhodes

After mining a bit, I found several issues:
- some coins do poorly than others.
- some coins produce 0.000001 BTC/sec while others only produce 0.00000033 BTC/sec
- does the algo take into account that we are mining the coin and adds it into the profitability calculation?  Cause it switches coins a lot.
- Some coins got high Orphans = lost production: Can this be reduced?

Copy and paste into a Spreadsheet to see it better

Some suggestions to add to the site:

- Show Difficulty rate, Reject rate % and Coin Exchange rate per round to understand why we got lower coin.
- if not factored in, modify algo to exclude our hash rate for current coin profitability rate.
- Extend the rounds to at least 10-15 minutes, the 8 minute rounds makes us lose about 1-1.5 minutes/round and in 60 minutes it can add up to 10.5 minutes of downtime/hour vs only up to 6 minutes/hour or 252 minutes/day vs 144 minutes/day.  Getting an extra 2 hours of hashing would be better.  if each round was 30 minutes, then we would only lose 72 minutes/day and gain 3 hours of hashing per day.
- Add some coins like COL, ADT, IFC (high coin amount/block)
- Add Block Finder reward (2-5%/block): It would be nice to reward those who actually find a block.  Keeps them happy and continue to mine here.
- Add a separate SHA256 Coin Multipool miner
- if not factored in, add 24-48 hours of coins/sec per coin type into profitability calculation.  This will deem which would be more profitable to mine at the time.
- As for removing coins,  only MNC is on my list.  I mine EMD, GDC and GLD so I would like them there too.

I autosell some and keep some (staked coins obvious reasons)...  Also those with high values I keep as well since they are active a lot.  So far, this pool looks interesting, but need a week to see if it is better than Multipool.  That one was horrible payouts.