Polygon Erigon EOL: Migration Guide to Bor Nodes & RPC Changes

Polygon Labs has announced that support for the 0xpolygon/erigon node implementation on the Polygon PoS network (Mainnet and Amoy) will be sunset on August 1, 2026.

In alignment with Polygon Labs’ recommendations, Tatum is migrating all archive-node infrastructure to Bor with PBSS (Path-Based State Scheme) configuration.

📘
Note
Polygon Labs: Bor - GitHub Pull Request

Key Changes & Impact

While Bor provides the same historical ledger data, there are significant differences in supported RPC namespaces between Erigon and Bor.

🚫 Deprecated Methods

The following Parity-style trace_* methods are exclusive to Erigon and will not be available on the new Bor infrastructure:

trace_block
trace_call
trace_callMany
trace_replayBlockTransactions
trace_replayTransaction
trace_filter

✅ Available Alternatives

Bor supports the standard Geth debug_trace* namespace. For most tracing use cases, you should transition to:

debug_traceTransaction
debug_traceBlockByNumber
debug_traceBlockByHash
debug_traceCall

🚧
Additional Compatibility Notes
Bor follows Geth-compatible behavior for debug and txpool namespaces. Customers relying on exact Erigon response schemas should validate their integrations before migration.

For debug_trace* methods, the memory field is not returned by default. To include EVM memory in trace output, pass enableMemory: true in the trace configuration.

For txpool_* methods, response schemas may differ from Erigon. For example, Bor may omit fields such as baseFee in txpool responses.

Historical eth_getProof Support: Bor currently serves eth_getProof requests only for the latest 128 blocks. Requests for older historical proofs are not currently supported by the Bor client.

Migration Timeline

Polygon Amoy (Testnet): Migration is scheduled for May 11, 2026.
Polygon Mainnet: Migration will follow the Amoy deployment (to be announced).
End of Life: All legacy Erigon nodes will be fully decommissioned by August 1, 2026.

Connection Endpoints

No endpoint URL changes are required. Your existing Polygon Mainnet and Polygon Amoy Gateway URLs will remain the same, but the underlying infrastructure will be migrated to Bor-based nodes.

Important Notice

If your application relies on the trace_ namespace (specifically for range queries via trace_filter), you must refactor your logic to use indexed logs (eth_getLogs) or the debug namespace before the deadline to avoid service interruption.