STAR COIN [STR] - The coin with bonus STAR blocks

[jjj0923]

If folks are having troubles getting synced up, my node is up most of the time on 10 Mbit static IP.

addnode=198.204.207.2

thanks I'll add it.

[NekoMiko]

I've been having trouble solo mining this coin since a couple of days ago. The wallet synchs fine, except for the "checkpoint too old" message, but my cgminer seems to be unable to submit any found blocks before it turns stale.

It kept saying "Pool 0 communication failure, caching submissions". Then it says the share became stale while retrying, so I couldn't actually receive any of the blocks I found.

I am using the latest wallet client, and this only started happening about 2 or 3 days ago. I'm sure there is nothing wrong with my local network, because I can solo mine everything else fine.

Any ideas?

TIA.

[jjj0923]

I've been having trouble solo mining this coin since a couple of days ago. The wallet synchs fine, except for the "checkpoint too old" message, but my cgminer seems to be unable to submit any found blocks before it turns stale.

It kept saying "Pool 0 communication failure, caching submissions". Then it says the share became stale while retrying, so I couldn't actually receive any of the blocks I found.

I am using the latest wallet client, and this only started happening about 2 or 3 days ago. I'm sure there is nothing wrong with my local network, because I can solo mine everything else fine.

Any ideas?

TIA.

I've been having the same problem - I've found that by unlocking the wallet will pick right up where it left off

go into the debug window and type : walletpassphrase your-password-here 60000 true

and that will do it for you...at least it did for me.

[NekoMiko]

I've been having the same problem - I've found that by unlocking the wallet will pick right up where it left off

go into the debug window and type : walletpassphrase your-password-here 60000 true

and that will do it for you...at least it did for me.

Yes, that helped. Thanks a lot!

It seems like you can't solo mine with an encrypted and locked wallet.

[jjj0923]

I believe you have to encrypt to get an address right?

[veremit]

You guys have definitely set the lines:-

rpcuser=myname
rpcpassword=mypass
rpcallowip=myip
rpcport=myport
server=1

in your StarCoin.conf (obviously matching the equivalent settings in your miner.conf or bat file/etc) ?

[NorbyTheGeek]

Anyone have an idea what's going on with StarCoin?  As of this writing, the last block generated was 777855 approximately 5 hours ago.  Both of my nodes are on the same block, and CoinWarz also lists 777855 blocks.  Difficulty isn't astronomical or anything.  It's almost like something got stuck.

[jjj0923]

Anyone have an idea what's going on with StarCoin?  As of this writing, the last block generated was 777855 approximately 5 hours ago.  Both of my nodes are on the same block, and CoinWarz also lists 777855 blocks.  Difficulty isn't astronomical or anything.  It's almost like something got stuck.

I was solo mining and it just stopped dead - all found blocks were being rejected so I gave up.

[vesperwillow]

Someone could be forking the coin with lots of hash.

[some138]

is this coin alive? I like the logo.

[bee7]

Someone could be forking the coin with lots of hash.

No. It was hit by the time wrap bug:

$ starcoind getblock 00000001219aabf7a0c0e629bacf6b70cbd857ebeb7e2575c6049c70306b5190
{
    "hash" : "00000001219aabf7a0c0e629bacf6b70cbd857ebeb7e2575c6049c70306b5190",
    "confirmations" : 1,
    "size" : 268,
    "height" : 777855,
    "version" : 4,
    "merkleroot" : "0221710eae6afdcc6cec652e513b74898e9929da0fa14d6124c157565ccd66e9",
    "mint" : 100.00000000,
   "time" : 1400607967,
    "nonce" : 2163618803,
    "bits" : "1d03cb20",
    "difficulty" : 0.26360777,
    "previousblockhash" : "00000000dfa28f824f3c569dbe8ae78c6dd0bb659f084f48d6c72a70277fd76c",
    "flags" : "proof-of-work",
    "proofhash" : "00000001219aabf7a0c0e629bacf6b70cbd857ebeb7e2575c6049c70306b5190",
    "entropybit" : 0,
    "modifier" : "dc6c78fb8aaa45f0",
    "modifierchecksum" : "56e6bebb",
    "tx" : [
        "0221710eae6afdcc6cec652e513b74898e9929da0fa14d6124c157565ccd66e9"
    ],
    "signature" : "30460221008f5a3e299781b03df544c442b1461a6724257b327550be38a568505bd01ad06e02210 0a7ab840456c6054aec1f0b7373226d5f8c6c9fd4bd4a25ad4107d7e3b70b587a"
}
$ starcoind getblock 00000000dfa28f824f3c569dbe8ae78c6dd0bb659f084f48d6c72a70277fd76c
{
    "hash" : "00000000dfa28f824f3c569dbe8ae78c6dd0bb659f084f48d6c72a70277fd76c",
    "confirmations" : 2,
    "size" : 268,
    "height" : 777854,
    "version" : 4,
    "merkleroot" : "a7ed902b6a2dee6a5045d277d19b50c77db83d3b4e7ce55cf203ca59a62db8e3",
    "mint" : 100.00000000,
   "time" : 1400608554,
    "nonce" : 3908568320,
    "bits" : "1d03fb5b",
    "difficulty" : 0.25113525,
    "previousblockhash" : "000000025cb702b64c9f44a96ab1f0177c82c203e2dba288423c8abaa7f939ee",
    "nextblockhash" : "00000001219aabf7a0c0e629bacf6b70cbd857ebeb7e2575c6049c70306b5190",
    "flags" : "proof-of-work",
    "proofhash" : "00000000dfa28f824f3c569dbe8ae78c6dd0bb659f084f48d6c72a70277fd76c",
    "entropybit" : 0,
    "modifier" : "dc6c78fb8aaa45f0",
    "modifierchecksum" : "dd993608",
    "tx" : [
        "a7ed902b6a2dee6a5045d277d19b50c77db83d3b4e7ce55cf203ca59a62db8e3"
    ],
    "signature" : "3046022100ea0230879f31cdf498f658b604b1502ee967c0c40bfce5f34daa60bf6220f7b602210 0db1bce696553cebd95a8721a3dd8b865eb71b85000e85842881756ee115868cb"
}

