Copay is an easy-to-use, open-source, multiplatform, multisignature, secure bitcoin wallet platform for both individuals and companies. Copay uses Bitcore Wallet Service (BWS) for peer synchronization and network interfacing.
For a list of frequently asked questions please visit the Copay FAQ.
- Multiple wallet creation and management in-app
- Intuitive, multisignature security for personal or shared wallets
- Easy spending proposal flow for shared wallets and group payments
- BIP32 Hierarchical deterministic (HD) address generation and wallet backups
- Device-based security: all private keys are stored locally, not in the cloud
- Support for Bitcoin testnet wallets
- Synchronous access across all major mobile and desktop platforms
- Payment protocol (BIP70-BIP73) support: easily-identifiable payment requests and verifiable, secure bitcoin payments
- Support for over 150 currency pricing options and unit denomination in BTC or bits
- Mnemonic (BIP39) support for wallet backups
- Paper wallet sweep support (BIP38)
- Hardware wallet support (Trezor and Ledger) (only in Chrome App version)
- Email notifications for payments and transfers
- Push notifications (only available for ios and android versions)
- Customizable wallet naming and background colors
- Multiple languages supported
- Available for iOS, Android, Windows Phone, Chrome App, Linux, Windows and OS X devices
Clone the repo and open the directory:
git clone https://github.com/bitpay/copay.gitcd copay
Ensure you have Node installed, then install and start Copay:
npm installnpm start
localhost:3000 to view the app.
Note: This method should only be used for development purposes. When running Copay in a normal browser environment, browser extensions and other malicious code might have access to internal data and private keys. For production use, see the latest official releases.
- Install Android SDK
- Install Xcode 6.1 (or newer)
Before starting Copay from Xcode, add these lines to "Custom iOS Target Properties":
App Transport Security (ATS) enforces best practices in the secure connections between an app and its back end. Read complete documentation.
iPad Multitasking support requires launch story board in bundle
To fix this problem, add the following:
Add this line to your Build Settings -> Header Search Paths -> Release
- Install Visual Studio 2013 (or newer)
Copay uses NW.js (also know as node-webkit) for its desktop version. NW.js is an app runtime based on
- Install NW.js on your system from nwjs.io
npm run-script chrome
On success, the Chrome extension will be located at:
browser-extensions/chrome/copay-chrome-extension. To install it go to
chrome://extensions/ in your browser and ensure you have the 'developer mode' option enabled in the settings. Then click on "Load unpacked chrome extension" and choose the directory mentioned above.
The Copay Firefox Extension has been deprecated and is no longer supported.
Copay implements a multisig wallet using p2sh addresses. It supports multiple wallets, each with its own configuration, such as 3-of-5 (3 required signatures from 5 participant peers) or 2-of-3. To create a multisig wallet shared between multiple participants, Copay requires the extended public keys of all the wallet participants. Those public keys are then incorporated into the wallet configuration and combined to generate a payment address where funds can be sent into the wallet. Conversely, each participant manages their own private key and that private key is never transmitted anywhere.
To unlock a payment and spend the wallet's funds, a quorum of participant signatures must be collected and assembled in the transaction. The funds cannot be spent without at least the minimum number of signatures required by the wallet configuration (2-of-3, 3-of-5, 6-of-6, etc.). Once a transaction proposal is created, the proposal is distributed among the wallet participants for each to sign the transaction locally. Finally, when the transaction is signed, the last signing participant will broadcast the transaction to the Bitcoin network.
Copay also implements BIP32 to generate new addresses for peers. The public key that each participant contributes to the wallet is a BIP32 extended public key. As additional public keys are needed for wallet operations (to produce new addresses to receive payments into the wallet, for example) new public keys can be derived from the participants' original extended public keys. Once again, it's important to stress that each participant keeps their own private keys locally - private keys are not shared - and are used to sign transaction proposals to make payments from the shared wallet.
For more information regarding how addresses are generated using this procedure, see: Structure for Deterministic P2SH Multisignature Wallets.
Since v1.2 Copay uses BIP39 mnemonics for backing up wallets. The BIP44 standard is used for wallet address derivation. Multisig wallets use P2SH addresses, while non-multisig wallets use P2PKH.
Information about backup and recovery procedures is available at: https://github.com/bitpay/copay/blob/master/backupRecovery.md
Previous versions of Copay used files as backups. See the following section.
It is possible to recover funds from a Copay Wallet without using Copay or the Wallet Service, check the Copay Recovery Tool.
Copay encrypts the backup with the Stanford JS Crypto Library. To extract the private key of your wallet you can use https://bitwiseshiftleft.github.io/sjcl/demo/, copy the backup to 'ciphertext' and enter your password. The resulting JSON will have a key named:
xPrivKey, that is the extended private key of your wallet. That information is enough to sign any transaction from your wallet, so be careful when handling it!
The backup also contains the key
publicKeyRing that holds the extended public keys of the Copayers.
Depending on the key
derivationStrategy, addresses are derived using
BIP44 or BIP45. Wallets created in Copay v1.2 and forward always use BIP44, all previous wallets use BIP45. Also note that since Copay version v1.2, non-multisig wallets use address types Pay-to-PublicKeyHash (P2PKH) while multisig wallets still use Pay-to-ScriptHash (P2SH) (key
addressType at the backup):
|Copay Version||Wallet Type||Derivation Strategy||Address Type|
|>=1.5||Multisig Hardware wallets||BIP44 (root m/48')||P2SH|
Using a tool like Bitcore PlayGround all wallet addresses can be generated. (TIP: Use the
Address section for P2PKH address type wallets and
Multisig Address for P2SH address type wallets). For multisig addresses, the required number of signatures (key
m on the export) is also needed to recreate the addresses.
BIP45 note: All addresses generated at BWS with BIP45 use the 'shared cosigner index' (2147483647) so Copay address indexes look like:
m/45'/2147483647/0/x for main addresses and
m/45'/2147483647/1/y for change addresses.
Since version 1.5, Copay uses the root
m/48' for hardware multisignature wallets. This was coordinated with Ledger and Trezor teams. While the derivation path format is still similar to BIP44, the root was in order to indicate that these wallets are not discoverable by scanning addresses for funds. Address generation for multisignature wallets requires the other copayers extended public keys.
Copay depends on Bitcore Wallet Service (BWS) for blockchain information, networking and Copayer synchronization. A BWS instance can be setup and operational within minutes or you can use a public instance like
https://bws.bitpay.com. Switching between BWS instances is very simple and can be done with a click from within Copay. BWS also allows Copay to interoperate with other wallets like [Bitcore Wallet CLI] (https://github.com/bitpay/bitcore-wallet).
Copay supports Ledger and Trezor hardware wallets. Hardware wallet support is only available through the Chrome App. Ledger support is only available on multisig wallets.
To use Ledger, you need to have the Ledger Chrome App installed, available at: https://chrome.google.com/webstore/detail/ledger-wallet/kkdpmhnladdopljabkgpacgpliggeeaf
To use Trezor, you need to have the Trezor Chrome Extension installed, available at: https://chrome.google.com/webstore/detail/trezor-chrome-extension/jcjjhjgimijdkoamemaghajlhegmoclj
To create or join a wallet using Ledger or Trezor go to:
Add Wallet -> Create or Join -> Advanced options -> Wallet Seed -> select Trezor or Ledger
Both devices support multiple accounts, so you can use them for multiple wallets. Select the account and then click on create or join.
It is also possible to import a wallet from a device using: Add Wallet -> Import -> Hardware wallet
Here it is also necesary to select the account number.
When creating or joining a wallet, Copay will ask for two public keys for the device. One public keys is used for the wallet itself and the other is used as an entropy source to create a private / public key pair for signing requests to the Wallet Service.
Every time you need to sign a transaction, the device will be needed to perform the signature. Follow the on screen instructions after clicking the
Finally, in case you lose the device and you have the 24 word seed for the device, you can recover access to your funds using Copay, see: https://github.com/bitpay/copay/blob/master/backupRecovery.md#hardware-wallets
Copay uses standard gettext PO files for translations and Crowdin as the front-end tool for translators. To join our team of translators, please create an account at Crowdin and translate the Copay documentation and application text into your native language.
To download and build using the latest translations from Crowdin, please use the following commands:
cd i18nnode crowdin_download.js
This will download all partial and complete language translations while also cleaning out any untranslated ones.
- Japanese: @dabura667
- French: @kirvx
- Portuguese: @pmichelazzo
- Spanish: @cmgustavo
- German: @saschad
- Russian: @vadim0
Copay uses the
MAJOR.MINOR.BATCH convention for versioning. Any release that adds features should modify the MINOR or MAJOR number.
We release bug fixes as soon as possible for all platforms. Usually around a week after patches, a new release is made with language translation updates (like 1.1.4 and then 1.1.5). There is no coordination so all platforms are updated at the same time.
- t+0: tag the release 1.2 and "text lock" (meaning only non-text related bug fixes. Though this rule is sometimes broken, it's good to make a rule.)
- t+7: testing for 1.2 is finished, translation is also finished, and 1.2.1 is tagged with all translations along with bug fixes made in the last week.
- t+7: iOS is submitted for 1.2.1. All other platforms are submitted with auto-release off.
- t + (~17): All platforms 1.2.1 are released when Apple approves the iOS application update.
- Download the
firstname.lastname@example.org key (
gpg --recv-keys 1112CFA1)
- Download Copay binary (
$FILENAME) and signature file (
- Verify the signature by running:
$ gpg --verify \$FILENAME.sig \$FILENAME# It should return:Good signature from "Copay (visit copay.io) <email@example.com>"
Instead of importing the public key from a public server (like gnu's) you can grab it from here:
Save that text to /tmp/key, and then import it as follows:
gpg --import /tmp/key
(Thanks @pzkpfwVI and @mika-mitzahlen for this section, taken from Gist.
Anyone and everyone is welcome to contribute. Please take a moment to review the guidelines for contributing.
Please see Support requests
Copay is released under the MIT License. Please refer to the LICENSE file that accompanies this project for more information including complete terms and conditions.