CANTON 3.4 TO CANTON 3.5 TRANSITION

Update: 2026-04-24

See details in the long-term SV Operations schedule

Phase 1: Splice 0.5.x releases pause, and multiple new Splice Daml models go into effect
- The Splice 0.5.x release line is complete

Daml Models and configuration settings going live on MainNet in Phase 1:
- Development Fund Manager Party is now live on MainNet as of April 15th.
- CIP-0104 Traffic-based App Rewards Increments 2 and 3 are in effect on MainNet
- May 5th: Daml models from Splice 0.5.16 go live on MainNet. All Validators must upgrade to Splice 0.5.16 on MainNet before this date.

Phase 2: Splice 0.6.x Release line. Splice 0.6.x begins to introduce features from Canton 3.5 as part of the standard bundle. Protocol-breaking changes remain behind feature flags.
- Splice 0.6.0 had errors in early testing by SVs on DevNet.
- Splice 0.6.1 will be released to SVs on Monday, April 27th.
- Validators should not upgrade until at least Tuesday, April 28th.
- Splice 0.6.x will introduce Logical Synchronizers, along with the ability to upgrade between two physical synchronizer nodes while preserving the same Logical SynchronizerID
- This will allow protocol-changing upgrades to take place without pausing Daml transactions. Topology transactions, like adding new nodes, onboarding parties, and vetting Daml models, do pause during protocol-changing upgrades.

Major Milestones for Splice 0.6.x:
- April 27th: Splice 0.6.1 goes live on DevNet. Logical Synchronizer introduced.
- April 30th: Validator Liveness Rewards reduced to zero (0).
- Late May:* Super Validators practice an upgrade using a Logical Synchronizer (aka Logical Synchronizer Upgrade / LSU) on DevNet. No actual protocol changes will be introduced in this practice.

Phase 3: Upgrade Global Synchronizer networks to Canton Protocol 35
- After proving out Logical Synchronizer upgrades on Splice 0.6.x, all three Global Synchronizer networks will perform a Logical Synchronizer upgrade to Canton protocol Version 35.
- Final timing and numbering of this upgrade, and the specific Canton 3.5 features to be included along with it, is still TBD. New features will roll out over time, relying on LSUs to minimize impact on Node Operators and App Providers.

Major Milestones for Phase 3:
- Early June: LSU on DevNet introduces protocol upgrade and major new features. TestNet LSU follows one week later.
- Mid-June: LSU on MainNet introduces protocol upgrade. New features introduced, following the same feature flags and upgrade procedures introduced on DevNet and TestNet.

|| @Canton Builder @Dev Announcements @Product Updates ||

CC is now live on SwissBorg

Canton Coin (CC) is now available on SwissBorg, expanding access to the Canton ecosystem through a new gateway.

SwissBorg offers:
- Fiat on-ramps including Card, Apple Pay, and Google Pay
- Seamless swaps from 400+ assets into $CC
- Deep liquidity aggregated across 50+ exchanges for efficient execution

As $CC fuels the Canton Network, this listing helps bring broader access to infrastructure designed for real financial markets.

Original post: https://x.com/i/status/2047646884974784739 @Announcements

🤝 Canton Network x WalletConnect Integration is now live

WalletConnect has integrated with Canton Network, connecting 700+ wallets to a blockchain purpose-built for institutional finance.

Millions of users across WalletConnect's global ecosystem can now connect to institutional workflows, 24/7 collateral mobility, and on-chain payments, without broadcasting financial activity across the network.

→ Private, compliant on-chain activity
→ Institutional-grade payments & RWAs
→ Secure access without exposing sensitive data

This is a major step toward enabling access to institutional crypto markets 🏛

|| @Dev Announcements @Product Updates ||

Alchemy x Canton

Alchemy is now integrated with the Canton Network.

This expands how applications connect across coordinated, institutional-grade workflows, making it even easier for builders to tap into the network.

Institutional finance is already moving onchain, with $8T+ in tokenized assets, 800+ validators, and major financial institutions already in production across the Canton ecosystem.

