LLM Notice: This documentation site supports content negotiation for AI agents. Request any page with Accept: text/markdown or Accept: text/plain header to receive Markdown instead of HTML. Alternatively, append ?format=md to any URL. All markdown files are available at /md/ prefix paths. For all content in one file, visit /llms-full.txt
Skip to main content

MOET Stability and Risk Management

This document analyzes MOET's stability mechanisms, risk factors, and the safety measures that protect its $1 peg within the FCM ecosystem.

Current Implementation Status

Mock Token Status

The current MOET implementation is explicitly a "mock version for testing purposes" and lacks active stability mechanisms. This analysis describes the intended design for production deployment and identifies gaps in the current implementation.

Missing in Current Implementation:

  • Active MOET/USD price oracle monitoring
  • Algorithmic supply adjustments based on peg deviation
  • Reserve fund for redemptions
  • Governance controls for economic parameters
  • Emergency circuit breakers for extreme scenarios

Present in Current Implementation:

  • Over-collateralization requirements
  • Liquidation mechanisms
  • Interest rate adjustments via utilization
  • Mint-and-burn supply model

Stability Mechanisms

Over-Collateralization

The primary stability mechanism is requiring all MOET debt to be backed by excess collateral.

Collateralization Requirements:


_11
Standard Position:
_11
├── Collateral Factor (CF): 0.8 (80% of value usable)
_11
├── Target Health Factor (HF): 1.3
_11
├── Required Collateral: CF × HF = 0.8 × 1.3 = 1.04
_11
└── Collateralization Ratio: 1 / 0.8 × 1.3 = 162.5%
_11
_11
For Every 1 MOET Borrowed:
_11
├── Effective Collateral Required: $1.30
_11
├── Total Collateral Required: $1.625
_11
├── Safety Buffer: $0.625 (38.5%)
_11
└── Price Drop Tolerance: 38.5% before liquidation threshold

Collateralization by Asset:

CollateralCFTarget HFMin CollateralizationLiquidation Buffer
FLOW0.81.3162.5%38.5% price drop
stFLOW0.851.3152.9%34.6% price drop
USDC0.91.3144.4%30.8% price drop
wBTC0.751.3173.3%42.3% price drop
wETH0.751.3173.3%42.3% price drop

Why Over-Collateralization Provides Stability:

  1. Redemption Backing: Every MOET can theoretically be redeemed for >$1 worth of collateral
  2. Liquidation Buffer: Provides time for liquidators to act before insolvency
  3. Market Confidence: Users trust MOET is backed by real, valuable assets
  4. Arbitrage Floor: If MOET < $1, arbitrageurs can profit by buying MOET to repay debt and unlock collateral

Liquidation System

Liquidations maintain system solvency by clearing bad debt before positions become insolvent.

Liquidation Threshold:


_13
Position Becomes Liquidatable When:
_13
Health Factor < 1.0
_13
_13
Where:
_13
HF = (Σ CollateralValue × CollateralFactor) / TotalDebt
_13
_13
Example Liquidatable Position:
_13
├── Collateral: 1000 FLOW @ $0.60 = $600
_13
├── Collateral Factor: 0.8
_13
├── Effective Collateral: $600 × 0.8 = $480
_13
├── Debt: 615.38 MOET
_13
├── Health Factor: $480 / $615.38 = 0.78 < 1.0 ⚠️
_13
└── Status: Liquidatable

Liquidation Process:


_29
Step 1: Detection
_29
├── Keeper bots monitor: All position health factors
_29
├── Alert triggers: HF < 1.0
_29
├── Keeper prepares: MOET for liquidation
_29
└── Submits: Liquidation transaction
_29
_29
Step 2: Collateral Seizure Calculation
_29
├── Formula: CollateralSeized = (DebtRepaid × (1 + Bonus)) / PriceCollateral
_29
├── Example: (200 MOET × 1.05) / $0.60 = 350 FLOW
_29
├── Liquidator profit: 5% (from bonus)
_29
└── Incentive: Encourages fast liquidation
_29
_29
Step 3: Debt Repayment
_29
├── Liquidator provides: 200 MOET
_29
├── Position debt reduced: 615.38 → 415.38 MOET
_29
├── MOET burned: 200 tokens
_29
└── Supply reduced: Improves system collateralization
_29
_29
Step 4: Collateral Transfer
_29
├── Seized collateral: 350 FLOW
_29
├── Transferred to: Liquidator
_29
├── Remaining collateral: 650 FLOW
_29
└── Position still exists: Can be liquidated further if HF still < 1.0
_29
_29
System Impact:
_29
├── Bad debt cleared: Before insolvency
_29
├── Supply reduced: Burned MOET improves backing ratio
_29
├── Liquidator profit: Creates MOET demand (need MOET to liquidate)
_29
└── Peg support: MOET needed for profitable liquidations

