We need a new dev to take over CENT. What say you??The_Catman has royally jacked up the coin and does not know how to proceed. There are already multiple forks, wallets not syncing, etc.
Are these the responses of a confident developer?
I'm not sure why people are getting stuck at 50623, my chain's currently at 242690 and reports that there are currently 243036 blocks in the chain.
I will look into this further.
Alright, I need sleep, I'll continue trying to fix the problem tomorrow.
In the meantime, if anyone happens to be an expert on the proof of stake system, please take a look and see if you have any ideas. There's got to be a stake validation check somewhere I'm missing somewhere. The problem is that the new stake value is being used to check the old stake transactions and it obviously failing. On re-examination the method we used to change it was pretty obviously not going to work, but the other methods I've tried (using block nTime and nHeight, in various ways) don't seem to be working either.
To everyone having Pennies issues after Jan. 8th: Debug instructions
1. Open "Command Line Banking" and type 'getinfo'
- Make sure protocolversion is 7000 (version 0.10.0.0-beta)
- If not, go update to v0.10.0.0
2. Open "Command Line Banking" and type 'checkwallet'
- Make sure it responds {"wallet check passed" : true}
- If not, run 'repairwallet' and wait.
3. If your blockchain is stuck/not syncing
- Check your pennies.conf and wipe any nodes you aren't sure about
- Add 'node.cryptsy.com' Woops, seems cryptsy may have missed the update, hold off on that*
- Save and restart wallet
4. If it's still stuck
- Shut down wallet
- Go into your pennies appdata (%APPDATA%\Pennies)
- Delete all files other than 'pennies.conf' and 'wallet.dat'
- Relaunch wallet
- Wait for it to resync the chain from scratch
If none of this works, just wait a few days for the network to sort itself out, then open an issue on the github.
Alright, from what i'm seeing there's one of 3 problems going on at the moment.
1. Cryptsy is outdated and everyone who is reporting successful transactions is too.
2. There's a fork.
3. Uhhh, I forgot what this one was.
