As a programmer i know that one month delay is still pretty good and i'm not even mad. It's really good that they find a hole and can fix it, because it will be terrible to find this after release. What i don't understand is why the hell they want to use SQLlite anyway ? It got terrible performance in higher number of inserts and updates. PostgreSQL will be much better choice.
Crypti was (is) using SQLite, as a fork Lisk is using it also, the code is result of a 2 year development. But it was never really stress tested, with little interest from the community. As the test net was set up for lisk and hundreds of potential delegates started running nodes, sending transactions, testing stuff, it turned out that the current code can't handle the amount of transactions Lisk can expect after launch, not even with the optimalization and bug fixes Oliver made to the original crypti code since the fork.
As a temporary solution the transaction number per block was limited (in 0.1.4) and Lisk could've been released like that, and implement better solution later, but I guess they decided that delaying a few weeks to make the improvements are better than releasing Lisk with such limitations. (not to mention other fixes are also needed)
When you follow delevelopment and testnet events, its really not a mystery, and quite clear what lead to this decision, even when they try to make statements only about facts and not hint, speculate and otherwise fuel the fires of gossip.
This is why these scam accusations and conspiracy theories about playing (expected) bitcoin bubble, planning around Wave ico and other stuff are clear nonsense for anyone who is really following the happenings of lisk. Everyting that happend so far had a natural progression to it, that anyone can see (hundreds of ppl) who are active on the testnet, chat, and Lisk forum.
