> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/product-suite/decentralization-manager/use-cases.md). # Use Cases Vault governance, FAR rewards, multi-sig wallet, and utility service walkthroughs. The Decentralization Manager supports a range of multi-party governance scenarios on Canton. The walkthroughs below illustrate common deployments built on the onboarding, contract deployment, and governance workflows. ## Vault governance Deploy vault contracts governed by a decentralized party, where actions on the vault require threshold-based confirmation from member participants before they execute on the ledger. ## FAR rewards Coordinate the distribution of FAR rewards through governance confirmations, so that reward actions are proposed, confirmed by the required members, and executed under shared control. ## Multi-sig wallet Operate a wallet under decentralized control, where transactions are signed by multiple participants and only execute once the configured signing threshold is reached, removing reliance on any single key holder. ## Utility service Provision and run a utility service such as minting and burning under governance. The manager coordinates provider setup, mint, and burn actions through propose-confirm-execute cycles across the member participants. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bitsafe.finance/product-suite/decentralization-manager/use-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.