I don't know what this project has done, but I can tell you how I would build it, and why this approach would be better than the approach used by our current sy

I don't know what this project has done, but I can tell you how I would build it, and why this approach would be better than the approach used by our current system of certificate authorities. (1) In this model, the user decides which authorities to trust. With certificate authorities, the user must trust ALL of the "standard" authorities, or else wind up unable to verify sites that happen to purchase their cert from an untrusted authority. With notary servers, the end user can choose to trust whichever notaries they want (and not trust others) and can still validate certificates on all sites throughout the web. (2) It is possible to verify with more than one notary, but with certificate authorities each site is only (normally) signed by one CA. This means you could, for example, trust 5 different notaries and an attacker would need to suborn all 5, whereas with certificate authorities an attacker would need to suborn only 1. Since most users will not adjust the default settings, I would hope that browsers would ship configured to verify against a set of about 12 trusted notaries, approving any certificate verified by at least 9 of them. The only remaining piece needed is an onion-wrapped P2P protocol for forwarding the requests so that you don't leak your browsing history to all of the notaries.