Proposal: Open Source Reference Wallet

[davidrichards-da]

Development Fund Proposal Submission

Proposal file:
‎proposals/proposal-open-source-reference-wallet.md‎

---

Summary

This proposal proposes the delivery of two production-grade, open-source reference wallet packages: the Splice Portfolio dApp UI and the Splice Wallet Browser Extension. Operating strictly as provider-agnostic ecosystem public goods, these repositories provide end-to-end operational blueprints for integrating critical Canton Network protocol features, including CIP-0056 (Token Standard), CIP-0103 (dApp API), and multi-party hosting capabilities.
By establishing standardized, fully audited integration patterns, these reference implementations are designed to tangibly reduce external integrator onboarding timelines and accelerate network-wide feature parity for dApps, exchanges and wallet providers.

---

Checklist

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

---

[hythloda]

Review Feedback — Open Source Reference Wallet (Splice)

Thank you for the submission and for contributing a proposal focused on reference wallet implementations for the Canton ecosystem.

This proposal is clearly aligned with ecosystem priorities, particularly around CIP-0056 and CIP-0103 adoption, and addresses a real need for standardized integration patterns.

That said, a few areas would benefit from clarification:

---

1. Adoption expectations

The proposal outlines strong technical deliverables, but it would help to clarify:

• which partners (wallet providers, exchanges, dApps) are expected to adopt these implementations
• whether there are committed or active integration efforts

---

2. Scope vs. funding level

The proposal includes a large funding request across multiple components:

• dApp UI
• browser extension
• future feature expansion
• replacement of the existing wallet

It would be helpful to:

• clarify effort allocation across milestones
• and how the full scope maps to ecosystem impact

Overall, this is a strong and strategically aligned proposal. Clarifying adoption pathways and scope justification would strengthen confidence in its ecosystem impact.

[davidrichards-da]

Thanks for the feedback, @hythloda. The grant proposal has been updated based on the feedback provided and is ready for review again.

[evarsamis]

Temple supports this open source reference wallet grant proposal. A reference wallet like this will be very useful to develop new features against

[abisheksingh2024]

Bitgo is fully behind this grant proposal. When we first integrated with the Canton Network, we had to navigate several hurdles that a reference implementation would have cleared instantly. We anticipate this becoming an essential technical North Star for us as we integrate more complex, upcoming network features

[Jatinp26]

on DevRel level, as much as we have seen wallets being a major pain point, having an internal ref wallet implementation without hitting an access code wall would be a major help for more of our developer onboarding.

[Binxx35]

As a core wallet provider, Blockdaemon endorses this proposal. Having a gold-standard reference wallet ensures ecosystem consistency and accelerates the integration of new standards by serving as a template-driven blueprint for other providers. It’s the kind of asset that would have reduced hours during our launch, and it will be a benchmark for future rollouts.

[gaurav-hashrupt]

This is a great proposal and it will really help dApp like Verity that we are building. Hashrupt fully endorses this grant proposal that will make an open-source reference wallet available for us. Having a standardized tool like this is essential for streamlined our feature development for application builders like Hashrupt.

[pedrodneves]

Milestone 1: Splice Portfolio dApp UI

• Estimated Delivery: 4 months after CIP approval: by 31st July 2026
• Focus: Building a portfolio dApp UI with the foundational wallet features.
• Deliverables / Value Metrics & Acceptance Criteria:
  • Splice Portfolio, a wallet dApp UI with wallet feature reference implementations.
    • Splice Portfolio is a dApp and therefore, delegates party management to the CPI-0103 API provider (in this architecture, the Wallet Gateway)
  • Release in a public GitHub repo (Apache 2.0)
  • CIP-0056 token standard support
  • CIP-0103 dApp API compliant
  • Publicly accessible docker image and helm chart
  • Integrating with the Wallet Gateway via CIP-0103 giving the following features:
    • Integration for external party key storage
    • Self-hosted validator connection
    • Support for internal parties
  • Internal security audit
  • Transaction history
  • Canton Coin and DA Registry pre-approval support (in preparation for Preapproval support via standards)
  • Fully documented code and documentation of features added

Milestone	Description	Compensation
Milestone 1	Splice Portfolio dApp UI	4,000,000 CC upon committee acceptance

[pedrodneves]

Milestone 2: Splice Portfolio replaces the Splice Amulet Wallet

• Estimated Delivery: The same time as M1: by 31st July 2026
• Focus: The Splice Amulet Wallet is replaced by Splice portfolio and the Wallet Gateway as the default wallet in the splice stack.
• Deliverables / Value Metrics & Acceptance Criteria:
  • Sufficient feature parity with the current Splice Amulet Wallet. In addition to the features listed in Milestones 1, adding support for DevNet CC tap
  • The replacement of the Splice Amulet Wallet with Splice Portfolio in the validator stack.

Milestone 3: Splice Wallet Browser Extension

• Estimated Delivery: 3 months after delivery of M1 & M2: by 31st October 2026
• Focus: Provide a deployable browser extension package as a reference wallet implementation including party management.
• Deliverables / Value Metrics & Acceptance Criteria:
  • End-to-end reference wallet implementation through a browser extension deployment including all features of the Splice Portfolio dApp UI outlined in Milestone 1 plus:
    • In-browser key storage
    • Ability to create a party
    • Connection to the Splice Portfolio dApp UI
    • Chrome and firefox browser compatible
  • Third-Party Security Audit Report (Critical/High issues resolved)

Milestone	Description	Compensation
Milestone 2	Splice Portfolio replaces the Splice Amulet Wallet	1,000,000 CC upon committee acceptance

[pedrodneves]

Milestone 3: Splice Wallet Browser Extension

• Estimated Delivery: 3 months after delivery of M1 & M2: by 31st October 2026
• Focus: Provide a deployable browser extension package as a reference wallet implementation including party management.
• Deliverables / Value Metrics & Acceptance Criteria:
  • End-to-end reference wallet implementation through a browser extension deployment including all features of the Splice Portfolio dApp UI outlined in Milestone 1 plus:
    • In-browser key storage
    • Ability to create a party
    • Connection to the Splice Portfolio dApp UI
    • Chrome and firefox browser compatible
  • Third-Party Security Audit Report (Critical/High issues resolved)

Milestone	Description	Compensation
Milestone 3	Splice Wallet Browser Extension	2,500,000 CC upon committee acceptance

[pedrodneves]

Milestone 4: Future known improvements

• Estimated Delivery: 1 month after delivery of M3: by 30th November 2026
• Focus: Add known future features which wallet providers and exchanges will have to implement.
• Deliverables / Value Metrics & Acceptance Criteria:
  Since not all of the features are delivered or fully defined, this milestone’s scope, ability to be completed and timeline may need to be adjusted depending on the state of the features that it depends on.
  • Provide a reference implementation showing the ability to allow parties to pay for traffic fees via the wallet UI.
  • WalletConnect integration
  • Token Standard v2 support
  • Flows demonstrated for multi-hosting parties

Milestone	Description	Compensation
Milestone 4		1,000,000 CC upon final release and committee acceptance