Skip to content

Products · Decentralization Manager

Overview

Build governed applications across independent Canton nodes

Section titled “Build governed applications across independent Canton nodes”

Decentralization Manager is the open-source application from BitSafe for creating and operating Decentralized Parties on Canton Network. It coordinates the topology, packages, peers, governance and workflows that several organizations need to control one shared Canton party.

A Decentralized Party is a Canton party that several independent participants host and govern together. Its members and its approval rules change through approved workflows. Its party ID stays the same.

  • Create and operate Decentralized Parties.
  • Add members to a Decentralized Party, remove members, and change its threshold.
  • Decentralize an existing local party, so that other participants host it for failover or co-validation.
  • Decentralize an external party, so that several participants host a party whose key a wallet holds.
  • Serve a tenant API, /v0/tenant/*, that wallet providers call with an API key.
  • Coordinate encrypted peer-to-peer workflows between nodes over the Noise protocol.
  • Distribute and compare Daml packages across participants.
  • Propose, confirm, execute, cancel and expire governed actions.
  • Automate the assignment of CIP-104 reward coupons for a Decentralized Party.
  • Sign ledger transactions with a party key from the participant vault or from AWS KMS.
  • Extend the governance lifecycle with application-specific Daml modules.
GoalPage
Understand the components and how they coordinateArchitecture overview
Try it in developmentPrerequisites, Run locally and Run with Docker
Deploy and operate a nodeProduction deployment, Configuration reference and Monitoring and logging
Create a Decentralized PartyCreate a Decentralized Party
Add a participant to a Decentralized PartyAdd a member to a Decentralized Party
Add hosts to a party that only one participant hostsDecentralize an existing party
Host a wallet-held party on several participantsDecentralize an external party
Run a node next to an AWS KMS participantSign with AWS KMS
Collect CIP-104 rewards for a Decentralized PartyReward automation
Build a governed applicationModule selection and custom Daml and Use cases
Integrate through the operator API or the tenant APIAPI and workflow reference
Review securitySecurity architecture

Each participating organization runs its own Decentralization Manager node. Each organization controls the authentication, local state, Canton credentials, peer records and upgrades of its node. The node that starts a workflow run is the coordinator of that workflow run. The coordinator role ends with the workflow run. It gives no lasting control over the Decentralized Party.

Learn how the components work together: Architecture overview.