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: Taiko Unzen, Arbitrum Nitro 3.11.3, and clients rolled forward on 30 chains

Ankr Team
Docs Team

Nine of these upgrades tracked a hard activation, where a node left on the old version stops following the chain. Taiko's Unzen fork and Somnia's Jig fork both activated inside this window and we landed ahead of both. Monad testnet activated MONAD_TEN on 12 August, and our nodes were already on the release that carries it. Nothing changed in RPC method limits, error codes or rate limits.

Network upgrades​

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

  • Taiko: mainnet nodes upgraded for the Unzen hard fork, which activated on 6 August at 13:00 UTC. We waited for the stable client pin rather than running the release candidate into activation. See the Taiko releases.
  • Monad: testnet nodes on v0.16.0, which carried MONAD_TEN (MIP-8), activated on 12 August at 14:30 UTC. Earlier in the window testnet also took v0.15.2.
  • Somnia: mainnet nodes upgraded for the Jig hard fork.
  • Sui: mainnet nodes and validators to v1.76.1, which adds the gRPC query and filter APIs and required a full reindex. Testnet is on v1.77.1.
  • IOTA: mainnet nodes and validators to v1.28.3. Testnet runs the v1.29.0 release candidate for protocol version 32.
  • Gnosis: testnet to Nethermind 1.39.3, which upstream flags as a mandatory update. It hardens ABI decoding against malformed input and fixes memory-pool cleanup in block processing, with no consensus or database format changes.
  • zkVerify: nodes to 2.0.0, the Polkadot SDK stable2512 rebuild, ahead of the runtime 2.0.0 activation.
  • Arbitrum: Nitro v3.11.3 on Arbitrum One, Nova and Sepolia, and on the Orbit chains we serve, Xai mainnet and testnet and Gravity.

Client versions​

Deprecations and end of support​

Nothing new closed in this window. The two items from the last roundup still stand, and one of them has a deadline coming up:

  • Sui JSON-RPC. The implicit fallback to the Sui Foundation archival service disconnects at the end of September 2026, after which historical and pruned reads over JSON-RPC can return incomplete results. Migrate to gRPC or GraphQL.
  • Bahamut remains unserved after the network was discontinued.

Worth checking on your side​

  • Monad testnet. MONAD_TEN activated on 12 August at 14:30 UTC. Our nodes are on the release that carries it. If you run your own Monad testnet node behind the same integration and have not upgraded it yet, it is no longer following the chain.
  • Sui mainnet reindexed. The move to v1.76.1 required a full reindex, and it brings the gRPC query and filter APIs. If you were waiting on those to start your JSON-RPC migration, they are available now.
  • No RPC method limits, error codes, batch caps or range caps changed in this window.