Topic: STAR COIN [STR] - The coin with bonus STAR blocks - page 30. (Read 143782 times)
10000 STR for sell, pm me
Anyone interested in 81k STR? Pm me.
6000 for sale if anyone is interested PM me
sold for a peanut and 2 beanz
Isnt this the coin that spawn other broken coins like COL and ADT. You guys should let this one die a painful death.
6000 for sale if anyone is interested PM me
It has broken stake mining. The explanation is here and in the cross-linked threads.
The blocks of interest are #347385 and #347386.
The blocks of interest are #347385 and #347386.
Thanks for your pm bee7, I am looking into it this week!
Does having that checkpoint message affect ability to stake? I have the checkpoint message, was running wallet for 2 days straight it stayed in sync and at any point i could check and see the recent block would be up to date but it never attempts to stake ? STR that i have is months old now since last time it staked, any ideas what the problem might be?
It has broken stake mining. The explanation is here and in the cross-linked threads.
The blocks of interest are #347385 and #347386.
Does having that checkpoint message affect ability to stake? I have the checkpoint message, was running wallet for 2 days straight it stayed in sync and at any point i could check and see the recent block would be up to date but it never attempts to stake ? STR that i have is months old now since last time it staked, any ideas what the problem might be?
Wny block don't syncronize after 272359?
starcoin client v1.6
starcoin client v1.6
Have no idea. I just did it with no problems. Try from the very beginning.
Wny block don't syncronize after 272359?
starcoin client v1.6
starcoin client v1.6
It seems you did not get what checkpoint I meant.
I'm pretty sure I understood :/
getcheckpoint
{
"synccheckpoint" : "000000231e3abea847919c620b5693a36b6e454923b42398db927387523a08e4",
"height" : 371800,
"timestamp" : "2013-12-23 07:38:54 UTC"
}
As mentioned above please follow the instructions I posted to remove the checkpoint error!!
This time it worked out, thanks. Strange that when I sync'ed a few days ago it did not help.
Check the PM please
It seems you did not get what checkpoint I meant.
I'm pretty sure I understood :/
getcheckpoint
{
"synccheckpoint" : "000000231e3abea847919c620b5693a36b6e454923b42398db927387523a08e4",
"height" : 371800,
"timestamp" : "2013-12-23 07:38:54 UTC"
}
As mentioned above please follow the instructions I posted to remove the checkpoint error!!
But still, it is annoying and should be fixed in a correct way (by broadcasting the checkpoint) as otherwise cryptsy could easily reject the 'application'.
The checkpoint is being broadcasted, the checkpoint was updated on 24/12 I'm thinking this problem happens when the cpu gets overloaded during the sync or if memory drops too low, I am looking into the problem and will let you guys know when if I can narrow it down further!
I have another view:
Quote
starcoind getcheckpoint
{
"synccheckpoint" : "c51c1e21db4ea688465b72757c578bde94a19a780d376a6fb5997c8b7fa3f8b7",
"height" : 0,
"timestamp" : "2013-07-17 05:52:17 UTC"
}
{
"synccheckpoint" : "c51c1e21db4ea688465b72757c578bde94a19a780d376a6fb5997c8b7fa3f8b7",
"height" : 0,
"timestamp" : "2013-07-17 05:52:17 UTC"
}
Quote
starcoind getinfo
{
"version" : "v1.6.0.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 419379,
"moneysupply" : 32591791.93443700,
}
{
"version" : "v1.6.0.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 419379,
"moneysupply" : 32591791.93443700,
}
It seems you did not get what checkpoint I meant.
But still, it is annoying and should be fixed in a correct way (by broadcasting the checkpoint) as otherwise cryptsy could easily reject the 'application'.
The checkpoint is being broadcasted, the checkpoint was updated on 24/12 I'm thinking this problem happens when the cpu gets overloaded during the sync or if memory drops too low, I am looking into the problem and will let you guys know when if I can narrow it down further!
Cool beans, thanks. Yeah it's weird. I can tell you my memory load isn't even near half when this thing fires up or runs, nor are any of my cpu cores.
But still, it is annoying and should be fixed in a correct way (by broadcasting the checkpoint) as otherwise cryptsy could easily reject the 'application'.
The checkpoint is being broadcasted, the checkpoint was updated on 24/12 I'm thinking this problem happens when the cpu gets overloaded during the sync or if memory drops too low, I am looking into the problem and will let you guys know when if I can narrow it down further!
I also tried this. On one wallet it worked, but on another it hasn't. I even went so far as to transfer all the coins out of the wallet, completely deleted the wallet.dat and blockchain (everything in the data folder) and let the blockchain download from scratch. Still have that checkpoint message.
It doesn't hurt anything though, right? I'm still solo mining fine.
It shouldn't hurt anything as long as you are on the correct chain but while you are seeing that message there is no way to ensure that.
But still, it is annoying and should be fixed in a correct way (by broadcasting the checkpoint) as otherwise cryptsy could easily reject the 'application'.
Thanks. Copying the block chain from the working client did the trick. -rescan went fine, checkwallet said there were no problems. No more checkpoint message.
I also tried this. On one wallet it worked, but on another it hasn't. I even went so far as to transfer all the coins out of the wallet, completely deleted the wallet.dat and blockchain (everything in the data folder) and let the blockchain download from scratch. Still have that checkpoint message.
It doesn't hurt anything though, right? I'm still solo mining fine.
It shouldn't hurt anything as long as you are on the correct chain but while you are seeing that message there is no way to ensure that.
If you have a client that has synced correctly, try following these directions to get them both working right..
0. check you disks for corruptions, chkdsk or something similar
1. stop both clients
2. make a backup of the wallet and the chain on the broken client (wallet.dat, blkindex.dat, blk0001.dat and database folder)
3. delete the original blkindex.dat, blk0001.dat and database folder in the data directory of the broken client
4. copy the .dat files and database folder from the working client computers data directory to the broken clients data directory
5. open a command prompt or shell
6. run "starcoin-qt -rescan"
7. once the client opens, open the debug rpc console
8. if your wallet is locked unlock it using walletpassphrase
9. run the command checkwallet
10. if checkwallet found problems run repairwallet
11. you should have working client with your previous balance restored
12. if you wallet hasn't locked itself you can re-lock it with walletlock
Hope this helps,
ps. as a general rule it pays to keep a copy of the blockchain handy in case you need to restore it due to a corruption, saves having to resync the whole thing, eventually I'm hoping to provide a downloadable copy of the blockchain to save time resyncing
infin.
Hi All,
For those who are having problems...
Download the new 1.6 update released on 24/December at the website (http://www.starcoin.info/download.php)
If you get the checkpoint error and you have already updated to the new client for some reason or another corruption has occured in the chain...
To be able to fix you need to either redownload the blockchain from scratch or copy the chain from another working client and start the client with the command line option "-rescan".
Don't forget to backup your wallet before beginning this process just in case, and also don't forget to use the checkwallet/repairwallet command inside the debug console once the process is complete to confirm that your balance is corrected.
If anyone needs a hand feel free to drop me a pm.
Regards,
infin.
For those who are having problems...
Download the new 1.6 update released on 24/December at the website (http://www.starcoin.info/download.php)
If you get the checkpoint error and you have already updated to the new client for some reason or another corruption has occured in the chain...
To be able to fix you need to either redownload the blockchain from scratch or copy the chain from another working client and start the client with the command line option "-rescan".
Don't forget to backup your wallet before beginning this process just in case, and also don't forget to use the checkwallet/repairwallet command inside the debug console once the process is complete to confirm that your balance is corrected.
If anyone needs a hand feel free to drop me a pm.
Regards,
infin.
I also tried this. On one wallet it worked, but on another it hasn't. I even went so far as to transfer all the coins out of the wallet, completely deleted the wallet.dat and blockchain (everything in the data folder) and let the blockchain download from scratch. Still have that checkpoint message.
It doesn't hurt anything though, right? I'm still solo mining fine.
Hi hndrk,
Yes, pretty much.
--------------------------------
Hi VesperWillow,
Strange... You can try making a copy of peers.dat while the client is stopped and deleting the original, also make sure there are no other processor intensive applications running while it syncs..
Note: you can stop the client at points during the chain download process and make a copy of the chain (both .dat files and the database directory), just remember before stopping the client, ensure that it is not displaying the "checkpoint" error
It would be great to come up with a complete process that works for everyone, so please let us know how you go!
regards,
infin.
When StarCoin is accepted at Cryptsy,
how will it be traded?
It will be traded in the same way as the other coins on the site.how will it be traded?
People have to believe in the coin for them to trade their coins for it, right?
How are they going to believe in it?
We have some ideas that are currently in the works to increase confidence in the coin, need to run through some stuff with nzdude, but will keep you postedHow are they going to believe in it?
Will the coin automatically start trading for LiteCoins and BitCoins if Cryptsy accepts it onto their site?
Yes, pretty much.
--------------------------------
Did this, still says checkpoint too old. Will try again.
Hi VesperWillow,
Strange... You can try making a copy of peers.dat while the client is stopped and deleting the original, also make sure there are no other processor intensive applications running while it syncs..
Note: you can stop the client at points during the chain download process and make a copy of the chain (both .dat files and the database directory), just remember before stopping the client, ensure that it is not displaying the "checkpoint" error
It would be great to come up with a complete process that works for everyone, so please let us know how you go!
regards,
infin.
Jump to: