-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds multisig support #253
Conversation
matiu
commented
Dec 1, 2015
- defines 48' a purpose for multisig wallets
- adds p2sh address generate procedure
- adds Copay to 'compatible wallets'
- defines 48' a purpose for multisig wallets - adds p2sh address generate procedure - adds Copay to 'compatible wallets'
BIP's aren't usually amended after the fact, it might be an issue to introducing this a year and a half in. |
Given that the multisig extension uses a new purpose number, I dont think there could be an issue. Note that there are some BIP are received conceptually similar extensions like: |
NACK. This should go into BIP 48 according to BIP 43 specification. |
Also you should clearly state in BIP 45 that this BIP is obsoleted by BIP 48. |
Time Stamp ? On 11 December 2015 at 09:44, Pavol Rusnak notifications@github.com wrote:
|
|
||
===Purpose=== | ||
Because seeds that are part of a multisignature wallet cannot be scanned individually, a different | ||
purpose constant is must be used: 48'. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo/grammar
a different purpose constant
ismust be used
OK, closing this one then. I will submit a new proposal. This do not completely obsoletes BIP45, since with BIP45 it is possible to create wallet addresses without parties synchronization. |