List view
- Due by September 30, 2026•0/1 issues closed
- Due by August 31, 2026•0/1 issues closed
- Due by May 31, 2026•4/12 issues closed
- Due by May 31, 2026•0/5 issues closed
- No due date•5/43 issues closed
https://github.com/canton-foundation/canton-dev-fund/issues/278
Due by December 31, 2026https://github.com/canton-foundation/canton-dev-fund/issues/277
Due by December 31, 2026https://github.com/canton-foundation/canton-dev-fund/issues/276
Due by September 30, 2026•2/4 issues closedhttps://github.com/canton-foundation/canton-dev-fund/issues/275
Due by June 30, 2026•4/8 issues closedhttps://github.com/canton-foundation/canton-dev-fund/issues/366
Due by December 31, 2026- No due date
https://github.com/canton-foundation/canton-dev-fund/issues/364 Implementing granular, privacy-preserving data access controls between the untrusted dApp and the Gateway. - **Scoped Token Issuance:** Upgrading the auth module to issue scoped OIDC tokens. - Acceptance: Automated tests proving the Gateway issues tokens that strictly limit a dApp's access to specifically defined data sets on a validator. - **Read Review Authorization:** Delivery of a user-facing data access screen. - Acceptance: Functional visual component that accurately presents the dApp's requested data scope to the user, requiring explicit human approval before the scoped token is released to the dApp.
Due by October 31, 2026https://github.com/canton-foundation/canton-dev-fund/issues/363 Removing centralized identity dependencies to enable trustless Ledger API connectivity. - **Self-Signed Token Issuance (Auth):** Implementation of an internal Identity Provider (IDP) generating Self-Signed OIDC tokens using the user's primary signing key. - Acceptance: E2E integration logs demonstrating a successful transaction submission to the Ledger API where the authentication token is generated and signed locally by the user's cryptographic key material, without routing through or requiring uptime from a 3rd-party IDP (e.g., Auth0, Entra) - **Cryptographic validation** logic enabling the Gateway to authenticate directly with the Ledger API. - Acceptance: Automated test execution confirming the Gateway correctly validates the self-signed OIDC token's signature against the user's public key prior to Ledger API submission.
Due by August 31, 2026https://github.com/canton-foundation/canton-dev-fund/issues/362 Native Token Standard (CIP-056) Support: Integrating deep Canton Network native asset capabilities directly into the Gateway API and UI. - **CIP-0056 Integration:** Native token standard features implemented within the Gateway. - Acceptance: Verifiable E2E tests demonstrating the Gateway can successfully query token holdings, fetch transaction history, execute asset transfers, and manage allocations adhering strictly to the CIP-056 standard.
Due by July 31, 2026https://github.com/canton-foundation/canton-dev-fund/issues/361 Expanding institutional connectivity, hardening test coverage across all drivers, and delivering user-facing documentation for production readiness. - **Institutional Signing Drivers:** Delivery of signing drivers for at least one additional major institutional wallet provider. - Acceptance: E2E integration logs demonstrating successful transaction signing via the institutional infrastructure provider. - **Multi-Session Support:** Implementation of concurrent user handling. - Acceptance: Automated test execution proving a single Gateway instance can concurrently handle two distinct user sessions without state bleed. - **UI/UX & Canton Ecosystem Branding:** Update of the Gateway interface to adhere to Canton Foundation guidelines. - Acceptance: Visual review and sign-off by a Foundation designated UI/UX representative. - **User Documentation:** Delivery of comprehensive end-user materials. - Acceptance: Publication of a UI user manual and at least one step-by-step video walkthrough for standard setup. - **External Security Audit:** Delivery of a finalized security audit report from an independent, reputable Web3 security firm covering the core Gateway architecture and CIP-0103 implementation. - Requirement: All findings classified as "Critical" or "High" must have a verifiable patch merged into the main branch. - **Code Quality:** CI/CD pipelines must report maintaining: - gte80% Unit Test coverage - gte80% E2E test coverage that explicitly includes all institutional driver flows.
Due by June 30, 2026•2/30 issues closedhttps://github.com/canton-foundation/canton-dev-fund/issues/365
Due by October 31, 2026•0/3 issues closed- No due date•3/3 issues closed
- No due date
- No due date•1/1 issues closed
- No due date•1/1 issues closed
- No due date•0/1 issues closed
https://github.com/canton-foundation/canton-dev-fund/issues/360 Establishing the foundational API architecture, containerized deployment, and initial institutional connectivity required for MVP trading flows. - Reusable User API - dapp API-Server (CIP-0103) - Party Support (Internal/External Parties) - Containerized Deployment - Utility Migration - Initial Institutional Adapter (SP Drivers) - Developer Documentation - Internal Audit - Tested (80% Unit, 50% E2E) - Basic clear signing Targeting V1.0.
Due by May 31, 2026•85/116 issues closed- No due date•91/91 issues closed
Work to support exchange integrators
No due date•5/14 issues closed