Looking into issues now. Will update when i have all the info. Chain is back on track form what i can see
That does not sound good. Rather than making some fancy client skins, I would rather see the devs focus on client security and network monitoring tools first.
I understand your concern 100%. In fact for the skinnable wallet we are looking to hire outside. Network functionality and security are our #1 goal and I have been working on nothing else until any issues are resolved.
We can assure you chain is back on track and moving ahead smoothly. If you are having Issues syncing your client Re downloading the blockchain should resolve the issue.
This does not appear to be an attack of any sort but may have been caused or exaggerated by 90% of the network hashrate disappearing when verns pool went down. We had a slight dip in coin generation due to this today but all is well and back on track.
It will require a little more investigation as I was not available during the actual event. We are looking into the cause and will get to the bottom of it and hopefully prevent any issues from here on out. The next update is still on track for a release date of 7/30/2013
For now it is recommended that users spread out their hashrate. If the pool you are mining on is controlling a substantial amount of the network consider one of the many other great pools. This can only lead to a more efficient network and hopefully avoid any issues like this in the future.
I was mining at a different pool at the time. After having some issues with Vern's & Silverwolf on this coin, I wasn't expecting anything much, but I thought I'd give
http://cap.epools.org a try. Wow! What a difference. I was actually getting the correct amount of coin and slightly more. I was truly impressed with this pool. It just worked right.
After you mentioned an issue here, I checked the pool right before going to sleep and everything seemed to be working well, blocks were confirming so I wasn't concerned. The difficulty started going down so I figured miners were jumping to another coin and the number of coins I was mining was going up. When I woke up, I checked the pool stats and half my mining balance was gone. I definitely thought I got scammed by the pool. When I investigated further I realized that a fork did occur and that there were a whole chain of now invalid blocks.
It looks like the fork occurred between blocks 47,738 and 47,743. The pool synched back up with a longer chain between blocks 48,217 and 47,985. That's about 479 blocks on the invalid chain (value about $225 in coins). If we were the shorter chain, shouldn't we have synched back up automatically after a few blocks at most? I checked the Silverwolf pool, and that pool remained on the currently correct chain at the time of the fork.
I tried re-downloading the block chain a couple times. It struggled. Only three piers. It finally downloaded and all my wallet coins are there and confirmed. We need the checkpoint w/client update soon!
The other strange thing I noticed was that because the chain was taking hours to download, I sent a test transaction before I had the entire chain had downloaded. What happened surprised me. Not only did this transaction go through, but it received multiple confirmations. How is this even possible if my client didn't even download the block in which the transaction occurred? Is this something unique to Proof of Stake? I thought the client could only display a confirmed transaction after it downloaded the block that contained that transaction.
Please update once you have more info. about the fork. I've posted what I know. Thanks.
