CIP-0120? | Constitution specification

[Ryun1]

This proposal aims to describe a standardized technical form for the Cardano constitution.
Hoping to enhance the accessibility and safety of the document.

---

📄 Rendered proposal

[rphair]

Looks comprehensive & standardisation of form... with some rules like those already used to standardise manuscripts for comparison... will really help Constitution based tools.

One thing diffs and checksums will always notice is capitalisation. What standard is Intersect (and any other part of the community prolific in Cardano governance) developing around how Constitution is capitalised? English grammar rules for common & proper nouns would indicate (on which I based a recent cardano-foundation/developer-portal#1252 (comment) which also includes Ada spelling corrections like some below):

• "Cardano Constitution" is obviously a very specific proper noun phrase & so each word would be capitalised.
• the Constitution in effect... either the "initial" one or any updated version... would also be singular & therefore also capitalised "Constitution" as a common noun.
• draft or proposed constitutions are not unique & therefore are not capitalised.
• the phrase "the Constitution", unless talking non-specifically (e.g. "the constitution that voters prefer"), would generally be assumed to be THE Constitution and capitalised as a proper noun.

If you think these rules are true & helpful, it could likewise make sense to code them into the CIP so that capitalisation corrections don't cause appearance or the document checksum to vary over insignificant changes. If you want I will prepare that as a code diff.

Conversely, if governance major stake holders don't think this is an issue then let's establish that here... i.e. that the uncapitalised spelling "constitution" can also refer to THE "Constitution" itself... and I'll consider the matter concluded for this CIP & the Cardano community in general.

As with Ada vs. ADA vs. ada, using the term capitalised differently will make some think there are typos and inconsistencies everywhere: especially when appearing differently in the same sentence. We have seen this issue on the Dev Portal which has been an editorial headache even when documents didn't have to be checksummed.

• This all the more reason why I think the capitalisation issue might need to be addressed in the CIP itself... and maybe that of Ada as well since constitutions are likely to use this term frequently and in all 3 contexts.

N.B. I am someone with a long standing interest in these matters but by no means the "last word" on grammar, so please I would be open to other editorial guidelines.

cc @Quantumplation @kevinhammond @stevenj @michaelpj @katomm @KtorZ

[rphair]

From launch at CIP meeting yesterday it seems like everybody will be happy with the CIP number 120 🎉

[Ryun1]

With 5c2143f I have included your suggestions @Thomas-Upfield @stevenj 💪

[rphair]

@Ryun1 looks good so far & I feel ready to approve once Open Questions and TODO are addressed (please point out anything further that you feel is "in progress").

[rphair]

following up on #796 (comment) (resubmitted to change the editing scope):

[Ryun1]

@rphair

I have tided up all loose ends/comments, and added some fun test vectors.
I have forwarded this proposal to a few stakeholders for a final review.

[getnood]

Just popping in to suggest the entire document could (and should be) stored onChain as well.

If the text gets longer than 16kb as an array, just continue it on another token and link from the asset to the subsequent one.

For example, here is an onChain reading of the Ergo Manifesto, whose full text is preserved on the network

https://pool.pm/asset13wmugsz896ah40r7kmsr8r8d9e8z0yzfj0pw9y

Will be fun to make this for the Constitution. And I assume some fun book-io versions as well 🥳

[Ryun1]

@getnood

This is super cool, I didn't know about this.

is this method of chaining all the metadata together through multiple tokens, standardised at all?
I would fear that this could add a decent chunk of complexity in reading and writing the constitution, as well as doing a correctness check.

Although I do agree keeping it onchain is a really nice thing, to be able to do.

[getnood]

Sweet! Yeah it's super fun to make tokens connected to other tokens. There's no set standard for how to compose those connections, and I would assume a different approach from different creators depending on what they're doing. But here's some more examples:

This is a "collection token" that references all of the NFTs from a single collection (policy ID): https://pool.pm/asset1vdg65fezc5crtyhvt47n0gwvul94u2r74dhasa

Here's another fun example where a fungible token is made like a link tree to a bunch of different NFTs, and each of those NFTs are an index of other NFTs inside of a wallet: https://pool.pm/asset1xzw2algyy50t8x7f4mpg20tem33xemvm6rystq

( I still need to finish all the links/contents on the second example, but you can get the idea)

I think there's lots of creative ways to use connected networks of native assets on Cardano like this. Using CIP68 approaches also further expand the creative possibilities for what an individual, project, or organization might do

[Ryun1]

@getnood

Id love to collaborate on a competing proposal to CIP-120, which focuses on chaining metadata across tokens (may or may not have to be constitution specific).

How such documents can be written and read from chain would be super useful.

[getnood]

Heck yea can't wait to hear those ideas! Have been making tokens that reference tokens for like 3 years, and with exception to CIP69, is the first time the topic got interest. Stoked!

[Ryun1]

Although this standard is already being followed by the interim constitution
I dont see a rush to merge

Id like to keep it open, pending the constitutional workshops happening over the coming months
If new ideas arise with big changes I will merge this version as a V1 and work on a V2
Otherwise Im happy to add small tweaks to the current version