Moving a DeFi protocol to @CantonNetwork takes more than translating its code from Solidity to Daml. Protocols that rely on a global state have to be rethought for a network built around privacy.
Zenith Head of Ecosystem @GArentoft explains the problem in a new episode of Tokenization Talks with @haumicharts, and why Zenith takes a different route: Solidity applications deployed on an EVM environment inside Canton’s consensus, where they can interact with Canton-native assets.
Chapters worth jumping to:
> 06:25 How Zenith connects Ethereum applications to Canton
> 10:42 Daml, privacy and the developer challenge
> 15:10 Canton super validators and governance
> 20:33 Can Canton build a retail ecosystem?
Listen now on ↓
YouTube:
Spotify:
Apple Podcasts:
Zth.
PublishedFri, November 13, 2026
Sourcevia @zenithfdn ↗
Related updates
Zenith is among the co-sponsors supporting IBC's contribution to @lfdecentralized, alongside individuals from Wells Fargo, Figure Markets, OpenZeppelin, Partior, Cardano Foundation, and other industry leaders.
Look at who's coming together around open blockchain interoperability.
Banks, public blockchain ecosystems, digital asset infrastructure providers, and security companies are backing an initiative that brings IBC under neutral Linux Foundation governance.
And for us, this goes beyond supporting an open standard. Zenith is actively working with the @cosmos team, with IBC already integrated into Zenith Testnet. This lays the groundwork for cross-chain communication and asset transfers between Zenith and IBC-connected networks, extending interoperability beyond the Canton ecosystem.
IBC has facilitated $50B+ in transaction volume across 200+ networks. Its move to neutral Linux Foundation governance opens the door to broader collaboration across financial institutions, blockchain ecosystems, and infrastructure providers.
As institutional finance expands across different execution environments, interoperability becomes increasingly important. We're excited to be contributing to that work both through industry collaboration and technical integration.
Zth.
Universal Burn could see early participation before full automation.
Governance-led arrangements, such as a dedicated synchronizer under Foundation oversight, could help apps adopt the model sooner.
@Wesarn_real discusses with @LongViewCrypto.
Every CIP in the public repository carries a status.
Proposed. Approved. Active. Final. Withdrawn. Rejected. Replaced. Obsolete.
Whatever the outcome, every proposal stays on record.