Comment on page
Architecture
This section describes provides a high-level overview regarding the technical implementation of Mirror Protocol.
Even with a thorough understanding of Mirror Protocol, it is highly recommended to interact with Mirror through client channels such as the Mirror Web App or Mirror.js.
The source code for Mirror smart contracts can be found on GitHub. Mirror Protocol is deployed with one of each of the following contracts, organized through the Factory.
Contract | Function |
|---|---|
Gathers protocol fees incurred from CDP withdrawals and liquidations and send to Gov | |
Central directory that organizes the various component contracts of Mirror | |
Allows other Mirror contracts to be controlled by decentralized governance Distributes MIR received from Collector to MIR stakers and voters | |
Contract owned by Gov which enables contract migrations and admin actions through Mirror governance consensus. | |
Handles both long and short CDP creation, management, and liquidation | |
Responsible for locking up UST from short CDP | |
Provides an interface for registering new oracle provider and fetching asset prices with highest priority | |
Feeds price and collateral multiplier for each collateral asset type | |
Distributes MIR rewards from block reward to LP and sLP stakers | |
Registers and executes swap orders at submitted limit price and amount |
The Mirror Token (MIR) is a Terraswap CW20 Token instance that is created during the initial bootstrapping of the protocol and is registered with the Mirror Protocol core contracts.
When new mAssets are whitelisted, Mirror Protocol will create the following contract instances:
- Terraswap CW20 Token for the new mAsset
- Terraswap Pair for the new mAsset against UST
- Terraswap CW20 Token for the new mAsset's LP Token
- Terraswap CW20 Token for the new mAsset's sLP Token
Last modified 1yr ago