Quicknode — status

We are upgrading our Morph Mainnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC. Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported. During the maintenance window, brief interruptions to RPC availability may occur. RPC changes: - eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected. - Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used. - eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions. - MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702). - Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding. https://github.com/morph-l2/morph/releases/tag/v0.6.4 https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7

Started 2 nov. 2026, 00:00 UTC · Ongoing

We are upgrading our Stacks Mainnet infrastructure to v9.7.0 on 2026-11-02. This release patches recent Node.js security vulnerabilities and introduces new v3 API endpoints for block and transaction data, along with enhanced transaction metadata. A brief database migration will occur during the upgrade, and brief interruptions to RPC availability may occur on that date. RPC Changes: - GET /extended/v3/blocks — New cursor-paginated endpoint for Stacks block summaries, including tenure_height, tx_count, and Bitcoin anchor block reference. - GET /extended/v3/blocks/{height_or_hash} — New endpoint providing Stacks block details, including parent block hash, block size, and execution cost. - GET /extended/v3/bitcoin-blocks — New cursor-paginated endpoint for Bitcoin block summaries with header time and associated Stacks/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash} — New endpoint providing Bitcoin block details with header time and associated block/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash}/blocks — New endpoint listing Stacks blocks anchored to a specific Bitcoin block. - event_count — Added to v3 transaction summaries across all v3 endpoints (transactions list, batch, block transactions, principal transactions, and search). - /v2 RPC proxy — Simplified to a plain passthrough; custom fee estimation and transaction endpoint configuration are no longer available. https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.7.0

Started 2 nov. 2026, 00:00 UTC · Ongoing

We are upgrading our NEAR Mainnet infrastructure to nearcore 2.14.0 on 2026-10-30. This is a mandatory protocol upgrade (protocol version 86 to 88) introducing consensus-breaking changes, new action validation rules, and improved cryptographic support. Validators must upgrade before protocol version 87 voting begins on November 4th. Brief interruptions to RPC availability may occur on that date. RPC Changes: - view_access_key_list now supports pagination with after_key and limit parameters, returning a last_key field. Accounts with more than 100 access keys must use pagination; unpaginated requests for these accounts will fail. - tx, send_tx, and broadcast_tx_commit responses now include an optional cause field on TIMEOUT_ERROR, describing transaction progress (NOT_OBSERVED, PENDING, DOES_NOT_TRACK_SHARD, or ERROR). - tx_status is now the stable method name for what was EXPERIMENTAL_tx_status. Both names work identically; Quicknode documentation for tx_status is in progress. https://github.com/near/nearcore/releases/tag/2.14.0

Started 30 oct. 2026, 00:00 UTC · Ongoing

We are upgrading our Hedera Mainnet infrastructure to Mirror Node v0.165.0 and RPC Relay v0.80.2 on 2026-10-28. This release prepares the mirror node for the Nova/TSS 3.22.0 consensus-layer transition, introduces cryptographic improvements to block proof handling, and adds new REST and gRPC endpoints with enhanced security hardening. Brief interruptions to RPC availability may occur on that date. RPC Changes: Block proof hashing — Block proof hashing is transitioning to a new format. Dual support for both block proof formats is maintained during the rollout period to enable gradual operator deployment. https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.165.0

Started 28 oct. 2026, 00:00 UTC · Ongoing

We are upgrading our Fluent infrastructure to v1.5.1 on 2026-10-28. This release introduces native Ethereum precompiles (0x01–0x11 and P256VERIFY) via revm for significantly faster cryptographic operations, upgrades the rWasm runtime to 0.7.2 for improved consensus safety, and enforces a protocol-level transaction gas cap. Brief interruptions to RPC availability may occur on that date. RPC Changes: eth_sendTransaction / eth_sendRawTransaction — Transactions exceeding 100 Mgas will be rejected by the network (EIP-7825 with Fluent-specific limit); clients sending such transactions will receive rejection errors. Precompile execution (ecrecover, keccak256, sha256, ripemd160, bigModExp, bn256Add, bn256ScalarMul, bn256Pairing, blake2f, KZG, BLS12-381) — All Ethereum precompiles now execute via native revm implementations at the same addresses with identical gas costs and results, but with several times faster performance. https://github.com/fluentlabs-xyz/fluentbase/releases/tag/v1.5.1

