danielle
Pivian
RejectedPromise
3
May '17
Proposal
Implement a new dialogue in the PIVX-QT wallet, which allows users to create multisignature addresses with the wallet.
##What is multisignature?
Multisignature 2 (multisig) protection would enable the wallet to require M signatures out of a predetermined group of N signatures to spend funds from a multisignature address. A simple example is a spousal savings address, which would need a 2-of-2 multisig. This would require both signatures one from each spouse, to access funds in the account. This prevents one spouse accessing savings without the others permission.
##The Creation Dialogue
multisig-gui;
hash= e6e7529794c0d2d16f93dd63bcd9f409543793a29ca7e3cb0d29b19bad0bde4d
“mnbudget vote-many e6e7529794c0d2d16f93dd63bcd9f409543793a29ca7e3cb0d29b19bad0bde4d yes” to vote in favor
“mnbudget vote-many e6e7529794c0d2d16f93dd63bcd9f409543793a29ca7e3cb0d29b19bad0bde4d no” to vote against
"mnbudget getinfo multisig-gui” to check the status
---------------------------------- Update 9/2
Hello! Sorry for the lack of communication on my end in terms of updating this page.
Here is a full update of progress on the multisig GUI:
3
May '17
Proposal
Implement a new dialogue in the PIVX-QT wallet, which allows users to create multisignature addresses with the wallet.
##What is multisignature?
Multisignature 2 (multisig) protection would enable the wallet to require M signatures out of a predetermined group of N signatures to spend funds from a multisignature address. A simple example is a spousal savings address, which would need a 2-of-2 multisig. This would require both signatures one from each spouse, to access funds in the account. This prevents one spouse accessing savings without the others permission.
##The Creation Dialogue
- Link in File drop-down menu to launch
- Prompt the user for M
- Warning message about number of signatures present to access funds
- Prompt user for N signatures
- Warning message about not losing your signatures
- Message user that multisignature address has been successfully added to the wallet
- Send button disabled if transaction contains input from a multisignature address
- Prompt user for appropriate number of signatures for each multisignature address used as input
- Send button enabled when user has entered in M matching signatures for each multisignature address
multisig-gui;
hash= e6e7529794c0d2d16f93dd63bcd9f409543793a29ca7e3cb0d29b19bad0bde4d
“mnbudget vote-many e6e7529794c0d2d16f93dd63bcd9f409543793a29ca7e3cb0d29b19bad0bde4d yes” to vote in favor
“mnbudget vote-many e6e7529794c0d2d16f93dd63bcd9f409543793a29ca7e3cb0d29b19bad0bde4d no” to vote against
"mnbudget getinfo multisig-gui” to check the status
---------------------------------- Update 9/2
Hello! Sorry for the lack of communication on my end in terms of updating this page.
Here is a full update of progress on the multisig GUI:
- the creation dialog has stayed as expected
- the send dialog has had to move to it’s own page since incompatibility with the regular send page
- sign tab - enables users to sign a multisig (which they hold a redeem script for) with the TxHex and a button click, also allows signing through private keys
- automated fees/ change - users no longer must calculate fees and manually return change as in raw transactions
- spending dialog - when creating a multisig transaction, users must no longer create the tx and then sign it separately. Upon successful creation, the local wallet automatically signs the tx and the only step left is to send the hex for others to sign