Horizon Academy
English V3
English V3
  • Horizon Academy
  • Horizon Protocol
    • Introduction
      • Tokenomics
      • Business Model
      • Synthetic Assets - zAssets
    • Security Audit
    • Community
      • How to Initiate a HIP
      • HIPs
        • HIP-23 Revenue Sharing Model: Intent-based System Phase one
        • HIP-22: Create a zUSD - USDC pool on Pancakeswap V3
        • HIP-21: Stop Incentives to the zBNB - BNB pool on Wombat Exchange
        • HIP-20: Suspend zMATIC Market and Introduce zPOL Ahead of MATIC to POL Migration
        • HIP-19: Temporarily reduce C-Ratio to 350%
        • HIP-18: Add DOGE and SHIBA to Horizon Futures
        • HIP-17: Add DOT, AVAX, and MATIC to Horizon Futures
        • HIP-16: Add XRP, ADA, and LINK to Horizon Futures
        • HIP-15: Add SOL to Horizon Futures
        • HIP-14: Reduce Trading Fees during Horizon Futures Promotional Period
        • HIP-13: Suspend zNVDA market ahead of Stock Split and convert zNVDA to zUSD
        • HIP-12: Updated Utilization of zUSD & zBNB Liquidity
        • HIP-11: Redirect HZN from EARN Pool to PancakeSwap as ‘Bribe’ using Cakepie
        • HIP-10: Use zAssets from Community Fund staking to provide liquidity on Wombat via Yield Aggregator
        • HIP-9: Redirect HZN from EARN Pools to Wombat Exchange as ‘Bribes’
        • HIP-8: Move the zUSD-BUSD and zBNB-BNB Liquidity Pools to Wombat Exchange
        • HIP-7: Utilize the Community Fund for Additional Liquidity
        • HIP-6: Lower Target C-Ratio to 600% from 700%
        • HIP-5: List New zAssets
        • HIP-4: Use Keepers to Close Weekly Fee Periods
        • HIP-3: Suspend zTSLA ahead of Stock Split
        • HIP-2: Lower Target C-Ratio to 700%
        • HIP-1: Create incentivized zBNB/BNB pool
      • Community Grant Program
    • FAQs
  • Stake & Earn
    • Introduction
    • Staking on Horizon Protocol
      • Staking and Rewards
      • Mint, Burn, and Claim
      • Collaterialization and C-Ratio
      • Liquidation
      • Managing Risk
      • C-Ratio Strategies
      • Hedge your Portfolio
    • Interfaces
      • Account - Escrow
      • Account - Authorize
      • Account - History
    • Guides
      • How to Stake by Minting zUSD
      • Adding Liquidity for zUSD and zBNB pools
      • Add Liquidity for HZN-BNB
      • Remove LP Tokens for zUSD-BUSD Pool
      • Setting Up Chainlink Automation
  • Educational Articles
    • Glossary and Definitions
    • What are DeFi Derivatives and how are they used
    • A Brief History of Synthetic Assets and Financial Derivatives
    • DeFi Derivative Projects
Powered by GitBook
On this page
  1. FUTURES
  2. Futures Trading on Horizon Protocol

Oracles

Oracles are an integral part of decentralized exchanges, including all perpetual futures exchanges, since a price feed is required to track the price of the underlying asset for which the futures contracts can be traded.

Horizon Futures, a perpetual futures DEX, uses a Dual Oracle system, which combines Chainlink oracles with Pyth oracles to improve performance, security, and reduce trading fees. The reason that the two oracles are needed is that they serve two distinct functions, one that uses a push model, and the other that uses a pull model.

On the one hand, the Chainlink oracle is a perpetual oracle that uses the push model. It gets automatically updated based on a few requirements, whether it be time or upon a certain percentage of price movement achieved. The consistency of data from a push model oracle allows for the visualization of time graphs and the automatic updates of the price facilitate liquidation and circuit breaker mechanics, but fall short on the market clearing price due to latency at the time of trade execution.

On the other hand, the Pyth oracle uses a pull model, where a price gets updated on-chain upon execution of the trade on the blockchain, which then provides the trade with the most recent price, significantly reducing the amount of latency in the price. This means that traders transact at a more exact market clearing price, it removes the possibility of oracle latency arbitrage, and it allows for lower fees due to the prices being more accurate. Pull models are great at the time of transactions, but because the only time a new data point is recorded onto the blockchain is during a transaction, it does not produce a reliable and consistent price feed unless it is updated manually on-chain at regular intervals, which can be a costly endeavor.

Therefore, Horizon Futures takes the two oracle models and combines them in a dual oracle system. With both push and pull models working together, it allows for the best of both worlds.

Most people are already familiar with Chainlink oracles. If there’s interest in learning more about Pyth oracles, please check out the following:

Introduction video
Pyth Documentation