Skip to content
This repository has been archived by the owner on Mar 5, 2022. It is now read-only.

Release 0.1.1
Compare
Choose a tag to compare
@bstasyszyn bstasyszyn released this 29 Jan 23:20
v0.1.1
ed938ce
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

sidetree-fabric Release Notes - Jan 29, 2020

What's new in sidetree-fabric v0.1.1

Convert Document and TXN chaincode to in-process user chaincode #99

The Document and SidetreeTXN chaincodes now run in the peer's process. They no longer need to be installed but they do need to be instantiated.

Implement REST API's in the peer process #66

The external, Sidetree Docker container has been removed and the REST endpoints are now inside of the peer(s). Each peer exposes a REST endpoint according to its role. If the peer has the 'sidetree-resolver' role then the document resolver REST endpoint is exposed. If the peer has the 'sidetree-batch-writer' role then the document update endpoint is exposed.

Read Sidetree configuration from the ledger #65

Sidetree configuration is now stored on the ledger (which is channel-specific). Multiple Sidetree namespaces may be defined on each channel and a single REST server serves all of the namespaces (on a single port). For example, you can define the following namespace/path combinations:

  • Channel: mychannel, Namespace: did:sidtree, Base path: /document
  • Channel: mychannel, Namespace: did:bloc:trustbloc.dev, Base path: /trustbloc.dev
  • Channel: yourchannel, Namespace: did:bloc:yourdomain.com, Base path: /yourdomain.com

Dynamic updates are also supported. A new namespace may be added/removed dynamically, or the configuration for an existing namespace may be updated (e.g. a new protocol version added or the base path modified).

Assets 2
Loading