8.2.2 Interchain Services based on Hyperledger Fabric

Application Contract Development Guide in BSN production environment

The development of Fabric application contract is based on its own business scenario. The main implementation includes two parts: if the source chain initiates a cross-chain transaction, its application contract needs to get outbound to access the target chain; if the target chain receives a cross-chain transaction, its application contract needs to get inbound. Fabric's chain ID and cross-chain management contract’s name are automatically assigned and generated through the BSN operations and maintenance system when users open interchain services, and can be viewed in the BSN portal.

An example of a specific cross-chain transaction call can be found in Demo Contract Example.

Application Contract Development Guide in BSN Testnet

Fabric's chain ID in the BSN China Testnet is 88 and in the BSN International Testnet is 89. This chain ID is registered in Poly Enterprise, not the channel ID corresponding to Fabric itself. The name of Fabric cross-chain contract is ccm.

An example of a specific cross-chain transaction call can be found in Demo Contract Example.

Demo Contract Example

BSN production environment and BSN Testnet:

https://github.com/BSNDA/ICH/tree/main/sample/polychain/fabric-contract/online/hellopoly