This is another strong step forward for developer access and network connectivity.

Read more:
https://x.com/i/status/2044077407720862094 @Announcements

Major Exchange Expansion for CC

CC (Canton) continues to expand across major exchanges and platforms.

• Upbit has now enabled CC trading across the KRW, BTC, and USDT markets, significantly expanding access and liquidity in Korea
• Crypto.com App has also enabled deposits and withdrawals of $CC via the Canton Network

This is another strong step forward for global accessibility, liquidity, and ecosystem participation around Canton.

Upbit official notice:
https://www.upbit.com/service_center/notice?id=6144&view=share

Crypto.com App:
https://crypto.onelink.me/ADTi/neacpmij @Korean @Announcements

HSBC Payments on Canton

HSBC Payments is joining the Canton Network, marking another major step forward for institutional-grade settlement infrastructure.

HSBC has successfully completed a tokenised deposit pilot on Canton, demonstrating how deposits can be issued, transferred, and settled atomically with digital assets on the network.

This is a strong signal of what becomes possible when the right institutional partners are building on shared, privacy-preserving rails together.

The Canton team, no matter where they are, keeps moving crypto forward.

Read more:

https://financialit.net/news/infrastructure/hsbc-announces-successful-tokenised-deposit-pilot-canton-network-demonstrating @Announcements

🛠️ Canton Builders - We Want Your Feedback

The Canton DevRel team has just launched a new Quarterly Ecosystem Survey to better understand your builder experience.

Whether you’re actively building or just getting started, your input helps shape:
- Better tooling
- Improved onboarding
- Stronger ecosystem support

Please help us identify what is missing, what slows you down, what you enjoy about building on Canton, or anything else you'd like to share.

If you have a few minutes, we’d really appreciate your thoughts 👇
🔗 https://forms.gle/MBzEJ7h2EYvzaFoY9

|| @Canton Builder @Dev Announcements ||

Q1 Canton Network Developer Survey

This quarterly survey serves as a community pulse-check to measure what's working and where developers are experiencing friction. Please take some time to share your feedback.

Governance Through Contribution

On the Canton Network, governance rewards contribution, not capital accumulation.

As shown in the visual, Super Validators are selected for the utility they provide to the network, operating under neutral, transparent governance built for institutional use. @Announcements

Super Validators on Canton

Super Validators are the organizations that run, secure, and operate Canton’s Global Synchronizer, the shared coordination layer that enables atomic, privacy-preserving transactions across the network.

What they do

• Vote on onchain governance changes
• Participate in BFT consensus for message ordering and confirmation
• Keep the shared layer decentralized, with no single Super Validator in control
• Earn Canton Coin rewards tied to the utility they contribute
• Commit to a specific set of network milestones

Today, the Canton Network has 45+ Super Validators, spanning both TradFi institutions and crypto-native organizations, each bringing specialized capability while collectively governing the network.

Shared infrastructure requires coordinated operation, and this is what that looks like on Canton. @Announcements

ENTERING CANTON 3.4 TO CANTON 3.5 TRANSITION PERIOD

Starting this week, Canton Network enters a period of transition from Canton 3.4 to Canton 3.5.  This will introduce a series of significant new features on DevNet, TestNet and MainNet.

The transition will take place in multiple phases:
Phase 1: Splice 0.5.x releases pause, and multiple new Splice Daml models go into effect

Splice 0.5.18 is now available on DevNet, and will roll out to TestNet and MainNet over the coming two weeks.
- This will be the final feature release of the Splice 0.5.x release line. If issues are found in this release, Splice 0.5.19 will contain patches. If issues are found in this release, a Splice 0.5.19 release will be created that will contain patches only.

