Topic: KEEPING A DEAD COIN’S BLOCKCHAIN ALIVE: IS IT POSSIBLE? (Read 78 times)
@mrprep sorry I posted this in the wrong place (can this topic be deleted please)
sorry moderators, I just relized I posted it in the wrong forum by accident, you can delete this thread as I have posted it in the right forum.
Hi,
As I have a few free VPS servers available and I like researching the crypto industry, I am looking into several cryptocoins that have now been totally delisted from all exchanges.
These coins still have some nodes up and running (some of which might be the devs own nodes possibly).
I would like to keep the blockchain going, just in case there is a community takeover of the project like it has happened in a few cases.
Before launching these nodes, I make sure that in the conf files I have the addnodes= lines pointing to my own nodes as well as those that are still online that might belong to the devs.
However, blockchain syncing for my nodes stops at a specific block (the same block across all the nodes) and does not get past this hurdle.
I can see the peers still being connected at this point, but syncing stops for all of the nodes at exactly the same block and point in time.
I have tried deleting peers.dat, deleting all files except wallet.dat and the .conf with the addnodes, reindexing… all to no avail.
Now I am quite puzzled…. why would syncing stop as if “a central reference server” was missing if the blockchain is supposed to be fully decentralized?
Also, if I am correct in thinking that some of the few nodes that are not owned by me belong to the devs, why would they intentionally leave nodes running on a dead coin?
I would be grateful if I could have the comments from some blockchain experts regarding this issue.
Many thanks!
As I have a few free VPS servers available and I like researching the crypto industry, I am looking into several cryptocoins that have now been totally delisted from all exchanges.
These coins still have some nodes up and running (some of which might be the devs own nodes possibly).
I would like to keep the blockchain going, just in case there is a community takeover of the project like it has happened in a few cases.
Before launching these nodes, I make sure that in the conf files I have the addnodes= lines pointing to my own nodes as well as those that are still online that might belong to the devs.
However, blockchain syncing for my nodes stops at a specific block (the same block across all the nodes) and does not get past this hurdle.
I can see the peers still being connected at this point, but syncing stops for all of the nodes at exactly the same block and point in time.
I have tried deleting peers.dat, deleting all files except wallet.dat and the .conf with the addnodes, reindexing… all to no avail.
Now I am quite puzzled…. why would syncing stop as if “a central reference server” was missing if the blockchain is supposed to be fully decentralized?
Also, if I am correct in thinking that some of the few nodes that are not owned by me belong to the devs, why would they intentionally leave nodes running on a dead coin?
I would be grateful if I could have the comments from some blockchain experts regarding this issue.
Many thanks!
Jump to: