OriginProtocol / OriginProtocol/origin-dollar

Public Strategist Voting Tools

Open
#897 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement governance P4
Dominant language
Solidity
Stars
152
Forks
115
Avg merge
3d 20h
Merged PRs (30d)
17

Description

Currently a voter makes decisions about how to vote for weekly snapshot strategist actions by looking at a spreadsheet showing the current allocation and the current APY's.

While this is much better than the users needing to look these things up themselves. It still doesn't let users know about the actual behaviors and gotchas of the OUSD strategies. Off the top of my head:

  • It cost gas money for each move into or out of a strategy during a reallocation
  • There can be slippage (mostly negative, but occasionally positive) for moving in or out of convex
  • Moving into or out of Convex in the right proportions can almost zero slippage fees
  • No one can withdraw more than the smallest default strategy (relative to the proportion of coins)
  • Only some strategies can be default strategies
  • Sometimes we need to change default strategies
  • Given the size of our funds, we could possibly be changing the APY of Compound/AAVE strategies. If we move a lot of funds into AAVE, the APY on that coin will go down, and if we move a lot out of a strategy, the APY will go up in the strategy we are leaving.
  • Compound and AAVE USDT only have so much liquidity at a given time - we might not be able to withdraw everything we have in there at one shot.

I'm assuming we would want some kind of interactive system that shows the effects of doing these moves.

Ideally users would be able to see the effects and costs of allocation changes, beyond just changing the APY. This would make it easy to see that moving 250 million dollars to funds Compound USDT might cost 100K slippage, plus crater the APY there to near zero.

It would be good to default to showing things the way they are, to encourage leaving things the way they are unless there is a good reason.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the current spreadsheet and weekly snapshot strategist-action process, then define an interactive view that represents gas costs, slippage, APY changes, withdrawal liquidity, and default strategies; done means users can compare allocation changes with their effects and costs.

Written by the indexing model from the issue text.

Assessment

Tech stack
solidity
Domain
blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.