> 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

The implementation supports protocol identities, versions and historical profiles. That infrastructure allows software to identify the rules associated with a transaction; it does not by itself implement token governance.

### Anchor and contract identity

An anchor is located by its confirmed Bitcoin transaction coordinates. The implementation derives identifiers from those coordinates and uses protocol profiles and switch heights to resolve historical context.

The current anchor-derived contract identity uses the anchor's own location. The type system allows room for separate contract publications and later versions, but this is not evidence of a live proposal-and-vote mechanism updating one anchor automatically.

See [Anchor Contract](https://docs.ducatprotocol.com/how-ducat-works/anchor-contract.md) for the identity distinctions.

### Adopting a release

A concrete upgrade must identify:

1. The new software rules and applicable anchor or profile.
2. Its activation point and the prior profiles needed for replay.
3. How clients, guardians and validators select the same rules.
4. The treatment of existing vaults, including any required user transaction.
5. Compatibility and migration checks for keys, metadata, assets and balances.

Historical validation needs the relevant earlier context; it cannot simply reinterpret every old vault using today's settings.

Bitcoin outputs retain their original spending conditions until spent. A software upgrade or new anchor cannot change the keys or hashlocks already committed in an unspent vault.

### Planned voting design

On-chain proposals, token-weighted ballots, vote tabulation and automatic activation are future governance mechanisms unless a deployment provides the implemented formats and rules. This page does not specify an available voting procedure.

A future design must explain how voting outcomes map to executable software and existing Bitcoin outputs, as well as how conflicting or unavailable participants are handled.
