We're in a pre alpha state. Let's implement it first, get a whitepaper out and then talk about review and audits.
"External" audits of unfinished stuff make little to no sense.
You don't need even one line of code to review the idea behind POI.
In fact, reviews and designs are done before coding starts so that if there are problems, they can be fixed
In this particular case imho you have to code it because there is no other way to find the right balance between all the factors.
Say devs had the time to write a whitepaper and there was no code written yet.
How would they describe the balance of the factors that POI takes into account if they have no idea how they will behave under "real life" conditions?
Of course makoto is way more qualified to answer this so makoto (or any other core dev for that matter) please correct me if I'm wrong here
