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. SYSTEM ARCHITECTURE

Epochs

PreviousgigaAssetsNextPROTOCOL FLOWS

Last updated 6 months ago

Enjoyoors operates with epochs, a foundational feature for its protocol operations. An epoch is a specific time frame during which the protocol state remains constant under normal conditions. Throughout an epoch, key protocol parameters remain static as defined at the beginning of the epoch, while remain allocated to target protocols based on the initial distribution (unless urgent circumstances arise, such as immediate liquidity rebalancing or user withdrawals).

The duration of an epoch is a parameter determined by Governance. A seven-day period is currently considered the most reasonable, although this can be adjusted through governance voting.

Before the start of a new epoch, the protocol reassesses its key parameters. The risk management framework recalculates parameters, while DAO input and factual yield assessments are used to review the list of target DeFi protocols and their corresponding allocation weights.

Epochs also impact deposits and withdrawals. Deposits begin accruing yield starting from the epoch following the one in which the deposit was made. Similarly, withdrawals can only be claimed at the end of the epoch following the one in which the withdrawal request was submitted.

gigaAssets
gigaCDP