Skip to main content
Privy supports Canton at Tier 1. You can create Canton wallets, produce raw Ed25519 signatures, and export private keys. Your application is responsible for registering the wallet as an external party and interacting with the Canton network.
Creating a Privy wallet does not register a party on Canton. You must complete the validator’s external-party topology flow before the wallet can interact with the network.

Create a wallet

Create a wallet with chain_type set to canton. Run these examples on the server to keep the app secret private.
The wallet uses Ed25519 and EdDSA. Its address is the fingerprint of its public key, formatted as 1220 followed by a 32-byte SHA-256 digest. Canton party IDs add a party hint to this fingerprint: <party-hint>::<wallet.address>.

Register the party

Canton is a permissioned network. Register each new wallet through a validator that is connected to your target network. The validator constructs the topology transactions; Privy signs their hashes; the validator then submits them to the network. Your validator operator must provide:
  • The validator API base URL
  • A bearer token authorized to call the validator admin API
  • A unique party hint
The example below uses the validator’s external-party/topology/generate and external-party/topology/submit endpoints. Validator authentication is deployment-specific, so fetch the bearer token according to your operator’s instructions.
1

Generate topology transactions

Privy returns the Ed25519 public key as a 00 prefix followed by the 32-byte key. Canton expects only the raw 32-byte key, so remove the first byte.
2

Verify the party ID

Check that the validator derived the same fingerprint as Privy before signing anything.
3

Sign the topology transactions

Sign each transaction hash directly. Do not hash it again or add a prefix.
4

Submit the signed topology

Submit the original topology transactions with their signatures. Store the returned party_id; applications use the full party ID, not the fingerprint alone, when interacting with Canton.
After registration, use your validator’s APIs and Canton application libraries to construct and submit application-specific transactions. When Canton requires an Ed25519 signature over a 32-byte hash, sign that hash with Privy’s raw_sign method.
Canton support does not include transaction construction, submission, validator authentication, or party registration as managed Privy operations.