technology
Quicknode changes pending transaction tracking on Hedera
The provider marked its November 16 maintenance as complete. Its JSON-RPC relay 0.81.0 adds a pending transaction subscription and changes how receipt requests respond to transactions rejected before consensus.

Applications can subscribe to pending transactions
Quicknode marked its November 16 maintenance of Hedera mainnet infrastructure as complete. The provider had announced version 0.166.1 of its mirror node and version 0.81.0 of its JSON-RPC relay. The mirror node supplies data from the network, while the relay lets tools designed for the Ethereum ecosystem query or use Hedera. The announced maintenance concerns services Quicknode operates. It describes the deployment of these versions at that provider. Hashgraph’s status page separately shows that its own mainnet Hashio service uses the same relay version, 0.81.0. It tracks that service separately from Quicknode’s.
The relay adds the newPendingTransactions WebSocket subscription. An application that monitors transactions can ask to receive events as transactions become pending on the service. That information precedes the final transaction outcome. A wallet or dashboard still needs to retrieve the final status when displaying a confirmation or matching an operation with its receipt.
An error code distinguishes rejection before consensus
The eth_getTransactionReceipt method changes its response for transactions rejected before consensus. The relay can now return JSON-RPC error -32003 where the response could previously be null. Clients that use a null value to decide whether to keep checking need to handle the error code. An application that looks only for the absence of a receipt may treat the same situation differently depending on which relay version it queries.
According to Quicknode, the upgrade also fixes a race in eth_getTransactionCount. It could affect the value returned if the method was called immediately after submitting a transaction or at the same time as other requests. That value is used, among other things, to determine a transaction’s sequence number for an account. The provider also says aborted submissions now return HTTP 499 instead of 500.
Traces narrow the response to storage that was touched
The relay notes say prestateTracer, when used by debug_traceTransaction, now queries the mirror node endpoint for state before execution. The trace therefore returns storage slots the transaction actually touched. Diagnostic tools that expected more data about the contract need to account for that difference when using the response.
The mirror node also changes its REST responses. Quicknode announced a new field identifying whether a contract result corresponds to a transaction linked to a parent transaction. The provider also reported more accurate gas estimates for contract calls. These changes affect the interfaces applications use to observe activity or prepare calls. Their effects depend on the methods queried and on how the responses are handled.
