The Canton Protocol Development Fund is funded by 5% of future CC emissions. It exists to support builders, infrastructure, and ecosystem development. Grants are available for developers building applications, tooling, and infrastructure on Canton. The process is governed through the Foundation and reported quarterly. If you have an idea for what should be built on Canton, the PDF is the place to start.

Every smart contract on Canton runs on Daml and every Daml contract has three roles that control who can do what. Signatories: the parties whose authority is required for the contract to exist. A contract cannot be created or archived without all signatories agreeing. This is the trust anchor. Observers: parties who can see the contract but cannot modify it. They have read access, not write access. Visibility without control. Controllers: parties who can exercise choices on the contract, triggering state changes. But only within the boundaries the signatories defined. This three-role model is how Canton enforces authorization at the contract level.

CIP-0112 has been approved: Canton Network Token Standard V2. This is a major upgrade to the CIP-0056 token standard that governs how assets are issued, transferred, and settled across @CantonNetwork. V2 introduces improvements across privacy, performance, and compatibility with traditional financial accounting. What changes: → Privacy-enhanced batch settlement: Parties in a multi-leg trade only see their own legs, not the full settlement → Accountable holdings: The new Account model supports multi-tier custody chains, enabling traditional finance workflows on-chain → Committed allocations and iterated settlement: Assets can be locked to an app or protocol for prefunded trading, with settlement occurring repeatedly without re-authorization → Improved user flows: Traders authorize a settlement with a single signature through their wallet → EventLog for transaction parsing: Standardized event emission for wallets, exchanges, and apps → Full backwards compatibility with V1: Apps, assets, and wallets can upgrade independently The V2 standard is designed to bridge TradFi settlement workflows and DeFi composability on the same infrastructure without splitting the on-chain ecosystem. Approved June 12, 2026.

Here is what validators need to prepare for Canton Protocol 35. Minimum Splice version: 0.6.5. If you are not running this version, your node will not participate in the Protocol 35 upgrade. Confirm your version now. The upgrade uses a Logical Synchronizer mechanism. The old and new protocol versions coexist during the transition. Transactions continue processing. Once all validators confirm, the cutover happens seamlessly. Validators do not need to coordinate downtime. But they do need to be on the correct Splice version before the TestNet LSU window opens.

The @ETHGlobal New York hackathon starts in 24 hours. Canton Foundation's $10,000 bounty is live across four tracks, Private DeFi, TradFi & RWA, and Payments & Agentic Commerce. @JPandya26, Amanda Martin, @Viv_Diwakar, and @BenStolman will be at the Canton booth all weekend.