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

[ckoeber]

Sounds fun, any free samples?

Crazy; as you know mid conference Facebook bought Oculus Rift.

They were the small cool booth on Tuesday and by Wednesday/Thursday they were worth more than at least half of all of the other companies there.

Combined.

[ckoeber]

Awesome! Sounds like fun. I just started to get a little worried because I can't connect to any nodes currently, so can't even solo mine without creating a third fork

Just wanted to make sure it wasn't my end and that you were aware. Thanks!

I am really sorry; I can't connect to my server on the east coast and I am all the way on the west coast.

I do know your wallets are safe; I have the latest backup on a separate server which I can see.

I bet is just a hiccup that a reboot will take care of but I need to be there, of course

[danbi]

How do we decide which fork is the "good" one?

[almightyruler]

How do we decide which fork is the "good" one?

Code:

addnode=148.251.70.194
addnode=192.95.29.176
addnode=203.20.114.252

I think the first IP may be Cryptsy, or at least it is connected as a peer to Cryptsy. I did a test deposit earlier and it succeeded.

[cannonfodder]

Any chance someone could re-upload the blockchain somewhere since the link posted here isn't working? I'm unable to sync past block 18924 using the addnodes posted here. Thanks.

[icecube45]

Any chance someone could re-upload the blockchain somewhere since the link posted here isn't working? I'm unable to sync past block 18924 using the addnodes posted here. Thanks.

I'll try to do so tonight.

His link should be back up soon

[obelisk910]

So after updating my galaxycoin.conf to include the 3 nodes almightyruler posted earlier, I am now able to connect to 1 peer. However, my wallet isn't syncing. (Client has been open for several hours.)

Is this reason for concern? Is something wrong with my setup or are others experiencing the same troubles?

[harveyweizhao]

Try following nodes:

212.83.187.132
192.95.29.176
162.220.246.58
188.226.169.38
27.118.30.26
192.92.129.48
54.201.121.142
155.69.222.247

[obelisk910]

Awesome, I'm up to date now! Thanks for the addresses.

[cannonfodder]

Try following nodes:

212.83.187.132
192.95.29.176
162.220.246.58
188.226.169.38
27.118.30.26
192.92.129.48
54.201.121.142
155.69.222.247

Awesome, I'm up to date now! Thanks for the addresses.

Still a no go for me. Only syncs up to block 18924. Still hoping for the blockchain to get re-uploaded or for chriskoeber.com to come back online.

[Painful Truth]

How do we decide which fork is the "good" one?

By checking the current block. Compare with the good fork.

[almightyruler]

I think there may be an issue with the checkpointing code.

I'm synced to block 280156 (0000000011da6f86eb6d51a675f6af2101272fd2f4eee95686b3c75966fc9352), presumably on the correct chain, yet RPC 'getcheckpoint' shows a checkpoint from August last year:

Code:

{
    "synccheckpoint" : "0000000762d2c9455efbe448e9b47fd45c9690429fc3ab9305384f90b61147aa",
    "height" : 51870,
    "timestamp" : "2013-08-03 17:46:50 UTC"
}

I noticed this when doing testing for a coin I'm currently reviving. Some other PoS/PoW coins are also showing similar behaviour... but some are showing the expected newest checkpoint. This is just a wild guess, but I think that the code may only store checkpoints at the time you first install the coin. So the highest checkpoint at that time gets stored in the db, but any additional hardcoded checkpoints from future releases are not recognised. I don't know if this is intentional, but reusing the ppcoin code without changing the central checkpointing features (keys etc) has broken it, or it's a known bug that has already been fixed in some coins.

[danbi]

Is PoS working for anyone? I see my wallets try to PoS and end up with generating 0.0 coins, like this:

04/04/14 09:52:41 StakeMiner : proof-of-stake block found 1aec5486366a4a0abb7801c8976895da3cfbfac9e75e882986554c5342b777f
2
04/04/14 09:52:41 BitcoinMiner:
04/04/14 09:52:41 new block found  
  hash: 1aec5486366a4a0abb7801c8976895da3cfbfac9e75e882986554c5342b777f2  
target: 0000070369000000000000000000000000000000000000000000000000000000
04/04/14 09:52:41 CBlock(hash=1aec5486366a4a0abb7801c8976895da3cfbfac9e75e882986554c5342b777f2, ver=5, hashPrevBlock=0000
029c97ede08ae5d89bf440d4da1fb0912e969d3f8ec182d6c9304860abd3, hashMerkleRoot=ee2fb589568ae33fcf7860b9ab31ec23526238d15d97
9a431873e78c014cff97, nTime=1396605160, nBits=1e070369, nNonce=0, vtx=2, vchBlockSig=3045022100c6fa41c382b3b7f204ed44578b
a086aea654fdd52c0c4e7b5b5078ca4f0e963b02201bdfe0701b6fac850568ac9440d71fa38c605 8f1804206e18440105c0a03998a)
04/04/14 09:52:41   Coinbase(hash=55419e4618, nTime=1396605160, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 032e48040106062f503253482f)
    CTxOut(empty)
  Coinstake(hash=5a1a276cb0, nTime=1396605160, ver=1, vin.size=1, vout.size=3, nLockTime=0)
    CTxIn(COutPoint(d962c37983, 1), scriptSig=30450221008a6a96846b09b9)
    CTxOut(empty)
    CTxOut(nValue=63.0095, scriptPubKey=03e03b99ff204ab13b808ca96449ee29d0a43fb00a5119e0445f9f32fbe6cf86ab OP_CHECKSIG)
    CTxOut(nValue=63.00965, scriptPubKey=03e03b99ff204ab13b808ca96449ee29d0a43fb00a5119e0445f9f32fbe6cf86ab OP_CHECKSIG)
  vMerkleTree: 55419e4618 5a1a276cb0 ee2fb58956
