> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/reference/networks/canton.md).

# Canton (CC)

Canton on Ledger Enterprise: accepting incoming transfers, automatic approval, how balances are held, and dual-validator signing.

Canton behaves differently from every other network here, in ways that affect daily operations. Read this page before using a Canton Account.

## How Canton differs

Canton is built for privacy between institutions. Each party sees only the transactions it takes part in. There is no public ledger for anyone to inspect.

Three consequences shape how this product behaves:

* A transfer needs the consent of both parties. That is why receiving is an action here, and not a wait.
* A balance is held as a set of individual coin contracts, not as a number. The model is closer to Bitcoin than to Ethereum.
* Two validators co-sign every transaction.

For the network itself, see [canton.network](https://www.canton.network/).

## Token coverage

Ledger Enterprise supports **Canton Coin (CC)**.

Tokens that comply with the **Canton token standard**, [CIP-0056](https://github.com/canton-foundation/cips/blob/main/cip-0056/cip-0056.md), are supported on Request. CBTC, CUSD, SBC and USDCx are examples.

Support for a given token is enabled per Workspace. Ask your Ledger contact to enable one.

## Four things to know

<table><thead><tr><th width="257.3359375">Property</th><th>What it means for you</th></tr></thead><tbody><tr><td><strong>Nothing settles automatically unless feature is enabled</strong></td><td>Incoming transfers arrive as proposals. Somebody has to accept them unless automatic approval is enabled</td></tr><tr><td><strong>Balances are held as individual coin contracts</strong></td><td>One transfer can draw on at most <strong>100</strong> of them. Idle contracts lose value over time, and expire if fees grow beyond what they hold</td></tr><tr><td><strong>Two validators co-sign</strong></td><td>Every transaction is signed by both Ledger and a 3rd party validator. Neither can act on your behalf alone</td></tr><tr><td><strong>Token recovery sits with the issuer</strong></td><td>If a token fails, recovering it is the responsibility of whoever issued it, not Ledger</td></tr></tbody></table>

These are shown as a disclaimer when a Canton Account is created. They are not warnings about Ledger Enterprise; they are properties of the network.

## Receiving is an action, not a wait

On most networks receiving is passive: someone sends, and the funds appear. **On Canton you have to accept.**

An incoming transfer arrives as a **transfer proposal**, listed in the **Transfer Proposals** section of the Account overview. Each row shows the amount with its countervalue, when the proposal expires, and what you can do about it.

Accepting is a governed Request. It follows the Account's **Receive** Rule, needs the approvals that Rule specifies, and is signed with your own key like any other operation.

### What you see on a proposal

<table><thead><tr><th width="143.22265625">State</th><th>What it means</th></tr></thead><tbody><tr><td><strong>Review</strong></td><td>You can act. Accepting starts the approval flow</td></tr><tr><td><strong>Pending</strong></td><td>Someone has already started accepting it and it is awaiting approval. Open it to see the Request</td></tr><tr><td><strong>Not initiated</strong></td><td>Nobody has started, and you do not have permission to. Ask someone who does</td></tr><tr><td><strong>Expired</strong></td><td>The proposal lapsed before it was accepted. Nothing arrived</td></tr></tbody></table>

> **Important:** Proposals expire. An incoming transfer nobody accepts in time does not arrive, and the sender has to start again. Automatic approval, below, removes the need to watch for them.

To decline a transfer, let the proposal expire. There is no decline action in the interface.

> **Note:** A proposal can also disappear before you act on it. The sender can withdraw a transfer while it is still waiting. If a proposal you expected is no longer listed, ask the sender before you assume it failed.

## Automatic approval

Rather than accepting each transfer by hand, you can let incoming transfers be accepted automatically for a period. This is the **Receive approvals** section on the Account overview.

* **To turn it on, create a Request.** It is approved under the Account's Receive Rule. Your governance makes this decision, not an individual.
* You need permission to receive on the Account to turn it on. Without it you see the current state and no action.
* Once active, the section shows the date and time it runs until.

> **Warning:** Automatic approval **expires, and there is no reminder or renewal button**. When it lapses, incoming transfers go back to needing manual acceptance without notice. A proposal nobody notices then expires unaccepted.

Automatic approval is available on **main Canton Accounts only**, not on token Accounts. Token Accounts always require manual acceptance.

## Sending

Sending follows [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md), with two differences.

**A reason field.** You can attach a reason of up to 128 characters. It travels with the transaction as additional information. Some recipients require one.

**Your transfer waits for the recipient.** A transfer you send sits as a proposal on their side until they accept it. It has not settled until they do.

**You cannot take a sent transfer back.** Ledger Enterprise has no withdraw or cancel action for a transfer you have sent. If a transfer should not go through, ask the recipient not to accept it, and let the proposal expire.

> **Important:** Contact the recipient before the proposal expires. When a proposal lapses, nothing moves and nobody is notified. Both sides can be left expecting a payment that will never arrive.

**The 100-contract limit** matters on an Account that has received many small amounts. One transfer can draw on at most 100 coin contracts. If a payment needs more than that, send it in several transfers.

## Addresses

Canton identifies Accounts by a **party ID** rather than a conventional blockchain address. It is shared and verified the same way as any other address, described in [**Receiving assets**](/help-center-v2/guides/transactions/receiving-assets.md).

Sharing your party ID is what lets someone send to you. It is separate from accepting what they send.

## Related

* [**Receiving assets**](/help-center-v2/guides/transactions/receiving-assets.md)
* [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md)
* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Networks**](/help-center-v2/reference/networks.md)


---

# 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://help.enterprise.ledger.com/help-center-v2/reference/networks/canton.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.