Skip to main content

Architecture

1. Basic Architecture​

Hyperledger Fabric Architecture

Main Components​

ComponentDescription
VPS - EC2 MachineThe overall hosting environment (likely Amazon EC2 virtual private server)
ChainLaunchThe core application that manages blockchain deployments
DB (SQLite)Embedded SQLite database that stores configuration and state information
PeersBlockchain network nodes that maintain and validate the distributed ledger
OrderersComponents responsible for transaction ordering and block creation
UsersEnd users who interact with the system through UI or CLI

Key Relationships​

  • The entire system runs on a VPS/EC2 machine infrastructure
  • ChainLaunch is the central component that coordinates deployments
  • ChainLaunch uses an embedded SQLite database for persistent storage
  • ChainLaunch deploys both Peers and Orderers using Systemd
  • Users interact with ChainLaunch through either a user interface (UI) or command-line interface (CLI)

This appears to be a deployment architecture for a blockchain system, possibly based on Hyperledger Fabric (given the presence of Peers and Orderers, which are typical Fabric components). The system uses Systemd for service management to deploy and manage the blockchain components.

2. Module architecture​

ChainLaunch is a blockchain deployment and management platform with a modular architecture designed for flexibility, reliability, and cross-platform compatibility. The system enables deployment of various blockchain networks including Hyperledger Fabric, Besu, and other blockchain frameworks through a unified interface.

ChainLaunch Architecture

2.1 Deployment Module​

This central module handles the deployment of blockchain networks across different platforms.

Supported Blockchains:

  • Hyperledger Fabric
  • Hyperledger Besu
  • Additional blockchain frameworks

Deployment Methods:

  • SystemD (Linux environments)
  • LaunchD (macOS environments)
  • Docker (Cross-platform: Linux/macOS)

The deployment module interfaces with the appropriate system service manager based on the host operating system, ensuring consistent deployment across heterogeneous environments.

2.2 Backup Module​

Provides comprehensive data protection for blockchain network components.

Key Features:

  • Provider-based backup architecture supporting multiple backup strategies
  • Automated backup scheduling
  • Node state snapshots
  • Certificate and cryptographic material preservation

Supported Backup Providers:

  • Restic/S3: Backup to any S3-compatible storage (including AWS S3, MinIO, and other S3-compatible providers)
  • EBS Snapshots: Native AWS EBS volume snapshots with support for multiple authentication modes (static credentials, instance role/IRSA, named profile, role assumption via STS)
  • VMware Snapshots: VMware virtual machine snapshot integration

Backups are systematically collected from network nodes and associated certificates, then stored via the configured provider, ensuring data durability and disaster recovery capabilities.

2.3 Monitoring Module​

Continuously tracks the health and performance of the blockchain network.

Functionality:

  • Node availability monitoring through ping operations
  • Performance metrics collection
  • Anomaly detection
  • Integration with the Notifications module for alerts

2.4 Notifications Module​

Manages alerts and communications regarding network status.

Communication Channels:

  • Email notifications via configurable SMTP providers
  • Customizable notification rules and thresholds

2.5 Network Module​

Handles blockchain network configuration and management.

Capabilities:

  • Network creation and initialization
  • Node joining and management
  • Configuration updates and propagation
  • Network topology management

2.6 Plugin Module​

Provides an extensible architecture for adding custom functionality to ChainLaunch.

Capabilities:

  • Plugin registration and lifecycle management
  • Custom integrations with external systems
  • Extensible platform functionality

2.7 Smart Contract AI (SCAI) Module​

Provides AI-assisted smart contract and chaincode development capabilities.

Features:

  • Browser-based smart contract development environment
  • AI-powered code generation and assistance (Claude, OpenAI)
  • Integrated development workflow for chaincode

2.8 System Integration​

The modular design allows components to operate independently while maintaining coordinated functionality through well-defined interfaces. Key integration points include:

  • The Monitoring module triggers the Notifications module when issues are detected
  • The Network module submits configuration updates to the Deployment module
  • The Backup module interfaces with both network nodes and cloud storage

2.9 Cross-Platform Compatibility​

ChainLaunch achieves cross-platform operation through:

  1. Platform-specific deployment mechanisms (SystemD, LaunchD, Docker)
  2. Abstraction layers that normalize platform differences
  3. Containerization for consistent environments where appropriate

2.10 Storage and Persistence​

  • Network configurations and state information stored in an embedded SQLite database
  • Backups preserved via configured backup providers (S3-compatible storage, EBS Snapshots, VMware Snapshots)
  • Local caching for performance optimization

3. Deployment diagram​

The deployment diagram illustrates the complete node deployment workflow in ChainLaunch across both Linux and macOS operating systems. The process begins with a platform check that branches into two main paths:

For Linux systems, deployment utilizes SystemD services. This involves creating and configuring a .service file with working directory specifications, environment variables, resource limits, and restart policies. The service is then enabled and started through systemctl commands.

For macOS systems, deployment leverages LaunchD services. This path involves creating a .plist file configured with working directory settings, environment variables, standard I/O handling, and load-time behavior. The service is then loaded and started using launchctl commands.

Both deployment paths share common configuration requirements, including network settings, key and certificate management, chain data storage location, and log directory setup. The entire system operates within a standardized directory structure under ~/.chainlaunch/, containing dedicated directories for peers, orderers, and Besu nodes.