Do you think the devs want to patch the forking issue? Have you heard anything?
I ran a test with the proposed solution. It doesn't appear to help but hurt the network. The proper procedure is to orphan a chain the network rejects. This is part of the consensus building of the network. The proposed solution eliminates this, and actually accepts forks. The end result is unlimited forks and eventual breaking of the coin.
The code works as is.
Bill, no offense, but you are wrong on that point. The code does not "work" as is. The chain is forking at a near constant rate right now -- the "lead" chain just happens to be the one with the highest trust value. The fix simply makes the nodes reject any "fork" that reverts the height -- which is exactly how it should behave.
Either way, the chain is largely functional for anyone who isn't mining. The vast majority of blocks overwritten are the PoW blocks. I've found several other bugs in the client (errors in the TX generation, errors in TX version checks, wallet corruption issues, locking issues, etc.). I've tried to stamp a few out locally but it's rather unstable. I've had a miner running for 4+ days now and the majority of the mined blocks get erased and the wallet corrupts within 30 minutes or so and then needs to be restored.
The coin needs a massive overhaul to make it stable. My fix works to stop the rewinds but fixing the rest of the issues is likely outside my timeframe. $PAC offered me a slot on their team and I think I have to agree with expos that working on a new base is probably more beneficial for everyone at this rate. PAC is good for anyone staking but it's bad right now for anyone trying to mine it or send a lot of TX while someone is mining. I've, personally, got several TX stuck in no man's land as a result of the rewinds and overwritten blocks, I'm sure others do to.