- From: David Nicol <davidnicol@gmail.com>
- Date: Fri, 10 Jun 2016 15:46:14 -0500
- To: Roger Bass <roger@traxiant.com>
Received on Friday, 10 June 2016 20:46:16 UTC
My current thoughts on identity interoperability are as follows: An identity statement, including a public key, is composed into a data block in a human and machine readable file format, details to be determined. This data block is stored and replicated on IPFS or equivalent. The hash of the data block is then used as needed as an immutable identity handle. Problems such as private key loss/theft/cracking and the possibility of identity details (name, address) changing remain open. Detail change can be dealt with through indirection to mutable data blocks following the BEP44 semantics for limiting updates to distributed mutable data to the holder of a private key, which reduces to the familiar problem of protecting private keys. -- "Why would you want to be the last man alive on a sinking ship?" -- Elon Musk
Received on Friday, 10 June 2016 20:46:16 UTC