For AI agents: an LLM-friendly Markdown version of every page is available by appending .md to its URL or by sending an Accept: text/markdown request header. The full documentation index is at https://www.ankr.com/docs/llms.txt
Skip to main content

Roundup: Sui is retiring JSON-RPC, Bahamut end of support, and a rebuilt API reference

Ankr Team
Docs Team

Two deprecations need your attention: Sui is retiring JSON-RPC network-wide, with the hard cutoff in mid-October, and Bahamut is no longer served. Alongside that, we rebuilt the Advanced API reference, split the per-chain RPC pages, and rolled node clients forward on roughly 25 chains. Eight of those tracked a network upgrade with a hard activation, where a node left on the old version stops following the chain.

Deprecations and end of support​

Sui is retiring JSON-RPC​

The Sui Foundation is decommissioning JSON-RPC across the network in stages through 2026. Ankr runs its own Sui full nodes, so our JSON-RPC endpoint keeps working until the software removal in mid-October 2026, but the surface degrades before that and you should migrate now.

Sui JSON-RPC timeline
  • July 2026: Sui Foundation's public-good JSON-RPC endpoints were turned off (testnet the week of 6 July, mainnet the week of 20 July). Ankr endpoints were unaffected.
  • August 2026: JSON-RPC snapshots are no longer published.
  • September 2026: the implicit archival fallback is removed. Historical and pruned data over JSON-RPC may start failing.
  • Mid-October 2026: JSON-RPC is removed from Sui full-node software. Hard end, including on our nodes.

Migrate to gRPC for backends and indexers, or GraphQL for frontends and analytics. Both have been available on Ankr Sui endpoints since March. The JSON-RPC page carries the full timeline.

Bahamut​

The Bahamut team has discontinued the network, so Bahamut is no longer served on Ankr RPC and has been removed from the console chain list and the docs. If you still have Bahamut endpoints configured, they will return errors: point them elsewhere.

Docs​

  • Advanced API reference, rebuilt. The reference is now hand-structured MDX, matching the rest of the docs, with request and response shapes inline on each API's own page: Token API, NFT API, Query API and Stellar Soroban API. Stellar coverage now sits under its correct stellar_soroban namespace.
  • Per-chain RPC pages, split. The chains API section used to put a chain's methods, history and Web3 usage into a handful of very large pages. Each now has its own. Existing links still resolve.
  • Docs an agent can read. The site publishes an llms.txt index plus Markdown twins of every reference page, and headings, structure and metadata were reworked so that landing on a single method page gives you the endpoint, the parameters and a runnable example without following links first. Agents benefit most, but so does anyone arriving from search.

Network upgrades​

Each of these had an activation height or date, and the upgrade landed before it:

  • TRON: GreatVoyage v4.8.2, required for the move to block version 36.
  • Harmony: v2026.1.0 for the Bloom hard fork.
  • Monad: v0.15.1 for MIP-12.
  • Sui: mainnet nodes, validators and indexers to v1.75.2, which carries protocol version 129. Testnet is on v1.76.0.
  • IOTA: mainnet validators to v1.27.0 for protocol version 30. Testnet runs the v1.28.2 release candidate.
  • Celo: mainnet nodes moved off op-geth and onto op-reth ahead of the network's cutover.
  • Etherlink: the 6.6 kernel, a security hardening release, went live on 18 July.
  • Avalanche: Fuji testnet is on v1.15.0-fuji for Helicon.

Client versions​

Platform​

  • Browser gRPC clients can now send x-token. All *.grpc.ankr.com endpoints include x-token in Access-Control-Allow-Headers, so a gRPC-Web app authenticates with the header the docs recommend instead of failing CORS preflight or routing through a proxy.

Worth checking on your side​

Beyond the Sui migration above, most of this release is a version bump on the same client, which should be invisible to you. Two are not, because the client implementation itself changed, and tracing and archive behavior can differ between implementations:

  • Celo now runs op-reth instead of op-geth. If your integration calls debug_* or trace_* methods on Celo, re-run them against the new client before you depend on the output.
  • BNB Chain serves part of its traffic from reth-bsc rather than geth. The same advice applies to tracing and deep historical reads.

No RPC method limits, error codes or rate limits changed in this window.