Polygon PoS is an EVM-compatible proof-of-stake network with its own validator set that periodically checkpoints its state to Ethereum. It is widely used for tokens, NFT collections and consumer applications that need low transaction costs. Building on it means reusing Ethereum skills and tools while accounting for a different consensus, bridge and finality model.
Building on Polygon
Contracts are written in Solidity or Vyper and compiled to EVM bytecode, so Ethereum libraries and frameworks apply directly. Assets move between Ethereum and Polygon through bridge contracts, and the native gas token is specific to the network. Polygon also develops other networks, including zero-knowledge based ones, so the brief should state precisely which network is targeted.
- Languages: Solidity, Vyper
- Frameworks: Foundry, Hardhat
- Standards: the usual ERC token standards, plus bridge-mapped versions of Ethereum tokens
What auditors look at
- Finality and reorganizations: logic that treats a recent block as final, especially in off-chain services that react to events
- Bridge assumptions: which tokens are bridged versions, who controls their minting, and how deposits and exits are validated
- Oracle choice and liquidity depth, since prices can be easier to move on thinner markets
- Gas and loop limits in contracts that iterate over user lists, frequent in NFT and reward distribution code
- Standard EVM risks: reentrancy, access control, upgradeable proxy configuration
Before requesting quotes
- Name the exact Polygon network and whether the same code runs on other EVM chains
- Describe any bridging, including tokens mapped from Ethereum and who holds the related roles
- Explain how your back end or indexer handles confirmations and reorganizations
- Share the commit hash, the files in scope and the existing test suite