| copyright |
|
||
|---|---|---|---|
| lastupdated | 2021-08-10 | ||
| keywords | release note, latest changes, Hyperledger Fabric | ||
| subcollection | blockchain |
{:DomainName: data-hd-keyref="APPDomain"} {:DomainName: data-hd-keyref="DomainName"} {:android: data-hd-operatingsystem="android"} {:api: .ph data-hd-interface='api'} {:apikey: data-credential-placeholder='apikey'} {:app_key: data-hd-keyref="app_key"} {:app_name: data-hd-keyref="app_name"} {:app_secret: data-hd-keyref="app_secret"} {:app_url: data-hd-keyref="app_url"} {:authenticated-content: .authenticated-content} {:beta: .beta} {:c#: .ph data-hd-programlang='c#'} {:c#: data-hd-programlang="c#"} {:cli: .ph data-hd-interface='cli'} {:codeblock: .codeblock} {:curl: #curl .ph data-hd-programlang='curl'} {:curl: .ph data-hd-programlang='curl'} {:deprecated: .deprecated} {:dotnet-standard: .ph data-hd-programlang='dotnet-standard'} {:download: .download} {:external: .external target="_blank"} {:external: target="_blank" .external} {:faq: data-hd-content-type='faq'} {:fuzzybunny: .ph data-hd-programlang='fuzzybunny'} {:generic: data-hd-operatingsystem="generic"} {:generic: data-hd-programlang="generic"} {:gif: data-image-type='gif'} {:go: .ph data-hd-programlang='go'} {:help: data-hd-content-type='help'} {:hide-dashboard: .hide-dashboard} {:hide-in-docs: .hide-in-docs} {:important: .important} {:ios: data-hd-operatingsystem="ios"} {:java: #java .ph data-hd-programlang='java'} {:java: .ph data-hd-programlang='java'} {:java: data-hd-programlang="java"} {:javascript: .ph data-hd-programlang='javascript'} {:javascript: data-hd-programlang="javascript"} {:middle: .ph data-hd-position='middle'} {:navgroup: .navgroup} {:new_window: target="_blank"} {:node: .ph data-hd-programlang='node'} {:note .note} {:note: .note} {:note:.deprecated} {:objectc data-hd-programlang="objectc"} {:objectc: .ph data-hd-programlang='Objective C'} {:org_name: data-hd-keyref="org_name"} {:php: .ph data-hd-programlang='PHP'} {:php: data-hd-programlang="php"} {:pre: .pre} {:preview: .preview} {:python: .ph data-hd-programlang='python'} {:python: data-hd-programlang="python"} {:right: .ph data-hd-position='right'} {:route: data-hd-keyref="route"} {:row-headers: .row-headers} {:ruby: .ph data-hd-programlang='ruby'} {:ruby: data-hd-programlang="ruby"} {:runtime: architecture="runtime"} {:runtimeIcon: .runtimeIcon} {:runtimeIconList: .runtimeIconList} {:runtimeLink: .runtimeLink} {:runtimeTitle: .runtimeTitle} {:screen: .screen} {:script: data-hd-video='script'} {:service: architecture="service"} {:service_instance_name: data-hd-keyref="service_instance_name"} {:service_name: data-hd-keyref="service_name"} {:shortdesc: .shortdesc} {:space_name: data-hd-keyref="space_name"} {:step: data-tutorial-type='step'} {:step: data-tutorial-type='step'} {:subsection: outputclass="subsection"} {:support: data-reuse='support'} {:swift: #swift .ph data-hd-programlang='swift'} {:swift: .ph data-hd-programlang='swift'} {:swift: data-hd-programlang="swift"} {:table: .aria-labeledby="caption"} {:term: .term} {:terraform: .ph data-hd-interface='terraform'} {:tip: .tip} {:tooling-url: data-tooling-url-placeholder='tooling-url'} {:topicgroup: .topicgroup} {:troubleshoot: data-hd-content-type='troubleshoot'} {:tsCauses: .tsCauses} {:tsResolve: .tsResolve} {:tsSymptoms: .tsSymptoms} {:tutorial: data-hd-content-type='tutorial'} {:ui: .ph data-hd-interface='ui'} {:unity: .ph data-hd-programlang='unity'} {:url: data-credential-placeholder='url'} {:user_ID: data-hd-keyref="user_ID"} {:vbnet: .ph data-hd-programlang='vb.net'} {:video: .video}
{: #release-notes-saas-20}
Use these release notes that are grouped by date to learn about the latest changes to {{site.data.keyword.blockchainfull}} Platform for {{site.data.keyword.cloud_notm}} that built on Hyperledger Fabric v1.4.12 and v2.2.3. {: shortdesc}
Installing patches
For instructions on how to apply patches to your existing blockchain nodes. Patches are cumulative. This means that if multiple patches, for example 1.4.7-0 and 1.4.12-1, are available for a node, you should always select the latest patch, 1.4.12-1 in this case, wherever possible because it includes the fixes from the previous patches as well.
{: #10-08-2021}
Miscellaneous bug fixes and security patches.
Export certificates in .pem format for easy management and maintenance in {{site.data.keyword.cloud_notm}} Certificate Manager. See viewing and updating identities to learn more details.
{: #13-07-2021}
Certificate Authority (CA) patch 1.5.0-1, Peer and ordering node patch 1.4.12-2, 2.2.3-2
Miscellaneous bug fixes and security patches.
{: #16-06-2021}
Certificate Authority (CA) patch 1.4.9-8, Peer and ordering node patch 1.4.12-1, 2.2.3-1
Miscellaneous bug fixes and security patches.
The platform has been updated to include support for Hyperledger Fabric v1.4.12 and v2.2.3.
{: #05-05-2021}
Certificate Authority (CA) patch 1.4.9-7, Peer and ordering node patch 1.4.11-2, 2.2.2-2
Miscellaneous bug fixes and security patches.
{: #13-04-2021}
Certificate Authority (CA) patch 1.4.9-6, Peer and ordering node patch 1.4.11-2, 2.2.2-1
{: #02-22-2021}
Certificate Authority (CA) patch 1.4.9-5, Peer and ordering node patch 1.4.9-5 and 2.2.1-5
{: #01-12-2021}
Certificate Authority (CA) patch 1.4.9-4, Peer and ordering node patch 1.4.9-4, 2.2.1-4
Miscellaneous bug fixes and security patches.
{: #01-12-2021-logger-ui}
A new panel is available to override peer and ordering node log levels for specific component loggers. See Configuring node logging for more information.
{: #12-08-2020}
Certificate Authority (CA) patch 1.4.9-3, Peer and ordering node patch 1.4.9-3, 2.2.1-3
Miscellaneous bug fixes and security patches.
{: #11-19-2020}
Certificate Authority (CA) patch 1.4.9-2, Peer and ordering node patch 1.4.9-2, 2.2.1-2
Miscellaneous bug fixes and security patches.
When you link a new {{site.data.keyword.blockchainfull_notm}} Platform service instance to a Kubernetes cluster that uses community Kubernetes Ingress, the cluster Automatic Load Balancer (ALB) pods need to be restarted which can take five to ten minutes. If the restarts have not completed before you create your first blockchain Certificate Authority (CA), peer, or ordering node, the initial green status indicator on the new node can take slightly longer than you are accustomed to while the pods restart. Existing blockchain service instances are not impacted.
{: #11-02-2020}
Certificate Authority (CA) patch 1.4.9-1, Peer and ordering node patch 1.4.9-1, 2.2.1-1
Miscellaneous bug fixes and security patches.
If you are running OpenShift Container Platform 3.11 in {{site.data.keyword.cloud_notm}}, it is recommended that you upgrade your cluster to 4.4{: external} now in order to fully take advantage of the new features. After you upgrade your cluster, follow instructions to refresh your blockchain console to experience the latest functionality in this release. {: important}
{: #11-02-2020-upgrade}
In addition to deploying new nodes based on the latest Fabric v2.2.1 image, you can upgrade your existing nodes to Fabric v2.x and the capabilities of your channels, allowing organizations to take advantage of the new smart contract lifecycle process.
For information about upgrading nodes, check out Upgrading to a new version of Fabric. For information about updating the capabilities of your channels, check out Capabilities.
{: #11-02-2020-lc}
The platform has been updated to include support for Fabric v2.x smart contract lifecycle process, which enables the distributed governance of smart contracts. Learn mode about how to Deploy a smart contract using Fabric v2.x.
{: #11-02-2020-hsm}
A new process is available to configure an HSM for your blockchain nodes, delivering faster performance.
{: #11-02-2020-cert-renew}
Customers can now use the console to renew certificates that have expired or are about to expire, including the Certificate Authority (CA) TLS certificate, peer and ordering node enrollment certificates, and peer and ordering node TLS certificates.
{: #11-02-2020-delete-user}
You can now delete registered users from a CA.
{: #10-01-2020}
CA, Peer, and ordering node patch 1.4.7-3, 2.1.1-3
Miscellaneous bug fixes and security patches.
{: #08-25-2020}
CA, Peer, and ordering node patch 1.4.7-2, 2.1.1-2
Miscellaneous bug fixes and security patches.
Certificate expiration dates have been added throughout the component details, making it easier to monitor and track certificate expiration dates. See Certificate Management to learn more about your responsibilities. In addition, it is now possible to enable Node OU support for your MSPs and channels through the console. Read more about Node OU support, why this is important, and how to simplify certificate renewal for the MSPs on your network.
{: #07-14-2020}
CA, Peer, and ordering node patch 1.4.7-1, 2.1.1-1
Miscellaneous bug fixes and security patches.
{: #06-18-2020}
Peer and ordering node patch 1.4.7-0
{{site.data.keyword.IBM_notm}} considers this a critical patch that you should apply at your nearest opportunity. Not applying this patch risks being susceptible to a data integrity issue if you experience a CouchDB or underlying storage crash on your peer. This patch updates the CouchDB delayed_commits configuration property to false. The prior setting could cause the peer's CouchDB database to be in an inconsistent state in the event of a CouchDB or underlying storage system crash. The new setting ensures that a peer will recover from crashes in a consistent state. As always, it is recommended to utilize an endorsement policy that requires multiple peers to endorse a transaction, to avoid an inconsistency from a single peer from impacting the overall blockchain network state.
To be certain that your peers have no database corruption, you should reprovision your peers.
Miscellaneous bug fixes and security patches. If you are running OpenShift Container Platform 3.11 in {{site.data.keyword.cloud_notm}}, it is recommended that you upgrade your cluster to 4.3{: external} now in order to fully take advantage of the new features. After you upgrade your cluster, follow instructions to refresh your blockchain console to experience the latest functionality in this release. {: important}
{: #06-18-2020-images}
The platform introduces the capability to deploy new peer and ordering nodes based on either Hyperledger Fabric v1.4 or v2.x. Deploying peer and ordering nodes with the latest Fabric images is recommended to ensure that you have access to current Fabric fixes and features. It is not currently possible to migrate existing nodes to Fabric v2 images.
{: #06-18-2020-docker}
Leveraging the Fabric v2 external chaincode launcher capability, when you deploy a peer based on the Fabric v2.1.1 image, smart contracts are deployed into their own pod rather than inside a container on the peer pod.
{: #06-18-2020-Multizone}
If your Kubernetes cluster is configured to use multizone-capable storage, new peer and ordering nodes can be deployed that leverage multizone storage, effectively extending their high availability across cluster zones. See Multizone-capable Storage for more information.
{: #06-18-2020-k8s}
{{site.data.keyword.blockchainfull_notm}} Platform requires Kubernetes v1.15 - v1.18. If your existing Kubernetes cluster is running v1.14 or lower, you need to upgrade your cluster before you can update your existing blockchain components to this latest release.
{: #05-20-2020}
CA, peer, and ordering node patch 1.4.6-2
Miscellaneous bug fixes and security patches.
{: #05-20-2020-ICA}
You now have the option to configure an intermediate CA using the console or APIs to override the default CA settings. See the tutorial on Creating an intermediate Certificate Authority to learn more.
{: #05-20-2020-connx-profile}
The generated connection profile that client applications use to connect to the network has been streamlined and is now downloadable from the Organizations tab. See Downloading a connection profile to learn how.
{: #04-16-2020}
CA, peer, and ordering node patch 1.4.6-1
{: #04-16-2020-AWS-HSM}
If you plan to use AWS HSM, you must include the immutable and AltId parameters in your BCCSP configuration. See Fabric documentation for details.
Miscellaneous bug fixes
{: #03-24-2020}
{{site.data.keyword.IBM_notm}} is in the process of migrating existing {{site.data.keyword.blockchainfull_notm}} Platform consoles to v2.1.3, therefore, the new features described in this list may not yet be available in your console. Unsure what version you are currently using? Click the question mark icon in the upper right corner of the console. The {{site.data.keyword.blockchainfull_notm}} Platform version is visible under the page heading. Existing customers will receive a Cloud notification with more details about when their console will be migrated. {: note}
Hyperledger Fabric v1.4.6
All new nodes are deployed using Hyperledger Fabric v1.4.6. If you have an existing blockchain network, you should review the topic on Capabilities to understand how this new Fabric version can impact your network.
Hardware Security Module (HSM) support for node identities
Full cryptographic HSM support is now available for HSMs that implement the PKCS #11 standard. Using an HSM provides on-demand encryption, key management, and key storage. When you deploy a CA, peer, or ordering node, you now have the option to store the private key for the node identity in an HSM. See Configuring a node to use a HSM for more details.
Support for adding and removing ordering nodes from an existing ordering service
Previously, an ordering service could only contain one or five ordering nodes and they all were contributed from the same organization. Now, the ordering service can be deployed across multiple organizations in a blockchain network, enabling individual organizations to add and remove individual ordering nodes as required. Multi-organizational transaction ordering improves the decentralized nature of a blockchain network. Learn more about the process in the new Adding and removing Raft ordering service nodes tutorial.
Ability to override default CA, peer, ordering node configuration
Hyperledger Fabric includes many configuration options for a CA, peer, or ordering node. A subset of those options for the CA, peer and ordering node can now be overridden by using the console or the APIs.
Full Java smart contract development support
In addition to smart contracts written in JavaScript, TypeScript, and Go programming languages, it is now possible to deploy Java smart contracts from the console. Moreover, Java can be freely mixed and matched with other application and smart contract programming languages, including JavaScript, TypeScript, and Go. This heterogeneous programming language support enables an organization to capitalize on the full range of its development skills.
In order to use Java chaincode, developers should be aware that:
- Java 11 is required to execute Java smart contracts.
- Gradle v4.x and Maven v3.x are used to build Java smart contracts.
- Custom Gradle versions can be used by using a Gradle wrapper.
- Java smart contracts require the fabric-chaincode-shim at v1.4.6 or later, as this version is the first version that includes support for Java 11.
- For an example of a Java smart contract, see the FabCar Java smart contract{: external} from Fabric v1.4.
v2 APIs available
New {{site.data.keyword.blockchainfull_notm}} Platform console APIs using the route /v2/ are now available. Use of the earlier /v1/ APIs continues to be supported. See {{site.data.keyword.blockchainfull_notm}} Platform APIs for more information.
High Availability Certificate Authority
When a CA is deployed, replica sets can be configured to ensure High Availability of the node. Note that CA replica sets require a PostgreSQL database. Learn more in the Building a high availability Certificate Authority (CA) tutorial.
{: #02-06-2020}
Update default resource allocation
The default memory allocation for the peer container has been increased from 0.4GB to 1GB. When deploying a new peer, the peer container will now default to 1GB memory, but you can adjust this value according to your use case. Increasing the memory alleviates some resource contention that could occur during smart contract instantiation.
Existing peer containers are not impacted.
Peer and ordering node patch 1.4.3-1
The Ingress timeout for the gRPC web proxy has been increased to avoid an error during smart contract instantiation. It is recommended that you apply this patch to your existing peer and ordering nodes.
{: #12-11-2019}
Miscellaneous bug fixes
{: #11-15-2019}
Service availability in two new regions
The {{site.data.keyword.blockchainfull_notm}} Platform for {{site.data.keyword.cloud_notm}} is now available to be provisioned in two new {{site.data.keyword.cloud_notm}} regions: US East, and AP South. Refer to the locations information to see the data centers that are available in those regions.
{: #11-06-2019}
Simplified component creation flows
Peer, CA and ordering service creation has been streamlined. Now, when you create a node, you have to select a checkbox to configure advanced deployment options.
{: #10-02-2019}
Peer, CA, and ordering node patch 1.4.3-0
Zone selection for ordering nodes
When multiple zones are configured in your Kubernetes cluster, you can now choose which zone to deploy your ordering node to. Spreading nodes across zones is useful for ensuring high availability of your blockchain network.
Ability to set peer to be an anchor peer when the peer joins the channel
Users can now choose to designate a peer to be an anchor peer when the peer is being joined to the channel, rather than after the peer has joined the channel. An anchor peer must exist for each organization in order for cross organizational gossip to work. Anchor peers are also required for private data and service discovery to work. Learn how.
Ability to add a peer to a channel from the Channels tab
A peer can now be joined to a channel directly from the Channels tab. See Join a peer to a channel for more details.
Export/Import all
Allows for the bulk export and import of your blockchain network, including nodes, MSPs and identities, rather than having to export and import these components one at a time. See the topic on Exporting and importing in bulk for more details.
Hyperledger Fabric v1.4.3
All new nodes are deployed using Hyperledger Fabric v1.4.3. If you have an existing blockchain network, you should review the topic on Capabilities to understand how this new Fabric version can impact your network.
{: #08-21-2019}
Peer node patch 1.4.1-3
With this patch, you now have the ability to upload additional admin identities for a peer. See Adding new peer admin certificates for more information.
Select peer zone ({{site.data.keyword.blockchainfull_notm}} Platform for {{site.data.keyword.cloud_notm}} only)
If multiple zones are configured in your Kubernetes cluster on {{site.data.keyword.cloud_notm}}, you can now use the console UI to select the zone where the peer is deployed. This capability is important if you are configuring multizone HA for peers.
Peer database support now includes LevelDB
You now have the option to choose between CouchDB and LevelDB for your Peer database. For more information, see LevelDB vs CouchDB.
Certificate Authority (CA) updates
The console UI no longer stores the admin enroll id and secret that you provide when you create a CA. Therefore, after you create a CA, you are responsible for generating the admin certificates by using the new Associate identity and passing in the enroll id and secret. This change improves CA security. See Associating the identity of the CA admin for more details.
{: #08-12-2019}
Beta trial of the {{site.data.keyword.blockchainfull_notm}} Platform ends
The Beta trial of the {{site.data.keyword.blockchainfull_notm}} Platform, which began on February 12, 2019, has officially ended. All of the beta instances of your console and the components that you deployed into your Kubernetes cluster using the beta console will be deleted.
Peer node patch 1.4.1-2
This patch contains a security fix for the peer couchDB container.
{: #07-10-2019}
Ordering node patch 1.4.1-2
This patch fixes a problem that occurs when ordering nodes restart. The genesis block{: term} is updated which prevents the ordering node from communicating with the other nodes in the ordering service. You can apply this patch to all existing ordering nodes in your ordering services by following these instructions to update each ordering node. All new ordering nodes that you create will automatically include this fix.
Anchor peer removal
You now have the ability to remove anchor peers from a channel.
Miscellaneous bug fixes
Bug fixes and translation updates.
{: #05-24-2019}
Raft consensus protocol
The five node Raft ordering service, recommended for production networks, is now available. In addition, for development and testing purposes, you can deploy a single node Raft ordering service.
{: #05-09-2019}
Introducing {{site.data.keyword.blockchainfull_notm}} Platform Console APIs
APIs are now available to provision, edit, and delete peer, orderer, and CA nodes, making it possible to script the building of your blockchain network. Use the documentation in the {{site.data.keyword.cloud_notm}} API documentation repository{: external} to learn more about the APIs and try them out. In addition, see the topic on Building a network with APIs for instructions on how to use the APIs to build out your network.
Channel governance
Channel governance updates allow policies to be reconfigured. You can also control which channel members need to sign a channel update and you can orchestrate signature collection.
{: #04-17-2019}
Ability to size and scale node resources
When you deploy a node you now have the ability to specify the amount of CPU, memory, and storage to your containers, where applicable. You can later scale their resources up or down at a later time according to usage patterns. For more information, see Allocating resources.
Use of {{site.data.keyword.cloud_notm}} Identity and Access Management (IAM)
IAM is used to control user access to the console UI as well as restricting the actions they can perform in the UI. See this topic for information on how to add and remove users from the console.
{: #04-03-2019}
Support for external CA
When you add a peer or orderer node, you have the option to use certificates from an external CA, one that is not hosted by {{site.data.keyword.IBM_notm}}. See this topic on Using certificates from an external CA with your peer or ordering node for more information.
Tuning orderer performance
New orderer tuning parameters are available in the console to give you more control over your orderer throughput and performance. See this topic on Tuning your orderer for instructions on how to configure the parameters.