polygon

Deploy contracts, bridge tokens, and stake POL across Polygon PoS and zkEVM chains.

6|20|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/andresdefi/cryptoskills --skill polygon-andresdefi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polygon
Source: https://github.com/andresdefi/cryptoskills/tree/main/skills/polygon
Command: npx skills add https://github.com/andresdefi/cryptoskills --skill polygon-andresdefi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often have stale or incorrect knowledge about the Polygon ecosystem — confusing PoS with zkEVM, using deprecated MATIC references instead of POL, or hallucinating contract addresses. This Skill provides verified chain configurations, contract addresses, bridge workflows, and zkEVM-specific patterns so agents can build on Polygon without costly mistakes. ## Core Features & Use Cases - Dual-Chain Development: Complete configuration for Polygon PoS (chain ID 137) and zkEVM (chain ID 1101), including RPC endpoints, explorers, testnets (Amoy, Cardona), and Foundry/Hardhat deployment setups. - Bridging Workflows: Step-by-step PoS bridge deposits/withdrawals via RootChainManager and zkEVM LxLy bridge asset transfers with Merkle proof claiming, plus bridge monitoring via official APIs. - POL Token Operations: MATIC-to-POL migration, ValidatorShare staking delegation, reward claiming, and restaking with verified contract addresses. - Use Case: Deploy a Solidity contract to both Polygon PoS and zkEVM, bridge USDC from Ethereum to zkEVM, and monitor the claim status — all using the provided viem templates and verified addresses. ## Quick Start Ask the agent to deploy a contract to Polygon PoS and zkEVM using the provided Foundry commands and viem client template.

Frequently Asked Questions about polygon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a smart contract to Polygon zkEVM?

Use Foundry with forge create pointing to https://zkevm-rpc.com and chain ID 1101, or configure Hardhat with the zkEVM network. Standard Solidity contracts deploy without modification since zkEVM is a Type-2 ZK-EVM, and verification works through the zkEVM Polygonscan API.

How do I bridge tokens from Ethereum to Polygon?

For Polygon PoS, approve the ERC20Predicate and call depositFor on RootChainManager; tokens arrive in about 7-8 minutes. For zkEVM, call bridgeAsset on the LxLy bridge contract, then claim on the destination chain with a Merkle proof from the bridge API after proof generation.

What is the difference between Polygon PoS and Polygon zkEVM?

Polygon PoS is a sidechain with its own validator set using POL as gas, while zkEVM is a Type-2 ZK rollup using ETH as gas with Ethereum-secured finality. They have different chain IDs (137 vs 1101), different bridge contracts, and different finality mechanisms.

How do I migrate MATIC to POL tokens?

Call the migrate function on the migration contract at 0x29e7DF7b6c1264C3F63e2E7bB27143EeB8A05fe3 on Ethereum after approving your MATIC spend. The migration is 1:1, and POL at 0x455e53CBB86018Ac2B8092FdCd39d8444aFFC3F6 becomes your new token.

Why does my contract work on Ethereum but revert on Polygon zkEVM?

Common causes include using block.prevrandao which returns 0 on zkEVM, relying on SELFDESTRUCT which is disabled, or hitting higher gas costs on the modexp precompile. Replace randomness with Chainlink VRF and refactor self-destruct logic to withdrawal patterns.

How long does a Polygon PoS withdrawal to Ethereum take?

Withdrawals require burning tokens on Polygon PoS, waiting for a checkpoint submission to Ethereum (about 30 minutes), then calling exit on RootChainManager with a proof from the proof generator API. Checkpoint delays can extend this during congestion.