There will be 1000 write-ups criticizing the technology, approach, or distribution of @worldnetwork. In fact, it's pretty easy to do this for any person with crypto/security background. + You'll get a lot of media attention. But I think it's important to take a step back, imagine the potential of what if this actually works, understand the technical limitations, and see how we can solve one problem at a time. The project is still in the early phases of development. After browsing the docs for a few hours (they're very good for an early-stage project), here're a few low hanging recommendations to the team. * Make the audits public. Seems there were two audits done by Nethermind & Least Authority. The audits are not public yet. whitepaper.worldcoin.org/oth… * Run public security contests and bug bounties. e.g., using @immunefi and @code4rena. * Clearly state the assumptions. In any crypto/security system, it's important to understand the roots of trust. The assumptions should be of the form: "We trust that (a) the Orb is not compromised, (b) the PKI around the Orb is secure, (c) the ZK proof by Groth16 is secure, (d) the user's device storing the key is secure, etc." * State the assumptions around the Orb. e.g., The Orb generates an iris code of length X such that for all scans of all Orbs of the same person, the Hamming distance between any two pairs of scans is < Y, and for all pairs of iris scans that belong to different people, the Hamming distance is greater than Z. * It wasn't clear to me where the iris data is stored and not stored. Make that very explicit. Which devices / services have access to the full iris data vs its fingerprint? Is the fingerprint lossy or cryptographically secure? [i.e., no info about the pre-image, the iris sequence itself, can be extracted from the public info (statistically) vs its protected using crypto and holds private under some crypto assumptions]. * Anticipating a backlash of academic papers breaking the protocol, pro-actively engage with them. e.g., create research grants for folks to write a paper breaking some part of the protocol && suggesting a way to fix and improve it. * Start an open-source research / development program for alternatives to the Orb hardware implementation. cc @mnovendstern, @sama , @chriswaclawek