Polygon PoS bridge and MATIC-to-POL migration, decoded locally
rotki decodes Polygon PoS bridge deposits and withdrawals between Ethereum and Polygon, and the MATIC-to-POL token migration. Source and destination legs are linked so bridged assets are not double-counted. For Polygon PoS chain balances see the [Polygon PoS](/integrations/polygon-pos) integration. You choose which RPC endpoint handles the queries.
Supported features
- Polygon PoS bridge deposits and withdrawals decoded as protocol events, including the Exit NFT used to complete a withdrawal.
- Source-chain (Ethereum) and destination-chain (Polygon) legs linked to avoid double-counting.
- MATIC-to-POL token migration decoded.
Setup
- 1In rotki, add your address on both Ethereum and Polygon PoS.
- 2Open History and let the initial sync run. Bridge and migration events are decoded automatically.
Frequently asked questions
How is this different from the Polygon PoS integration?
The Polygon PoS integration tracks balances and activity on the Polygon chain itself. This page covers the Ethereum-side Polygon mechanisms: the PoS bridge transfers and the MATIC-to-POL migration.
Which RPC does rotki use for these events?
rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server.