Proposal: Canton Mobile SDK (Swift + Kotlin)

OPENPull Request
by sunstrike22816-07-2026Declined
1.1M CC requested
canton-apischampion-confirmed
References:CIP-0103
View on GitHub ↗← All Proposals

Development Fund Proposal Submission

Proposal file: ./proposals/2026-07-VertexPoint-canton-mobile-sdk.md

---

Summary

Canton Mobile SDK: native Swift (iOS) and Kotlin (Android) libraries for building on Canton from the two platforms end users hold. Covers the JSON Ledger API v2 client surface, on-device key management for external parties (secure element, biometric-gated interactive-submission signing), token standard V1 and V2, pre-built Splice bindings, and a native implementation of the CIP-0103 wallet connectivity surface over WalletConnect.

Total ask 1,150,000 CC, weighted 66% toward adoption: 600,000 CC pays only against independent Featured Apps running mobile clients on the SDK in production on mainnet. Engineering (390,000 CC) is gated behind acceptance milestones with a working proof of concept at Milestone 1. Apache-2.0 from the first release.

---

Checklist

  • [x] Proposal file added under /proposals/
  • [x] Milestones and funding amounts defined
  • [x] Acceptance criteria included
  • [x] Alignment with Canton priorities described

---

Notes for Reviewers

  • Champion: not assigned yet, submitting as Need Champion. Happy to walk any committee member through the proposal.
  • The funding shape follows Peaceful Studio #46: per-event adoption tranches, a security-review pass-through held outside the engineering envelope (capped at 130,000 CC), and an extended adoption window requested as an explicit exception (12 months; #46 carries 18).
  • Prospective adopter teams from the wallet side of the ecosystem are being invited to comment directly on this PR so the review is informed by teams that intend to build with the SDK.
  • The signing-scheme question (secure elements hold P-256, current documentation examples use Ed25519) is addressed head-on: Milestone 2 demonstrates onboarding and settlement with both schemes before the token-standard milestone opens.