Partial Liquidation:


_13
Current Implementation:
_13
├── Liquidators can repay: Any amount of debt
_13
├── Goal: Restore HF to healthy level (typically 1.05)
_13
├── Avoids: Complete position closure
_13
└── Benefits: User keeps remaining collateral, lower gas costs
_13
_13
Example Partial Liquidation:
_13
├── Initial: 1000 FLOW, 615.38 MOET debt, HF = 0.78
_13
├── Liquidator repays: 200 MOET (not full debt)
_13
├── New state: 650 FLOW, 415.38 MOET debt
_13
├── New HF: (650 × $0.60 × 0.8) / 415.38 = 0.75
_13
├── Still liquidatable: Additional liquidations needed
_13
└── Continues: Until HF restored above 1.0

Interest Rate-Based Stability

Utilization-driven interest rates create economic incentives that stabilize supply and demand.

Rate Mechanism:


_11
High Utilization → High Rates → Incentives:
_11
├── Borrow Side: Expensive MOET discourages new borrowing
_11
├── Repay Side: High cost incentivizes debt repayment
_11
├── Supply Side: High yields attract MOET deposits
_11
└── Result: Utilization decreases toward optimal
_11
_11
Low Utilization → Low Rates → Incentives:
_11
├── Borrow Side: Cheap MOET encourages new borrowing
_11
├── Repay Side: Low cost reduces urgency to repay
_11
├── Supply Side: Low yields discourage new deposits
_11
└── Result: Utilization increases toward optimal

Example Stabilization Cycle:


_29
Phase 1: High Demand
_29
├── Utilization: 92%
_29
├── Interest Rate: 45% APY
_29
├── MOET Price: $1.03 (high demand, premium)
_29
├── Borrower Response: "Too expensive, I'll repay early"
_29
├── Lender Response: "Great returns, I'll deposit more"
_29
└── Effect: Supply ↑, Demand ↓, Utilization → 85%
_29
_29
Phase 2: Market Adjustment
_29
├── Utilization: 85%
_29
├── Interest Rate: 18% APY (dropped)
_29
├── MOET Price: $1.00 (normalized)
_29
├── Market: Balanced state
_29
└── Stable: Rates and price
_29
_29
Phase 3: Low Demand
_29
├── Utilization: 65%
_29
├── Interest Rate: 7% APY
_29
├── MOET Price: $0.98 (low demand, slight discount)
_29
├── Borrower Response: "Cheap money, I'll borrow more"
_29
├── Lender Response: "Low returns, I'll withdraw"
_29
└── Effect: Supply ↓, Demand ↑, Utilization → 75%
_29
_29
Phase 4: Equilibrium
_29
├── Utilization: 75%
_29
├── Interest Rate: 9% APY
_29
├── MOET Price: $1.00
_29
├── Market: Optimal balance
_29
└── Stable: Long-term equilibrium

Arbitrage Mechanisms

Price deviations from $1 create profitable arbitrage opportunities that naturally restore the peg.

MOET Trading Above $1 (e.g., $1.05):


_30
Arbitrage Strategy:
_30
Step 1: Borrow MOET
_30
├── Deposit: $1,625 FLOW collateral
_30
├── Borrow: 1,000 MOET (valued at $1,000 on-protocol)
_30
├── Cost: Interest on 1,000 MOET debt
_30
└── Capital: 1,000 MOET in hand
_30
_30
Step 2: Sell MOET on Market
_30
├── Market price: $1.05
_30
├── Sell: 1,000 MOET for $1,050
_30
├── Profit captured: $50 immediate
_30
└── Hold: $1,050 stablecoins
_30
_30
Step 3: Wait for Peg Restoration
_30
├── MOET price: Returns to $1.00
_30
├── Or: Hold position and earn on $1,050
_30
└── Later repay: 1,000 MOET debt
_30
_30
Step 4: Close Position
_30
├── Buy back: 1,000 MOET at $1.00 = $1,000
_30
├── Repay debt: 1,000 MOET to ALP
_30
├── Withdraw: $1,625 FLOW collateral
_30
├── Net profit: $1,050 - $1,000 - interest ≈ $45
_30
└── Market impact: Selling pressure pushed MOET → $1.00
_30
_30
Arbitrageur Incentive:
_30
├── Risk-free profit: When MOET > $1
_30
├── Increased supply: More MOET on market (from borrowing)
_30
├── Selling pressure: Drives price down
_30
└── Peg restored: MOET returns to $1

MOET Trading Below $1 (e.g., $0.95):


_31
Arbitrage Strategy:
_31
Step 1: Buy Discounted MOET
_31
├── Market price: $0.95
_31
├── Buy: 1,000 MOET for $950
_31
├── Savings: $50 vs. $1 peg
_31
└── Capital: 1,000 MOET in hand
_31
_31
Step 2: Repay Existing Debt
_31
├── Existing position: 1,000 MOET debt (valued at $1,000 on-protocol)
_31
├── Repay using: 1,000 MOET purchased for $950
_31
├── Debt cleared: 1,000 MOET
_31
└── Savings realized: $50
_31
_31
Step 3: Unlock Collateral
_31
├── Debt: Fully repaid
_31
├── Health Factor: Infinite (no debt)
_31
├── Withdraw: All collateral
_31
└── Collateral freed: Can be used elsewhere
_31
_31
Alternative Strategy (Profitable Liquidations):
_31
├── Buy: 1,000 MOET for $950
_31
├── Liquidate: Underwater positions
_31
├── Receive: Collateral worth $1,050 (5% bonus)
_31
├── Net profit: $1,050 - $950 = $100
_31
└── Market impact: Buying pressure pushed MOET → $1.00
_31
_31
Arbitrageur Incentive:
_31
├── Discounted debt repayment: When MOET < $1
_31
├── Profitable liquidations: Higher margins
_31
├── Buying pressure: Drives price up
_31
└── Peg restored: MOET returns to $1

Risk Factors and Mitigation

Depeg Risk

Risk: MOET trades significantly away from $1, breaking user confidence.

Causes:


_17
Supply-Side Shock:
_17
├── Sudden collateral price crash
_17
├── Mass liquidations → large MOET sell pressure
_17
├── Liquidators dump MOET on market
_17
└── Price spirals: MOET → $0.80
_17
_17
Demand-Side Shock:
_17
├── Loss of confidence in protocol
_17
├── Users rush to repay debt
_17
├── High MOET demand → price spike
_17
└── Price spikes: MOET → $1.20
_17
_17
Oracle Failure:
_17
├── Oracle reports incorrect prices
_17
├── Wrong collateral valuations
_17
├── Inappropriate liquidations or minting
_17
└── System destabilization

Mitigation Strategies:


_12
Current (Implicit):
_12
├── Over-collateralization: Provides 38-42% buffer
_12
├── Gradual liquidations: Prevents sudden supply shocks
_12
├── Interest rate adjustments: Incentivize balance
_12
└── Arbitrage: Profit-seeking restores peg
_12
_12
Needed for Production:
_12
├── MOET/USD Price Feed: Active monitoring
_12
├── Circuit Breakers: Pause minting/borrowing during extreme volatility
_12
├── Reserve Fund: Protocol-owned MOET/collateral to stabilize price
_12
├── Stability Module: Direct MOET ↔ $1 redemptions (like DAI PSM)
_12
└── Gradual Rollout: Caps on total supply during early phase

Example Depeg Scenario:


