Canton 钱包与 Web3 钱包

Understanding the key differences between Canton and traditional crypto wallets

Canton wallets work differently from Web3 wallets like MetaMask. 本页 explains the key differences and what they mean for 用户 and 开发者.

Fundamental Differences

Privacy Model

Web3: Public by Default

On Ethereum, your 钱包:

• Has a public address anyone can see
• Shows 余额 to anyone who queries
• All 交易 visible on block explorers
• 交易 patterns analyzable

Anyone can query: 0x123...abc has 45.67 ETH
Anyone can see: 0x123...abc sent 5 ETH to 0x456...def

Canton: Private by Default

On Canton, your 钱包:

• Has a party identifier visible only to you
• 余额 visible only to you (and entitled Party)
• 交易 visible only to participants
• No public 交易 history

Only you can see: Your party has 100 CC
Only participants see: You transferred 20 CC to another party

转账 Capabilities

Canton wallets support transfer patterns not possible in traditional wallets.

Multi-Step Transfers

Traditional transfer: Send X now.

Canton supports complex 工作流:

Pre-Approvals

Allow another party to withdraw up to a certain amount:

flowchart LR
    A[Alice] --> |pre-approve 100 CC| B[Bob]
    B --> |withdraw 50 CC when needed| A

    Note[Bob can withdraw up to 100 CC<br>without Alice's per-transaction approval]

Use cases:

• Subscription payments
• Recurring transfers
• Automated 应用 flows

Allocations

Reserve tokens for a specific purpose:

flowchart TB
    WALLET[Your Wallet<br>100 CC]
    ALLOC[Allocated<br>30 CC for Trade]
    FREE[Available<br>70 CC]

    WALLET --> ALLOC
    WALLET --> FREE

Use cases:

• Trade settlement
• Escrow arrangements
• Multi-step 工作流

Delivery vs. Payment (DvP)

Atomic exchange of different assets:

flowchart LR
    subgraph Atomic[Single Atomic Transaction]
        A1[Alice sends CC] --> |atomic| B1[Bob sends Asset]
    end

    Note[Either both happen or neither happens]

Why this matters:

• No settlement risk
• No trust required between Party
• Complex exchanges in single 交易

Connection Model

Web3: Any RPC

Web3 wallets connect to any compatible RPC 端点:

• Infura, Alchemy, or self-hosted
• Can switch 提供方 freely
• Any node can answer queries

Canton: Your 验证者

Canton wallets connect to a specific validator:

• The validator hosting your party
• Can’t freely switch (party is hosted somewhere specific)
• Only your validator has your data

flowchart TB
    subgraph Web3[Web3 Model]
        W1[Wallet] --> RPC1[RPC 1]
        W1 --> RPC2[RPC 2]
        W1 --> RPC3[Any RPC]
    end

    subgraph Canton[Canton Model]
        W2[Wallet] --> VAL[Your Validator]
        VAL --> |hosts| PARTY[Your Party]
    end

Identity Model

Web3: Address-Based

• Address derived from public key
• Anyone can generate addresses
• Pseudonymous (address is identity)

Canton: Party-Based

• Party identifier tied to validator hosting
• Party creation involves validator
• Not pseudonymous in the same way

Explorer Differences

Web3: Global Explorer

Block explorers show all 网络 activity:

• Any 交易
• Any address 余额
• Any 合约 state

Canton: Personal Explorer

Canton explorers show your activity:

• Your 交易 only
• Your balances
• Your 合约

Implications for 用户

Implications for 开发者

下一步

本文由 CC Privacy Club 根据 Canton Network 官方文档（CC-BY-4.0）整理翻译，仅供学习；实现细节以官方最新版本为准。