> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/whats-new/2026/november-2026.md).

# November 2026

2026-11-06

### Mapping Update

* Gate.io Derivatives **NVDA\_USDT** perpetual has been remapped from `nvdax-usdt` to `nvda-usdt`. The delisted NVDAX\_USDT perpetual keeps `nvdax-usdt`
* Gate.io Derivatives **SPY\_USDT** perpetual has been remapped from `spyx-usdt` to `spy-usdt`. The delisted SPYX\_USDT perpetual keeps `spyx-usdt`
* Uniswap V3 **NVIDIA (Ondo Tokenized) / WETH** pool has been remapped from `nvda-weth` to `nvdaon-weth`

2026-11-13

### Funding Rate Update

Four fields are now returned by the Derivatives Risk endpoint, `/v2/data/derivatives.v2/risk`. These were previously available on the Exchange-provided metrics stream only.

* `funding_rate_ts` records the exchange timestamp of the settlement that produced `funding_rate`.
* `next_funding_time` records when the next settlement is due.
* `funding_interval` gives the exchange’s funding period for the contract, for example `8h` or `continuous`.
* `is_actual_funding_rate` indicates whether `funding_rate` was the rate in force at the start of the requested interval.

`funding_interval` is returned per instrument, so contracts on the same exchange may carry different periods. It supersedes `funding_rate_frequency` on the reference endpoint, which holds a single static value per exchange.

Where an exchange applies funding continuously, `funding_interval` returns `continuous` and `next_funding_time` and `is_actual_funding_rate` are not applicable. `is_actual_funding_rate` is evaluated against the start of the requested interval, so where an exchange records settlement shortly after the hour it returns `false` at intervals equal to or coarser than the funding period.

Full field definitions are documented under Exchange-provided metrics.


---

# 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.kaiko.com/whats-new/2026/november-2026.md?ask=<question>&goal=<user_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.
