FAQs

How do I use a newly created user?

After the organization administrator registers the user in Fabric CA using the Add User function, run the enrollment operation using fabric-ca-client or the Fabric SDK to issue credentials for that user.

Why can't I install the uploaded chaincode file?

The most common cause is missing dependencies. The uploaded file must include both the chaincode and all its dependencies packaged together—uploading the chaincode source alone is not enough.

To fix this:

1. Test the chaincode locally to confirm it compiles and runs correctly.

2. Package the chaincode and its dependencies into a single archive using either the script tool provided by BaaS or the peer chaincode package command.

3. Upload the packaged file through the BaaS console.

What version of Hyperledger Fabric does BaaS support?

BaaS currently supports Hyperledger Fabric 1.4.5. For details on changes in each release, see the release notes.

How does Alibaba Cloud BaaS handle Hyperledger Fabric version upgrades?

BaaS adopts new Fabric versions from the first patch release or later within a major version line—for example, 1.4.1 or later under the 1.4 major version—rather than the initial major release. This approach prioritizes stability. If a significant number of users request an initial major release, Alibaba Cloud evaluates and tests it before adoption.

When a new version is adopted:

• New blockchain networks use the new version by default.

• Existing networks continue running on their current version. Choose a maintenance window that suits your business before upgrading.

Version and data compatibility follows the same compatibility guarantees as Hyperledger Fabric itself.

For consortiums that span multiple organizations or companies, all organizations should run the same Hyperledger Fabric version to maintain compatibility.

How does BaaS achieve high availability for Hyperledger Fabric?

BaaS implements high availability (HA) at three layers:

Infrastructure layer (Kubernetes)

• The Kubernetes cluster runs multiple master nodes and multiple worker nodes.

• Pod Anti-Affinity rules distribute Fabric components across nodes to prevent single-point failures.

Fabric layer

• Each consortium deploys three orderers with the etcd Raft consensus algorithm by default.

• Each peer organization deploys at least two peers by default, and you can increase this count.

• CA supports two-node cluster deployment (Enterprise Edition and Enterprise Security Edition only), backed by the High-availability Edition of Alibaba Cloud RDS.

Application layer

• Alibaba Cloud SLB provides load balancing with health checks for all connections to Fabric backend services.

• Service Discovery support lets applications dynamically connect to available blockchain nodes.

Does BaaS support private cloud deployment?

Yes. BaaS supports private cloud deployment on three platform types:

• Container Service in Apsara Stack Enterprise

• Apsara Stack Agility PaaS

• Container service platforms built on native Kubernetes by users or third-party vendors

The BaaS console for private cloud deployments is shown below. To discuss private cloud options, contact the Alibaba Cloud sales team.