Akropolis
  • 🕶️Introduction
  • 🧠Using Akropolis
  • 💸Products
    • 🌀Vortex
      • 💫Overview
      • 💻How it works
      • 🛣️Roadmap
      • ✍️Competitor Comparison
    • 🎆Yearn Integration
    • 💜AKRO staking
  • 🏛️Governance
    • 🟣AKRO token
    • 📋Governance process
  • 🏗️Developer documentation
    • 💫Vortex
      • 👓High-Level View
      • 🍭Contract Design
      • 🌾Key Function - harvest
      • 🧑‍💻🧑💻 Integration guide
      • ❗Risk Management
        • Position Buffer
        • remargin()
        • unwind()
        • emergencyExit()
        • Funding Rate Monitoring
    • 🚦Deployed Contracts
      • Vortex
        • Testnet contracts
    • 🐧Open Source Development
      • Amun Ra
      • Pensify
      • C2FC
      • AkropolisOS
      • Sparta
      • Delphi
      • Polkahub
      • Ethereum <-> Substrate bridge
      • Web3 Wallet Kit
      • Substrate Staking portal
  • 🔐Security
    • 🔮Audits
    • 🐞Bug Bounty
  • 📚Additional Resources
    • 📑FAQ
    • 💥Community Channels
    • 📓Basis Trading and Perpetual Contracts
Powered by GitBook
On this page
  1. Developer documentation
  2. Vortex

High-Level View

PreviousVortexNextContract Design

Last updated 3 years ago

Vortex actively maintains three core positions:

  1. ETH Holdings - The long - ETH Holdings are sourced from a decentralized exchange and held idle in an address.

  2. ETH Short Contracts - The short - ETH Short Contracts are collateralized in USDC and collect the Funding Rate from the decentralized derivatives exchange.

  3. Position Buffer - The safety - The Position Buffer is sourced from user deposits and held idle to ensure the ETH Short Contracts are not liquidated.

For more information, see

Vortex v1 utilizes as the decentralized derivatives exchange and has been developed to accommodate their unique .

🏗️
💫
👓
Position Buffer
MCDEX
AMM Design