Historical tracing on Kaia ends on 15 September
From 15 September Kaia runs on full nodes, and how far back a call can reach changes. Tracing keeps working for recent history, roughly a day of blocks, and a state read at an explicit older block needs archive state that a full node does not hold. Everything else on Kaia stays as it is: the same endpoints on mainnet and testnet over HTTPS and WSS, the same rate limits, the same error codes, and the same method list apart from the five listed below.
Deprecations and end-of-support
Historical tracing on Kaia, from 15 September 2026
These five methods were the documented exception to debug_* being unsupported on Kaia. They move into the unsupported list, because they now answer only for recent history:
| Method | What happens after 15 September |
|---|---|
debug_traceTransaction | works for recent history, about 100,000 blocks back, then returns -32000 historical state unavailable |
debug_traceBlockByNumber | same |
debug_traceBlockByHash | same |
debug_traceBlock | same |
debug_traceCall | same |
At Kaia's one second block time that window is roughly a day, and we measured it on our own nodes rather than reading it off a config.
A state read at an explicit older block is affected too. eth_call, eth_getBalance and eth_getStorageAt with a block number instead of latest need archive state, and a full node answers -32000 missing trie node. Calls against latest are unaffected.
eth_getLogs keeps working over the full block history, because logs and receipts need no historical state, and nothing else on the Kaia method list changes.
Worth checking on your side
If you trace Kaia transactions, check how far back your integration reaches. A pipeline that traces blocks as they arrive keeps working. A backfill, a reorg audit or an on-demand trace of an old transaction does not, and it needs a different data source from 15 September.
If historical tracing on Kaia is part of how your product works, write to our Sales team at sales@ankr.com before the date and we will look at the options with you.
Everything else
No method limits, error codes or rate limits changed on any other network. Kaia mainnet and testnet remain available on every plan that carried them before.