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. Risk management framework

gigaAsset allocation rules

Another important aspect of capital and risk management involves establishing rules for gigaAsset deployment, which define target weights for gigaAsset allocations across specific types of DeFi protocols. Adhering to the risk framework, these weights prioritize exposure to more established, lower-risk protocols while minimizing potential risks associated with less familiar or higher-risk ones. The general categories of protocols Enjoyoors works with are shown below:

Protocol Type

Description

Restaking Protocols

gigaAssets will be restaked and earn yield securing different blockchains and decentralized services.

Lending protocols

Single-sided liquidity protocols from which users can borrow gigaAssets. The more interesting use-case is when gigaAssets are used as collateral because they allow for additional exposure for the Enjoyoors protocol due to leverage. (e.g. the protocol could borrow DAI at 3% APY on AAVE against ETH gigaAsset and stake it for 5% APY)

Curve AMMs

The AMM will serve as a primary source of external gigaAsset liquidity. It will earn fees for its Liquidity providers and the Enjoyoors protocol while working with Intelligent Peg Adapters (IPAs) to control the peg of gigaAssets.

Liquidity Seekers

These are emerging DApps and protocols that strive to build up their TVL and are willing to reward liquidity in their tokens for this.

The initial distribution of weights is intentionally conservative. These numbers are subject to change based on risk assessment and governance decisions in the future.

Protocol Type

Target Weight

Description

Rebalance threshold

Restaking

80%

Most of the liquidity will be funneled to shared security protocols, which offer low yield but on much safer terms than all others. Usually they have unstaking periods of no longer than Enjoyoors epoch of 7 days.

+/-5%

Lending

5%

Small fraction to allow for secondary lending markets. Allocation may be increased when gigaAssets will be accepted as collateral.

+/-1%

AMM + IPA

10%

Both AMM and IPA will hold 5% each pegkeeper can increase or decrease AMM supply to control the peg.

+/-2%

New protocols

5%

Initially a low allocation to new protocols, liquidity provision for airdrop farming, possibly with liquidity locks.

+/-1%

Current distribution weights will be most frequently affected by the increase in synthetic supply (due to liquidity entering the protocol) or the decrease in synthetic supply (due to de-risking or liquidity exiting the protocol).

PreviousTechnical risksNextDecentralized system architecture

Last updated 3 months ago