The difference between times of the last PoW block and the one before last is negative. Thus the re-targeting algorithm in use produces negative difficulty. Though, the getblocktemplate RPC call produces some positive target, then the wallet declines all blocks you find.

[timerland]

so this needs a patch....

[bee7]

so this needs a patch....

Yes. btw, the PoS minting is broken on this coin long ago:

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.

[shveicar]

It now remains to wait when there will be a new team and new developers. Otherwise, it can be stated that the death of the coin. 

[vesperwillow]

Someone could be forking the coin with lots of hash.

No. It was hit by the time wrap bug

Well either way, it was slashed. It was evident something along those lines was going on.

[veremit]

Hrm, yes I see what the issues are .. since this will force a global wallet update (fork) anyway .. let me see if I can rustle something up, will have a word with the other guy who's tentatively bug-fixing with me, and will try to get a release out asap.

[CharityMiningPools]

Due to lack of support and development, CharityMiningPools will be closing it's Starcoin pool at the end of this month.  Please withdrawal any coins that you may have on our site by this date.

str.charityminingpools.com

[bee7]

Version 1.7.0

Win64: https://mega.co.nz/#!9dBynbaS!YEvnMIXoKMyyMzcMlldZoLyQX6-zyH3VP6a03kmkook
source: https://github.com/bee7/starcoin

After the time-wrap bug hit Starcoin at block 777855 again and finally stoped the network from producing new blocks the following changes to the protocol were implemented:

1) The ActualSpacing is bound by 2 seconds and TargetTimespan, i.e. 15 minutes
2) The PoW/PoS ratio is set to 1:3 (compare to the original one 1:12) to allow more PoW blocks as anyway for the last half a year the PoS was already broken.
3) The block trust scoring algorithm changed to target 3 PoW blocks among past 12 blocks.

Release Notes:

The Windows binary provided is native Win64 application cross-built using linux mingw64 environment.
It is built with BerkeleyDB 4.8.30 and openssl-1.0.1g. The builtin CPU miner in above mentioned build should not work due to some incompatibility between mingw64 and original scrypt implementation. Though, mingw32 version should work just fine. Feel free to build one if you need this functionality.

Please note, I am not going to be a developer of this coin, I just released a fix that may allow the StarCoin to survive.

So, let's see if cryptsy updates its wallet to this version.

Good luck.

[shveicar]

Please note, I am not going to be a developer of this coin, I just released a fix that may allow the StarCoin to survive.

Then why do it. Or coin will have normal design and own team or do not need it and must die. Let worried those who are bought tens of thousands of these coins.
They can’t sit back and wait for something indefinite

[bee7]

Please note, I am not going to be a developer of this coin, I just released a fix that may allow the StarCoin to survive.

Then why do it. Or coin will have normal design and own team or do not need it and must die. Let worried those who are bought tens of thousands of these coins.
They can’t sit back and wait for something indefinite

The community should decide to support the coin further or not by running wallet or not running. The holders could hire someone for part of their stakes, for example, if they do care. The coin has no team for almost 6 months already: the last update to the coin had been published on Jan 7 and it was a checkpoints update. At that time the PoS was already broken: the last PoS block submitted to the net on Sat Dec 14 12:49:20 UTC 2013. It had been delisted from cryptsy and then listed again in Feb. So, there is still quite a number of people who likes it for some reason.

Juts tell me please, if Gavin and company announce today that they quit the project, would Bitcoin die? Why do you think that the existence of a dedicated dev team is a must? I agree that it is nice, when the dev team exists. But still, this coin survived during 6 months without any developer support!