> For the complete documentation index, see [llms.txt](https://docs.tajirchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tajirchain.com/governance/proposal-templates/contract-upgrade.md).

# Contract Upgrade

Use this format when deploying improved logic, adding new features, fixing issues, or applying security upgrades.

***

### **Proposal Title**

Provide a brief and descriptive title.

**Example:**\
*Upgrade Governance Contract to v1.2*

### **Summary**

Explain what contract is being upgraded and the purpose of the change.

### **Motivation**

Why this upgrade is necessary:

* Bug fixes
* Optimization
* Security enhancements
* Introduction of new features

### **Upgrade Details**

List all relevant information for reviewers:

* Current (old) contract address
* New contract address
* Key differences between versions
* Any required migration steps

### **Risk Considerations**

Identify potential risks involved in the upgrade:

* Compatibility issues
* Required downtime, if any
* Complexity of state migration

### **Execution Steps**

If the upgrade will be executed through a multisig or governance payload, include the call data format here:

```
target: <contract_address>
value: 0
calldata: <upgrade_function_payload>
```

### **Voting Options**

* **Yes** — Execute upgrade
* **No** — Keep current version
* **Neutral** —  Skip Voting