NewRobinhood Chain dedicated RPC nodes · private endpoint · unlimited RPSRobinhood Chain nodes · from $199/moConfigure →
ChainsRobinhood ChainNEWfrom $199/moArcNEWfrom $199/moEthereumfrom $199/moSolanafrom $999/moBSCfrom $199/moBasefrom $199/moArbitrumfrom $199/moPolygonfrom $199/moAvalanchefrom $199/moBitcoinfrom $199/moBrowse all chainsFull index (1,000+)
SolutionsTrading bots & MEVIndexers & analyticsExchanges & paymentsChain teams & validatorsBring your own hardware
ResourcesUpdatesWhat is a dedicated RPC node?LocationsFAQAbout
PricingContact
Updates

What changed, and when.

New chain pages, the network changes we record from official docs (hardforks, client sunsets, mandatory upgrades), offers, and the occasional write-up. Same feed as our Telegram channel, or take the RSS.

Latest posts

Written for people who run nodes.

16 Sept 2026 · comparison

Stablecoin-native L1s compared for node operators: Arc, Stable, Plasma and Tempo

Four Layer-1s built around stablecoins launched within a year of each other. This is the comparison from the operator's chair: chain IDs, gas tokens, consensus, what node types exist, the hardware each chain's docs ask for, and what a dedicated node costs.

Read →
16 Sept 2026 · launch

Arc mainnet is live: what a dedicated Arc node looks like on day one

Circle's Arc launched its public mainnet on 16 September 2026. Here is what the network is, what you can run on it, the hardware Arc's own docs ask for, and what a dedicated Arc node costs.

Read →
The log · 125 entries

