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
  3. Risk Management

Funding Rate Monitoring

To function correctly, the Funding Rate must be favorable to Vortex. If the Funding Rate is consistently against Vortex, positions will be managed/unwound accordingly. This funding rate is constantly managed by the Vortex Manager and, if is determined that the funding rate will remain unfavourable for a prolonged amount of time, then the strategy will be unwound to prevent further losses.

PreviousemergencyExit()NextDeployed Contracts

Last updated 3 years ago

🏗️
💫
❗