Skip to main content

Release Notes

Per-release summary of what changed in ChainLaunch (the open-source chaindeploy distribution). Versions are tagged at github.com/LF-Decentralized-Trust-labs/chaindeploy/releases.

v0.4.0 — Fabric-X subsystem​

Headline: First-class support for Hyperledger Fabric-X — the high-throughput, Arma-consensus variant of Fabric with split orderer/committer services and a postgres-backed query layer.

What's new​

  • Fabric-X networks (overview)
    • Two-stage lifecycle (create → join) so orderer groups and committers receive the genesis block before booting.
    • Single-MSP mode (one shared AcmeMSP for all parties — easiest for token-sdk-x sample apps) and multi-MSP mode (one MSP per party — production-shape Arma BFT topology).
    • 4-party network provisions ~22 containers in single-MSP mode, ~37 in multi-MSP mode.
  • One-click quickstart
    • Web UI: Networks → Fabric-X → Quick-start runs the full provisioning flow with progress streaming.
    • CLI: chainlaunch fabricx quickstart --network-name my-fabricx --parties 4. See chainlaunch fabricx quickstart for flags.
  • Namespaces (guide) — logical partitions within the single arma channel, each backed by its own postgres table.
  • Block & transaction explorer for Fabric-X, served from the committer's query-service.
  • Network templates for Fabric and Besu — export a network as a reusable template, import it in another instance. (Fabric-X template support is on the roadmap.)
  • linux-arm64 release artifact ships alongside linux-amd64, darwin-amd64, darwin-arm64.
  • Backup credential encryption at rest for backup-target configs.
  • End-to-end test improvements for login and user creation flows (Playwright).

Breaking changes​

None. Fabric-X is an additive subsystem — existing Fabric and Besu networks are unaffected.

Upgrade notes​

  • No data migrations required for Fabric or Besu workloads.
  • Backup-target rows created before this version are auto-migrated on first read; no manual action needed.
  • If you run on macOS / Windows Docker Desktop and want to use Fabric-X, set CHAINLAUNCH_FABRICX_LOCAL_DEV=true on the server process so containers can reach the host (see Quickstart prerequisites).

Known limitations​

  • Fabric-X chaincode is not managed by ChainLaunch — business logic lives in token-sdk-x applications outside the platform.
  • Single channel per Fabric-X network (always arma); use namespaces for logical partitioning.
  • The reference token-sdk-x plugin x-sources (fabricx-network, fabricx-identity) ship in ChainLaunch Pro, not in the open-source build.

See also​

Earlier releases​

For pre-0.4.0 release notes, see the GitHub releases page.