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: Avalanche Helicon lands ahead of 22 September, and this month's end-of-support dates arrive

Ankr Team
Docs Team

Avalanche's Helicon upgrade activates on 22 September at 15:00 UTC, and our nodes already run the release that carries it. Core shipped an emergency hardfork, Sui moved to protocol 136, and Ethereum mainnet and Sepolia moved to reth v2.5.2. Separately, Solana activated Transaction V1 today, and that one needs a change in your client.

Network upgrades​

Each of these has an activation date or is flagged mandatory upstream, and the upgrade landed before it:

  • Avalanche: mainnet nodes on AvalancheGo v1.15.0, the Helicon release. Helicon activates on 22 September at 15:00 UTC. It brings continuous execution, a dynamic minimum gas price, auto-renewed staking, a shorter minimum staking period, and a 90% uptime requirement. If you run your own Avalanche node behind the same integration, upgrade it before that instant.
  • Core: mainnet nodes run v1.0.26, past the emergency hardfork that activated on 3 September at 01:00 UTC to close a block reward exploit. Testnet2 moved on the same schedule.
  • Solana: Transaction V1 activated at the start of epoch 1035 on 15 September. It has its own entry, because it is the one item this week that breaks working client code.
  • Sui: mainnet nodes on mainnet-v1.79.1, carrying protocol version 136, which takes effect at an epoch boundary rather than a fixed time. Testnet went first, on testnet-v1.79.0.
  • TRON: mainnet nodes on GreatVoyage-v4.8.2.2, which upstream marks mandatory. It covers transaction validation consistency, Stake 2.0 and SELFDESTRUCT edge cases, and jump table fixes. There is no fork deadline attached to it.
  • NEAR: nodes on nearcore 2.13.4, which upstream ships as a security release.
  • IOTA: mainnet on v1.31.2. Testnet moved to protocol 34 first.

Client versions​

  • Ethereum mainnet and Ethereum Sepolia: reth v2.5.2. web3_clientVersion returns reth/v2.5.2-5a6940e on both.
  • Optimism Sepolia: op-reth v2.4.4.
  • Arbitrum One: Nitro v3.11.4. Offchain Labs published the binary build ahead of the source release, so there is no upstream release page to link yet.
  • Filecoin: Lotus v1.36.3.
  • Sui Walrus: mainnet storage nodes v1.55.2, testnet on v1.56.0.

Deprecations and end of support​

The two dates we announced last week arrived today, 15 September. Nothing new was added this week.

  • Fifteen endpoints stopped answering. Fuel, Xai, Syscoin, Rollux, Kusama, Litecoin and the last Tenet surface are gone entirely, and six testnets and variants are gone while their network stays. The full list and the exact endpoint strings to grep for are in last week's entry. Their API reference pages are removed and inbound links resolve to the chain list.
  • Historical tracing on Kaia ended. The five debug_trace* methods that were the documented exception to debug_* being unsupported on Kaia now answer only for recent history, and a state read at an explicit older block needs archive state a full node does not hold. What still works and what does not.
  • Sui JSON-RPC. The implicit fallback to the Sui Foundation archival service disconnects at the end of September 2026. After that, historical and pruned reads over JSON-RPC can return incomplete results. Sui is removing the JSON-RPC interface from its node software, so migrate to gRPC or GraphQL.

Worth checking on your side​

  • Solana is the one that needs code changes. Set maxSupportedTransactionVersion to the integer 1 and check your decoder. Details and the three defaults that changed.
  • Avalanche Helicon, 22 September at 15:00 UTC. Our nodes are ready. Yours need to be too if you run one.
  • If you still call one of the fifteen retired endpoints, you are already getting an error. Since the 31 August tier change a few of them answer HTTP 200 carrying -32000 Unauthorized rather than a 403, and a client that only checks the status code reads that as success.
  • No method limits, error codes, batch caps or block-range caps changed on any network that stays. The -32015 on Solana comes from the node software, not from our gateway, and it is listed on the error reference alongside the codes the gateway returns.