User Tools

Site Tools


Expected Hyperledger Fabric v1.1 Content

Dashboard for specific Epics, Stories, and tasks are available in the Hyperledger Fabric Jira Dashboard.

Discussion for Fabric releases happens on the #fabric-release channel in RocketChat.

We have published the v1.1.0-preview release November 1, 2017 and v1.1.0-alpha release January 26, 2018. Documentation is maintained in the master branch of the docs.

See the latest roadmap.

High level overview:

Introduction of the following new features:

v1.1.0-alpha (also includes v1.1.0-preview content)

  • Ability to distinguish types of MSP identities, peer vs client. This information can be utilized for access policies throughout the system. FAB-5664
  • Ability to trigger events on a per channel basis rather than global peer basis. FAB-5695
  • Filtered block event - Register for block transaction events with minimal information such as txid and tx validation indicator. FAB-5481
  • Package CouchDB indexes with chaincode to enable efficient queries of ledger state. FAB-3067
  • Mutual TLS between Fabric nodes, and between clients and nodes. FAB-6715
  • Rolling Upgrade via configured capabilities - Support nodes of mixed versions in Fabric networks. FAB-5556


  • Node JS chaincode - An additional implementation of chaincode that mirrors the current Golang version in functionality. The benefit is that when using the node SDK(although you can still use any SDK of your choosing) you are provided a full stack development model. This also helps the large Javascript developer community base with a familiar coding language. FAB-2331
  • Node JS connection profile - Currently all applications need to capture information of the target fabric environment. This enhancement generates a common exchange doc, with backend topology information. With this doc the application will no longer need to construct the channel, add peers, orderers and get the org admin, simplifying your application development. FAB-5363
  • Provide an encryption library that allows customers to encrypt sensitive data that a chaincode processes and updates. This provides another level of security for highly sensitive data. FAB-830
  • Attribute based access control (ABAC) for chaincode, using attributes included in Fabric CA generated certificates. This provides another means of enforcing access control in chaincode. FAB-5346
  • Chaincode APIs to retrieve transaction submitter information including certificate attributes FAB-6089
  • Performance and scale. FAB-6421
    • Orderer performance improvement FAB-5274
    • Orderer horizontal scaling improvements which allows for more orderers to be added to handle more volume and load. FAB-5258
    • MSP Identity caching FAB-5880
    • Parallel transaction validation FAB-5932
    • CouchDB performance improvement FAB-2725
  • CRL support for Fabric CA - Ability to get a cert revocation list from Fabric CA. FAB-5300
  • Enable fabric-ca-client to create a Certificate Signing Request - If a user wishes to use an external CA for generating and signing the certificates, it would be useful to leverage the fabric-ca-client and BCCSP to generate a certificate signing request for the keys generated by the BCCSP and write the CSR to a file without any interaction with the fabric-ca-server. This would allow the user to then send the CSR file to an external CA. FAB-5389

Experimental Features - *not* to be included in v1.1 release images, but available if you build from source and first set EXPERIMENTAL=true environment variable:

  • Enable (new/incomplete) features to be selectively included/excluded from the build. FAB-6020
  • Private channel data. Ability to keep data on a channel private. This data will never be sent to the ordering service with the transaction. The private data is shared with a subset of peers, governed by policies, via the gossip protocol. For example all channel participants may need to be aware of a trade, but keep the trade price private among the trade participants. FAB-1151
  • Finer grained access control on channel functions rather than organization scoped access. For example specify which identities or group of identities can invoke chaincode, retrieve blocks, retrieve transactions, etc. FAB-3621
  • Java for smart contracts (chaincodes). FAB-1973
projects/fabric/proposedv1_1.txt · Last modified: 2018/02/20 10:54 by David Enyeart