I salute SYS for returning the 250BTC portion of the escrow so that Moolah has the entire escrow. As far as your latest update:
In other words, the core team did not have any hard-core C++ devs?
Given all the wildcards, I think MOOLAH should withold the escrow until
1) an independent review led by a team of completely independent developers, perhaps selected by Moolah, independently review the code and certify there are no hidden bugs that will come back to bite people later
2) the leadership team is reorganised with developers/project managers that are vetted (Proof Of *Real* Developer) who have a clean history that affirms they'd never release a broken Litecoin-clone code/network like this.
I think a revised roadmap needs to be prepared and put in the hands of a team the market will have confidence in. Right now, the only reason the market price is hovering above the ICO price is because Moolah has affirmed that it will not release the escrow as long as the wallet remains broken. I'd argue that it should also not be released until there's confidence there's a team in place that wont release more broken code and empty promises in the future. That's when the price will soar toward where it should've been at this point. Until then, we're looking at stagnation and uncertainty about code quality, even if you manage to band aid this depressing launch.
- 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.
In other words, the core team did not have any hard-core C++ devs?
- 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)
- 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)
Given all the wildcards, I think MOOLAH should withold the escrow until
1) an independent review led by a team of completely independent developers, perhaps selected by Moolah, independently review the code and certify there are no hidden bugs that will come back to bite people later
2) the leadership team is reorganised with developers/project managers that are vetted (Proof Of *Real* Developer) who have a clean history that affirms they'd never release a broken Litecoin-clone code/network like this.
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.
Of course, we're addressing the initial higher-priority issues first.
I think a revised roadmap needs to be prepared and put in the hands of a team the market will have confidence in. Right now, the only reason the market price is hovering above the ICO price is because Moolah has affirmed that it will not release the escrow as long as the wallet remains broken. I'd argue that it should also not be released until there's confidence there's a team in place that wont release more broken code and empty promises in the future. That's when the price will soar toward where it should've been at this point. Until then, we're looking at stagnation and uncertainty about code quality, even if you manage to band aid this depressing launch.