> For the complete documentation index, see [llms.txt](https://civicscommittee.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://civicscommittee.docs.intersectmbo.org/our-previous-work/cip-151-cip-175.md). # CIP-151 / CIP-175 To vote in governance, a stake pool operator has to use their cold keys, the same air-gapped keys that secure the pool itself. That friction keeps many SPOs from voting at all, and low SPO turnout is a direct risk to ratifying governance actions. Two technical proposals set out to remove it, by letting SPOs vote with a hot key derived from their cold key, without ever exposing the cold infrastructure. #### The endorsement The Civics Committee **unanimously endorsed** [**CIP-151**](https://cips.cardano.org/cip/CIP-0151) on 16 July 2026, and sent a formal [endorsement statement](https://docs.google.com/document/d/1dMQMNP_sM1bsCZ-VkbUn3mmZK9t1iTkgUcPAataN-4E/edit?usp=sharing) to the Technical Steering Committee, asking that it be brought into scope for the next protocol hard fork. #### The transition to CIP-175 A week later, on 23 July 2026, the committee noted that [**CIP-175**](https://cips.cardano.org/cip/CIP-0175) had emerged as the better technical path to the same goal. It moved its endorsement to CIP-175, keeping the underlying objective unchanged: let SPOs participate in governance without cold-key friction. The committee notified the TSC of the transition (30 July 2026). This is the committee acting in its advisory role: it does not decide protocol changes, but it evaluates them, backs the ones that serve governance participation, and says so on the record. --- # 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://civicscommittee.docs.intersectmbo.org/our-previous-work/cip-151-cip-175.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.