_33
Day 1: Flash Crash
_33
├── FLOW price: $1.00 → $0.50 (-50%)
_33
├── System debt: 10M MOET
_33
├── Liquidations triggered: 3M MOET worth
_33
├── Liquidators acquire: 3M MOET
_33
├── Liquidators sell: On DEXs for stablecoins
_33
├── MOET price: $1.00 → $0.92 (-8%)
_33
└── Fear spreads: Users panic
_33
_33
Day 2: Panic Selling
_33
├── Users sell: MOET positions on DEXs
_33
├── More liquidations: Triggered by volatility
_33
├── MOET price: $0.92 → $0.85 (-15% total)
_33
├── System still solvent: Collateral > debt
_33
└── But: Market price ≠ redemption value
_33
_33
Recovery Mechanism (Without Direct Intervention):
_33
├── Arbitrageurs notice: MOET at $0.85, redeemable for $1 of collateral
_33
├── Arbitrage: Buy MOET at $0.85, repay debt, profit $0.15 per MOET
_33
├── Buying pressure: Increases demand
_33
├── Liquidations stabilize: Collateral prices bottom out
_33
├── Days 3-7: MOET gradually recovers to $0.95
_33
├── Days 8-14: Returns to $1.00
_33
└── Lesson: Protocol remained solvent, market recovered naturally
_33
_33
Recovery Mechanism (With Direct Intervention):
_33
├── Protocol Reserve: Buys 500K MOET at $0.85 = $425K spent
_33
├── Immediate support: Prevents further decline
_33
├── Confidence restored: Users see protocol actively defending peg
_33
├── Days 2-3: MOET returns to $0.98
_33
├── Days 4-5: Stabilizes at $1.00
_33
├── Protocol profits: Sells 500K MOET at $1.00 = $500K (earned $75K)
_33
└── Reserves replenished: Ready for next crisis

Cascading Liquidation Risk

Risk: One liquidation triggers more liquidations in a downward spiral.

Mechanism:


_24
Step 1: Initial Liquidation
_24
├── FLOW drops: $1.00 → $0.70 (-30%)
_24
├── 1,000 positions: Become liquidatable
_24
├── Liquidations begin: Keepers repay debt, seize collateral
_24
└── MOET burned: 5M tokens
_24
_24
Step 2: Collateral Dumping
_24
├── Liquidators sell: Seized collateral (1,000 FLOW each)
_24
├── Market impact: Large FLOW sell pressure
_24
├── FLOW price drops further: $0.70 → $0.60 (-14% more)
_24
└── More positions: Become liquidatable
_24
_24
Step 3: Cascade
_24
├── Round 2 liquidations: Another 2,000 positions
_24
├── More collateral dumped: FLOW → $0.50
_24
├── Round 3 liquidations: 5,000 positions
_24
├── Panic selling: Amplifies decline
_24
└── System stress: Extreme
_24
_24
Step 4: Potential Insolvency
_24
├── If cascade continues: Collateral value < debt value
_24
├── Protocol becomes insolvent: Cannot back all MOET
_24
├── MOET depeg: Severe loss of confidence
_24
└── Crisis: System failure

Mitigation:


_12
Current Measures:
_12
├── High Collateralization: 162.5% provides buffer
_12
├── Liquidation Bonus: 5% (not too high to encourage mass liquidations)
_12
├── Partial Liquidations: Don't force full position closure
_12
└── Interest Rates: Increase during high utilization to slow borrowing
_12
_12
Needed Enhancements:
_12
├── Liquidation Rate Limits: Max X positions per hour
_12
├── Progressive Liquidation Bonus: Decreases as more liquidations occur
_12
├── Emergency Collateral Injection: Protocol buys collateral to support prices
_12
├── Liquidation Pauses: Temporary halt during extreme volatility
_12
└── Insurance Fund: Protocol-owned reserves to cover insolvency

Oracle Risk

Risk: Incorrect price data leads to wrong liquidations or improper minting.

Failure Modes:


_20
Price Manipulation:
_20
├── Attacker manipulates: DEX price feed
_20
├── Oracle reports: False price spike (FLOW = $10)
_20
├── Users borrow: Excessive MOET based on inflated collateral
_20
├── Price returns: FLOW = $1, positions insolvent
_20
└── Protocol loss: Uncollateralized MOET in circulation
_20
_20
Oracle Downtime:
_20
├── Oracle stops updating: Stale prices
_20
├── Actual price drops: FLOW $1 → $0.50
_20
├── Oracle still reports: $1.00 (stale)
_20
├── No liquidations triggered: Positions become insolvent
_20
└── System risk: Delayed liquidations, bad debt accumulation
_20
_20
Price Lag:
_20
├── High volatility: FLOW swings $0.80 → $1.20 → $0.70
_20
├── Oracle updates: Every 10 minutes (lagging)
_20
├── Liquidations: Triggered on stale data
_20
├── User loss: Liquidated unfairly
_20
└── Protocol reputation: Damaged

