Cronos EVM Docs
  • Getting Started
    • Getting Started
    • Background
    • Architecture
    • Cronos roadmap
  • FOR USERS
    • 💳Crypto.com Card Top Up
    • 🔥Crypto Wallets
    • 🦊MetaMask Configuration
    • 🦁Brave Wallet
    • 🌉Bridges
      • From the Crypto.com App and Exchange
        • From the Crypto.com App
        • From the Crypto.com Exchange
      • IBC (Cronos POS Chain, other Cosmos chains)
        • Cronos Bridge Web App
      • Independent bridges
      • FAQs for Bridge transfers
      • FAQs for transactions from/to centralized exchanges
    • 🚰Testnet Faucet
    • 💡Tips & FAQs
    • 👮Key Principles for Wallet Security
    • GasTracker
  • FOR DAPP DEVELOPERS
    • 💡Founder FAQs
    • 🏅Hacker's Getting Started Resources
    • 📃Smart Contracts
      • Contract Development on Testnet
      • Contract Deployment and Verification
      • Contract Verification Export: Cronoscan To Cronos Explorer
      • Best Practices
      • Token Contract Addresses
    • 💻dApp Creation
      • Free and commercial RPC endpoints
      • Wallet integrations
      • Web3-wallet
      • JSON-RPC methods
      • Address Conversion
      • Swagger Playground
    • ⚙️Dev Tools & Integrations
      • All dev tools & integrations
      • Account Abstraction
      • Band Protocol
      • Banxa
      • GoldRush
      • Cronos Safe
      • Flair
      • Google Bigquery
      • Moralis
      • Pyth
      • Secret Network
      • SubQuery
      • Witnet
    • Crypto.com AI Agent SDK
  • FOR NODE HOSTS
    • Running nodes
      • Cronos Mainnet
        • Quicksync
        • State-sync
        • Public Node Sync
        • KSYNC
        • The "Huygen" upgrade guide (v0.6.* to v0.7.*)
        • The "v0.7.0-hotfix" upgrade guide (v0.7.* to v0.8.*)
        • The "Galileo" upgrade guide (v0.8.* to v1.0.*)
        • The "Titan" upgrade guide (v1.0.* to v1.1.0)
        • The "v1.2" upgrade guide (v1.1.* to v1.2.0)
        • The "v1.3" upgrade guide (v1.2.* to v1.3.0)
        • The "v1.4" Pallene upgrade guide (v1.3.* to v1.4.1)
        • Patching Unlucky & Duplicate Tx
      • Cronos Testnet
      • Devnet
      • Best Practices
      • Cronosd build with Nix
      • VersionDB
      • MemIAVL
      • Local State Sync
    • Cronosd
  • CRONOS PLAY
    • Introduction
    • Unity Engine
      • Current Version
      • Legacy Version
        • EVM
        • Login Example
        • Custom RPC
        • ERC20
        • ERC721
        • ERC1155
      • Useful Links
    • Unreal Engine
      • Installation and Enabling
      • Working with Blueprint
        • Actors and Blueprint Classes
        • Cronos Configuration
        • Connect Defi Desktop/Onchain Wallet with URI
        • Connect Wallets with QR Code
        • Connect WalletConnect Step by Step
        • WalletConnect 2.0 and Unreal Engine 5: Hello World Example
        • Wallet
        • ERC20
        • ERC721
        • ERC1155
        • Broadcast Transactions
        • Get Tokens or Transactions
      • Working with C++
        • Creating a C++ Project
        • Creating a child DefiWalletCoreActor
        • Querying a contract
        • Customizing Network
      • Demo
    • Cronos Play C++ SDK
    • Crypto.com Pay Integration
    • Cronos Play FAQ
  • Block Explorers
    • Block Explorer and API Keys
    • Cronos Explorer
    • Cronoscan
  • CRONOS CHAIN PROTOCOL
    • Chain ID and Address Format
    • Cronos General FAQ
    • Genesis
    • Modules
      • module_bank
      • module_distribution
      • module_slashing
      • module_feemarket
    • Chain Details
      • List of parameters
      • Technical glossary
      • Protocol Documentation
    • Common IBC Commands
  • Cronos zkEVM
    • Cronos zkEVM
  • Resources
    • Media / brand kit
