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

Release 0.1.4
Compare
Choose a tag to compare
@bstasyszyn bstasyszyn released this 27 Aug 15:41
v0.1.4
67510e9
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.

fabric-peer-ext Release Notes - Aug 27, 2020

What's new in fabric-peer-ext v0.1.4

This release is based on the Fabric 2.2 codebase. Along with various bug fixes, the following features were added:

Application-specific Gossip data #401

A Gossip handler registry that allows applications to register a handler for an application-specific message type. When a Gossip message of a certain app-specific type is received then the registered handler is invoked and the handler may respond to the request.

Auth filter registry #405

An Auth Filter registry that allows applications to register an Auth filter (in-process) which is managed by the Resource Manager (similar to in-process chaincode).

Enhancements to the Transaction Service

  • Commit type option was added to EndorseAndCommit #408
  • Peer filter option was added to EndorseAndCommit #409
  • Async option was added to EndorseAndCommit #415
  • New CommitEndorsements function which allows a client to commit a set of endorsements #407
  • New VerifyProposalSignature function which verifies the signature on a signed proposal #423
  • New ValidateProposalResponses function which validates a set of proposal responses #427

Support for collection hash r/w sets in Block Publisher #431

Clients can now receive private collection hash read and write block events.

Support for private data reads and writes in Block Publisher #455

Clients can now receive private collection read and write block events.

Support for Fabric 2 chaincode lifecycle #451

In-process chaincode can be approved and committed using Fabric 2 chaincode lifecycle, as well as the legacy lifecycle.

Access control for ledger config #497

Ledger configuration operations are now controlled using channel-specific ACL entries.

State database provider resource #505

A State Database Provider resource is available for applications wishing to read from the state database directly without having the read show up on the ledger.

Other changes

  • The full set of Fabric integration and unit tests have been re-enabled (some tests were disabled in the initial update to Fabric 2.0)
  • Various performance improvements such as caching blockchain info in the Couch blocks database
Assets 2
Loading