Mitigation:


_12
Current Protections:
_12
├── Multiple Oracle Sources: IncrementFi, Band, Pyth
_12
├── Price Staleness Checks: Reject outdated prices
_12
└── Price Deviation Guards: Flag abnormal movements
_12
_12
Needed Enhancements:
_12
├── Median Price Aggregation: Use median of 3+ oracles
_12
├── Time-Weighted Average Price (TWAP): Smooth out volatility
_12
├── Circuit Breakers: Pause protocol on extreme deviation
_12
├── Keeper Slashing: Penalize keepers for using manipulated prices
_12
├── Price Confidence Intervals: Only accept high-confidence oracle data
_12
└── Fallback Oracles: Backup sources if primary fails

Example Oracle Attack Prevention:


_16
Normal Operation:
_16
├── Oracle 1 (IncrementFi): FLOW = $1.00
_16
├── Oracle 2 (Band): FLOW = $1.01
_16
├── Oracle 3 (Pyth): FLOW = $0.99
_16
├── Median: $1.00
_16
└── Use: $1.00 for calculations
_16
_16
Attack Attempt:
_16
├── Attacker manipulates: Oracle 1 → $10.00 (flash loan attack on DEX)
_16
├── Oracle 2 (Band): FLOW = $1.01 (not manipulated)
_16
├── Oracle 3 (Pyth): FLOW = $0.99 (not manipulated)
_16
├── Median: $1.01 (attack filtered out)
_16
├── Deviation check: $10 vs $1.01 = 890% deviation ⚠️
_16
├── System response: Reject Oracle 1, use only 2 & 3
_16
├── Fallback price: Median($1.01, $0.99) = $1.00
_16
└── Attack failed: No improper minting occurred

Smart Contract Risk

Risk: Bugs or exploits in MOET, ALP, or FYV contracts lead to loss of funds.

Threat Vectors:


_21
Reentrancy Attacks:
_21
├── Attacker calls: Withdraw function
_21
├── During execution: Calls back into contract
_21
├── Exploit: Withdraws funds multiple times
_21
└── Result: Drained reserves
_21
_21
Overflow/Underflow:
_21
├── Large numbers: Exceed max uint limits
_21
├── Wrap around: 2^256 - 1 + 1 = 0
_21
├── Exploit: Create debt/collateral from nothing
_21
└── Result: Unlimited MOET minting
_21
_21
Access Control Bugs:
_21
├── Missing modifiers: Anyone can call admin functions
_21
├── Exploit: Unauthorized minting
_21
└── Result: Infinite MOET supply
_21
_21
Logic Errors:
_21
├── Incorrect formulas: Health factor calculated wrong
_21
├── Exploit: Borrow more than allowed
_21
└── Result: Undercollateralized positions

Mitigation:


_13
Current Safeguards:
_13
├── Cadence Language: Resource-oriented, prevents many common bugs
_13
├── Flow Blockchain: Built-in safety features
_13
└── Standard Interfaces: FungibleToken standard compliance
_13
_13
Needed for Production:
_13
├── Multiple Audits: At least 2-3 independent security audits
_13
├── Bug Bounty Program: Pay white-hats to find vulnerabilities
_13
├── Formal Verification: Mathematical proof of correctness
_13
├── Gradual Rollout: Limited supply caps during testing
_13
├── Emergency Pause: Admin can halt contracts in crisis
_13
├── Timelocks: Delay on admin actions for community review
_13
└── Insurance: Protocol coverage (e.g., Nexus Mutual)

Centralization Risk

Risk: Single admin controls minting, creating censorship or manipulation risk.

Current State:


_10
Centralized Control:
_10
├── Minter Resource: Single resource at admin account
_10
├── Can mint: Unlimited MOET
_10
├── No oversight: No multi-sig or timelock
_10
└── Single point of failure: Admin key compromise = total control

Mitigation Roadmap:


