> 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.