[RE-ANN] Galaxycoin Revival! KGW, POS/POW hybrid [TRADING ON CRYPTSY]

[Miner-TE]

Seriously ... "difficulty" : 47.61663649,

[NoobKidOnTheBlock]

Seriously ... "difficulty" : 47.61663649,

Arrrgh I hate that when someone with lots of hash mines for a bit then takes off with the difficulty still high cause that freezes the chain for the rest of us dammit

[Miner-TE]

Coming down.
    "blocks" : 978225,
    "difficulty" : 24.20694193,


Some People need to realize how difficulty works.  Just putting a mass of hash on a coin when it's at low diff does not get you the best bang for your buck.  You just drive up difficulty to the same block timing.

Better to gradually add hash. Become some percent of nethash, start getting that percent of blocks solved and adjust/add hash as desired.

[NoobKidOnTheBlock]

Coming down.
    "blocks" : 978225,
    "difficulty" : 24.20694193,


Some People need to realize how difficulty works.  Just putting a mass of hash on a coin when it's at low diff does not get you the best bang for your buck.  You just drive up difficulty to the same block timing.

Better to gradually add hash. Become some percent of nethash, start getting that percent of blocks solved and adjust/add hash as desired.

Yes 100% completely agree!! The driving the difficulty up doesn't do anything except get the chain stuck once the huge hash leaves mining Galaxycoin cause the difficulty is too high for other miners to solve.

[Hobbyist]

This coin is completely dead, right ?

Not completely ...

Code:

galaxycoind getpeerinfo
[
    {
        "addr" : "70.163.93.46:15521",
        "services" : "00000001",
        "lastsend" : 1466645255,
        "lastrecv" : 1466645268,
        "conntime" : 1466642372,
        "version" : 60008,
        "subver" : "/Satoshi:2.0.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1187512,
        "banscore" : 0
    },
    {
        "addr" : "193.68.21.36:15521",
        "services" : "00000001",
        "lastsend" : 1466645268,
        "lastrecv" : 1466645268,
        "conntime" : 1466642396,
        "version" : 60008,
        "subver" : "/Satoshi:2.0.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1187512,
        "banscore" : 0
    },
    {
        "addr" : "203.20.114.252:15521",
        "services" : "00000001",
        "lastsend" : 1466645398,
        "lastrecv" : 1466645256,
        "conntime" : 1466642666,
        "version" : 60008,
        "subver" : "/Satoshi:2.0.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1187519,
        "banscore" : 0
    },
    {
        "addr" : "37.187.96.15:15521",
        "services" : "00000001",
        "lastsend" : 1466645245,
        "lastrecv" : 1466645400,
        "conntime" : 1466642819,
        "version" : 60008,
        "subver" : "/Satoshi:2.0.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1187519,
        "banscore" : 0
    },
    {
        "addr" : "108.161.135.192:50107",
        "services" : "00000001",
        "lastsend" : 1466645253,
        "lastrecv" : 1466645261,
        "conntime" : 1466643291,
        "version" : 60008,
        "subver" : "/Satoshi:2.0.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 842598,
        "banscore" : 0
    }
]

[almightyruler]

This coin is completely dead, right ?

I'm still running two 24/7 nodes, one with full time PoS.

As far as a current use for this coin... yeah, I guess that stopped when Cryptsy did. Doesn't mean it's dead, though.

[almightyruler]

There's a bit of a problem with minting GLX at the moment:

09/25/16 03:25:05 generated 64.00
09/25/16 03:25:05 ERROR: CheckBlock() : coinbase timestamp is too early
09/25/16 03:25:05 ERROR: ProcessBlock() : CheckBlock FAILED
09/25/16 03:25:05 ERROR: BitcoinMiner : ProcessBlock, block not accepted

I think what is happening is that one node has a clock a few minutes fast, and because there's relatively few nodes, it has a much larger effect on what the network collectively agrees is the correct time. So when I find a block solution, and try to create a block with my (correct) local timestamp, it is rejected because the network time is ahead. The only solution is to restart the client, but eventually the time will slip ahead again.

Looks like 193.23.157.12 has the fast clock, because the +237 offset appears as it connects:

09/24/16 15:17:15 accepted connection 193.23.157.12:51020
09/24/16 15:17:15 send version message: version 60008, blocks=1243669, us=x.x.x.x:15521, them=193.23.157.12:51020, peer=193.23.157.12:51020
09/24/16 15:17:15 Added time data, samples 5, offset +237 (+3 minutes)

[...]

09/25/16 03:46:10 accepted connection 193.23.157.12:51757
09/25/16 03:46:10 send version message: version 60008, blocks=1244130, us=x.x.x.x:15521, them=193.23.157.12:51757, peer=193.23.157.12:51757
09/25/16 03:46:10 Added time data, samples 5, offset +237 (+3 minutes)