_17
Phase 1: Multi-Sig (Immediate)
_17
├── Minter Resource: Controlled by 3-of-5 multi-sig
_17
├── Requires: Multiple team members to approve minting
_17
├── Reduces: Single point of failure
_17
└── Timeline: Before mainnet launch
_17
_17
Phase 2: DAO Governance (6-12 months)
_17
├── Minting Proposals: Community votes on supply changes
_17
├── Timelock: 48-hour delay on parameter changes
_17
├── Veto Power: Community can reject bad proposals
_17
└── Transparency: All actions on-chain and public
_17
_17
Phase 3: Full Decentralization (12-24 months)
_17
├── Algorithmic Minting: Based on predefined rules only
_17
├── No Admin Keys: Smart contracts fully autonomous
_17
├── Emergency Council: Limited powers, only for critical bugs
_17
└── Community Control: All parameters governed by token holders

Liquidity Risk

Risk: Insufficient MOET liquidity on DEXs leads to high slippage and price instability.

Problem:


_13
Low Liquidity Scenario:
_13
├── DEX Pool: 100,000 MOET / 100,000 USDC
_13
├── User wants to swap: 10,000 MOET (10% of pool)
_13
├── Slippage: ~5% (constant product formula)
_13
├── Received: 9,500 USDC instead of 10,000
_13
└── Price impact: MOET effectively worth $0.95
_13
_13
Cascading Effect:
_13
├── Low liquidity → High slippage
_13
├── High slippage → Arbitrage inefficient
_13
├── Inefficient arbitrage → Peg deviates more
_13
├── Peg deviation → Loss of confidence
_13
└── Confidence loss → More selling → Lower liquidity

Solution:


_16
Protocol-Owned Liquidity (POL):
_16
├── Protocol deposits: 1M MOET + 1M USDC into DEX
_16
├── Deep liquidity: Reduces slippage
_16
├── Permanent: Protocol doesn't remove liquidity
_16
└── Stability: Enables efficient arbitrage
_16
_16
Liquidity Mining Incentives:
_16
├── Reward LPs: With protocol tokens
_16
├── Attract: Third-party liquidity providers
_16
├── Increase depth: More liquidity = better peg stability
_16
└── Gradual reduction: As protocol matures
_16
_16
Example Impact:
_16
├── Before: 100K pool, 10K swap = 5% slippage
_16
├── After: 5M pool (with POL), 10K swap = 0.1% slippage
_16
└── Arbitrage: Becomes profitable at ±0.2% deviation vs. ±2% before

Safety Measures Summary

Current Protections

MechanismDescriptionEffectiveness
Over-Collateralization162.5% backing requiredStrong - provides 38-42% safety buffer
Liquidation SystemClears bad debt at HF < 1.0Moderate - depends on keeper efficiency
Interest RatesUtilization-based incentivesModerate - self-balancing over time
Mint-Burn ModelSupply tied to debtStrong - prevents uncollateralized supply
Partial LiquidationsAvoids full position closureStrong - reduces cascade risk
Multi-Oracle SupportMultiple price sourcesModerate - needs median aggregation

Required for Production

EnhancementPurposePriority
MOET/USD OracleMonitor peg deviationCritical
Reserve FundDirect peg supportCritical
Circuit BreakersPause during crisisHigh
Multi-Sig MintingDecentralize controlCritical
Liquidation LimitsPrevent cascadesHigh
Insurance FundCover insolvencyHigh
Security AuditsFind vulnerabilitiesCritical
Protocol-Owned LiquidityEnsure DEX depthMedium
DAO GovernanceCommunity controlMedium

Risk Assessment Matrix

Likelihood vs. Impact


_19
Critical Risk (Address Immediately):
_19
├── Smart Contract Bug: Medium likelihood, Extreme impact
_19
├── Oracle Manipulation: Low likelihood, Extreme impact
_19
└── Admin Key Compromise: Low likelihood, Extreme impact
_19
_19
High Risk (Address Before Mainnet):
_19
├── Cascading Liquidations: Medium likelihood, High impact
_19
├── Depeg During Volatility: High likelihood, Medium impact
_19
└── Liquidity Crisis: Medium likelihood, High impact
_19
_19
Medium Risk (Monitor and Improve):
_19
├── Interest Rate Inefficiency: Low likelihood, Medium impact
_19
├── User Error: High likelihood, Low impact
_19
└── Temporary Oracle Lag: Medium likelihood, Low impact
_19
_19
Low Risk (Acceptable):
_19
├── Minor Slippage: High likelihood, Very low impact
_19
├── Network Congestion: Medium likelihood, Low impact
_19
└── UI/UX Issues: High likelihood, Very low impact

Risk Tolerance Recommendations

For Analysts:


_17
Conservative View:
_17
├── Current MOET: Not suitable for large-scale production
_17
├── Missing: Critical stability mechanisms
_17
├── Recommendation: Wait for production-ready version
_17
└── Risk: High for early adopters
_17
_17
Moderate View:
_17
├── Testnet MOET: Good for experimentation
_17
├── Limited mainnet: Acceptable with caps (<$10M TVL)
_17
├── Recommendation: Start small, scale gradually
_17
└── Risk: Acceptable with proper risk management
_17
_17
Aggressive View:
_17
├── Launch MOET: With current design
_17
├── Iterate fast: Fix issues as they arise
_17
├── Recommendation: Move fast, learn from mistakes
_17
└── Risk: High, but manageable with monitoring

Next Steps for Production Readiness

Phase 1: Critical Infrastructure (Pre-Mainnet)


_19
1. Implement MOET/USD Oracle
_19
├── Deploy: Chainlink or similar price feed
_19
├── Monitor: Real-time peg tracking
_19
└── Alert: Deviations > ±2%
_19
_19
2. Add Multi-Sig Minting
_19
├── Deploy: 3-of-5 multi-sig contract
_19
├── Transfer: Minter resource to multi-sig
_19
└── Test: Minting process with multiple signers
_19
_19
3. Create Reserve Fund
_19
├── Allocate: 10% of initial supply
_19
├── Management: Protocol-controlled
_19
└── Use: Peg stabilization operations
_19
_19
4. Security Audit
_19
├── Hire: 2-3 reputable audit firms
_19
├── Scope: MOET, ALP, FYV contracts
_19
└── Fix: All critical and high-severity findings

Phase 2: Enhanced Stability (0-3 Months Post-Launch)


_19
1. Deploy Circuit Breakers
_19
├── Implement: Auto-pause on extreme volatility
_19
├── Thresholds: ±20% collateral price moves
_19
└── Recovery: Manual restart after review
_19
_19
2. Liquidation Rate Limits
_19
├── Implement: Max liquidations per block
_19
├── Progressive bonuses: Decrease during mass liquidations
_19
└── Monitoring: Alert on high liquidation volume
_19
_19
3. Protocol-Owned Liquidity
_19
├── Deploy: 1M MOET + 1M USDC to DEX
_19
├── Monitor: Slippage and arbitrage efficiency
_19
└── Adjust: Add more if needed
_19
_19
4. Expand Oracle Coverage
_19
├── Add: Pyth and additional sources
_19
├── Implement: Median price aggregation
_19
└── TWAP: Time-weighted averaging

Phase 3: Decentralization (6-12 Months)


_19
1. DAO Governance Launch
_19
├── Deploy: Governance token
_19
├── Distribute: To users and stakeholders
_19
└── Proposals: Parameter changes via voting
_19
_19
2. Algorithmic Minting Rules
_19
├── Codify: Minting conditions in smart contract
_19
├── Remove: Arbitrary admin minting
_19
└── Governance: Only way to change rules
_19
_19
3. Emergency Council
_19
├── Form: 5-7 member security council
_19
├── Powers: Limited to emergency pause only
_19
└── Oversight: Community can remove members
_19
_19
4. Full Transparency
_19
├── Dashboard: Real-time protocol metrics
_19
├── Analytics: Historical data and trends
_19
└── Audits: Ongoing bug bounty program

Conclusion

MOET's stability relies on a multi-layered approach combining over-collateralization, liquidations, interest rate adjustments, and arbitrage incentives. While the current mock implementation lacks active stabilization mechanisms, the intended design provides substantial safety margins through:

  1. 162.5% collateralization creating a significant buffer against volatility
  2. Liquidation systems clearing bad debt before insolvency
  3. Economic incentives through interest rates and arbitrage opportunities
  4. Automated capital flows via FYV yield providing position protection

For production deployment, critical enhancements are needed including MOET/USD oracles, reserve funds, multi-sig controls, and comprehensive audits. With these measures in place, MOET can serve as a stable, capital-efficient synthetic stablecoin powering the FCM ecosystem.

Key Takeaway for Analysts: MOET's stability is fundamentally sound in design but requires additional infrastructure before large-scale production use. The over-collateralization model provides strong backing, but active monitoring and intervention capabilities are essential for maintaining the peg during extreme market conditions.

Additional Resources