Powered by GitBook
On this page
  • Overview
  • Basic tutorial
  • Crypto.com Onchain Wallet

Was this helpful?

Edit on GitHub
  1. FOR DAPP DEVELOPERS
  2. dApp Creation

Wallet integrations

PreviousFree and commercial RPC endpointsNextWeb3-wallet

Last updated 4 months ago

Was this helpful?

Overview

Cronos chain is supported by the following self-custodial wallets:

  • Crypto.com Onchain Wallet.

  • Rabby (rabby.io)

  • MetaMask (requires custom network configuration) (metamask.io).

  • Trust Wallet.

  • and more than 30 other wallets (you can see a more complete list of dev tools ).

Crypto.com Onchain Wallet, Trust Wallet and MetaMask have mobile apps that include in-app dApp browsers. Users can access dApps on the go via these in-app browsers. We recommend that all dApp developers integrate with these 3 wallets at least, and more if possible.

Basic tutorial

for a basic example on how to implement the main wallet connection methods available to Cronos dApp developers.

Crypto.com Onchain Wallet

A non-custodial wallet to store, earn, and grow your crypto

is a non-custodial wallet that gives users full control of their crypto and private keys. Private keys are encrypted locally on the user’s mobile phone, and protected by Biometric Authentication and 2-Factor Authentication.

If you are a dApp developer, integration with the Crypto.com Onchain Wallet is the best way to deliver a smooth user experience to more than 50 million Crypto.com customers.

Users will be able to login with your dApp in several ways:

  • On Mobile, they can visit your dApp and connect to it via the in-app browser of the Crypto.com Onchain Wallet iOS or Android apps.

  • On Desktop, they can install the Crypto.com Wallet Extension from the Chrome extension store into their Chrome, Edge or Brave browser. The extension can be connected to the Crypto.com Onchain Wallet mobile app (in which case the user will need to confirm each transaction on their mobile phone), or alternatively it can work as a standalone extension entirely in the browser.

  • Finally, on Desktop too, the Crypto.com Onchain Wallet is available as a standalone app.

To get your dApp listed on the dApp section of Crypto.com Onchain Wallet, the steps are as below:

  • Ensure your dApp successfully integrates the Crypto.com Wallet Extension SDK, with a functional wallet connection (refer to the details below)

  • The relevant team will review your submission and may proceed with the listing of your dApp.

As a developer, if you would like to offer all the mobile and desktop connection options provided by the Crypto.com Onchain Wallet, the first step is to integrate your dApp with the Crypto.com Wallet Extension.

Once the Wallet Extension is working, all the other connection methods should start working as well, even on mobile, since they are supported by the same SDKs.

The Crypto.com Wallet Extension currently supports the following networks:

  • Cronos

  • Cronos POS Chain

  • Ethereum

  • Bitcoin

  • BNB Smart Chain

  • Polygon

  • Avalanche-C

  • Cosmos

  • Fantom

  • Arbitrum

  • Optimism

  • Gnosis

  • Aptos

  • All other EVM-compatible networks (manual configuration)

  • Cronos Testnet

  • Goerli Testnet

  • Scroll Alpha Testnet

  • Aptos Devnet

  • Aptos Testnet

Once the connector is activated, your dApp can retrieve the provider using getProvider() and subsequently use it via a common Web3 SDK like ethers.js.

Some developers may need to dig deeper into the documentation, for example if they are not using React or need more customization. In this case, please refer to:

Submit your dApp details using the

The official repository and documentation of Crypto.com Wallet Extension are available at: .

For most dApp developers, the best way to integrate the Crypto.com Wallet Extension is to develop your application's front-end in React and to use the DeFiWeb3Connector object which is provided by the "@deficonnect/web3-connector" npm package as documented here: .

Github:

Document:

💻
here
Follow this link
Crypto.com Onchain Wallet
Submission Form
https://github.com/crypto-com/deficonnect-monorepo
https://github.com/crypto-com/deficonnect-monorepo/tree/develop/packages/web3-connector
https://github.com/crypto-com/deficonnect-monorepo
https://github.com/crypto-com/deficonnect-monorepo/wiki/Chrome-Extension-Wallet-Integration