Skip to content
Alchemy Logo

Polygon PoS Erigon Client Deprecation Notice

Polygon Labs is sunsetting Erigon support on Polygon PoS on August 1, 2026. To align 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, it does not support Erigon-specific RPC namespaces. Beginning August 1, 2026, the following methods will no longer be available on Polygon Mainnet (polygon-mainnet) or Polygon Amoy (polygon-amoy):

  • The entire trace_* namespace — for example, trace_filter, trace_block, trace_replayBlockTransactions, trace_transaction, and trace_call.
  • The entire erigon_* namespace — for example, erigon_getHeaderByNumber.

Migrate to methods supported by Bor before August 1, 2026 to avoid disruption:

  1. Replace trace_* calls with the corresponding debug_trace* methods, such as debug_traceBlockByNumber, debug_traceTransaction, and debug_traceCall.
  2. For range-based trace_filter use cases, use eth_getLogs against indexed event logs.
  3. Replace erigon_* calls with standard Ethereum RPC equivalents. For example, replace erigon_getHeaderByNumber with eth_getBlockByNumber.

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 [email protected] or open a ticket in the Alchemy Dashboard.

Was this page helpful?