> For the complete documentation index, see [llms.txt](https://docs.defi.app/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defi.app/knowledge-base/trade-and-earn/trade-perpetuals/faqs.md). # FAQs #### 1. **How Do Perpetuals Work?** Perpetual futures (or “perps”) are derivative contracts that let you speculate on an asset’s price indefinitely. There’s no expiration date, so you can hold any position as long as you have enough margin. To keep the contract’s price aligned with the asset’s actual (spot) price, perps use a mechanism called the **funding rate**, which is a regular payment exchanged between traders: * If the perpetual price is above spot, longs pay shorts. * If it’s below, shorts pay longs. Defi App performs the funding transaction every 8 hours. *** #### 2. **How Are Perps Implemented in DeFi App?** *** #### 3. **What Are Oracle Sources?** An oracle is a bridge between on-chain systems and off-chain data (specifically, price feeds). Because smart contracts can’t fetch external data on their own, oracles provide trustworthy, tamper-resistant pricing so protocols can handle derivatives, liquidations, and valuations. *** #### 4. **Which Oracle Sources Does DeFi App Use?** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.defi.app/knowledge-base/trade-and-earn/trade-perpetuals/faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.