WalletConnect PY is an open-source Python library for developers who want their Python tools to pair with mobile crypto wallets through WalletConnect v2, the protocol now branded as Reown. It is a client implementation rather than a wallet app, so there is no window to open and no balance to manage inside it.
Read this before you start: WalletConnect v1 is retired. Its bridge servers were shut down, and this library does not cover v1. The latest release is an alpha, v0.1.0-alpha.0, so treat it as experimental software and test it thoroughly. It is free and licensed under Apache 2.0.
What WalletConnect PY Is and Where It Fits
WalletConnect PY sits between your Python code and a wallet that lives on a phone. It is a building block for other software, not a product you open and use. A typical example is an account plugin for a Python development framework, which needs a way to hand signing work to a wallet the user controls.
This separation matters. Your script never needs to hold the wallet's secret keys, because approval happens in the wallet app. The library handles the messages in between, so your code can request a signature and wait for the result.
Key Concepts: Pairing, Sessions and Relays
Three terms explain most of how WalletConnect works. Pairing is the first handshake, usually shown as a link or QR code that the wallet scans or accepts. A session is the ongoing connection that follows once the user approves the pairing, and it can be closed from either side.
Relays are the servers that pass messages between the script and the wallet, since the two devices rarely reach each other directly. Understanding these pieces helps you debug a failed connection and decide which session approvals to trust.
Who Should Consider WalletConnect PY
The library suits Python developers who are building an integration and are comfortable reading code, managing a virtual environment and testing with small amounts or test networks. It is a good fit for teams that want an open-source codebase they can audit.
It is not a good fit for people who simply want to hold and send crypto on a PC. Those readers need a finished wallet with a graphical interface, and the catalog lists several in the comparison section below.
Key features
Python client for WalletConnect v2
Pairing with mobile wallets
Relaying signing requests
Supported coins
The library does not carry its own coin list. Which chains and assets you can work with depends on the mobile wallet you pair with and on the requests your Python tool sends.
How to install Walletconnect PY on Windows
- 1
Get the files from the official source
Download only from the official website or the project's GitHub Releases page at github.com/apeworx/walletconnect-py. Windows builds are listed as likely, so look for Windows files on the releases page. Avoid mirrors and links shared in chats or forums.
- 2
Verify the download
Compare the file's SHA-256 checksum with the value published with the release, or check the signature if one is provided. Do not run a file whose hash does not match.
- 3
Create a separate Python environment
Set up a virtual environment for this project so the library's dependencies stay isolated from your other tools. Then follow the package installation steps in the repository README.
-
Install and test pairing
Install the library into that environment and run a small test script that starts a pairing request. Confirm the session on your wallet before you send any real signing request.
How to use Walletconnect PY
Using WalletConnect PY is a developer task rather than a click-and-go app. The usual flow runs inside a Python script or an account plugin that calls the library.
- Install the library in a virtual environment and confirm your script imports it without errors.
- Start a session from your script, which produces a pairing link or code.
- Open your mobile wallet, scan or paste the pairing link, and approve the connection.
- Send a harmless test request, such as a short message to sign, and check that the wallet displays it.
- Read every request on the phone before approving. Reject anything you did not expect.
- Close the session when testing is finished, so no connection stays open.
Pros & cons
- Free and open source under the Apache 2.0 license
- Gives Python tools a route to mobile wallets through WalletConnect v2
- Source code is public on GitHub for review
- Fits developers building account plugins and similar tooling
- WalletConnect v1 is retired, so this is not a v1 solution
- The latest release is an alpha (v0.1.0-alpha.0)
- It is a developer library with no graphical interface
- Windows support is likely but should be confirmed on the releases page
Is Walletconnect PY safe?
WalletConnect v1 is dead, and this library is still experimental: the latest release is an alpha, so it is not a mature production tool. Download files only from the project's GitHub Releases page or its official website, and check the SHA-256 checksum or signature before running anything. Keep the code in a folder you control. Never enter a seed phrase on a third-party website or into a script prompt. Review every signing request on your mobile wallet, since a session approval can authorize actions. Check the latest version on the official website before you start.
- Official source only. Download from github.com/apeworx/walletconnect-py. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Most programs in this catalog are end-user wallets. Coinomi covers more than 1,700 assets, Exodus adds a built-in exchange on the desktop, Atomic Wallet lists over 500 coins, and Trust Wallet runs as a browser extension on PC. Frame is a system-level Web3 wallet for the desktop. WalletConnect PY is different: it is a library that lets your own Python code request signatures from a wallet. If you want to hold and manage funds, choose one of those wallets. If you are building a Python tool that needs pairing, this library is the relevant piece.
Specifications
- Price
- Free
- Type
- Open source
- License
- Apache 2.0
- Latest version
- v0.1.0-alpha.0
- Last update
- 28 Oct 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/apeworx/walletconnect-py
Frequently asked questions
No. WalletConnect PY is a Python library for developers. It lets Python code pair with a mobile wallet through WalletConnect v2 and send signing requests to it. You do not store funds inside it, and there is no graphical interface for managing a balance.
The code is open source under Apache 2.0, so it can be reviewed. However, the latest release is an alpha, and the protocol generation it was built around, WalletConnect v1, has been retired. Get the files only from the project's own repository, check the checksum, and review every request on your wallet before approving it.
No. WalletConnect v1 is dead because its bridge servers were shut down, and this library does not act as a v1 client. It is meant for WalletConnect v2, which the project now presents under the Reown name.
Yes. The library is listed as free and is released under the Apache 2.0 license, which allows use, modification and redistribution under its terms. Read the license file in the repository for the exact conditions before you build a product on it.
Windows support is likely, since the project builds for Windows, but check the releases page for files that match your system. The library runs from a Python environment rather than installing like a typical Windows application.
Reown is the new name the project uses for WalletConnect v2, so the same protocol is described under both names. WalletConnect PY is a client for that protocol, which means the library works with the current generation rather than the retired v1 system.
Verdict
WalletConnect PY suits Python developers who are building tools that need to pair with mobile wallets over WalletConnect v2. It is free, open source and readable in its repository. It is an alpha library rather than a finished product, and it sits on a protocol generation that has replaced the retired v1. Choose it if you are writing the integration yourself and can test carefully. If you simply want to hold and send crypto on your PC, pick a dedicated wallet from the comparison above.