> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/consolidated-resources/roll-schedules.md). # Roll schedules Nexus perpetuals do not expire, so there is no roll schedule. **There is no roll schedule, because Nexus perpetual futures do not expire.** A roll schedule exists on a venue whose contracts have a fixed expiry: positions must be closed or rolled into the next contract before the current one settles. Nexus lists **perpetuals**. They trade continuously with no expiry and no daily settlement window, and you can hold a position indefinitely as long as it stays above its maintenance margin requirement. What replaces the roll economically is **funding**: instead of converging on an expiry price, the perpetual is tethered to its index by periodic funding payments between longs and shorts. Read about funding if you want the cost of carrying a position over time. See [Funding rates](/trading/trading/perpetuals/funding-rates.md). Two related things that are *not* roll schedules but are sometimes confused with them: * **Force-settlement.** A market being delisted is settled at a pre-committed rule rather than rolled. That rule is a per-market parameter set when the market is listed. * **Session breaks.** Some non-crypto markets are configured against exchange hours rather than 24/7. See the [Asset directory](/asset-directory/asset-directory.md). A session break is not a roll and does not settle a position. --- # 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.nexus.xyz/consolidated-resources/roll-schedules.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.