> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/cardano-constitution/read-the-cardano-constitution/hash.md). # Hash {% hint style="danger" %} **ARCHIVED** This page has been archived. It's content might be outdated. {% endhint %} Constitutional Delegates were elected to represent their Constitutional Workshop and work to approve a Cardano Constitution to be put on-chain for DReps and the CC to vote. Although different file formats have been used along the way for drafting purposes, the version of the Constitution that must go on-chain is a text file (.txt) and a hash of that text file. Hashing is used to confirm if a file matches the one being referenced. The hash of a file is like a fingerprint, and is unique to each file. If a single character changes in the file, the hash no longer matches. A text file is used to ensure the hash matches as long as all of the written characters match. Text files strip away all except the written characters in the file, ensuring the hash will match so long as none of the words are changed in the file. Other programs, like Google Docs and Word, will add invisible information in the file. The hash of “Hello World” in a Google Document would not match the hash of “Hello World” in a Word document. So, the Constitution text being voted on is being shared as a .txt file with the associated hash. This allows you to confirm that the document up for vote matches, word for word, the one that’s been distributed to you ahead of time. \\ BLAKE2b-256 hash digest: `2a61e2f4b63442978140c77a70daab3961b22b12b63b13949a390c097214d1c5` **How-to Check the hash** **Easy Way** Please see [Instructions to **verify** the constitution hash](https://docs.google.com/document/d/1xmDkMrL6ebaLNBsysiNQrtABcVnYBmsteQQcsrzGOpo/edit?tab=t.0#heading=h.bxb46qftdspf). **CLI Way** Using straight Cardano CLI pull from repo (no repo cloning needed). ``` cardano-cli hash anchor-data --url https://raw.githubusercontent.com/IntersectMBO/draft-constitution/refs/heads/main/2024-12-05/cardano-constitution-1.txt ``` Using Cardano CLI with local repo. ``` cardano-cli hash anchor-data --file-text ./2024-12-05/cardano-constitution-1.txt ``` Using hashing script (which uses Cardano CLI and b2sum). ``` ./scripts/hash.sh ./2024-12-05/cardano-constitution-1.txt ``` \\ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/cardano-constitution/read-the-cardano-constitution/hash.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.