> For the complete documentation index, see [llms.txt](https://docs.trade.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trade.xyz/perpetuals/changelog/oracle-time-constant-updates.md).
# Oracle Time Constant Updates
Changelog entry for xyz oracle time-constant updates.
### April 30, 2026 - Oracle Time Constant Update
We reduced the internal oracle time constant from 1 hour to 30 minutes for equity perpetuals.
### November 21, 2025 - Oracle Time Constant Update
We reduced the internal oracle time constant from 8 hours to 1 hour for equity perpetuals.
Effect in Practice
* Faster reflection of price discovery - during closed sessions, the oracle now tracks orderflow with a shorter time constant, reducing the gap between “traded price” and oracle.
* Lower funding drag on genuine moves - traders who are directionally right on gap moves keep more of the move (87% vs 10%); shorts who sit through those gaps receive much less funding compensation.
* Same safety properties - the 1 / max\_leverage band on mark vs last external spot still limits single-tick jumps and weekend bands in mark.
---
# 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.trade.xyz/perpetuals/changelog/oracle-time-constant-updates.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.
