Decentralized Authentication. Chew on that for a bit. But why is it needed? Here’s what Bitpay said about this:
Today, BitPay is excited to announce our proposal for a new passwordless authentication protocol, based on the same cryptography used in the Bitcoin protocol. By eliminating server-side storage of passwords, we can drastically reduce the impact of a compromised server.We’ve given long and careful thought to how best to protect the security of our customers’ data, of especially critical importance when dealing with financial information. Existing authentication schemes that you might be familiar with include username and password, client-side SSL certificates, or even shared secrets — in the end of our review, we found each of these to be lacking in various ways, so we made the decision to build BitAuth.
But how? How is a decentralized authentication system possible? Inspired by the same elliptic-curve cryptography as Bitcoin, Bitpay proposes to use SIN, or system identification number. Originally proposed by Jeff Garzik, Bitcoin Core Developer, SIN is intended to be a fully decentralized, anonymous, secure identity. SIN also has the following features:
On top of these, there is the chance for two SIN’s, type-1 and type-2.
Type-1, also known as a persistent SIN, is more of a scarce SIN intentionally costing a lot to deter spam and validation, just like Bitcoins.
Type -2, also known as ephemeral SIN, acts more like Bitcoin addresses, which is where the disposable feature comes from.
Note this is all a proposal, but here is how Bitpay would do it:
How BitAuth Works
This system would provide numerous benefits listed below:
As of now, Bitpay has a Github (see below) where people can test out the new authentication system. It’s only fitting that if we are dealing with decentralized currency, the security that handles it is decentralized as well.
Photo Source: Bing Images and Microsoft Paint (editing)
1 Hova Villas Brighton & Hove
BN3 3DH United Kingdom
All rights reserved by Bitcoinist Ltd. | 2016.