Topic: [RE-ANN] Galaxycoin Revival! KGW, POS/POW hybrid [TRADING ON CRYPTSY] - page 15. (Read 51784 times)

Hey ckoeber, mind giving me an update on the status of your pool/node? Everything OK over there? I'm unable to connect to either. Thanks

A static IP is a bit better, but a diverse p2p network is fairly resilient; so long as you can connect (outbound) to at least one peer, the rest of the network will figure out your IP for inbound connects.

Good call, I'll get on that. I'll let you know when it's up!

More nodes

Woohoo!

Shhh! I'm mining the genesis block at the moment.

Also, you could use a service like noip.com to get a static ip for a node, I can stick that in the galaxycoin.conf example

Alright sounds good, I'll do my best to get on setting that up. I'm on university internet at the moment, so nothing I can do from here. As soon as I get the chance I'll try to get a permanent node set up at my house. Will I need to get a static WAN IP for that? Never heard whether or not TWC will do that, and never paid attention to how frequently it changes.

PS: icecube45coin. haha. awesome.

I also note a lot of intensive peer activity on the node at 193.68.21.36, some indeed seem to be old clients stuck in a loop. Hope to find some time to actually plot the bandwidth consumption of the node, might be interesting. The peer sync code indeed needs some blacklisting/throttling functionality and also probably a "boost/bootstrap" mode to let new clients download the block chain faster.

I will be setting more nodes, if it helps the network. Just to stop traveling for a bit

Thanks for that warning!

I might firewall those peers as well, don't want my bandwidth being used!

Just a warning that when a coin forks the older clients can be quite aggressive with requesting blocks. They request the same set of blocks over and over, I guess because of a bug or oversight in the code.

For example, 148.251.13.39 appears to be on the old chain (starting height 251827). I tracked its bandwidth for a period of 60 seconds:

128804 bytes in
1398272 bytes out

... and it's constantly growing. It seems the older client can never internally resolve the fork, so it gets stuck in some sort of loop requesting the same blocks.

As mentioned earlier in this thread it has had an impact on my DSL link; I have had to resort to firewalling GLX peers that are on the old fork to stop them hogging it.

edit: there are currently 3 old chain GLX peers consuming about 0.5Mbps of my 1Mbps uplink speed (50% of my entire upload capacity)

Download the client and make sure it is 100% synced. Follow the guide on the first post.

Make sure this is what your galaxycoin.conf config file is like:


Then, open port 15521 to the world; you can then announce the IP address everyone else should connect to for your system.

As for bandwidth see this: http://bitcoin.stackexchange.com/questions/12974/what-is-the-bandwidth-of-the-standard-bitcoin-client-as-at-august-2013

Woohoo! We'd love a new node!

Its as simple as port forwarding the connection port, and running the client!

I'm not sure about the bandwidth usage, but it shouldn't be much.

Thanks so much!
-icecube45

Hey ckoeber or icecube: (or anyone that can explain really)

I am definitely willing to host a node if it's something I have the resources to do. I don't have a web server, but if possible, I'll help from home. I'm on the correct chain, is there anything more to it than running galaxycoin-qt and possibly keeping a port forwarded? And using "connect" instead of "addnode"?

Also, what kind of bandwidth will this consume/what will I need? (preferably tcp) I only have a 1M upload at my house.

If this will be a lengthy setup, feel free to PM me. Actually, if you post it here, maybe someone else will join in too and we'll have more nodes.

Sorry if this is noob question

It is. I am not sure why that is happening myself. As IceCube45 has mentioned once more addnodes come in the issue should be resolved.

At this point, the syncing of the blockchain naturally is a VERY long process, due to the amount of nodes still on the V1 blockchain, as more nodes transfer to the V2 blockchain, this should resolve itself..

For now we need to rely on this download, unfortunately, but hopefully not for long,

Everyone can help by hosting a node

Things work with your block chain database. But the coin daemon (wallet) is supposed to be able to build and verify it's own block chain, from the network. This does not seem to happen -- something is seriously broken. The wallet always ends up to

