polygon

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

1|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/naruto11eth/cryptoskills --skill polygon-naruto11eth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polygon
Source: https://github.com/naruto11eth/cryptoskills/tree/main/skills/polygon
Command: npx skills add https://github.com/naruto11eth/cryptoskills --skill polygon-naruto11eth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires viem.

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, and Foundry/Hardhat deployment setups. - Bridging Workflows: Step-by-step PoS bridge deposits/withdrawals and zkEVM LxLy bridge asset transfers with claim proof retrieval via bridge APIs. - POL Token Operations: MATIC-to-POL migration, ValidatorShare staking, reward claiming, and restaking with viem code examples. - Use Case: Deploy a Solidity contract to Polygon zkEVM, bridge ETH from Ethereum mainnet via the LxLy bridge, and monitor the transaction until it reaches consolidated finality — all using the provided templates and verified contract addresses. ## Quick Start Ask the agent to deploy a contract to Polygon PoS using Foundry and verify it on Polygonscan with the provided RPC endpoints and configuration.

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 the zkEVM RPC at https://zkevm-rpc.com (chain ID 1101), or configure Hardhat with the zkevm network. Standard Solidity contracts deploy without modification since zkEVM is Type-2 EVM-equivalent.

How do I bridge tokens from Ethereum to Polygon PoS?▼

Approve the ERC20Predicate contract to spend your tokens, then call depositFor on the RootChainManager contract with ABI-encoded deposit data. Tokens arrive on Polygon PoS in approximately 7-8 minutes via state sync.

What is the difference between Polygon PoS and Polygon zkEVM?▼

Polygon PoS is a sidechain with its own validator set using POL as gas token (chain ID 137), while zkEVM is a Type-2 ZK rollup using ETH as gas (chain ID 1101) that inherits Ethereum security through ZK proofs. They have different RPCs, bridges, and finality models.

How do I migrate MATIC to POL tokens?▼

Call the migrate function on the migration contract at 0x29e7DF7b6c1264C3F63e2E7bB27143EeB8A05fe3 on Ethereum after approving it to spend your MATIC. The migration is 1:1, burning MATIC and minting POL.

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

How long does a Polygon PoS withdrawal to Ethereum take?▼

Withdrawals require burning tokens on Polygon PoS, waiting for checkpoint inclusion on Ethereum (approximately 30 minutes), then submitting an exit proof via RootChainManager. Checkpoint delays can extend this during congestion.