Legacy gasPrice vs EIP-1559 dynamic fees for Polygon PoS mainnet
0 reputation · 24 Mar 2022, 12:04 UTC
Fee strategy for Polygon PoS mainnet deployment
A signed transaction succeeds against a local Hardhat node but remains pending or is displaced when broadcast to Polygon PoS mainnet during base-fee volatility. The goal is to choose a fee configuration that transfers reliably from local development to mainnet without hardcoded values that become stale.
Polygon PoS follows EIP-1559 rules with a per-block base fee and an optional priority fee. Legacy gasPrice transactions remain accepted but may be priced as maxFeePerGas, and local nodes often use fixed or zero gas pricing that does not reflect mainnet conditions. Wallet and SDK implementations also differ on whether maxPriorityFeePerGas is populated through eth_feeHistory or static defaults.
Which approach fits this constraint: legacy gasPrice for broader tooling compatibility, or EIP-1559 maxFeePerGas and maxPriorityFeePerGas to track mainnet base-fee changes? When local eth_feeHistory results diverge from mainnet RPC responses, how should maxPriorityFeePerGas be derived?
polygon