Difference between revisions of "Sidetree"

From MgmtWiki
Jump to: navigation, search
(Context)
(Solutions)
 
(16 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
* As of 2020-11-15 the IPFS implementations were at Alpha release level and not recommended for production use.
 
* As of 2020-11-15 the IPFS implementations were at Alpha release level and not recommended for production use.
 
* As of 2020-11-15 the Sidetree spec required two versions of the DID and stipulated that any RP relying on that DID would have to accept either version interchangeably.
 
* As of 2020-11-15 the Sidetree spec required two versions of the DID and stipulated that any RP relying on that DID would have to accept either version interchangeably.
*
+
* The Sidetree folk introduced the idea of "equivalent" IDs (see above problem) into the DID Core spec just before it went to ba a candidate (2021-04-01) This makes extra work for the RP with no benefit to the RP.
 +
 
 +
==Solutions==
 +
What is Sidetree?
 +
 
 +
Self-issued identifiers, for example, Decentralized identifiers (DIDs) enable a person or entity to securely authenticate, demonstrate intent and exchange data, where the identifier is being managed independently of those systems and organizations. DID events such as creation, updates, and revocations can be organized and propagated by DID networks. Sidetree describes a protocol for building such networks without being coupled to a particular underlying ledger or event record system. The protocol and data model described by Sidetree enables a decentralized identifier model that allows its user to ultimately be in control of the identifier and its history, without introducing additional trust requirements beyond the underlying event record system. Sidetree-based networks can be implemented on top of a wide variety of event record and propagation methodologies(public [[Blockchain]]s, [[Federation]] and witness protocols, or [[Permissioned Blockchain]]s) and can be as open as the underlying mechanism. Sidetree enables a scalable protocol, that can be overlaid on a variety of event record and propagation systems, for creating vibrant digital ecosystems based on decentralized identifiers
 +
 
 +
from Troy Ronda 2021-04-02
 +
* Microsoft introduced did:ion with sidetone and BitCoin support after four years of work. <ref>Pamela Dingle, ''ION – We Have Liftoff!'', Microsoft (2021-03-25) https://techcommunity.microsoft.com/t5/identity-standards-blog/ion-we-have-liftoff/ba-p/1441555</ref>
 +
* [https://securekey.com SecureKey] Implementations
 +
#https://github.com/trustbloc/sidetree-core-go: Ledger-agnostic Go implementation of Sidetree
 +
# withOrb (https://github.com/trustbloc/orb) and Hyperledger Fabric
 +
# [https://github.com/trustbloc/sidetree-fabric variations] built on top.
  
 
==References==
 
==References==

Latest revision as of 10:54, 10 April 2021

Full Title

Sidetree is a spec for a collection of Distributed ID methods that uses IPFS to guarantee uniqueness of a DID.

Context

Microsoft started to build Sidetree as the backing for the Ion DID method to improve responsiveness to reads and writes of ID data.

  • Sidetree basically intercepts any request for ID reads or writes and tries to cache them to avoid a delay caused by a read or write to the Bitcoin Blockchain.

Problems

  • As of 2020-11-15 the Sidetree spec did not guarantee that an old key used for signing or encryptions would be available from any of their methods.
  • As of 2020-11-15 the IPFS implementations were at Alpha release level and not recommended for production use.
  • As of 2020-11-15 the Sidetree spec required two versions of the DID and stipulated that any RP relying on that DID would have to accept either version interchangeably.
  • The Sidetree folk introduced the idea of "equivalent" IDs (see above problem) into the DID Core spec just before it went to ba a candidate (2021-04-01) This makes extra work for the RP with no benefit to the RP.

Solutions

What is Sidetree?

Self-issued identifiers, for example, Decentralized identifiers (DIDs) enable a person or entity to securely authenticate, demonstrate intent and exchange data, where the identifier is being managed independently of those systems and organizations. DID events such as creation, updates, and revocations can be organized and propagated by DID networks. Sidetree describes a protocol for building such networks without being coupled to a particular underlying ledger or event record system. The protocol and data model described by Sidetree enables a decentralized identifier model that allows its user to ultimately be in control of the identifier and its history, without introducing additional trust requirements beyond the underlying event record system. Sidetree-based networks can be implemented on top of a wide variety of event record and propagation methodologies(public Blockchains, Federation and witness protocols, or Permissioned Blockchains) and can be as open as the underlying mechanism. Sidetree enables a scalable protocol, that can be overlaid on a variety of event record and propagation systems, for creating vibrant digital ecosystems based on decentralized identifiers

from Troy Ronda 2021-04-02

  • Microsoft introduced did:ion with sidetone and BitCoin support after four years of work. [1]
  • SecureKey Implementations
  1. https://github.com/trustbloc/sidetree-core-go: Ledger-agnostic Go implementation of Sidetree
  2. withOrb (https://github.com/trustbloc/orb) and Hyperledger Fabric
  3. variations built on top.

References

  1. Pamela Dingle, ION – We Have Liftoff!, Microsoft (2021-03-25) https://techcommunity.microsoft.com/t5/identity-standards-blog/ion-we-have-liftoff/ba-p/1441555