JuicyPerp - Gamified Options Trading
  • 🍇What is JuicyPerp?
  • 🚀Quick Start
    • Prerequisites
    • Step-by-step Guide
  • 🌟Rewards
  • ⚔️Protocol Design
    • Mechanic
    • Pool Creation & Liquidation
    • Payouts & Multipliers
    • Fees
    • Claiming
    • Oracle Data
    • Contracts
    • Risks and Disclaimers
  • ⁉️FAQs
    • 🤝Troubleshooting
  • 🔒Audit
  • Legal
    • 📓Terms of Service
    • 🔍Privacy Policy
Powered by GitBook
On this page
  • Risks
  • Disclaimers
  1. Protocol Design

Risks and Disclaimers

As with every decentralized protocol there are certain risks involved. This page consolidates known risks and presents the following disclaimers to help you understand them better.

PreviousContractsNextFAQs

Last updated 10 months ago

Risks

The protocol relies on the availability of the . In the very unlikely case of an outage of the Pyth network, battle pools might not initially be liquidated as expected and have to be resolved manually. This can take multiple hours, but ensures that battle pools are either still liquidated at the correct price or refunded.

Disclaimers

Timers displayed on the dApp are for visualization purposes only. The entire battle mechanic is decentralized and executed on a smart contract level, which measures time according to the .

⚔️
Pyth Oracle network
Arbitrum sequencer