Ducatus Wallet is a secure bitcoin wallet platform for both desktop and mobile devices. Ducatus Wallet uses DucatusCore Wallet Service (DWS) for peer synchronization and network interfacing.
Ducatus Wallet is fork Copay.
- Bitcoin and Bitcoin Cash coin support
- 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)
- Email notifications for payments and transfers
- Push notifications (only available for ios and android versions)
- Multiple languages supported
- Available for iOS, Android, Chrome App
Note: This method should only be used for development purposes. When running Ducatus Wallet 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:
git clone git@github.com:DUCATUS-revival/ducatus-wallet.git
cd copayEnsure you have Node v10.24.1 installed, then install and start Ducatus Wallet:
npm install
npm run apply:copay
npm run startVisit localhost:8100 to view the app.
To run the tests, run:
npm run test
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 development environment is ready, run the start:android package script.
npm run apply:copay
npm run prepare:copay
npm run start:androidFollow the Cordova iOS Platform Guide to set up your development environment.
When your development environment is ready, run the start:ios package script.
npm run apply:copay
npm run prepare:copay
npm run start:iosBefore 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 uncommitted 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 install
npm run apply:copay
npm run prepare:copay
npm run final:androidnpm run clean-all
npm install
npm run apply:copay
npm run prepare:copay
npm run final:iosPush notification doesn't work on iOS 12 due to an update of Xcode and plugin cordova-plugin-fcm.
A current workaround is to comment out the line to prevent the removal of the file during the debug build (line 56 in platforms/ios/cordova/lib/copy-www-build-step.js).
Ducatus 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, Ducatus 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.
Ducatus 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.
Ducatus 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/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 Ducatus Wallet without using Copay or the Wallet Service, check the Copay Recovery Tool.
Ducatus Wallet encrypts the backup with the Stanford JS Crypto Library. To extract the private key of your wallet you can go to settings, choose your wallet, click in "more options", then "wallet information", scroll to the bottom and click in "Extended Private Key". 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 use BIP45. Also note non-multisig wallets use address types Pay-to-PublicKeyHash (P2PKH) while multisig wallets still use Pay-to-ScriptHash (P2SH) (key addressType at the backup):
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 DWS 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.
Ducatus 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.
Ducatus Wallet depends on DucatusCore Wallet Service (DWS) for blockchain information, networking and wallet synchronization.
Ducatus uses the MAJOR.MINOR.BATCH convention for versioning. Any release that adds features should modify the MINOR or MAJOR number.
Ducatus is released under the MIT License. Please refer to the LICENSE file that accompanies this project for more information including complete terms and conditions.
Copyright 2022 Ducatus.