Can the LWMA (Linear Weighted Moving Average) Difficulty Adjustment Algorithm save hacash？

[ADcarry-tech]

To put it bluntly, the fact that the Hacash blockchain is still running right now is all thanks to World Pool's persistence—they keep advancing the block height despite the high difficulty. But when the difficulty drops, JustFine switches its hash power over and raids. This is essentially hash power fraud. Yet the project team hasn't made any changes to address this. Although they previously gave a bunch of reasons, saying things like "once the hash power increases, hash power fraud will be avoided," I think this explanation is very unrealistic. The current situation is that JustFine is able to obtain cheap coins precisely because of this behavior, which is causing the price to stagnate. How can we wait until hash power increases to the point where fraud can be prevented?

The current situation doesn't look very optimistic to me. It's thanks to World Pool still having confidence in Hacash that they tolerate JustFine's disgraceful behavior. If one day World Pool stops driving the chain forward, Hacash's block growth will stall or become extremely slow. I don't think this is good for Hacash at all. I really don't understand why the project team won't update the difficulty adjustment mechanism. If World Pool pulls out, we won't reach block height 765,432 by the end of the year. I strongly urge the project team to consider updating the difficulty adjustment mechanism.

1. It’s not about scale, it’s about the exploit:
   We welcome massive hashrate—IF they mine 24/7 and secure the network. But what Justfine does is "Pool Hopping." They drop massive hashrate to mine blocks in seconds, intentionally triggering a massive difficulty spike, and then abruptly leave. They are exploiting a slow Difficulty Adjustment Algorithm (DAA), not just competing.

2. Your regular PC wouldn't survive:
   You said you would mine with a regular PC if others left. Here is the reality under the current algorithm: When the whale pushes the difficulty to the moon and leaves, the difficulty stays locked at that extreme high. Your regular PC would take months or years just to mine a single block. The blockchain literally freezes ("blockchain stall"). No small miner can survive the aftermath.

3. The "We just need more hashrate" fallacy:
   You are right that if the network's baseline hashrate was equal to Justfine's, this wouldn't be an issue (like Bitcoin). But how does a developing project attract massive, stable hashrate? By having a fair, stable environment. If the current broken DAA constantly allows whales to use the network as an ATM and leaves regular miners in the high-difficulty trap, no one will ever stay to build that baseline hashrate.

Fixing the DAA using LWMA is not about punishing big miners; it’s about fixing a math loophole that allows the blockchain to be frozen. Every growing PoW coin has to patch this.

Regarding the recent fatal vulnerability where whale miners (like Justfine) use massive hashrate to maliciously conduct "hashrate oscillation attacks," accumulating tokens at low difficulty and abruptly leaving when the difficulty peaks—thereby trapping loyal miners in a virtually unmineable state for long periods—we must immediately implement technical countermeasures. Considering the team's limited development bandwidth and the need for immediate results, I strongly recommend executing an emergency hard fork to adopt the industry's simplest and most mature solution: the LWMA (Linear Weighted Moving Average) Difficulty Adjustment Algorithm. This algorithm is specifically designed to counter sudden hashrate spikes and drops, requiring minimal code changes without complex underlying refactoring. Developers simply need to search GitHub for the widely recognized open-source solution "Zawy12 LWMA" and spend a fraction of time replacing the current difficulty calculation function (for example, setting it to reference the past 60 blocks). This guarantees that whenever massive hashrate maliciously cuts in, the difficulty will instantly skyrocket to force the attackers out, and conversely, it will drop rapidly to protect the remaining miners once the malicious hashrate retreats. This is currently the most pragmatic approach with the lowest developmental cost (only a few dozen lines of code) to completely crush this pool-hopping exploit. For the sake of the project's ecosystem and the survival of our true community miners, I urgently implore the team to evaluate and deploy this life-saving update as soon as possible.

It is crucial to sacrifice "greater complexity and slight precision in release timing" in exchange for "ultimate block smoothness". We should first ensure the stability of the train's speed before considering the comfort of the passengers, shouldn't we?

Looking forward to your reply！

[ADcarry-tech]

Or, without changing any mechanism, could we reduce the difficulty adjustment of 288 blocks to 60 or 30 blocks, thereby increasing the cost of frequent switching by speculative computing power, and ensuring the stability of the main network? @jojion @jojoin @secretary010 @jcb55 @vaibhavch @