Cip updates#1
Merged
Merged
Conversation
Signed-off-by: dave-axymos <dave@axymos.com>
Signed-off-by: dave-axymos <dave@axymos.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Documentation-only changes, but they materially change the proposed protocol flows (payments, transfers, disputes, and governance), so reviewers should validate the revised design semantics.
Overview
Updates the Canton Naming CIP to version 1.1 with a new end-user-focused overview and revised formal spec.
The proposal is reworked to align with CIP-56:
NameRecordis described as a 1-of-1 token/holding, transfers move to a CIP-56TransferFactorytwo-stepNameTransferInstructionflow, and renewals are specified viaCredentialFactory_UpdateCredentials(plus aRenewNamealias for JSON API clients).Economics and ops are simplified: registration/renewal fees become two holder-funded transfers (holder→registrar commission, holder→DRO treasury) with batched payouts via a new
Treasurycontract; disputes drop on-ledger staking/voting in favor of stake-free disputes resolved by k-of-n DRO actions; name uniqueness is specified via 256RegistrarShards to serialize concurrent registrations; and an emergencyPause/GA_Unpausemechanism is added.Reviewed by Cursor Bugbot for commit f582847. Bugbot is set up for automated code reviews on this repo. Configure here.