No lost confidence. Just had to solve pos first.
Has this been solved now wrt coding?
Yes, I released a white paper on DPOS last week and have implemented a large part of it and will be testing it in the days ahead. Resolving the security model in a way that one can thoroughly understand and prove is secure was a major challenge. You can follow discussions on this forum where about a half dozen variations / iterations where vetted and found wanting... Let me list the evolution:
1) Mining with Momentum... tossed due to centralization and non profitability
2) Transactions as Proof of Stake white paper (Nov 28th, 2013) adjusted mining difficulty by stake. Suffered from weakness on deciding who should produce the next block.
3) Ripple Consensus + TaPOS was the concept in January at the Miami event through Feb, but after attempted implementation we realized it had several deal breakers:
a) the unique node list was an invite-only group and a point of trust
b) the UNL was not compensated in any way
c) the bandwidth requirements / scalability were an issue
4) Fall back on a simple mining + TaPOS and various variations on equations for option 2. All of these variations suffered from many potential attacks and would require many confirmations. It became too complex to analyze. (Feb through March)
5) Single trustee which could be fired... the process was too manual but otherwise sound.
6) Delegated POS this solution has been reviewed, found to be decentralized, fast, and secure without ambiguity. We have finally resolved the issue.
In that time we also identified problems and found solutions to several market manipulation attacks. These need to be implemented, but then we should be good to go.
As you can see R&D is not predictable when you are at the bleeding edge of innovation and solving problems as they are discovered.