Good approach, RJF, but things like the bug I pointed out 6 posts above yours need to be ironed out yesterday, considering the volume & interest that this coin has gained, in order to keep that momentum going.
If people can't trust the totals in their wallets, or t hat a wallet will function on the exchange (it has been in maintenance for how many days now on coinexchange.io?) or that stakes will be accurate and accepted/added to current wallet funds within a few hours of minting, then we have a big, big problem on our hands in terms of investor confidence.
#1 problem to fix: accurate & reliably awarded & confirmed stakes #2 problem to fix: stability with the pending vs available totals in the wallet, without the need to re-sync.
if you can isolate the problem and fix it, then feel free to make a pull request to the github. although i will save you some time and explain that there is no error, your stakes were just being orphaned. orphaning is a natural process in the blockchain growing.
To everyone else who has been waiting patiently (thank you btw) I guess i should explain what is taking so long.
Here's a technical explanation:
The wallet had a problem with sending messages due to a seg fault that would occur when trying to lock the critical section required to copy memory to the sending data stream which is used to actually send messages between the peers on the network. The easiest way to find an error with seg faults or mem leaks for C++ is a tool called valgrind. However valgrind takes almost 2x as much resources and runs slower than the program would by itself. so every time i made a change to a build and ran valgrind it would take between 1 and 2 hours to find out if the change actually worked. A very slow process. Assuming my latest change actually fixes the problem (and based on the pthread_mutex documentation found here:
http://www.cplusplus.com/reference/mutex/mutex/ i have a feeling i did fix the problem by forcing an unlock on deconstruction) people running daemons can upgrade tonight and UI users should be able to update by wednesday.
Not technical explaination:
In short, sending messages would sometimes cause the wallets to crash and it was a big problem.
During the week i do work a full time job as a software engineer, so work with commute does take up about 9 hours of my day. During the week days i only can come home and work on this coin for 3 or so hours before i have to do other life stuff and go to bed early enough that i can get up the next day.
Please stop asking if the exchange is closing down or stealing coins, they were offline by instruction until i could figure out how to solve this error.
I understand it is taking longer to get some stuff done than people want but i only have so much time during the day and these changes that are separating out ECC from the other coins will be worth it in the long run. Obviously there is more work to be done. Next we will be putting out GUIs for users and then i will finally have a chance to update the website.
Thank you those of you who have come together on slack and helped to rebuild the front end for the website and those of you who are helping to contribute to the electron UI github that will be used for the coin for the future.
We know there are issues that need to be solved. There are 6 or 7 people now working on code to fix all of them.
-Griffith
