New Builder Video: Canton Developer Docs Walkthrough

The first video collaboration between the Canton Network and Canton Foundation YouTube channels is now live.

This is the first of several deeper DevRel walkthrough videos for builders and developers, focused on helping teams better understand how to build on Canton.

The video walks through the newly updated Canton developer documentation, including:
- A single entry point for docs
- App development learning paths
- SDKs and tools
- Built-in AI assistant support
- Developer resources for building, testing, and deploying

Watch the full walkthrough:

https://youtu.be/-AWep7dLSXo?si=iRF6Ag29Dca7QHPZ @Dev Announcements @Product Updates

Gate Enables USDCx on Canton Network

Gate has officially enabled USDCx deposits and withdrawals on the Canton Network, giving users another way to move and use USDCx across trading and asset management on the platform.

To support the launch, Gate has also opened multiple Canton ecosystem campaigns, with a combined reward pool valued at $150,000 in CC.

What is included

USDCx Deposit Challenge

Users who deposit USDCx via Canton Network can participate in a rewards campaign focused on stablecoin deposits and ecosystem activity.
https://www.gate.com/announcements/article/51351

CandyDrop

Gate has launched a CandyDrop campaign focused on CC spot trading and first-trade tasks, with additional CC rewards available.
https://www.gate.com/announcements/article/51356

Simple Earn

Gate Simple Earn has launched fixed-term CC products, giving users another way to participate through Gate’s wealth management products.
https://www.gate.com/announcements/article/51357

Official announcement

Read the full Gate announcement here:
https://www.gate.com/announcements/article/51355 @Announcements

CIP-0116 Approved: Featured App Locking

CIP-0116 has been approved, introducing CC locking requirements for Featured App designation on the Canton Network.

The goal is to make Featured App status more objective and market-based, while prioritizing applications that demonstrate committed capital and long-term alignment.

What this means for builders

Featured Apps must now meet clear onchain locking requirements to qualify for and maintain Featured App status.

This helps create a more transparent process for:
- Featured App eligibility
- Application prioritization
- Ongoing alignment with the network
- Governance around Featured App status

Builders and app teams can review the full proposal here:
https://github.com/canton-foundation/cips/blob/main/cip-0116/cip-0116.md @Product Updates

USDCx Support on Bybit

Bybit now supports USDCx deposits on the Canton Network.

Withdrawals are expected to be enabled tomorrow at 10:00 AM UTC.

This adds another access point for users moving assets through the Canton ecosystem.

Read the full announcement:
https://announcements.bybit.com/en/article/bybit-now-supports-usdcx-deposits-and-withdrawals-on-the-canton-network-bltdffca748ba41d8fe/ @Announcements

Those of you who are Integrating WalletConnect on Canton dApp, I have dropped a minimal demo showing how to integrate WalletConnect into a Canton Network dApp using the raw @walletconnect/sign-client.

https://github.com/Jatinp26/Canton-WalletConnect-demo/tree/main

Video coming soon...
@Canton Builder

GitHub - Jatinp26/Canton-WalletConnect-demo: A demo showing how to ...

A demo showing how to integrate WalletConnect into a Canton Network dApp. - Jatinp26/Canton-WalletConnect-demo

Builder Office Hours AMA Starts in 1 Hour

Are you curious about building on the Canton Network?

Have questions about development workflows, vibe coding on Canton, ecosystem tooling, or transitioning from Solidity?

Join Jatin Pandya and Jason-Michael Wilson in 1 hour for a live builder-focused session covering development, support, and what is ahead for Canton builders.

Join the session

📍 Discord Builder Stage
https://discord.com/channels/1379531004116471878/1486688897441464340

🔔 Reminder link
https://discord.com/events/1379531004116471878/1502355330129068083
- # There may also be a surprise announcement at the end 👀 || @Canton Builder @Events @Dev Announcements ||

Canton Builders Office Hours

Join us this Thursday for a live Builder Office Hours hosted by Jatin Pandya and Jason-Michael Wilson.

This session is focused on builders across the Canton ecosystem and will include discussion around development, ecosystem support, and what is ahead for Canton builders.

Details

📅 Thursday, May 14
🕘 9:00 AM EST / 1:00 PM UTC
📍 Discord Builder Stage: https://discord.com/channels/1379531004116471878/1486688897441464340
🔔 Reminder: https://discord.com/events/1379531004116471878/1502355330129068083

We hope to see builders, developers, and ecosystem teams there.
||@Canton Builder @Product Updates @Events ||
- # There may also be a surprise announcement at the end 👀

For Builders: Development Discussions Moving to the Forum

If you are building on the Canton Network, we are shifting app development questions and technical discussions to the Canton Forum.

This will serve as your primary hub for collaboration and app dev support among Canton builders, making it easier to track conversations, share knowledge, and build in public.

Going forward, please direct:
- App development questions
- Technical discussions
- Implementation feedback
- Collaboration requests

Join the forum:
https://forum.canton.network/ @Canton Builder @Announcements @Dev Announcements

Hey @Canton Builder
New Release for Canton Builder MCP to have Extended Info on WalletConnect Integration for Canton Guide.

Check it here: https://github.com/Jatinp26/Build-on-Canton-MCP

What's this? (for new builders here)
When developers use AI e.g Claude to learn Canton, they often get recommended deprecated documentation links. This Local MCP Integration solves that. It provides a curated, remotely updated knowledge base covering Canton's Dev Stack and Guide Devs using Claude 0 to 100.

The server fetches its knowledge base from this repo on startup, then caches it locally. If and when we push an update e.g WalletConnect, every MCP user gets it automatically on their next Claude restart, no manual pulls needed.

Seven Integrations in Six Weeks

A new breakdown from StakeCraft highlights recent development across the Canton Network.

In a six-week period, updates include:
- Bank deposit settlement
- Custody-native lending
- SMB credit distribution
- Cross-chain interoperability across 165 blockchains
- AI-powered smart contract audits
- Reported network activity reaching $8T in monthly settled value
The article provides a detailed look at how these components are coming together across the network.

See the full article:
https://x.com/i/status/2051651374719328473 @Announcements @Product Updates

Canton’s Privacy Model

Canton approaches privacy differently from most blockchains.

On the Canton Network, transaction data is only visible to the parties involved. The Global Synchronizer enables atomic settlement across applications without exposing details to uninvolved participants.

Participants choose what data to share, with whom, and under what conditions.

For regulated financial markets, this is what makes the difference between infrastructure institutions can actually use and infrastructure they cannot. @Announcements

Image available on Discord

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

Image available on Discord

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

Image available on Discord

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

Image available on Discord

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

Image available on Discord

Image available on Discord

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

Image available on Discord

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

Image available on Discord

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