A system that solves the problem of user verification while still respecting their privacy
Included in this archive are planning documents for the BlockAuth service
##Organiztional Overviews BlockAuth Whitepaper The Whitepaper gives a general description of why BlockAuth is needed, basic overview of how the technology will function, and the benefits the Identity Registrar services it certifies can provide.
Founding Ideas and Goals This document details what principals are important to us, how we intend to benefit the entire community, and the direction that we plan to take the organization.
Industry Opportunities BlockAuth certified Identity Registrars have the power to change how a lot of businesses operate. This is a list of some of those businesses and how they could be improved by using the services that the Registrars can provide.
Developer Incentives This document describes our strategy of getting BlockAuth compatible software modules developed for as many platforms as possible by engaging developers and offering bounties.
Franchise Fees and Operating Costs This document describes some of the requirements to be a Identity Registrar, including operational fees, membership fees, and obligations.
Open Source Projects to Contribute to By contributing to existing open source projects, we help the community and ourselves. It's both the smart and the right thing to do.
##Operational Overviews Ensuring User Privacy Rights This document describes the user experience when they sign up at a new site and how they can see what information is being requested and how they have the power to deny it or to provide "proxy" information.
Security Practices This document describes some of the basic security principals that BlockAuth and all identity registrars must follow, as well as the power users have over the tradeoff between security and convienence.
Token Plans and Pricing The use of the BlockAuth token is integral in the Verification Marketplace feature. This describes what the tokens are, what they're used for, and how much they cost during the crowdsale. It also describes the intended use of the remaining tokens.
User Data To Verify This document is more of a list of information we plan to let users assert that we intend to verify. This list will change often as more and more requests are received
user Verification Procedures Users may assert information about themselves, but it's the job of the Verification Partner or Identity Registrar to verify that information. This document is the first attempt at writing the requirements for those verifications
Verification Partners Describes the roles of Verification Partners. Identity Registrars can also be Verification Partners if they let other Identity Registrars submit information to be verified on behalf of another Identity Registrar.