Quote from: Kam800 on March 14, 2014, 10:37:37 AM

Quote from: vujk on March 14, 2014, 10:22:18 AM

Quote from: Kam800 on March 14, 2014, 06:35:51 AM

Quote from: vujk on March 14, 2014, 05:45:53 AM

My mint wallet has stopped minting since 3/11. I have updated to the current wallet and still nothing. It is unlocked. Any ideas? I found this in the debug log, not sure if it is relevant.

ProcessMessages(version, 101 bytes) : CHECKSUM ERROR nChecksum=f14d14f9 hdr.nChecksum=21f0e818

PROCESSMESSAGE MESSAGESTART NOT FOUND
Huh

Hmm, sounds like some sort of corruption may be at fault here. Checksum implies that one or more files aren't the size that the program expects them to be. I think it's worth replacing all current Mintcoin files with new ones (except wallet.dat ofc)

Give this a shot:
1. Close down your wallet
2. Backup the wallet.dat file somewhere safe.
3. Delete all Mintcoin files on your PC - the QT.exe folder as well as the data in %appdata%\roaming\Mintcoin\... (assuming you're on Windows)
4. Download a new copy of the Mintcoin wallet 1.5
5. Run the exe, wait for it to open and then close it again.
6. Copy your backed-up wallet.dat into the %appdata% folder
7. Restart your client and see if it syncs.

As the coins haven't moved this won't reset their age, as well as ruling out 99% of files potentially corrupted.

ok, I did this. I now show some "stake" in my wallet. But now it is stuck on block 109242, and my debug log has this crap...

received block 9fb99d9eb26563c688b9
ProcessBlock: ORPHAN BLOCK, prev=4db3d6ce487544161c68
received block 4db3d6ce487544161c68
ProcessBlock: ORPHAN BLOCK, prev=4691e4561e3419ec08a7
received block 4691e4561e3419ec08a7
ProcessBlock: ORPHAN BLOCK, prev=0af201510002444622b9
received block 0af201510002444622b9
ProcessBlock: ORPHAN BLOCK, prev=a4bd259ef07e15ffc772
received block a4bd259ef07e15ffc772
ProcessBlock: ORPHAN BLOCK, prev=db07b6d2f06a2c3f5d39
received block db07b6d2f06a2c3f5d39
ProcessBlock: ORPHAN BLOCK, prev=7708fcd256ae76dd4ad6
received block 7708fcd256ae76dd4ad6
ProcessBlock: ORPHAN BLOCK, prev=437b842e2b9b347cbcce
received block 437b842e2b9b347cbcce
ProcessBlock: ORPHAN BLOCK, prev=055f4cc976326559973f
received block 055f4cc976326559973f
ProcessBlock: ORPHAN BLOCK, prev=1a10d32f7c21cd25f763
received block 1a10d32f7c21cd25f763
ProcessBlock: ORPHAN BLOCK, prev=37f5610ba9289fba539a
received block 37f5610ba9289fba539a
ProcessBlock: ORPHAN BLOCK, prev=000000000f195ddc7b1b

Cool, sounds like you fixed the problem

It would appear though that some of the blocks you might have generated got solved by someone else, and are therefore orphaned. You will soon start minting new ones though.

That raises a question though; would the stake that generated an orphaned block be elligible to mint again or is it back on counter for 20-odd days?

Perhaps a dev could help explain, or has anyone who has been minting seen the same stake generate orphans until it succeeds? I've seen rumour of a 20% success rate but don't quote me on that - other people's mileage may vary based on whatever factors may be involved.

I am still having issues if anyone can throw in their 2 cents. The wallet will not sync. I redid all the files, redownloaded most of the block chain. It will not sync past block 114596. It is minting now, but they are stuck on confirms. I have the conf file from 1.5 in the correct spot.

I have some weird stuff in the log file..

ERROR: FetchInputs() : 8367dda47a mempool Tx prev not found 65cb2c80b3
stored orphan tx 8367dda47a (mapsz 4)
received block fe00bb01e7da09f54ec2
ProcessBlock: ORPHAN BLOCK, prev=bd05b6207a81db20e1ee
received block bd05b6207a81db20e1ee
ProcessBlock: ORPHAN BLOCK, prev=860fd4e3cb0168fc4bf8
ERROR: FetchInputs() : c7cd6fed6f mempool Tx prev not found 04f7c03cfe
stored orphan tx c7cd6fed6f (mapsz 5)
received block 860fd4e3cb0168fc4bf8
ProcessBlock: ORPHAN BLOCK, prev=a0ff4e7192bcd658d72

PROCESSMESSAGE MESSAGESTART NOT FOUND