Account identity
Aperture derives and validates the public account under Polygon PoS rules. It does not assign a generic address from another network family.
Supported production mainnet
Polygon PoS in Aperture.
A network-aware home for POL—with Polygon PoS addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
Polygon PoS is not just a ticker.
Polygon PoS is an EVM-compatible proof-of-stake network with its own validators, blocks, and account state, plus checkpointing relationships with Ethereum.
Address format. A 20-byte EVM account displayed as a 0x-prefixed hexadecimal address.
Polygon PoS uses Ethereum-style addresses, but a Polygon balance is not an Ethereum-mainnet balance. Check the network at both ends.
Native asset and tokens
POL pays gas in Aperture’s Polygon PoS catalog. Tokens are identified by their Polygon contract addresses.
Fees and transaction state
The network’s native asset pays gas. A transaction hash, receipt, block inclusion, and any rollup settlement stage describe different parts of its lifecycle.
Mainnet boundary
This catalog entry is Polygon PoS mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.
Receive safely
The network is part of the address.
In Aperture, choose Polygon PoS and the exact asset before copying an address or QR code. The sender, exchange, or bridge must use the same mainnet. A matching symbol, logo, or familiar-looking string does not prove compatibility.
- Confirm the receive screen says Polygon PoS.
- Copy or scan the complete address; do not retype it.
- Check whether the sending service requires an additional memo, tag, or network-specific field.
- For a new route or meaningful amount, consider a small test transfer first.
- Keep the receive screen available until the sender has verified the same network.
Send deliberately
Review what the signature will authorize.
Aperture keeps asset selection, recipient validation, amount, fee review, authorization, broadcast, and finality as distinct stages. Before authorizing a transaction on Polygon PoS, review the full recipient, the POL amount, and the network fee together.
Blockchain transfers may be irreversible. Aperture cannot cancel a confirmed transaction, recover an incorrect destination, or move an asset that was sent through the wrong network.
Transaction signing happens on the device. Public account data, fee requests, transaction history, and the signed transaction may reach network infrastructure; the private signing key is not part of the broadcast payload.
Verify independently
Use the right source for the right question.
Network documentationUnderstand Polygon PoS protocol rules
Public block explorerInspect Polygon PoS public chain state
Aperture JournalHow accounts and networks stay separate
Aperture JournalReceive crypto safely in Aperture
External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.
Aperture for iPhone and iPad
One interface. 25 mainnets. No blurred boundaries.
Use Polygon PoS alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.