There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:
invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8
This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.
Great that you find the issue after someone mined > 8h on the broken version of your wallet. Maybe you should think about developing and testing on testnet next time.
There's no problem with tpruvot's miner at all, why would hashrate be displayed correctly on other pools but not on MPH? But it's always good to "fix" things by breaking them.
And did you even check what's in the commit of that pull request ? It's basically just commenting out submitting stale shares:
https://github.com/tpruvot/ccminer/pull/24/commits/ab4487105eb2766face0b52db1a778fd1220fd39I wonder if there's ANY technological knowledge here as I cannot see any kind of positive development whatsoever...
The old wallet is based on 0.8.x branch of bitcoin.. Years old.
Syncing takes about a week to finish to the current chain.
"importprivkey" forces a full resync of the chain - 2 weeks
Moving wallet.dat away (for backup) and restarting the wallet - again a full resync (2 weeks)...
"getblocktemplate" often says "connectinputs() failed" and doesn't deliver a template to work on
If there are several (zerocoin) tx'es in mempool the wallet responds slower and slower to getblocktemplate or other queries.
Maybe you want to fix up at least A FEW things and work with other pools as well as just with 95% hashrate centralization "MPH" fixing things for them in their favour.
Show Posts
