Canton Ecosystem Intelligence

Scan 2026-09-20 05:38 UTC · 235/235 cards · Why · Grounding · UI how

Reference · SDK Daml 713 open (534 >1yr) · Canton v3.5.18 (2026-09-17) · Splice 0.8.3 ·

235 proposals · choose a Focus queue, then narrow by Action

Focus

Intelligence

Showing

Approval chains

Every proposal needs the same ⅔ Super-Validator vote — but on two different tracks (19 technical · 214 economics · 2 collision)

Why this matters: Whether a proposal succeeds is decided less by its code than by which track it travels and who controls that track. Technical merit is won in CIP working groups; CC economics is won by traffic, locking, and Featured-App rewards. Both are ratified by the same Super Validators — so the same voting bloc that judges a standard also controls the money. Reading this tells you where a given proposal will actually be won or lost, and where DA's SDK influence is strong (standards) versus exposed (economics it doesn't control).

What you get: Use it to route your effort: champion standards on the technical track, watch the economics track for reward-driven decisions that bypass technical review, and open the collision set first — that's where a technical change is really an economics decision wearing a CIP.

Filter cards by track (counts from cards.json)

Filter by track below — click a chip or row to show only those cards. Clear returns to the Focus queue.

Tracks What each track means

How each track runs (step by step)

A · Technical merit

Idea → cip-discuss
Draft CIP PR → WG review
SV sponsor + endorser
⅔ SV vote
Implementation (DA OSS veto on core)
Final when ⅔ adopt on-chain

B · CC economics

Build app → generate traffic
Lock CC (CIP-0116)
Apply Featured App
Same ⅔ SV vote
Traffic-weighted rewards (CIP-0104)
Reinvest / lock more (flywheel)

Collision Read these first

2 collision tags + 2 FA-without-tech-review signals (Decision Health) — hypotheses, not verdicts.

Detection matrix

CC emission split (post CIP-0096) — why economics dominates

~62% Featured Apps · CIP-0104 ~20% Super Validators · CIP-0105 ~15% Users · CIP-0104 / mint schedule 5% Dev Fund · CIP-0082 / CIP-0100 0% Validator liveness · CIP-0096

Citing

57 SVs CIP-0104 CIP-0116 CIP-0105 CIP-0096 CIP-0082 CIP-0100 proposals/ Trust grounding

What is known vs what is assumed

3 cited discrepancies (challengeable) · 79 open hypotheses

Each of these 235 proposals is scored against two fixed references: the DA ownership map (surfaces DA alone maintains — Daml, Canton, Splice) and the two approval tracks that share one ⅔ Super-Validator vote (technical merit vs CC economics). A tag appears when proposal text diverges from that map, or when the money path and the merit path look misaligned. Every tag is cited and data-driven — not 100%, and fair to challenge. “Know” = tags already attached to classified cards with linked sources. “Assume” = timing / keyword heuristics still open to falsification.

Cited · data-driven · not 100% · challenge freely

Click a row to isolate its cards. The filter banner states what the tag means and what to do next — including clearing a bad match.

Know Cited on the cards

3 of 235 cards carry a cited discrepancy tag; 21 already have a proposed next action.

Assume Hypotheses to challenge

79 heuristic signals still open to challenge — mostly community gap-filling, which is common in this corpus, not by itself an alarm.

Sources

Classified cards in this dashboard · Decision Health heuristics on CIP/grant text · cited, not 100% — challenge freely

Citing

Trust grounding Why Detection matrix Grounding

Patterns

Where pressure is building

This scan settled on 5 signals across 4 lenses (Governance, Structural, People, Surface / ops) — the ones with measurable magnitude, after dropping redundant metrics. 3 rated strong. The loudest right now: 16.2× — Proposal volume is grant-weighted, not standards-weighted. Each card leads with the number, then what it implies, then what would confirm or break it. Cross lenses to act — a structural backlog only becomes a to-do once a People signal names who can clear it.

Governance Structural People Surface / ops weak notable strong

What each lens means

Governance — who pays & what CI enforces (DA self-fund, board rules)
Structural — volume & delivery pressure (grants vs CIPs, milestones)
People — who can move both tracks (bridges, cohorts)
Surface / ops — changes that skip CIP paper trails (configs, binaries)

Governance

15/49 DA-* proposal files

Dev Fund partially routes DA operating spend

Foundation governance pays for core DA maintenance. Code authority stays with DA; budget authority partially sits on the board.

DA-* share31% proposals/49 md

Reads with Pair with Structural grant volume: the board is funding both community gaps and DA ops — same pipeline, different owners.

Confirms / breaks New DA-* proposals without matching CIP / OSS ownership notes.

