Skip to content

Conversation

@Ryun1
Copy link
Collaborator

@Ryun1 Ryun1 commented Oct 17, 2025

This CIP extends CIP-100 | Governance Metadata to introduce a standardized onChain property. The onChain property encapsulates the on-chain effects using CIP-116 | Standard JSON encoding for Domain Types standard encoding, enabling verification that metadata content matches on-chain action and preventing metadata replay attacks.

Todo

  • Answer open question(s)
  • Add richer more comprehensive examples
  • Flesh out Rationale

See rendered proposal on branch

@rphair rphair added Category: Metadata Proposals belonging to the 'Metadata' category. State: Triage Applied to new PR afer editor cleanup on GitHub, pending CIP meeting introduction. labels Oct 17, 2025
Copy link
Collaborator

@rphair rphair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very good to see this; I'd been expecting to see the progression of this issue someday:

cc @gitmachtl @Quantumplation @Crypto2099

@ptrdsh
Copy link
Contributor

ptrdsh commented Oct 22, 2025

Im also all down for it. Very useful 🙏

One other additional onchain datapoint Id find useful is to add the corresponding address to an author pubkey in the author section, especially if its a CIP-0008 signature instead of an ed55219 sig (or also in that new onchain section).

something like AddressOfWitnessPublicKey:

"authors":
    [
        {
            "name": "Cardano Foundation",
            "witness":
            {
                "witnessAlgorithm": "CIP-0008",
                "publicKey": "a535adf6786e2f8cd4bb7451e9f5b6368a037b8ed42f35b8446fb8946b7d153d",
                "signature": "845846a201276761646472657373583901acb2792c1cb10724327852ac8d03f870732c5bc8e10c22a8b80991411ef0ec112a3c73539566bde6b6abe41bb79191c1baa69edfcb0581f2a166686173686564f45820365b88ab14451ab057845f697ab4c7aa78ce82c26a6dad092db0e3fe48c468e858400825fe66ad9f2f9f003b345336004fd9a4e6d1c9d4b3677e47563b23132fc3879829fc2e2c300cf459cb92c5282daa46230122055528166253715e74024ae20c"
            },
            "AddressOfWitnessPublicKey": "addr1qxkty7fvrjcswfpj0pf2ergrlpc8xtzmersscg4ghqyezsg77rkpz23uwdfe2e4au6m2heqmk7gersd6560dljc9s8eqr6r3v3"
        }
    ]

As for the approach to get this standardized: why cant we edit the existing CIP(s)? Im sure there are more learnings that we could apply to a larger overhaul than just this useful addition. (one immediate example of that would be the reference object type translation.)

@Ryun1
Copy link
Collaborator Author

Ryun1 commented Oct 28, 2025

@ptrdsh

something like AddressOfWitnessPublicKey:

This is quite a nice idea, I would support something like this.
But maybe better suited within the scope of another CIP
Ive deliberately tried to keep this proposal very small and straight forward.

@rphair rphair changed the title CIP-???? | Governance Metadata - On-Chain Effects CIP-0169? | Governance Metadata - On-Chain Effects Oct 28, 2025
Copy link
Collaborator

@rphair rphair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Ryun1 as you observed this was well supported at the CIP meeting so please do the business to update the CIP number to 169 🎉

@rphair rphair added State: Confirmed Candiate with CIP number (new PR) or update under review. and removed State: Triage Applied to new PR afer editor cleanup on GitHub, pending CIP meeting introduction. labels Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Category: Metadata Proposals belonging to the 'Metadata' category. State: Confirmed Candiate with CIP number (new PR) or update under review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants