Quote from: yoyotu on August 18, 2014, 07:42:22 AM

Quote from: sushipooo on August 18, 2014, 07:35:37 AM

Quote from: yoyotu on August 18, 2014, 07:26:52 AM

Quote from: danosphere on August 18, 2014, 07:17:04 AM

"Defensive whining?". Please. We've already apologized many, many, many times. Already detailed steps being taken to make sure similar problems don't happen later but let me expand on it- with the current team we have, and no funding, and no plans to dump (to get funding), we are planning on:
- get help from all the smart C++ devs we can, we already have several helping us thanks to the potential of this project. They will be compensated once we have funds to compensate them with.
- addressing the issues with wallet rescan crash which is affecting some users
- increasing the amount of DNSseeds we have because the network gets hammered more than we expected when resyncs are flying around
- making sure the merged mining works as something to do with tx messages appears to be preventing that
- addressing anything that might come up with using services- no issues have been reported yet but we already know we need some form of getServiceCost() command prior to using a service; issue has been logged in github.
- We need to get a better process with pool operators to avoid these forks when updates need to roll out - as today
- We plan on upgrading the codebase to bitcoin 0.9.2 (this is not easy) as it has many improvements, better packaging and testing tools
- Complete the automated test suite which is a challenge on a p2p network where assertions are dependent on confirmations (that is what cakenet is for)

That is the shortlist of things we must address ASAP. Beyond that, we have a roadmap of features and will have a better build/release process for these moving forward:

Of course, we're addressing the initial higher-priority issues first.

The features is too faraway.Just do the basic quick,as wallet SYNC,wallet UI,blockchain...
Otherwise you will lose your supporter,Even if you do better later,Because they had gone away.

wallet offline ... investigating blockchain issues. @BittrexExchange

refresh your browser dude, it's been online at bittrex for at least a few hours now.

refresh your browser bro, The wallet been disabled at bittrex now.

lol I see it has