Proposal: Open-Sourcing the K2F Labs Rust SDK for Canton
Development Fund Proposal Submission
Proposal file:
/proposals/2026-07-K2FLabs-rust-sdk-upstreaming-integration.md
This PR supersedes #524, which could not be reopened after its branch was rewritten.
Summary
K2F Labs runs a production Rust SDK for Canton: canton-sdk, an async Ledger API client with DAR code generation, a typed Daml runtime, and value transcoding, and splice-sdk, a Splice application layer for the token registry, Scan, and wallet flows. The stack processes thousands of transactions on Canton mainnet, including behind Walley, a self-custodial wallet. This proposal funds turning it into a public ecosystem asset: open-sourcing under Apache-2.0 with conformance against the Ledger Client Standard, integration with the official toolchain (dpm, Canton/Splice release cadence), and a final milestone gated on adoption by independent organizations, with 35% of the request contingent on that externally verified adoption.
Checklist
- Proposal file added under
/proposals/ - Milestones and funding amounts defined
- Acceptance criteria included
- Alignment with Canton priorities described
Notes for Reviewers
- SIG alignment: canton-apis.
- Champion: to be determined, per Canton Foundation guidance; the proposal can remain in Needs Champion while the committee reviews it.
- Relationship to the approved Rust SDK proposal (#407) is addressed in the Rationale: this proposal is complementary, not competing. It puts a production-proven Rust client in the ecosystem's hands now, provides a second implementation conformant to the Ledger Client Standard, and adds the Splice application layer (registry, Scan, wallet flows, indexing) that no current grant covers as working client code. K2F will coordinate crate namespaces with the greenfield effort and contribute to a shared conformance suite; neither proposal depends on the other's approval.
- Post-grant maintenance is self-funded: K2F's production applications run on these crates, so maintenance continues as part of our own operational upgrade cycle.