Quote from: thandie on April 25, 2016, 09:29:51 AM

Quote from: Fullhd on April 25, 2016, 09:11:41 AM

Handelt es sich hierbei nicht um einen Crypti Klon? Inwiefern hätte es technische Probleme geben können? Auf SQLite alleine kann man die Argumentation schlecht stützen meiner Meinung nach.

Max und Oliver sind erfahrene Leute.

Wäre es nur noch ein reiner Crypti Klone, wäre Lisk schon längst gestartet - oder?

https://blog.lisk.io/pre-launch-development-plan-2691f91fe24e#.if3thgvg5

https://blog.lisk.io/official-lisk-release-2efac0ea3b3#.r8iv8jfjl

Quote

Soon after we announced the scheduled release date and pre-launch development plan, someone stress tested our network and it collapsed. A few hours later Oliver released a fix which sets the transaction maximum per block to 10. It fixed the stress test related problems and made the network stable again, however it became crystal clear that we need to optimise Lisk before launch. The code was not durable enough yet to withstand the enormous popularity of Lisk. Therefore, Oliver completely switched the Lisk blockchain database layer from SQLite to PostgreSQL. Additionally, he implemented many speed optimisations and restructured big parts of the block synchronisation code.

The results are fantastic; the client is much faster and more responsive. All concurrency problem we had, when many users were using the same node (e.g. login.lisk.io) are resolved. Additionally, the network backbone is far more robust and scalable. The update will be available next week in order to properly test it, a testnet reset is necessary.

Unfortunately, the database switch pushed us back for 9 days and further tests of the changes will require a total of one week. On GitHub we also received more issues in the past weeks which need to be fixed before launch.

Therefore, coming back to the release date. In order to have a successful launch Lisk needs to simply work. We decided for quite a generous release date. Which gives us more than enough time to properly test the new release, finish the pre-launch development plan, and work on the GitHub issues.

Klar das es kein 1:1 Klon ist, der Großteil der Technik ist identisch.