Polygon setup is POL Gas Funding for First Wallet Transactions

POL Replaced MATIC in the Network Configuration

POL now names the native gas asset that Polygon PoS wallets reserve for every state-changing transaction. Wallet records that still label this balance MATIC need a metadata update, not a different account.

The network changed its native symbol on September 4, 2024, when POL superseded MATIC for Polygon PoS gas and staking. MATIC already held natively on Polygon PoS moved to POL without a holder transaction, while the migration relationship remained 1:1. That distinction matters during setup because an old wallet label can disagree with the chain while the underlying balance remains usable. Edit the currency symbol to POL or refresh the built-in network entry. No ERC-20 import is required for the native gas balance, and no MATIC-to-POL contract call belongs in the ordinary Polygon PoS wallet setup.

Wallet Presets, dApp Requests, and Manual RPC Entry

Wallet presets reduce typing in MetaMask and Rabby Wallet, while manual entry exposes the fields that determine network identity. A dApp request commonly uses EIP-3085 to propose Polygon PoS metadata; the wallet still shows an approval prompt before saving it. Manual Polygon setup offers the clearest diagnosis when a preset carries an old MATIC symbol or a retired endpoint. All three methods should resolve chain ID 137 from the RPC, and adding the network changes wallet metadata rather than moving tokens.

Chain Identity Must Match the RPC Response

Polygon PoS setup succeeds when the chain identifier, RPC response, and displayed native symbol describe the same network.

Mainnet uses chain ID 137, while the Amoy testnet uses 80002 and Ethereum mainnet uses 1. These identifiers let an EVM wallet separate signatures and balances even though one account keeps the same hexadecimal address across compatible chains. An externally owned account address contains 20 bytes, rendered as 40 hexadecimal characters after the 0x prefix, or 42 characters in total. The repeated address does not merge balances: POL on Polygon PoS and a token at the matching Ethereum address occupy different ledgers.

The RPC endpoint supplies chain state, estimates, balances, and broadcasts; it does not hold the account. A valid endpoint must return 0x89, the hexadecimal form of 137, when the wallet calls eth_chainId. Keep the network name human-readable, set POL as the native symbol, and use Polygonscan as a separate receipt viewer. A mismatch warning means the endpoint and saved record disagree, so the endpoint or chain field needs correction before funding.

How Much POL Does a First Transaction Need?

A first transaction needs its estimated gas multiplied by the effective gas price, plus the transferred amount when that value is POL.

A plain transfer between externally owned accounts has an intrinsic cost of 21,000 gas units. The intrinsic amount assumes empty calldata and no access list. Polygon PoS uses EIP-1559 Type 2 transactions, which carry two fee caps: maxFeePerGas and maxPriorityFeePerGas. Polygon PoS mainnet requires a minimum priority fee of 25 gwei. The base fee changes with block demand, so the wallet reads it near submission time. One gwei equals 10^9 wei, and one POL equals 10^18 wei because POL uses 18 decimal places. Multiply gas used by the effective gas price to obtain the final fee in wei.

The gas limit is a ceiling on computation, not a quoted charge. Unused gas remains uncharged, while the fee cap reserves enough balance for inclusion. Contract calls need an estimate from the exact calldata because an ERC-20 transfer performs more EVM work than a native POL transfer. Fund for the displayed maximum, then judge the expense from the receipt.

Funding Paths Put POL on the Destination Chain

POL funds gas only when the balance exists on Polygon PoS under the address that will sign the transaction.

A supported exchange withdrawal can deliver POL directly to Polygon PoS. The selected withdrawal network controls the destination ledger, so the network choice must say Polygon or Polygon PoS rather than Ethereum. The receiving address remains the same 42-character EVM address. The exchange determines its withdrawal minimum and service charge, which are live provider values rather than Polygon protocol constants.

On a first pass, Polygon Portal moves supported assets between Ethereum and Polygon PoS through the PoS bridge. A source transaction consumes ETH for gas on Ethereum, and the mapped destination asset arrives on Polygon PoS after the bridge process. The portal also includes a Refuel route for selected assets through 0x, which converts part of the transfer into destination gas. Availability depends on the chosen asset and route, so the confirmation screen must show POL arriving on Polygon PoS.

