Leaving Base L2 for Polygon L1
Base inclusion and its ethereum settlement are distinct from final receipt on Polygon. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
Bridge Base to Polygon
FromBase
ToPolygon
ENTER AMOUNTUSDC / BASE -> USDC / POLYGON
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.Direction
Base → Polygon
Asset
USDC
Source gas
ETH
Destination gas
POL
How the Sasquatch deposit route works
1. Select the source
Choose the USDC asset and Base network you currently hold.
2. Review the route
Check the estimated output, fees, timing, and Polygon destination network.
3. Create the order
Open the live route and follow the exact deposit instructions.
4. Track delivery
Use the receipt and status page until the destination funds arrive.
What you need to know
Base deposit-side execution
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Base. EVM 0x account address A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger.
Select a Polygon-compatible output
EVM 0x account address POL is the native gas asset for Polygon. The quote identifies whether the delivered asset is native, contract-based, or bridged.
Polygon receipt-side execution
Polygon is a L1 EVM network in the Polygon ecosystem. POL pays destination-side network gas on Polygon. EVM 0x account address A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.
Base to Polygon bridge mistakes
Route-specific mistakes include sending on a network other than Base; using a destination that is not valid for Polygon; running out of ETH before the source transaction is submitted. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas.
Private Route for USDC → USDC
Base wallet, token-transfer, contract, log, and gas activity remain public, and Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Base to USDC on Polygon path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.
- ✓Reduces the obvious link between the USDC deposit and USDC receipt
- ✓Compare standard and Private Route options for Base → Polygon
- ✓Shows what remains public on Base and Polygon before you deposit
Related routes
Private Base to Polygon route explainerPrivacy limits and live availabilityNo-KYC and verification rulesProvider and region requirementsCan a bridge link source and destination wallets?FAQ answerWhat is cross-chain privacy?FAQ answerWhat is a private crypto swap?FAQ answerCan bridge transactions be traced?Privacy researchPrivate bridge security checklistPrivacy researchHow cross-chain transactions are trackedPrivacy research
Base to Polygon FAQs
Which asset can travel from Base to Polygon?
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Polygon output before depositing.
Which gas balances matter for this bridge?
A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. The bridge output does not automatically fund every later gas need.
What destination address should be used?
EVM 0x account address Do not substitute a Base address merely because a wallet displays both networks.
What wrong-direction mistake can prevent delivery?
Sending on a network other than Base, selecting a representation not listed by the quote, or entering an address invalid for Polygon can prevent normal detection or receipt.
Can I bridge USDC from Base to Polygon without KYC?
Requirements are checked for the live USDC Base to Polygon quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.