Enjoyoors
  • WHITEPAPER
    • Introduction
    • User-abstracted rehypothecation
      • Giga CDP of Enjoyoors
      • Giga CDP design
      • Deep secondary liquidity for gigaAssets
    • Protocol stability
      • Efficient portfolio management
      • Supply regulation for gigaAssets
      • System-wide insurance
    • Risk management framework
      • Market risks
      • Technical risks
      • gigaAsset allocation rules
    • Decentralized system architecture
      • Public chain infrastructure
      • Orchestrator appchain
      • Oracles
      • Interchain communications
    • Key protocol features
      • Epochs
      • Reward auctions
      • Intelligent peg adapters
    • Further considerations
      • Making RWAs work harder
      • Own DeFi ecosystem
      • Our priorities
  • SYSTEM ARCHITECTURE
    • Overview
    • Public Blockchain Infrastructure
      • Vaults
      • gigaAsset Manager
      • Target Protocols
      • Target Protocol Adapters
      • Intelligent Peg Adapters
      • AMM Pools
      • Rewards Treasury
    • AVS Relayer
      • Relayers
    • Enjoyoors Orchestrator AppChain (L3)
      • Enjoyoors Management System
      • Orchestrator AppChain Layers
      • Security Mechanisms
      • Price Oracle
      • Governance
      • gigaCDP
      • Portfolio Management System
      • Auctions
      • Insurance Pool
    • gigaAsset Bridge
    • gigaAssets
    • Epochs
  • PROTOCOL FLOWS
    • Deposit
    • Withdraw
    • Auction
  • RISKS
    • Protocol risks
Powered by GitBook
On this page
Export as PDF
  1. WHITEPAPER
  2. Protocol stability

System-wide insurance

Enjoyoors secures LP risks of users depositing funds into Giga CDP by covering potential losses with its insurance pool. To maintain liquidity in the insurance pool, the protocol collects InsuranceFee, a cut of all yield generated in the protocol.

There are two main risks the protocol avoids via insurance:

  • Slashing risks in protocols where gigaAssets are deployed

  • Risks of hacks resulting in losses of gigaAssets

In both cases, a user can expect compensation from the insurance pool to cover the loss of initially staked funds. If the insurance pool is insufficiently liquid, the protocol uses its native token treasury to cover potential losses.

In the worst-case scenario, if the insurance pool and token treasury are insufficient to cover the losses, users bear the loss collectively. They commit to repaying a fraction of the lost gigaAssets proportionally to their stakes in protocol vaults before being allowed to withdraw their initial deposits from vaults.

PreviousSupply regulation for gigaAssetsNextRisk management framework

Last updated 3 months ago