> 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/decentralization-manager/get-started/join-the-bitsafe-node-operator-network.md).

# Join the BitSafe Node Operator Network

{% hint style="info" %}
Join the BitSafe Node Operator Network to be considered for Canton applications that need independent operators for their Decentralized Parties.
{% endhint %}

### How it works

A node operator deploys Decentralization Manager on an existing Canton node and connects that node with BitSafe as a peer. Once the connection is validated, the operator is added to BitSafe's registry of available nodes.

When an app developer needs independent operators, BitSafe matches connected peers first. The app and participating operators enter into their own commercial agreement. BitSafe often coordinates the operator group and may act as the application administrator.

### Before starting, please check:

* [ ] An existing Canton node is running and accessible
* [ ] A technical contact is available for setup and validation
* [ ] That you are downloading the most current version of Decentralization Manager
* [ ] Peer and party details are ready to exchange securely

Decentralization Manager currently supports **AWS KMS**. Support for **MPC-H KMS** is being added.

### Join in two steps

#### 1. Deploy Decentralization Manager

Deploy the open-source application on the existing Canton node:

* [GitHub repository](https://github.com/DLC-link/decentralization-manager)
* [Product documentation](https://docs.bitsafe.finance/product-suite/decentralization-manager)

Confirm that the application is running and accessible before starting the peer exchange.

#### 2. Connect with BitSafe as a peer

1. Share your peer details and party ID with BitSafe.
2. BitSafe shares its peer details and party ID.
3. Add BitSafe's details to the Decentralization Manager instance.
4. Both teams confirm that the peer connection is visible and healthy.

### Next Steps

1. **Validation:** The connection and basic operational readiness are checked.
2. **MainNet connection:** Approved operators repeat the peer exchange on MainNet.
3. **Registry activation:** The operator is added to BitSafe's available-node registry.
4. **App matching:** BitSafe introduces suitable operators when an application needs a Decentralized Party.
5. **Commercial agreement:** The app and node operators agree scope, responsibilities, service levels, and fees.

### Commercial model

Commercial terms are agreed between each app and its participating node operators. Common structures include:

* A percentage of the app's Featured App Rewards
* A flat monthly fee
* A combination of reward share and a flat fee

BitSafe may coordinate the operator group and act as administrator, but operator earnings are not guaranteed. Fees depend on the application, operating requirements, service levels, and commercial agreement.

### Ready to begin?

Contact the BitSafe point of contact to start TestNet onboarding. BitSafe will confirm the technical contact, secure exchange channel, and required connection details.

***

### Resources

* [Node Operator Product Sheet](https://docsend.com/view/e7r4fvijh8x3zd9a)
* [Building Decentralized Parties](https://docsend.com/view/k9jeckpvng348reu)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bitsafe.finance/decentralization-manager/get-started/join-the-bitsafe-node-operator-network.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.