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.they claimed to be the successor of ethereum but they never created the code to handle the amount of transactions a successor to eth would. did they not believe in their coin. amazing imagine if people knew this before this would be a whole different story. i predict more errors after launch code is unfinished and done quickly release it next year check it thoroughly