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.
What is a Decentralized Party?
Section titled “What is a Decentralized 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.
What Decentralization Manager provides
Section titled “What Decentralization Manager provides”- 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.
Choose a path
Section titled “Choose a path”| Goal | Page |
|---|---|
| Understand the components and how they coordinate | Architecture overview |
| Try it in development | Prerequisites, Run locally and Run with Docker |
| Deploy and operate a node | Production deployment, Configuration reference and Monitoring and logging |
| Create a Decentralized Party | Create a Decentralized Party |
| Add a participant to a Decentralized Party | Add a member to a Decentralized Party |
| Add hosts to a party that only one participant hosts | Decentralize an existing party |
| Host a wallet-held party on several participants | Decentralize an external party |
| Run a node next to an AWS KMS participant | Sign with AWS KMS |
| Collect CIP-104 rewards for a Decentralized Party | Reward automation |
| Build a governed application | Module selection and custom Daml and Use cases |
| Integrate through the operator API or the tenant API | API and workflow reference |
| Review security | Security architecture |
Operating boundary
Section titled “Operating boundary”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.
Technical sources
Section titled “Technical sources”- Decentralization Manager repository
- Repository README
- Architecture
- Adding a member to a Decentralized Party
- Decentralizing an existing party
- Decentralizing an external party
- Signing with AWS KMS party keys
- Reward automation package
- Wallet library for the tenant API
- Deployment guide
Next step
Section titled “Next step”Learn how the components work together: Architecture overview.
Ask the docs
Answers come only from this documentation and can be wrong. Check the linked pages.
Ask a question about BitSafe, CBTC or the developer guides. For example: