Proposal: On-Chain Enforcement of Super Validator Locking and Long-Term Commitment

[cardenaso11]

Development Fund Proposal Submission

Proposal file:
Link to the proposal added in this PR (e.g., /proposals/your-proposal-name.md)
/proposals/CIP-0105.md
Permalink: https://github.com/obsidiansystems/canton-dev-fund/blob/1f9706eb379d7327c7f5755763e3b85d78cf09f0/proposals/CIP-0105.md

---

Summary

Briefly describe the proposal and the value it delivers to the Canton ecosystem (2–3 sentences).

CIP-0105 (Super Validator Locking & Long-Term Commitment Framework) was approved by the Canton Foundation on March 2, 2026. Phase 2, the on-chain enforcement layer that delivers the framework's core value, remains unimplemented.

This proposal funds Obsidian Systems to design, build, deploy, and maintain Phase 2 as a Splice application.

---

Checklist

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

---

Notes for Reviewers

(Add anything the Tech & Ops Committee should pay attention to.)

Tech & Ops Voting Committee Champion: Ali Abrar

[waynecollier-da]

A complete solution for Phase 2 needs to consider locking delegation and wallet substitution, to allow apps to be built that support a full lifecycle of lending and borrowing by SVs. A Phase 2 solution in Splice should cover all the steps in the current Phase 1 operational process.

Please review the Phase 1 operational process at https://github.com/canton-foundation/configs/blob/main/Super%20Validator%20Operational%20Processes/SV-Locking-Process.md

Please also consider partnering with Helix Labs and/or Cumberland and/or Avro Digital to provide a complete solution for Phase 2, or propose an Obsidian-only approach that addresses all these features.

[meiersi-da]

There's also a prior draft of a locking mechanism: https://github.com/hyperledger-labs/splice/pull/3603

I'd suggest to also mention that; and take it into account in the design phase.

[Ian-avro]

Hi @cardenaso11

There are at least 3 teams working on CIP 105 components already.

I propose that we pause on this grant proposal draft until we can flesh out the CIP105 design further.

Top of mind:

1. Capture the biz logic of the SV lock process, Vesting schedule etc
2. Atomic Lock Substitution
3. Delegated locking
4. Observability

Happy to discuss!

Relevant Resources
Previously submitted grant: PR #105
Splice Issue #4841
Splice PR #4898
Splice Issue #4842

[nycnewman]

What assumption / dependencies does this implementation have on smart contract support by wallet providers or custodians? Do wallet /exchange providers (i.e. DFNS, Copper, Blockdaemon, Bitgo, etc, etc) need to support any contracts, Dars, automation if they are currently used for holding the SV balances?

[waynecollier-da]

Some useful comments from HelixLabs @vazilias https://github.com/vaziliaz on Eric Mann's (Avro Digital) proposal here:
canton-network/splice#4841 (comment)