Daml Models and configuration settings going live on MainNet in Phase 1:
- April 15th: Development Fund Manager Party changes from null to a value
- April 20th: CIP-0104 Traffic-based App Rewards Increments 2 and 3:
- Increments 2 and 3 are complete, ahead of schedule, and have been included in Splice 0.5.18. Please see the "Note" section in the Splice 0.5.18 release notes for details.
- These features will roll out to TestNet and MainNet over the coming two weeks, arriving on MainNet April 20th
- This enables API support for precise traffic costs per transaction (as used for application reward attribution), earlier than the original plan of mid-May.
- Increment 4 is currently on track to be available on MainNet by the end of June.
- May 5th: Daml models from Splice 0.5.16 go live on MainNet. All Validators must upgrade to Splice 0.5.16 on MainNet before this date.

Phase 2: Splice 0.6.x Release line. Splice 0.6.x begins to introduce features from Canton 3.5 as part of the standard bundle. Protocol-breaking changes remain behind feature flags.
- Most important: Splice 0.6.x will introduce Logical Synchronizers, along with the ability to upgrade between two physical synchronizer nodes while preserving the same Logical SynchronizerID
- This will allow protocol-changing upgrades to take place without pausing Daml transactions. Topology transactions, like adding new nodes, onboarding parties, and vetting Daml models, do pause during protocol-changing upgrades.

__Major Milestones for Splice 0.6.x: __
- April 27th: Splice 0.6.0 goes live on DevNet. Logical Synchronizer introduced
- April 30th: Validator Liveness Rewards reduced to zero (0).
- Late May: Super Validators practice an upgrade using a Logical Synchronizer (aka Logical Synchronizer Upgrade / LSU) on DevNet. No actual protocol changes will be introduced in this practice.

Phase 3: Upgrade Global Synchronizer networks to Canton Protocol 35
- After proving out Logical Synchronizer upgrades on Splice 0.6.x, all three Global Synchronizer networks will perform a Logical Synchronizer upgrade to Canton protocol Version 35.
- Final timing and numbering of this upgrade, and the specific Canton 3.5 features to be included along with it, is still TBD. New features will roll out over time, relying on LSUs to minimize impact on Node Operators and App Providers.

Major Milestones for Phase 3:
Early June: LSU on DevNet introduces protocol upgrade and major new features. TestNet LSU follows one week later.
Mid-June: LSU on MainNet introduces protocol upgrade. New features introduced, following the same feature flags and upgrade procedures introduced on DevNet and TestNet.

|| @Dev Announcements @Product Updates @Canton Builder||

Canton at ETHCC

Canton is hosting a builders breakfast bar in Cannes, bringing together builders, partners, and ecosystem teams for coffee and conversations around what comes next for institutional infrastructure.

A great way to start the morning at ETHCC. @Announcements

Protocol Development Fund: Who can apply

The Protocol Development Fund supports work that strengthens the Canton Network.

Anyone can propose work that benefits the network, with three common paths:
- Committee-led proposals from Tech & Ops members with clear delivery and milestones
- Open community proposals from external builders with a Tech & Ops sponsor
- RFPs issued for specific priorities with defined scope and outcomes

Proposals are evaluated based on merit, structure, and alignment with network priorities. @Announcements

Attention

Splice 0.5.16, coming to DevNet on March 23rd, introduces new Daml models that will impact some exchanges and applications.

Action:
All exchanges and wallets that parse AmuletRules_Transfer transactions directly must either update their parsing methods to the new transfer workflows, or move to CIP-0056 token standard transfers.

All application developers who directly depend on splice-amulet models older than version 0.1.17 must recompile to a version greater than or equal to 0.1.17.

The Daml models requiring these changes will take effect on the following dates:

DevNet: Apr 7, 2026
TestNet: Apr 21, 2026
MainNet: May 5, 2026

Details in the Splice Release Notes: https://docs.dev.sync.global/release_notes.html#release-notes
Fully detailed example of the new transaction formats in this doc: https://docs.google.com/document/d/1kRxG8KQxY6bzzmJYm2PkRWaGCFWwVK7JXwomsz8pfaU/edit?tab=t.0

|| @Dev Announcements @Product Updates @Canton Builder ||

Validators and Super Validators on Canton

Canton separates execution from coordination to preserve privacy while enabling scale.

Validators handle transaction execution within their own domains.
Super Validators coordinate the network through the Global Synchronizer without accessing transaction contents.

