No description, website, or topics provided.
Switch branches/tags
Clone or download
Latest commit ee65e6a Oct 24, 2018
Failed to load latest commit information.
angular-bitauth New flow to link the bitpay card Oct 13, 2016
angular-bitcore-wallet-client Merge into copay-cash Oct 16, 2017
app-template 5.2-rc1 Oct 17, 2018
bitanalytics Updated BitAnalytics. Sep 13, 2018
bitcoin-cash-js Migrate bitcoincashjs to bitcoincashjs-fork. Jun 1, 2018
chrome-app chore(gitignore): untrack files modified by the apply task Oct 18, 2016
i18n translations from crowdin Oct 17, 2018
resources Icon for Android push notifications. Sep 15, 2018
src Merge pull request #383 from Bitcoin-com/wallet/task/557 Oct 17, 2018
test Got the Enter Amount screen unit tests running. Sep 3, 2018
util Update version and show rc-beta May 25, 2018
www Merge pull request #380 from Bitcoin-com/wallet/task/603 Oct 9, 2018
.coveralls.yml add coverage reports Jun 5, 2014
.editorconfig fix amount.js for fiat/config Aug 31, 2017
.gitignore Getting Leanplum app ID and key from outside the repo. Sep 13, 2018
.travis.yml ci(travis): no coverage is currently being generated Oct 27, 2016 Update Jul 29, 2016
Gruntfile.js Workaround for Cordova not supporting XCode 10. Oct 17, 2018
LICENSE Update LICENSE Jan 23, 2016 Instructions for building. Sep 14, 2018 update backup recovery info Jan 13, 2017 update doc Nov 10, 2015
bower.json Update bower.json Aug 17, 2018
build.json fix appxmanifest values Jun 22, 2017 Cleaned up log message. Aug 17, 2018
fixFirebasePlugin.js Update: Fixes issue with building due to new update of Google Play se… Mar 28, 2018
jsdoc.conf.json JSDocs generated by grunt Sep 14, 2014
package.json Fix package.json. Aug 27, 2018

The wallet is a fork of the Copay Wallet (

The wallet is a secure bitcoin wallet platform for both desktop and mobile devices. It uses Bitcore Wallet Service (our fork of the Bitpay Bitcore Wallet Service) (BWS) for peer synchronization and network interfacing.

Binary versions of The wallet are available for download at

For a list of frequently asked questions please visit the Wallet FAQ.

Main Features

  • Multiple wallet creation and management in-app
  • Creates both Bitcoin Cash (BCH) and Bitcoin Core (BTC) wallets by default
  • 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)
  • 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, Linux, Windows and OS X devices

Building the wallet

You don't need to run npm install, run apply:bitcoincom instead

npm run apply:bitcoincom

There is a bug when building the next step, you will need to go directly into one of the javascript files in node_modules

nano node_modules/asn1.js-rfc5280/index.js

Delete the whole try catch part at the top, replace it with only

var asn1 = require('asn1.js');

If you don't do this, you will get this error:

» <!doctype html>
» ^
» ParseError: Unexpected token

Testing in a Browser

Note: This method should only be used for development purposes. When running the wallet in a normal browser environment, browser extensions and other malicious code might have access to internal data and private keys.

Clone the repo and open the directory:

git clone
cd Wallet

Ensure you have Node installed, then install and start the wallet:

npm run apply:bitcoincom
npm start

Visit localhost:8100 to view the app.

A watch task is also available to rebuild components of the app as changes are made. This task can be run in a separate process – while the server started by npm start is running – to quickly test changes.

npm run watch

External Config

When creating the production version, the build scripts expect a configuration file called leanplum-config.json to be in the directory that contains the project folder, with contents in the following format:

  "dev": {
    "appId": "",
    "key": ""
  "prod": {
    "appId": "",
    "key": ""

Testing on Real Devices

It's recommended that all final testing be done on a real device – both to assess performance and to enable features that are unavailable to the emulator (e.g. a device camera).


Follow the Cordova Android Platform Guide to set up your development environment.

When your developement enviroment is ready, run the start:android npm package script.

npm run apply:bitcoincom
npm run start:android


Follow the Cordova iOS Platform Guide to set up your development environment.

When your developement enviroment is ready, run the start:ios npm package script.

npm run apply:bitcoincom
npm run start:ios

Desktop (Linux, macOS, and Windows)

The desktop version of the wallet currently uses NW.js, an app runtime based on Chromium. To get started, first install NW.js on your system from the NW.js website.

When NW.js is installed, run the start:desktop npm package script.

npm run apply:bitcoincom
npm run start:desktop

Build wallet App Bundles

Before building the release version for a platform, run the clean-all command to delete any untracked files in your current working directory. (Be sure to stash any uncommited changes you've made.) This guarantees consistency across builds for the current state of this repository.

The build:*-release commands build the production version of the app, and bundle it with the release version of the platform being built.


npm run clean-all
npm run apply:bitcoincom
npm run build:android-release


npm run clean-all
npm run apply:bitcoincom
npm run build:ios-release

Desktop (Linux, macOS, and Windows)

npm run clean-all
npm run apply:bitcoincom
npm run build:desktop-release

About The Wallet


The wallet 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, the wallet 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.

The wallet 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. Wallet Backups and Recovery

The wallet 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.

Wallet Export Format

The wallet encrypts the backup with the Stanford JS Crypto Library. To extract the private key of your wallet you can use, 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!

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.

Bitcore Wallet Service

The wallet depends on Bitcore Wallet Service (BWS) for blockchain information, networking and synchronization. A BWS instance can be setup and operational within minutes or you can use a public instance like Switching between BWS instances is very simple and can be done with a click from within the wallet. BWS also allows the wallet to interoperate with other wallets like [Bitcore Wallet CLI] (


The wallet 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 wallet documentation and application text into your native language.

To download and build using the latest translations from Crowdin, please use the following commands:

cd i18n
node crowdin_download.js

This will download all partial and complete language translations while also cleaning out any untranslated ones.

Contributing to this project

Anyone and everyone is welcome to contribute. Please take a moment to review the guidelines for contributing.


Please see Support requests