npm install @owstack/ows-walletOWS Wallet
=======
This is a secure wallet platform for both desktop and mobile devices. The wallet uses the following wallet services for peer synchronization and network interfacing.
* BCH Wallet Service (BCH)
* BTC Wallet Service (BTC)
Binary versions of this wallet are available for download at OpenWalletStack.com. Binaries are signed with the key wallet@openwalletstack.com – See the section How to Verify Wallet Signatures for details.
For a list of frequently asked questions please visit the Wallet 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
- Device-based security: all private keys are stored locally, not in the cloud
- Synchronous access across all major mobile and desktop platforms
- Support for over 150 currency pricing options
- 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 OSX devices
- BIP32 Hierarchical deterministic (HD) address generation and wallet backups
- Support for Bitcoin testnet wallets
- Payment protocol (BIP70-BIP73) support: easily-identifiable payment requests and verifiable, secure bitcoin payments
- 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)
- BIP32 Hierarchical deterministic (HD) address generation and wallet backups
- Payment protocol (BIP70-BIP73) support: easily-identifiable payment requests and verifiable, secure bitcoin payments
- Unit denomination in BCH or bits
- Mnemonic (BIP39) support for wallet backups
- Paper wallet sweep support (BIP38)
> Note: This method should only be used for development purposes. When running 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.
Clone the repo and open the directory:
``sh`
git clone https://github.com/owstack/ows-wallet.git
cd ows-wallet
Ensure you have Node installed, then install and start the wallet:
`sh`
npm run apply:ows-wallet
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
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.
`sh`
npm run apply:ows-wallet
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.
`sh`
npm run apply:ows-wallet
npm run start:ios
Follow the Cordova Windows Phone Platform Guide to set up your development environment.
When your developement enviroment is ready, follow this instructions:
- Go to app-template folder, search for config-template.xml and then remove this line:
`sh`
and then enable this one:sh`
- Run:sh`
npm run clean-all
npm run apply:ows-wallet
npm run start:windows
- Then open the project file with VS inside cordova/platform/windows/
The desktop version 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.
`sh`
npm run apply:ows-wallet
npm run start:desktop
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 final commands build the production version of the app, and bundle it with the release version of the platform being built.
`sh`
npm run clean-all
npm run apply:ows-wallet
npm run final:android
`sh`
npm run clean-all
npm run apply:ows-wallet
npm run final:ios
- Install Visual Studio 2015 (or newer)
- Go to app-template folder, search for config-template.xml and then remove this line:
`sh`
and then enable this one:sh`
- Run:sh`
npm run clean-all
npm run apply:ows-wallet
npm run final:windows
- Then open the project file with VS inside cordova/platform/windows/
`sh`
npm run clean-all
npm run apply:ows-wallet
npm run final:desktop
> cd chrome-app/
`sh`
npm run apply:ows-wallet
grunt
make
On success, the Chrome extension will be located at: browser-extensions/chrome/ows-wallet-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.
To enable external services, set the WALLET_EXTERNAL_SERVICES_CONFIG_LOCATION environment variable to the location of your configuration before running the apply task.
`sh`
WALLET_EXTERNAL_SERVICES_CONFIG_LOCATION="~/.ows-wallet/externalServices.json" npm run apply:ows-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.
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.
Information about backup and recovery procedures is available at: https://github.com/owstack/ows-wallet/blob/master/backupRecovery.md
It is possible to recover funds from a wallet without using the wallet app or the wallet service, check the OWS Wallet Recovery Tool.
The 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!
The backup also contains the key publicKeyRing that holds the extended public keys of the copayers.derivationStrategy
Depending on the key , addresses are derived usingaddressType
BIP44 or BIP45. Wallets always use BIP44, all previous wallets use BIP45. Also note that non-multisig wallets use address types Pay-to-PublicKeyHash (P2PKH) while multisig wallets still use Pay-to-ScriptHash (P2SH) (key at the backup):
| Wallet Version | Wallet Type | Derivation Strategy | Address Type |
|---|---|---|---|---|
| All | Non-multisig | BIP44 | P2PKH |
| All | Multisig | BIP44 | P2SH |
| All | Multisig Hardware wallets | BIP44 (root m/48') | P2SH |
The wallet 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.
The wallet depends on wallet services for blockchain information, networking and copayer synchronization. A wallet service instance can be setup and operational within minutes or you can use a public instance like https://bws.openwalletstack.com. Switching between wallet service instances is very simple and can be done with a click from within the wallet. The wallet service also allows the wallet to interoperate with other wallets like BTC Wallet CLI.
Note: Hardward wallet support only available for bitcoin (BTC) wallets.
The wallet 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, the app 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 send or accept buttons.
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 the wallet, see: https://github.com/owstack/ows-wallet/blob/master/backupRecovery.md#hardware-wallets
To download and build using the latest translations from Crowdin, please use the following commands:
`sh`
cd i18n
node crowdin_download.js
This will download all partial and complete language translations while also cleaning out any untranslated ones.
Translation Credits:
- TBD
convention for versioning. Any release that adds features should modify the MINOR or MAJOR number.$3
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.
$3
- 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.How to Verify Signatures
1. Download the
wallet@openwalletstack.com public key (gpg --recv-keys 1112CFA1)
2. Download the wallet binary ($FILENAME) and signature file ($FILENAME.sig)
3. Verify the signature by running:` bash
$ gpg --verify \
$FILENAME.sig \
$FILENAMEIt should return:
Good signature from "OWS Wallet (visit openwalletstack.com) "
`$3
Instead of importing the public key from a public server (like gnu's) you can grab it from here:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: SKS 1.1.5
Comment: Hostname: pgp.mit.eduTBS
-----END PGP PUBLIC KEY BLOCK-----
Save that text to /tmp/key, and then import it as follows:
gpg --import /tmp/key
Anyone and everyone is welcome to contribute. Please take a moment to
review the guidelines for contributing.
* Bug reports
* Feature requests
* Pull requests
Please see Support requests
OWS Wallet is released under the MIT License. Please refer to the LICENSE file that accompanies this project for more information including complete terms and conditions.