Skip to content

Get Started

Tip

STAY IN THE KNOW

Keep up with the latest Wallet Suite updates from the Dojima team and community by subscribing to our Notifications.

Wallets that support Dojima 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 Dojima. Please note that this is not an exhaustive index.

Warning

THIRD-PARTY WALLETS

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

Info

CENTRALIZED EXCHANGES (CEXS)

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

Native Wallets

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

Wallet Custody Account Type Multi-Sig NFT dApp Browser Bridge Support Fiat On-Ramp Platforms
1inch non-custodial EOA no interface yes yes no 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 no yes yes mobile
Bitski custodial EOA no interface yes no browser, api/sdk
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 no yes mobile
D’Cent* hybrid EOA no interface yes yes no mobile
Exodus* non-custodial EOA no no no yes mobile, desktop
Gnosis Safe* non-custodial smart contract yes interface yes no no mobile, browser, api/sdk
Guarda non-custodial EOA no no no yes yes mobile, browser, desktop
Huobi non-custodial EOA no no no yes no mobile
Ledger* non-custodial EOA no interface no no no hardware, mobile, desktop
Loopring non-custodial smart contract 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 mobile, desktop
MyEtherWallet* non-custodial EOA no interface no mobile
Opera Crypto Browser* non-custodial EOA no support yes mobile, browser
Pillar non-custodial EOA no interface no mobile
Rainbow non-custodial EOA no interface yes mobile, api/sdk
SafePal* non-custodial EOA no no yes hardware, mobile, api/sdk
Sequence non-custodial smart contract no interface no browser, api/sdk
SimpleHold non-custodial EOA no no no mobile, api/sdk
SteakWallet non-custodial EOA no interface no mobile, api/sdk
TokenPocket non-custodial EOA no support yes yes no mobile, browser, api/sdk
Torus non-custodial EOA no support no no no browser, api/sdk
Trezor* non-custodial EOA no support no hardware, mobile
Trust Wallet* non-custodial EOA no support yes mobile
Unstoppable non-custodial EOA no no yes mobile, api/sdk
Venly hybrid smart contract no interface no browser, api/sdk
Wirex* non-custodial EOA no no no mobile
XDeFi non-custodial EOA no interface no no no browser
Zerion non-custodial EOA no no yes mobile, browser

Warning

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 Dojima network.

Key Management Strategy

The following basic steps allow for the integration of a client-side application with Dojima:

  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.