I'm very interested in this. My only concern is that Lisk (and Rise) codebase in its current state is quite vulnerable and both projects have yet to allow delegates to forge without causing forks. I believe I just read that they will be rewriting their code from scratch which is quite an undertaking and I think some are skeptical. With Ark being a Lisk code base, are you prepared to rewrite the code to become more stable?
Thanks. I think 120% bonus for Lisk investors is huge. I like it.
Please keep in mind that I'm not a developer, but as long as I'm around I take a stab at this too-
While Rise wants a rewrite Shift and Asch managed to make the Lisk codebase work for forging or at least found some temporary solutions. fixcrypt, our main developer also has several ideas, some he came up with while he was working for Lisk, and I know he also had a talk with asch main dev, and probably others about various issues and possible solutions not just about the forking problem but others as well.
I'm not sure how much of these ideas will be implemented into the initial testnet code, as fix had been busy with various other stuff, but he has some well defined ideas and development plans. I think you all will hear about them later.
I think 51 delegates should also initially help with the forking issue until better ways are found, but please don't quote me on that one.

Thanks for the clarification. I'll be watching. Probably buy some on day 1. Good luck guys!