Would also be interested about the actual status of the coin. Is it still supported by the dev? Or is it abandoned?

I hope it will revive after this one year lockdown, right now it seems as it´s in deep sleep.

hopefully we will not see a huge dump when coins get released after one year lockdown. But I expect to see endless dumping of the coin.
Would also be nice to read at least from time to time some news from the dev but from what I read here, the project has been abandonned... could anyone confirm this? Or am I completely wrong...

reposting what I wrote before:

If I have understood what has been posted correctly, when work time permits (a few weeks), Fuzzbawls and Freetrade will write the code to:

1. Fork the coin back to not requiring a one-year time lock on newly mined coins.  Those coins already time-locked will remain so according to their maturity block listed in the wallet.
2. Fix a minor bug with timelock concerning the length of time selectable for term deposits.
3. This will require a new wallet (ver 3.0?)

After that, I would expect additional pools to activate, perhaps Supernova and others.
Nicehash still lists HODL as an option so you may see some mining activity there.
Several people on this forum have said they will be adding their own hashing power to the mining activity.
YoBit, the only current exchange listing HODL, may or may not follow the fork, or may have to be paid to follow it.
One poster here said he would add HODL payment capability to his online grocery.
We will have to convince additional exchanges to list HODL.
We will need to find additional vendors willing to accept HODL as payment.

Does that help?

While this is "the plan", please understand that I signed on as a repository and release MAINTAINER. It was never my intention to be the sole contributor of code changes. That being said, I do still plan to write the code for this fork (if nobody else submits a PR), but keep in mind that as a contractor any/all paid contract work will push this down in priority for me.

This isn't a call for someone to pay me to write the fork code, not at all. It is simply a statement of facts regarding the timeline. At the moment, I have about a week's worth of already paid work that will take priority and I really cannot guarantee that more contract work won't come in the mean time.


The miner improvements are still not satisfactory for windows builds. As previously stated, this is something that I cannot debug myself! This is not my code nor do I have the required hardware to get issues sorted properly. My inclination is to just say "fuck it" for in-wallet miner improvements and let the community invest in proper GBT miner inclusion...or merge the improvements "as-is" and let windows users fumble with in-wallet mining.    Neither are "good" solutions, admittedly, but I don't see much else I can do on my own.

I was bored and tried to submit a block using stratum and submitblock but I still have the issue that blocks aren't accepted because of no hodling time or something similar. How would I need to submit the block to make it work?

Gotta sync my wallet up and see when my locked blocks will mature, I have a feeling it is from now to the next 2 weeks.

i think me 2 , at this point its not much worthy....

Merged the internal miner changes since there hadn't been any new commits in some time. AFAIK it is only windows that has issues with the improvements.




submitting the block isn't the issue, constructing the block from the template is. The coinbase transaction needs to have the OP_CHECKLOCKTIMEVERIFY flag passed in the script, which is of course non-standard. Looking forward, however, this will be a moot point as the next release will revert the requirement and coinbase transactions will be back to "normal" (ie, pre-fork) conditions.

just wanted to drop a line. Recent severe storms in the area here have caused structural damage to my home and surrounding area. I will be taking the next few weeks to address repairs which will of course mean that I won’t be making any code changes for HODL anytime soon.

I STRONGLY encourage opening a call for those in the community with coding skills to submit code change pull requests needed for the fork. Our PR testing is automated and quite thorough. I do get notifications on my phone about PRs, and can still do some quick manual reviews when necessary.