Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

On Sat, Apr 26, 2014 at 6:08 AM, Thomas Voegtlin wrote: > Perhaps the only thing that needs to be standardized is the order of > public keys in the redeem script: I think they should be sorted, so that > the p2sh address does not depend on the order of pubkeys. Yes. That solution is already impl

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

Ah, I see now. Thanks. And actually now I re-read it, Manuel's explanation was clear, it just didn't sink in for some reason. -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eX

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

On 04/26/2014 04:33 PM, Mike Hearn wrote: > > Let's assume we use one shared branch for everyone. Then two > cosigners could need a new receiving address at the same time, and > get the next unused address on that branch. > > This is the part I struggle to understand. There is no share

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

> > Let's assume we use one shared branch for everyone. Then two cosigners > could need a new receiving address at the same time, and get the next > unused address on that branch. > This is the part I struggle to understand. There is no shared branch because each user/cosigner has their own unique

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

On Apr 26, 2014 6:43 AM, "Mike Hearn" wrote: > > I'm not sure I understand why you need any special structure for this at all. The way I'd do it is just use regular HD wallets for everyone, of the regular form, and then swap the watching keys. Why do people need to be given a cosigner index at all

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

Le 26/04/2014 11:43, Mike Hearn a écrit : > I'm not sure I understand why you need any special structure for this at > all. The way I'd do it is just use regular HD wallets for everyone, of the > regular form, and then swap the watching keys. Why do people need to be > given a cosigner index at a

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

I'm not sure I understand why you need any special structure for this at all. The way I'd do it is just use regular HD wallets for everyone, of the regular form, and then swap the watching keys. Why do people need to be given a cosigner index at all, given that they all have unique root keys anyway

Re: [Bitcoin-development] New BIP32 structure for P2SH multisig wallets

I will just chime in that I've been working on a similar spec for Armory to implement P2SH multisig and I came up with basically an identical scheme. I think you covered most of what is needed. The one thing I did differently was try to match the BIP 32 structure, by keeping the original 3 level

[Bitcoin-development] New BIP32 structure for P2SH multisig wallets

Hi, I'm part of the team building copay , a multisignature P2SH HD wallet. We've been following the discussion regarding standardizing the structure for branches both on this list and on github (1 , 2 <