⚡ Hybrid-Ready Fabric Network Overview

[apierr]

This document explains the structure of the Hyperledger Fabric network setup using a hybrid-ready BCCSP stub.
It shows how Docker Compose, Dockerfiles, and images interact. 🚀

---

🗺 ASCII Diagram

╔════════════════════════════════════════════════════════════╗
║                    docker-compose.yaml                     ║
║                fabric-baseline-hybrid                      ║
╠════════════════════════════════════════════════════════════╣
║ Defines services:                                          ║
║   • peer0_org1                                             ║
║   • orderer                                                ║
║                                                            ║
║ Configuration:                                             ║
║   • environment variables                                 ║
║   • volumes                                                ║
║   • ports                                                  ║
║   • network                                                ║
╚═══════════════════════╦════════════════════════════════════╝
                        │
          ┌─────────────┴─────────────────────┐
          │                                   │
╔═════════▼════════════╗           ╔══════════▼════════════╗
║  peer0_org1 service  ║           ║    orderer service    ║
╠═════════════════════╣           ╠═══════════════════════╣
║ image:               ║           ║ image:                ║
║   custom-fabric-peer ║           ║   hyperledger/        ║
║   :2.5               ║           ║   fabric-orderer:2.5 ║
║   (built locally)    ║           ║                       ║
║                      ║           ║ environment:          ║
║ environment:         ║           ║   • CORE_ORDERER_     ║
║   • CORE_PEER_BCCSP_*║           ║     BCCSP_*           ║
║   • CORE_PEER_BCCSP_ ║           ║                       ║
║     DEFAULT_TYPE=    ║           ║ volumes, ports, net   ║
║     HYBRID           ║           ╚══════════╦════════════╝
║                      ║                      │
║ volumes, ports, net  ║                      │
╚══════════╦═══════════╝           ╔══════════▼════════════╗
           │                       ║   Official Image      ║
╔══════════▼═══════════╗           ║ fabric-orderer:2.5   ║
║   Dockerfile.peer    ║           ╚══════════════════════╝
╠═════════════════════╣
║ FROM fabric-peer:2.5 ║
║ COPY bccsp/hybrid/   ║
║ make peer            ║
║ ENTRYPOINT peer      ║
╚═════════════════════╝

---

📖 Explanation

1️⃣ Docker Compose YAML

• Orchestrates all containers in the network. 🛠
• Uses already available images for standard services, e.g., the orderer. ✅
• Specifies environment variables, volumes, ports, and networks. 🌐

2️⃣ Peer Custom Image

• The peer0_org1 container uses a custom-built image with the HYBRID BCCSP stub. 🧩
• The Dockerfile (Dockerfile.peer) starts from the official Fabric peer image and adds the stub code. ✨
• Environment variable CORE_PEER_BCCSP_DEFAULT_TYPE=HYBRID instructs the peer to use the HYBRID provider. 🔑
• Currently, the stub delegates all cryptographic operations to ECDSA (SW). 🔒

3️⃣ Orderer

• The orderer container uses the official image hyperledger/fabric-orderer:2.5. 🏛
• It is also configured hybrid-ready via environment variables but still uses ECDSA. ⚙️

4️⃣ Workflow

1. Docker Compose reads the YAML and starts the containers. ▶️
2. Peer0_org1 starts using the custom image that includes the HYBRID stub. 🟢
3. Orderer starts using the official image with hybrid-ready config. 🟢
4. The network works as usual with ECDSA, ready for future Post-Quantum integration. 🕒

---

This setup allows a gradual approach:

• Start with a functioning ECDSA network. ✅
• Introduce a hybrid BCCSP stub in the peer. 🧩
• Add Post-Quantum cryptography later without changing the network orchestration. ⚡

---

If you want, I can also highlight the “future PQC steps” directly in the ASCII diagram with emojis, so it’s visually clear where the upgrade will occur. Do you want me to do that?