MOGA: Make Onomy Great Again - A Restructuring Proposal
This post is providing a pathway forward for the Onomy DAO to Make Onomy Great Again (MOGA). If you are not yet up to speed, you may catch up by reading this.
MOGA calls for a complete restructuring and rebuilding of Onomy, done right from the ground up with proven modules and providing a clear path to product deliveries. Moreover, long-overdue upgrades to the SDK versioning to be in line with best practices, many bug fixes, and directly translate to metrics like faster block times and compatibilities that lead to highly competitive products.
The Internet Financial System (IFS) the DAO has long written about and worked toward stands ready to be delivered, built on a complete rework of Onomyâs principles, values, culture, and community-led transparency.
We will not sugarcoat the situation, this journey will indeed present new challenges; but should the DAO agree to move forward with the resources and talent that stand ready to support, we can make it happen if we all do our part. At least a very strong shot at it. It only takes a little bit of orchestration amongst the talent here.
I. The Aionic Systems Proposed Reserve
- Opaque descriptions, no documentation
- Buy And Burn of NOM using Liquidated Collateral
- This mechanism and the handling of the liquidated collateral itself is not provided. Additionally, thereâs still debt.
- No Outside Oracle Problem (ONEX Price Feeds)
- The AS model uses ONEX for pricing data. Without massive liquidity, small orders will move the market enough to liquidate vaults. After the recent findings and ONEX exploit, we do not imagine LPs willing to commit substantial liquidity on the current ONEX model. No outside oracles creates a situation of extreme risk for vault owners (issuers).
II. An Alternate Pathway for The Reserve
- Rather than try to understand Aionic Systemâs undocumented Reserve model or try to address what we consider as design flaws, we propose to utilize existing and proven modules that can be adapted for Onomyâs purposes. For this, we propose to fork and adapt Agoricâs IST module, which is an implementation of MakerDAOâs CDP (DAI) model for issuing stablecoins with approved collateral types.
- In discussions with Onomyâs developer ecosystem, talent has come forward to offer a statement of work for the DAO to consider for this implementation.
Current IST module
- Written in JavaScript so we need to re-implement it in go as a cosmos-sdk module for using it.
- Components include:
- Oracle handler - provided via Skip Connect, an in-protocol oracle.
-
VaultFactory - collateralized debt positions (CDP), issuing stablecoins and management of CDPs.
-
PSM - Parity Stability Module
-
Reserve - Asset reserve for all accumulated fees of the system
-
A deeper look at the protocol design can be viewed on the whitepaper here.
The Scope
The goal is to develop a stablecoin protocol based on the Agoric IST model. This protocol will allow users to mint multiple types of currency and utilize various DAO-approved assets, such as NOM, ATOM, et al, as collateral. Each collateral asset will have different collateral ratios.
Oracle Module
This module is designed for handling oracle data as the protocol needs collateral asset prices (ATOM, OSMO, NOM) based on multiple currencies (USD, EUR, JPY). For security purpose, this data should be combined from multiple sources:
- Onomyâs validators can implement a sidecar that requires validators to submit oracle data via a price feeder. We can reference the oracle mechanism from Slinky, now named Skip Connect, which is a general purpose price oracle leveraging ABCI++.
- Other oracle blockchains may be incorporated - like Band, Stork, etc. Band protocol supports querying oracle data though IBC.
Vault
Following the vault design, users can deposit their collateral (limit on community approved crypto-assets) to mint stablecoins. They can mint more than just one currency type (USD, EUR, JPY) as voted by the DAO with multiple collateral types (ATOM, OSMO, NOM). The amount of stablecoins that can be minted is determined by the value of the collateral in the vault, and the collateralization ratio established for that collateral type. Users can retrieve their collateral by paying back the stablecoin that was borrowed plus the stability fee, which gets allocated to the Reserve Treasury and becomes protocol-governed liquidity.
User Flow:
- Create Vault: users can create a vault and deposit accepted collateral to mint stablecoins.
- Adjust Vault: users can adjust assets in their vault by depositing more assets or withdrawing assets. This allows the user to adjust their vaultâs collateralization ratio.
- Close Vault: users can pay back stable coins and close their vault to receive their collateral asset they initially deposited.
Note that vaults could be liquidated if its collateral rate is below the liquidation threshold.
Liquidation
Given the volatility of crypto-asset prices, a collateralization ratio is set for each collateral type. If the collateral value drops below the liquidation threshold, the protocol initiates the liquidation of the collateral through an on-chain auction. The auction sells collateral assets to cover the outstanding stablecoin debt in the vault, and charges a liquidation penalty to the vault. Depending on the result of the auction, excess assets may be returned to vault holders, prioritized by their collateralization ratio at the time of liquidation:
- Matching collateral: collateral = debt
- Liquidation penalty : Collateral * Liquidation penalty
- Returned to user = Excess collateral - Liquidation penalty
There are 2 cases when a liquidation happens:
- Auction raises enough stablecoins to cover: In this case, we handle it normally and donât need to use the reserve. Stablecoin raised by the auction are burned to reduce debt at a 1:1 ratio. The protocol takes the liquidation penalty and sends it to a reserve while excess collateral will be sent to the vaultâs owner.
- Auction does not raise enough to cover stablecoin debt: This situation led to a shortfall, necessitating the use of Reserve Treasury to cover the debt.
Reserve Treasury
Onomyâs DAO maintains and controls the Reserve Treasury. The Reserve Treasury grows via fees collected from the system. It may be used to provide additional collateral to cover any shortfall that may result from liquidation auctions.
Auction module
The auction module handles the execution of collateral liquidation auctions, allowing users to bid on liquidated vault collateral. Onomyâs auction process would follow the descending clock auction model implemented in IST. This auction starts with a high initial price, which decreases over time until a bid is placed or the auction reaches its floor price. For collateral liquidation, the auction begins at or above the current oracle price rather than the locked price that triggered the liquidation. This approach helps ensure that the collateral is sold at fair market value, minimizing losses for both the protocol and the vault owner.
Parity Stability Module (PSM)
The Parity Stability Module (PSM) enables trading between vault-issued stablecoins and approved external stablecoins like USDC or USDT (up to a governance-determined limit). Users can provide USDT, for example, and receive newly-minted oUSD, rather than minting oUSD through a vault. This provides low cost and timely arbitrage opportunities whenever vault-issued stablecoins trades away from parity with the USD and other national currencies.
Parameters
Parameters for vaults are set by governance, and may adjust to meet changing economic circumstances and risk factors.
Vault parameters include:
- Debt limits per collateral type
- Collateral ratio
- Liquidation threshold
- Minting fee
- Stability fee
- Liquidation penalty
Peg Mechanism
In the description below, a placeholder name $oUSD is used.
Soft Peg: $oUSD will maintain a soft peg based on market demand:
- When $oUSD is greater than $1, users will be incentivized to deposit collateral assets to mint more $oUSD and sell it at a price > $1, gradually bringing $oUSD back to $1.
- When $oUSD is less than $1, users/arbitrageurs will be incentivized to buy $oUSD on the open market to repay deposits and receive back collateral / LSDs, thereby incentivizing movement of $oUSD closer to the $1 peg.
Hard Peg: With a hard peg, $oUSD will maintain its price with the minting fee, which is the rate calculated for borrowing and redemption. The borrowing fee will include the base rate.
- When $oUSD is less than $1, the protocol can increase the minting fee, making borrowing less attractive, thereby reducing the rate of increase in the supply of R, giving more time for the soft peg mechanisms to work. This increases the reserve funding to provide additional collateral where needed.
- When $oUSD is greater than $1, the minting fee will decrease according to a predetermined formula to encourage more minters to operate, leading to additional supply of $oUSD and consequently lowering the price of $oUSD.
The first line of defense is vault overcollateralization; users manage their vaults to ensure that they have enough collateral to cover their outstanding stablecoins minted. If the value of the collateral vaults drops below the liquidation threshold, the Protocol will liquidate the vault collateral. The Reserve Treasury is used to cover any remaining shortfall. If a shortfall still remains, additional fees flowing into the Reserve Pool are used as an additional backstop. In extreme circumstances, the Onomy DAO can vote to utilize Treasury NOM to support outstanding $oUSD.
III. Timelines and Budget
The total time estimated is 16 weeks, whereby a highly detailed design document is to be provided with all adaptations from DAO discussions by Week 3. The remaining 12-13 weeks are for completing all the detailed modules and mechanisms listed to provide a production ready version for testnet, followed by mainnet shortly thereafter. This will also include protocol user and system documentation.
The estimated price is $200,000 to complete this scope of work. We are speaking with the developer ecosystem to break down this estimate into milestones that the DAO can fund upon completion. Note that none of this funding goes to the founding team and the work would be contributed by developers and validators in the ecosystem. These time estimates and costs are their quotes to the DAO.
An obstacle could be that at current prices, a substantial amount of NOM is required out of the DAO Treasury. By breaking down the total cost into milestone based payments, we can better utilize the NOM in Treasury and enable time for project and ecosystem growth that may lead to requiring far less total NOM. Additionally, the dev contributors are requesting cash payment to cover operational items that would require USD.
Additionally, the DAO should look to utilize the Treasury NOM responsibly and take care not to sell on exchanges. Treasury tokens may be offered by the DAO via discount-to-market OTC price deals bid on by DAO members. This funds the proposal and gets long-term stakeholders involved. The only risk is not finding willing counterparties.
We will inquire with the developer ecosystem partners on the appetite for all-token or partial-token payment for the services.
IV. The Future of Onomyâs IFS - Building Beyond Reserve
- Phasing out of ONEX Chain, ONEX coin, and the Market Module (ONEX logic). Focus all activity on NOM and the Parent Onomy Chain. Upgrade the Cosmos SDK versioning used to the latest, improve block times.
- New Swap DEX powered via liquidity aggregation, enabling Onomy community and all users to swap any token for any token across all major ecosystems and chains via an aggregation of all bridges (IBC, Axelar, and more). This integration anticipates enabling any user from other ecosystems to easily onboard into NOM and the Onomy ecosystem without the need for CEXs.
- New Orderbook functionality focused on FX markets via the Reserve stablecoins
- Hummingbot integration for High Frequency Trading
- Incentivize net-new creations built in the ecosystem (new apps, RWA markets, integrations, etc)
V. Ongoing Operational Funding for Founding Team (excluding AS)
Depending on the result of the MOGA Proposal, DAO, Community, and Partner feedback; we may look to the DAO to offer what they think is reasonable for continued funding out of the Treasury should you all agree on the path forward. You choose for us if the time comes and we will detail our contributions.
Note, we have begun the transition to take over front-end interface nodes and hosting for ongoing maintenance.
VI. Aionic Systems Involvement
Community discussions about ASâs proposal and the response has led many contributors and members of the DAO to believe that if Aionic Systems keeps its existing stake in Onomy, it imperils any efforts made to a new path forward as deposits into exchanges will continue if history teaches us any lesson. Importantly, integrity is important. Can we honestly ask partners to dedicate time and resources, or the DAO to fund new things with such a risk as has been identified?
Additionally, this leads to significantly less funding opportunities as finding OTC partners to cover operational costs, or this proposal, will prove extremely difficult.
To this end, we are compiling options discussed in the community so far - it is on you, the DAO, to make your voices heard and vote for the path forward once governance proposals in this direction are made.
1. Return half of the NOM holdings to the DAO treasury & prolong vesting for the remaining 50%
This strategy reduces potential impact by 50%, whilst giving the Onomy ecosystem enough time to breathe before the remaining 50% of tokens are unvested. It also protects part of ASâ founding stake, allowing him to enjoy upside as Onomy grows for the work done thus far even if thereâs no involvement going forward.
This requires an immediate return of 50% out of â13M NOM, and a 1-year cliff with an additional 2-year vest following.
2. Vest all outstanding tokens to assure Onomyâs path forward
This strategy gives Onomy enough time to reorganize, build, and deploy the current roadmap, but poses the risk of excessive selling once the tokens are unvested. However, if the project is successful, enough liquidity may exist in future to support the sells.
This proposes a 2-year cliff with an additional 2-year vest following.
3. Return all outstanding tokens to the DAO treasury.
Perhaps the most extreme option, this strategy dictates that all outstanding tokens controlled by AS are returned to the DAO Treasury. This effectively cuts ties altogether with AS, but eliminates any potential upside for the individual.
4. AS retains 100% of their tokens. Onomy continues on whatever AS builds, even if it means losing core talent and contributors.
DAO Members, partners, and contributors: We kindly ask for your thoughts on this moral quandary - we believe that should AS keep all tokens, additional effort would be in vain, preventing the protocolâs growth. Indeed, Onomy was never built on the premise of token price, but instead on the ideal of building products that improve cryptoâs status quo, helping it cross the chasm into long-term, mainstream usage by anyone and everyone.
However, as weâve been shown time and time again, and granted the actions that have recently come to light, the invisible hand of the market prices the success of a protocol on its token, should that token exist. Transforming into a non-token protocol is not an option at this stage, and NOM remains an integral part of the Onomy Ecosystem. Its utility can flourish if market confidence can be maintained and not affected by irresponsible sells by the largest stakeholders.
Your Choice
Nomads, it is time to discuss this proposal and make your choices.
Please give us feedback on the following questions:
- Do you agree with the path forward to build out the Onomy Reserve and the costs associated with it, led by non-founding contributing entities and validators?
- Are you willing to support the founding team with NOM grants (based on subsequent milestone-based DAO funding requests) to maintain the front-end, conduct business development, design products, acquire new users, whilst managing the relationships with the other contributing entities?
- Which of the three options presented to mitigate the Aionic System risks are you most happy with? The options are:
A) Return 50% to treasury & vest rest
B) Vest all
C) Return all to the Treasury
D) Attempt to continue as is
Your feedback, support, and suggestions are essential to pushing Onomy forward.