Polygon smart contract audits
HYDN audits Solidity contracts on Polygon PoS. Alongside the standard review, Polygon audits check finality and reorganisation assumptions, bridging between Polygon and Ethereum, native token handling after the MATIC to POL migration, and the gas and block-time differences that affect timing logic.
Polygon-specific risks we check
- Finality. Off-chain components such as relayers, indexers and exchanges that credit deposits must wait for finality before acting.
- Bridging. Assets moving between Polygon and Ethereum pass through bridge contracts with their own delays and proofs. Your protocol should not treat a pending bridge transfer as settled.
- Native token. Logic that handles the native gas token or the staking token should be checked against the current POL token.
- Timing. Block times differ from mainnet, so durations measured in blocks need converting.
- Ecosystem integrations. Oracles, DEXs and lending markets on Polygon have their own liquidity and update characteristics.
The rest of the audit
The full HYDN audit process applies, with a private report, up to two rounds of fix review, and a final report and certification.
Frequently asked questions
Do we need to worry about reorgs on Polygon?
Any contract or off-chain service that acts on an event before it is final can be caught out if the chain reorganises. Check how many confirmations your system waits for and whether that matches current finality guarantees.
Does the move to POL affect our contracts?
It can, if your contracts or scripts hard-code the old MATIC token address or assume its behaviour. Check any integration that handles the native or staking token.
Published Updated