Skip to main content

Create Fabric Nodes

This tutorial walks you through creating peer and orderer nodes for your Fabric network in ChainLaunch.

Prerequisites​

Create Nodes via the UI​

Single Node​

  1. Go to Nodes in the left sidebar
  2. Click Fabric Node
  3. Select the organization from the dropdown
  4. Choose the node type: Peer or Orderer
  5. Configure network settings (listen address, external endpoint) or keep defaults
  6. Click Create Node

The node will start automatically and appear in the nodes list with status RUNNING.

Bulk Create (Multiple Nodes)​

Use bulk create to set up multiple peers and orderers at once:

  1. Go to Nodes in the left sidebar

Nodes section

  1. Click Bulk Create next to Fabric Node

Bulk create button

  1. Select the organization from the dropdown (e.g., Org1MSP)

Select organization

  1. Enter the Number of Peers (e.g., 2)

Number of peers

  1. Enter the Number of Orderers (e.g., 3)

Number of orderers

  1. Click Next to review network configuration

Next step

  1. Review the settings and click Next again

Review settings

  1. Click Create Nodes to start provisioning

Create nodes

  1. All nodes are created and running

Nodes created

Create Nodes via CLI​

# Create a single peer
chainlaunch node create --type peer --org Org1MSP

# Create a single orderer
chainlaunch node create --type orderer --org Org1MSP

# Bulk create: 2 peers + 3 orderers for Org1MSP
chainlaunch testnet fabric \
  --name my-network \
  --org "Org1MSP" \
  --peerOrgs "Org1MSP" \
  --ordererOrgs "Org1MSP" \
  --peerCounts "Org1MSP=2" \
  --ordererCounts "Org1MSP=3"

Create Nodes via API​

# Create a peer node
curl -X POST http://localhost:8100/api/v1/nodes \
  -H "Content-Type: application/json" \
  -d '{
    "name": "peer0-org1",
    "platform": "FABRIC",
    "nodeType": "FABRIC_PEER",
    "organizationId": 1
  }'

# Create an orderer node
curl -X POST http://localhost:8100/api/v1/nodes \
  -H "Content-Type: application/json" \
  -d '{
    "name": "orderer0-org1",
    "platform": "FABRIC",
    "nodeType": "FABRIC_ORDERER",
    "organizationId": 1
  }'

Node Types​

TypePurposeMinimum per network
PeerEndorses transactions, commits blocks, hosts chaincode1 per org
OrdererOrders transactions into blocks, manages channels1 (3+ recommended for fault tolerance)
CAIssues certificates for org identities1 per org (created automatically)

Tips​

  • Orderer count: Use 3 or 5 orderers for crash fault tolerance (CFT). A single orderer works for development but has no fault tolerance.
  • Peer count: Start with 1 peer per org for PoC. Add more for high availability or to separate endorsement from committing.
  • Resource planning: Each peer needs ~512MB RAM and each orderer ~256MB RAM minimum.

Next Steps​