04/04/14 09:52:41 generated 0.00
04/04/14 09:52:41 AddToWallet 5a1a276cb0  new
04/04/14 09:52:41 WalletUpdateSpent found spent coin 127.009nvc d962c37983318db1c65081c50854a5f7a6743cc5311da76811bd282bc1afda4b
04/04/14 09:52:41 SetBestChain: new best=1aec5486366a4a0abb7801c8976895da3cfbfac9e75e882986554c5342b777f2  height=280622  trust=38765705825153  blocktrust=2392192  date=04/04/14 09:52:40
04/04/14 09:52:41 ProcessBlock: ACCEPTED

I then see an transaction like this

    {
        "account" : "",
        "category" : "generate",
        "amount" : 127.91500000,
        "confirmations" : 125,
        "generated" : true,
        "blockhash" : "1aec5486366a4a0abb7801c8976895da3cfbfac9e75e882986554c5342b777f2",
        "blockindex" : 1,
        "blocktime" : 1396605160,
        "txid" : "5a1a276cb05b69c3b2656f0382b3eced722e4469706751b1feb110a28a0d85f3",
        "time" : 1396605160,
        "timereceived" : 1396605160
    },

Does this mean I actually got 127.915 generated, despite the message? Or was my earning just 0.906?
( wasn't paying attention to the balances)

EDIT: doing some calculations on the transactions, I figure out it is indeed working, and in this case produced 0.906 coins.

[icecube45]

ckoeber
The unzip command on some linux machines will result in corrupted files,
I recommend revising your script to fix this, perhaps upload a .tar.gz file instead of a .zip

[icecube45]

Is there an update coming, stuck on block 18924?

You're on linux?
Please use ckoeber's script for upgrading to the 2.0 blockchain, linux wallets have a problem atm updating past that block

[SolidStateSurvivor]

Mining Pools:

Chriskoeber- ON NEW FORK
http://galaxypool.chriskoeber.com
0% fees
(Chriskoeber was an active part of keeping the community alive)

Danbi's pool- NEW FORK
http://glxpool.digsys.bg
0% fees

Cryptcoins NEW FORK
http://galaxy.cryptcoins.net
Proportional Payout

Verters NEW FORK
http://glx.verters.com/
1% Fee. Prop Payouts.

http://galaxypool.chriskoeber.com <-- Is no longer up, at least hasn't been for days, or weeks.
http://glx.verters.com/ <-- Neither is this.

http://glxpool.digsys.bg <-- Dunno what this guy is doing but as soon as you start mining there he puts his big solo miner in the pool and takes it out of there when you stop.

http://galaxy.cryptcoins.net <-- 5.23% fees (with the reward included) Enough said.

[andyge]

Resistance to attack 51%, seems a little less.
Too few million total 5000.
Wallet connection is slow, is also upload?

[danbi]

http://glxpool.digsys.bg <-- Dunno what this guy is doing but as soon as you start mining there he puts his big solo miner in the pool and takes it out of there when you stop.

I am running this pool.

Would you please explain how this conclusion came to life? I keep three small CPU miners on the pool in order to make it tick, and their total is under 150 hash/s (kilo hashes per second).

Recently, there have been visitors to my pool, perhaps you one of them, who managed to provide over 70% of the network hashing power. Clearly, GLX needs more miners in order to prevent events like this. I even wondered if my pool had not created a fork..

The pool is otherwise ok, I will just use the time when you guys aren't here to update the software a bit.

EDIT: The new MPOS theme is indeed ugly.

[icecube45]

Hmm, thanks for the update on the pools..
As for ckoeber's pool, it's been going in and out.

And for the stuck wallets... try using connect= (node here) in your config.

[icecube45]

Hmm, thanks for the update on the pools..
As for ckoeber's pool, it's been going in and out.

And for the stuck wallets... try using connect= (node here) in your config.

Not to sound rude.. But.. Like I said in the post "not working with any solutions on here". I'm a tech & have been building computers & installing/updating software for over 10yrs, add nodes/connect was the first thing I've changed (redownload the with all option I could find).. Are there any other solutions you might have?

Here is what i'm running, on Windows?
****
v2.0.0.0
OpenSSL 1.0.1e 11 Feb 2013
18924
255318
Wed Jul 17 03:04:10 2013
****

Haha, sorry
We get the variety of users here.
Join me in freenode, ##galaxycoin.
I'll help you 1 on 1