Zenith @ZenithFdn

@CantonNetwrkTR @CantonNetwork Great to see more of the Canton community following Zenith's progress! We're excited to bring the EVM ecosystem closer to Canton's institutional network 🫡

@CantonArmy @temple_ny @BitSafe_Finance Great to see the Canton ecosystem continuing to expand 👏

@CantonArmy @HeslinKim Don’t build what you think the market wants. Build what institutions are asking for, because at that point you have a definitive customer, not a bet 👏

Ethereum built the most composable financial ecosystem in the world. @CantonNetwork built what institutions needed first: privacy, compliance, and atomic settlement at real scale. For years those two things existed in parallel, with no native path between them. Zenith’s role is to be the middle ground where they converge. Not by picking which asset class comes first or by betting on a specific tokenization thesis, but by building the execution environment that lets the full scope of traditional capital markets - U.S. Treasuries, sovereign debt, JGBs, tokenized funds - compose natively with the lending protocols, liquidity pools, and DeFi primitives that Ethereum developers have spent a decade building and hardening. @HeslinKim explains the philosophy behind this in the clip below. Zenith doesn’t define the product roadmap in advance. The institutions coming to Zenith as customers define it, because when a specific institutional need drives what gets built, you already know the application has a home before a single line of code is written. The Zenith EVM Testnet is where that convergence starts, open today for developers to build on: docs.zenith.network Zth.

Canton Army @CantonArmy

2 days ago

Institutions ask. Zenith builds. @ZenithFdn co-founder Heslin Kim explains why customer demand shapes what they’re bringing to Canton.

3 8 38 2K 0

Zenith does not use PHP anywhere in our tech stack and our platform is not affected.

The word“composability” gets used to describe three very different things in blockchain, and conflating them is the source of most of the confusion around cross-chain finance. > Bridging: An asset is locked in one place and a representation of it is created somewhere else. The asset has moved, but what you now hold is a claim on a lockbox. If the lockbox fails, the claim is worthless. > Messaging: One chain sends a message, and another chain acts on it later. The two halves of the operation settle separately, on different schedules, under different finality rules. > Atomic composability: Every step of an operation, across every application and asset involved, happens in a single transaction. Either all of it succeeds, or none of it does. TradFi knows the third one as delivery versus payment (DvP), Ethereum developers know it as atomic smart contract execution. It’s the only one that matters for finance at scale, and it’s the one Zenith was built around. The full argument is in the article. Zth.

Zenith @ZenithFdn

3 days ago

x.com/i/article/2113…

2 4 11 1K 2

x.com/i/article/2113…

Most cross-environment blockchain architectures break composability at the seam between environments. Zenith was built to eliminate that seam entirely. At @blockworksDAS Asia 2026, @HeslinKim described what Zenith co-architected with @digitalasset’s CPO Bernard Elsner: the first non-EVM L1 with atomic EVM settlement, where block production and state finality are embedded directly into Canton’s consensus. The result: Daml-native Canton assets, with their full selective disclosure and privacy model intact, composable with the top DeFi protocols in the same atomic transaction. An EVM application doesn’t just connect to Canton, it settles inside it. The institutional asset layer and Ethereum’s developer ecosystem, finally on the same rails. The 3.6 upgrade brings external_call() to @CantonNetwork Mainnet. What Heslin describes here is what that actually means in practice. Zth.

@theorem_markets @ethereum Congratulations team! RWA trading done right. 🤝🏼

@chaingreets @miladdogecoindo @SvpChain 👀

Zenith has joined the Digital Assets Association (DAA), a Singapore-based non-profit advancing the integration of blockchain technology into traditional finance. Singapore is an important meeting point for financial institutions, digital asset infrastructure, and cross-border capital markets. DAA brings these worlds together, with a focus on institutional blockchain adoption, asset tokenization, and connecting traditional finance with on-chain markets. Zenith is joining a network of industry players including @coinbase, @BitGo, @GSR_io, @trmlabs, Murex, and many others. At Zenith, we're building Ethereum-compatible execution infrastructure for Canton Network. Zenith EVM lets developers build Solidity applications that interact atomically with Canton-native assets and workflows, and Zenith Stack enables institutions to deploy their own customizable EVM environments with greater control over how they operate. Looking forward to being part of the DAA community and contributing to what's being built across the region. Learn more: digitalassetsassociation.org Zth.

@SuontamaJulia @ERC3643Org gZenith! 🤝

external_call() was co-architected with @digitalasset’s core protocol team from the ground up, with changes made inside @CantonNetwork's protocol, not on top of it. Every milestone independently verified by @CantonFdn's governance committees before the next one began. The primitive is now part of Canton’s main branch. It is live on the Zenith EVM Testnet today and is scheduled for rollout to Canton Mainnet as part of the upcoming 3.6 release. Two years of building toward something that didn’t exist before: a single atomic decision across a Daml workflow and an EVM runtime, finalized together inside Canton’s consensus. Try it: docs.zenith.network Zth.

Canton Network @CantonNetwork

5 days ago

Canton can finalize a transaction where a Daml contract calls directly into an EVM runtime and back, as a single decision. @ZenithFdn built the external_call() primitive that makes this possible. @NorbertVadas explains how it works.

4 36 144 9K 7

Multi-chain institutional infrastructure at this scale is a significant signal. Canton, Besu, and now Stellar, each serving a specific purpose within DTCC’s architecture. Zenith is the EVM and SVM extension on the Canton side, and the developer ecosystem that can now build on top of this is the part worth watching 🫡

@AssetsDaily @CantonNetwork gCanton!

The scale of what DTCC is building keeps coming into focus. Multi-chain by design - Canton, Besu, Stellar - with each environment doing what it does best. Zenith’s role in that picture is opening Canton’s side of it to Ethereum developers. The application layer being built around this infrastructure is the next interesting chapter. Zth.

@Nick_Researcher The ecosystem around Canton is filling out Zenith EVM is the public builder path, Zenith Stack is the institutional execution path. Both are meant to plug into the rails that are already there. Zth. 🔥

@Nick_Researcher @CantonNetwork @The_DTCC @Broadridge @HSBC @Tradeweb Institutional rails are already live. The builder access layer is what lets more teams put applications on top of them 🫡

Canton for privacy and compliance, Besu for private network requirements, Stellar for payments infrastructure. This is how large-scale institutional initiatives actually operate, they don’t choose one chain, they choose the right environment for each requirement. Zenith sits in that picture as the EVM and SVM extension of @CantonNetwork, connecting Ethereum’s developer ecosystem to where this settlement activity happens 🫡

@cantonnews_org @Canborsa_DEX 👏👏👏