Getting started
This page serves as a wallet index for wallets compatible with Polygon. You can browse through the many partner wallets that support Polygon chains, or choose to go with Polygon Portal, which is Polygon’s native asset management solution.
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 Portal is a comprehensive solution for account management on Polygon.
The Portal can be used to perform a variety of tasks, such as:
- Bridge your assets via Socket bridge and a range of third-party bridges
- Manage your assets and token lists
- Use the Refuel Gas feature to purchase MATIC or ETH for gas on the destination chain
- Leverage developer tools to help you build your dream dApp
- Swap assets easily with third-party DEXs
For more details on what features Polygon Portal offers, and guides on how to use it perform token operations such as bridging ETH, MATIC, and custom tokens between Polygon PoS and zkEVM, and Ethereum, refer to the guide below.
Info
If you come across any issues, Polygon support is just a click away! Feel free to get in touch with us for assistance.
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:
Info
Please note that this is not an exhaustive index.
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 | ||
WalletKit | non-custodial | EOA, smart contract | no | yes | yes | yes | no | browser, mobile, 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.js
to 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.