Canton and LayerZero
Canton applications use the Daml smart contract language. A Daml template defines a contract’s data and the choices (actions) that specific parties can exercise on it. Each party is hosted on a participant node (also called a validator node). The participant node stores only the contracts that its parties can see. The synchronizer orders transactions but does not store contract state.What Changes on Canton
Before you send tokens into Canton from another chain, read Send from Another Chain to Canton.
Canton Guides
Getting Started on Canton
The differences from the EVM, and what a Canton integration needs.
Technical Overview
The Canton model as it affects LayerZero: parties, Daml, disclosure, packages, holdings, and fees.
Protocol Overview
How LayerZero runs on Canton: the Virtual Endpoint Rollup, LayerZero parties, and the message lifecycle.
OFT Deployment
Every step to connect an existing CIP-0056 token to LayerZero with an OFT adapter and wire it to an EVM chain.
Canton Coin
Bridge native Canton Coin on Canton to and from bridged CC on BSC, Solana, HyperEVM, and HyperCore.
LayerZero on Canton is not yet open for self-service integrations. The Canton packages and deployment tooling are not public, so Deploying an OFT on Canton marks each step that you complete with LayerZero Labs. To discuss integrating, contact the LayerZero team.
Network Details
LayerZero’s Canton testnet deployment runs on the Global Synchronizer DevNet, not on Canton TestNet.
For the DVNs that verify Canton Coin messages on Canton mainnet, see the Canton deployment page and DVN Providers.