> For the complete documentation index, see [llms.txt](https://docs.ducatprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ducatprotocol.com/governance/upgradeability.md). # Upgradeability * Clients can spend their DUCAT using a time-locked bitcoin transaction in order to participate in governance. These transactions are marked with a special `OP_RETURN` output and indexed by the validators. * There are two types of governance transactions: **Proposals** and **votes**. * A **proposal** transaction carries inscription data, and publishes the new terms being proposed. * A **vote** transaction also carries inscription data, and references the proposal(s) that it is voting for. * Validators will index and validate these proposals, and tabulate the votes for/against them for a pre-defined voting period. * If a proposal is successful, validators will automatically update their contract state to reflect the new changes. * If all participants run the same validator software (including guardians), then there should be network consensus on the state of the contract. * There should also be consensus on the historical state of the contract for any given block height, which allows older vaults to be processed with the correct contract state. --- # 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.ducatprotocol.com/governance/upgradeability.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.