Reserve Pool

Users can acquire OURO (the inflation-proof asset) by depositing crypto assets of equivalent value into Reserve Pool. 
For instance, when BNB is trading at 1000 BUSD on secondary markets, a user can deposit his 10 BNB into the pool, and in return acquire 10,000 BUSD worth of OURO. 
Assuming this 10 BNB is the only asset in the pool when the price of BNB falls to 900 BUSD, the pool would not have sufficient assets to back up OURO issued (10,000 BUSD worth of OURO issued, but only 9,000 BUSD worth of BNB held), the system would mint new OGS tokens (Ouro Governance Share), and sell them on secondary markets to acquire enough collateral for the pool. 

When the price of BNB increases, however, the system would contain excessive collateral relative to the amount of OURO issued. In this case, at least 70% of the extra collateral would be used to 1. buyback OGS on secondary markets for a token burn (50%), and 2. to form an insurance fund (50%), while at most 30% of excess collateral would be reserved to support an increase in the Default Exchange Price of OURO. 
Normally, users who deposit assets or return OURO will trigger a rebase. if no user makes any mint/burn OURO action, the system rebase will be triggered once per day 
Users can also acquire assets held by the pool by depositing OURO of equivalent value. Deposited OURO will subsequently be burnt. 
When a user is requesting to deposit OURO and receive an asset that the system supports but does not have enough stored to fulfill this request, the system will swap the requested asset on secondary markets for the user. For instance, when a user is requesting to swap 1000 BUSD worth of BNB, but the pool has only 500 BUSD worth of BNB stored, the system would purchase BNB on Pancakeswap with the user’s OURO. The user will be responsible for any fees and slippage incurred.

Governance & Operations - Previous

Ouro Governance Share (OGS)

Next - Platform Components

System Buffer

Last modified 7mo ago

Copy link