public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Pavol Rusnak <stick@gk2.sk>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP32 "wallet structure" in use? Remove it?
Date: Sat, 26 Apr 2014 15:41:56 +0200	[thread overview]
Message-ID: <CAPg+sBjkrG=ZeKxweBzCHqGDMhh8CN0cFQi2g7G-qjRxicQa4g@mail.gmail.com> (raw)
In-Reply-To: <535BA597.70708@gk2.sk>

On Sat, Apr 26, 2014 at 2:24 PM, Pavol Rusnak <stick@gk2.sk> wrote:
> On 04/26/2014 12:48 PM, Tier Nolan wrote:
>> Maybe the solution is to have a defined way to import an unknown wallet?
>
> That is nonsense. There is no way how to import the wallet if you don't
> know its structure.

I agree. Especially when multiple chains are combined (multisig) for
P2SH usage, defining things like a gap limit becomes impossible
without knowing some metadata.

However, perhaps it is possible to define something like "BIP44
import-compatible", meaning that the application doesn't actually
support all of BIP44 features, but does guarantee not losing any funds
when imported? Similar things could be done for other purpose types.

-- 
Pieter



  reply	other threads:[~2014-04-26 13:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 10:23 [Bitcoin-development] BIP32 "wallet structure" in use? Remove it? Andreas Schildbach
2014-04-25 14:53 ` Jim
2014-04-25 15:46   ` Gregory Maxwell
2014-04-25 15:49     ` Mike Hearn
2014-04-25 21:58       ` Aaron Voisine
2014-04-26 10:36     ` Thomas Voegtlin
2014-04-26 10:48       ` Tier Nolan
2014-04-26 10:59         ` Tamas Blummer
2014-04-26 11:03           ` Tamas Blummer
2014-04-26 12:24         ` Pavol Rusnak
2014-04-26 13:41           ` Pieter Wuille [this message]
2014-04-26 16:03     ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPg+sBjkrG=ZeKxweBzCHqGDMhh8CN0cFQi2g7G-qjRxicQa4g@mail.gmail.com' \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=stick@gk2.sk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox