Skip to content

Jg/cip 0105 externally implemented governance locks - #2

Open
jonored wants to merge 30 commits into
mainfrom
jg/cip-0105-externally-implemented-governance-locks
Open

Jg/cip 0105 externally implemented governance locks#2
jonored wants to merge 30 commits into
mainfrom
jg/cip-0105-externally-implemented-governance-locks

Conversation

@jonored

@jonored jonored commented Jul 15, 2026

Copy link
Copy Markdown

More of a directional sketch than a proper PR: implementation of basic CIP-0105 governance locking and unlock to a vesting state on top of V2 allocations.

Not intended to cover most of the scenario; only for technical approach discussion.

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If an upgrade test is required, comment /upgrade_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a logical synchronizer upgrade test is required (from canton-3.5), comment /lsu_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

cocreature and others added 30 commits July 21, 2026 14:38
Current limitations:

1. The split between governance and operator votes is a placeholder.
2. The tests are a joke. Given that I think at this stage this is more
   about how we arrange stuff this hopefully doesn't detract from
   review too much.
3. There are some open questions on the migration.
4. We may want to move beneficiaries to a different place.

Signed-off-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
Signed-off-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
Signed-off-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
Signed-off-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
Signed-off-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
…evelopment cycles by allowing the LSP to work cross-package when working on code.
…ing up development cycles by allowing the LSP to work cross-package when working on code."

This reverts commit 15dfa70.
…ev cycles (canton-network#6523)

---------

Signed-off-by: Cale Gibbard <cale.gibbard@obsidian.systems>
@jonored
jonored force-pushed the jg/cip-0105-externally-implemented-governance-locks branch from ffcbb39 to d2b93f2 Compare August 3, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants