I think since we've now got a self funding DAC and it looks like the SEC is on a mission to fuck over every blockchain company, it might be in Invictus' best interests to quickly get burn through all AGS funds after the "marketing push". I'd say that posting a $10k bounty on an iOS/Android wallet would get the job done fast.
I agree that Invictus should pay their employees/grants through AGS funds first before the developers start taking any pay from diluting delegates.
I don't think developing a mobile client is as simple as putting up a bounty like you are claiming. The I3 dev team is the one best suited to quickly modify the BitShares toolkit and the BTS blockchain to be suitable for lightweight client validation. It is a tricky problem that I think they are best suited to solve rather than relying on some new devs that get paid by bounty. The team only needs to build a command line lightweight client that can securely
send and receive funds with the minimum amount of trust (meaning economic incentives need to be aligned to reduce the risk of bad actors, IMHO this requires certain hard fork changes to the blockchain) and without needing to download and validate the entire blockchain. Once that proof-of-concept is done, then I think we could use bounties to get other devs to port over that open-source implementation to the various platforms (browser, Android, iOS) with appropriate GUIs.
Yes I understand validation technology is necessary for a lightweight mobile client. I feel as though security can wait until adoption is higher though. I don't anticipate any major hacks until user adoption is high. Hackers only go after the big pies.
I disagree that security should wait. I don't think the effort required for cold storage with offline transaction signing is very high, but it provides an immense amount of security of funds. Multisig is a little bit trickier but I still think at least building the support in the client provides far more benefit than the costs in development. I guess I would be willing to accept a swap in priorities between step 3 and step 5 if the amount of effort for implementing usable multisig is really a lot higher than I think. But I certainly think that the multisig implementation and getting companies on-board to support it can be done in parallel to the Android/iOS client development efforts, and they are both way
more important than Key Graph, a full voting booth implementation, and Turing complete scripts.