The WalletConnect Network powers over 65,000+ apps and 700+ wallets, including EOAs, custodians, and hardware wallets, giving millions of users a secure way to access your application.

Connect your App
 to the WalletConnect Network

Built into the largest onchain apps

From DeFi to payments to gaming, identity, and beyond. WalletConnect powers secure onchain connections across 65,000+ apps.

Most applications choose to onboard to the network via an SDK partner who makes the integration easy. See below for a list of our registered partners

Understanding the WalletConnect Network

WalletConnect is an open-source protocol that securely connects wallets to apps. By standardizing wallet-to-app communication, it enables millions to safely and easily engage with onchain applications.

Understanding the WalletConnect Network
How do I choose the right SDK for my app?

Different SDKs are designed for different needs. The best fit depends on what you're building and who you're building for. Here are a few things to consider:

  • Chains: Does the SDK support the networks your app runs on?
  • Wallet support: Do you need embedded wallets, external wallet connections, or both?
  • Features: Are onramps, swaps, or payments part of your flow?
  • Platform: Are you building for mobile, web, or both?
  • Data: Will you need usage insights or analytics?
  • Scale and support: Do you want full control or a managed experience

    Take a moment to map your app’s goals, and you’ll know what to prioritize.

What does it cost?

Some SDKs are free and open source. Others offer paid plans with additional features, hosted infra, or support.

How hard is it to integrate?

Most SDKs take minutes to get started.

What chains are supported?

Support varies. Some SDKs focus on EVM only, while others support Solana, Bitcoin, and more.

Do all of these SDK support WalletConnect?

Yes. All of these SDKs connect to the WalletConnect Network in some way. They help your app talk to 700+ wallets and 65,000+ other apps. Some SDKs offer WalletConnect as a built-in layer, while others require you to configure it manually.