# Polygon

> LOPW on Polygon through the EVM binding: chain ids and CAIP-2 ids for Polygon Amoy and Polygon PoS, native USDC addresses, explorers, the Chainlink oracle note, and the LOPW contract addresses or the deployment status for each network.

*LOPW documentation · Networks.* Canonical page: https://lopw.com/docs/networks/polygon.html · This Markdown twin: https://lopw.com/docs/networks/polygon.md · Index of all pages: https://lopw.com/llms.txt · Everything in one file: https://lopw.com/llms-full.txt

Polygon runs LOPW through the shared [EVM binding](https://lopw.com/docs/networks/evm.html): Solidity contracts, EIP-712 typed data signed with secp256k1, native USDC with 6 decimals, Chainlink feeds for P6 and x402 `exact` with EIP-3009. Polygon PoS and the Amoy test network: native USDC (not the bridged USDC.e) is the stake and payment token.

**EVM binding**

## At a glance

| Item | Polygon Amoy | Polygon PoS |
| --- | --- | --- |
| Network name (API paths) | `polygon-amoy` | `polygon` |
| CAIP-2 | `eip155:80002` | `eip155:137` |
| Chain id | 80002 | 137 |
| USDC (native, 6 decimals) | [0x41E94Eb019C0762f9Bfcf9Fb1E58725BfB0e7582](https://amoy.polygonscan.com/address/0x41E94Eb019C0762f9Bfcf9Fb1E58725BfB0e7582) | [0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359](https://polygonscan.com/address/0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359) |
| Explorer | [amoy.polygonscan.com](https://amoy.polygonscan.com) | [polygonscan.com](https://polygonscan.com) |
| P6 oracle | Chainlink feed, verified on-chain at deployment | Chainlink feed, verified on-chain at deployment |
| LOPW deployment | None published | None published |

## LOPW contracts

### Polygon Amoy

Not deployed No LOPW deployment is published on this network yet.

### Polygon PoS

Not deployed No LOPW deployment is published on this network yet.

## Oracle note

P6 terms on Polygon name a Chainlink `AggregatorV3Interface` feed and its pair label as `bytes32`. The seller cites the `roundId` it used; the validator reads `getRoundData(roundId)` on-chain, applies `max_oracle_age` to the round’s `updatedAt`, and proves a breach with the exact integer deviation test. Every feed address is verified on-chain (`description()`, `decimals()`) before use and recorded in `deployments/.json`.

## What is identical to every other EVM network

- The Solidity contracts, their functions, errors and events.
- The EIP-712 type strings and the domain `LOPW` / `1`; only `chainId` and `verifyingContract` change.
- The wire form: 0x-hex ABI encoding of `SignedOffer` and `SignedReceipt`.
- USDC with 6 decimals as stake and payment token; x402 `exact` with EIP-3009.
- Indexing after `EVM_CONFIRMATIONS` confirmations, writing the same `events`, `services` and `claims` rows with `network` set to the names above.

## For agents

> **For agents**
>
> | Item | Value |
> | --- | --- |
> | Network name in API paths | `polygon-amoy` (Polygon Amoy), `polygon` (Polygon PoS); served once a LOPW deployment is published for the network |
> | CAIP-2 id | `eip155:80002`, `eip155:137` |
> | Wire encoding of `extensions.lopw` | 0x-hex ABI encoding of `SignedOffer` (`info.offer`) and `SignedReceipt` (`receipt`); schemas [offer-evm.json](https://lopw.com/docs/schemas/offer-evm.json) and [receipt-evm.json](https://lopw.com/docs/schemas/receipt-evm.json) |
> | Explorer | `https://amoy.polygonscan.com/tx/{hash}`, `https://amoy.polygonscan.com/address/{address}` |
> | USDC | `0x41E94Eb019C0762f9Bfcf9Fb1E58725BfB0e7582` (Polygon Amoy), `0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359` (Polygon PoS) |

- [EVM binding](https://lopw.com/docs/networks/evm.html): Types, EIP-712 hashing, contracts, P6 with Chainlink, x402 with EIP-3009, SDK.
- [All networks](https://lopw.com/docs/networks/): Stellar as the reference binding, the EVM networks, and the planned Solana binding.