Skip to main content

Wallets

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. The following page serves as a wallet index for wallets compatible with Polygon. Please note that this is not an exhaustive index.

Third-party wallets

These third-party wallets have integrated Polygon and support a variety of features. You should use your own due diligence in researching and using them. The official Polygon Support cannot provide support for issues with these wallets or other non-native wallets.

Centralized Exchanges (CEXs)

For a list of CEXs that support Polygon, visit a third-party tracking website such as CoinMarketCap.

Stay in the know

Keep up with the latest wallet suite updates from the Polygon team and the community by subscribing to the Polygon notification groups.

Native Wallets

Polygon Support can provide assistance to users and address issues related to the following wallets:

WalletCustodyAccount TypeMulti-SigdApp BrowserPlatform
PoS Walletnon-custodialEOAnonobrowser
Hermez Walletnon-custodialEOAnonobrowser
Avail Apps (testnet)non-custodialEOAyesnobrowser

Partner Wallets

The following wallets are solutions that Polygon Technology has partnered with:

WalletCustodyAccount TypeMulti-SigNFTdApp BrowserBridge SupportFiat On-RampPlatforms
1inchnon-custodialEOAnointerfaceyesyesnomobile
Alpha Wallet*non-custodialEOAnointerfaceyesyesyesmobile, api/sdk
Atomic Wallet*non-custodialEOAnonononoyesmobile, desktop, api/sdk
Ambirenon-custodialsmart contractnointerfacenoyesyesbrowser
BitKeepnon-custodialEOAnointerfacenoyesyesmobile
BitskicustodialEOAnointerfaceyesnobrowser, api/sdk
Coin98non-custodialEOAnointerfaceyesyesyesmobile, browser, api/sdk
CoinbasehybridEOAnointerfaceyesyesyesmobile, browser, api/sdk
CypherDnon-custodialEOAnonoyesmobile
D'Cent*hybridEOAnointerfaceyesyesnomobile
Exodus*non-custodialEOAnononoyesmobile, desktop
Gnosis Safe*non-custodialsmart contractyesinterfaceyesnonomobile, browser, api/sdk
Guardanon-custodialEOAnononoyesyesmobile, browser, desktop
Huobinon-custodialEOAnononoyesnomobile
Ledger*non-custodialEOAnointerfacenononohardware, mobile, desktop
Loopringnon-custodialsmart contractnononomobile, api/sdk
Magic*custodialEOAnononomobile, browser, api/sdk
MathWallet*custodialEOAnononoyesyesmobile, browser, api/sdk
MetaMask*non-custodialEOAnointerfaceyesnonomobile, browser, api/sdk
Multis*non-custodialEOAnononomobile, desktop
MyEtherWallet*non-custodialEOAnointerfacenomobile
Opera Crypto Browser*non-custodialEOAnosupportyesmobile, browser
Pillarnon-custodialEOAnointerfacenomobile
Rainbownon-custodialEOAnointerfaceyesmobile, api/sdk
SafePal*non-custodialEOAnonoyeshardware, mobile, api/sdk
Sequencenon-custodialsmart contractnointerfacenobrowser, api/sdk
SimpleHoldnon-custodialEOAnononomobile, api/sdk
SteakWalletnon-custodialEOAnointerfacenomobile, api/sdk
TokenPocketnon-custodialEOAnosupportyesyesnomobile, browser, api/sdk
Torusnon-custodialEOAnosupportnononobrowser, api/sdk
Trezor*non-custodialEOAnosupportnohardware, mobile
Trust Wallet*non-custodialEOAnosupportyesmobile
Unstoppablenon-custodialEOAnonoyesmobile, api/sdk
Venlyhybridsmart contractnointerfacenobrowser, api/sdk
Wirex*non-custodialEOAnononomobile
XDeFinon-custodialEOAnointerfacenononobrowser
Zerionnon-custodialEOAnonoyesmobile, browser
*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 a client-side application with Polygon:

  1. Set up Web3: web3.js is a javascript library that allows a client-side application to talk to the blockchain. We configure web3 to communicate via a developer-based wallet like MetaMask. Use the web3.js docs to learn about adding web3.js to your project.
  2. Set up an Account: You will be able to send transactions (specifically ones that alter the state of the blockchain).
  3. Instantiate Contracts: Once a web3 object in place, we next instantiate our deployed contract, with which we interact.
  4. Call functions: Fetch data via functions in the contract - through our contract object.