Getting started
This section serves as a wallet index for wallets compatible with Polygon.
Please note that this is not an exhaustive index.
Wallets that support Polygon allow for key management, access to accounts controlled by private keys, and interfaces that allow users to perform chain actions and sign transactions.
Centralized Exchanges (CEXs)
For a list of CEXs that support Polygon, visit a third-party tracking website such as CoinMarketCap.
Native wallets¶
The Polygon Wallet Suite is a comprehensive solution for account management on Polygon.
It includes:
- A portfolio view to check balances on Polygon chains.
- A bridge for transferring assets between Polygon PoS and Ethereum.
- A swap feature for swapping between tokens.
- A token mapper for mapping tokens between Polygon and Ethereum.
- A faucet for obtaining free test tokens.
- A safe bridge for securely bridging between Polygon and Ethereum.
- A bridge explorer for checking bridging transactions.
- Staking options to secure the Polygon PoS by staking MATIC tokens.
- A bridge for transferring assets between Polygon zkEVM and Ethereum.
- A zkEVM explorer for block explorer and analytics.
- Access to ecosystem dApps.
Polygon support can also provide assistance to users and address issues related to the wallet suite.
| Interfaces | Custody | Account Type | Multi-Sig | dApp Browser | Platform |
|---|---|---|---|---|---|
| Polygon Wallet Suite | non-custodial | EOA | yes (Safe Bridge) | yes | browser |
| Hermez Wallet | non-custodial | EOA | no | no | browser |
Tip
Keep up with the latest Wallet Suite updates from the Polygon team and community by subscribing to our notifications.
Partner wallets¶
Third-party wallets
These third-party wallets have integrated Polygon and support a variety of features. You should do your own due diligence before using them. The official Polygon Support cannot provide assistance for issues with these wallets or other non-native wallets.
Content disclaimer
Please view the third-party content disclaimer here.
The following wallets are solutions that Polygon Technology has partnered with:
| Wallet | Custody | Account Type | Multi-Sig | NFT | dApp Browser | Bridge Support | Fiat On-Ramp | Platforms |
|---|---|---|---|---|---|---|---|---|
| 1inch | non-custodial | EOA | no | interface | yes | yes | yes | mobile |
| Alpha Wallet | non-custodial | EOA | no | interface | yes | yes | yes | mobile, api/sdk |
| Atomic Wallet* | non-custodial | EOA | no | no | no | no | yes | mobile, desktop, api/sdk |
| Ambire | non-custodial | smart contract | no | interface | no | yes | yes | browser |
| BitKeep | non-custodial | EOA | no | interface | yes | yes | yes | mobile, browser extension |
| Bitski | custodial | EOA | no | interface | no | yes | no | browser, api/sdk |
| Coin Wallet | non-custodial | EOA | no | no | no | no | yes | mobile, browser, desktop |
| Coin98 | non-custodial | EOA | no | interface | yes | yes | yes | mobile, browser, api/sdk |
| Coinbase | hybrid | EOA | no | interface | yes | yes | yes | mobile, browser, api/sdk |
| CypherD | non-custodial | EOA | no | yes | yes | yes | yes | mobile |
| D’Cent | hybrid | EOA | no | interface | yes | yes | no | mobile |
| Exodus | non-custodial | EOA | no | yes | no | no | yes | mobile, desktop |
| Gnosis Safe | non-custodial | smart contract | yes | interface | no | no | no | mobile, browser, desktop, api/sdk |
| Guarda | non-custodial | EOA | no | no | no | yes | yes | mobile, browser, desktop |
| Huobi | non-custodial | EOA | no | yes | yes | yes | no | mobile |
| Ledger | non-custodial | EOA | no | interface | no | no | yes | hardware, mobile, desktop |
| Loopring | non-custodial | smart contract | no | no | no | no | no | mobile, api/sdk |
| Magic* | custodial | EOA | no | no | no | mobile, browser, api/sdk | ||
| MathWallet | custodial | EOA | no | no | no | yes | yes | mobile, browser, api/sdk |
| MetaMask* | non-custodial | EOA | no | interface | yes | no | no | mobile, browser, api/sdk |
| Multis* | non-custodial | EOA | no | no | no | yes | mobile, desktop | |
| MyEtherWallet* | non-custodial | EOA | no | interface | no | yes | mobile | |
| Omni | non-custodial | EOA | no | interface | no | yes | mobile, api/sdk | |
| Opera Crypto Browser* | non-custodial | EOA | no | support | yes | mobile, browser | ||
| Paraswap Multichain Wallet* | non-custodial | EOA | no | support | yes | Apple iOS | ||
| Pillar | non-custodial | EOA | no | interface | no | yes | mobile | |
| Rainbow | non-custodial | EOA | no | interface | yes | no | mobile, api/sdk | |
| SafePal | non-custodial | EOA | no | no | yes | yes | hardware, mobile, api/sdk | |
| Sequence | non-custodial | smart contract | no | interface | no | browser, api/sdk | ||
| SimpleHold | non-custodial | EOA | yes | no | no | yes | mobile, api/sdk | |
| TokenPocket | non-custodial | EOA | no | support | yes | yes | yes | mobile, browser, api/sdk |
| Torus | non-custodial | EOA | yes | support | no | no | no | browser, api/sdk |
| Trezor | non-custodial | EOA | no | support | no | hardware, mobile | ||
| Trust Wallet | non-custodial | EOA | no | support | yes | yes | mobile | |
| Unstoppable | non-custodial | EOA | no | yes | yes | no | mobile, api/sdk | |
| Venly | hybrid | smart contract | no | interface | no | browser, api/sdk | ||
| Wirex* | non-custodial | EOA | yes | no | no | mobile | ||
| XDeFi | non-custodial | EOA | no | interface | no | no | no | browser |
| Zerion | non-custodial | EOA | no | yes | yes | yes | mobile, browser | |
| Particle Network | non-custodial | hybrid | no | yes | yes | yes | yes | mobile, browser, api/sdk |
Non-native wallet support
Wallets denoted with * in the table above are not natively supported with the wallet software and require manual steps to add the Polygon network.
Key management strategy¶
The following basic steps allow for the integration of a client-side application with Polygon:
- Set up Web3: web3.js is a javascript library that
allows a client-side application to talk to the blockchain. We configure web3.js to communicate
via a developer-based wallet like MetaMask. Use the web3.js docs to learn about adding
web3.jsto your project. - Set up an account: You will be able to send transactions (specifically those that alter the state of the blockchain).
- Instantiate contracts: Once a web3 object is in place, we next instantiate our deployed contract, with which we interact.
- Call functions: Fetch data via functions in the contract through our contract object.