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.

📘
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.

Known limitations vs Polygon Erigon

trace_call/trace_callMany still require the simulated sender to pass Bor's upfront gas balance check; once funded, gas debit/refund is suppressed.
trace_block omits the state-sync pseudo-transaction for pre-Madhugiri blocks (< 80,084,800 on mainnet); post-Madhugiri blocks are fully supported.
vmTrace for a post-Madhugiri state-sync transaction reports an empty ops list (state-sync events execute outside the regular EVM opcode flow).

Tatum contributed native Parity trace_* RPCs to Polygon Bor. A technical walkthrough of the engine, 96% Erigon parity, and how operators can enable it today. You can check more about it in the following blog:

https://tatum.io/blog/parity-trace-apis-polygon-bor

🚧
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.