Together, this model enables private execution, atomic settlement, and network-wide composability on the Canton Network.

Take a closer look at how each role operates in the visuals below. @Announcements

The Canton Ecosystem Updated

The Canton Ecosystem continues to expand across every layer of the stack.

From custody and wallets to exchanges, DeFi, tokenized assets, onchain cash, liquidity, and developer tools, builders and institutions are coming together on the same network.

This is what it looks like when institutional infrastructure and onchain innovation converge.

Explore the growing ecosystem and the teams building on Canton: https://www.cantonecosystem.com/ @Announcements

DeFi on Canton is taking shape

Canton’s DeFi ecosystem is beginning to take form, with featured apps deploying across multiple verticals.

These applications are building on the same privacy-preserving, atomic settlement rails already used by institutions on the Canton Network.

DeFi and TradFi are converging to create AllFi on Canton. @Announcements

CIP-0105 Approved: SV Locking & Long-Term Commitment Framework

CIP-0105 has been approved.

This proposal introduces a voluntary, onchain framework allowing Super Validators (SVs) to demonstrate long-term commitment to the Canton Network.

How it works

Super Validators may choose to lock a portion of their lifetime earned $CC rewards.
The more rewards locked, the greater their forward SV Weight.

Locked tokens vest gradually over 365 days.

Why it matters

As the Canton Network becomes more visible to external markets, governance must rely on cryptographic proof of alignment, not reputation alone.

CIP-0105 ensures governance influence accrues to those demonstrating real, long-term commitment to the network.

Read the full proposal:
https://github.com/canton-foundation/cips/blob/main/cip-0105/cip-0105.md @Announcements

Canton is an open network. Users are free to connect wallets and interact with Featured Apps or non-Featured Apps of their choosing. The Foundation does not curate or designate “approved” tools across the broader ecosystem, nor does it gate who can deploy applications to the network.

As always, users should exercise their own judgment and perform appropriate due diligence before interacting with any third-party application—especially those that have not been formally introduced or documented by the teams behind them.

To put this in perspective: you wouldn’t go to Ethereum to complain about something happening on Arbitrum, or to Solana to complain about pump fun. The same principle applies within the Canton ecosystem—individual dApps operate independently and are responsible for their own products and services.

If you require support for any ecosystem dApps, please contact the official support channels of that specific application. The main Canton Telegram channel nor main Discord chats cannot provide support for third-party dApps.

If an app seeks Featured App status or formal recognition, that process is public and transparent and will be clearly communicated to the community. App specific business models and user commercials are not determined or implemented by the Foundation.

As always, DYOR (Do Your Own Research) before interacting with any application or protocol within the ecosystem.

|| @Announcements ||

Three important updates:

Batched and Weighted Featured App Markers ~~are live on MainNet as of last week (Splice 0.5.11)~~. Coming March 31st to MainNet. This will make it possible to replace App Markers with a single weighted marker setting a weight equivalent to the nominal traffic cost of the transaction. Multiple markers will be be processed as a batch. Implementing weighted and batched markers reduces your total transaction cost, speeds up transaction processing, and makes more bandwidth available across the network.
- This is an intermediate step on the path toward traffic-based app rewards (CIP-0104).

Free confirmation responses went live last week. This means that if your node hosts parties that are involved in transactions that they do not submit, your node does not need to pay a traffic fee to submit confirmation responses for those transactions.

Fork coming March 31st. Splice 0.5.11 introduces Daml models that will fork any node that does not upgrade to at least 0.5.11 before those Daml models go live. These models were previously scheduled to go live yesterday, but that has been delayed until March 31st to resolve a bug in a dependent process on the Sequencer

|| @Dev Announcements @Product Updates ||

Security Advisory — Potential secrets exposure in validator logs

We have identified an issue where sensitive credentials (such as your PostgreSQL password and Ledger API auth token) may be written in plaintext to validator application logs. This only occurs under a specific combination of conditions described below.

