From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Marek Palatinus <marek@palatinus.cz>
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
Date: Thu, 25 Aug 2016 11:02:27 +0200 [thread overview]
Message-ID: <CAPg+sBidFN7o4HSFqL_MXnSU9vhQFo2bDorPu_MiZWutcV4ecw@mail.gmail.com> (raw)
In-Reply-To: <CAJna-Hjueu2-ShSGCTVF10x4yW5LUV1jv60SfY0rcGe149p5GA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
This is not the place to discuss the merits and/or issues of these BIPs,
only whether they should be treated as final.
On Aug 25, 2016 10:51, "Marek Palatinus via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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
>>
>>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2404 bytes --]
prev parent reply other threads:[~2016-08-25 9:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 20:12 [bitcoin-dev] BIP Status updates (including to Active/Final Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130 Luke Dashjr
2016-08-23 20:54 ` Kenneth Heutmaker
2016-08-24 6:59 ` Jonas Schnelli
2016-08-24 8:34 ` Gregory Maxwell
2016-08-24 12:51 ` Thomas Voegtlin
2016-08-24 13:47 ` Andreas Schildbach
2016-08-24 18:22 ` Luke Dashjr
2016-08-24 14:18 ` Jonas Schnelli
2016-08-24 14:42 ` Jochen Hoenicke
2016-08-25 7:39 ` Jonas Schnelli
2016-08-25 7:56 ` Thomas Voegtlin
2016-08-25 8:08 ` Jonas Schnelli
2016-08-25 8:12 ` Jonas Schnelli
2016-08-25 8:50 ` Marek Palatinus
2016-08-25 9:02 ` Pieter Wuille [this message]
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+sBidFN7o4HSFqL_MXnSU9vhQFo2bDorPu_MiZWutcV4ecw@mail.gmail.com \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=marek@palatinus.cz \
/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