MIME-Version: 1.0
In-Reply-To: <57BEA866.5070801@jonasschnelli.ch>
References: <201608232012.12588.luke@dashjr.org>
	<90bf12f2-e109-28b4-e93e-54bbc8002cb4@electrum.org>
	<57BDACB2.9040307@jonasschnelli.ch>
	<278c940d-4b3b-2b8a-1aa5-f0991f1e6c8e@gmail.com>
	<57BEA0B0.3090308@jonasschnelli.ch>
	<756a4e04-c42d-cd61-794d-59f159c109b5@electrum.org>
	<57BEA775.4020701@jonasschnelli.ch> <57BEA866.5070801@jonasschnelli.ch>
From: Marek Palatinus <marek@palatinus.cz>
Date: Thu, 25 Aug 2016 10:50:43 +0200
Message-ID: <CAJna-Hjueu2-ShSGCTVF10x4yW5LUV1jv60SfY0rcGe149p5GA@mail.gmail.com>
To: Jonas Schnelli <dev@jonasschnelli.ch>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=94eb2c1309d60a8065053ae1809c
Subject: Re: [bitcoin-dev] BIP Status updates (including to Active/Final
 Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130
Precedence: list

--94eb2c1309d60a8065053ae1809c
Content-Type: text/plain; charset=UTF-8

As Luke pointed, BIP44 is already used by many wallets and to my knowledge
people don't have any real world issues with that, including loading funds
in another BIP44 wallet. I'm not saying that BIP44 is perfect from all
points of view, but IMO it just works for most use cases. Let's set it as
final, and propose competing standards which cover all your concerns.

slush

On Thu, Aug 25, 2016 at 10:12 AM, Jonas Schnelli via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
> > The development paradigm of "maybe detect funds" is not something we
> > should *not* encourage for Bitcoin IMO.
>
> Sorry. That was one "not" to many.
>
> </jonas>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

--94eb2c1309d60a8065053ae1809c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As Luke pointed, BIP44 is already used by many wallets and=
 to my knowledge people don&#39;t have any real world issues with that, inc=
luding loading funds in another BIP44 wallet. I&#39;m not saying that BIP44=
 is perfect from all points of view, but IMO it just works for most use cas=
es. Let&#39;s set it as final, and propose competing standards which cover =
all your concerns.<div><br></div><div>slush</div></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Thu, Aug 25, 2016 at 10:12 AM, Jon=
as Schnelli via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin=
-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfo=
undation.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span =
class=3D""><br>
&gt; The development paradigm of &quot;maybe detect funds&quot; is not some=
thing we<br>
&gt; should *not* encourage for Bitcoin IMO.<br>
<br>
</span>Sorry. That was one &quot;not&quot; to many.<br>
<br>
&lt;/jonas&gt;<br>
<br>
<br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div><br></div>

--94eb2c1309d60a8065053ae1809c--