I had to manually delete the chain again, restore a backup, reconnect manually, unlock my wallet, restart my miners... then I was able to mine again. From 1AM to 3:30AM my miners were dead in the water...
I HOPE that is not "what it was supposed to do"... That is the problem we have all had. With the addition of no reconnections, which I still have. I just happened to luck out and catch 2 new connections that just joined the chain. The rest in the list are auto-killing my connection attempts to them, once they get connected. (As if I was personally responsible for the misbehaving. Guilt by association, though we were all connected to that peer. How do 20 connections stay, and five get perma-ban and isolated to mining alone, every time?)
When it says "not enough proof of stake"... is it complaining because someone created a POS block, and there was already enough "claimed"... Thus, not enough POS to accept that block? It shouldn't disconnect us for that, ever... just reject it, and update the height, as obviously, that one that submitted the block did not have the latest POS block, which was the "limit" for that minute/hour.
Unless it is complaining that someone created a POS but they didn't have enough POW blocks to convert to POS, thus, not enough POS... (That is the most uninformative warning I have ever seen. lol. Might as well say, "something didn't work right" as the warning... like javascript does! xD)
If it is bitching about someone creating a POS for a block which they don't have enough POW available... then you need to check one of two things in our wallets... or both...
1: Is there a POW block ready for POS (then mine POS, if it is accepting POS on the system)
2: Is there STILL a POW block ready for POS (then submit POS, if it has not been spent, or consumed by a prior POS solution)
Optionally 3: Reserve 10 POW for POS, prior to mining/solving the actual POS block, as "unavailable for POS"... Since I notice that POS happens first, THEN it removes the coins after submitting... at which point the coins could have been spent, or consumed by a POS that just got accepted a few seconds ago.
and on the other side...
Don't kill people because they submitted what they thought MIGHT be accepted, being unaware that the unrelayed POS block the server didn't distribute, was the last POS block that was just about to be sent to that user for building-on. Simply ignore it, since it is a POS block, that has near-zero diff, and you should be expecting a ton of invalid ones to arrive, as we all solve them real fast. (Unless you raise the diff, then they come more spaced-apart, and traverse the network to us, faster. Stopping us from submitting the POS we were just about to submit, if we thought the limit wasn't reached yet.)
If the first thing is true... about us being banned because the wallet is creating POS for POW's that we don't have available... then you might want to tell us to stop mining when there is (limit - 1), as having one less will not matter on the next cycle it will ask for one more. However, that WILL reduce the last flood of submissions, letting the ones still in transit, or ones that have not gotten the (limit value) yet... get accepted without forking and rejecting them for something the wallet did.
Also...
Instead of just "disconnecting us", under suspicion of whatever... (Which is what is creating the forks, the program isolates us as a group, through the one relaying to the one severing the connection.)
Give the program some kind of warning to let it know WHY it is being disconnected, before disconnecting. If only so you can locate the issue better, by talking to the one being disconnected. Since you have no idea who is disconnecting who, or why, unless you witness it yourself. It is easy to find those of us getting disconnected. We are the ones frequenting the forums.
But it doesn't tell us why we are being rejected, it just rejects us.