Who is affected?
You may be affected if both of the following are true:
1. Your validator deployment uses additional DARs beyond the standard Splice dars, AND you deployed those dars via the .appDars Helm value OR by manually setting the SPLICE_APP_DARS environment variable to a non-null value. (Uploading additional DARs via other means does not make you affected.)
2. DEBUG-level logging is enabled for the validator app.
- Helm deployments: DEBUG logging is on by default.
- Docker Compose deployments: The default log level was changed from DEBUG to INFO in Splice 0.5.10.

What should I do?
1. Immediately ensure your validator app log level is set toINFO or above. This stops any further exposure.
If you believe your deployment matched both conditions above, we recommend rotating the following secrets:
- PostgreSQL database password
- Ledger API auth token
- Any other secrets you may have added as environment variables on the validator app deployment

Fix
This issue has been resolved in splice#4230 and will be included in the upcoming 0.5.14 release.

|| @Dev Announcements @Canton Builder ||

Privacy and Institutional Scale on Canton

Privacy is a core requirement for institutional deployment.

Canton’s network-of-networks architecture supports horizontal scaling through independent synchronizers and dynamic traffic routing.

As activity grows, institutions can introduce additional synchronizers to expand capacity without creating central bottlenecks.

This design enables sustained, institutional-scale operation on the Canton Network.

Shaul Kfir explains the model and its implications in detail.

Full interview:
https://x.com/i/broadcasts/1lPJqvmnAObxb?s=20 @Announcements

Attention

Splice 0.5.13, which will be available on DevNet next week, deprecates the sample python script, scan_txlog.py, that has until now provided a reference for how to download and parse the Scan /updates stream. This script will no longer be maintained, and will be removed in a future release. Developers interested in understanding how to parse transactions from history should refer to the documentation for Reading and parsing transaction history involving Token Standard contracts.

DAML MODEL UPGRADE ISSUE impacting PQS users

The following DAML package versions were introduced by Splice 0.5.11, and are effective on DevNet as of this week.

name version

amulet 0.1.16

amuletNameService 0.1.17

dsoGovernance 0.1.22

validatorLifecycle 0.1.6

wallet 0.1.17

walletPayments 0.1.16

These Daml model versions are currently scheduled to go live on TestNet (March 3rd) & MainNet (March 10th).

However, Splice 0.5.11 deployments this week on TestNet have exposed an issue where in certain cases, "uploaded but not-yet vetted" packages break some assumptions in PQS. In order to avoid these issues, validator operators that use PQS are advised, as part of the 0.5.11 deployment, to make the following configuration changes:

• in k8s, set the Helm value on the validator app maxVettingDelay to 0m
• in docker-compose, add to the validator container an environment variable  ADDITIONAL_CONFIG_MAX_VETTING_DELAY with value canton.validator-apps.validator_backend.max-vetting-delay = 0m

@Dev Announcements @Canton Builder

New Blog: Scaling Canton Apps with Wallet and App Interoperability

We just published a new post outlining a proposed standard to improve wallet and app interoperability across the Canton Network.

The goal is to make it easier for wallets and applications to connect, communicate, and operate seamlessly, helping increase overall network connectivity and composability.

If you are building a wallet or application on Canton, this is an important step toward creating more unified user experiences and stronger ecosystem coordination. More updates on this initiative will follow.

**Read the full post: **

https://www.canton.network/blog/scaling-canton-apps-with-a-standard-for-wallet-and-app-interoperability @Announcements

Canton Protocol Development Fund is live

The Canton Foundation has launched the Canton Protocol Development Fund and opened the Grants Program.

This creates dedicated funding for work that strengthens the Canton Network:
core protocol R&D, developer tooling, security and audits, reference implementations, and shared ecosystem infrastructure.

If you are building something that provides common good utility on Canton, you can propose it for support. Funding is milestone based, paid in Canton Coin, and guided by a clear review process with public reporting.

Learn more about the Protocol Development Fund:
https://canton.foundation/canton-foundation-launches-protocol-development-fund/

Explore the Grants Program and apply:
https://canton.foundation/grants-program/ @Canton Users

CIP-0100: Development Fund Governance Update 🔔