Check your computer's clocks, please.

[almightyruler]

No blocks added to the chain for over 3 months. Guess this coin is done.

[ArchitektoR]

No blocks added to the chain for over 3 months. Guess this coin is done.

restarted my solo pool and put 3 mini gridseeds on it to support network - just 1 block was generated. Will let them mine.

If someone needs it - can reconfigure this NOMP pool to be public.

[almightyruler]

My own little Gridseed coincidentally crashed an hour or two before your message, otherwise my coin chooser software would have resumed mining as soon as it saw the block moving.

Working now.

Just keep an eye out for consistent rejects - that most likely means the "coinbase timestamp is too early" error mentioned above...

[MicroGuy]

Our team obtained many of the cryptocurrencies that were frozen on Cryptsy's servers when the exchange collapsed. The Galaxycoin wallet.dat was among those recovered.

We are now in the process of giving these wallet files back to their respective communities. The wallet has not been inspected and it's unknown if it contains any coins. If you are a developer of this coin, or a longstanding community member, you can file a request for the wallet in this thread: https://www.gldtalk.org/index.php?topic=3789.0

[emdje]

Our team obtained many of the cryptocurrencies that were frozen on Cryptsy's servers when the exchange collapsed. The Galaxycoin wallet.dat was among those recovered.

We are now in the process of giving these wallet files back to their respective communities. The wallet has not been inspected and it's unknown if it contains any coins. If you are a developer of this coin, or a longstanding community member, you can file a request for the wallet in this thread: https://www.gldtalk.org/index.php?topic=3789.0

Great job you guys, some good news in all the bad around Cryptsy.

Wish I had my Cryptsy trading and deposid/withdrawal history backed up  
Don't know what I had on there anymore  

[Stouse49]

Our team obtained many of the cryptocurrencies that were frozen on Cryptsy's servers when the exchange collapsed. The Galaxycoin wallet.dat was among those recovered.

We are now in the process of giving these wallet files back to their respective communities. The wallet has not been inspected and it's unknown if it contains any coins. If you are a developer of this coin, or a longstanding community member, you can file a request for the wallet in this thread: https://www.gldtalk.org/index.php?topic=3789.0

Great job you guys, some good news in all the bad around Cryptsy.

Wish I had my Cryptsy trading and deposid/withdrawal history backed up  
Don't know what I had on there anymore  

I was working on getting the wallet up and running from Cryptsy, but can't find the source code for the wallet.  Are there any miners or block explorers?

[almightyruler]

I was working on getting the wallet up and running from Cryptsy, but can't find the source code for the wallet.  Are there any miners or block explorers?

I'm running a miner.

I've uploaded the last source I have (grabbed from github on 2nd July 2014) here: http://www.almightycoins.org/download/galaxycoin-master.zip

[Ivanech]

I was working on getting the wallet up and running from Cryptsy, but can't find the source code for the wallet.  Are there any miners or block explorers?

I'm running a miner.

I've uploaded the last source I have (grabbed from github on 2nd July 2014) here: http://www.almightycoins.org/download/galaxycoin-master.zip

Sounds good.

In addition, could you provide a list of actual peer nodes to sync wallet (getpeerinfo output)?

[almightyruler]

# coin: galaxycoin
addnode=193.68.21.36
addnode=203.20.114.252
addnode=85.236.188.28

[Stouse49]

Thanks for the link to the wallet source and the addnodes.  Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

[almightyruler]

Thanks for the link to the wallet source and the addnodes.  Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

48k sounds too small - a freshly created "empty" wallet.dat is already 128k in size.

Have you tried the -salvagewallet commandline option? (Make a backup of the existing wallet.dat first)

[Stouse49]

Thanks for the link to the wallet source and the addnodes.  Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

48k sounds too small - a freshly created "empty" wallet.dat is already 128k in size.

Have you tried the -salvagewallet commandline option? (Make a backup of the existing wallet.dat first)

I tried the -salvagewallet, but still there were no coins in this wallet.  Must have been a dud.

[almightyruler]

Thanks for the link to the wallet source and the addnodes.  Unfortunately the cryptsy wallet that I had was only about 48Kb in size and had no balance.

48k sounds too small - a freshly created "empty" wallet.dat is already 128k in size.

Have you tried the -salvagewallet commandline option? (Make a backup of the existing wallet.dat first)

I tried the -salvagewallet, but still there were no coins in this wallet.  Must have been a dud.

I can have a poke around if you like. Send me a copy? A 'proper' wallet.dat contains some recognizable clear text strings, so if this wallet also contains them, it may be possible to reverse engineer from that point, and figure out the offsets of private keys.

Maybe even something brute forcish like importing every possible 20 byte sequence in the file as a private key may work... to do this with a 48k file would generate around a million potential keys.