Geode Document Hub
  • Geode Document Hub
  • The Staking Library
    • 🔥The Issue
    • 🧯A Solution
  • Operator Marketplace
    • 🟢A Validator's Lifecycle
    • 🔵Maintenance Fee
    • 🟡Onboarding New Operators
    • 🔴Regulating the Marketplace
      • 🚨Prison
  • Key Concepts
    • 🪙Staking Derivatives
      • G-Derivatives
        • gETH vs gAVAX
    • 🌀Portal
      • 🔐Isolated Storage
      • 🤝Dual Governance
      • ⚠️Limited Upgradability
    • ⚙️Permissionless Configurable Staking Pools
      • 🎭Current Interfaces
      • ⛏️Maintainers
    • 🛡️Withdrawal Contracts
      • ⛑️Recovery Mode
      • 🕗Withdrawal Queue
    • 🌊Bound Liquidity Pools
    • 🔭Oracles
      • Telescope Ether
      • Telescope Avax
    • 👾Future of Geode
      • Better Maintainers (WIP)
      • Synthetic Liquidity (WIP)
      • Dynamic Withdrawals (WIP)
      • Further Decentralization
        • Supporting EIP-4788 (DRAFT)
        • Quadratic Weighted Senate (DRAFT)
        • Degen Operators (DRAFT)
        • Decentralized Telescope (DRAFT)
      • Chain Sync (AVAX) (draft)
  • Ethereum Guides
    • 📗Staking Pool HandBook
      • Initiating a Customizable Staking Pool
      • Managing Your Operator Set
      • Changing Your Pool's Owner
      • Manage Your Maintenance Fee
      • Private Pools and Whitelisting
      • Using a Bound Liquidity Pool
      • Using Maintainers for Your Pool
      • Securing Your Withdrawal Contract
      • Decentralizing Your Pool
    • 📕Operator Handbook
      • Get Onboarded
      • Initiating an Operator
      • Communicating with Portal
      • Creating Validators
      • Changing an Operator's Owner
      • Switching Your Fee
      • Switching Your Validator Period
      • Using Maintainers
      • Optimizing Your Revenue
      • Exiting Validators
    • 📘Liquidity Pool HandBook
  • Avalanche Guides
    • Staking Pool Handbook
    • Operator Handbook
  • Developers
    • Networks
    • Live Contracts
      • Avalanche v1
      • Ethereum v2
        • gETH.sol
        • Portal.sol
          • globals.sol
          • DataStoreUtilsLib.sol
          • GeodeUtilsLib.sol
          • DepositContractUtilsLib.sol
          • OracleUtilsLib.sol
          • StakeUtilsLib.sol
        • Swap.sol
          • AmplificationUtils.sol
          • MathUtils.sol
          • SwapUtils.sol
          • LPToken.sol
        • WithdrawalContract.sol
        • Interfaces
          • ERC20InterfaceUpgaradable.sol
          • ERC20InterfacePermitUpgradable.sol
    • Audits
    • Bug Bounties
Powered by GitBook
On this page
  • Why?
  • How much?
  • Example for 10% Synthetic Liquidity
  1. Key Concepts
  2. Future of Geode

Synthetic Liquidity (WIP)

Utilizing this feature will require a Bound Liquidity Pool.

Why?

Synthetic Liquidity will allow less than 100% collateralization ratio to be introduced for a staking derivative.

However, Synthetic Liquidity is only created on deposits and burned on withdrawals.

This way, we can allow a continuous liquidity flow to bound liquidity pool, without creating any issues on the supply model.

How much?

Staking Pool Owners can set a parameter up to x% for synthetic minting.

x is potentially between 10-25.

Example for 10% Synthetic Liquidity

The price of the derivative on the following example will be 1 Ether.

  1. User puts 100 Ether in Portal to be used for Staking Operations.

  2. 90 Ether is added to the Pool.

    • Decreases the pool APR.

  3. Portal mints 110 Ether worth of gETH, 110 gETH

    • Created tokens are not backed by any collateral.

  4. 100 Ether worth of gETH is given back to staker, 100 gETH

  5. 10 Ether and 10 Ether worth of gETH (10 gETH) is put into Bound Liquidity Pool.

    • Increases the Pool APR.

  6. The LP tokens are given to the Withdrawal Contract.

  7. When user comes back with 100 gETH, which can represent more than 100 Ether, respective LP tokens are burned, and the remaining Ether amount will be filled by Validator Withdrawals.

PreviousBetter Maintainers (WIP)NextDynamic Withdrawals (WIP)

Last updated 2 years ago

👾