- Edited
For those concerned that this proposal breaches the framework set out in OIP-18, it doesn't. It just takes us to the lower end of the framework range given current OHM issuance.
For those mentally thinking there would be a step-change reduction in APY once 10m tokens had been issued (which I thought), this proposal is (practically speaking) only a minor adjustment to that model.
Assume the snapshot is completed and APY reduction implemented around 27 DEC. A 4 week linear reduction in APY goes into effect, finishing around 20 January. Token issuance drops over the 4 weeks the APY reduction is being implemented, but not that much. We might end up with 8m tokens or so (rather than 10m) by the end of JAN 2022. I am too lazy to do the math right now but it's not that hard to model.
My point is only that the change suggested here is both OIP-18 'compliant' and only a modest variation from the mental model most OHMies had likely created for themselves through a casual and inaccurate reading of OIP-18 (a group in which I include myself).
So I support this, and I think all OHMies (who want to) can support it without worrying about any contravention of OIP-18.
Frankly, I am more concerned about our slow v2 migration, our fragmenting liquidity (as we go cross-chain) and our bond pause. Bonds are absurdly profitable and a great way to grow the community-- from a revenue standpoint they blow away Treasury earnings, LP fees and PRO and they are critical to our ongoing success and user adoption. The sooner we have functional front-ends running for bonding and marketing on every target chain, the better for all OHMies.