Everything, newest first.

  1. Post

    Stablecoin-native L1s compared for node operators: Arc, Stable, Plasma and Tempo

    Four Layer-1s built around stablecoins launched within a year of each other. This is the comparison from the operator's chair: chain IDs, gas tokens, consensus, what node types exist, the hardware each chain's docs ask for, and what a dedicated node costs.

  2. Post

    Arc mainnet is live: what a dedicated Arc node looks like on day one

    Circle's Arc launched its public mainnet on 16 September 2026. Here is what the network is, what you can run on it, the hardware Arc's own docs ask for, and what a dedicated Arc node costs.

  3. New chain

    Arc mainnet page

    Arc moved from testnet to mainnet on our side the day Circle launched it: chain ID 5042, USDC gas, dedicated full and archive nodes from $199/mo.

  4. New chain

    GIWA page

    Dunamu (Upbit) OP Stack L2. Nodes on GIWA Sepolia today, mainnet on launch day, from $99/mo.

  5. Site

    Pricing cards on every chain page

    Full, archive and validator prices side by side above the configurator, each card opening the configurator with that node type picked.

  6. Site

    Telegram channel

    New chain pages, offers and weekly network changes now post to @argusnodes_channel automatically.

  7. Network change

    Arc

    Arc mainnet went live on 16 September 2026 with more than 100 institutional and ecosystem builders on day one, an 11-member founding validator cohort and USDC as the gas token; Circle names Alchemy, Blockdaemon, Chainlink, Figment, Kaleido and QuickNode among the launch infrastructure providers. source ↗

  8. New chain

    Gno.land page

    Beta Mainnet (gnoland1) nodes from $99/mo; the gnoland-1 mainnet is not launchable yet.

  9. Offer

    Robinhood Chain promoted

    First in the Chains menu and on the homepage: dedicated Robinhood Chain RPC nodes from $199/mo.

  10. Site

    Homepage price picker

    Pick any researched chain and node type on the homepage and see the starting price before talking to anyone.

  11. Site

    GetBlock comparison

    GetBlock added as the seventh provider in every comparison table, read from its own pages.

  12. Offer

    STANDARD band at $199

    Every chain that was $349 moved to $199/mo starting, Solana excepted. Four bands: $99, $199, archive from $799, Solana class $999.

  13. Site

    Full chain index

    Every network alive on its own chain ID in the canonical registry now has a page, priced on the same flat terms.

  14. Network change

    Arc

    arc-node v0.8.0 (28 August 2026) is mandatory: Zero8 activated on testnet at 2026-09-03 15:00 UTC and Zero7/Zero8 on mainnet at 2026-09-10 15:00 UTC. It moves to reth 2.2 with Storage V2 snapshots, disables admin RPC routes by default (--rpc.admin to enable), makes arc-snapshots download take explicit --chain and --el-profile flags, and deprecates the separate-host EL/CL RPC transport ahead of removal in v0.9.0. source ↗

  15. Network change

    MegaETH

    Mainnet has taken frequent hardforks in 2026 (Rex2 4 Feb, Rex3 21 Feb, Rex4 20 Apr, Rex5 5 Jun) and Rex6 is scheduled for 25 August 2026 03:00 UTC; Rex7 is unscheduled. source ↗

  16. Network change

    Igra

    Attesters stake a minimum of 400,000 IGRA permissionlessly, with slashing of 1/16 of stake only for provable fraud; the attester staking lock's intended unlock date is 24 August 2026. source ↗

  17. Network change

    ADI

    Mainnet docs list ERC-7702, ERC-4844 and debug_traceCall with custom tracers as unsupported; the chain was producing blocks (height 1,004,563) on 22 August 2026. source ↗

  18. Network change

    Aura Network

    The official docs site docs.aura.network has been returning HTTP 525 (SSL handshake failure) as of 2026-08-22; the documentation source remains readable in the aura-nw/docs GitHub repo, last updated 2025-02-24. source ↗

  19. Network change

    Dexalot

    The Dexalot subnet (chain 432204) is live and producing blocks: the official RPC returned block 72,431,093 on 2026-08-22, and the docs repo was last updated Jun 3, 2026. source ↗

  20. Network change

    ENI

    Mainnet is live: the official RPC returned chain ID 173 and block 37,120,983 on 2026-08-22. source ↗

  21. Network change

    Firo

    The client is actively maintained (repository pushed August 22, 2026). source ↗

  22. Network change

    GateLayer

    No official hardware figures exist beyond 'typically 1-5 TB' of disk for archive mode; mainnet was producing blocks (height 29,317,227) on 22 August 2026. source ↗

  23. Network change

    Terra

    The former official endpoints phoenix-lcd.terra.dev and phoenix-rpc.terra.dev now redirect to lcd-terra.tfl.foundation / rpc-terra.tfl.foundation, which returned 'No provider found to serve this request' on 2026-08-22, and a 'Terra Node Syncing Issue' opened January 2026 is still open; confirm chain liveness with the founder before listing. source ↗

  24. Network change

    Warden Protocol

    Mainnet (warden_8765-1) is live: the official RPC reported height 10,106,755 on 2026-08-22 running CometBFT 0.38.19, and the chain was upgraded to wardend v1.0.1 at block 5,418,000 in March 2026 (v1.0.0 tagged March 3, 2026; v1.0.1 tagged March 23, 2026). source ↗

  25. Network change

    XPR Network

    Mainnet is live (chain 384da888...437e0, head block advancing 2026-08-22) with 21 active producers; docs.xprnetwork.org carries no node-operator section, so node setup relies on the xpr.start repo. source ↗

  26. Network change

    Bifrost (Polkadot)

    The Bifrost source repository linked from the collator docs (github.com/bifrost-io/bifrost, binary bifrost-v0.15.0) now returns 404; runtime releases continue in github.com/bifrost-io/bifrost-release, most recently bifrost-v0.25.4 on 21 August 2026 (low-priority upgrade, runtime 25004 for Bifrost Polkadot, Kusama and Paseo). source ↗

  27. Network change

    Cardano

    UTxO-HD is now mandatory: node 10.4.1 integrated UTxO-HD (in-memory or LMDB on-disk backend), 10.7.0 added the LSM-tree on-disk backend, and 11.1.0 (pre-release 2026-08-21) removes the V1 LedgerDB and LMDB backend and the legacy tracing system, so LMDB users must switch backends and migrate tracing config. source ↗

  28. Network change

    Cosmos Hub

    Gaia v28.0.0 (pre-release tagged 21 August 2026) removes the Interchain Security provider module entirely; the upgrade handler sets staking max_validators to the former max_provider_consensus_validators. source ↗

  29. Network change

    Etherlink

    Ganesha 7.0 activated on 21 August 2026, adding the Michelson interface and Native Atomic Composability; it requires octez-evm-node 0.64 or later (released 30 July 2026). source ↗

  30. Network change

    Tempo

    Tempo ships required hardforks on a bi-weekly to monthly cadence with at least 7 days' mainnet notice; T1 through T10 (v1.1.1 to v1.13.0) activated between February 12 and August 21, 2026, and consensus-breaking upgrades are mandatory. source ↗

  31. Network change

    ADI

    On 20 August 2026 at 15:00 UTC ADI mainnet (testnet on 18 August) switched to a new P2P (devp2p) protocol; external nodes still on the old HTTP-replay version stopped syncing and must run v0.20.12, which replaces HTTP replay with P2P (port 3060 TCP+UDP), removes the proof-sync sidecar and needs an updated genesis file. source ↗

  32. Network change

    Boba

    Isthmus (20 August 2026) and Jovian (25 August 2026) activate on Boba Sepolia with mandatory op-node v1.19.0 / op-reth v2.3.1 and runtime chain-spec files; Boba Mainnet dates are not yet scheduled. source ↗

  33. Network change

    Canton Network

    Splice 0.7.4 (tagged 20 August 2026) upgrades the bundled Canton to 3.5.14; validators are expected to stay current with network versions. source ↗

  34. Network change

    Filecoin

    Forest ships frequently (v0.36.0 on 20 August 2026) and Venus remains active (v1.20.0, 18 May 2026), so all three listed clients are maintained as of August 2026. source ↗

  35. Network change

    Nibiru

    Hotfix v2.18.1 (2026-08-20) is a mainnet security upgrade; operators must pre-stage the matching nibid binary before the scheduled upgrade height. source ↗

  36. Network change

    Starcoin

    Starcoin v1.13.21 (released 2026-08-20) is an emergency mandatory hard fork for Main: every node must upgrade before block 32,165,300 (projected about 2026-08-21 23:46 UTC+8); from that height every block must carry an Ed25519 block permit signed by a compiled-in authorization key, and v1.13.20 or older nodes fall onto a legacy fork. source ↗

  37. Network change

    Aleo

    snarkOS v4.9.1 (August 19, 2026) is a mandatory upgrade with mainnet consensus activation at height 21,342,000 (predicted August 24, 2026); v4.9.0 (July 29, 2026) activated at height 20,794,000 and v4.8.0 (June 29, 2026) at height 19,860,000, so operators must track frequent consensus-version upgrades. source ↗

  38. Network change

    Obyte

    ocore 0.4.6 (protocol version 4.0) is actively developed with commits through 19 August 2026; minimum core version for full nodes is 0.4.2. source ↗

  39. Network change

    Ergo

    Latest stable client is 6.0.4 (18 August 2026); 6.1.x builds are RocksDB variants published as pre-releases and 6.5.0 'Ergo Matrix' is DevNet-only. source ↗

  40. Network change

    Fluent

    The official node binary is `fluent`, built from the fluentlabs-xyz/fluentbase repo (latest release v1.4.0, August 18, 2026), with prebuilt binaries and a ghcr Docker image; the docs site itself publishes no node-operator or hardware guide. source ↗

  41. Network change

    Solana

    Agave 4.2 is the recommended mainnet release for August 2026 with feature activations beginning the week of August 17, 2026: a 90% rent reduction, larger (4096-byte, v1 format) transactions, and slot times stepping from 400ms to 200ms; indexers decoding raw transaction bytes must handle the v1 layout. source ↗

  42. New chain

    Robinhood Chain page

    Arbitrum Orbit chain from Robinhood (chain ID 4663): dedicated full and archive nodes from $199/mo.

  43. Network change

    Supra

    Mainnet (chain id 8) runs node binary supra_node_v11.5.1 with framework aptosvm-v1.16_supra-v1.8.15 since epoch 7573 (2026-08-14); governance proposal 37 activated the v11 feature flags (BLS keys, BCFT certificates, DKG, inclusion proofs) at epoch 7575, and validators still on legacy ed25519 keys were dropped from the active set (83 to 66). source ↗

  44. Network change

    Acala

    Acala and Karura remain actively maintained: runtime 2.37.0 (2026-08-13) adjusted governance parameters to prevent spam attacks, following 2.36.0 (2026-06-14), 2.35.0 (2026-03-17) and 2.34.0 (2026-02-21); these are runtime releases with no node-operator action required. source ↗

  45. Network change

    Firo

    On August 13, 2026 Firo disclosed and mitigated a Spark protocol vulnerability (coin forgery in multi-input spends; about 200 FIRO minted by the researcher on mainnet) and shipped mandatory v0.14.17.2, which restricts each Spark spend to a single coin until the v0.14.18.0 hard fork targeted for the third week of August 2026. source ↗

  46. Network change

    Karura

    Karura shares the Acala codebase and release train: runtime 2.37.0 (2026-08-13, branch release-karura-2.37.0) adjusted governance parameters to prevent spam attacks, after 2.36.0 (2026-06-14), 2.35.0 (2026-03-17) and 2.34.0 (2026-02-21), so Karura is still actively maintained. source ↗

  47. Network change

    Aptos

    Node releases are frequent (v1.48.6 on 2026-08-12, v1.48.7-hotfix on 2026-08-19); operators are expected to track mainnet releases closely. source ↗

  48. Network change

    IOTA

    iota-node is actively maintained with frequent network releases (mainnet v1.29.0 on 12 August 2026, v1.30.x on testnet/devnet in the same month); the operator docs also say IOTA plans to migrate indexing-heavy RPC endpoints away from full nodes to the separate iota-indexer / GraphQL services. source ↗

  49. Network change

    Nolus

    nolus-core v0.8.4 (2026-08-12) adds the v0.8.4 upgrade handler and bumps ibc-go to v10.5.0-nolus-1, following v0.8.3 (2026-08-04) which moved to Go 1.25 and the Nolus ibc-go fork with a Solana light client. source ↗

  50. Network change

    Qubic

    Bob, the indexer exposing Ethereum-style JSON-RPC 2.0 and REST, is under active release (v1.5.16 on 2026-08-12) and is the official RPC/API component listed alongside Core and Core Lite. source ↗

  51. Network change

    Stacks

    stacks-core 4.0.2 (August 11, 2026) is a recommended bugfix release that adds a Bitcoin Core 31+ compatibility fix requiring burnchain.wallet_name to be set. source ↗

  52. Network change

    Namada

    Namada apps v201.0.9 (2026-08-10) is the latest release on the v201 mainnet line, fixing ZK proof validation and updating the CometBFT docker image to 0.37.16; the SDK was re-licensed to MIT. source ↗

  53. Network change

    Reya

    On August 7, 2026 Reya moved its mainnet sequencer to Conduit, still running a customised Arbitrum Orbit build, with no change to endpoints or chain ID. source ↗

  54. Network change

    Somnia

    The Jig hard fork activated on 6 August 2026 with sustained-use gas discounts and sender-dependent GASPRICE semantics; after upgrading, node operators can reclaim hundreds of GB by deleting retired storage types. source ↗

  55. Network change

    Ink

    The inkonchain/node repo (last commit August 5, 2026) still ships only op-geth and an archive path that depends on geth snapshots from the Gelato index; its README says an op-reth Compose path is still pending. source ↗

  56. Network change

    ApeChain

    The official replica image is nitro-node:apechain-3.9.9 and the docs say a node syncs from snapshot in up to a few hours; the latest published mainnet snapshot (30 July 2026) is about 1.2 TB compressed. source ↗

  57. Network change

    Darwinia

    v7.0.3 (2026-07-30, Upgrade Priority LOW) is the latest release (Darwinia2 spec 7030, increased governance decision window) with pre-built Linux binaries and a ghcr.io image; the node-operator docs (last updated 2026-01-28) still show v6.7.1 in their download commands, so check the releases page for the current binary. source ↗

  58. Network change

    Obyte

    A further protocol upgrade (pemCurvesFix, noPrivateAssetsWithConditions, bestParentPrefersOp) activates at mainnet MCI 12,155,000; the activation MCI was pushed back on 29 July 2026, so nodes must run current ocore before it is reached. source ↗

  59. Network change

    Ontology

    Ontology v3.1.2 (29 July 2026) is a mandatory upgrade: 'All mainnet nodes need to be upgraded BEFORE the block height of 20800000'. source ↗

  60. Network change

    Ontology

    The client is actively maintained (repository last pushed 29 July 2026), but the developer docs do not publish hardware requirements or an archive mode, so sizing must come from operator experience. source ↗

  61. Network change

    Qubic

    Core release v1.301.0 (2026-07-29) was a mandatory non-seamless update adding the Bpp9000 mining algorithm and outsourced-computations consensus, and releases continue weekly per epoch (v1.301.7 on 2026-08-19 for epoch 227). source ↗

  62. Network change

    AtomOne

    The docs.atom.one node setup and upgrade guides still reference v1.1.2 and Go 1.22.10, so use the atomone-hub/networks repo for current binary versions; the project is actively maintained (latest release 2026-07-28). source ↗

  63. Network change

    Bifrost Network

    bifrost-node v2.2.1 (28 July 2026) is a mandatory update fixing a block-sync panic and a relay-executive membership hook; the client is actively maintained (repo pushed 21 August 2026). source ↗

  64. Network change

    Bitcoin Cash

    BCHN v29.1.0 (2026-07-28) is an optional release that raises default -rpcthreads 4 to 16 and -rpcworkqueue 16 to 64 and adds spent-output RPCs. source ↗

  65. Network change

    Zcash

    NU6.3 (Ironwood) activates on mainnet at height 3,428,143 (~2026-07-28); Zebra v6.0.0 (2026-07-10) or later is mandatory and has an end-of-support height of 3,528,960. source ↗

  66. Network change

    Bitcoin SV

    Teranode source is public and shipping (v0.15.8 on July 27, 2026; v0.16.0 betas through August 6, 2026) but the official docs still place it in a testnet phase on Teratestnet; SV Node remains the documented mainnet client. source ↗

  67. Network change

    Sui

    JSON-RPC deprecated: disabled on Sui Foundation mainnet full nodes the week of 27 July 2026, full decommission (code removal) mid-October 2026; migrate to gRPC or GraphQL RPC. source ↗

  68. Network change

    Avail

    avail-node v2.3.5.0 (2026-07-23) raised the minimum supported Rust version to 1.88 and bumped the SP1 SDK to v6 for anyone building from source; v2.3.6.0 (2026-08-17) is the latest release, so the project is actively maintained. source ↗

  69. Network change

    Nibiru

    nibid v2.17.0 (2026-07-23) added EVM mempool protection (8 live nonce slots per sender), governance-controlled Wasm block hooks and vendored Cosmos SDK/IBC Go v7 into the repo. source ↗

  70. Network change

    Alephium

    Full node v4.6.0 (20 July 2026) redesigned the full-node websocket, which affects WebSocket consumers. source ↗

  71. Network change

    Cardano

    Van Rossem intra-era hard fork to protocol version 11 activated on mainnet 18 July 2026 (ratified 13 July 2026); cardano-node 11.0.1 (released 2026-05-05) is the version that crosses the boundary. source ↗

  72. Network change

    Zcash

    zcashd reached End of Life: all zcashd 6.20.0 nodes halted automatically on 2026-07-18 at block 3417100 and the zcash/zcash repository is archived; node operators must run Zebra and wallet users migrate to Zallet. source ↗

  73. Network change

    Zcash

    Zebra v6.2.0 (2026-07-17) adds an experimental zcashd-compat mode for custodians and v6.3.0 (2026-08-10) is the current release; Zebra is actively maintained by the Zcash Foundation. source ↗

  74. Network change

    Chia

    Project is actively maintained: chia-blockchain 2.7.3 was released 16 July 2026 (2.7.2 on 9 July 2026 added Weight Proof v2 and Python 3.14 support). source ↗

  75. Network change

    Stacks

    stacks-core 4.0.1 (July 15, 2026) contains the Epoch 4.0 (PoX-5, Clarity 6) hard fork activating at Bitcoin block 960,230 (about July 30, 2026); 3.4.x nodes diverge after that height, and from 4.0.1 stacks-node and stacks-signer ship as one combined release with a shared version. source ↗

  76. Network change

    Neutron

    On 14 July 2026 the neutron-org/neutron repository was archived and placed in maintenance mode with no active security monitoring; the canonical repository for releases and security fixes is now github.com/solva-solutions/neutron, and other core repos (neutron-sdk, neutron-std, mainnet-assets, testnets) were archived on 1 July 2026. source ↗

  77. Network change

    Bifrost (Polkadot)

    Following the Hyperbridge security incident, Bifrost announced on 13 July 2026 that it is discontinuing Hyperbridge, taking an on-chain snapshot at 15 July 2026 06:00 UTC and restoring affected vDOT/vETH balances through governance, with Hyperbridge ETH variants replaced 1:1 by Snowbridge ETH. source ↗

  78. Network change

    Mixin

    Mixin Kernel v0.19 ('fleet fireflies') was tagged July 13, 2026 with follow-up tags v0.19.5 (August 5, 2026) and v0.19.6 (August 10, 2026); the previous numbered line was v0.18.0 from February 2024, so operators on older builds should upgrade. source ↗

  79. Network change

    Berachain

    Fusaka (Fulu) hard fork activated on mainnet 8 July 2026 16:00 UTC; BeaconKit v1.4.1 mandatory ('All mainnet operators must upgrade to this version before the fork activates'). source ↗

  80. Network change

    Ink

    Upgrade 19 (Karst hard fork) activated on mainnet OP Stack chains including Ink on July 8, 2026 16:00:01 UTC, requiring op-node v1.19.1 and op-reth v2.3.3 before activation. source ↗

  81. Network change

    Qubic

    The original qubic-archiver (go-archiver) is end-of-life and unmaintained; operators must migrate to archiver-v2 (go-archiver-v2, v1.6.1 released 2026-07-08) using the archiver-db-migrator tool. source ↗

  82. Network change

    GIWA

    Upgrade 19 (Karst) activated on GIWA Sepolia on 6 July 2026 at 15:00 KST (timestamp 1783317600): Osaka EVM, a 16,777,216 per-transaction gas cap, BN256 pairing input capped at 300 pairs, fault proofs moved from CANNON to CANNON_KONA (kona-client) and the L2 Contract Manager. op-geth and op-program do not support it. source ↗

  83. Network change

    Robinhood Chain

    Robinhood announced Robinhood Chain mainnet on July 1, 2026 alongside stock tokens and DeFi products, and the docs state 'Robinhood Chain is live'. source ↗

  84. Network change

    Chiliz

    Chiliz Chain 2.8.1 (June 2026) schedules the Cancun hard fork for 30 June 2026 11:00 CEST and Pascal/Prague for 11:30 CEST on mainnet, so nodes must run v2.8.1 or later. source ↗

  85. Network change

    Filecoin

    Lotus patch releases v1.36.1 (30 June 2026) and v1.36.2 (27 July 2026) followed with Ethereum RPC correctness fixes and a switch from the deprecated Jaeger exporter to OTLP. source ↗

  86. Network change

    GateLayer

    node-binary v2.0.0 (30 June 2026) ships gatelayer-reth (op-reth based) plus gatelayer-node in place of the earlier gatelayer-geth binary; the RunRPCNode docs page still describes op-geth, so follow the repo for current binaries. source ↗

  87. Network change

    Neutron

    On 30 June 2026 Neutron's official X account stated that, per the Neutron Foundation's announcement to enter long term support, Foundation-supported front ends had been deprecated and published a CLI guide for withdrawing funds; neutron.org, docs.neutron.org, forum.neutron.org and governance.neutron.org now all redirect to that post. source ↗

  88. Network change

    RISE

    Official node software is the risechain/rise-node compose stack (rise-exec replica and rise-op-node images, plus daily mainnet snapshots); latest release v0.6.0 on June 29, 2026, and testnet snapshots are 'currently unavailable'. source ↗

  89. Network change

    0G

    Aristotle v1.0.6 (19 Jun 2026) was a mandatory upgrade before 2026-06-26 00:00 UTC, enabling double-sign slashing. source ↗

  90. Network change

    Bifrost Network

    bifrost-node v2.2.0 (24 June 2026) upgraded to polkadot-sdk stable2512, adding Ethereum Fusaka hard-fork compatibility at the EVM layer. source ↗

  91. Network change

    Cronos

    Mainnet upgrade table now runs through cronos v1.7.0 at block 58,825,800; latest stable releases are the v1.7.x line (v1.7.8 on 24 June 2026) with v1.8.0-alpha (17 July 2026) previewing libp2p networking and Block-STM execution. source ↗

  92. Network change

    Manta Pacific

    A migration window on Wednesday 24 June 2026 at 18:00 CET moved Manta Pacific batches from the forked OP Stack Celestia implementation to the native Alt-DA OP Stack approach; replicas had to switch op-geth to op-reth, update op-node and run an op-alt-da Celestia component or fall off the chain. source ↗

  93. Network change

    AtomOne

    The v4 upgrade (Proposal #21, block 9550000, v4.0.0 released 2026-06-23) moved AtomOne to the AtomOne Cosmos SDK v0.50 fork and IBC v10, added x/coredaos, and requires Go 1.26.4; operators should run v4.0.1 or later (v4.1.0 released 2026-07-28). source ↗

  94. Network change

    Ink

    Ink announced (June 23, 2026) that it is moving to OP Enterprise Fully Managed, with Optimism running sequencers, RPC, explorer and incident response from an August 2026 cutover; chain ID and contracts are unchanged, and features like one-day withdrawals and 200ms subblocks are planned. source ↗

  95. Network change

    Venom

    Venom Foundation published its 'Venom migrates to next-generation protocol' FAQ on 18 June 2026, so the migration window is running as of August 2026. source ↗

  96. Network change

    Flare

    go-flare v1.14.0 (June 17, 2026, AvalancheGo 1.14.0) was mandatory on Flare before July 14, 2026 12:00 UTC; it raises the minimum C-chain base fee to 500 GWei, lifts the maximum validator stake from 200M to 300M FLR and sets a 20% minimum delegation fee. source ↗

  97. Network change

    Axelar

    The v1.4 mainnet upgrade (axelar-core v1.4.7, proposal 480, height 30135800, ~14:00 UTC 2026-06-16) removed the legacy link-deposit token-transfer paths, routes legacy EVM governance via Amplifier GMP, and bumps to CometBFT v0.38.23, wasmd v0.54.7, libwasmvm v2.2.6, Cosmos SDK v0.50.15 and ibc-go v8.8.0. source ↗

  98. Network change

    TON

    Native token renamed from Toncoin (TON) to Gram (GRAM) on 15 June 2026 after a TON Vote referendum; balances and contracts unchanged, no migration. Official docs now refer to Gram throughout. source ↗

  99. Network change

    XRPL

    XRP Ledger v3.2.0 (15 June 2026) renamed the core server from rippled to xrpld under XLS-0095: package names (xrpld RPM/DEB), config file (/etc/xrpld/xrpld.cfg), database directory (/var/lib/xrpld/db/), service name and user-agent all changed; an official migration guide exists. Peering port now defaults to 2459; NuDB block size configurable; TLS/mTLS for gRPC. source ↗

  100. Network change

    Akash Network

    Mainnet 18 (akash v2.1.0, Proposal 328) was scheduled for block 27,230,465 around 2026-06-11 and ships Oracle v2 (full oracle state wipe and re-init) plus AEP-82 resource reclamation; the latest release is v2.1.1 (2026-07-24) with v3.0.0 alphas in progress. source ↗

  101. Network change

    Secret Network

    v1.25.0 (released 2026-06-10) added beta support for non-SGX nodes that replay enclave traces from an upstream SGX node over gRPC, plus MachineID replacement and ProofOfCloud-validated machines. source ↗

  102. Network change

    Verona (formerly XION)

    xiond v30.0.0 (2026-06-09) applied the remaining Xion-to-Verona branding renames in the binary and API docs. source ↗

  103. Network change

    Provenance

    provenanced v1.29.0 (8 June 2026) and v1.30.0 (20 August 2026) followed; v1.30.0 deprecates and deactivates the quarantine module, so node operators should expect roughly bi-monthly coordinated upgrades. source ↗

  104. Network change

    Arc

    arc-node v0.7.2 (4 June 2026) lowered the default JSON-RPC gas cap to 30M, capped batch requests at 100 entries and rejects replay-unprotected (pre-EIP-155) transactions over RPC by default. source ↗

  105. Network change

    Sora

    The Substrate-based SORA network is still being released: sora2-network 4.8.8 (framenode) shipped on 4 June 2026 together with runtime upgrades 4.8.6 to 4.8.8. source ↗

  106. Network change

    Vara Network

    gear v2.0.0 (2026-06-02) is a mandatory node binary upgrade (runtime spec 20000): the WASM sandbox moved from Wasmer to Wasmtime, gclient was merged into gsdk, and the repository was reorganized to separate Vara from the new Vara.ETH execution environment. source ↗

  107. Network change

    NEAR

    nearcore 2.11.0 carried protocol version 83 (vote 13 Apr 2026) and a further upgrade to protocol 84 was scheduled for 1 June 2026; testnet and mainnet releases run ~5 weeks apart. source ↗

  108. Network change

    Radix

    Cuttlefish (node v1.3.0) was the last mandatory protocol update, enacted by validator readiness signal in December 2024; since then only opt-in Cuttlefish patch releases have shipped, most recently v1.3.0.4 (April 2026) and v1.3.0.5 (1 June 2026) adding the db.keep_previous_substate_values disk-space option. source ↗

  109. Network change

    B² Network

    The official node guides still pin op-geth v1.101315.2 / op-node v1.7.7 (snapshot 20250707) and the public RPC reported Geth/v1.101315.2 on 22 Aug 2026; OP Labs declared op-geth end-of-support on 2026-05-31, so B² nodes depend on a frozen client line with no published op-reth path. source ↗

  110. Network change

    Blast

    Blast's node stack (blast-geth) is a fork of op-geth; Optimism's upstream op-geth reached end of support on 31 May 2026, and Blast has published no migration path to reth.

  111. Network change

    BOB

    OP Labs marks op-geth as end-of-support on 31 May 2026 and names op-reth the primary supported execution client for OP Stack nodes, so any remaining op-geth BOB nodes should be migrated. source ↗

  112. Network change

    Boba

    op-geth and op-erigon reached end-of-life on 31 May 2026; op-reth is the only supported execution client and a migration guide generates a reth database from existing data. source ↗

  113. Network change

    GateLayer

    OP Labs declared op-geth end-of-support on 2026-05-31 and it does not support the Karst hardfork; GateLayer's published docker-compose still pulls ghcr.io/gatechain/geth, so confirm the supported execution image with Gate before deploying. source ↗

  114. Network change

    Ink

    op-geth support ended May 31, 2026; Optimism says all node operators should migrate to op-reth (v2.2.3 or later), and op-geth cannot follow the now-active Karst hard fork. source ↗

  115. Network change

    Katana

    op-geth reached end-of-support on 31 May 2026 and does not support the now-active Karst hardfork; Katana's official node configs mark op-geth deprecated and tell all operators to run op-reth (v2.2.3 or later per OP docs). source ↗

  116. Network change

    Mode

    Optimism ended support for op-geth on 31 May 2026; op-geth does not support the Karst hardfork, so OP Stack node operators are told to migrate to op-reth v2.2.3 or later while op-node continues. source ↗

  117. Network change

    Optimism

    op-geth reached end-of-support on 2026-05-31 and does not support the Karst hardfork, so op-geth nodes can no longer follow the canonical chain; operators must run op-reth (or Nethermind). source ↗

  118. Network change

    Soneium

    OP Labs lists op-geth as end-of-support on 31 May 2026 and op-reth as the primary supported execution client, while Soneium's FAQ still documents op-geth; node operators should plan for op-reth. source ↗

  119. Network change

    Astar

    Client v5.49.2 (28 May 2026) was a CRITICAL upgrade migrating collators to slot-based Aura consensus, required by runtime-2207 (10 Jun 2026), which also froze WASM contract uploads and instantiation. source ↗

  120. Network change

    Moonriver

    Client v0.52.0 (28 May 2026) made slot-based authoring mandatory with a dynamic relay-parent offset; blocks authored with the wrong offset are rejected by the runtime, so collators and RPC nodes should run v0.52.x (latest v0.52.3, 15 Jun 2026). source ↗

  121. Network change

    Fetch.ai

    Actively maintained as of Aug 2026 (fetchd repo pushed 27 May 2026, mainnet reports fetchd v0.15.0 on CometBFT 0.38), but the docs active-networks page still lists v0.14.0 as the current mainnet version and the ledger is now documented under the ASI Network brand. source ↗

  122. Network change

    Boba

    The latest official mainnet archive snapshot (Reth, 26 May 2026) is 13.9 GB; no hardware requirements are published in the node-operator docs. source ↗

  123. Network change

    Citrea

    The CTR governance token went live for trading and staking on 26 May 2026, and Citrea marked six months of the Clementine bridge on 4 Aug 2026. source ↗

  124. Network change

    DATA Network (formerly Story)

    Seneca (story v1.8.0, released 25 May 2026) was a mandatory hardfork at height 18,173,000 that reduced the active validator set from 80 to 21 per SIP-00011. source ↗

  125. Network change

    Cronos POS Chain

    chain-main v7.2.0 (20 May 2026, upgrade plan v7 at heights above 29,782,800) rewrote the chain's tokenomics with new x/inflation and x/tieredrewards modules and upgraded to Cosmos SDK v0.53.4 and IBC v10.5.1. source ↗

Ask AI what changed on a chain you runClaudeChatGPTPerplexityGrokGoogle AI Mode
Path B · Your metal

Already own servers? We set up your RPC node on them.

Colo racks, spare machines, hardware your compliance rules say you must own: we install, sync, tune and monitor the node on your servers. You keep the hardware and the custody. You get the same private endpoint, the same no-limits configuration, the same dashboard and the same 24/7 engineers, for one flat monthly management fee, quoted within the hour and payable in crypto. We never charge for metal.

Send us your specs and we confirm the fit against the chain's own requirements before anything is billed.

  1. 01We audit your specs
  2. 02We install, sync and tune
  3. 03We keep watch, 24/7
Talk to us on TelegramTelegram