# Governance ### Principals Origin Protocol is developed and maintained by Origin Protocol Labs, a legal entity incorporated in the Cayman Islands. Origin Protocol Labs serves as a core contributor and operational steward of the protocol, acting in accordance with the direction of xOGN governance. Protocol upgrades, parameter changes, and strategy approvals are subject to the governance processes described below. Origin products operate as decentralized protocols governed by a distributed set of stakeholders. Yield generation, fee collection, and fee distribution are executed entirely through smart contracts. Upgrades to these contracts pass through a timelock and can only be initiated through governance controlled by xOGN holders. Although the initial contracts and strategies were developed by the Origin team, protocol evolution is open to the broader community. Governance participants can propose parameter changes, introduce new strategies, contribute code, or vote on active proposals. The expectation is that major decisions are made collectively, while limited day-to-day responsibilities may be delegated to trusted contributors who maintain the protocol’s operations. Governance proposals require participation from at least 20% of the xOGN supply to reach quorum. There is no minimum requirement to cast a vote on existing proposals. All approved proposals are executed only after passing through a timelock, ensuring a delay between approval and implementation. This delay provides transparency and allows users to exit positions if a proposal introduces changes they deem unfavorable. ### **Proposal lifecycle** Changes to Origin’s smart contracts require onchain proposals to be created, approved, and executed by governance token holders. All pending and historical onchain proposals are visible on the governance page of the [Origin Dapp](https://app.originprotocol.com/). Initiating this type of formal, binding proposal requires technical skills and knowledge of the protocol’s code. Onchain proposals also involve transaction costs (gas fees) necessary to update the state of the blockchain. As a result, most proposals go through an informal, off-chain process occurring on the [Origin Protocol Snapshot Space](https://snapshot.org/#/origingov.eth). Snapshot enables any eligible governance token holder to create a proposal or vote at no cost. This also reduces the complexity and expense required to make a proposal and allows for the community to signal its approval or opposition to a given change. We encourage everyone to propose improvements at any time. To help stay up to date on Snapshot proposals, you can enable email notifications by visiting [Snapshot V1](https://v1.snapshot.box/#/), clicking on your username, and adding an email. It’s natural for proposals to be accompanied by healthy debate or discussion regarding implementation, reasoning, methodology, etc. Discussions regarding new proposals now start in the [Origin Governance Forum](https://governance.originprotocol.com/) and are cross-posted to [Origin's Discord server](https://originprotocol.com/discord). ### **Timelock Contract** All approved proposals execute onchain through a timelock that enforces a mandatory 2-day delay (172,800 seconds) between governance approval and implementation. This window gives any user time to review an approved change and take action before upgrades take effect. **Contract address (Ethereum):** 0x35918cDE7233F2dD33fA41ae3Cb6aE0e42E0e69F The timelock uses role-based access control. The proposer role — held by the governance multisig — queues onchain proposals approved onchain by xOGN governance. The executor role runs them after the delay has elapsed. No single address can both propose and execute without the delay intervening. ## **Participating** High-level criteria are required to vote and make proposals: Hold sufficient xOGN tokens (Staked Origin Tokens) * No minimum to vote on existing proposals * 5,000 xOGN to create a Snapshot proposal * 100,000 xOGN to create an on-chain proposal (Note, you have the option to delegate your votes to another Ethereum wallet.) Here are the step-by-step instructions to vote and create a proposal: 1. Obtain OGN from a centralized exchange like Coinbase or Binance, or a decentralized exchange such as Uniswap or Curve. 2. Stake OGN using the [Origin App](https://app.originprotocol.com/#/ogn/staking) 3. Submit and discuss the proposal on the [Origin Governance Forum](https://governance.originprotocol.com/) and share the link on the [Origin Protocol Discord server](https://originprotocol.com/discord) under the #governance channel for maximum visibility *(1-4 weeks of discussion recommended)* 4. Submit the proposal on Snapshot for a signaling vote 5. Vote for the implementation to be executed Feel free to use one of the [templates](/resources/governance-templates.md) as a guide for writing governance proposals #### Here are the parameters currently configured on the governance contract: | Name | Value | Description | | --------------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Voting delay | 24 hours | How soon the voting period begins following the submission of a proposal - can be used to enforce a delay after a proposal is published for users to buy tokens, or delegate their votes | | Voting period | 48 hours | The window of time for votes to be cast following the end of the voting delay | | Proposal threshold | 100,000 xOGN | The minimum number of tokens required for an account to be eligible to submit a proposal | | Quorum | 20% of xOGN supply | The minimum number of votes needed for a proposal to succeed (assuming a majority of them are in support of the proposal) | | Late quorum extension | 11,520 blocks (\~1.6 days) | The amount of time required to pass from when a proposal reaches quorum until its voting period ends | | Timelock delay | 172,800 seconds (2 days) | The minimum amount of time required after the end of the voting period before a proposal can be executed and take effect | ## Guardians Guardian multisigs can act without a timelock delay for time-sensitive operations: depositing and withdrawing from strategies, adjusting vault buffers, pausing deposits and redeems, swapping collateral, and managing rebasing. These functions require the multisig threshold but not a governance vote or timelock period. The Guardian multi-sig can do the following actions on the vault: * depositToStrategy - deposit multiple assets from the vault into the strategy. * withdrawFromStrategy - withdraw multiple assets from the strategy to the vault. * setVaultBuffer - adjust the amount of funds held outside strategies for cheaper redeems. * setAssetDefaultStrategy - which strategy mints and redeems pull from for a particular strategy * withdrawAllFromStrategy - remove funds from a single strategy and send them to the vault * withdrawAllFromStrategies - remove funds from all active strategies and send them to the vault * pauseRebase - pause all rebases * pauseCapital - pause all mints and redeems * unpauseCapital - allow all mints and redeems * swapCollateral - swaps collateral assets sitting in the vault ### Governance & Guardian Addresses
RoleChainAddressConfiguration
ProposerEthereum0xbe2AB3d3d8F6a32b96414ebbd865dBD276d3d895-of-8 Safe
ProposerBase0x92A19381444A001d62cE67BaFF066fA1111d7205-of-8 Safe
ProposerSonic0xAdDEA7933Db7d83855786EB43a238111C69B00b5-of-8 Safe
ProposerArbitrum0xfD1383fb4eE74ED9D83F2cbC67507bA6Eac2895-of-8 Safe
GuardianEthereum0xF14BBdf064E3F67f51cd9BD646aE3716aD938F2-of-9 Safe
GuardianBase0x28bce2eE5775B652D92bB7c2891A89F03661971-of-2 Safe
GuardianSonic0x63cdd3072F25664eeC6FAEFf6dAeB668Ea4de92-of-9 Safe
--- # Agent Instructions: 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: ``` GET https://docs.originprotocol.com/ogn/governance.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.