Technically, if multiparty rules are set before your die then after you die then they still apply, however you might find that certificates associated with a particular ID will get revoked and thus the ID won’t be really useful after you die. But it all depends on the use case.

Thanks for the link - there do seem to be some similarities with where we're heading. The fact that there are several new initiatives popping up in this field suggests to us that there is real potential for creating something useful here (not just our own crazy idea), and the feedback we're getting here really helps us focus on what's important from a user point of view.

Hi warningsigns, thank you for your feedback.

You are 100% right, and we know we will have to prove our trustability. We will open our code and make it auditable. And we are designing our system with the philosophy that any user data is a "liability" for us, and we want to reduce this liability. All the data is encrypted client side with your private key, all the identity management system can only be controlled by your private key, and we are looking into decentralized storage systems as a mean of eliminating any form of central point of failure.

buwaytress,

We use the Ethereum blockchain for the low level identity management features of our system. It takes care of things like attribute management, certification issuance and management and identity profile control. The blockchain is useful it provides an unequivocal source of truth about the state of someone's identity.

One other problem with regular cryptographic authentication is that people lose their key which essentially amounts to you losing your account. But if your "Identity profile" is a contract address instead of a public key or a wallet address, you can define rules (think multi party enforced rule) to change who controls an "identity profile contract" and use this as a secure yet simple recovery mechanism.

Hi mobnepal, thank you very much for the feedback and for signing up as a beta tester.

Our work on the mobile application is almost complete, then we'll be working on the browser extension. The browser identifies the required information by the website. It sends a request to the phone for the information, the phone sends back the requested encrypted information to browser which is decrypted by the browser.

Hi Patatas, thanks for your feedback - looking forward to hearing what you think of the webpage.

It’s still early days for us, so our aim was to allow people to make up their up own mind about what they find important about this kind of solution, rather than us speaking too much beforehand of what we assume is important. But you are right that we could indeed have explained a bit more up front, thanks for making us aware of that.

Hi buwaytress, thank you very much for your feedback.

In our first iteration, we want to increase usability by reducing the perceived complexity of managing multiple credentials. We do this by hiding all form fields and replacing them by a one step login/registration process. This first iteration is really about refining the user experience of a would-be identity manager.

Then, we want to get rid of passwords altogether, because let's be honest: passwords are not the best solution to signing in online anymore. We believe that public/private key cryptography authentication like what's used in Bitcoin really is where the innovation lies and that it must be put to good use in this area - and that's what we aim to do.

Hi LeGaulois, thanks for the feedback. We love the suggestion, we’ll look into it!

Hi MoonIsBlue, thank you for the feedback and the name suggestion, we'll take it all into consideration!

Hi TryNinja, thanks for the comment and questions.

The autofill feature provided by our browser extension means that you can use Lynx for the sites you listed from day one.

Our step after that would be to get a lot of services directly involved. One way to achieve this is to make the service dead simple to integrate for the devs. The aim is to make the service plug and play through things like wordpress plugins and javascript widgets.

Even if a service decides not to take direct advantage of our ID verification feature, you’ll still be able to use the autofill function to connect to those sites.

Hi AT101ET, thanks for the feedback!

This is our first version that is akin to a form filler/password manager, but our mission is to create an ethereum-based self sovereign identity hence the decentralized property.

This system uses principles related to 2FA (something you know (passcode)/something you are (touch id) and something you own (phone)) then signs a challenge issued by the website to authenticate yourself.
Your data is encrypted on your phone and protected by the phone’s keystore/keychain (passcode) or touchid.

For the name, do you have any suggestions?

We’ve been working for a few months now on a tool to change the way people sign in online and keep their personal information secure.

This is our first step towards a decentralized identity solution. We want to create something useful, so we’re keen to get some initial feedback: https://lynxid.tech

What do you think - does it look like we are heading down the right path?