Started 28 oct. 2026, 00:00 UTC · Ongoing

We are upgrading our Bitcoin Mainnet Ordinals infrastructure from ord 0.23.2 to 0.29.1. This release rolls up several versions of indexer improvements, including richer inscription metadata in API responses, new gallery and bulk lookup endpoints, a new recursive endpoint for raw block data, and a fix for indexing transactions that include pay-to-anchor outputs. During the maintenance window, brief interruptions to Ordinals API availability may occur. RPC Changes: - Inscription JSON responses — added. Inscription responses now include a properties object (attributes, traits, title, and gallery items) along with the metaprotocol field. - Inscription parents — fixed. Invalid parents are now filtered out and no longer returned for inscriptions. - /children routes — added. Child inscription routes now support JSON responses. - /gallery — added. New JSON endpoint for retrieving gallery inscriptions, with paginated gallery items. - /galleries and /collections — changed. /collections now returns results in reverse order, and hidden inscriptions are excluded from both /collections and /galleries. - /missing — added. New endpoint to check whether a batch of inscriptions exists in a single request. - /r/block/ — added. New recursive endpoint that returns the raw block hex for a given block hash or height. - Block inscriptions pagination — changed. Requests for an out-of-range page now return an empty page instead of an error. - Outpoint and TXID lookups — fixed. Outpoints and TXIDs made up entirely of decimal digits now resolve correctly instead of being misrouted. - Sat lookups — fixed. "Not found" sat index responses are no longer cached, so subsequent lookups return current data. - Rune amounts — fixed. Decimal amounts with excessive precision or values that would overflow now return a proper error. - Pay-to-anchor outputs — fixed. Transactions containing pay-to-anchor (P2A) outputs are now indexed correctly. Prior versions could return incorrect inscription and output data for these transactions. https://github.com/ordinals/ord/releases/tag/0.29.1

Started 28 oct. 2026, 00:00 UTC · Ongoing

We are upgrading our Sui Testnet infrastructure to v1.83.0 on 2026-10-28. This release advances the protocol to version 140 with consensus-breaking changes, including refined object funds withdrawal checks, transaction effects optimization, and substantial improvements to gRPC and error handling. Brief interruptions to RPC availability may occur on that date. RPC Changes: - SimulateTransaction — When gas selection cannot find enough SUI to cover the gas budget, the error now carries structured metadata (owner, requiredBudget, coinBalance, addressBalance) via a google.rpc.ErrorInfo with reason INSUFFICIENT_GAS_BALANCE (domain sui.io), allowing clients to read the required budget without message parsing. If budget estimation fails, the error reports the execution failure with reason TRANSACTION_EXECUTION_FAILED and includes ExecutionError details. - SubscribeTransactions, SubscribeCheckpoints — Now populates effects object types, clever errors, and event json when the read mask requests them, matching GetTransaction behavior. - ListTransactions, ListEvents — Requests below the node's retention now return OUT_OF_RANGE instead of INTERNAL. Cursors can be sent back in either ordering without skipping items. Descending requests with end_checkpoint above the latest indexed checkpoint + 1 now return OUT_OF_RANGE. On pruning fullnodes, all requests needing data below the pruning floor return OUT_OF_RANGE. Pages now correctly report hasNextPage/hasPreviousPage based on end reason rather than arbitrary boundaries. - ListCheckpoints — Requests with a starting cursor past the server's indexed tip now return OUT_OF_RANGE instead of an empty page. Pages now correctly report hasNextPage/hasPreviousPage based on end reason. Checkpoints with an after cursor at or below filter.afterCheckpoint, or a before cursor at or above filter.beforeCheckpoint, now returns the checkpoints within the bound instead of an empty page. - GetEpoch — Now lists mldsa65_auth among protocol feature flags. https://github.com/MystenLabs/sui/releases/tag/testnet-v1.83.0

Started 28 oct. 2026, 00:00 UTC · Ongoing

The scheduled maintenance has been completed.

Started 27 oct. 2026, 00:00 UTC · Resolved 28 oct. 2026, 00:01 UTC