A direct transfer from another Polygon PoS account is the shortest funding path. The sender pays that transaction fee, and the receiving wallet does not sign merely to receive native POL. MoonPay, Transak, and Ramp provide purchase or transfer routes in supported regions, but their asset and network labels must point to Polygon PoS before confirmation.

An existing USDC, USDT, or WETH balance cannot pay an ordinary EVM fee by itself. Swapping one of those ERC-20 tokens also requires a contract transaction, creating a circular problem when the POL balance is zero. A sponsored application built with a paymaster or Sequence Gas Tank can cover a specified action, but sponsorship belongs to that application rather than the wallet account globally. Choose the route by locating the source asset first, then confirm that its destination is chain 137.

The First Send Must Leave a Gas Reserve

A first POL send must leave enough native balance for its own fee rather than assigning the full balance as value.

Wallets calculate a sendable maximum by subtracting a fee reserve from the POL balance. If the transfer value plus gas ceiling exceeds the balance, the node rejects it before execution. A native transfer between externally owned accounts sends POL in the value field and has 21,000 intrinsic gas with no calldata or access list. An ERC-20 transfer instead sends zero native value to a token contract, yet the signer still pays POL for the contract execution.

The account nonce orders outgoing transactions and increases by 1 after each included transaction. Two pending transactions cannot execute independently with the same nonce; the later one replaces or conflicts with the earlier submission. Let the wallet read the pending nonce from chain 137, review the destination and fee ceiling, and keep a small POL remainder for the next state change.

Token Display Follows Contract Identity

Token display depends on the Polygon PoS contract address and decimal precision, while native POL appears without an ERC-20 import. Native USDC uses 6 decimal places, as does USDT on Polygon PoS, whereas WETH uses 18. A wallet may hide any of these balances until their Polygon contract records are imported. Adding a token changes the interface only; it does not create a balance. Match the contract to chain 137 before interpreting a zero balance or preparing the first token transfer. Further detail lives in Polygon guide.

Receipts Separate Inclusion, Finality, and Balance Changes

A Polygon PoS receipt proves execution status, gas consumption, block inclusion, and the address that received the state change.

The transaction hash contains 32 bytes and appears as 64 hexadecimal characters after a 0x prefix, producing 66 visible characters. Polygonscan and wallet activity views use that hash to locate one submission. Receipt status 1 records successful execution, while status 0 records a reverted execution whose gas was still consumed. Compare gasUsed with effectiveGasPrice to reconstruct the charged POL fee, then compare the sender and recipient addresses rather than relying on a token label alone.

Heimdall v2 milestones give Polygon PoS deterministic finality in 2 to 5 seconds once at least two-thirds of validating stake agrees on the Bor block sequence. Checkpoints serve a different bridge function by committing a Merkle root to Ethereum at intervals of about 256 Bor blocks. A first wallet transfer that remains on Polygon PoS relies on milestone finality; an exit to Ethereum waits for checkpoint inclusion. Decide whether the receipt proves a local transfer or starts a bridge workflow.

Edge Cases in Nonces, RPCs, and Smart Wallets

Most advanced Polygon setup failures come from stale RPC state, a blocked nonce sequence, or a smart-account flow that uses sponsored execution.

Changing from dRPC to Alchemy or another Polygon-capable provider changes the route to chain data, not the address or POL balance. Querying a second provider distinguishes an interface delay from an unincluded transaction. A replacement reuses the pending nonce with a valid higher fee, while a new transaction takes the next nonce. The chain ID inside the signature must remain 137 throughout.

Safe and other smart accounts execute contract logic rather than sending a plain externally owned account transfer. An EIP-4337 flow packages the action as a UserOperation for a bundler, and a paymaster may sponsor its gas under application rules. Sequence exposes this model through managed gas sponsorship. Identify whether the signer is an externally owned account or a smart account before choosing a POL top-up, nonce action, or sponsored route.