Just read the whitepaper. Am a little disappointed, to be honest. It's basically a copy of the Crypti paper, and it's very light on details. If you're going to have an ICO, I want something more in-depth and technical than that. I recognize that I can read your code, as it's on Github, but that's not usually my preferred method for coming to an understanding of a complex system. My time is short these days, and digesting code tends to take much longer than understanding a higher-level description.
I bought into the Ethereum presale because every detail had been clearly exposed in its white and yellow papers. With Lisk, there are too many undisclosed details at present for me to feel very comfortable about its future right now. Maybe if I read the code and compare it to Crypti's... but that's a time-consuming proposition.
This is a great post which could benefit Lisk moving forward. Here we have common concerns about the technical details of Lisk and the technology.
Could you go into more detail on what kind of technical and in-depth details Lisk is lacking? (This is a genuine question, not sarcastic nor criticizing you or defending Lisk.)
As part of the community, I believe the approach from ryepdx should be taken seriously, and any other future technical questions should be addressed and added to the documentation.