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

[Spekske]

We need more hosts for addnodes for everyone.


To host, AFTER you verified you are on the latest fork!

You just need this galaxycoin.conf and have port 15521 open to the world

Code:

listen=1
daemon=1
server=1
rpcuser=**Yourusername**
rpcpassword=**Yourpassword**
rpcport=15522
rpcconnect=127.0.0.1
addnode=71.4.209.204

You can also add verified addnodes to your config later.

The client works with that single connect= entry in the .conf and your .zip file, BUT as soon as you change anything like trying to run it with daemon=1 or server=1 options it crashes again with the exception runaway error....

[ADRIATICon]

We need more hosts for addnodes for everyone.


To host, AFTER you verified you are on the latest fork!

You just need this galaxycoin.conf and have port 15521 open to the world

Code:

listen=1
daemon=1
server=1
rpcuser=**Yourusername**
rpcpassword=**Yourpassword**
rpcport=15522
rpcconnect=127.0.0.1
addnode=71.4.209.204

You can also add verified addnodes to your config later.

The client works with that single connect= entry in the .conf and your .zip file, BUT as soon as you change anything like trying to run it with daemon=1 or server=1 options it crashes again with the exception runaway error....

Still works fine on Windows 8.1 at least.

[ADRIATICon]

Thanks to all for their help!

Updating main post!

great! I believe Cryptsy must have been informed by now.

Cheers!
Soopy

I do see a small test deposit going into Cryptsy from my Windows 8.1 client in Pending status, 0 confirmations there and 22 in the Windows client. I have a ticket open with Cryptsy in case it gets "stuck" again.

[ADRIATICon]

Thanks to all for their help!

Updating main post!

great! I believe Cryptsy must have been informed by now.

Cheers!
Soopy

I do see a small test deposit going into Cryptsy from my Windows 8.1 client in Pending status, 0 confirmations there and 22 in the Windows client. I have a ticket open with Cryptsy in case it gets "stuck" again.

Cryptsy's response:

"Thank you for contacting us about this issue. Please give it 24hours for
deposit to show due to high volume of deposits. Let me know
when your deposit has gone thru. Thank you kindly for your patience
and understanding."

[ckoeber]

The client works with that single connect= entry in the .conf and your .zip file, BUT as soon as you change anything like trying to run it with daemon=1 or server=1 options it crashes again with the exception runaway error....

Hmmm, OK what operating system are you using?

As another person has mentioned this works fine on Windows 8.1.

[Spekske]

The client works with that single connect= entry in the .conf and your .zip file, BUT as soon as you change anything like trying to run it with daemon=1 or server=1 options it crashes again with the exception runaway error....

Hmmm, OK what operating system are you using?

As another person has mentioned this works fine on Windows 8.1.

I did a fresh install on windows 7 64 bit

[ckoeber]

I did a fresh install on windows 7 64 bit

OK I will try it out on a Win 7 box today sometime and will look at what needs to happen to make those clients work.

[Spekske]

I did a fresh install on windows 7 64 bit

OK I will try it out on a Win 7 box today sometime and will look at what needs to happen to make those clients work.

One more note, I started that same pc this morning, it has nothing else running on it, left the galaxycoin.conf with only that line connect=x.x.x.x and it came up with a message that the qt-client has stopped working, after pressing close program and waiting another 5 minutes or so it still starts running, but there are obviously some bugs still in it. If possible and if you have time maybe also have a look at the Linux daemon, I would like to run galaxycoind for hosting on my server but it gets stuck at block 18924, even when I enter the same info in the .conf file, plus rpcuser and pass of course or it won't run

[ckoeber]

Two warnings to everyone in the GalaxyCoin community that only you can solve:

1. We need more systems out there hosting the new fork so that there are more addnodes! I believe everyone is connecting to my system, which is fine for the moment but not good long term.

2. Still too many people on the old fork. It is probably still working because the developers set it up so that difficulty changes do not start occurring until the 255,145 block but after a while we will have two serious forks. Get the NEW client and get it synced to the NEW fork!

If these two things aren't largely remedied by those reading what I just said then folks will be sorry!

[TheCoinFinder]

Try adding glx.verters.com - port 15521 is open and blockchain is New Fork and up to date

[ckoeber]

Try adding glx.verters.com - port 15521 is open and blockchain is New Fork and up to date

Thanks. Need all the help we can get.

[Spekske]

Try adding glx.verters.com - port 15521 is open and blockchain is New Fork and up to date

I have tried most of those options on my Linux machine with the same result every single time, it stops at block 18924, I have just removed everything once more, downloaded from the new source, recompiled, start galaxycoind with only 1 connect= address in the .conf and the same happens again, there is something weird going on, port 15521 is open and pointing to that server on the firewall so all should work but it doesn't... I have even tried removing all contents again, use glx.verters.com as the only connect= adddress and the same happens yet again....

[Spekske]

Try adding glx.verters.com - port 15521 is open and blockchain is New Fork and up to date

I have tried most of those options on my Linux machine with the same result every single time, it stops at block 18924, I have just removed everything once more, downloaded from the new source, recompiled, start galaxycoind with only 1 connect= address in the .conf and the same happens again, there is something weird going on, port 15521 is open and pointing to that server on the firewall so all should work but it doesn't... I have even tried removing all contents again, use glx.verters.com as the only connect= adddress and the same happens yet again....

I now have galaxycoind.exe on my windows machine running, it is on the new fork and can be used as an extra node, 87.209.206.80, I'll leav it running until there is a solution for the Linux version and I can switch over to that server, but the ip address will remain the same.

[ckoeber]

Try adding glx.verters.com - port 15521 is open and blockchain is New Fork and up to date

I have tried most of those options on my Linux machine with the same result every single time, it stops at block 18924, I have just removed everything once more, downloaded from the new source, recompiled, start galaxycoind with only 1 connect= address in the .conf and the same happens again, there is something weird going on, port 15521 is open and pointing to that server on the firewall so all should work but it doesn't... I have even tried removing all contents again, use glx.verters.com as the only connect= adddress and the same happens yet again....

Thanks for the effort; I'll check to see if the Blockchain I have zipped up will work on Linux clients.

[TheCoinFinder]

Same with the broken block at that early stage.

This is what happens if I try to sync from beginning.

Unzipping the blockchain and working from there works instead though

[Spekske]

Try adding glx.verters.com - port 15521 is open and blockchain is New Fork and up to date

I have tried most of those options on my Linux machine with the same result every single time, it stops at block 18924, I have just removed everything once more, downloaded from the new source, recompiled, start galaxycoind with only 1 connect= address in the .conf and the same happens again, there is something weird going on, port 15521 is open and pointing to that server on the firewall so all should work but it doesn't... I have even tried removing all contents again, use glx.verters.com as the only connect= adddress and the same happens yet again....

Thanks for the effort; I'll check to see if the Blockchain I have zipped up will work on Linux clients.

I have even tried that option but it states it cannot load blkindex.dat

[almightyruler]

FYI, I was able to use the zip to get a FreeBSD (64 bit) compile of the new client kickstarted. Had no luck syncing until I downloaded the correct blockchain.

[TheCoinFinder]

Hmm seems like the blockchain is damaged early on.

Is there a reason we are trying to use the old blockchain still?

[ckoeber]

Hmm seems like the blockchain is damaged early on.

Is there a reason we are trying to use the old blockchain still?

Preservation of transaction history; if we completely start a new blockchain then your old coins are worthless.

It'll be like starting a completely new alt-coin.

[Tommo_Aus]

Tompool.org pool is updated to the latest GLX fork