Furthermore there is a continuous, heavy load on the testnet every day to check the reliability of the blockchain network. I can only repeat myself: Sasha's strategy is to release the main net only after having achieved an error-free stable testnet for a few weeks. And this is a very responsible approach, IMHO.
Yes, you are wrong. The main programmer responsible for the Waves back-end has made a lot of changes since the launch of the testnet: middle of August: https://github.com/wavesplatform/Waves/commits/master
You are right on the devnet. They have an own developer network where most of the work is being done. If a module is ready for testing they upload it to github.
You are right on the devnet. They have an own developer network where most of the work is being done. If a module is ready for testing they upload it to github.
That's exactly where I looked. So please prove me wrong and link at least one major fix or feature addition since 18 August which is not a version number change, Scorex merge or some minor build script or config edit. I want to see that "lots of changes".
All CPU, stability and blockchain size improvements mentioned above seem to be caused by this:
https://github.com/wavesplatform/Waves/commit/3cad6e3c244cdfe5b2efc3e20a60291f049d8323
This is not even a fix but a configuration for low-end hardware. This, together with restricting memory usage made the node more stable on cheap VPS most testers use.
And no, I didnt mean private network. I meant private Github branch.
FUD accusations are irrelevant. This thread needs some technical discussion
Also, I'm giving everyone concerned an easy opportunity to hype the project some more by proving me wrong 
