---
name: oracle-canton
description: Use for Canton Network, Canton Coin (CC / Amulet), Scan reads, and onboarding. Not EVM. Read-only.
---

# Canton Network / Canton Coin

Canton is a **separate ledger family**. Do not route it through EVM grants,
EVM scanners, Uniswap venues, or MetaMask RPC.

## What this skill owns

- Static onboarding: what Canton is, why it is not EVM, wallets, validators.
- Scan health and DSO party id.
- ANS party / name lookup (`name::fingerprint`).
- Canton Coin (Amulet / CIP-0056) holdings summary when Scan answers.
- Open mining rounds / traffic price context.

## What this skill does not own

- Quotes, swaps, bridges, sniping, MEV.
- Unsigned transaction preparation.
- Signing or broadcast.
- Private Daml application contracts (Scan cannot see them).

## Tools

- `canton_guide` — offline steps and links. Call this first for "what is Canton".
- `canton_health` — Scan version. UNAVAILABLE is a real answer.
- `canton_dso` — Global Synchronizer DSO party id.
- `canton_party` — ANS lookup by party id or name.
- `canton_holdings` — CC available/locked totals for one party.
- `canton_rounds` — open/issuing rounds; `amuletPrice` is not a DEX quote.

## Onboarding steps to give users

1. Canton is not Ethereum. No chainId, no ERC-20, no Uniswap.
2. Read https://docs.canton.network/overview/understand/five-minute-overview
3. CC pays traffic fees. https://docs.canton.network/overview/understand/canton-coin
4. Use a Canton wallet, not MetaMask. https://docs.canton.network/integrations/wallets/for-users
5. LocalNet is free. MainNet validator join: https://canton.foundation/validators/
6. Oracle reads Scan CC facts. Transfers happen in the user's Canton wallet.

## Hard rules

- Never fabricate an RPC or chainId.
- Never treat a 403/timeout as balance 0.
- Never claim prepare/sign support.
- Party ids must look like `name::fingerprint`. Reject `0x` addresses.