RFC: Canton Bindings — multi-language SDKs + JWT/OIDC + pre-flight profiler

App Development
, , ,
1

Hi everyone, sharing a heads-up on a Dev Fund RFC currently active
on grants-discuss, in case the community here would like to weigh in.

Following the Q1 2026 Developer Experience survey results that @dunebuggie
shared earlier this year, my co-founder Anirudh Singh and I (HackTour India,
https://x.com/HackTourIND) have scoped a proposal for the three runtime-layer
gaps the survey called out that no current PR addresses:

  • Typed Client SDK + Code Generator for languages beyond TypeScript
    (Python, Java/Kotlin, Rust, Go)
  • JWT/OIDC authentication middleware for TradFi/Hybrid teams
  • Pre-flight transaction byte-size and Canton Coin cost profiler

Working name: Canton Bindings. Deliberately complementary to Cantool (#77),
CantonTrace (#185), PartyLayer (#9), and Wallet Gateway (#109), with a
Cantool plugin in Milestone 4 so it integrates cleanly with Eric’s CLI.

Active discussion thread on grants-discuss:
https://lists.sync.global/g/grants-discuss/topic/rfc_canton_bindings/119439952

Full design doc (architecture, milestones, alignment table, risk register):
https://github.com/jatinsahijwani/canton-bindings/blob/289c8610e4bf3447b1221ba610c184ed8b74593d/README.md

Would especially love input from folks in the Daml Tooling, DAR Lifecycle,
dApp Integration, and Canton APIs SIGs, and anyone building TradFi/Hybrid
apps who’s hit the JWT pain firsthand. Discussion in either venue welcome.

Thanks!
— Jatin

2

Hey @Jatin_Sahijwani

Good to see the PR idea, Kindly please make the PR to dev fund and we will have daml-tooling SIGs to review and take a deep look into it as well followed by security review.

Please share the PR Link once made.

Thanks,
Jatin Pandya,
DevRel Manager, Canton Foundation

3

Quick update before opening the PR : after reading the full proposals/
directory in canton-dev-fund, we’re tightening scope to avoid overlap
with existing in-flight work:

  • Dropping Go (Noders’ go-daml + go-wallet-daml already cover this)
  • Dropping TypeScript (DA’s dApp SDK proposal covers this)
  • Dropping Python (DAZL exists; Noders has already upstreamed
    protobuf v3 + OpenAPI support)

Refined scope: Java/Kotlin SDK + Rust SDK + JWT/OIDC Auth Kit
(Keycloak/Auth0/Azure AD/Okta) + Pre-Flight Profiler + Cantool plugin.

This focuses us on the institutional JVM cohort (the 83% TradFi/Hybrid
respondents in the Q1 survey) and the auth/cost-estimation gaps that
no existing proposal addresses. Filing the PR with this refined scope
later today.

— Jatin

4

Here is the PR Link that we have made :

The PR was auto-closed by the bot for the standard external-proposer
Champion requirement (CIP-0100). Proposal content is intact; bot auto-applied
the daml-tooling label which is the correct routing.

Thanks!
— Jatin

5

Hi Jatin,

PR opened as you suggested:

The bot auto-closed it pending Champion confirmation (standard external
proposer flow per CIP-0100), with the daml-tooling label correctly
auto-applied. Will reopen once Champion is confirmed.

Thanks again for the direction.

— Jatin