Filename parse on /proposals/*.md.

Structural

16.2× Dev Fund open items per CIP open item

Proposal volume is grant-weighted, not standards-weighted

SDK impact reaches the ecosystem through funded apps far more than through CIP text. Roadmap intake and review capacity should be weighted toward grant deliverables, not standards throughput.

canton-dev-fund open390 cips open24

Reads with Pair with Governance DA self-funding: volume is grant-weighted and part of that volume is DA's own ops spend.

Confirms / breaks Wallet, custody, explorer, and integration tooling landing as grants ahead of any CIP.

Live open-item counts on canton-foundation/canton-dev-fund and /cips.

Structural

41·86 weak proposals · stale milestone issues

Delivery risk: artifact milestones meet stale execution issues

Promises in proposal markdown and tracking in issues diverge. Many milestone issues are one grant's checklist — the risk signal is weak framing plus stale milestone issues, not the raw issue count.

weak / artifact41/48 milestone-titled158 stale ≥30d86

Reads with Pair with People bridges: the same authors often sit on both the proposal and the delivery issue.

Confirms / breaks Milestone issues that gain comments after ≥30d quiet, or scope cuts.

Proposal milestone keywords + title-framed Dev Fund issues.

People

9 CIP↔grant bridge authors

A small set of authors bridges standards and grants

These authors are the highest-leverage relationship map for SDK direction: one conversation reaches both the standards track and the funded-app track.

bridgesbame-da, davidrichards-da, hilarl, hythloda

Reads with Pair with Structural signals: bridges are who to call about grant volume and delivery risk.

Confirms / breaks Their next PRs — earliest indicator of where both tracks move next.

Authors with PRs on both cips and canton-dev-fund.

Surface / ops

2026-09-20 last push · configs-runtime

Validator ops surface stays active without CIPs

Config/binary changes can force SDK and docs follow-ups with no governance paper trail. This surface needs monitoring even though it never produces a CIP.

configs-runtime2026-09-20 configs2026-09-17 binaries2026-09-14

Reads with Pair with Governance: ops moves can land without CIP text — watch CI and board rules separately from this surface.

Confirms / breaks Config or binary bumps that imply a version note or SDK compatibility change.

Push timestamps on SV ops repos.

Sources

Live repo counts · classified cards · stored pull corpus · 49/49 proposals md · 179 issues · 4 workflows

Citing

Detection matrix Data pull map proposals/ cips

Predictions

Near-term watch list

Each row names a measured trigger and the next artifact that would confirm it. Corpus stays on disk for Admin reference — citations here point at GitHub.

Dev Fund grant proposers

390 open Dev Fund items vs a thin CIP pipeline

→ Wallet, custody, explorer, and integration tooling asks

Confirm by New grant PRs in those categories on canton-dev-fund

SV / ops maintainers

Push on configs-runtime dated 2026-09-20

→ Validator config or binary bumps → docs / SDK version notes

Confirm by Follow-up commits or release tags on configs-runtime

pedrodneves, tkatrichenko, hythloda

Highest recent PR counts across scanned surfaces

→ Their next PRs set near-term board direction

Confirm by New PRs from these handles reaching Project 3 / 5

Dev Fund Milestones board

Funded vs aspirational split lives on the board, not in PRs

→ Items moving to funded / in-progress before any CIP surfaces

Confirm by Status changes on Project 5

Sources

Org snapshot · stored deep corpus · board status

Citing

Detection matrix Why Dev Fund issues

Who is shaping this

Who moves the roadmap — and who to talk to first

Why this matters: SDK strategy is won through people, not only CIPs: the orgs concentrating contribution, authors who bridge standards and grants, and SIGs drawing the most energy right now.

What you get: 5 org cohorts · 8 CIP↔grant bridges · 8 hot SIGs. Start with bridges (one conversation reaches both tracks), then Digital Asset / daml-tooling. Click a name or SIG to filter their cards.

Inferred cohorts · cited where possible · not confirmed · challenge freely

Where contribution concentrates

Larger cohort + tighter SIG focus = one alignment conversation propagates farthest.

global-synchronizer-scaling

10 handles cluster here, concentrated in global-synchronizer-scaling. Alignment with this cohort propagates across those workstreams fastest.

Do Already DA-connected — keep the loop tight; their PRs preview DA direction.

2 handles cluster here. Alignment with this cohort propagates across those workstreams fastest.

Do Filter their cards and open a direct line before their SIG decisions harden.

1 handles cluster here. Alignment with this cohort propagates across those workstreams fastest.

Do Filter their cards and open a direct line before their SIG decisions harden.

1 handles cluster here. Alignment with this cohort propagates across those workstreams fastest.

Do Filter their cards and open a direct line before their SIG decisions harden.

1 handles cluster here. Alignment with this cohort propagates across those workstreams fastest.

Do Filter their cards and open a direct line before their SIG decisions harden.

CIP ↔ grant bridges — highest leverage

8 authors write on both the standards track and the funded-grant track — highest-leverage outreach on this page.

Do Open SDK outreach here first — signal travels both directions.

Hot SIG cohorts

Most distinct authors touching the SIG right now — where docs / SDK support pays back fastest.

Sources

GitHub authors + inferred org attribution · SIG labels on PRs · inferred, not confirmed — challenge freely

Citing

Trust grounding Advisor why

Grounding · Methods · Spec

grounding

Trust grounding (citation map) Cited facts & data sources (trust-v8) CIPs registry Dev Fund proposals Funded proposals (/proposals) Governance workflows Project 3 — Incoming Project 5 — Milestones Canton Foundation (57 SVs)

methods

Data pull map Why this exists How the tool reasons Decision Health patterns HITL teach-back

spec

Product contract (SPEC)

Cards by Focus

Each card is one Foundation proposal. Focus filters which pile you see; the verb on the card is a proposed next step for human review — not an order.

Alignment risk

High alignment or architecture risk — decide first (HITL) · 3 cards

GRANT CC economics token-asset-standards champion-confirmed Respond ⚡ foreign architecture

ERC-20 Middleware for CIP-56 Tokens

PR #453 · Eunoia-cym unverified · 2026-06-11 · 💬 6 (proposed — review)

Summary: The proposal introduces an ERC-20 middleware that allows EVM wallets and dapps to interact with Canton-native tokens, potentially expanding the ecosystem but requiring careful consideration of privacy and authorization.

privacy: at risk auth: neutral comp: preserved

⚠ privacy: Public-state assumptions of ERC-20 could undermine Canton's privacy guarantees.

Enables

Enables interoperability with Ethereum-based wallets and dapps, potentially expanding the user base.

Costs

Risk of compromising Canton's privacy model due to public-state assumptions in ERC-20.

Proposed action

Respond — Engage in discussion to ensure alignment with Canton's architectural principles and security standards.

Suggested why

The proposal may introduce architectural conflicts with Canton's privacy and authorization models.

TTP: P2, P3 Alignment: medium Affects: insufficient data SIG: direct

⚠ suggested risk note: The proposal may introduce architectural conflicts with Canton's privacy and authorization models.

3 sources

ERC-20 semantics may conflict with Canton's authorization mechanisms. — PR body
Public-state assumptions of ERC-20 could undermine Canton's privacy guarantees. — PR body
PR #453 metadata (title, labels, comments=6) — https://github.com/canton-foundation/canton-dev-fund/pull/453

View on GitHub →

GRANT CC economics token-asset-standards Track ⚡ foreign architecture

Canton <-> Solana/EVM bridge proposal

PR #13 · GotFly unverified · 2026-02-21 · 💬 3 (proposed — review)

Summary: The proposal introduces a cross-chain bridge solution that could enhance Canton's interoperability with other blockchain networks, potentially increasing its utility and adoption. However, it relies on external infrastructure (Asterizm) which may introduce additional complexity.

privacy: at risk auth: neutral comp: at risk

⚠ privacy: The bridge introduces an external architecture that may compromise Canton's privacy model by integrating with account-based systems like Solana and EVM networks.

⚠ composability: The bridge may introduce composability issues due to differences in asset representation and transaction models between Canton's UTXO-based system and account-based systems like Solana/EVM.

Enables

Enables cross-chain interoperability with Solana, Ethereum, and other EVM networks.

Costs

Potential weakening of privacy and composability due to integration with foreign architectures.

Proposed action

Track — Monitor the development and implementation of this bridge to understand its impact on privacy, authorization, and composability within the Canton ecosystem.

Suggested why

Polyglot/multi-VM mention — Daml SDK does not yet support this VM; check for assumed SDK support (gap) and parallel tooling (fragmentation).

TTP: P2, P3 Alignment: medium Affects: insufficient data SIG: direct

⚠ suggested risk note: Polyglot/multi-VM mention — Daml SDK does not yet support this VM; check for assumed SDK support (gap) and parallel tooling (fragmentation).

3 sources

Proposal introduces a bridge solution for Canton — PR body
Asterizm provides the cross-chain messaging infrastructure — PR body
PR #13 metadata (title, labels, comments=3) — https://github.com/canton-foundation/canton-dev-fund/pull/13

View on GitHub →

GRANT CC economics Track ⚡ foreign architecture

Unified Liquidity Hub Proposal

PR #103 · Randynamic unverified · 2026-03-19 · 💬 1 (proposed — review)

Summary: The proposal introduces a new liquidity hub and stablecoin framework, which could require updates to the SDK for integration with Daml Finance KYC-bound Custody Vaults and EVM Virtual Blockchain routing contract. Source: PR body.

privacy: at risk auth: neutral comp: at risk

⚠ privacy: Introduces EVM Virtual Blockchain routing contract, which may conflict with Canton's privacy model.

⚠ composability: Introduces a new liquidity hub and stablecoin framework, which may require significant compositional changes in the ecosystem.

Enables

Enables regulated institutions to pool collateral and route liquidity to whitelisted DeFi protocols via a standardized CIP-56 compliant stablecoin.

Costs

Potential conflict with Canton's privacy model due to the introduction of an EVM Virtual Blockchain routing contract.

Proposed action

Track — Monitor the development of this proposal to understand its impact on the SDK and ecosystem alignment.

Suggested why

The proposal may introduce new features that could require alignment with existing Canton priorities.

TTP: P2, P3 Alignment: medium Affects: insufficient data SIG: direct

⚠ suggested risk note: The proposal may introduce new features that could require alignment with existing Canton priorities.

2 sources

Unified Liquidity Hub proposal — https://github.com/canton-foundation/canton-dev-fund/pull/103
PR #103 metadata (title, labels, comments=1) — https://github.com/canton-foundation/canton-dev-fund/pull/103

View on GitHub →

Attention

Needs eyes — may drift; pick an Action (Respond / Track / …) · 22 cards

GRANT CC economics daml-tooling Respond ⚡ filling DA gap

DamlCov test coverage tool proposal

PR #323 · mderka unverified · 2026-05-11 · 💬 5 (proposed — review)

Summary: The proposed DamlCov tool aims to enhance the testing capabilities of Daml smart contracts by providing unique features tailored for Daml's authorization model, UTXO-like state, and multi-party privacy semantics. It will integrate with existing Daml tooling and provide CI/CD pipeline support (source: PR body).

privacy: preserved auth: preserved comp: neutral

Proposed action

Respond — Engage with the author to discuss integration points and alignment with current SDK development goals.

Suggested why

The proposal needs to be aligned with the current SDK development roadmap.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal file added under /proposals/ — PR body
Milestones and funding amounts defined — PR body
PR #323 metadata (title, labels, comments=5) — https://github.com/canton-foundation/canton-dev-fund/pull/323

View on GitHub →

GRANT CC economics needs-champion Respond ⚡ filling DA gap

Compliance SDK for EVM Developers on Zenith

PR #621 · Noosphere-314 unverified · 2026-08-06 · 💬 2 (proposed — review)

Summary: The proposal introduces a Compliance Middleware SDK that enables Solidity developers to interact with Canton's compliance primitives, enhancing regulatory adherence in RWA workflows. This could lead to increased adoption of Canton's standards but requires careful integration to maintain architectural integrity.

privacy: neutral auth: at risk comp: neutral

⚠ authorization: Introduces ERC-20 semantics that may conflict with Canton's authorization model if not properly integrated.

Enables

Enables Solidity developers to leverage Canton's compliance primitives, potentially expanding the ecosystem.

Costs

May introduce authorization conflicts if not properly aligned with Canton's current standards and practices.

Proposed action

Respond — Engage the author to discuss alignment and potential integration strategies for the SDK within the existing ecosystem.

Suggested why

The proposal needs to be closely aligned with Canton's strategic roadmap and compliance standards.

TTP: P2, P3 Alignment: medium Affects: insufficient data SIG: direct

⚠ suggested risk note: The proposal needs to be closely aligned with Canton's strategic roadmap and compliance standards.

3 sources

Proposal introduces ERC-20 semantics — PR body
Aims to enhance regulatory compliance in RWA workflows — PR labels
PR #621 metadata (title, labels, comments=2) — https://github.com/canton-foundation/canton-dev-fund/pull/621

View on GitHub →

GRANT CC economics daml-tooling Champion ⚡ filling DA gap

Daml upgrade migration planner proposal

PR #91 · pmensik unverified · 2026-03-16 · 💬 22 (proposed — review)

Summary: The Daml Upgrade Migration Planner aims to automate and derisk smart contract upgrades on Canton, focusing on single-participant migration planning through JSON/Markdown output. It leverages existing Canton primitives without reinventing validation logic (source: PR body).

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Support the proposal as it enhances Daml upgrade processes and aligns with tooling priorities.

Suggested why

The proposal aligns with Canton's priorities but may require further clarification on follow-up opportunities.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Proposal introduces CLI tool for automating and derisking Daml upgrades — PR body
PR #91 metadata (title, labels, comments=22) — https://github.com/canton-foundation/canton-dev-fund/pull/91

View on GitHub →

GRANT CC economics canton-apis champion-confirmed Champion ⚡ filling DA gap

Canton Mobile SDK Proposal

PR #574 · sunstrike228 unverified · 2026-07-16 · 💬 16 (proposed — review)

Summary: The proposal introduces native Swift and Kotlin libraries for Canton, expanding the platform's reach to mobile devices. This aligns with the goal of increasing adoption by providing a more accessible development environment for iOS and Android users.

privacy: preserved auth: neutral comp: at risk

⚠ composability: Introducing platform-specific SDKs may fragment composability across different ecosystems.

Enables

Enables mobile app development on Canton, expanding its user base.

Costs

Potential fragmentation of the SDK ecosystem due to platform-specific implementations.

Proposed action

Champion — Champion this proposal to accelerate mobile app development on Canton.

Suggested why

The proposal aligns with Canton's priorities but requires further review to ensure it does not introduce significant architectural conflicts.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Proposal introduces native Swift and Kotlin libraries for Canton — PR body
PR #574 metadata (title, labels, comments=16) — https://github.com/canton-foundation/canton-dev-fund/pull/574

View on GitHub →

GRANT CC economics wallet-apps Approved Champion ⚡ filling DA gap

Wallet Gateway Reference Implementation

PR #109 · Stephan-da Digital Asset · 2026-03-19 · 💬 13 (proposed — review)

Summary: The proposal introduces a middleware that decouples signing services from application environments, potentially reducing SDK integration complexity and increasing security through standardized interfaces. Source: PR body.

privacy: preserved auth: preserved comp: neutral

Proposed action

Champion — Support the development of this reference implementation to enhance wallet interoperability and reduce onboarding friction for enterprises.

TTP: P2, P3 Alignment: none Affects: insufficient data SIG: direct

4 sources

Proposal introduces secure, vendor-neutral middleware — PR body
Enhances wallet interoperability and reduces onboarding friction for enterprises — PR body
PR #109 metadata (title, labels, comments=13) — https://github.com/canton-foundation/canton-dev-fund/pull/109
Author Stephan-da classified as DA (-da / known handle) — https://github.com/orgs/digital-asset/people

View on GitHub →

GRANT CC economics daml-tooling champion-confirmed Champion ⚡ filling DA gap

DAWE proposal for DAML tooling

PR #400 · ayanuali unverified · 2026-06-01 · 💬 10 (proposed — review)

Summary: The DAWE proposal aims to build an automated workflow evaluator for DAML, enhancing the ecosystem's tooling. This could improve developer experience and automation capabilities.

privacy: preserved auth: neutral comp: at risk

⚠ composability: The introduction of new tooling may introduce composability issues if not well-integrated with existing DAML workflows.

Costs

Potential integration challenges could arise from introducing a new automated workflow evaluator.

Proposed action

Champion — Champion the proposal to ensure it aligns with Canton SDK development goals and benefits the broader DAML community.

Suggested why

The proposal needs to be closely aligned with Canton's priorities to ensure it benefits the ecosystem.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal file added under /proposals/ — PR body
Milestones and funding amounts defined — PR body
PR #400 metadata (title, labels, comments=10) — https://github.com/canton-foundation/canton-dev-fund/pull/400

View on GitHub →

GRANT CC economics dapp-integration daml-tooling canton-apis Champion ⚡ filling DA gap

Denex Developer SDK for Canton

PR #238 · mgaare unverified · 2026-04-22 · 💬 9 (proposed — review)

Summary: The Denex Developer SDK aims to accelerate development by providing TypeScript types and Zod schemas from Daml contracts, a type-safe high-level SDK library, and tools for managing Canton LocalNets. This aligns with the goal of improving developer experience and reducing setup time (source: PR body).

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Evaluate and champion the proposal to integrate Denex Developer SDK into the Canton ecosystem.

Suggested why

The proposal needs to be aligned with Canton's development priorities and ensure it does not conflict with existing tools or initiatives.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Denex Developer SDK accelerates Canton app development — PR body
PR #238 metadata (title, labels, comments=9) — https://github.com/canton-foundation/canton-dev-fund/pull/238

View on GitHub →

GRANT CC economics dapp-integration daml-tooling champion-confirmed Champion ⚡ filling DA gap

Ginie English-to-DAML Dapp Builder

PR #123 · BlockXAI unverified · 2026-03-23 · 💬 7 (proposed — review)

Summary: Introduces a new tool for non-technical users to build and deploy DAML full-stack applications on Canton, enhancing adoption without requiring prior knowledge of DAML. (source: PR body)

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Champion Ginie's proposal as it aligns with the goal of increasing developer engagement and lowering the barrier to entry for new developers.

Suggested why

Polyglot/multi-VM mention — Daml SDK does not yet support this VM; check for assumed SDK support (gap) and parallel tooling (fragmentation).

TTP: P2, P3 Alignment: medium Affects: insufficient data SIG: direct

⚠ suggested risk note: Polyglot/multi-VM mention — Daml SDK does not yet support this VM; check for assumed SDK support (gap) and parallel tooling (fragmentation).

3 sources

Ginie transforms plain English into fully compiled, deployed Daml Full Stack Apps on Canton — PR body
Acquired 1500 Canton Passionate Builders on platfrom — PR body
PR #123 metadata (title, labels, comments=7) — https://github.com/canton-foundation/canton-dev-fund/pull/123

View on GitHub →

GRANT CC economics daml-tooling champion-confirmed Champion ⚡ filling DA gap

CCpedia Expands Knowledge Infrastructure

PR #439 · 0xFearless-1 unverified · 2026-06-09 · 💬 6 (proposed — review)

Summary: The proposal aims to expand Canton's knowledge infrastructure, which could enhance the SDK by providing more comprehensive and open-source tools for developers. This aligns with the goal of fostering a broader community adoption (source: PR body).

privacy: preserved auth: neutral comp: at risk

⚠ composability: Expanding the knowledge infrastructure could potentially increase complexity and impact composability if not carefully managed.

Costs

The expansion of the knowledge infrastructure may introduce additional maintenance burdens.

Proposed action

Champion — Champion the proposal to ensure it receives necessary support and resources within the Canton ecosystem.

Suggested why

The proposal is aligned with Canton's priorities but requires further validation to ensure it does not conflict with existing plans.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

ccpedia aims to expand Canton's live knowledge infrastructure — PR body
PR #439 metadata (title, labels, comments=6) — https://github.com/canton-foundation/canton-dev-fund/pull/439

View on GitHub →

GRANT CC economics canton-apis needs-champion Champion ⚡ filling DA gap

Open-source Rust SDK for Canton ecosystem

PR #525 · kevmuko unverified · 2026-07-10 · 💬 5 (proposed — review)

Summary: The proposal aims to integrate a production-proven Rust SDK into the official Canton toolchain, enhancing interoperability and client diversity. Source: PR body.

privacy: preserved auth: neutral comp: at risk

⚠ composability: Integrating a new SDK may require careful consideration to maintain composability with existing tools and standards.

Enables

Enables Rust developers to contribute to the Canton ecosystem, potentially expanding user base.

Costs

Requires coordination with existing toolchain and conformance testing to ensure seamless integration.

Proposed action

Champion — Champion this proposal to align with Canton's priorities and enhance ecosystem diversity.

Suggested why

The proposal aligns with Canton's priorities but requires a champion to move forward.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal file added under /proposals/ — PR body
Milestones and funding amounts defined — PR body
PR #525 metadata (title, labels, comments=5) — https://github.com/canton-foundation/canton-dev-fund/pull/525

View on GitHub →

GRANT CC economics token-asset-standards needs-champion Champion ⚡ filling DA gap

Talwex Proposes DeFi Composability Standard for Canton

PR #740 · arno-burnuk-talwex unverified · 2026-08-27 · 💬 5 (proposed — review)

Summary: The proposal aims to introduce composable DeFi primitives on Canton, enhancing liquidity and adoption. It aligns with the goal of fostering a robust financial products ecosystem.

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Champion this initiative to support the development of a secure and composable DeFi ecosystem on Canton.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Proposal aims to introduce composable DeFi primitives on Canton — PR body
PR #740 metadata (title, labels, comments=5) — https://github.com/canton-foundation/canton-dev-fund/pull/740

View on GitHub →

GRANT CC economics daml-tooling needs-champion Champion ⚡ filling DA gap

Visual Debugging Plugin for Daml on Canton

PR #494 · smehrjerdian unverified · 2026-07-04 · 💬 4 (proposed — review)

Summary: The proposal introduces a visual debugging plugin that enhances the developer experience by providing transaction debugging, structured test output with assertion diffs, and a searchable debug log panel. This aligns with improving developer tooling as per Foundation priorities (PR body).

privacy: preserved auth: neutral comp: at risk

⚠ composability: Introducing a new debugging tool may fragment existing developer workflows and tools, but it aims to enhance them (PR body).

Costs

The introduction of a new plugin could potentially lead to fragmentation if not well-integrated with existing Daml development practices.

Proposed action

Champion — Engage with the Tech & Ops Committee to champion this proposal for its potential to significantly improve Daml development workflows.

Suggested why

The proposal aligns with Canton's priorities but requires further discussion to ensure full alignment.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal file added under /proposals/ — PR body
Milestones and funding amounts defined — PR body
PR #494 metadata (title, labels, comments=4) — https://github.com/canton-foundation/canton-dev-fund/pull/494

View on GitHub →

GRANT CC economics daml-tooling champion-confirmed rfp-19:dpm-components Champion ⚡ filling DA gap

Versioned Debug Info for Daml

PR #743 · djolertrk unverified · 2026-08-28 · 💬 4 (proposed — review)

Summary: The proposal aims to enhance debugging capabilities in Daml by introducing a versioned debug metadata format and supporting compiler features. This will improve developer experience and error resolution, aligning with the DAML tooling roadmap.

privacy: preserved auth: neutral comp: neutral

Proposed action

Champion — Champion this initiative to integrate enhanced debugging tools into the DAML ecosystem.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Proposal aims to improve debugging in Daml — PR body
PR #743 metadata (title, labels, comments=4) — https://github.com/canton-foundation/canton-dev-fund/pull/743

View on GitHub →

GRANT CC economics canton-apis Champion ⚡ filling DA gap

Nexus Framework for TypeScript SDKs

PR #15 · mehmetkr-31 unverified · 2026-02-22 · 💬 3 (proposed — review)

Summary: The Nexus Framework aims to simplify Daml development by providing a type-safe, isomorphic TypeScript SDK that integrates seamlessly with React and Next.js. It leverages the Canton JSON Ledger API and official Daml codegen output (source: PR body).

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Champion Nexus Framework for its potential to enhance developer experience and adoption of Canton.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Nexus Framework aims to simplify Daml development — PR body
PR #15 metadata (title, labels, comments=3) — https://github.com/canton-foundation/canton-dev-fund/pull/15

View on GitHub →

GRANT CC economics dapp-integration daml-tooling needs-champion Champion ⚡ filling DA gap

CantonTrace Debugging Platform Proposal

PR #185 · justmert unverified · 2026-04-10 · 💬 3 (proposed — review)

Summary: The proposal introduces a comprehensive debugging and security analysis platform for Canton Network, enhancing developer experience by filling gaps identified in the 2026 Developer Experience Survey. (source: PR body)

privacy: preserved auth: neutral comp: at risk

⚠ composability: Potential risk to composability if the tool becomes a dependency for contract development, limiting flexibility.

Costs

The introduction of CantonTrace may increase maintenance burden and could potentially limit composability if it becomes an essential part of the development process.

Proposed action

Champion — Champion this proposal to enhance Canton's developer tooling ecosystem.

Suggested why

The proposal aligns with CIP-0082 but may require further alignment with broader Canton priorities.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

4 sources

Proposal file added under /proposals/ — PR body
Milestones and funding amounts defined — PR body
Alignment with Canton priorities described — PR body
PR #185 metadata (title, labels, comments=3) — https://github.com/canton-foundation/canton-dev-fund/pull/185

View on GitHub →

GRANT CC economics daml-tooling needs-champion Champion ⚡ filling DA gap

DPM Ledger Operations Suite Proposal

PR #520 · rose2221 unverified · 2026-07-09 · 💬 3 (proposed — review)

Summary: The proposal introduces a suite of DPM components that enhance ledger operations and testing without altering Canton's core functionality, aligning with the Foundation's goals for community-built tooling.

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Engage with the author to champion this proposal within the Tech & Ops Committee.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

The proposal introduces a suite of DPM components. — PR body
No changes to Canton internals are made. — PR body
PR #520 metadata (title, labels, comments=3) — https://github.com/canton-foundation/canton-dev-fund/pull/520

View on GitHub →

GRANT CC economics needs-sig-label needs-champion Champion ⚡ filling DA gap

Rubic Cross-Chain Aggregation for Canton

PR #483 · axtezy unverified · 2026-06-23 · 💬 2 (proposed — review)

Summary: The proposal introduces cross-chain swap functionality via Rubic, enhancing Canton's DeFi capabilities without requiring individual DEX integrations. This could attract more developers and projects to the platform (source: PR body).

privacy: preserved auth: neutral comp: preserved

Proposed action

Champion — Engage with the champion to understand the technical details and alignment with Canton's strategic priorities.

Suggested why

The proposal needs to be reviewed for alignment with Canton's strategic priorities.

TTP: P2, P3 Alignment: medium Affects: insufficient data SIG: direct

⚠ suggested risk note: The proposal needs to be reviewed for alignment with Canton's strategic priorities.

3 sources

Proposal introduces Rubic cross-chain swap aggregator — https://github.com/canton-foundation/canton-dev-fund/pull/483
Rubic integration enhances Canton's DeFi capabilities — PR body
PR #483 metadata (title, labels, comments=2) — https://github.com/canton-foundation/canton-dev-fund/pull/483

View on GitHub →

GRANT CC economics daml-tooling Champion ⚡ filling DA gap

Formal verification for DAML standards

PR #12 · zakaryaeboudittv unverified · 2026-02-21 · 💬 2 (proposed — review)

Summary: The proposal aims to provide formal verification models for specific DAML standards, which can enhance the reliability and security of SDK-based applications. This aligns with the ongoing efforts to improve the robustness of DAML ecosystem tools (source: PR body).

privacy: preserved auth: neutral comp: neutral

Proposed action

Champion — Support the proposal to ensure alignment with DA's strategic goals for formal verification and tooling.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal aims to deliver formal verification for specific DAML standards. — PR body
Scope is limited to CIP-0056 and CIP-0047. — PR body
PR #12 metadata (title, labels, comments=2) — https://github.com/canton-foundation/canton-dev-fund/pull/12

View on GitHub →

GRANT CC economics daml-tooling Champion ⚡ filling DA gap

Canton Builder Navigator for ecosystem tools

PR #88 · deepthi-2531 unverified · 2026-03-15 · 💬 2 (proposed — review)

Summary: The proposal aims to enhance developer onboarding and tool discovery, improving the overall developer experience by providing a structured catalog with machine-readable manifests and AI-assisted search capabilities. This aligns with the need for better ecosystem management as Canton grows (PR body).

privacy: preserved auth: neutral comp: at risk

⚠ composability: Risk of fragmentation if not aligned with existing SDK practices.

Costs

Potential for fragmentation if the tooling is not well-integrated into the existing ecosystem.

Proposed action

Champion — Support this initiative to improve developer onboarding and tool discovery in the Canton ecosystem.

Suggested why

The proposal is scoped as shared ecosystem infrastructure and not a commercial product, aligning with Canton's open-source ethos.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal requests funding for Canton Builder Navigator — PR body
Provides a structured catalog with machine-readable manifests and AI-assisted search capabilities — PR body
PR #88 metadata (title, labels, comments=2) — https://github.com/canton-foundation/canton-dev-fund/pull/88

View on GitHub →

GRANT CC economics daml-tooling dar-app-management champion-confirmed Champion ⚡ filling DA gap

Decompiler for DAR artifacts

PR #661 · ds-jacano unverified · 2026-08-21 · 💬 2 (proposed — review)

Summary: The proposal aims to fund a Daml-LF decompiler, enhancing the ability of validators and auditors to inspect deployed DAR artifacts. This could improve security review processes but requires coordination with existing SDK tooling.

privacy: neutral auth: neutral comp: preserved

Proposed action

Champion — Support the development of an open-source Daml-LF decompiler to enhance DAR artifact inspection capabilities.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

2 sources

Funds a Daml-LF decompiler — PR body
PR #661 metadata (title, labels, comments=2) — https://github.com/canton-foundation/canton-dev-fund/pull/661

View on GitHub →

GRANT CC economics wallet-apps Track ⚡ filling DA gap

Agentic Wallet with ZK Verification on Canton

PR #92 · ch4r10t33r unverified · 2026-03-16 · 💬 20 (proposed — review)

Summary: The proposal introduces significant SDK integration points for agentic payment workflows and zero-knowledge proofs, enhancing the financial capabilities of Canton's ecosystem. Source: PR body.

privacy: preserved auth: at risk comp: neutral

⚠ authorization: Phone number-based authentication introduces a new authorization mechanism that may require careful integration to preserve existing security standards.

Costs

Phone number-based authentication may increase the complexity of authorization management.

Proposed action

Track — Monitor the progress and impact of the proposed infrastructure to ensure alignment with Canton’s privacy-preserving principles and composability standards.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: direct

3 sources

Proposal introduces agentic wallet infrastructure with ZK verification. — PR body
Milestones include phone number auth and risk model integration. — PR body
PR #92 metadata (title, labels, comments=20) — https://github.com/canton-foundation/canton-dev-fund/pull/92

View on GitHub →

GRANT CC economics dapp-integration daml-tooling Core/ready for vote Track ⚡ filling DA gap

Tenderly Simulation for Daml on Canton

PR #481 · nebojsa94 unverified · 2026-06-22 · 💬 4 (proposed — review)

Summary: The proposal introduces a simulation environment for Daml contracts running on Canton, which could enhance developer experience and testing capabilities. However, it is an external integration that may introduce additional complexity to the SDK ecosystem.

privacy: neutral auth: neutral comp: at risk

⚠ composability: Integrating an external simulation tool may introduce compatibility issues with the current SDK and ecosystem tools.

Costs

The integration of Tenderly could potentially lead to increased maintenance overhead due to additional dependencies.

Proposed action

Track — Monitor the progress of the Tenderly Simulation integration to ensure alignment with DA's architectural principles and SDK development goals.

TTP: P2, P3 Alignment: low Affects: insufficient data SIG: adjacent

2 sources

Proposal introduces simulation environment for Daml contracts on Canton — PR body
PR #481 metadata (title, labels, comments=4) — https://github.com/canton-foundation/canton-dev-fund/pull/481

1 source

Classification failed — no LLM grounding applied — https://github.com/canton-foundation/cips/pull/262

View on GitHub →

0.7.0 · 2026-07-30

[release] Release 0.7.0 (#6623) Tag 0.7.0 Commits: 0 · files: 0

Tag / notes →