> For the complete documentation index, see [llms.txt](https://docs.overtime.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overtime.io/learn-about-overtime/overtime-governance.md).

# Overtime Governance

## Overtime Governance

Overtime is governed directly by **$OVER holders**. Every Overtime Improvement Proposal (OIP) is approved or rejected by $OVER holders in a Snapshot vote. The elected Overtime Council that used to decide OIPs was dissolved by [OIP-263](https://github.com/thales-markets/overtime-improvement-proposals/blob/main/OIPs/OIP-263.md), which passed in June 2026.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Read Overtime OIPs</td><td></td><td></td><td><a href="https://github.com/thales-markets/overtime-improvement-proposals">https://github.com/thales-markets/overtime-improvement-proposals</a></td><td></td></tr><tr><td>Vote on OIPs</td><td></td><td></td><td><a href="https://www.overtime.io/dao">https://www.overtime.io/dao</a></td><td></td></tr></tbody></table>

**How an OIP is decided**

1. **Draft and publish.** Anyone can draft an OIP and publish it in the [OIP repository](https://github.com/thales-markets/overtime-improvement-proposals) on GitHub.
2. **Discuss.** The proposal is discussed with the community in the [Overtime Discord](https://discord.gg/overtime-io).
3. **Vote.** $OVER holders vote on [Snapshot](https://www.overtime.io/dao). If posting to Snapshot requires privileged access, authorized team members or governance operators post the vote on the proposer's behalf.
4. **Finalize.** The result becomes final unless it is vetoed by the Elders (see below).
5. **Implement.** The Overtime DAO deploys any new or updated smart contracts required by a successful OIP.

**Voting rules**

|                     | Regular OIPs                                                                   | Meta-governance OIPs (changes to the governance rules themselves)              |
| ------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |
| **Approval needed** | At least 60%                                                                   | At least 80%                                                                   |
| **Quorum**          | The lower of 10,000,000 $OVER or 30% of the circulating voting-eligible supply | The lower of 15,000,000 $OVER or 50% of the circulating voting-eligible supply |

Quorum is adaptive: using the lower of a fixed amount or a share of the circulating supply keeps quorum reachable as the supply shrinks through $OVER buybacks and burns.

**Who can vote**

Voting power is based on $OVER holdings, as configured on Snapshot. $OVER held by the Overtime treasury, treasury-associated wallets, treasury-controlled multisigs or any other protocol-controlled wallet **cannot vote**, and it doesn't count toward the circulating voting-eligible supply used for quorum. Governance reflects circulating holders, not protocol balances.

**Elders: a limited emergency safeguard**

Direct token voting carries risks such as whale concentration, temporarily accumulated voting power and low turnout. As a narrow backstop, at least **three former Overtime Council members**, acting as Elders, can publicly veto a Snapshot result in Discord before it becomes final.

* Elders can only block an outcome that is clearly malicious, rushed, governance-breaking or otherwise harmful to the protocol. The veto is meant to be exceptional, not a second approval layer.
* Elders cannot submit proposals, approve proposals or create votes.
* Active core contributors cannot act as Elders, so the core team cannot use the veto to overrule holders.
* New Elders can be added if at least three existing Elders publicly approve the addition in Discord.

**From Council to direct voting**

For about five years, first as Thales and then as Overtime, governance ran through an elected council: $OVER holders elected Council members for six-month epochs, and the Council reviewed and voted on every proposal. The Council was later reduced from seven members to five. As the protocol matured and proposal volume fell, OIP-263 moved the final vote to $OVER holders directly while keeping the same public proposal and discussion process.
