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

Release 0.1.3
Compare
Choose a tag to compare
@bstasyszyn bstasyszyn released this 06 May 18:23
v0.1.3
14f5b4b
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 - May 6, 2020

What's new in sidetree-fabric v0.1.3

Configurable store for Sidetree operations #171

The operation store for each namespace is configurable in the Sidetree consortium configuration.

Configurable DCAS store #190

The DCAS store for each namespace is configurable in the Sidetree consortium configuration.

CAS REST endpoint #169

REST endpoint to upload and retrieve content (https://trustbloc.github.io/sidetree-fabric/docs/api/#/Content%20Addressed%20Storage)

Blockchain REST endpoints

REST endpoints to query for Sidetree transactions and Fabric blocks on the blockchain (https://trustbloc.github.io/sidetree-fabric/docs/api/#/Blockchain)

File handler REST endpoints #145

Framework to support multiple HTTP endpoints that serve up files (e.g. schemas, .well-known, etc.) which are stored in DCAS. A file is uploaded to DCAS through one of the configured endpoints and a DCAS ID is returned. The ID is then mapped to a resource name and stored in a Sidetree 'index' document. The ID of the index document is referenced in the ledger configuration for the given HTTP path so that a client may retrieve the file (which is stored in DCAS) using a friendly name.

Bearer token authorization #152

Authorization tokens are configured at the peer config (core.yaml) and then referenced in the REST handler configuration. If tokens are defined for a REST endpoint, then an authorization handler is first invoked in order to validate that a valid token was passed in the request header. If the token is valid then the request is allowed to proceed, otherwise an HTTP 401 (UNAUTHORIZED) is returned.

Persistent queue for batch operations #32

Operations are written to a LevelDB-backed queue so that queued operations aren't lost on peer restart.

Fabric 'cluster' mode for BDD tests #173

The BDD test now runs using Fabric clustered peers, i.e.the peers in one org share a database.

Assets 2
Loading