"blocks" : 18924,

Depending on pre-built block chain is risky..

By the way, on a client I left to download the block chain from scratch, I now get this (repeated already several times):

03/22/14 13:06:31 received block 0000008eae20635f44ff
03/22/14 13:06:31 SetBestChain: new best=0000008eae20635f44ff681b6efc740b1501721c0d871d5f54e08d3c6baac001  height=18924  trust=18925  blocktrust=1  date=07/17/13 08:04:10
03/22/14 13:06:31 ProcessBlock: ACCEPTED
03/22/14 13:06:31 received block 2273c83fc8168441c0c3
03/22/14 13:06:31 ERROR: ConnectInputs() : 2bd7a74729 stake reward exceeded
03/22/14 13:06:31 InvalidChainFound: invalid block=2273c83fc8168441c0c3  height=18925  trust=1587918  blocktrust=1568993  date=07/17/13 08:04:12
03/22/14 13:06:31 InvalidChainFound:  current best=0000008eae20635f44ff  height=18924  trust=18925  blocktrust=1  date=07/17/13 08:04:10
03/22/14 13:06:31 ERROR: SetBestChain() : SetBestChainInner failed
03/22/14 13:06:31 ERROR: AcceptBlock() : AddToBlockIndex failed
03/22/14 13:06:31 ERROR: ProcessBlock() : AcceptBlock FAILED
03/22/14 13:06:31 received block 000001b716889e17bd32
03/22/14 13:06:31 Postponing 1 reconnects
03/22/14 13:06:31 REORGANIZE
03/22/14 13:06:31 REORGANIZE: Disconnect 0 blocks; 0000008eae20635f44ff..0000008eae20635f44ff
03/22/14 13:06:31 REORGANIZE: Connect 1 blocks; 0000008eae20635f44ff..2273c83fc8168441c0c3
03/22/14 13:06:31 ERROR: ConnectInputs() : 2bd7a74729 stake reward exceeded
03/22/14 13:06:31 ERROR: Reorganize() : ConnectBlock 2273c83fc8168441c0c3 failed
03/22/14 13:06:31 InvalidChainFound: invalid block=000001b716889e17bd32  height=18926  trust=2633914  blocktrust=1045996  date=07/17/13 08:04:16
03/22/14 13:06:31 InvalidChainFound:  current best=0000008eae20635f44ff  height=18924  trust=18925  blocktrust=1  date=07/17/13 08:04:10
03/22/14 13:06:31 ERROR: SetBestChain() : Reorganize failed
03/22/14 13:06:31 ERROR: AcceptBlock() : AddToBlockIndex failed
03/22/14 13:06:31 ERROR: ProcessBlock() : AcceptBlock FAILED
03/22/14 13:06:31 received block 0000038bcfde6a76a612
03/22/14 13:06:31 Postponing 2 reconnects


it then goes on and on and postpones up to 499 reconnects...

The permanent node at 193.68.21.36 has been updated to version 2.0.0.

The mining pool at http://glxpool.digsys.bg has been upgraded to 2.0.0.

Sorry for the late reaction, I happen to travel quite a lot around the world recently.

1) Yes, can not agree more that community contributors should be respected. 
2) But it does not naturally prove that it is right to make a folk in this way. As a coin holder, it is wired to see your coin gone after a compulsory update.
3) As a cryptocurrency, the GLX should be handled as a mission critical software. Higher standard of testing should be involved before any update, especially for the compulsory one.

The price of GLX is crashing, it might be a lesson for everyone.

A community contributor should not be treated and talked to that way and made fun of , if you really wanted to put blames please do so to the original dev , who made a coin and abandoned it , you should be grateful , if not for this team , GLX would be long gone and dead and all your coins proved worthless and I believe there's an apology for the entire community who's putting their time and effort to keep GLX what it is and expect nothing in return , unlike devs who premine and run away with it , here it's about LOVE for what we LOVE to do mate and what we expect in return is appreciation and a little bit of respect for what we do.

Please keep that in mind when throwing around blames.

Regards,
Soopy
Community Developer