Polygon Labs is sunsetting Erigon support on Polygon PoS on August 1, 2026. In line with that change, Alchemy is migrating our Polygon Mainnet and Amoy infrastructure from Erigon to Bor, the recommended Polygon client, on the same date.
Because Bor is a Geth-based client, several Erigon-specific RPC methods will no longer be available after the migration. Beginning August 1, 2026, the following methods will no longer be supported on Polygon Mainnet (polygon-mainnet) or Polygon Amoy (polygon-amoy):
- The entire
erigon_*namespace, for exampleerigon_getHeaderByNumber. trace_filtertrace_gettrace_rawTransaction
The remaining trace_* methods (trace_block, trace_transaction, trace_call, trace_callMany, trace_replayTransaction, and trace_replayBlockTransactions) will continue to be available after August 1, 2026, but will be served by Bor instead of Erigon.
Migrate the affected methods before August 1, 2026 to avoid disruption:
erigon_*methods. Replaceerigon_*calls with standard Ethereum RPC equivalents. For example, replaceerigon_getHeaderByNumberwitheth_getBlockByNumber.trace_filter. There is no direct server-side equivalent in Bor. Calldebug_traceBlockByNumberwithcallTracerfor each block in the desired range and performfrom/tofiltering client-side.trace_get.trace_getreturns a single subtrace of a transaction by its trace-address path. Calldebug_traceTransactionwithcallTracerand index into the returned call tree client-side.trace_rawTransaction. Usedebug_traceCall. Becausedebug_traceCallacceptsTransactionArgsrather than signed RLP bytes, the client must decode the raw transaction, recover the sender, and rebuild the call arguments.
Bor currently supports eth_getProof only for the latest 128 blocks. Requests for proofs from older historical blocks are not currently supported by the Bor client.
If you have any questions or need assistance migrating, contact us at support@alchemy.com or open a ticket in the Alchemy Dashboard.