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