-Eric

On Mar 11, 2014, at 7:35 PM, Alan Reiner <etotheipi@gmail.com> = wrote:

=20 =20
I might as well throw in a word about Armory. After our next release in a couple weeks, we will be going full-speed at new wallets and BIP32 integration. Just like Jean-Pierre = mentioned, we'll be using parallel trees to generate P2SH addresses after sorting the keys lexicographically. We plan to introduce the concept of a wallet "bundle" (that name is far from concrete... I'd love a better word). All wallets in a bundle are protected by = the same backup, and stored in the same file. The default behavior = will be use new branches in the same BIP32 tree when a user creates a new "wallet", though we will allow multiple bundles in advanced and expert usermode (which is needed to have watching-only wallets from a different seed created from an offline computer).

However, we do plan to allow separate parties to create multisig-intended wallets with public parts that can be exported and combined with other users. We feel this is critical, as it = allows for linked wallets in which there was never a single-point of failure from key-generation to signing. This is especially important for contexts where employees may be handling a company's Bitcoins wallets.

On this topic, I have gotten a lot of inquiries into BIP 38 and = 39. I was not clear whether those BIPs were worth prioritizing ... i.e. is there a general consensus from a variety of wallet developers that they should be supported? Rather, I'm happy to start prioritizing them if others do too, but I haven't spent much time trying to understand them to even know if they're mature, yet.

-Alan

On 03/11/2014 08:29 PM, Jean-Pierre Rupp wrote:
Hello people,

We are working on some of this stuff. We had some very early draft on
how we envisioned multisig happening. It is all implemented in Haskoin
available as multiple repositories in Github. I am happy to see this
gathering momentum.

Our multisig system uses BIP-0032 HD wallets, and there will soon be
BIP-0039 support for keys compatibility.

Our wallet uses synced trees rooted at the extended pubkeys of the
participants. Currently we are sorting public keys in the scripts to
avoid ambiguity.

Download haskoin-wallet:

cabal install haskoin-wallet

Check out the hw command (installed in ~/.cabal/bin/hw). Use importtx to
bring transactions into the wallet. You must initialize first with a
seed and create an account. It supports both regular and multisig =
accounts.

Perhaps this can lead to interesting discussions on key exchange, and
the appropriate handling of wallet metadata. I=92d love to work on a
proper standard that could lead us to compatible implementations.

This document explains how we do it now:

http://haskoin.c=
om/~xeno/hd-multisig-wallet.html

Cheers!
----------------------------------------------------------------=
--------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and =
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTe=
ch
_______________________________________________
Bitcoin-development mailing list
Bitcoin-developm=
ent@lists.sourceforge.net
=
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
= --------------------------------------------------------------------------= ----
Learn Graph Databases - Download FREE O'Reilly Book
"Graph = Databases" is the definitive new guide to graph databases and = their
applications. Written by three acclaimed leaders in the = field,
this first edition is now available. Download your free book = today!
http://p.sf.net/sfu/13534_NeoTech_________________________= ______________________
Bitcoin-development mailing = list
Bitcoin-development@lists.sourceforge.net
https://lists.sourcef= orge.net/lists/listinfo/bitcoin-development