Blockchain Service scenario

Available in VPC

Blockchain Service starts with creating a blockchain network from the NAVER Cloud Platform console. Next, set up each component that makes up the blockchain network, and install and instantiate the chaincode in the channel to enable the blockchain network.

The overall Blockchain Service usage scenario can be summarized as follows:

Configure single network

• For example, a single participant creates 1 network, and transactions occur in 1 channel

• The highlighted part such as msp1 in the scenario is an example name of a component of Blockchain Service in the diagram above.

1. Create network
   • Network: nbs-net1
   • Orderer: MSP(oderer1-msp1), CA(orderer1-ca1), Orderer(orderer1)
   • Organization: MSP(msp1), CA(msp1-ca1), Peer(msp1-peer1)
   • Channel: channel1 (configuring a channel when creating a network configures a consortium for "msp1" automatically)
   • Guide page when creating a component separately (configured in the following order)
     • 1. Create network
2. Create additional organization and peer

• Organization : MSP(msp2), CA(msp2-ca2), Peer(msp2-peer2)
• Create CA
• Add an ID for the peer to the CA created (msp2-ca2) (see Manage CA user ID)
• Create MSP
• Create peer

3. Configure consortium
   • Include msp2 MSP in orderer consortium
4. Join msp2 MSP as a member of the channel (channel1)
   • Manage channel member (MSP)
5. Join msp2-peer2 to channel1
   • Manage peer in channel
6. Develop chaincode
7. Package chaincode (CDS)
8. Install chaincode
9. Instantiate chaincode
10. Call, build, and run chaincode

• Create and export Client-type ID certificate in msp1-ca1 CA (see Manage CA user ID)
• Exporting access information from msp1 MSP (see Export MSP)
• Use certificate and access information to call, build, and run chaincode (see Develop, build, and run application)

11. Run 10 times with msp2

Configure multi network

• For example, 2 participants create 2 networks, and transactions occur on 2 channels

• The highlighted part such as msp1 in the scenario is an example name of a component of Blockchain Service in the diagram above.

1. Configure Network 1
   • Proceed until step 5 of Configure single network above
2. Create Network 2 Create network
   • Network: nbs-net2
   • Orderer: MSP(oderer2-msp2), CA(orderer2-ca2), Orderer(orderer2)
   • Organization: MSP(msp3), CA(msp3-ca3), Peer(msp3-peer3)
   • Channel: channel2 (configuring a channel when creating a network configures a consortium for "msp3" automatically)
   • Guide page when creating a component separately (configured in the following order)
     • 1. Create network
3. Invite network 2 from network 1
   • Invite network
   • Upon invitation confirmation, each imports the other's MSP, and network 2 automatically imports network 1's orderer/channel
4. Add the msp3 imported from network 1 and network 2 to the orderer consortium
   • Configure consortium
5. Add the msp3 imported from network 1 and network 2 as a channel member
   • Manage channel member (MSP)
6. In network 2, add msp3-peer3 to the automatically imported channel1
   • Manage peer in channel
7. After chaincode development and packaging, install in both networks 1 and 2, and instantiate chaincode in network 1
   • Develop chaincode
   • Package chaincode (CDS)
   • Install chaincode
   • Instantiate chaincode
8. Use certificate and access information in network 1 to call, build, and run chaincode for msp1 and msp2
   • Create and export Client-type ID certificate in msp2 CA (see Manage CA user ID)
   • Exporting access information from msp2 MSP (see Export MSP)
   • Call, build, and run chaincode (see Develop, build, and run application)
9. Proceed 8 times with msp3 at network 2