Topic: KEEPING A DEAD COIN’S BLOCKCHAIN ALIVE: IS IT POSSIBLE? (Read 312 times)

It is unfortunate that you have thus far failed to inform us what specific Proof of Stake coin you are working with.

There was development / evolution happening in the old days, many of the earliest Proof of Stake coins required manual "rebalancing" of the "transaction outputs", which is geekspeak for "pile the coins into ideal-sized piles for staking".

Most of the oldest PoS coins required not only that the wallet be online but also that each "pile" (UTXO) of coins "rest" a while before becoming eligible to be used in staking.

Thus having all your coins in one "pile" should give a high chance of "winning" a stake reward, but then that pile would have to rest for a while, and time is of course usually measured in blocks, meaning probably if your huge number of coins at one address is in the form of just one, or just a few, "piles" (UTXOs for example assuming that is what your specific such coin calls them), it might well be the case that all the "piles" in your wallet have already won a stake reward and are all "resting" X number of blocks waiting to become eligible again.

So for example if your coin requires 30 days "rest" to become eligible, and its target block time is one day, you probably need at least 30 "piles" in order that each day one pile becomes eligible, probably winning the reward that day, then the next pile's day has hopefully come, so it probably wins that day, and so on.

If the target block-time is faster than one block per day of course more piles would be required.

Later PoS coins re-balanced automatically, even maybe allowing setting target size of "pile" in config file or by RPC command or commandline "switch".

For example I think one of the differences between Gold Pressed Latinum and Gold Pressed Latinum 2, in addition of course to GPL2 being pure PoS while plain old GPL was hybrid PoW and PoS, is that GPL2 has some form of automatic balancing so you don't have to manually pile your GPL2 coins into "ideal sized" piles (UTXOuts).

If it just so happens that one of the GPLs, or any of the other old PoS coins used in the Galactic Milieu, is the coin you are referring to / having trouble with, you could try adding addnode=LFM.Knotwork.com and addnode=Server1.Knotwork.net to your nodes list too.

-MarkM-

EDIT: I neglected to emphasise that you don't need multiple addresses, all your "piles" can be in the same address; just when populating an address send multiple separate transactions to it if the client does not offer commands for manipulating "piles", selecting from which "pile" to send and suchlike.

Hi again everyone,

thanks for all of your answers!

Any thoughts on why the blockchain is not staking any more coins, considering that, as I said above, I am the third biggest holder of coins in one single transaction?

Thanks a lot.

actually a good goal is to examine the blockchain directly and see the possibility of dead coins can be mined again. but I would rather agree with you, if the coins are dead it means they no longer have volume and that means they are no longer valuable in the market and it is better if they are completely erased to reduce energy consumption.

Thanks for all of your answers, I feel closer to understanding the problem. Yet something still does not add up. Because I am the second largest coin holder (I actually have the coins in ONE single transaction to add more weight on the network) yet I still can't stake. I used to stake until about 10 days ago, then suddendly it stopped when the blockchain syncing stopped as I said previously.

My current getstakingstatus is

{
    "validtime" : true,
    "haveconnections" : true,
    "walletunlocked" : true,
    "mintablecoins" : true,
    "enoughcoins" : true,
    "mnsync" : false
}

Thanks again for your help!

In PoS you need a dormant coin to run the blockchain, your node will not do this job that is why the block will not move up or stuck.
Fork can be a reason for it too, try to stake your coin and observe it. Will the block move up or not

you can of course keep the chain alive, tho you might need to make sure YOUR the seed, (or you recode a hard seed with your own)
you need to read how  PoW chain works man, anyone with the hash can move it, thats WHY its "decentralized"
your problem is because they hardcoded a seednode, the team is a fuck they shouldnt do that except off the bat sometimes to help the network
as you can see tho it causes trouble long term when they take down the network seed
get synced (or pick a checkpoint)
code your own seed
fork into it
chain is yours

I hope your efforts can correspond with your rewards.
Your are dealing with coin which you do not have any information about the history as regards the specifications, the blockchain should have served as a live information.
POS coin often stuck for so many reasons but most especially the “Fake Stake” attacks.
Good luck with your research.

The coins are currently not being mined? And no new block is created? No transaction is taking place any longer. So, the project is abandoned.
The developers probably don't want their projects to be completely dead hence they keep few things running.

Sorry, I mistyped. I did actually use addnode= , in fact as I said at the time the blockchain gets stuck I do see the peers still connected, they just stop syncing.

Thanks everyone for the answers!

However, I forgot to mention that both of the coins that I am experimenting with are 100% POS, so there is no hardware mining involved in it.

So, in view of this, what else could cause, in your opinion, that the blockchain gets totally stuck?

If that coin's client is identical to Bitcoin Core, you're using the wrong parameter.
It should be addnode= without 's' and can be written in multiple lines if you need to manually add more peers.

If you have added other parameters, please tell us.

(For "non-staking" coins) Nodes don't create new blocks... miners do. So unless someone is actively mining, then there won't be any new blocks added to the blockchain. Most people won't bother mining "dead" coins, because it costs money to purchase and run mining hardware. Given that the dead coins are delisted and essentially have zero value, there is no way to convert any mining rewards (block rewards and/or transaction fees) into $$$ to cover those costs.

They're dead for a reason... best to just let them go and help save the planet by reducing energy consumption... It's what Greta would want

Maybe there was simply no new block mined and the block where it stops is the last block?
Then the blockchain is stuck there until somebody mines the next block.

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!