Siren Flow
  • Introduction
  • 🧜‍♀️Siren Protocol
    • Glossary
    • Use Cases
    • Siren Flow Architecture
      • Hybrid Pricing Model
      • Automated Hedging System
      • Unified Liquidity Pools
      • Portfolio Margin
      • Capital Management
  • FAQ
    • About Siren
    • For Users
    • Product Strength
    • What are Options?
    • What is ITM, ATM and OTM?
    • What are Greeks?
    • Who is the Liquidity Provider?
    • Contract Specifications
    • Siren Protocol Fees
    • Pyth Integration
    • Liquidations
  • Community
    • Governance
    • Discord
    • Twitter
    • Telegram
    • Medium
  • Tutorials
    • Advanced Trading Strategies on Siren
    • Trading on Siren: A Step-by-Step Guide
Powered by GitBook
On this page
  1. Siren Protocol
  2. Siren Flow Architecture

Unified Liquidity Pools

Supporting Options for Any Asset

PreviousAutomated Hedging SystemNextPortfolio Margin

Last updated 1 year ago

Siren Flow’s model of using stablecoins as collateral for all options allows the platform to create options for a wide range of assets, regardless of whether token-specific liquidity pools already exist for those assets.

Unified Liquidity Pools enable traders to purchase options for any asset with a reliable price feed, greatly expanding the range of available options. By adopting this model, Siren Flow offers unparalleled flexibility and opportunities for traders in the DeFi options space.

Under the new system, LPs no longer need to maintain different assets in multiple pools in order to earn yield. By consolidating liquidity into a single pool that earns aggregated fees across various markets, Siren Flow simplifies and enhances the user experience.

NOTE: This is a living document that will continue to be updated as Siren evolves. To contribute, please visit . Specific questions may be answered and technical guidance may also be provided from time to time in the to those who are interested in building on top of the protocol.

🧜‍♀️
Siren on GitHub
Siren Discord