Skip to content

Fix stale DSO delegate references (delegateless automation, CIP-0064) #625

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Nunobrazz wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fix stale DSO delegate references (delegateless automation, CIP-0064) #625

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e5c79fd
Fix stale DSO delegate references (delegateless automation, CIP-0064)
Nunobrazz May 26, 2026
e8af8c8
Merge branch 'main' into patch-1
8bitpal May 26, 2026
6b62765
Merge branch 'main' into patch-1
8bitpal May 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs-main/overview/reference/sv-governance-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ This threshold ensures two properties: **integrity** (a dishonest minority canno

## Governance Roles

Any SV can propose a governance action by creating a `VoteRequest` on-chain. All other SVs can then cast votes (accept or reject) on that request. Once the vote threshold is met, the DSO delegate executes the action.
Any SV can propose a governance action by creating a `VoteRequest` on-chain. All other SVs can then cast votes (accept or reject) on that request. Once the vote threshold is met, any SV can execute the action. Execution no longer depends on a designated DSO delegate, which was replaced by delegateless automation per [CIP-0064](https://github.com/canton-foundation/cips/blob/main/cip-0064/cip-0064.md).

There are two execution paths for actions that require confirmation:

Expand Down Expand Up @@ -132,7 +132,7 @@ The GSF does not have unilateral control over the network. Its SV node carries t

## On-Chain Governance Architecture

All governance state lives on-chain as Daml contracts. The `DsoRules` contract holds the authoritative record of DSO membership (`svs` map), the DSO delegate, and the current configuration. The `AmuletRules` contract holds the Canton Coin configuration schedule. Vote requests, confirmations, and SV state contracts are all ledger-visible, making governance auditable by any party with access to the Scan app.
All governance state lives on-chain as Daml contracts. The `DsoRules` contract holds the authoritative record of DSO membership (`svs` map), and the current configuration. The `AmuletRules` contract holds the Canton Coin configuration schedule. Vote requests, confirmations, and SV state contracts are all ledger-visible, making governance auditable by any party with access to the Scan app.

The decentralized party model means that the DSO party itself has a confirmation threshold of `ceiling(numSVs * 2.0 / 3.0)`. Every transaction signed by the DSO party must be confirmed by at least that many SV participant nodes, enforcing BFT at the Canton protocol layer independent of the application-level voting logic.

Expand Down