Difference between revisions of "Trust Registry Identifier"
From MgmtWiki
(→Problems) |
|||
| Line 1: | Line 1: | ||
==Full Name== | ==Full Name== | ||
| − | [[Trust Registry Identifier]] is a | + | [[Trust Registry Identifier]] is a [[Decentralized Identifier]] that implements a Sidetree protocol build on top of Bitcoin.procols of the DIF. |
==Context== | ==Context== | ||
| Line 6: | Line 6: | ||
==Problems== | ==Problems== | ||
* Existing Identifier Providers, like Google and Yahoo, extract information from users of their services for their own purposed which compromise the user's privacy. | * Existing Identifier Providers, like Google and Yahoo, extract information from users of their services for their own purposed which compromise the user's privacy. | ||
| − | * Most other | + | * Most other [[Decentralized Identifier]]s have abandoned well-testing and certified security protocols in favor of esoteric, new and untested protocols that are not supported by the hardware protected keystores that are necessary to achieve high level of authentication assurance. |
==Solution== | ==Solution== | ||
Revision as of 13:30, 22 August 2020
Contents
Full Name
Trust Registry Identifier is a Decentralized Identifier that implements a Sidetree protocol build on top of Bitcoin.procols of the DIF.
Context
Problems
- Existing Identifier Providers, like Google and Yahoo, extract information from users of their services for their own purposed which compromise the user's privacy.
- Most other Decentralized Identifiers have abandoned well-testing and certified security protocols in favor of esoteric, new and untested protocols that are not supported by the hardware protected keystores that are necessary to achieve high level of authentication assurance.
Solution
Trust Registry Identifier is based on the Sidetree https://github.com/decentralized-identity/sidetree, which this project uses internally with the code required to run the protocol on Bitcoin, as the ION network.
