|
| 1 | +v1.3.0 Release Notes - October 10, 2018 |
| 2 | +--------------------------------------- |
| 3 | + |
| 4 | +What's New in Hyperledger Fabric v1.3 |
| 5 | +------------------------------------- |
| 6 | + |
| 7 | +The following features/epics are included in this release: |
| 8 | + |
| 9 | +FAB-10120 - Identity Mixer for anonymous transactions |
| 10 | +Keep client identities anonymous and unlinkable through the use of |
| 11 | +zero-knowledge proofs. |
| 12 | + |
| 13 | +FAB-8812 - State-based endorsement |
| 14 | +Allows the default chaincode-level endorsement policy to be overridden by a |
| 15 | +per-key endorsement policy. |
| 16 | + |
| 17 | +FAB-2809 - Chaincode pagination of query results |
| 18 | +Clients can now page through result sets from chaincode queries, making it |
| 19 | +feasible to support large result sets with high performance. |
| 20 | + |
| 21 | +FAB-8779 - Java chaincode support |
| 22 | +As an addition to the current Fabric support for chaincode written in Go and |
| 23 | +Node.js, Java is now supported. |
| 24 | + |
| 25 | + |
| 26 | +Changes, Known Issues, and Workarounds |
| 27 | +-------------------------------------- |
| 28 | + |
| 29 | +FAB-11122 - Removal of event hub |
| 30 | + |
| 31 | +The 'old' event hub has been removed in Hyperledger Fabric v1.3. It is |
| 32 | +replaced by the peer channel-based event service which was introduced in |
| 33 | +Fabric v1.1. |
| 34 | +Applications using the old event hub must switch over to the new |
| 35 | +channel-based event service before upgrading to v1.3 peer or SDKs. |
| 36 | + |
| 37 | + |
| 38 | +FAB-12088 - Java chaincode support on s390 architecture |
| 39 | + |
| 40 | +Java chaincode support is not yet available on s390 architecture. |
| 41 | + |
| 42 | + |
| 43 | +FAB-12134 Same chaincode source receiving fingerprint mismatch error |
| 44 | + |
| 45 | +Chaincode installed in different ways may result in "chaincode fingerprint |
| 46 | +mismatch data mismatch" error upon instantiation. This may happen when |
| 47 | +installing chaincode by using different SDKs. To workaround the problem, |
| 48 | +package the chaincode prior to installation and instantiation, by using |
| 49 | +the "peer chaincode package" command. |
| 50 | + |
| 51 | + |
| 52 | +Known Vulnerabilities |
| 53 | +--------------------- |
| 54 | +FAB-8664 - Peer should detect and react when its org has been removed |
| 55 | +This is a relatively low severity problem, because it requires a significant |
| 56 | +conspiracy of network admins, but it will be addressed in a future release. |
| 57 | + |
| 58 | + |
| 59 | +Resolved Vulnerabilities |
| 60 | +------------------------ |
| 61 | +None. |
| 62 | + |
| 63 | + |
| 64 | +Other improvements and fixes |
| 65 | +---------------------------- |
| 66 | +Updated to Go version 1.10.4 |
| 67 | +Updated baseimage version to 0.4.13 |
| 68 | + |
| 69 | +For the full list of improvements and fixes, refer to the release change log: |
| 70 | +https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v130 |
0 commit comments