Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agree on governance parameters #295

Closed
micahalcorn opened this issue Aug 2, 2022 · 8 comments
Closed

Agree on governance parameters #295

micahalcorn opened this issue Aug 2, 2022 · 8 comments
Assignees
Labels
enhancement New feature or request P1 Large amount of significant user impact, a meaningful feature is broken
Milestone

Comments

@micahalcorn
Copy link
Member

Let's take inventory of each parameter that controls the on-chain governance system. This includes voting period, timelock, quorum requirement, proposal threshold, etc.

@micahalcorn micahalcorn added enhancement New feature or request P1 Large amount of significant user impact, a meaningful feature is broken labels Aug 2, 2022
@micahalcorn micahalcorn added this to the Sprint 32 milestone Aug 2, 2022
@DanielVF
Copy link
Member

DanielVF commented Aug 5, 2022

Governor Configs

name value
initial voting delay 1 block
initial voting period 32,727 blocks - approx 5.11 days
initial Proposal Threshold 5,000,000 veOGV
quorumPercent 4% of veOGV supply
late quorum extension 5760 blocks - approx 0.90 days
time lock delay 2 days

@DanielVF DanielVF assigned micahalcorn and unassigned DanielVF Aug 5, 2022
@joshfraser
Copy link
Member

It would be helpful to take inventory of what numbers other established governance systems are using. For example, I know Compound requires 0.25% to issue a vote and 4% for a quorum. What about other protocols? Let's learn from those who have gone before. My initial reaction is that 4% feels rather low from a security standpoint.

@Techmoen
Copy link

Techmoen commented Aug 12, 2022

In simple terms, at 4%, around 0.4% of the veOGV balance in OGV would be required to reach quorum currently. At the current level of 9.7B veOGV, this would require (1/10.5) * 4% * 9.7B = ~37M OGV. With 478M OGV in circulation currently, this is approximately 8% of the circulating supply, the main question is how much of this circulating supply is liquid (ie. on exchanges).

If there were to be a coordinated governance attack, purchases of OGV would occur on a DEX to avoid KYC. Based on Uniswap liquidity alone, 4% would be secure as not enough liquidity currently exists there. However, as someone buys in on Uniswap, market makers will step in and help satisfy the liquidity required on the DEX. If someone were to slowly accumulate OGV in this way, then you have to assume total liquidity across all exchanges (CEX and DEX) would be in play. From this, you can then estimate the slippage and arrive at a total cost to reach quorum.

For example: assuming about half of the circulating supply is liquid (~240M OGV), and that to accumulate 37M OGV would incur total price slippage of 500%, it would cost approximately $0.007145 * 5 * 37M = $1.32M to reach quorum. This would be fairly expensive with no guarantee of success, as the Origin team will have other controls in place.

@micahalcorn
Copy link
Member Author

@Techmoen thanks for digging into this. Circulating supply is actually almost double the figure that you have here. I suspect that you referenced CoinGecko or CoinMarketCap, which were wrong. We're working on getting those updated. The source of truth will be our own endpoint at https://www.originprotocol.com/circulating-ogv.

@micahalcorn
Copy link
Member Author

Current Compound parameters

name value
Voting delay 13,140 blocks (2 days)
Voting period 19,710 blocks - (3 days)
Proposal threshold 25,000 COMP ($1.5M, 0.37% of circulating supply)
Quorum votes 400,000 COMP ($23.5M, 5.83% of circulating supply)
Timelock 2 days

@micahalcorn micahalcorn modified the milestones: Sprint 32, Sprint 33 Aug 22, 2022
@micahalcorn
Copy link
Member Author

Here's where we ended up last week with one open question about the quorum requirement needing to be higher until we have sufficient monitoring:

https://docs.google.com/spreadsheets/d/1YLKGDuxw-xq9utjjtvZcHu8IvQ2cV9nNZlvFURIHA00/edit

@Techmoen
Copy link

Here's where we ended up last week with one open question about the quorum requirement needing to be higher until we have sufficient monitoring:

https://docs.google.com/spreadsheets/d/1YLKGDuxw-xq9utjjtvZcHu8IvQ2cV9nNZlvFURIHA00/edit

10% veOGV (which is also over 10% of circulating OGV market cap ~87M OGV) should be safe. It would require far beyond the $ estimate in the spreadsheet because of slippage as there is only 11M OGV on Uniswap total, so I think that effectively makes it impossible to carry out some kind of attack for the time being. The main drawback of setting it at 10% is that it will require more participation to pass things without a high rate of delegation or whale participation.

@micahalcorn
Copy link
Member Author

Per the discussion in Discord, let's proceed with a 20% quorum requirement. Here are the final parameters:

name value
initial voting delay 1 block
initial voting period 3 days
initial Proposal Threshold 10,000,000 veOGV
quorumPercent 20% of veOGV supply
late quorum extension 2 days
time lock delay 2 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P1 Large amount of significant user impact, a meaningful feature is broken
Projects
Status: Done
Development

No branches or pull requests

4 participants