Together with @hectoinc, we published a piece on why tokenization alone isn't enough and why execution is what actually builds capital markets.
Zenith is the native EVM and SVM extension for @CantonNetwork, adding EVM and SVM execution alongside Canton's native Daml environment so developers can build on institutional rails without rewrites or bridges. Hecto is building pre-IPO market infrastructure that composes with Canton natively, with Zenith's EVM environment as one of the pieces it interacts with.
Two teams betting on the same thing: serious capital markets belong on institutional rails and stay composable with the open on-chain economy.
Zth.
🚨NEW EPISODE: How Canton Unlocks Institutional DeFi with Ethereum🚨
Today we're joined by @NorbertVadas, Head of Product at Zenith (@ZenithFdn), to explore how @ethereum compatibility is coming to @CantonNetwork and what that means for institutional finance.
In this episode we're discussing:
- What Zenith is building on Canton
- Canton’s privacy-first architecture
- DAML and Canton smart contracts
- Why EVM compatibility matters
- Bridging Canton assets into Ethereum
- CIP-56 assets explained
- Unified liquidity for institutional assets
- Bringing DeFi to Canton
- Rollup-inspired architecture
- State management and scalability
- Institutional adoption and real-world assets
- Mainnet roadmap and what's next
- And much more—enjoy!
—
Timestamps:
(00:00) Introduction
(00:51) What is Zenith?
(04:04) Norbert's background
(06:02) Why build Zenith?
(08:22) Understanding DAML
(12:45) Why EVM compatibility?
(17:14) CIP-56 assets explained
(27:43) How Zenith executes
(39:13) RWA lending example
(42:15) Bringing DeFi to Canton
(45:58) State growth & scalability
(50:14) Who is using Zenith?
(56:46) What's next?
(1:01:28) Mainnet roadmap
(1:03:24) Outro
STILL CONFUSED ON WHAT @ZenithFdn ACTUALLY IS👀
You don't have to worry. It's simpler than most threads make it sound.
Zenith is not a bridge connecting two environments. It's not an L2 posting state roots back to a base layer. It's an EVM extension to Canton's core protocol.
@ZenithFdn@CantonNetwork Both sides are covered by Canton's Global Synchronizer sequencing, mediation, and finality handled by one consensus mechanism across both environments at once 🔂
Zenith is not a bridge connecting two environments. It is not an L2 posting state roots back to a base layer. Zenith is an EVM extension to Canton's core protocol.
The practical difference: a Canton-native application can consume an ERC-20 token, bring it to @CantonNetwork, use it in a workflow, and return the output to the EVM side without writing specific EVM logic or running a separate node. Both environments are covered by Canton's Global Synchronizer: sequencing, mediation, and finality handled by the same consensus mechanism across both sides simultaneously.
@NorbertVadas explains the full architecture in his @indexed_pod episode: https://t.co/ow9p8MRJJZ
Zth.
Japan's JGB repo market processes ¥250-270 trillion annually, roughly $1.6 trillion, representing around 10% of the global government bond-backed repo market. It currently settles a business day after execution, operates within traditional market hours, and requires manual processes at every step.
Earlier this year, Zenith was invited to join @progmat_en's Tokenized JGB and On-chain Repo Working Group alongside MUFG, Mizuho, Sumitomo Mitsui, BlackRock Japan, State Street, SBI Securities, Japan Exchange Group, and other major institutions. The working group is conducting a joint study on bringing that market on-chain, targeting same-day settlement, 24/7 availability, and cross-border access.
With around $350 billion in on-chain repo already in execution globally today, Japan's JGB market is the next major step in that trajectory. A comprehensive report is expected in October 2026, with issuance pilots targeted for later this year.
Zth.
@flop_labs https://t.co/M1cLnGiGVb
Made this for Technocore (@flop_labs) and signed it into the technocore room as #536.
did:key:z6Mko71d19wcGzmhgU2qahS48YeH3no7XVydDFGWjVwSoUKX
@flop_labs Note: this checks the format is correct, not that you own the private key. That still needs a real signature.
U can also check at https://t.co/M1cLnGiGVb
did:key:z6Mko71d19wcGzmhgU2qahS48YeH3no7XVydDFGWjVwSoUKX
STILL DON'T KNOW IF YOUR DID:KEY IS ACTUALLY VALID? @flop_labs
Before you publish your identity for Technocore, you can check it in one place
→ https://t.co/3nwtB69wLe
I saw people pasting DIDs without knowing if the format was even right, I built a small validator to check.
@flop_labs WHAT IT DOES →
> Decodes your did:key
> Checks the key type (Ed25519, secp256k1, etc.)
> Confirms the byte length is correct
> Tells you if it's structurally valid or broken
> All client-side, in your browser nothing is sent anywhere.
Robin Chest is coming soon 🤯
The NFT mint will be exclusive on OpenSea
Blockchain @RobinhoodApp
First 5555 participants will receive WL👇
https://t.co/qpP1kGLCGM
The rest will participate in a raffle
Each chest contains $BUBU tokens, which can be opened at a special event before TGE