CIP-0100 is now approved, formalizing how Canton Network’s 5% Development Fund (CIP-0082) is governed.

The fund is administered by the Canton Foundation Tech & Ops Committee with a clear process for:
- Proposal submission
- Milestone-based grants
- Ongoing accountability

Transparency & Reporting 📊

You can expect:
- Quarterly public reporting on receipts, balances, commitments, disbursements, and outcomes
- Annual independent audit/attestation of the fund

How Funding Works 💧

Funding is designed to be earned through delivered milestones:
- Recipients mint CC directly when milestones are verified
- Funds do not route through the Foundation

Long-Term Goal 🛠️

The goal is simple:
Sustain long-term investment in core protocol R&D, developer tooling, security, audits, and ecosystem infrastructure that compounds utility over time. @Announcements

2,000,000,000 CC burned

Canton has now passed 2,000,000,000 CC burned.

On Canton Network, 100% of network fees are burned, with fees priced in USD, so supply is only retired when there is real activity on chain. Every burn reflects actual transactions executed under institutional controls.

This is burn–mint equilibrium in practice: rewards secure the network and support builders, while sustained usage continuously reduces supply.

Two billion burned. Real network use. Real compounding utility. @Announcements

Validators powering Canton

Canton now has 700+ validators securing the network.

On Canton:
- Validators execute smart contract logic at the edge and validate private transactions only for the parties involved, so data stays strictly need to know.
- Super Validators operate the Global Synchronizer, order Canton Coin (CC) transactions, and coordinate atomic workflows across applications.

Together, this validator layer upholds privacy and sovereignty and makes interoperability possible at institutional scale on Canton Network. @Announcements

Need-to-know privacy, by design

Public chains broadcast everything to everyone. Canton does not.

On Canton, privacy is built directly into the asset and smart contract, so only the right parties can see, store, validate, and audit the data. @Announcements

Canton Community on Telegram

Canton's builder community is scaling across more platforms. @Announcements

If you are shipping, integrating, or closely tracking regulated onchain finance, you can now connect with the broader ecosystem in our Telegram hub.

Join the Telegram community here:
https://t.me/cantonnetwork1

On Validators, Access, and Alignment

In a recent Quadrillions episode, Yuval Rooz spoke about what validator participation should look like in practice, and how that connects to the original promise of blockchain.

On many networks, becoming a validator effectively requires staking tens of millions, which excludes the very teams this technology was meant to open doors for.

Canton takes a different approach.

Super Validators on Canton Network are not selected simply because they can post the most capital, but because they add the most value: smaller crypto firms and operators that showed up early, shipped, onboarded users, and put real work into the network.

The core principle is straightforward:
alignment should come from contribution and responsibility, not just balance sheet size.

You can listen to the full discussion right below 👇 @Announcements

Have you checked out the Quadrillions Podcast yet?

Quadrillions is Canton’s podcast, created in collaboration with Blockworks.

If you have not listened yet, now is a good time to catch up on recent episodes.

Check it out here 👉 https://quadrillionspod.com/ @Announcements

Node Operators on Canton

Node operators are the backbone of Canton Network, running privacy-enabled infrastructure, securing assets, and connecting real financial applications across markets.

Thinking about operating a node? Here is what node operators do:

• Validate and host application workflows for their own institutions and clients, keeping sensitive data private while transacting on a shared network.
• Plug into a public network of roughly 640+ validators and about 38 Super Validator nodes that coordinate atomic settlement across independent applications.
• Earn Canton Coin ($CC) for liveness and network usage, and, as Super Validators, help govern protocol upgrades and the Global Synchronizer.

If you are building institutional-grade finance, from tokenized Treasuries to money market funds and collateral networks, running a node is how you gain direct, secure access to Canton infrastructure and help shape its roadmap. @Announcements

Welcome New Validators

New validators joining the Canton Network @Announcements:

1. Exaion
2. LBank
3. Solv Finance
4. Sats Terminal
5. Humaine
6. Empireum
7. Global Settlement
8. Gemini
9. Gemini 2
10. Coinversaa Incorporated
11. Rho Labs
12. Newity
13. Ampersan
14. Waybridge
15. Boosty Labs
16. Ms Pay
17. Stableport
18. SV Nodeops
19. C7
20. 5nghost
21. Coinbase
22. Coinbase
23. Coinbase
24. NewMoney
25. KvarnX

Privacy and Institutional Capital

Privacy is the key to unlock institutional capital at scale.

• Without it, blockchains are suitable for experiments, not trillions.
• With it, institutions get control over who sees what, regulators get the visibility they need, and capital can finally flow 24/7.

That’s how real finance moves on-chain. @Announcements

Attention Canton Community

We’re launching the Canton Network Developer Experience & Tooling Survey to learn more about you, the projects you’re building, and how this community, our docs, and our tools can better support your work.

If you write Daml, build on Canton, operate infrastructure, or are just getting started, your feedback is extremely valuable and will directly shape what we prioritize next (content, examples, events, and tooling improvements).

👉 Please take a few minutes to fill out the survey here: https://forms.gle/r6UC3fMsWKLvNfVX7

Thank you in advance for helping us make this a better place for builders. If you have thoughts beyond the survey, feel free to share them in #《🛠️・dev-feedback-and-questions》 as well.

|| @Dev Announcements@Canton Builder@Announcements@Learner ||

Privacy for Real Finance

Privacy isn’t optional for real financial workflows.

Canton is designed so only the right parties see the right data, without sacrificing composability or compliance.

That combination is what makes institutions comfortable moving core workflows on-chain. @Announcements

On-Chain Derivatives for Institutions

Institutions want the speed of crypto without the compromises.

With institutional derivatives activity accelerating, trading desks now expect:
- Around-the-clock liquidity
- Composability across platforms
- Privacy that meets institutional standards
- Full compliance

Most chains make you choose between these. Canton doesn’t.

Canton Network is the only public L1 that lets institutions trade, settle, and manage collateral on-chain with traditional-market confidence and blockchain-native benefits.

This is the next phase of capital markets.
This is where finance flows.

Learn more:
https://www.canton.network/blog/on-chain-collateral-for-bilateral-crypto-derivatives-trading @Announcements

Recap with Canton

The Canton Network continues to grow as partners across the globe bring real-world financial products on-chain. Here’s a snapshot of what’s been rolling out across the ecosystem:
- JPMorgan brings JPM Coin to Canton
https://www.coindesk.com/tech/2026/01/07/jpmorgan-to-issue-its-jpm-stablecoin-directly-on-privacy-focused-canton-network
- Lloyds and Archax complete the UK’s first tokenised deposit transaction on Canton
https://www.lloydsbankinggroup.com/media/press-releases/2026/lloyds/lloyds-tokenisation.html
- DTCC announces plans to tokenize DTC-custodied U.S. Treasury securities on Canton
https://www.dtcc.com/news/2025/december/17/dtcc-and-digital-asset-partner-to-tokenize-dtc-custodied-us-treasury-securities
- World Liberty Financial announces its intention to deploy USD1 on Canton
https://www.prnewswire.com/news-releases/the-canton-network-announces-intention-to-deploy-world-liberty-financials-usd1-stablecoin-advancing-institutional-grade-onchain-finance-302643063.html
- Circle goes live with a USDC-backed stablecoin on Canton
https://www.canton.network/blog/usdcx-now-live-on-canton-unlocking-private-and-composable-usdc-backed-settlement
- Franklin Templeton expands its Benji technology platform to Canton
https://www.coindesk.com/tech/2025/11/11/franklin-templeton-expands-benji-technology-platform-to-canton-network

From tokenized deposits to stablecoins and Treasuries, Canton is seeing momentum across regulated, institutional-grade on-chain finance. @Announcements

Where TradFi Meets DeFi

The gap between traditional finance and decentralized finance is closing.

Canton delivers institutional-grade privacy and control on a public, composable blockchain, resolving the trade-offs that once kept these worlds apart.

Global finance meets programmable rails. @Announcements