Wallet Gateway Reference Implementation #109 Milestone 3: Browser Extension Deployment Capability

Milestone 3: Browser Extension Deployment Capability

Repurpose the Gateway’s core routing logic and CIP-103 API server to run entirely locally within a browser context, serving as the foundational background engine for ecosystem Reference Wallets (e.g. Development Fund Proposal: Open Source Reference Wallet - Splice Portfolio).

• Browser-Extension-Compatible Gateway Engine: Delivery of the core Wallet Gateway components packaged as a localized, browser-compatible library (e.g., NPM package). This involves migrating enterprise server dependencies to Web-native equivalents (e.g., WebCrypto API) to ensure execution within Manifest V3 background service workers.

Acceptance:* Automated CI/CD logs demonstrating successful compilation of the Gateway logic into a browser-compatible artifact.

• Local dApp API Server (CIP-103): Implementation of the dApp API server capable of running locally in the browser to accept connections from web-based dApps without routing through a remote Docker instance.

Acceptance:* Verifiable automated tests executing a JsPrepareSubmission flow exclusively within a browser-sandboxed environment, proving the local engine can independently administer connections to the KeyStore and Ledger APIs.

| Milestone | Target deadline | Funding Request | | :--- | :--- | :--- | | Milestone 3: Local Deployment Capability and Browser Engine: | August 31st 2026 | 800.000 CC |

_Originally posted by @pedrodneves in https://github.com/canton-foundation/canton-dev-fund/issues/109#issuecomment-4512200194_