The Bitcoin.com wallet is a fork of the Copay Wallet (https://github.com/bitpay/copay).
The Bitcoin.com 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 Bitcoin.com wallet are available for download at Bitcoin.com.
For a list of frequently asked questions please visit the Bitcoin.com Wallet FAQ.
- 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
Note: This method should only be used for development purposes. When running the Bitcoin.com 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 https://github.com/Bitcoin-com/Wallet.git
cd WalletEnsure you have Node installed, then install and start the Bitcoin.com wallet:
npm run apply:bitcoincom
npm startVisit 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
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:androidFollow 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:iosThe desktop version of the Bitcoin.com 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:bitcoin.com
npm run start:desktopBefore 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 final 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 final:androidnpm run clean-all
npm run apply:bitcoincom
npm run final:iosnpm run clean-all
npm run apply:bitcoincom
npm run final:desktopThe Bitcoin.com 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 Bitcoin.com 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 Bitcoin.com 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.
The Bitcoin.com 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.
The Bitcoin.com wallet 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!
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.
The Bitcoin.com 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 https://bws.bitcoin.com. Switching between BWS instances is very simple and can be done with a click from within the wallet. BWS also allows the Bitcoin.com wallet to interoperate with other wallets like [Bitcore Wallet CLI] (https://github.com/bitpay/bitcore-wallet).
The Bitcoin.com 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 Bitcoin.com 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.jsThis will download all partial and complete language translations while also cleaning out any untranslated ones.
Anyone and everyone is welcome to contribute. Please take a moment to review the guidelines for contributing.
Please see Support requests
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent